RMAN INCARNATIONS
HI,
in RMAN ( 8i) restore log I have this erroe :
RMAN> run
2> {
3> set until time "TO_DATE( '26/04/2007 13:00:00', 'MM/DD/YYYY
4> HH24:MI:SS' )";
8> }
RMAN-03002: failure during compilation of command
RMAN-03013: command type: set
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog
How should I do to find available incarnations with DATE TIME ?
Many thanks.
The goal it is marked for your backup is going far beyond of the available backups. Was this database cloned? On the other hand there is no backup available to meet the criteria you have set at the beginning.
Post the output of the command:
LIST INCARNATION OF DATABASE;
and
LIST BACKUP;
Similar Messages
-
hi,
can somebody tell me the exact meaning of this command, why it needed, & what to do with the information it displayed
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 8 ORCL 1220490334 PARENT 1 30-AUG-05
1 2 ORCL 1220490334 CURRENT 534907 20-JUL-09
help me
thanks.hi!
What is incarnation and when do we need ?
when ever you perform incomplete recovery.Like you have "Flashback database" to some scn in past or you performed "Point in time recovery" so you have to open your database with Resetlog option .by doing this the
database will go into NEW INCARNATION ..it means that your database is re-born..
your online redolog will be archived and
log sequence number will be reset to 1
The important thing to note here is that your database have gone into a new incarnation so the archives have become useless because they were belonging to previous incarnation.so after opening your database with resetlog you should immediately take a full database backup.
http://www.mcs.csueastbay.edu/support/oracle/doc/10.2/backup.102/b14192/flashptr006.htm#CIHHDCCD
See Description of "Figure 7-1 Database Incarnation History With Multiple Resetlogs"
just refer to this figure and i hope that you will understand incarnation? -
Relationship between current incarnation & Backups/ RMAN-20011
Hi
I have
the following situation in RMAN:
Incarnations:
>
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 CURRENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 ORPHAN 997986 02-MAR-11
>
Backups:
>
RMAN> list backup;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
176 56.57M DISK 00:00:42 02-MAR-11
BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
List of Archived Logs in backup set 176
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 977121 02-MAR-11 988286 02-MAR-11
1 3 988286 02-MAR-11 994189 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of Datafiles in backup set 187
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
201 4.48M DISK 00:00:01 02-MAR-11
BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
List of Archived Logs in backup set 201
Thrd Seq Low SCN Low Time Next SCN Next Time
1 4 994189 02-MAR-11 996336 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
214 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
244 757.50K DISK 00:00:01 02-MAR-11
BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
List of Archived Logs in backup set 244
Thrd Seq Low SCN Low Time Next SCN Next Time
1 5 996336 02-MAR-11 997210 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of Datafiles in backup set 261
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
279 742.00K DISK 00:00:01 02-MAR-11
BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
List of Archived Logs in backup set 279
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 997210 02-MAR-11 997953 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
297 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
*342 438.00K DISK 00:00:00 02-MAR-11*
BP Key: 345 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104935
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
List of Archived Logs in backup set 342
Thrd Seq Low SCN Low Time Next SCN Next Time
*1 7 997953 02-MAR-11 998260 02-MAR-11*
BS Key Type LV Size Device Type Elapsed Time Completion Time
*364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11*
BP Key: 366 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104937
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of Datafiles in backup set 364
File LV Type Ckp SCN Ckp Time Name
*1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf*
*2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf*
*3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf*
*4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf*
BS Key Size Device Type Elapsed Time Completion Time
*387 7.58M DISK 00:00:02 02-MAR-11*
BP Key: 392 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110421
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
List of Archived Logs in backup set 387
Thrd Seq Low SCN Low Time Next SCN Next Time
*1 8 998260 02-MAR-11 1000465 02-MAR-11*
BS Key Type LV Size Device Type Elapsed Time Completion Time
*410 Full 9.36M DISK 00:00:10 02-MAR-11*
BP Key: 412 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110425
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 1000507 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
483 Full 9.36M DISK 00:00:05 02-MAR-11
BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
571 Full 9.36M DISK 00:00:04 02-MAR-11
BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
667 Full 9.36M DISK 00:00:18 04-MAR-11
BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE Included: Modification time: 04-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
RMAN>
>
I want rebuild the Database with the Backup (bold text).
And I get the error after executed the following script:
>
RMAN> RUN
2> {
3> # STARTUP NOMOUNT;
4> # RESTORE SPFILE TO '/u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' from TAG "TAG20110302T063849";
5> # SHUTDOWN IMMEDIATE;
6> STARTUP NOMOUNT;
7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
8> STARTUP MOUNT;
9> SET UNTIL SCN 1000507;
10> RESTORE DATABASE;
11> RECOVER DATABASE;
12> ALTER DATABASE OPEN RESETLOGS;
13> }
database is already started
Starting restore at 04-MAR-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag=TAG20110302T110425
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
output file name=/CDATA/TESTDB/control01.ctl
output file name=/CFLASH/TESTDB/control02.ctl
Finished restore at 04-MAR-11
database is already started
database mounted
released channel: ORA_DISK_1
executing command: SET until clause
Starting restore at 04-MAR-11
Starting implicit crosscheck backup at 04-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=136 device type=DISK
Crosschecked 11 objects
Finished implicit crosscheck backup at 04-MAR-11
Starting implicit crosscheck copy at 04-MAR-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 04-MAR-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /CFLASH/TESTDB/archivelog/2011_03_04/o1_mf_1_1_6q1k25xs_.arc
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /CDATA/TESTDB/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /CDATA/TESTDB/users01.dbf
channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag=TAG20110302T104937
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:13:45
Finished restore at 04-MAR-11
Starting recover at 04-MAR-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/04/2011 13:47:17
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog
>
How can I know the right incarnation to reset current?
Please , help
reagards
hqr200475
Edited by: hqt200475 on 04.03.2011 06:19Hi Werner,
I tried some experiments to find out the Relationship between current incarnations & Backups !
Here is a listing 2 hours before with the incarnation 460:
>
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
RMAN> list backup;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
176 56.57M DISK 00:00:42 02-MAR-11
BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
List of Archived Logs in backup set 176
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 977121 02-MAR-11 988286 02-MAR-11
1 3 988286 02-MAR-11 994189 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of Datafiles in backup set 187
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
201 4.48M DISK 00:00:01 02-MAR-11
BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
List of Archived Logs in backup set 201
Thrd Seq Low SCN Low Time Next SCN Next Time
1 4 994189 02-MAR-11 996336 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
214 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
244 757.50K DISK 00:00:01 02-MAR-11
BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
List of Archived Logs in backup set 244
Thrd Seq Low SCN Low Time Next SCN Next Time
1 5 996336 02-MAR-11 997210 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of Datafiles in backup set 261
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
279 742.00K DISK 00:00:01 02-MAR-11
BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
List of Archived Logs in backup set 279
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 997210 02-MAR-11 997953 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
297 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
342 438.00K DISK 00:00:00 02-MAR-11
BP Key: 345 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104935
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
List of Archived Logs in backup set 342
Thrd Seq Low SCN Low Time Next SCN Next Time
1 7 997953 02-MAR-11 998260 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11
BP Key: 366 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104937
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of Datafiles in backup set 364
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf
2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf
BS Key Size Device Type Elapsed Time Completion Time
387 7.58M DISK 00:00:02 02-MAR-11
BP Key: 392 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110421
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
List of Archived Logs in backup set 387
Thrd Seq Low SCN Low Time Next SCN Next Time
1 8 998260 02-MAR-11 1000465 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
410 Full 9.36M DISK 00:00:10 02-MAR-11
BP Key: 412 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110425
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 1000507 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
483 Full 9.36M DISK 00:00:05 02-MAR-11
BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
571 Full 9.36M DISK 00:00:04 02-MAR-11
BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE Included: Modification time: 02-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
667 Full 9.36M DISK 00:00:18 04-MAR-11
BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE Included: Modification time: 04-MAR-11
SPFILE db_unique_name: TESTDB
Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
RMAN> @TESTDB_rr.rman
RMAN> RUN
2> {
3> # STARTUP NOMOUNT;
4> # RESTORE SPFILE TO '/u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' from TAG "TAG20110302T063849";
5> # SHUTDOWN IMMEDIATE;
6> STARTUP NOMOUNT;
7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
8> STARTUP MOUNT;
9> SET UNTIL SCN 1000507;
10> RESTORE DATABASE;
11> RECOVER DATABASE;
12> ALTER DATABASE OPEN RESETLOGS;
13> }
database is already started
Starting restore at 04-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=12 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/04/2011 13:29:58
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN> **end-of-file**
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
>
regards
hqt200475 -
Oracle 9i RMAN list incarnation query empty?
Hello,
We have switched to a standby DB and now trying to backup that particular db on the same catalog database...
When we do a list incarnation on the standby DB the list is empty , why is that ?
RMAN> list incarnation;
RMAN>
Any ideas , thx
now we are getting this message ...
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch1 channel at 12/07/2009 21:38:25
ORA-03113: end-of-file on communication channel
Edited by: jrmtl on Dec 7, 2009 7:08 PMWhen we try to register the database it says already registered?!?
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 12/07/2009
7
RMAN-20002: target database already registered in recovery catalog -
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,
ChuckIn 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 -
What is Database Incarnations in rman ?
hi all
What is incarnation in rman , what is the use of it.....
tell me in simple words, i googled it i did not get exactly what it means...
Regards,
Vamsi,'Incarnation' literally means 'became flesh'. So 'was born'. And there is nothing before birth.
You can also compare it with crossing a wooden bridge over a ravine (what you always see in cartoons like 'Speedy Gonzales'), after you have crossed, the bridge collapses, and there is no way back. That is incarnation too.
During alter database open resetlogs, the logsequence of the database is reset, this is an incarnation (act of birth) and without RMAN there is no way of going back to a previous incarnation.
You will have an incarnation when the database is created and every time you use resetlogs. RMAN allows you to reset the database to a 'previous incarnation'.
Sybrand Bakker
Senior Oracle DBA -
Oracle 9i rman list incarnation command empty
Hello,
We have switched to a standby DB and now trying to backup that particular db on the same catalog database...
When we do a list incarnation on the standby DB the list is empty , why is that ?
RMAN> list incarnation;
RMAN>
Any ideas , thx
sorry for the double post in wrong section
now we are getting this message ...
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch1 channel at 12/07/2009 21:38:25
ORA-03113: end-of-file on communication channel
Edited by: jrmtl on Dec 7, 2009 7:02 PMHi,
Can you try:
select * from V$DATABASE_INCARNATION;in sqlplus and post the output?
The ORA 3113 can have a lot of reasons for example instable network or no resources on the server.
Regards
Tycho -
RMAN - returning to prior incarnations
I was practicing backups with my colleagues, and we shut down the database twice, reopening it both times with 'resetlogs', without backing it up in between. The database lacked the archivelog it needed for recovery the last time, so we read the docs and prepared to return to a previous incarnation.
We returned to 3 incarnations prior and restored/recovered using:
RMAN> restore database "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
RMAN> recover database "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
I have two questions:
1) What did returning to the prior incarnation gain for us? Seems like I could've just issued the restore/recover commands and performed an incomplete recovery.
2) Do I need to remove the archive logs from the 2 later incarnations, or is RMAN smart enough to know that they don't apply?
Thanks,
Chuckckd38 wrote:
I bought my Samsung Continuum the day after Thanksgiving of last year, November 26. Originally, I intended to sell the Continuum and purchase the iPhone at retail price. However, just tonight, I stumbled upon Verizon's return page that said they were extending the 30 day return policy to phones that were purchased from November 27th on. The last day to do this is tomorrow. The problem is I bought my phone exactly ONE day before this cutoff date. Tomorrow, I plan on going to the store to see if they will make an exception and let me return it. Then, my plan now is to activate my old phone (Samsung Rogue) until the iPhone would arrive in February and get it for $199 instead of $599.
How flexible is Verizon with these kinds of things? And do you think this will work? I will be begging the store manager tomorrow to see if they wil take it back as I wont have to pay retail and just pay the subsidized price for the iPhone. It would really stink if that one day will cost me.
Any thoughts?
Also, one other question. If the "Smartphones Talk Free Promotion" happens to still be in effect for the iPhone, would I be eligible still? (I am a secondary line and the Continuum was my first smartphone). I am not sure as technically, the iPhone would be my 2nd smartphone once I return my current one (hopefully),
Thanks!
I hate to be the harbinger of bad news, but you are probably going to be burdened with the Continuum because of that one day. The store may help if you are really nice, but it is unlikely. Work the charm and charisma, though. It is the least that you could do. -
Deleting old incarnation through RMAN
Hi All,
Could you please let me know how to delete old incranation and the backups related to that incarnation from RMAN for a particular database in Oracle 9i.
Regards
Harpreet SinghHi,
Thanks all for your help. I have achieved what I was looking for. I have deleted all the backups from the recovery catalog, according to you retention policy and also removed the unwanted incarnations from the recovery catalog. This is what I did:-
crosscheck backup of database completed before 'sysdate - 35';
crosscheck backup of archivelog all completed before 'sysdate -35';
report obsolete recovery window of 35 days device type 'sbt';
delete force noprompt obsolete recovery window of 35 days device type 'sbt';
delete backup of database completed before 'sysdate-35';
delete backup of archivelog all completed before 'sysdate-35';
And then to remove the incarnations from the RMAN by logging in the RMAN database with the onwer of the recovery catalog:-
RMAN> Delete from dbinc where dbinc_key=< dbinc_key>;
MAY BE THIS CAN HELP SOMEONE IN THE FUTURE!!!!!!!!!!!!!!!!!!!!!!!
Regards
Harpreet Singh -
Unable to open 11g R2 database now after trying an RMAN restore
Hi my database is not opening now.
What I was trying was to restore the database on my new server from latest database taken from my old live server and applying it on my new 11g DB (new server-database already created)
old server-11.1.0.7.0-windows 2003 server 32 bit
new server-11.2.0.3.0-windows 2008 64 bit server
The steps i have done which caused this , (After everything was working fine, i did these foll.steps and now all messed up):
The oracle database on this new server was already 11.2.3.0 -it was not upgrade, i directly installed 11.2.0.3.0 on it + applied latest patches etc.
I took RMAN backup from old server 11.1.0.7.0 oracle database.
Copied this backup to to the new server flash recovery area &every step of the restore was working fine -
in nomount mode, restored the control file from autobackup-fine
in mount mode, catalogued the files-fine (Backup from old live,copied to new live)
I restored&Recovered the database until the latest archivelogs.
Until the above steps-all worked fine like a normal recovery steps.
Then I gave "alter database open resetlogs" in RMAN prompt, it gave out error and from that point onwards I am unable to open the database now.
Unfortunately, couldnt grab full screenshot of the error in RMAN but the error basically said that bootstrap failed and i have to open the database with the upgrade option?
Please see in alert log as well
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Following is the last lines from alert log:
[code]
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Windows NT Version V6.1 Service Pack 1
CPU : 4 - type 8664, 4 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:3760M/8191M, Ph+PgF:9170M/16381M
VM name : VMWare Version (6)
Using parameter settings in server-side spfile F:\APP\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEGEOP.ORA
System parameters with non-default values:
processes = 150
memory_target = 3728M
control_files = "F:\ORACLE11G\ORADATA\GEOP\GEOP\CONTROL01.CTL"
control_files = "F:\ORACLE11G\ORADATA\GEOP\GEOP\CONTROL02.CTL"
control_files = "F:\ORACLE11G\ORADATA\GEOP\GEOP\CONTROL03.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_format = "ARC%S_%R.%T"
db_recovery_file_dest = "I:\oracle\flash_recovery_area"
db_recovery_file_dest_size= 45G
undo_tablespace = "UNDOTBS1"
sec_case_sensitive_logon = FALSE
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=GEOPXDB)"
audit_file_dest = "F:\APP\ORACLE\ADMIN\GEOP\ADUMP"
audit_trail = "DB"
db_name = "GEOP"
open_cursors = 300
diagnostic_dest = "F:\APP\ORACLE"
Thu Dec 12 17:22:18 2013
PMON started with pid=2, OS id=3440
Thu Dec 12 17:22:18 2013
PSP0 started with pid=3, OS id=10252
Thu Dec 12 17:22:19 2013
VKTM started with pid=4, OS id=11684 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Thu Dec 12 17:22:19 2013
GEN0 started with pid=5, OS id=4528
Thu Dec 12 17:22:19 2013
DIAG started with pid=6, OS id=5652
Thu Dec 12 17:22:19 2013
DBRM started with pid=7, OS id=7676
Thu Dec 12 17:22:19 2013
DIA0 started with pid=8, OS id=5724
Thu Dec 12 17:22:19 2013
MMAN started with pid=9, OS id=6632
Thu Dec 12 17:22:19 2013
DBW0 started with pid=10, OS id=3572
Thu Dec 12 17:22:19 2013
LGWR started with pid=11, OS id=8876
Thu Dec 12 17:22:19 2013
CKPT started with pid=12, OS id=3748
Thu Dec 12 17:22:20 2013
SMON started with pid=13, OS id=8108
Thu Dec 12 17:22:20 2013
RECO started with pid=14, OS id=1932
Thu Dec 12 17:22:20 2013
MMON started with pid=15, OS id=7468
Thu Dec 12 17:22:20 2013
MMNL started with pid=16, OS id=8136
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = F:\app\oracle
Thu Dec 12 17:22:21 2013
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 3351347149
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Thu Dec 12 17:22:26 2013
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Started redo scan
Completed redo scan
read 11 KB redo, 6 data blocks need recovery
Started redo application at
Thread 1: logseq 3, block 2, scn 59089613795
Recovery of Online Redo Log: Thread 1 Group 6 Seq 3 Reading mem 0
Mem# 0: F:\ORACLE11G\ORADATA\GEOP\GEOP\REDO06.LOG
Completed redo application of 0.01MB
Completed crash recovery at
Thread 1: logseq 3, block 24, scn 59089633817
6 data blocks read, 6 data blocks written, 11 redo k-bytes read
Read of datafile 'F:\ORACLE11G\ORADATA\GEOP\GEOP\TEMP01.DBF' (fno 201) header failed with ORA-01203
Rereading datafile 201 header failed with ORA-01203
Errors in file F:\APP\ORACLE\diag\rdbms\geop\geop\trace\geop_dbw0_3572.trc:
ORA-01186: file 201 failed verification tests
ORA-01122: database file 201 failed verification check
ORA-01110: data file 201: 'F:\ORACLE11G\ORADATA\GEOP\GEOP\TEMP01.DBF'
ORA-01203: wrong incarnation of this file - wrong creation SCN
File 201 not verified due to error ORA-01122
LGWR: STARTING ARCH PROCESSES
Thu Dec 12 17:22:27 2013
ARC0 started with pid=19, OS id=10876
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Thu Dec 12 17:22:28 2013
ARC1 started with pid=24, OS id=10912
Thu Dec 12 17:22:28 2013
ARC2 started with pid=25, OS id=6652
Thu Dec 12 17:22:28 2013
ARC3 started with pid=26, OS id=9648
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
Thread 1 advanced to log sequence 4 (thread open)
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Thread 1 opened at log sequence 4
Current log# 4 seq# 4 mem# 0: F:\ORACLE11G\ORADATA\GEOP\GEOP\REDO04.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Archived Log entry 64945 added for thread 1 sequence 3 ID 0xc7c27920 dest 1:
Errors in file F:\APP\ORACLE\diag\rdbms\geop\geop\trace\geop_ora_12260.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Errors in file F:\APP\ORACLE\diag\rdbms\geop\geop\trace\geop_ora_12260.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Error 704 happened during db open, shutting down database
USER (ospid: 12260): terminating the instance due to error 704
Instance terminated by USER, pid = 12260
ORA-1092 signalled during: ALTER DATABASE OPEN...
opiodr aborting process unknown ospid (12260) as a result of ORA-1092
Thu Dec 12 17:22:33 2013
ORA-1092 : opitsk aborting process
[/code]
Please please please let me know what steps should I do now to get my 11g database operational again?
Now when i am trying:
(SQL prompt)
[code]
>sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.3.0 Production on Thu Dec 12 17:22:05 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup open;
ORACLE instance started.
Total System Global Area 3891630080 bytes
Fixed Size 2261120 bytes
Variable Size 2147487616 bytes
Database Buffers 1728053248 bytes
Redo Buffers 13828096 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 12260
Session ID: 5 Serial number: 5
SQL> startup open upgrade;
SP2-0714: invalid combination of STARTUP options
SQL> startup upgrade;
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> startup upgrade open;
SP2-0714: invalid combination of STARTUP options
SQL> alter database mount;
ERROR:
ORA-03114: not connected to ORACLE
SQL> shutdown immediate;
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> startup nomount
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL>
[/code]This is why you do backups both before and after doing other things.
So one way to do something like this:
Backup old db.
expdp old db.
Install new 11gR2, create database.
Back it up.
Turn off archivelog.
impdp
Turn on archivelog.
Back it up.
The general thought here is you would start over with the first new db backup if the imp didn't work, you turn off archiving to avoid generating lots of redo that would be for a recovery you would never do.
There is more than one way to do it (TIMTOWTDI), best way depends on details, including volume of data and platform changes. expdp/impdp has an over the network option if disk space is limited and network is fast.
I usually allow for several tries when going to a new box, since the new box will require testing anyways. -
Rman recovery issue in oracle database 10g
hi all,
i have two backups of database one is full and of 3 days previous than sysdate and one is incremental level 1 of sysdate.i have recover database successfully upto 3 days previous and open database with resetlogs but recovering the incremental backup i got the following error
RMAN> restore database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI
*:SS')";*
*Starting restore at 10-JUN-09*
*using channel ORA_DISK_1*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03002: failure of restore command at 06/10/2009 14:23:13*
*RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time*
what should i do in this regard to recover upto sysdate with rmanRMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> restore database until time "to_date('06/10/09 01:09:00','MM/DD/YY HH24:MI
*:SS')";*
*Starting restore at 11-JUN-09*
*allocated channel: ORA_DISK_1*
*channel ORA_DISK_1: sid=155 devtype=DISK*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03002: failure of restore command at 06/11/2009 10:28:42*
*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*
*RMAN-06023: no backup or copy of datafile 2 found to restore*
*RMAN-06023: no backup or copy of datafile 1 found to restore*
*RMAN> restore database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI*
*:SS')";*
*Starting restore at 11-JUN-09*
*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 C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\SYSTEM01.DBF*
*restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\UNDOTBS01.DBF*
*restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\SYSAUX01.DBF*
*restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\USERS01.DBF*
*restoring datafile 00005 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\PROJECT1.DBF*
*restoring datafile 00006 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\LIMS1.DBF*
*restoring datafile 00007 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\FMADATA01.DBF*
*channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC*
*OVERY_AREA\WINDB\BACKUPSET\2009_06_10\O1_MF_NNND1_TAG20090610T130709_52YTFH6T_.B*
*KP*
*channel ORA_DISK_1: restored backup piece 1*
*piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WINDB\BACKUPSET\2009_0*
*6_10\O1_MF_NNND1_TAG20090610T130709_52YTFH6T_.BKP tag=TAG20090610T130709*
*channel ORA_DISK_1: restore complete, elapsed time: 00:01:26*
*Finished restore at 11-JUN-09*
*RMAN> recover database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI*
*:SS')";*
*Starting recover at 11-JUN-09*
*using channel ORA_DISK_1*
*starting media recovery*
*archive log thread 1 sequence 59 is already on disk as file C:\ORACLE\PRODUCT\10*
*.2.0\FLASH_RECOVERY_AREA\WINDB\ARCHIVELOG\2009_06_10\O1_MF_1_59_52YVW5X9_.ARC*
*archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WINDB\ARCHIVEL*
*OG\2009_06_10\O1_MF_1_59_52YVW5X9_.ARC thread=1 sequence=59*
*media recovery complete, elapsed time: 00:00:02*
*Finished recover at 11-JUN-09*
*RMAN>*
then after performing the recovery when i tried to open the database
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
i have also tried to open it with resetlogs
any suggestion to open it now ? -
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 95676701Thanks 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 -
ORA-01180: can not create datafile 1 during RMAN restore.
Hello,
I am trying to refresh one of our QA environments and I am getting this error message:
RMAN> run
2> {
3> allocate channel c1 device type disk;
4> allocate channel c2 device type disk;
5> restore database;
6> recover database;
7> }
allocated channel: c1
channel c1: SID=5 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 08-NOV-12
using channel ORA_DISK_1
creating datafile file number=1 name=+DATA1/alephpr/datafile/system.269.722874729
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/08/2012 16:27:40
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DATA1/alephpr/datafile/system.269.722874729' I created a new database from scratch with the same name as is in Production, later on I will proceed to rename it to the right one. I started the steps for refreshing the PRD copy:
RMAN> shutdown immediate
using target database control file instead of recovery catalog
database dismounted
Oracle instance shut down
RMAN> startup nomount
connected to target database (not started)
Oracle instance started
Total System Global Area 534462464 bytes
Fixed Size 2228200 bytes
Variable Size 176160792 bytes
Database Buffers 348127232 bytes
Redo Buffers 7946240 bytes
RMAN> set dbid=3573460394
executing command: SET DBID
RMAN> restore controlfile from '/restorealeph/c-3573460394-20121106-01';
Starting restore at 08-NOV-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=130 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
+output file name=+DATA1/alephpr/controlfile/current.260.798747585+
+output file name=+FLASH/alephpr/controlfile/current.276.798747585+
Finished restore at 08-NOV-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1Once the control file is restored, I need to crosscheck, delete expired and catalog the backups at the new server:
RMAN> crosscheck backup;
Crosschecked 48 objects
RMAN> delete noprompt expired backup;
Deleted 48 EXPIRED objects
RMAN> list backup summary;
specification does not match any backup in the repositoryI need now to catalog the backups we transferred from Prod into the QA server's directory /restorealeph:
RMAN> catalog start with '/restorealeph/';
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
4097 B F A DISK 07-NOV-12 1 1 NO BACKUP_ALEPHPR.TUR_110712030000
4098 B A A DISK 07-NOV-12 1 1 NO BACKUP_ALEPHPR.TUR_110712030000
RMAN> list backup tag="BACKUP_ALEPHPR.TUR_110712030000";
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4097 Full 178.04G DISK 00:00:00 07-NOV-12
BP Key: 4097 Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
Piece Name: /restorealeph/9cnpm51u_1_1
List of Datafiles in backup set 4097
File LV Type Ckp SCN Ckp Time Name
1 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/system.269.722874729
2 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/sysaux.266.722874731
3 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.289.722874727
4 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.257.722874727
5 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/users.298.722874731
6 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/audit.299.723372305
7 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_datos.260.723372307
8 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/case_indices.261.723372307
9 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_hist.262.723372309
10 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_l.264.723372319
11 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_long.265.723372349
12 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_md.270.723372355
13 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.271.723372369
14 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_xl.272.723372375
15 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_l.273.723372401
16 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_md.274.723372427
17 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_sm.275.723372455
18 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/index_xl.276.723372473
19 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/tools.278.723372501
26 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/data_sm.300.736088959
27 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_meta.301.746385117
28 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_pstore.302.746385119
29 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/dev_disco_ptm5_cache.304.746385121
30 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs1.305.796391931
31 Full 6919879655786 07-NOV-12 +DATA1/alephpr/datafile/undotbs2.306.796392185
BS Key Size Device Type Elapsed Time Completion Time
4098 16.89G DISK 00:00:00 07-NOV-12
BP Key: 4098 Status: AVAILABLE Compressed: NO Tag: BACKUP_ALEPHPR.TUR_110712030000
Piece Name: /restorealeph/9enpm6lj_1_1
List of Archived Logs in backup set 4098
Thrd Seq Low SCN Low Time Next SCN Next Time
1 35722 6919870864350 06-NOV-12 6919871887697 06-NOV-12
1 35723 6919871887697 06-NOV-12 6919872372211 06-NOV-12
1 35724 6919872372211 06-NOV-12 6919872410158 06-NOV-12
1 35725 6919872410158 06-NOV-12 6919872447301 06-NOV-12
1 35726 6919872447301 06-NOV-12 6919872503332 06-NOV-12
1 35727 6919872503332 06-NOV-12 6919872551564 06-NOV-12
1 35728 6919872551564 06-NOV-12 6919872603881 06-NOV-12
1 35729 6919872603881 06-NOV-12 6919872655942 06-NOV-12
1 35730 6919872655942 06-NOV-12 6919872698722 06-NOV-12
1 35731 6919872698722 06-NOV-12 6919872741655 06-NOV-12
1 35732 6919872741655 06-NOV-12 6919872782284 06-NOV-12
1 35733 6919872782284 06-NOV-12 6919872872302 06-NOV-12
1 35734 6919872872302 06-NOV-12 6919872910206 06-NOV-12
1 35735 6919872910206 06-NOV-12 6919872945577 06-NOV-12
1 35736 6919872945577 06-NOV-12 6919872980056 06-NOV-12
1 35737 6919872980056 06-NOV-12 6919873013411 06-NOV-12
1 35738 6919873013411 06-NOV-12 6919873050761 06-NOV-12
1 35739 6919873050761 06-NOV-12 6919873084996 06-NOV-12
1 35740 6919873084996 06-NOV-12 6919873122049 06-NOV-12
1 35741 6919873122049 06-NOV-12 6919873521767 06-NOV-12
1 35742 6919873521767 06-NOV-12 6919873952773 06-NOV-12
1 35743 6919873952773 06-NOV-12 6919874258549 06-NOV-12
1 35744 6919874258549 06-NOV-12 6919874472213 06-NOV-12
1 35745 6919874472213 06-NOV-12 6919874744856 06-NOV-12
1 35746 6919874744856 06-NOV-12 6919875113086 06-NOV-12
1 35747 6919875113086 06-NOV-12 6919875733337 06-NOV-12
1 35748 6919875733337 06-NOV-12 6919876139061 06-NOV-12
1 35749 6919876139061 06-NOV-12 6919876707162 06-NOV-12
1 35750 6919876707162 06-NOV-12 6919877706313 06-NOV-12
1 35751 6919877706313 06-NOV-12 6919877919039 06-NOV-12
1 35752 6919877919039 06-NOV-12 6919878024429 06-NOV-12
1 35753 6919878024429 06-NOV-12 6919878107673 06-NOV-12
1 35754 6919878107673 06-NOV-12 6919878258511 06-NOV-12
1 35755 6919878258511 06-NOV-12 6919878308336 06-NOV-12
1 35756 6919878308336 06-NOV-12 6919878424419 06-NOV-12
1 35757 6919878424419 06-NOV-12 6919878488485 06-NOV-12
1 35758 6919878488485 06-NOV-12 6919878827092 06-NOV-12
1 35759 6919878827092 06-NOV-12 6919879350098 07-NOV-12
1 35760 6919879350098 07-NOV-12 6919879675556 07-NOV-12
2 35949 6919870864360 06-NOV-12 6919871494640 06-NOV-12
2 35950 6919871494640 06-NOV-12 6919871887487 06-NOV-12
2 35951 6919871887487 06-NOV-12 6919872410655 06-NOV-12
2 35952 6919872410655 06-NOV-12 6919872552468 06-NOV-12
2 35953 6919872552468 06-NOV-12 6919872698940 06-NOV-12
2 35954 6919872698940 06-NOV-12 6919872872690 06-NOV-12
2 35955 6919872872690 06-NOV-12 6919872980371 06-NOV-12
2 35956 6919872980371 06-NOV-12 6919873085902 06-NOV-12
2 35957 6919873085902 06-NOV-12 6919873569082 06-NOV-12
2 35958 6919873569082 06-NOV-12 6919873949096 06-NOV-12
2 35959 6919873949096 06-NOV-12 6919874404640 06-NOV-12
2 35960 6919874404640 06-NOV-12 6919875011814 06-NOV-12
2 35961 6919875011814 06-NOV-12 6919875631429 06-NOV-12
2 35962 6919875631429 06-NOV-12 6919876324885 06-NOV-12
2 35963 6919876324885 06-NOV-12 6919876363526 06-NOV-12
2 35964 6919876363526 06-NOV-12 6919876748508 06-NOV-12
2 35965 6919876748508 06-NOV-12 6919877741784 06-NOV-12
2 35966 6919877741784 06-NOV-12 6919878108943 06-NOV-12
2 35967 6919878108943 06-NOV-12 6919878424477 06-NOV-12
2 35968 6919878424477 06-NOV-12 6919879012111 06-NOV-12
2 35969 6919879012111 06-NOV-12 6919879260589 07-NOV-12
2 35970 6919879260589 07-NOV-12 6919879350086 07-NOV-12
2 35971 6919879350086 07-NOV-12 6919879464935 07-NOV-12
2 35972 6919879464935 07-NOV-12 6919879548399 07-NOV-12
2 35973 6919879548399 07-NOV-12 6919879675564 07-NOV-12
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ALEPHPR 3573460394 PARENT 1 13-MAY-10
2 2 ALEPHPR 3573460394 PARENT 2229467 28-JUN-10
3 3 ALEPHPR 3573460394 CURRENT 6918261828355 26-SEP-12The ASM structure is created...
ASMCMD> lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 1048576 509282 507421 0 507421 0 N DATA1/
MOUNTED EXTERN N 512 4096 1048576 50641 42850 0 42850 0 N FLASH/
ASMCMD> cd DATA1/ALEPHPR/DATAFILE
ASMCMD> pwd
+DATA1/ALEPHPR/DATAFILEBoth source and target databases are 11.2.0.2 PSU 6 running on Linux x64. I cannot use RMAN Duplicate since there is no visibility among different environments (PROD - QA in this case).
Any idea?
Thanks
Martin
Edited by: martin.morono on Nov 8, 2012 11:19 AM
Edited by: martin.morono on Nov 8, 2012 11:49 AMThanks Levi,
I slightly modified your script to recatalog the backup pieces since they are note stored at the same location in PR and QA.
No luck. The error message is different but the result is the same... it keeps failing.
RMAN> run {
2> allocate channel c1 device type disk;
3> allocate channel c2 device type disk;
4> restore controlfile from '/restorealeph/c-3573460394-20121107-01';
5> startup mount;
6> catalog start with '/restorealeph/';
7> restore database from tag 'BACKUP_ALEPHPR.TUR_110712030000';
8> }
allocated channel: c1
channel c1: SID=191 device type=DISK
allocated channel: c2
channel c2: SID=131 device type=DISK
Starting restore at 09 NOV 2012 13:11:09
channel c2: skipped, AUTOBACKUP already found
channel c1: restoring control file
channel c1: restore complete, elapsed time: 00:00:15
output file name=+DATA1/alephpr/controlfile/current.260.798747585
output file name=+FLASH/alephpr/controlfile/current.276.798747585
Finished restore at 09 NOV 2012 13:11:24
database is already started
database mounted
Starting implicit crosscheck backup at 09 NOV 2012 13:11:31
Crosschecked 52 objects
Finished implicit crosscheck backup at 09 NOV 2012 13:11:39
Starting implicit crosscheck copy at 09 NOV 2012 13:11:39
Crosschecked 2 objects
Finished implicit crosscheck copy at 09 NOV 2012 13:11:40
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_1.279.795017193
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_2_seq_34950.273.795014469
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_1.281.795017413
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_2.283.795017519
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_3.290.795018411
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_4.291.795018559
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_5.292.795018707
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_6.293.795018811
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_7.294.795018899
File Name: +flash/ALEPHPR/ARCHIVELOG/2012_09_26/thread_1_seq_8.295.795020509
File Name: +flash/ALEPHPR/CONTROLFILE/Current.268.798725123
searching for all files that match the pattern /restorealeph/
List of Files Unknown to the Database
=====================================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Do you really want to catalog the above files (enter YES or NO)? YEs
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /restorealeph/9cnpm51u_1_1
File Name: /restorealeph/9enpm6lj_1_1
File Name: /restorealeph/c-3573460394-20121107-00
File Name: /restorealeph/c-3573460394-20121107-01
File Name: /restorealeph/c-3573460394-20121106-01
Starting restore at 09 NOV 2012 13:11:48
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/09/2012 13:11:48
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to 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
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN>Just in case, I re-run this script including the crosscheck backup and the delete noprompt expired backups before restoring an the error messages were the same.
THanks again for your help.
Regards.
Martin
Edited by: martin.morono on Nov 9, 2012 7:21 AM -
Problem creating physical Standby database with RMAN
Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again -
Problem in performing multiple Point-In-Time Database Recovery using RMAN
Hello Experts,
I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
Environment:
Oracle 11g, ASM,
Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
Snapshot DiskGroups :
Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
Steps performed for point in time recovery:
1. Restore control file from snapshot 2.
RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
3. Catalog data files from snapshot 1.
4. Catalog archive logs from snapshot 2.
5. Perform point in time recovery till given time.
STARTUP MOUNT;
RUN {
SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
SET UNTIL TIME "06-mar-2013 09:30:00";
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
Results:
Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
Starting recover at 28-FEB-13
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/06/2013 11:10:57
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until time 'MAR 06 2013 09:45:00'
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
Doubts:
1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
However for this to work, I always need to keep the AutoBackup feature enabled.
How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
Please help me out in this issue.
Thanks.992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.
Maybe you are looking for
-
I have been trying to complete the most simplist of task's or so I am told, which is to update my Intel 440 BX MS 6156 VER 1 BX7 64MB memory to 256MB by using two 128MB memory cards. Twice I have been given the wrong cards, the last two were labeled
-
How can I get rid of tab groups (not a button, but the feature itself)? Hate it. Thank you.
I would like to have just tabs without groups, visible all at once, as we had it in previous firefox versions. I don't see any instructions/options. Please help.
-
Exporting Crystal Report To Excel
Hello, I have created a report in crystal for my company. It sorts by rep name, then customer, then products they purchased. When I export to excel, it comes over fine, but the customer name, address, etc. is in the same column as quantity, price, et
-
How to restrict Stock posting in Specific Storage Location
We Want to restrict posting of cenvet creadit taken material to specific storage loacation at time of GRN (MVT 105)
-
Can you alter the JVM heap space size for all Windows users?
Hi, I have used the "-Xmx" option to increase the Java Heap space for my Java application. This works fine, but all other users on my system still have the default heap space setting and I want them to have use an increased heap space as well. I cann