migrate catalog basic rman 10.2 11.2

My rman catalog is currently in a 10.2.0.4 IS based on Windows.

I'm moving it to 11.2.0.4 SE on Linux.

I thought at first it would be a simple the schema of the source expdp, impdp rman which target.

The database is created. The user created "rman" and recovery_catalog_owner granted to him.

Exported from the current catalog with "" expdp system / * directory = dpump dumpfile = exp_rmcat_catalog.dmp = logfile = exp_rmcat_catalog.log rman schemas "»

"Copy the dump file to the new server and import with."

Impdp ${localuser} / patterns$ {localpwd} = directory of rman dumpfile logfile = DPUMP = rmcat_import.log = ${dumpfile} table_exists_action = replace

But in a second trial of the importation, he threw a lot of mistakes like

ORA-39111: type of dependent object OBJECT_GRANT: "RMAN" ignored, basic VIEW object type: "RMAN". "' TSATT_V ' already exists

OK, I understand that the 'table_exists_action"applies to the tables and objects not non-table. I was a bit surprised to find non-table that the rman schema objects, but it occurs to me that since they are, and they come from a 10 g database, could it be questions their import in a an 11 g database? Would I better off clean start, issuing a CATALOG to CREATE then import only tables?

All of the databases being backed up with rman are 11.2.0.2 or 11.2.0.4. The catalog rman itself is the last database 10g I.

Ah, I forgot the IMPORT CATALOG command.

So...

create the rman schema owner in new catalog databsae

create the catalog in the new database

catalog import not unregister, a database at a time.

Tags: Database

Similar Questions

The most basic RMAN implementation
Version: 10 gr 2

For my test db ora652, I need to use RMAN for backup and restore. The backup location is called NFS mounting
```
/dbbackup/ora652
```
I need to use the most basic RMAN implementation. I don't want to use a repository (customer RMAN) IE. I'm going to call the utility RMAN database the ORACLE_HOME to do.

Can anyone provide me the command configure RMAN to do this?

Here are my files
```
--datafiles
/u02/oradata/ora652/system01.dbf
/u02/oradata/ora652/undotbs01.dbf
/u02/oradata/ora652/sysaux01.dbf
/u02/oradata/ora652/users01.dbf
/u02/oradata/ora652/shp_tbs01.dbf

--temp files
/u02/oradata/ora652/temp01.dbf

--redo logs
/u02/oradata/ora652/redo01.log
/u02/oradata/ora652/redo02.log
/u02/oradata/ora652/redo03.log

--control files
/u02/oradata/ora652/control01.ctl
/u02/oradata/ora652/control02.ctl
/u02/oradata/ora652/control03.ctl
```
Hello
Is your database runn ing in ARCHIVELOG mode?

the details you have given it seems that is not, and in this case, you can use RMAN to perform a backup to cold.

You can use rman to resolve some persistent settings which is your backup location

DISK of TYPE DEVICE CONFIGURED CHANNEL format ' / dbbackup/ora652/%d_DB_%u_%s_%p';

then whenever you perform a backup, it will be written to this place

a simple cold backup script
```
run{
shutdown immediate;
startup mount;
backup database;
alter database open;
}
```
concerning

Alan

RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target
Hello

RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the backup command to 2009-03-31 21:59:24
RMAN-03014: implicit recovery catalog Resync failed
RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database

I get the above error while taking backup RMAN Level0. I am able to connect to the database of the catalogue without any problem.

I already have this registry database command in RMAN prompt. Now I am able to see backup list but I don't know how that DB asking to sign up for today. Until yesterday, the backups were running fine btu today his application to enter the catalog DB.

Here we manually to connect the catalogue in this way
rman target $ /.
RMAN > catalog connection rmanuser/password @ < globalcatalogDB >
connected.

After that if I give this command means...

RMAN > backup from the list of database;
I get the error I pasted at the earliest.

Thanks in advance.
If you do not have a catalog, you need not to save the database. Rely you only on the target database controlfile. If you use a catalog, you must save the target database, but only once. If you sometimes use a catalog - and sometimes not--the appropriate command is RESYNC (although in many cases RMAN automatically done).

Werner

Catalog RMAN 11g XE

First of all, personally, I'm a novice of the oracle, more than one linux administrator myself. But I support troubleshooting of errors with backups RMAN of a database.
We are connecting to Enterprise Edition of Oracle (11.2.0.4.0) to back up the database. Our catalog of recovery is the use of Oracle 11 g Express edition (I think that the version number is specifically 11.2.0.2.0)
The backup sends a pretty normal RMAN backup script. We get the result of our newspapers:
Recovery Manager: release 11.2.0.4.0 - Production Wed Feb 26 10:17:17 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: LIVEDB (DBID = #)
connected to the recovery catalog database
PL/SQL package CATALOG. DBMS_RCVCAT 11.02.00.02 in the RCVCAT database version is not current
PL/SQL package CATALOG. DBMS_RCVMAN 11.02.00.02 in the RCVCAT database version is not current
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure to allocate command to the channel ch00 at 26/02/2014 10:17:19
RMAN-10015: error compiling program PL/SQL
RMAN-10014: PL/SQL error on line 102 12 column 0: statement ignored
RMAN-10014: PL/SQL 302 on column error line 102 24: component 'THROTTLE_ME' must be declared
Complete recovery manager.
(Note: the renowned CATALOG database and target recovery catalog name renamed to LIVEDB to keep things generic)
I'm assuming that the issue is ORACLE XE has an outdated version of the recovery catalog from the RMAN on the target database (11.2.0.4.0 vs 11.2.0.2).
So, two questions:
(1) does a version problem as I guess, or is there something else?
(2) at - it something we can do using the software oracle XE as the recovery catalog?
I have the RMAN script, if I need to publish.

So we have successfully our catalog updated 11.2.0.4 and made a backup.

The solution, which may have been easier than easy, had to use RMAN (11.2.0.4) client to connect to our catalogue (11.2.0.2). Then, run the upgrade catalog command.

Simple.

Basically

RMAN > connect username/password@CATALOG

RMAN > upgrade catalog

Obviously, CATALOG is the name of your catalog of recovery and probably should have a tnsnames.ora entry and others.

We got it to work.

clcarter, thanks for the bread crumbs - I never thought to use the updated backend catalog rman client.

Using the Scheduler to run the rman script directly stored in the recovery catalog

Hi everyone, I usually automate my backups rman, using either cron or dbms_scheduler to call my stored in a sh file NIX rman scripts. Everything works fine but anyone know how / if it is possible to call a stored in the recovery catalog rman script. Let's say I have create a script in the catalog:
RMAN > create script showall
Comment "just one example of demonstration."
{
VIEW ALL;
}
Can I use dbms_scheduler to call this script directly? If Yes, how and if not then how can we plan for this or a stored script stored in the rman catalog catalog. Been looking all over the place, but everything seems to indicate leaving Oracle to call .sh or .bat file.
Kind regards
Dave

Well, let us know the result.

The link you supplied refers to 12 c Scheduler improvements it seems, it may not be applicable to lower versions of Oracle.

Error during the registration of RMAN from the primary to the catalog database
Hi all

Here we have an environment with db1 (db_unique_name) 10g dataguard as primary and db2 (db_unique_name) Physics of the standby database. Also, we have configured a schema on a third computer as a database of catalog using following steps.

The measures taken in the catalog database (appsdb):

SQL > create tablespace rmancatlog_tbs datafile ' / u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend extent management local segment space management auto;

SQL > create user rman identified by oracle
2 default tablespace rmancatlog_tbs
3 unlimited quota on rmancatlog_tbs
4;

SQL > GRANT connect, resource, recovery_catalog_owner to rman;

RMAN > create catalog.
Recovery catalog created

AMT added entries of catalog in primary and standby database. Then the primary database, we have tried to register for the catalog database. It shows that it registers. But all queries later rman throws the error. Here are the steps and the error:

[oracle@db1 ~] $ rman target sys/oracle catalog rman/oracle@appsdb
Recovery Manager: release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: NIOS (DBID = 1589015669)
connected to the recovery catalog database

RMAN > register database;
registered in the recovery catalog database

RMAN > outline report;
Report of the database schema
List of permanent data files
===========================
Size (MB) Tablespace RB segs Datafile file name
----
-------------------- ------------------------
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of command report to the 08/10/2012 06:16:06
[RMAN-00600: internal error, arguments [8201] [] [] []]

Can anyone help on this error?
Thanks in advance.
Hello;

Then, you have to re-create the controlfile to the target database. (Not funny)

I like to use the method of trace file myself.

How to recreate a Controlfile [ID 735106.1]

Best regards

mseberg

RMAN-06004: error recovery catalog database ORACLE

Hi all

I'm new to the RMAN module, please help me solve the error below.

Recovery Manager: Release 9.2.0.6.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

connected to target database: DB96 (DBID=2450380394)
connected to recovery catalog database

RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_FULL_%T_%U.rman' MAXPIECESIZE 4 G; 
2> CONFIGURE CONTROLFILE AUTOBACKUP ON; 
3> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_ctlfile_%F'; 
4> CONFIGURE RETENTION POLICY TO REDUNDANCY 1; 
5> shutdown immediate; 
6> startup mount; 
7> backup database; 
8> CROSSCHECK BACKUP; 
9> DELETE NOPROMPT OBSOLETE; 
10> alter database open; 
11> list backup summary; 
12> exit;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 06/20/2011 11:31:55
RMAN-06004: ORACLE error from recovery catalog database:
 
RMAN-20001: target database not found in recovery catalog
Recovery Manager complete.

Please do the neeful.

Kind regards
Jame

Jame,

connect to retrieve catalog owner user (RMAN) using SQLPLUS on the catalog database and run the following query.

SQL> select * from rc_database;

Another thing is, check, if your catalog is accidentally created in the target database or you sure sound in a separate database (possibly on a separate server).

Thank you
RANA

Published by: RANA June 20, 2011 17:08

Published by: RANA June 20, 2011 17:41

RMAN catalog 11 GR 2 Update Catalog RMAN-06429
Hi all

I have databases oracle 11 GR 1 material and GR 11, 2 in use.
Last time I would upgrade the catalog with 'Upgrade catalog' database to backup databases the new 11 GR 2.

The upgrade looks good, but after this task, I have 21 invalid objects in the RMAN catalog and it was not possible to compile without error. And all the other which backups using the catalog fails the RMAN-06429.
-> Package PL/SQL BAKRMAN. DBMS_RCVCAT Version 11.02.00.02 in the RCVCAT too recent database.
I therefore return to the action.

What is the right way to use the catalog rman with levels of different database?
How can I use the catalog also for 11 GR 2 databases without any side effect on my other 11 GR 1 material databases?
The rman catalog reside on a 11.1.0.7.0 database.

BR
Daniel

http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/compat003.htm
Database TARGET RMAN-06429 is not Compatible with this Version of RMAN [245698.1 ID]
Hello

So, how I understand, I should send the command "upgrade catalog" new 11 GR 2 database server.

Yes, the process of looking at this.

Opening of session of rman 11 GR 2 binary upgrade CLI:

$ rman catalog bakrman /@.

connected to the recovery catalog database
RMAN PL/SQL package. Version X.X.X.X in database RCVCAT DBMS_RCVCAT is too old

RMAN > upgrade catalog;

recovery catalog owner is BAKRMAN
Enter the command of CATALOG to UPGRADE again to confirm the upgrade of the catalogue

RMAN > upgrade catalog;

Upgraded to version X.X.X.X recovery catalog
DBMS_RCVMAN package updated to version X.X.X.X
DBMS_RCVCAT package updated to version X.X.X.X

After that this upgrade, only objects of schema in the recovery catalog database should be improved, right?

Fix.

Kind regards
Tycho

Edited by: tychos January 25, 2011 14:40

RMAN-20001: target not found in the recovery catalog database
I'm practicing the loss of all control files. I have backups of catalog rman configured for controlfile autobackup. So far, I did this.

RMAN > startup nomount;
Oracle instance started

Total System Global Area 209715200 bytes

Bytes of size 1272864 fixed
155190240 variable size bytes
Buffers 50331648 database bytes
Redo buffers 2920448 bytes

RMAN > restore controlfile autobackup.

From restoration to SEPT. 08.-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 156 devtype = DISK

field of recovery destination: / u02/flash_recovery
name of database (or unique name of database) used for research: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: restore full automatic backup of control file
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Restoration finished in 08-SEVEN.-10

RMAN > change the editing of the database;

mounted database
output channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure to modify the order db at 08/09/2010 14:54:50
RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database

I guess it has something to do with the DBID but... I don't have and I do not know how to find.
Hello
Try this
RMAN > Connect target /.
RMAN > Connect catalog rman/rman@test
RMAN > startup nomount;
RMAN > list backup of controlfile;

WITH THE HELP OF RMAN BACKUP CATALOG
Hello...

I INTEND TO TAKE THE "ORCL" DATABASE BACKUP USING THE CATALOGUE. FIRST, I CREATED A DATABASE USING DBCA NAMED "RMAN". NOW, IN THE FLASH RECOVERY AREA, I'LL HAVE TWO FOLDERS "ORCL" AND "RMAN".

MY QUESTION IS THAT... I HAVE USED WITH RMAN CATALOG AND TOOK THE GAME TO FULL DATABASE BACKUP AS BACKUP... BUT THE BACKUP SET WAS PLACED IN

E:\oracle\product\10.2.0\flash_recovery_area\ORCL\BACKUPSET\2009_07_29\O1_MF_NNNDF_FULLBACKUP_5703B10H_. BKP

I WANT TO KNOW WHEN I USE CATALOG RMAN DATABASE AS WHY IT IS IMPLEMENTED BACKUP ORCL...?
SO WHAT'S THE CHANCE OF CREATING A SEPARATE DATABASE "RMAN". ?
SEPARATE RMAN DATABSE IS JUST FOR CREAT CATALOG, THEN THE REGISTRY ORCL IN THIS CATALOG DATABASE?

THANKS FOR REPLYING...

I TOOK THE BACKUP AS BELOW...

............................................... RMAN DATABASE...

C:\Documents and Settings\Vortex > set oracle_sid = rman

C:\Documents and Settings\Vortex > sqlplus / as sysdba

SQL * more: Release 10.2.0.1.0 - Production on sea 29 Jul 11:31:20 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With partitioning, OLAP and Data Mining options

SQL > create user identified by human rman
* 2 default tablespace users *.
* 3 tablespace temporary temp *.
* 4 account unlock; *
Created by the user.

SQL > grant connect, resource, recovery_catalog_owner to rman;
Grant succeeded.

SQL > change the quota of rman to unlimited user on the users;
Modified user.

SQL > exit
Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.1.0 - Production
With partitioning, OLAP and Data Mining options

C:\Documents and Settings\Vortex > rman@rman catalog rman

Recovery Manager: Release 10.2.0.1.0 - Production on sea Jul 29 11:33:08 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Catalog database recovery password:
connected to the recovery catalog database

RMAN > create catalog.
Recovery catalog created.

............................................... ORCL DATABASE...

Microsoft Windows XP [Version 5.1.2600]
Copyright (C) 1985-2001 Microsoft Corp.

C:\Documents and Settings\Vortex > set oracle_sid = orcl

C:\Documents and Settings\Vortex > rman@rman for catalog rman target /.

Recovery Manager: Release 10.2.0.1.0 - Production on sea Jul 29 11:37:10 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID = 1221198182)
Catalog database recovery password:
connected to the recovery catalog database

RMAN > register database;

registered in the recovery catalog database
from full resynchronization of the recovery catalog
full complete Resync

RMAN > show all.

RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP # by default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' E:\ORACLE\PRODUCT\10.2.0\DB10G\DATABASE\SNCFORCL. ORA'; #

RMAN > CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration settings:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration settings are stored successfully
from full resynchronization of the recovery catalog
full complete Resync

RMAN > outline report;

Report of the database schema

List of permanent data files

Size (MB) Tablespace RB segs Datafile file name

1 470 SYSTEM YES E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01. DBF
2 25 UNDOTBS1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01 YES. DBF
SYSAUX 3 230 NO E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01. DBF
4 5 USERS WITHOUT E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01. DBF

List of temporary files

File Size (MB) (MB) Maxsize Tempfile Tablespace name

1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEMP01 20 TEMP 32767. DBF

RMAN > run
* 2 > {allocate channel ch1 type disk; *}
* 3 > backup database tag = BACKUP; *
* 4 > release channel ch1. *
{* 5 >} *.

allocated channel: ch1
channel ch1: sid = 148 devtype = DISK

From backup 29 July 09
channel ch1: starting full datafile backupset
channel ch1: specifying datafile (s) in backupset
input datafile fno = 00001 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01. DBF
input datafile fno = 00003 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01. DBF
input datafile fno = name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01 00002. DBF
input datafile fno = 00004 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01. DBF
channel ch1: starting piece 1 to 29 July 09
channel ch1: finished piece 1 to 29 July 09
room handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_07_29\O1_MF_NNNDF_FULLBACKUP_570
3B10H_. Tag BKP = BACKUP comment = NONE
channel ch1: complete set of backups, time: 00:01:38
Backup finished in 29 July 09

From control file and SPFILE Autobackup 29 July 09
room handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2009_07_29\O1_MF_S_693489105_5703F5L
K_. Comment BKP = NONE
File control finished and Autobackup SPFILE to 29 July 09
output channel: ch1.

RMAN >

Published by: Muhammad.Usman on July 28, 2009 23:01
You can also take your backups without a recovery catalog database. The additional advantage of using a database to catalog vs using the controlfile as repository (default average) target is essentially
>
RMAN automatically manages backup metadata in the database control file is saved. To protect and maintain metadata backup for long periods of time, the RMAN Repository is created in a separate database. This repository is generally referred to as a catalog of recovery. The benefits of using a catalog of recovery include:

*

Stores long-term backup information
*

Store the metadata for multiple databases
*

Restore a backup available on another system

Another reason to use a recovery catalog is the limited size of the target database control file. If the control file is too small to contain additional metadata from backup, then the existing backup information are crushed, making it difficult to restore and recover using these backups.
>

of http://download.oracle.com/docs/cd/B19306_01/server.102/b25159/configbp.htm#CHDBCHAC

Kind regards
Uwe

http://uhesse.WordPress.com

RMAN-06004: ORACLE recovery catalog database error: ORA-03113: end - of -
Hello

I experience backup scripts. because once done, she will move to pod pre box.

Database runs in mode archvelog
I have lgged in the dbserver himself.

the shell scripts is:
#! / usr/bin/sh
source. / game - env # this file will have ID password for catalogue and the target sources
echo executing command: database Backup
ECHO
RMAN TARGET $dbuser / $dbpwd$ rmandb CATALOG $rmanuser/$rmanpwd@$rmandb < < eof
Run {}
stop immediately;
start-up;
}
expressions of folklore
output

When I run, I get the following error

connected to target database: HERMESQA (DBID = 3819666523)
connected to the recovery catalog database

RMAN > 2 > 3 > 4 > 5 >
database closed
dismounted database
Instance Oracle to close

connected to the database target (not started)
Oracle instance started
mounted database
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the boot command at 11/06/2009 11:27:54
RMAN-06004: the recovery catalog database ORACLE error: ORA-03113: end of file on communication channel

could you suggest where I have error.

Thank you
Benjamin Gopal
Do not back up the database using the same catalog of recovery recovery catalog of accommodation. You could just try it back up without a recovery catalog and to ensure that this database has an automatic backup of controlfile, for example.

RMAN - Catalog and ControlFile Recovery
I recorded rock database (same host) and Fatima databases (in another machine) in the RECOVERY CATALOG.

I m sticking with Faure database backup using the recovery catalog

RMAN >

Complete recovery manager.
^ C
H:\ > rman target sys/farooq@farooq catalog rman2/cat@rock

Recovery Manager: Release 10.2.0.1.0 - Production on Mon Sep 8 14:41:17 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: FAURE (DBID = 1820635189)
connected to the recovery catalog database

RMAN > register database;

RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of the register command to the default channel on 2008-09-08 14:41:37
RMAN-20002: target database is already registered in the recovery catalog

RMAN > outline report;

Report of the database schema

List of permanent data files
===========================
Size (MB) Tablespace RB segs Datafile file name
---- -------- -------------------- ------- ------------------------
1 YES D:\ORADATA\FAROOQ\SYSTEM01 480 SYSTEM. DBF
2 35 UNDOTBS1 D:\ORADATA\FAROOQ\UNDOTBS01 YES. DBF
SYSAUX 3 250 NO D:\ORADATA\FAROOQ\SYSAUX01. DBF
4 5 USERS WITHOUT D:\ORADATA\FAROOQ\USERS01. DBF
5 100 EXAMPLE NO D:\ORADATA\FAROOQ\EXAMPLE01. DBF

RMAN > list backup;

RMAN > backup as incremental compressed backupset of level 0 database more archivelog;

From backup 08-SEP-08
Current archived log
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of command thus backup archivelog at 2008-09-08 14:43:03
RMAN-03014: implicit recovery catalog Resync failed
RMAN-06004: error ORACLE recovery catalog database: RMAN-20020: incarnation of the database not defined

RMAN > list incarnation of database;

List of Incarnations of the database
DB key Inc key STATE ID DB name DB reset reset time SNA
------- ------- -------- ---------------- --- ---------- ----------
3641 3649 FAURE 1820635189 PARENT 534907 29 JULY 08
FAURE 3641 3642 1820635189 CURRENT 695424 08-SEP-08

RMAN > RESET DATABASE to incarnation 3642
2 >.

database restore the incarnation 3642

RMAN > backup as incremental compressed backupset of level 0 database more archivelog;

From backup 08-SEP-08
Current archived log
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 142 devtype = DISK
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 1 recid = 4 = 664886867 stamp =
archive log entry thread = 1 sequence 2 recid = 5 = 664888152 stamp =
archive log entry thread = 1 sequence = recid 3 = 6 = 664888938 stamp
archive log entry thread = 1 sequence 4 recid = 7 = 664889572 stamp =
archive log entry thread = 1 sequence 5 recid = 8 = 664889658 stamp =
archive log entry thread = 1 sequence 6 recid = 9 = 664891871 stamp =
archive log entry thread = 1 sequence 7 recid = 10 = 664892590 stamp =
archive log entry thread = 1 sequence 8 recid = 11 = 664900983 stamp =
archive log entry thread = 1 sequence 9 recid = 12 = 664902190 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y35PK_. Tag BKP = comment TAG20080908T150314 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:26
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 8 recid = 1 stamp = 664886398 =
archive log entry thread = 1 sequence 9 recid = 2 = 664886399 stamp =
archive log entry thread = 1 sequence 10 recid = 3 = 664886403 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y407K_. Tag BKP = comment TAG20080908T150314 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:09
Backup finished 08-SEP-08

From backup 08-SEP-08
using channel ORA_DISK_1
channel ORA_DISK_1: additional start-up compressed 0 datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
input datafile fno = 00001 name = D:\ORADATA\FAROOQ\SYSTEM01. DBF
input datafile fno = 00003 name = D:\ORADATA\FAROOQ\SYSAUX01. DBF
input datafile fno = 00005 name = D:\ORADATA\FAROOQ\EXAMPLE01. DBF
input datafile fno = name 00002 = D:\ORADATA\FAROOQ\UNDOTBS01. DBF
input datafile fno = 00004 name = D:\ORADATA\FAROOQ\USERS01. DBF
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_NNND0_TAG20080908T150351_4D9Y49WW_. Tag BKP = comment TAG20080908T150351 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:01:15
Backup finished 08-SEP-08

From backup 08-SEP-08
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 10 recid = 13 = 664902308 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150512_4D9Y6T1D_. Tag BKP = comment TAG20080908T150512 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup finished 08-SEP-08

From control file and SPFILE Autobackup 08-SEP-08
piece handle = D:\ORACLE\RMAN_BACKUP\CTL_SP_BAK_C-1820635189-20080908-09 comment = NONE
Control finished and Autobackup SPFILE file 08-SEP-08

RMAN > list backup;

Backup list
===============
S LV TY Device Type delay #Pieces compressed #Copies Tag key
------- -- -- - ----------- --------------- ------- ------- ---------- ---
4615 DISC 08-SEP-08 1 1 YES TAG20080908T150314
4617 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
4650 DISC 08-SEP-08 1 1 YES TAG20080908T150512
4670 HAS NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517

RMAN >

Now, I m conneting to Faure - target database and obtaining the same information from the control file backup.

H:\ > rman target sys/farooq@farooq

Recovery Manager: Release 10.2.0.1.0 - Production on Mon 8 Sep 15:05:38 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: FAURE (DBID = 1820635189)

RMAN > LIST BACKUP SUMMARY;

using the control file of the target instead of recovery catalog database

Backup list
===============
S LV TY Device Type delay #Pieces compressed #Copies Tag key
------- -- -- - ----------- --------------- ------- ------- ---------- ---
21. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
22. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
23 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
24. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150512
25 A NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517

My question: why are the information stored in the database control file (Faure) target so that its stored in the recovery catalog?
Hello

By default, RMAN stored metadata in the file control, all the RMAN is first written to control the file and then catalog of recovery if leaves. For example, when rman creates a new backupset, you can view the information in the v$ backup_set and you can also view the same information of the recovery RC_BAKCUP_SET catalog views.
So every change repository is stored in two places... Control file and optionally recovery_catalog

The catalog of recovery of the RMAN Repository versions are stored in database tables and version control repository os file stored as files in with in the control file.

-Pavan Kumar N

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

---------- ---------- ---------- ----------

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

---------- ------- ------- ------------------------------ --- ----------

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

Need help with Ora-00001: constraint Unique voilated in catalog synchronization

Hi Experts...
Has got some problem in the catalog... desperately need help...
Oracle: 11 GR 2
Here is a detail of the error.
from full resynchronization of the recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of command resync to the default channel on 26/11/2013 18:01:34
ORA-01403: no data found
ORA-00001: unique constraint (DNKF_GRIP. BRL_U1) violated
========================++++++++++++++++=========================
Kind regards

Hei,

Cool... I have also encountered this kind of error long back... Follow and fortunately we it will be solved.

A problem with the constraint or the Index after the upgrade of the catalogue in 11 GR 2

Remove the constraint, if available, otherwise check index, if found the drop... Rest is history...

First, check the BRL_U1... It can be constrained or an index on the catalog database.

May be it's problem... the compulsion was abandoned during the catalog migration process, but the corresponding index has not been abandoned.

The catalog DB:

-Removal of the index

SQL > connect rman.

SQL > select * from user_constraints where constraint_name = "BRL_U1";

SQL > select * from user_indexes where index_name = "BRL_U1";

SQL > drop index BRL_U1;

Once it will be deposited now connect to the production database to connect to the catalog and re-synchronize... It should work like that...

RMAN target / catalog rman/password@catalog_db_name

RMAN > catalog resync;

from full resynchronization of the recovery catalog

full complete Resync

RMAN > exit

======================================

Kind regards

Firdous Shah

How to make a backup of the database with RMAN Oracle Single Instance

People,
Hello. I use the server of Oracle 11 GR 1 material with operating system Oracle Linux 5.10 database.
I understand how to back up the database instance in SQL Server with Windows. But do not really understand how to back up the database instance in Oracle on Linux.
I did it cold and hot backup for the database HRCS90 instance, but both receive the same error message.

Cold backup is below:
SQL > startup
ORACLE instance started.
Total System Global Area 538677248 bytes
Bytes of size 2146024 fixed
528482584 variable size bytes
4194304 buffers of data bytes
Redo buffers 3854336 bytes
Mounted database.
Open database.

SQL > shutdown immediate
The database is closed.
The database is dismounted.
ORACLE instance stops.

RMAN > backup database;
From backup 25 November 13
using the control file of the target instead of recovery catalog database
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the backup command to the 25/11/2013 14:26:52
RMAN-06171: not connected to the target database

RMAN > backup HRCS90
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-00558: error occurred during parsing of order entry
RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, as, backup backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, basic data, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, strength, file, incremental, keep, (, maxsetsize nochecksum, noexclude, nokeep, not, proxy, pool, re-use, recovery, section, skip). ', spfile, skip readonly, setsize, tablespace, tag to validate.
RMAN-01008: the identifier of the AfDB was: HRCS90
RMAN-01007: line 1 column 8 file: entry standard

RMAN > backup database HRCS90
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-00558: error occurred during parsing of order entry
RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, backupset channel, copy, controlfilecopy, backup, common, base data, data file, datafilecopy, remove, diskratio, db_recovery_file_dest, filesperset, format, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, more reuse, recovery, section, skip, spfile, pass readonly, setsize, tablespace, tag, to).
RMAN-01008: the identifier of the AfDB was: HRCS90
RMAN-01007: line 1 column 17 file: entry standard
While the instance of database HRCS90 is starting, I do hot backup by using the same commands and get the same error message with above cold backup.
My question is:
Can any folk tell me specific steps (order by order) to back up a single instance of the database in Oracle with RMAN?

Thank you.

Yes, you can restore and recover the backup, but not at the moment. You will only be able to restore and recover at the time of your backup.

For example.

If you take backup (mount point with no mode of journal archive) at 06:00 and your grave database crashes at 21:00, you will be able to restore and recover until 06:00. You will find all the changes made to the database between 06:00 and 21:00.

If you want your database to recover until 9 PM or until a point in time, then you must put your database in log mode archive, and then save the archives.

migrate catalog basic rman 10.2 11.2

Similar Questions

Maybe you are looking for