RMAN and database incarnations

In experimenting with RMAN, I got our team into a situation where a test database would not restore and recover. I performed an incomplete recovery, opened resetlogs, and without performing a backup, did the same thing again.
In any case, we started reading up on how to return to a previous database incarnation. We're not using a Recovery Catalog w RMAN, but 10g has been enhanced so that the control file now tracks db incarnations.
We set the db incarnation back 2 previous, and then performed:
RMAN> restore database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
RMAN> recover database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
and all seems well.
I have 2 questions:
1) Was the return back 2 incarnations really necessary? It seems like the database would've considered the 2 lines above an incomplete recovery and restore/recovered anyway.
2) Do I need to manually remove the archive logs created for incarnations 3 & 4, or will RMAN know that they are not applicaable? And how does it know they're inapplicable, if so? The incarnation?
Thanks for reading this looong question,
Chuck

Similar Messages

Unable to recover database after rman recovery and database open resetlogs

I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM

Rman restore and database size

I am testing a production database backup from tape.
Our test machine does not have the same disk space as our production machine.
Right now, here is the production size info:
Allocated (GB)               137.16
Used (GB)                    60.71
Allocated Free Space (GB)     76.45
Is there a way to restore with rman and restore only the actual size of the database?
In my case 61gig instead of 140G.

Then i am confuse. I had this other problem where i had a big aud$ table in my system tablesace. I have truncated the table, now i need my 20gig space back.
auditing
The solution proposed was to do a backup and restore using RMAN after truncating AUD$:
http://www.dizwell.com/prod/node/613
I did not tried it yet. But after reading this, i though i could be able to restore a rman backup that takes less space.

Rman and duplicate database.

Hi,
I have some problems with rman and duplicate a database.
Im trying to duplicate a database on a anoter server than the target, and I have run the command SQL>startup force nomount, on the auxiliary system.
But I don't know what commands to use i rman.
Have backup-files on disk at the same server as the auxiliary system is on.
Any tips and tricks?!
Thanks in advanced,
Micke.

I had the same question a while ago. The location of the files you'll need to restore from are specified in the controlfile. The location referenced in the controlfile will be the location where they were put but RMAN on your "source" server. So for instance, if RMAN drops the backup set in /opt/oracle/dbs/tmp, then your controlfile will point to /opt/oracle/dbs/tmp. (yours probably won't be here, it's just an example). Your controlfile WILL however have to go in the dbs directory, wherever that is.
What worked for me in the past was placing the backup files on the destination server in /home/oracle/backup_<date> and recreating the file structure based on that of the source server (even if it's just empty dirs) and symlink the last level of the tree to the folder where the files reside.
For example:
ln -s /home/oracle/backup_03272008 /opt/oracle/dbs/tmp
I think there's a more efficient way to do this, but this worked for me.

Oracle RMAN and SAP Databases

Hi all,
Am mainly an Oracle DBA and had just recently return to supporting SAP customers after a 4 year absence of supporting non-SAP customers.
Anyway, I have some question on using Oracle RMAN with SAP databases. Backup softwares are Netbackup and Data Protector.
I managed to get the backup working, that is, there is no issues, Oracle RMAN backup using SAP's brarchive and brbackup works alright. My question is about using an Oracle RMAN catalog. I've read thru several SAP documentation and cannot find one where I can use a RMAN catalog.
Reading from
http://help.sap.com/saphelp_nw04/helpdata/en/d1/43d7cab9a04a409cc46876e36762c2/content.htm
Does that mean I cannot use a RMAN catalog? Had anyone managed to use a RMAN catalog to do the RMAN backup?
*Another question I have is, do I need Netbackup and Data Protector if I want to run RMAN backup to disk via brarchive and brbackup? Does backint requires a SBT library to use RMAN? What I mean is, I want to use RMAN but doing backup to disk instead of to tape which means I don't need the tape library installed, will backint know that this is the case and will not look for the tape library?
Any advise or feedback on this will be very much appreciated. Thanks in advance.
Extracts from http://help.sap.com/saphelp_nw04/helpdata/en/d1/43d7cab9a04a409cc46876e36762c2/content.htm are as below:
The Oracle Recovery Manager (RMAN) is an Oracle backup program. You can use it as a command line interface (CLI) or as a graphical user interface (GUI) in the Oracle Enterprise Manager (OEM). We support RMAN with the SAP backup tools BRBACKUP and BRARCHIVE.
RMAN uses the System Backup to Tape (SBT) interface to back up to tape devices. We implement SBT using the SAP backup library. External backup tools can implement this interface as a dynamic link library (DLL).
Integration
By integrating RMAN into BRBACKUP, you can add security and flexibility to important functions in existing backup strategies and tools:
· The recovery catalog is not used. The backup information is stored in the control file. After the backup, the control file is also backed up. In a restore, the control file is restored first, followed by the data files.
· The integration of RMAN into BRBACKUP also guarantees integration into the SAP Structure linkComputing Center Management System (CCMS).
· BRBACKUP tape management functions as previously (that is, as when using the SAP backup library).
· You can still use the BACKINT interface with external tools.
· All previous SAP backup strategies are supported while using RMAN. Nevertheless, RMAN is not supported for standby database backups and split-mirror backups.
· The following components are delivered with the standard Oracle8 installation:
¡ RMAN with the Oracle SBT interface
¡ Backup library and backup tool Networker from Legato
¡ Legatou2019s BACKINT interface implementation (as of Oracle 8.0.5)
The SAP installation also delivers the SAP backup library with BRBACKUP and BRARCHIVE.
Edited by: newbie01.sap on Jun 11, 2010 10:50 AM

Hi,
This question has been answered by Stefan Koehler. Not sure why the thread is not updated by his response. I am hoping to give him the max points actually.
It was a very good response which is as below:
Subject: Re: Oracle RMAN and SAP Databases
Message: Hello,
> Does that mean I cannot use a RMAN catalog? Had anyone managed to use a RMAN catalog to do the RMAN backup?
Correct - if you are using the BR*Tools and RMAN you are not able to use a RMAN catalog with it.
You can do manual catalog syncs, but the BR*Tools are not supporting a catalog database.
>Does backint requires a SBT library to use RMAN?
Check this documentation (Point "RMAN Backups Without Backup Library"): http://help.sap.com/saphelp_nw04/helpdata/en/3f/9d800e1aec11d2b42c00609419997a/content.htm
> Any advise or feedback on this will be very much appreciated.
We are also using RMAN for taking backup of all our oracle database (SAP and non-SAP), but without any BR*Tools.
That is also possible - check sapnote #105047 (Part "50. Recovery Manager (RMAN)").
As you mentioned, that you are a fulltime DBA you should have enough knowledge to use RMAN without BR*Tools.
Regards
Stefan

Implementing RAC database backup through RMAN and grid control.

Hi...
plz... can any one give me good document (metalink documents id or else) to implement RAC database backup through RMAN. and also grid document...

user8943492 wrote:
Hi...
plz... can any one give me good document (metalink documents id or else) to implement RAC database backup through RMAN. and also grid document...Read below links
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/backup.htm#i443637
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/rmanops.htm#i474611
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/toc.htm

About database incarnations in catalog versus non-catalog

Hi all
Listing out the incarnations of my target database when not connected to the recovery catalog :
RMAN> list incarnation of database testdb;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       TESTDB   2539541829       PARENT 1          11-JUL-11
2       2       TESTDB   2539541829       PARENT 591584     12-JUL-11
3       3       TESTDB   2539541829       PARENT 2061948    19-JUL-11
4       4       TESTDB   2539541829       ORPHAN 1345130669 13-MAY-13
5       5       TESTDB   2539541829       CURRENT 1345130669 15-MAY-13And listing out the incarnations when connected to the catalog:
RMAN> list incarnation of database testdb;
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1178485 1178523 TESTDB   2539541829       PARENT 1          11-JUL-11
1178485 1178524 TESTDB   2539541829       PARENT 591584     12-JUL-11
1178485 1178525 TESTDB   2539541829       PARENT 2061948    19-JUL-11
1178485 1178526 TESTDB   2539541829       ORPHAN 1345130669 13-MAY-13
1178485 1178486 TESTDB   2539541829       CURRENT 1345130669 15-MAY-13Why are INC KEY numbers not matching? Is this a bug or is it expected behaviour?
Please help me shed some light on this..
Thanks.

Hi,
Manual said:
DB Key- When combined with the Inc Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key to unregister a database from a recovery catalog, that is, delete all the rows associated with that database from the recovery catalog.
INC Key- When combined with DB Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key in RESET DATABASE TO INCARNATION when recovering the database to a time before the most recent RESETLOGS.
<<http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta027.htm#CHDGGAFF>>
recovery-catalog and control file-catalog is a catalog of different, So not match.
Regards,

RMAN and Point IN time recovery

1. We have a table with bad data.
2. We know that data was entered via the GUI exactly one week ago.
3. I have an RMAN database full back-up that was taken the same day but before the table was screwed.
4. the database in archivelog mode.
5. we will be happy to restore the database in the condition before the change occured
5. when I restore database via RMAN, and do:
recover UNTIL TIME '16-MAR-2005';
Oracle restore bad data, and if I put time or scn I get a message that the database incarnation is wrong!
Is there any other way to do it?
TIA

Thanks Laurent! I was able to restore it only until Mar. 17?
1. RMAN> reset database to incarnation 2;
2. RMAN> restore database until time "timestamp '2005-03-15 00:00:00.00'";
RMAN-03002: failure of recover command at 03/29/2005 19:44:11
RMAN-06555: datafile 1 must be restored from backup created before 15-MAR-05
3. My backup was created on Mar. 16, :
RMAN> restore database until time "timestamp '2005-03-17 00:00:00.00'";
RMAN-03002: failure of restore command at 03/29/2005 19:46:55
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
4. RMAN>Restore database; OK
5. RMAN>Recover database; internal error!
RMAN-03002: failure of recover command at 03/29/2005 20:08:02
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile 'G:\ORACLE\ORA10G\FLASH_RECOVERY_DATA\ORCLSRMA\CONTROLFILE\2005_03_2
3\O1_MF_1_14_14442T9B_.ARC'
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3021], [1], [15], [2], [0], [419057]
, [0], [416789]
6. RMAN> recover database until time "timestamp '2005-03-17 00:00:00.00'"; OK
7.RMAN> recover database until time "timestamp '2005-03-17 00:00:00.00'"; OK
8. RMAN> alter database open resetlogs; OK
9. RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORCLSRMA 2671268838 PARENT 1 09-MAR-04
2 2 ORCLSRMA 2671268838 PARENT 318842 01-MAR-05
3 3 ORCLSRMA 2671268838 ORPHAN 380529 25-MAR-05
5 5 ORCLSRMA 2671268838 CURRENT 409286 29-MAR-05
4 4 ORCLSRMA 2671268838 ORPHAN 416789 25-MAR-05

Database Incarnation

Hi all
Does it matter whether after a database incarnation has been made that there are files from both incarnations around? I performed a test recovery from tape, basically all files that could be used to recover, to a test server, and performed an Oracle (full database) suggested recovery. It worked, but in the aftermath, there are archivelogs with different database incarnation number, and redo logs with differerent incarnation number. I understand that the database is essentially a 'new database' as far as creation is considered.
Thanks, David

Hi Nicolas
Yes, I was actually doing a restore from one machine to another so the incarnation was different. My confusion was about whether having files with different incarnation numbers around made a difference; logically it can't - except for maybe my suspicion. The restore was an OEM rman suggested recovery; don't think it did resetlogs. It was a total (all files) recovery.
Thanks, David

RMAN-20021: database not set

Hi All,
We have database Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production running on RedHat edition 4.
I have done incomplete recovery of database to previous incarnation using autobackup controlfile with RMAN, opened database with resetlogs everything went fine. database is up and running. Now when i tried to take backup of the database i have received following error
Starting backup at 29-APR-08
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:21:21
RMAN-20021: database not set
RMAN> set DBID=279496673
executing command: SET DBID
RMAN> backup database plus archivelog ;
Starting backup at 29-APR-08
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:22:46
RMAN-20021: database not set
RMAN> backup database;
Starting backup at 29-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/29/2008 19:23:48
RMAN-20021: database not set
RMAN-06031: could not translate database keyword
Can anyone please advice as what is reason behind this error. searched on the internet but nothing found rather than contacting oracle support
Regards
Vinay

Sorry forgot to add some information.
before recovery we were using recovery catalog which was on the same database.
while doing recovery restored controlfile by
RMAN> restore controlfile from '/oracle/oradata/envdvp/backup/controlfile/C-279496673-20080429-18';
and then performed restore and recovery operation

RMAN and RAC

Hi all,
Just a query with RMAN and backing up RAC databases.
Reading Metalink Note: 243760.1 (RMAN: RAC Backup and Recovery using RMAN) it suggests that, for a 2 node RAC cluster, 2 channels should be set up, with a connection to each instance. For example,
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node2';
On our systems though, which we inherited, the backup script has 4 channels, but all of them connecting to Instance A). For example,
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
Now, we have done backup/restoration testing and it all appears to work. I can confirm that both UNDO tablespaces are being backed up, and all archivelogs as well.
I believe the reason why all connections go to the A) node is because the backup storage is locally mounted on the A) node and accessible by the B) node over the private network.
(We use Sun Cluster to mount the backup storage globally between the nodes, with A) being the master/local access and B) having access over the network).
The question is, is there any critical reason why we should connect to each instance, or is it a best practice type thing (e.g. to share the load between nodes) ?
Thanks for you input.

Hi I am trying to register 2 instances in the recovery catalog also. What was the order of operations?
Is this sequesnce correct?
[oracle@vtl-rman ~]$ set ORACLE_SID=fprcprod1
[oracle@vtl-rman ~]$ rman target sys/password@fprcprod1 catalog rman/password@fprccat
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Sep 20 16:32:38 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: FPRCPROD (DBID=1881352426)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1179 1180 FPRCPROD 1881352426 CURRENT 1 18-SEP-07
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'sys/password@fprcprod1';
new RMAN configuration parameters:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'sys/password@fprcprod2';
new RMAN configuration parameters:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> list incarnation;

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

Simple Problems of oracle 8i using Rman and so.................

I am Shan here. I am DBA student for oracle 8i. I have a problem with a backup and recoverys article which is Rman. If you can not help for this then please tell me a contact of that person who can help me. If u can then it is on..
1- I create a user RMAN. I grant him a quota on rman and on rman_temp tablespace; grant him a dba, sysdba, recovery_catalog_owner role. Then I connect it to target. Then I create catalog, then register database then type a command of list (LIST COPY OF DATABASE and LIST BACKUP OF DATABSE) it shows me nothing. ok.
Then I take a whole backup of a database with the command
Run {
Allocate channel c1 type disk;
Backup
Format d:\backup\whole_%d_%s_%p.bak
(Database) ;}
This command shows me allocating channel and then processing backup Then this commend ended successfully. And it shows me files physically of my desire path. Then I query a command of LIST for showing me my backup details (LIST BACKUP OF DATABSE). But it shows me nothing. No details about my backup. But the file is still physically there at my given path.
This is the same story with copy command it physically create a file there but do not show it with LIST COPY OF DATABASE command.
It is not a story of a single Computer I changed it and do the same stuff with the others but the result is same. But I got desire results on one Computer but next day I got another problem with this Computer. I type a command of list backup it shows me the results. It has two backup pieces. I tried to delete them with change command by allocating channel for delete type disk. And then change backupset 605(backup set no) delete;. It shows me that he deleted that file form path but when I query of list backup it show me the same results which it show me before delete. Then I tried to delete second set which is still there I would not allow me to delete that set and give a error that catalog does not have the information about that file but list command show me both pieces. I do manual resync catalog command but no difference on results.
Then I take another whole backup at another place, and query to get its information but list command does not show the results. It shows me the old results. Then I take a backup of a single data file and query but the result is same.
I also tried to delete that copy data file by change command but it says that recovery catalog do not have the information about that file.
2- If we allocate more then one channels for backup on a same drive what will be the behavior of those channels.
Will them not working parallel. And tell me that it is true that channels will work parallel when they are writhing information on different drives (different drive means that two different hard drives physically).
Syntax of all commands is writen,I tallied it by book.<<<<<<<<<<<<<<<<3- What is O stands for in crosscheck command? A stands for available U Stands for Unavailable and O Stands for? In a status column.
4- Please tell me a single command to delete all tables of a user. (Single command..)
We are using ORACLE 8i (8.1.7.0.0) Version for practice.
Give its solution by mail
[email protected]

I have briefly used sql*ldr in linux and yes, it does support exit codes

RMAN Active Database error

Hello Team,
I was doing ACTIVE DATABASE CLONING WHEN I NOTICED THIS ERROR:-
released channel: t15
released channel: t16
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/10/2012 18:50:41
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/dupp3db/arch/dup3_1_145_794494895.arc'
ORA-10877: error signaled in parallel recovery slave
I went through a notr in metalink ( ID 1098638.1), but didn't able to resolve it not able to undetstand. Please suggest

rman> list incarnation;
rman> RESET DATABASE TO INCARNATION <x>;
*X is the correct incarnation

RMAN-05520: database name mismatch, auxiliary instance has ORADB

Hi,
i am using Oracle 10g (10.2.0.1.0) in RHEL 5 server. i am trying to duplicate my primary database(ORADB) to standby database with name DEVDB in different server. I have taken an RMAN backup and transferred to standby server and now i am trying to duplicate with the below commands
[oracle@rhel5 data]$ rman target / auxiliary sys/oracle@DEVDB
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Mar 9 16:11:52 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORADB (DBID=2542358497, not open)
connected to auxiliary database: ORADB (not mounted)
RMAN>
RMAN>
RMAN> duplicate target database to DEVDB
2> ;
Starting Duplicate Db at 09-MAR-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=151 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/09/2013 16:14:02
RMAN-05520: database name mismatch, auxiliary instance has ORADB, command specified DEVDB
My primary db pfile has
*.db_name='ORADB'
*.db_unique_name='ORADB'
My standby db has
*.db_name='ORADB'
*.db_unique_name='DEVDB'
Regards,
007

Hello again;
Agreed. You have at least two issues.
Generally I change the SID
export ORACLE_SID=DEVDB
Then I start NOMOUNT using an INIT file.
Then this should be correct
connected to target database: ORADB (DBID=2542358497, not open)
connected to auxiliary database: ORADB (not mounted)h2. Later
I think I was wrong I would like to change my answer. I looked back and found my old notes and things are not as I stated above.
I used an INIT file ( standby side ) for cloning as follows :
db_name=RECOVER2
instance_name=RECOVER2
control_files=("/u01/app/oracle/oradata/RECOVER2/control01.ctl", "/u01/app/oracle/flash_recovery_area/RECOVER2/control02.ctl")
db_recovery_file_dest=/u01/app/oracle/flash_recovery_area
db_recovery_file_dest_size=4070572032
compatible=11.2.0.0.0
core_dump_dest='/u01/app/oracle/diag/rdbms/recover2/RECOVER2/cdump'
db_block_size=8192
audit_file_dest=/u01/app/oracle/admin/RECOVER2/adump
undo_tablespace=UNDOTBS1
undo_management = AUTO
undo_retention=10800So for the duplicate I don't set DB_UNIQUE_NAME
I Backed up the target database as shown here with the ‘backup current controlfile for standby format’ command:
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/RECOVER2/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/RECOVER2/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/RECOVER2/sb_t%t_s%s_p%p';
release channel d1;
}I did a startup the standby as follows : ( Notice you are correct about the SID and I was incorrect )
export ORACLE_SID=RECOVER2
/home/oracle:SRECOVER2 >sysplus "/ as sysdba"
Connected to an idle instance.
SQL> startup nomount pfile='/u01/app/oracle/admin/RECOVER2/pfile/initRECOVER2.ora';I started RMAN like this :
/home/oracle:SRECOVER2 >export ORACLE_SID=RECOVER2
rman target sys/password@recover2 auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Sep 10 13:35:29 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECOVER2 (not mounted)So you connect to the Primary, but the auxiliary should show "not mounted"
Finally I issue the duplicate command
RMAN> run {
2> allocate channel C1 device type disk;
3> allocate auxiliary channel C2 device type disk;
4> duplicate target database for standby nofilenamecheck;
5> }Best Regards
mseberg
Edited by: mseberg on Mar 9, 2013 10:39 AM

RMAN and database incarnations

Similar Messages

Maybe you are looking for