RMAN recovery Issue
Hi Expert,
I having a issue when do db recovery with following error. My db is not in archivelog mode. Kindly advise Tks
channel dev1: restore complete
Finished restore at 20-AUG-10
Starting recover at 20-AUG-10
starting media recovery
unable to find archive log
archive log thread=1 sequence=1
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: '/export/home/oracleas/oradata/orcl/system01.dbf'
released channel: dev1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/20/2010 15:12:34
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 8165752
Recovery Manager complete.
Hi,
Information as per below:
RMAN> list incarnation of database;
using target database controlfile instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORCL 1236121495 PARENT 1 20-JUN-06
2 2 ORCL 1236121495 CURRENT 743480 15-JAN-10
3 3 ORCL 1236121495 ORPHAN 8165752 20-AUG-10
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1 Full 1G DISK 00:01:58 20-AUG-10
BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20100820T122103
Piece Name: /export/home/oracleas/infra/backup/01llqgtf_1_1
List of Datafiles in backup set 1
File LV Type Ckp SCN Ckp Time Name
1 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/system01.dbf
2 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/undotbs01.dbf
3 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/sysaux01.dbf
4 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/users01.dbf
5 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/portal.dbf
6 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptldoc.dbf
7 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptlidx.dbf
8 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptllog.dbf
9 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ias_meta01.dbf
10 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/discopltm1.dbf
11 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/discopltc1.dbf
12 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/dcm.dbf
13 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/oss_sys01.dbf
14 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/wcrsys01.dbf
15 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_rt.dbf
16 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_dt.dbf
17 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_idx.dbf
18 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_lob.dbf
19 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/orabpel.dbf
20 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/bam.dbf
21 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/oca.dbf
22 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/uddisys01.dbf
23 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/attrs1_oid.dbf
24 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/battrs1_oid.dbf
25 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/gcats1_oid.dbf
26 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/gdefault1_oid.dbf
27 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/svrmg1_oid.dbf
28 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/very_large_data.dbf
29 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/very_large_indexes. dbf
30 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/large_indexes.dbf
31 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/medium_data.dbf
32 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/medium_indexes.dbf
33 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/small_data.dbf
34 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/small_indexes.dbf
35 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/TBS_MYGST.DBF
36 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/very_large_data_k b.dbf
37 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/very_large_indexe s_kb.dbf
38 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/large_data_kb.dbf
39 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/large_indexes_kb. dbf
40 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/medium_data_kb.db f
41 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/medium_indexes_kb .dbf
42 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/small_data_kb.dbf
43 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/small_indexes_kb. dbf
44 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/TBS_MYKBGST.DBF
Similar Messages
-
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 ? -
RMAN Backup Issue when Full backup file was missing
Hi,
On : 11.2.0.2 version, Recovery Manager
RMAN Backup issue
Last week we had the NFS Issue where we backup the files onto NFS.
The problem occurred in the below sequence
Saturday the backup was successful
Saturday before deleting the backup files they are copied to tape
Deleting the backup files via OS command
Sunday Full backup started but due the NFS issue backup failed(Killed the instance and restarted)
Did the RMAN Incremental backup which worked on Monday
On Tuesday RMAN started complaining and started doing the Full backup.
no parent backup or copy of datafile 1 found
no parent backup or copy of datafile 3 found
no parent backup or copy of datafile 24 foundSony any idea why the Incremental backup worked on Monday but not on Tuesday
Regards
NMOk here is why I would like exact filenames..
1) to speed the time of recovery. I am much more familiar with traditional recovery methods than RMAN, and while I myself installed and suggested RMAN for backups, our other (11i) database does not use RMAN and so I am more familiar with traditional recovery. So to be able to recover quickly I want to have these files as close as possible to the original names so that I can use my standard script (from a trace file) to recreate the control fiile. If I can get RMAN to spit out the filies with original names but keep RMAN for making the backup, I may ditch the rman bacjup script in chron and write a traditional hot backup script which copies the files the old fashioned way.
2) to reduce cloning time. The RMAN duplicate command is not as good as I thought. I was actually easier for me to restore RMAN backups first to a box that has all the same paths, and THEN shutdown (cold) these files and copy them cold to another server, and restore from there. Agaiin if I can get the original file names, I could choose to do recovery either way (RMAN or traditional) in a real emergency instead of being forced to use rman.
3) to be able to switch to a backup file in the FRA without having to rename it. Seems logical if it is already named correctly.
thanks ! Marvi -
Error while rman recovery of database
We are using rman recovery for database clone.
I am getting the following error,
restoring datafile 00442 to /d05/u10/oracle/ndevdata/applsysd06.dbf
channel dup1: reading from backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
failover to previous backup
How to resolve this?
Thanks,
Kavithahi;
Please follow:
Re: erros while clong a db
Also check:
http://kr.forums.oracle.com/forums/thread.jspa?threadID=546746
Re: rapid clone from RMAN backup
Regard
Helios -
RMAN Recovery failing , Need Suggestion
RMAN Recovery is failing 3 times with these errors , need suggestion
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/20/2006 22:44:32
RMAN-03015: error occurred in stored script Memory Script
ORA-19504: failed to create file "/oradata/F3LIPO/system/tools_01.dbf"
ORA-27040: skgfrcre: create error, unable to create file
HP-UX Error: 2: No such file or directory
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 09/20/2006 23:12:27
RMAN-06403: could not obtain a fully authorized session
RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
HP-UX Error: 2: No such file or directory
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/21/2006 12:24:56
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operationMy concern is
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/21/2006 12:24:56
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current -
Oracle RMAN recovery catalog database in a Primary and Standby mode
Hello All,
The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers. The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups).
Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
Thanks in advance..
Regards,
Abhijit"The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups"
Hi,
i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
There is no TAF in this situation.
Hope this helps.
Regs,
Drew -
hellow,
I am working on a rman recovery scenario as follows:
---I have a full backup on sunday
---My database in archivelog mode
---now I lost one of table on Monday 7:20PM
---then I lost another table on same day at 7:40PM
---I came to know about this(both table drop incident) at 7:45PM same day
---Now I have to recover both the tables
---I have catalog database configured
please tell me step by step, how the recovery should be done?
And I also want to know where I can find such scenarios on which I can work any book or web resource?This is an abstract of http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr006.htm#sthref651
DBPITR within the current incarnation is performed using the current control file. When performing DBPITR, you can avoid errors by using the SET UNTIL command to set the target time at the beginning of the process, rather than specifying the UNTIL clause on the RESTORE and RECOVER commands individually. This ensures that the datafiles restored from backup will have timestamps early enough to be used in the subsequent RECOVER operation.
The steps required for DBPITR are as follows:
Connect RMAN to the target database and, if applicable, the recovery catalog database. Bring the database to a MOUNT state:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
Perform the following operations within a RUN block:
Use SET UNTIL to specify the target time, restore point, SCN, or log sequence number for DBPITR. If specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment variables.
If automatic channels are not configured, then manually allocate disk and tape channels as needed.
Restore and recover the database.
The following example performs DBPITR on the target database until SCN 1000:
RUN
SET UNTIL SCN 1000;
# Alternatives:
# SET UNTIL TIME 'Nov 15 2004 09:00:00';
# SET UNTIL SEQUENCE 9923;
RESTORE DATABASE;
RECOVER DATABASE;
Note:
You can also use time expressions, restore points, or log sequence numbers to specify the SET UNTIL time:
SET UNTIL TIME 'Nov 15 2004 09:00:00';
SET UNTIL SEQUENCE 9923;
SET UNTIL RESTORE POINT before_update;
If the operation completes without errors, then your DBPITR has succeeded. You can open the database read-only and perform queries as needed to ensure that the effects of the logical corruption have been reversed. If not, you may have chosen the wrong target SCN. In such a case, investigate the unwanted change further and determine a new target SCN, then repeat the DBPITR process.
7.6.4.1 Using a Time Expression for Database Point-in-Time Recovery
You can use a time expression instead of the SCN in the SET UNTIL statement, as shown in the preceding example. However, note that if you use SET UNTIL TIME to specify the target time for point-in-time recovery, some times that you can specify may not be in the current incarnation. The database may have been in an ancestor incarnation, or even in a sibling incarnation, at the target time. If your target time is not in the current incarnation, then see "Point-in-Time Recovery to an Ancestor Incarnation" for more information on DBPITR to ancestor incarnations, and Oracle Database Backup and Recovery Advanced User's Guide for more information on DBPITR to incarnations that are not ancestors of the current incarnation.
7.6.5 Options After Database Point-in-Time Recovery
After a successful DBPITR, your choices are:
Export one or more objects from your database using an Oracle export utility such as Data Pump Export. You can then recover the database to the current point in time and re-import the exported objects, as a way to return these objects to their state prior to the unwanted change without abandoning all other changes.
Open your database for read-write, abandoning all changes after the target SCN. In such a case, you must open the database with the RESETLOGS option, as shown here:
RMAN> ALTER DATABASE OPEN RESETLOGS;
The current online redo logs are archived, the log sequence number is reset to 1, and the online redo logs are given a new time stamp and SCN. Identifying redo log files with a new log sequence number and incarnation eliminates the possibility of corrupting datafiles by the application of obsolete archived redo logs.
The OPEN RESETLOGS operation will fail if a datafile is off-line, unless the datafile went offline normally or is read-only. You can bring files in read-only or offline normal tablespaces online after the RESETLOGS because they do not need any redo.
Sybrand Bakker
Senior Oracle DBA -
Rman Recovery using backup created using dbconsole
Thanks for taking my questions. First, I see there is another person asking about rman recovery but I am hoping mine is not identical.
BACKGROUND
Archiving and flashback is on.
Database is 11g.
Full on-line database backup is done using dbconsole (oem) and includes control, spfile and archive logs.
RECOVERY
I am testing my recovery to a new serve.
I installed oracle
Restored a backupset from one backup to the new servers flashbackup area.
Recovered the spfile ok
Recovered the control file ok
Found last seq number ok
Restore database ok
RECOVER DATABASE UNTIL SEQUENCE - NOT OK
Error=DATAFILE 1 MUST BE RESTORED FROM BACKUP OLDER THAN SCN
QUESTIONS
Where did I go wrong?
Could it be my rman backup didn't backup all necessary archive logs?
How do I fix this and can I fix it using dbconsole?
Also, is it still possible to fix the test server without loading any new files?
Thanks!
KathieHello,
To answer your questions, it looks like your backup is out of sync with SCN for datafiles with your Oracle 11g database.
What you need to do is first check the low SCN and current SCN for your database to that in your RMAN backup files.
You can check backups in RMAN command line with
RMAN> list backup;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
1 349.08M DISK 00:01:14 24-JAN-08
BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20080124T180119
Piece Name: C:\ORACLE\FLASHBACK\ORCL\BACKUPSET\2008_01_24\O1_MF_ANNNN_TA
G20080124T180119_3SLJQOFO_.BKP
List of Archived Logs in backup set 1
Thrd Seq Low SCN Low Time Next SCN Next Time
1 1 1030802 04-JAN-08 1053767 05-JAN-08
1 2 1053767 05-JAN-08 1104812 06-JAN-08
Then open another prompt window and SQL*PLUS session as sysdba privileged account:
SQL> select name, current_scn from v$database;
NAME CURRENT_SCN
ORCL 4089528
You need to make sure that you are trying to restore database with RMAN with a backup for the SCN numbers that are older than the current database SCN in database or Oracle will complain.
Enterprise Manager dbconsole will work but nothing beats the power of a command line.
Use the automated repair options for the Oracle 11g Database Repair advisors.
1. Connect to RMAN
rman target=/
RMAN> list failure;
RMAN> repair failure preview;
RMAN> repair failure;
For more details, Arup Nanda has a good overview of RMAN with Oracle 11g:
http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-rman.html
Hope this helps you out.
-Ben
Cheers,
Ben Prusinski
http://oracle-magician.blogspot.com/ -
I have an Oracle 8i running on Solaris 9 server, the following shell script is used to backup the database using crontab and it runs daily during off-peak hours:
DAY=`date +%Y%m%d%H%M`
rman nocatalog msglog=/oracle/u01/app/oracle/product/8.1.7/daily_rman.log append <<!
connect target /
run {
allocate channel c1 type disk format '/oradb/backup/ctrl_%s_%p_%t.rman';
backup current controlfile;
run {
allocate channel c1 type disk format '/oradb/backup/full_%s_%p_%t.rman';
allocate channel c2 type disk format '/oradb/backup/full_%s_%p_%t.rman';
allocate channel c3 type disk format '/oradb/backup/full_%s_%p_%t.rman';
allocate channel c4 type disk format '/oradb/backup/full_%s_%p_%t.rman';
allocate channel c5 type disk format '/oradb/backup/full_%s_%p_%t.rman';
backup incremental level=0 database;
run {
allocate channel c1 type disk format '/oradb/backup/arch_%s_%p_%t.rman';
sql 'alter system archive log current';
sql 'alter system archive log current';
backup archivelog from time 'sysdate-1' delete input;
svrmgrl <<!
connect internal
alter database backup controlfile to '/oradb/backup/${DAY}.ctl';
And the backup runs successfully. Now the problem when I take the backup output and try to recover it on another server running the same Oracle 8i on Solaris 9 and using the control file generated in the last step of the backup, the RMAN recovery proceeds without errors until the end of the recovery script in which startup the database which I get an error that the controlfile timestamp is newer than some datafiles, although the control file was taken last. Any ideas what went wrong?Hi Luts/All , let me explain more:
The restore script on the target server copies the control file from the last step in the backup script and startup mount, then :
rman nocatalog <<!
connect target /
run {
allocate channel c1 type disk;
allocate channel c2 type disk;
restore database;
recover database ;
The RMAN session restore completes and the recover starts and stops at the last available archivelog, and asks for the next archivelog, is there a way to tell RMAN to stop asking for the next archivelog after the last available one and do the startup?
Following is the output of the restore session:
Restore starts and completes
RMAN-08024: channel c2: restore complete
RMAN-03022: compiling command: recover
RMAN-03022: compiling command: recover(1)
RMAN-03022: compiling command: recover(2)
RMAN-03022: compiling command: recover(3)
RMAN-03023: executing command: recover(3)
RMAN-08054: starting media recovery
RMAN-03022: compiling command: recover(4)
RMAN-03023: executing command: recover(4)
RMAN-08017: channel c1: starting archivelog restore to default destination
RMAN-08022: channel c1: restoring archivelog
RMAN-08510: archivelog thread=1 sequence=22141
RMAN-08022: channel c1: restoring archivelog
RMAN-08510: archivelog thread=1 sequence=22142
RMAN-08022: channel c1: restoring archivelog
RMAN-08510: archivelog thread=1 sequence=22143
RMAN-08023: channel c1: restored backup piece 1
RMAN-08511: piece handle=/oradb/backup/arch_6854_1_635508091.rman tag=null params=NULL
RMAN-08024: channel c1: restore complete
RMAN-08515: archivelog filename=/archivelogs/arch1_22141.dbf thread=1 sequence=22141
RMAN-08515: archivelog filename=/archivelogs/arch1_22142.dbf thread=1 sequence=22142
RMAN-08515: archivelog filename=/archivelogs/arch1_22143.dbf thread=1 sequence=22143
RMAN-08060: unable to find archivelog
RMAN-08510: archivelog thread=1 sequence=22144
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: c2
RMAN-08031: released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03006: non-retryable error occurred during execution of command: recover(4)
RMAN-07004: unhandled exception during command execution on channel default
RMAN-20000: abnormal termination of job step
RMAN-06054: media recovery requesting unknown log: thread 1 scn 124394793 -
9.2.0.6 RMAN Disaster recovery issue
Our production database crashed and we are doing DR on a new host.
We dont have any catalog database and we dont use controlfile autobackup.
We just do a full backup including controlfile and also archive logs
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
run {
allocate channel d1 type disk;
backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
release channel d1;
We copied these backup pieces to the new host and tried the following way to restore the database.
startup nomount
rman
connect target /
RMAN> set DBID 2507695351;
executing command: SET DBID
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore controlfile from '/data/TESTDB/rman/testdb_bk_2_1_724368405';
5> }
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 14-JUL-10
channel d1: restoring controlfile
channel d1: restore complete
replicating controlfile
input filename=/data/TESTDB/cntrl01.dbf
output filename=/data/TESTDB/cntrl02.dbf
output filename=/data/TESTDB/cntrl03.dbf
Finished restore at 14-JUL-10
released channel: d1
exit
sqlplus '/ as sysdba'
shutdown immediate;
startup mount;
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore database;
5> }
using target database controlfile instead of recovery catalog
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 15-JUL-10
released channel: d1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/15/2010 00:03:18
RMAN-06026: some targets not found - aborting 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
We are using 9.2.0.6 on LINUX
The list backup commands too return EMPTY
RMAN> list backup;
RMAN> list backup of database;
---Any ideas ?
SrinivasI am also uploading the logfile of the backup job of the source database
RMAN> run
2> {
3> allocate channel d1 type disk;
4> backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
5> backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
6> release channel d1;
7> }
allocated channel: d1
channel d1: sid=17 devtype=DISK
Starting backup at 14-JUL-10
channel d1: starting full datafile backupset
channel d1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001 name=/data/TESTDB/system01.dbf
input datafile fno=00002 name=/data/TESTDB/undotbs01.dbf
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_bk_2_1_724368405 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:01
Finished backup at 14-JUL-10
Starting backup at 14-JUL-10
current log archived
channel d1: starting archive log backupset
channel d1: specifying archive log(s) in backup set
input archive log thread=1 sequence=3 recid=1 stamp=724368322
input archive log thread=1 sequence=4 recid=2 stamp=724368406
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_al_3_1_724368406 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:02
channel d1: deleting archive log(s)
archive log filename=/data/TESTDB/arch/archTESTDB_3.arc recid=1 stamp=724368322
archive log filename=/data/TESTDB/arch/archTESTDB_4.arc recid=2 stamp=724368406
Finished backup at 14-JUL-10
released channel: d1
RMAN> exit -
Oracle Server - Enterprise Edition - Version: 10.2.0.3
RMAN Catalog : 10.2.0.4
I am using the follwoing script for backup :
4> run
5> {
6> allocate channel dev1 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
7> allocate channel dev2 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
8> backup database FILESPERSET 20 ;
9> backup archivelog all archivelog until time 'sysdate-1' delete all input ;
10> release channel dev1 ;
11> release channel dev2 ;
12> }The issue is with backup archivelog all archivelog until time 'sysdate-1' delete all input ;
This command gives error
ORA-19588: Archived Log Recid Stamp Is No Longer Valid
even after doing crosscheck .
Referred Metalink ID : 1189883.1
which clearly indicates that the statement
backup archivelog all archivelog until time 'sysdate-1' delete all input ;
is wrong by logic and is the reason for the issue .
And suggests to use
backup archivelog until time 'sysdate-1' delete all input ;
or
backup archivelog all delete input ;
which definitely do not serve the purpose .
The logic that needs to be implemented is
I need to backup all archivelogs and delete archivelogs until sysdate-1 .....
How can I do this ? Please help ....
Regards
Renjith MadhavanOf course. You have asked Oracle to backup files as of 1 day old. Your command is explicitly stating that it is not to backup files newer than 1 day old.
Read and understand "archivelogRecordSpecifier" at
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#sthref121
UNTIL TIME "Specifies the end date for a sequence of archived redo log files"
It is actually used when doing RECOVER and RESTORE so as to do Point In Time Recovery.
Backups are not done with UNTIL TIME. The only scenario where someone would backup until TIME is when he is writing separate sets of backups deliberately to different backupsets (e.g. one backupset representing 01-Dec will subsequently be copied to another location or to Tape-1, the next backupset representing 02-Dec will be copied to a different location or to Tape-2 etc).
However, when you do a BACKUP DATABASE today, you have to ensure that you BACKUP ARCHIVELOG upto the latest archivelog else, you will NOT be able to use today's database backup for restore and recovery.
Hemant K Chitale
Edited by: Hemant K Chitale on Dec 6, 2010 2:57 PM -
Oracle 11.2.0.1
Windows 7 Home Premium
RMAN> backup database;
Starting backup at 05-MAR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 05-MAR-12
channel ORA_DISK_1: finished piece 1 at 05-MAR-12
piece handle=E:\APP\NISHA\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_03_05\O1_MF_NCSNF_TAG20120305T122505_7O8RTBXJ_.BKP tag=TAG20120305T122505 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN> 1.What is the problem in above scnerio ?
2.How to take RMAN backup when db is down ?
3.How to take RMAN backup when db is noarchivelog mode ?
Please help me. Thank you.I am trying to do a full RMAN cold backup and am getting the following :
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
What’s the cause ?
Here’s the example
connected to target database (not started)
Oracle instance started
database mounted Total System Global Area 1610612736 bytes Fixed Size 2056504 bytes
Variable Size 603983560 bytes
Database Buffers 989855744 bytes
Redo Buffers 14716928 bytes using target database control file instead of recovery catalog
allocated channel: backup_disk1
channel backup_disk1: sid=4977 instance=TEST1 devtype=DISK Starting backup at 31-OCT-13
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 31/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:46
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
released channel: backup_disk1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:47
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
The cause is simple, the database has not been shutdown cleanly. You will require to restart the database and shutdown again, if in a RAC you will have to shutdown all instances cleanly.
Disabing archive log and attempting to backup the database will demonstrate the cause.
SQL> startup force;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
Database opened.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL>
Now we’ll try again to backup datafile 1.
RMAN> backup datafile 1;
Starting backup at 31-OCT-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 13/10/2013 20:43:34
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
This is simply because we issue a shutdown abort on the instance. However, just preforming a recovery will allow you to backup as required.
SQL> recover database;
Media recovery complete.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:UsersGary>rman target sys/passwd@db11g
Recovery Manager: Release 11.2.0.1.0 – Production on Thu Oct 31 20:44:15 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DB10G (DBID=3002158372, not open)
RMAN> backup datafile 1;
Starting backup at 06-DEC-10using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=125 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:APPGARYORACLEPRODUCT10.2.0DB_1ORADATADB10GSYSTEM01.DBF
channel ORA_DISK_1: starting piece 1 at 31-OCT-13
channel ORA_DISK_1: finished piece 1 at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GBACKUPSET2010_12_06O1_MF_NNNDF_TAG20101206T204423_6HTCR810_.BKP tag=TAG20101206T204423 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 31-OCT-13
Starting Control File and SPFILE Autobackup at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GAUTOBACKUP2010_12_06O1_MF_S_737066556_6HTCSQVF_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 31-OCT-13
RMAN> exit
Interestingly, even with the recovery performed, we cannot switch back to archivelog mode without a clean shutdown.
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
So we’ll startup and shutdown again. You cannot use the force option since that still does not perform a normal shutdown and you’ll get the same error.
SQL> alter database open;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered. -
Problem with time based rman recovery
Hi and happy boxing day:
I am following by the letter the instructions in Sybex FundamentalsII book p.348 regarding an rman time based recovery. Here is the syntax:
RMAN> run {
2> allocate channel ch1 type disk;
3> set until time 'DEC 26 2007 10:30:00';
4> restore database;
5> recover database;
6> sql 'alter database open resetlogs';
7> }
and here is the error:
allocated channel: ch1
channel ch1: sid=11 devtype=DISK
executing command: SET until clause
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 12/26/2007 11:06:45
ORA-01858: a non-numeric character was found where a numeric was expected
Is this a format issue? Any tips please!
Thanks,
DAYou can only register a database once if you are using a recovery catalog, so whoever or whatever told you to re-register is simply getting their terminology in a knot!
There **is** a sort-of "re-register" command which does sometimes need to be issued after a resetlogs: it's called a RESET command. See http://tinyurl.com/29t5lr for details. A "reset" is, effectively, a "re-register".
One of the details you will see is that you only need to do a manual reset if it was **you** that issued a resetlogs, outside of RMAN. If you get RMAN to do the resetlogs, however, then there's no need to also issue the reset command, because RMAN already knows about it (and has already updated its own metadata accordingly).
The other thing you'll notice from the documentation is that if you aren't using a recovery catalog then the concept of issuing a reset is entirely redundant. That's because you can't recover to a prior incarnation of the database without a catalog: it's one of the main reasons for wanting to run in catalog mode in the first place. No catalog = no ability to step through incarnations = no need to inform RMAN that you're in a new incarnation. -
Help Educate Me on an RMAN Recovery Question
Perhaps I am not understanding how recovery should work, so, let me lay out my situation:
First things first:
Oracle 11.2.0.2.5 on AIX 6.1
Source database: POR02P on a 4 node cluster
Auxiliary database: POR02x (single instance)
I want to duplicate my source database to my auxiliary database as of 02-APR-2013 at 3:00PM
Here are how my backups run:
LEVEL0 On Sunday at 8:00 AM
LEVEL1 Differential all other days at 8:00 AM
Intermediate Archivelogs backups run at the following times daily: 00:45, 11:45, 19:45
March 31 is my LEVEL0.
So, the way I understand things, to do this duplicate:
I need my LEVEL0 from Sunday
I need my LEVEL1 from Monday
I need my LEVEL1 from Tuesday
I need all my archivelogs from just before the LEVEL1 on Tuesday started all the way to after 3:00PM on Tuesday:
Restore archive backups from:
4/2 11:45
4/2 19:45
All my backups include a controlfile.
According to my above analysis, I made sure the required files were on disk.
After making sure my files were on disk, I went to my source database and ran the following to make sure Oracle had all the files it needs:
RMAN> run {
2> set until time = "to_date('02-APR-2013 15:00:00','DD-MON-YYYY HH24:MI:SS')";
3> restore database preview summary;
4> }
This above command succeeds and I can verify all the files it mentions are on disk.
Here is the problem, the restore of the LEVEL0 and LEVEL1's succeed. When it starts recovery, it fails asking for an archive log that both:
*1. Was not listed as part of the PREVIEW command*
*2. Is from a time between my LEVEL0 and first LEVEL1.*
I was under the impression that RMAN does not need archivelogs from BETWEEN incremental backups.
Am I wrong about this?
Doesn't an incremental LEVEL1 differential go back to the last incremental and get all the needed blocks thereby making the "in between" archivelogs obsolete?
If I am wrong about this, that solves part of my confusion...
The other part of my confusion is why does the PREVIEW command not specify the archivelogs it asks for during recovery?
If you can answer my question now, you can skip the rest.
Else, here are all the dirty details.
Here is mt PREVIEW command as run on the source database. The output supports how I think this should work:
RMAN> run {
2> set until time = "to_date('02-APR-2013 15:00:00','DD-MON-YYYY HH24:MI:SS')";
3> restore database preview;
4> }
executing command: SET until clause
Starting restore at 23-APR-2013 13:47:30
using channel ORA_DISK_1
using channel ORA_DISK_2
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
11386312 Incr 0 105.12M DISK 00:00:23 31-MAR-2013 08:00:29
BP Key: 11386324 Status: AVAILABLE Compressed: YES Tag: LEVEL0
Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
List of Datafiles in backup set 11386312
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
3 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
4 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
5 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
6 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
9 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
14 0 Incr 15658251 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
BS Key Type LV Size Device Type Elapsed Time Completion Time
11613131 Incr 1 122.93M DISK 00:00:21 01-APR-2013 08:00:19
BP Key: 11613143 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f2o5vig5_1_1.BAK
List of Datafiles in backup set 11613131
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
3 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
4 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
5 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
6 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
9 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
14 1 Incr 16624714 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
BS Key Type LV Size Device Type Elapsed Time Completion Time
11784495 Incr 1 119.81M DISK 00:00:20 02-APR-2013 08:00:19
BP Key: 11784507 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK
List of Datafiles in backup set 11784495
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/system.258.810123295
3 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs1.260.810123303
4 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs2.261.810123315
5 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs3.262.810123315
6 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/undotbs4.263.810123317
9 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_orasdpm.274.810135793
14 1 Incr 17547965 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim_lob.281.810135799
BS Key Type LV Size Device Type Elapsed Time Completion Time
11386314 Incr 0 901.41M DISK 00:03:33 31-MAR-2013 08:03:38
BP Key: 11386326 Status: AVAILABLE Compressed: YES Tag: LEVEL0
Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
List of Datafiles in backup set 11386314
File LV Type Ckp SCN Ckp Time Name
2 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
7 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
8 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
10 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
11 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
12 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
13 0 Incr 15658225 31-MAR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
BS Key Type LV Size Device Type Elapsed Time Completion Time
11613133 Incr 1 77.77M DISK 00:00:36 01-APR-2013 08:00:41
BP Key: 11613145 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f1o5vig5_1_1.BAK
List of Datafiles in backup set 11613133
File LV Type Ckp SCN Ckp Time Name
2 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
7 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
8 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
10 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
11 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
12 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
13 1 Incr 16624711 01-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
BS Key Type LV Size Device Type Elapsed Time Completion Time
11784497 Incr 1 71.67M DISK 00:00:27 02-APR-2013 08:00:32
BP Key: 11784509 Status: AVAILABLE Compressed: YES Tag: LEVEL1D
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
List of Datafiles in backup set 11784497
File LV Type Ckp SCN Ckp Time Name
2 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/sysaux.259.810123299
7 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/users.264.810123317
8 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_mds.273.810135793
10 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_soainfra.275.810135795
11 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_oim.276.810135797
12 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_biplatform.277.810135797
13 1 Incr 17547912 02-APR-2013 08:00:06 +POR02P_DATA/por02p/datafile/lfgprod_ias_opss.278.810135797
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
11784501 60.89M DISK 00:00:09 02-APR-2013 08:00:53
BP Key: 11784513 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g1o626tc_1_1.BAK
List of Archived Logs in backup set 11784501
Thrd Seq Low SCN Low Time Next SCN Next Time
2 147 17279219 02-APR-2013 00:45:13 17549976 02-APR-2013 08:00:35
4 149 17279360 02-APR-2013 00:45:13 17549980 02-APR-2013 08:00:35
1 179 17279579 02-APR-2013 00:45:15 17549968 02-APR-2013 08:00:34
BS Key Size Device Type Elapsed Time Completion Time
11784499 26.99M DISK 00:00:04 02-APR-2013 08:00:48
BP Key: 11784511 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g2o626tc_1_1.BAK
List of Archived Logs in backup set 11784499
Thrd Seq Low SCN Low Time Next SCN Next Time
3 149 17279600 02-APR-2013 00:45:15 17549971 02-APR-2013 08:00:34
1 180 17549968 02-APR-2013 08:00:34 17549996 02-APR-2013 08:00:40
3 150 17549971 02-APR-2013 08:00:34 17549999 02-APR-2013 08:00:40
2 148 17549976 02-APR-2013 08:00:35 17550003 02-APR-2013 08:00:41
BS Key Size Device Type Elapsed Time Completion Time
11784500 2.00K DISK 00:00:01 02-APR-2013 08:00:52
BP Key: 11784512 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g3o626tj_1_1.BAK
List of Archived Logs in backup set 11784500
Thrd Seq Low SCN Low Time Next SCN Next Time
4 150 17549980 02-APR-2013 08:00:35 17550007 02-APR-2013 08:00:41
BS Key Size Device Type Elapsed Time Completion Time
11798434 28.77M DISK 00:00:05 02-APR-2013 11:45:28
BP Key: 11798442 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g7o62k2j_1_1.BAK
List of Archived Logs in backup set 11798434
Thrd Seq Low SCN Low Time Next SCN Next Time
1 181 17549996 02-APR-2013 08:00:40 17687415 02-APR-2013 11:45:05
3 151 17549999 02-APR-2013 08:00:40 17687418 02-APR-2013 11:45:05
BS Key Size Device Type Elapsed Time Completion Time
11798432 20.40M DISK 00:00:03 02-APR-2013 11:45:27
BP Key: 11798440 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g8o62k2k_1_1.BAK
List of Archived Logs in backup set 11798432
Thrd Seq Low SCN Low Time Next SCN Next Time
2 149 17550003 02-APR-2013 08:00:41 17687399 02-APR-2013 11:45:03
4 151 17550007 02-APR-2013 08:00:41 17687403 02-APR-2013 11:45:03
2 150 17687399 02-APR-2013 11:45:03 17688884 02-APR-2013 11:45:15
4 152 17687403 02-APR-2013 11:45:03 17688895 02-APR-2013 11:45:15
BS Key Size Device Type Elapsed Time Completion Time
11798433 66.00K DISK 00:00:00 02-APR-2013 11:45:27
BP Key: 11798441 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g9o62k2n_1_1.BAK
List of Archived Logs in backup set 11798433
Thrd Seq Low SCN Low Time Next SCN Next Time
1 182 17687415 02-APR-2013 11:45:05 17688871 02-APR-2013 11:45:14
3 152 17687418 02-APR-2013 11:45:05 17688875 02-APR-2013 11:45:14
BS Key Size Device Type Elapsed Time Completion Time
11834701 54.22M DISK 00:00:08 02-APR-2013 19:45:32
BP Key: 11834709 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_gdo63g6k_1_1.BAK
List of Archived Logs in backup set 11834701
Thrd Seq Low SCN Low Time Next SCN Next Time
1 183 17688871 02-APR-2013 11:45:14 17982647 02-APR-2013 19:45:04
3 153 17688875 02-APR-2013 11:45:14 17982641 02-APR-2013 19:45:04
BS Key Size Device Type Elapsed Time Completion Time
11834699 44.18M DISK 00:00:07 02-APR-2013 19:45:31
BP Key: 11834707 Status: AVAILABLE Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_geo63g6k_1_1.BAK
List of Archived Logs in backup set 11834699
Thrd Seq Low SCN Low Time Next SCN Next Time
2 151 17688884 02-APR-2013 11:45:15 17982650 02-APR-2013 19:45:04
4 153 17688895 02-APR-2013 11:45:15 17982653 02-APR-2013 19:45:04
Media recovery start SCN is 17547912
Recovery must be done beyond SCN 17548424 to clear datafile fuzziness
Finished restore at 23-APR-2013 13:47:32
Here is a summary of the files it lists:
Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f2o5vig5_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130401_f1o5vig5_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g1o626tc_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g2o626tc_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g3o626tj_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g7o62k2j_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g8o62k2k_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_g9o62k2n_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_gdo63g6k_1_1.BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130402_geo63g6k_1_1.BAK
Here is my list of files on disk. There are actually
more files listed here because the PREVIEW command does
not show pieces with Control/SPFILE backups:
-rw-r----- 1 oracle oinstall 945201152 Mar 31 08:03 POR02P_20130331_e5o5su45_1_1.BAK
-rw-r----- 1 oracle oinstall 110231552 Mar 31 08:00 POR02P_20130331_e6o5su46_1_1.BAK
-rw-r----- 1 oracle oinstall 1261568 Mar 31 08:00 POR02P_20130331_e7o5su4v_1_1.BAK
-rw-r----- 1 oracle oinstall 81559552 Apr 1 08:00 POR02P_20130401_f1o5vig5_1_1.BAK
-rw-r----- 1 oracle oinstall 128909312 Apr 1 08:00 POR02P_20130401_f2o5vig5_1_1.BAK
-rw-r----- 1 oracle oinstall 1277952 Apr 1 08:00 POR02P_20130401_f3o5vigv_1_1.BAK
-rw-r----- 1 oracle oinstall 75161600 Apr 2 08:00 POR02P_20130402_fto626s5_1_1.BAK
-rw-r----- 1 oracle oinstall 125640704 Apr 2 08:00 POR02P_20130402_fuo626s5_1_1.BAK
-rw-r----- 1 oracle oinstall 1294336 Apr 2 08:00 POR02P_20130402_fvo626su_1_1.BAK
-rw-r----- 1 oracle oinstall 63847936 Apr 2 08:00 POR02P_20130402_g1o626tc_1_1.BAK
-rw-r----- 1 oracle oinstall 28300800 Apr 2 08:00 POR02P_20130402_g2o626tc_1_1.BAK
-rw-r----- 1 oracle oinstall 2560 Apr 2 08:00 POR02P_20130402_g3o626tj_1_1.BAK
-rw-r----- 1 oracle oinstall 30164480 Apr 2 11:45 POR02P_20130402_g7o62k2j_1_1.BAK
-rw-r----- 1 oracle oinstall 21393920 Apr 2 11:45 POR02P_20130402_g8o62k2k_1_1.BAK
-rw-r----- 1 oracle oinstall 68096 Apr 2 11:45 POR02P_20130402_g9o62k2n_1_1.BAK
-rw-r----- 1 oracle oinstall 56855552 Apr 2 19:45 POR02P_20130402_gdo63g6k_1_1.BAK
-rw-r----- 1 oracle oinstall 46324224 Apr 2 19:45 POR02P_20130402_geo63g6k_1_1.BAK
-rw-r----- 1 oracle oinstall 3072 Apr 2 19:45 POR02P_20130402_gfo63g6r_1_1.BAK
Okay, so at this point, I think I have everything I need.
Here is my RMAN command:
# start up auxiliary in nomount
run {
allocate auxiliary channel a1 type disk;
allocate auxiliary channel a2 type disk;
allocate auxiliary channel a3 type disk;
allocate auxiliary channel a4 type disk;
set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
DUPLICATE DATABASE TO por02x
BACKUP LOCATION '/backup_rman/backupset/por02p'
NOFILENAMECHECK
LOGFILE
GROUP 1 ('+DB_REDO') SIZE 512M,
GROUP 2 ('+DB_REDO') SIZE 512M,
GROUP 3 ('+DB_REDO') SIZE 512M,
GROUP 4 ('+DB_REDO') SIZE 512M,
GROUP 5 ('+DB_REDO') SIZE 512M,
GROUP 6 ('+DB_REDO') SIZE 512M,
GROUP 7 ('+DB_REDO') SIZE 512M,
GROUP 8 ('+DB_REDO') SIZE 512M;
For now, I won't paste in the entire output of the log,
just enough to see that it works fine through the restore,
then fails at an archivelog. If someone wants the whole
thing, I can add it in:
RMAN> run {
2> allocate auxiliary channel a1 type disk;
3> allocate auxiliary channel a2 type disk;
4> allocate auxiliary channel a3 type disk;
5> allocate auxiliary channel a4 type disk;
6> set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
7> DUPLICATE DATABASE TO por02x
8> BACKUP LOCATION '/backup_rman/backupset/por02p'
9> NOFILENAMECHECK
10> LOGFILE
11> GROUP 1 ('+DB_REDO') SIZE 512M,
12> GROUP 2 ('+DB_REDO') SIZE 512M,
13> GROUP 3 ('+DB_REDO') SIZE 512M,
14> GROUP 4 ('+DB_REDO') SIZE 512M,
15> GROUP 5 ('+DB_REDO') SIZE 512M,
16> GROUP 6 ('+DB_REDO') SIZE 512M,
17> GROUP 7 ('+DB_REDO') SIZE 512M,
18> GROUP 8 ('+DB_REDO') SIZE 512M;
19> }
allocated channel: a1
channel a1: SID=49 device type=DISK
allocated channel: a2
channel a2: SID=98 device type=DISK
allocated channel: a3
channel a3: SID=146 device type=DISK
allocated channel: a4
channel a4: SID=194 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 23-APR-2013 14:22:07
contents of Memory Script:
sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
shutdown clone immediate;
startup clone nomount;
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 2137886720 bytes
Fixed Size 2221336 bytes
Variable Size 503319272 bytes
Database Buffers 1610612736 bytes
Redo Buffers 21733376 bytes
allocated channel: a1
channel a1: SID=98 device type=DISK
allocated channel: a2
channel a2: SID=146 device type=DISK
allocated channel: a3
channel a3: SID=194 device type=DISK
allocated channel: a4
channel a4: SID=242 device type=DISK
contents of Memory Script:
sql clone "alter system set db_name =
''POR02P'' comment=
''Modified by RMAN duplicate'' scope=spfile";
sql clone "alter system set db_unique_name =
''POR02X'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile from '/backup_rman/backupset/por02p/POR02P_20130331_e7o5su4v_1_1.BAK';
alter clone database mount;
executing Memory Script
sql statement: alter system set db_name = ''POR02P'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''POR02X'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 2137886720 bytes
Fixed Size 2221336 bytes
Variable Size 503319272 bytes
Database Buffers 1610612736 bytes
Redo Buffers 21733376 bytes
allocated channel: a1
channel a1: SID=98 device type=DISK
allocated channel: a2
channel a2: SID=146 device type=DISK
allocated channel: a3
channel a3: SID=194 device type=DISK
allocated channel: a4
channel a4: SID=242 device type=DISK
Starting restore at 23-APR-2013 14:23:02
channel a2: skipped, AUTOBACKUP already found
channel a3: skipped, AUTOBACKUP already found
channel a4: skipped, AUTOBACKUP already found
channel a1: restoring control file
channel a1: restore complete, elapsed time: 00:00:10
output file name=+POR02U_CTL/por02x/control01.ctl
Finished restore at 23-APR-2013 14:23:12
database mounted
channel a1: starting datafile backup set restore
channel a1: specifying datafile(s) to restore from backup set
channel a1: restoring datafile 00001 to +por02u_data
channel a1: restoring datafile 00003 to +por02u_data
channel a1: restoring datafile 00004 to +por02u_data
channel a1: restoring datafile 00005 to +por02u_data
channel a1: restoring datafile 00006 to +por02u_data
channel a1: restoring datafile 00009 to +por02u_data
channel a1: restoring datafile 00014 to +por02u_data
channel a1: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK
channel a2: starting datafile backup set restore
channel a2: specifying datafile(s) to restore from backup set
channel a2: restoring datafile 00002 to +por02u_data
channel a2: restoring datafile 00007 to +por02u_data
channel a2: restoring datafile 00008 to +por02u_data
channel a2: restoring datafile 00010 to +por02u_data
channel a2: restoring datafile 00011 to +por02u_data
channel a2: restoring datafile 00012 to +por02u_data
channel a2: restoring datafile 00013 to +por02u_data
channel a2: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK
channel a1: piece handle=/backup_rman/backupset/por02p/POR02P_20130331_e6o5su46_1_1.BAK tag=LEVEL0
channel a1: restored backup piece 1
channel a1: restore complete, elapsed time: 00:00:55
channel a2: piece handle=/backup_rman/backupset/por02p/POR02P_20130331_e5o5su45_1_1.BAK tag=LEVEL0
channel a2: restored backup piece 1
channel a2: restore complete, elapsed time: 00:05:05
Finished restore at 23-APR-2013 14:28:24
channel a2: reading from backup piece /backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK
channel a1: piece handle=/backup_rman/backupset/por02p/POR02P_20130402_fuo626s5_1_1.BAK tag=LEVEL1D
channel a1: restored backup piece 1
channel a1: restore complete, elapsed time: 00:00:35
channel a2: piece handle=/backup_rman/backupset/por02p/POR02P_20130402_fto626s5_1_1.BAK tag=LEVEL1D
channel a2: restored backup piece 1
channel a2: restore complete, elapsed time: 00:00:35
starting media recovery
unable to find archived log
archived log thread=1 sequence=163
released channel: a1
released channel: a2
released channel: a3
released channel: a4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/23/2013 14:29:41
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 163 and starting SCN of 15660537
RMAN> **end-of-file**
So, if I go back to my source:
RMAN> list backup of archivelog sequence 163 thread 1;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
11386318 66.51M DISK 00:00:09 31-MAR-2013 08:04:08
BP Key: 11386330 Status: EXPIRED Compressed: YES Tag: ARCHIVE_BAK
Piece Name: /backup_rman/backupset/por02p/POR02P_20130331_e9o5subf_1_1.BAK
List of Archived Logs in backup set 11386318
Thrd Seq Low SCN Low Time Next SCN Next Time
1 163 15336390 31-MAR-2013 00:45:14 15661283 31-MAR-2013 08:03:51
The archivelog is not reported as part of the preview
command. Also, shouldn't it's changes be included in
the next day's LEVEL1?
Thanks for anyone's time. Would be happy to provide
more info.Levi,
Thank you very much for your insight.
However, I may have found something. I have not fully tested and found a solution so I have not posted an update yet...I want to make sure I have a complete answer. However, I will provide some details.
I decided to go ahead and restore ALL my archivelogs just to see if I could get the recovery to work.
It still did not work!
So, I happened to look at my alert log (can't believe I did not check it before) and I saw this:
Wed Apr 24 13:34:20 2013
Errors with log +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241
Recovery interrupted!
Recovered data files to a consistent state at change 17574527
Media Recovery failed with error 19755
Errors in file /opt/app/oracle/diag/rdbms/por02x/por02x/trace/por02x_pr00_2973744.trc:
ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '+POR02P_DATA/por02p/changetracking/ctf.272.810127579'
ORA-17503: ksfdopn:2 Failed to open file +POR02P_DATA/por02p/changetracking/ctf.272.810127579
ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
Slave exiting with ORA-283 exception
Errors in file /opt/app/oracle/diag/rdbms/por02x/por02x/trace/por02x_pr00_2973744.trc:
ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '+POR02P_DATA/por02p/changetracking/ctf.272.810127579'
ORA-17503: ksfdopn:2 Failed to open file +POR02P_DATA/por02p/changetracking/ctf.272.810127579
ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
ORA-15001: diskgroup "POR02P_DATA" does not exist or is not mounted
ORA-10877 signalled during: alter database recover logfile '+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241'...
Then, I looked on Metalink and found this:
Oracle Support Document 1098638.1 (Rman Duplicate fail ORA-19755, Tries Open The Block Change Tracking File of Source DB) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1098638.1
[https://support.oracle.com/epmos/faces/DocumentDisplay?id=1098638.1]
Now, this document is very interesting within the context of the problem I am having. However, it says a few things:
1. This is fixed in the oracle patchset 11.2.0.2 as part of Bug 7500916.
---I am on patchset 11.2.0.2!
2. The workaround is to disable change tracking before duplicate.
---this is not really an option for me...we like having this turned on...it considerably speeds up our backups
3. Workaround is to set DB_FILE_NAME_CONVERT in the SET-clause of duplicate, instead of using DB_FILE_NAME_CONVERT setting in an init.ora or spfile.
---tried this...did not work
4. Workaround is to create a dummy file in the location where the error ORA-19755 is signalled.
---have not tried this yet
Another interesting thing to note:
My database is left in mounted state when it fails. After seeing this document, just for fun I:
SQL> alter database disable block change tracking;
Database altered.
And Then:
RMAN> run {
2> set until time = "to_date('02-APR-2013:15:00:00','DD-MON-YYYY:HH24:MI:SS')";
3> recover database;
4> }
executing command: SET until clause
Starting recover at 24-APR-2013 14:20:20
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=98 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=146 device type=DISK
starting media recovery
archived log for thread 1 with sequence 181 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_181.7864.813591241
archived log for thread 1 with sequence 182 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_182.2358.813591247
archived log for thread 1 with sequence 183 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_183.3637.813591249
archived log for thread 2 with sequence 149 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_149.9547.813591241
archived log for thread 2 with sequence 150 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_150.9570.813591241
archived log for thread 2 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_151.6148.813591247
archived log for thread 3 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_151.9630.813591239
archived log for thread 3 with sequence 152 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_152.4418.813591247
archived log for thread 3 with sequence 153 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_153.9782.813591247
archived log for thread 4 with sequence 151 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241
archived log for thread 4 with sequence 152 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_152.6936.813591241
archived log for thread 4 with sequence 153 is already on disk as file +DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_153.9610.813591249
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_151.7352.813591241 thread=4 sequence=151
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_181.7864.813591241 thread=1 sequence=181
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_149.9547.813591241 thread=2 sequence=149
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_151.9630.813591239 thread=3 sequence=151
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_150.9570.813591241 thread=2 sequence=150
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_152.6936.813591241 thread=4 sequence=152
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_182.2358.813591247 thread=1 sequence=182
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_152.4418.813591247 thread=3 sequence=152
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_1_seq_183.3637.813591249 thread=1 sequence=183
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_3_seq_153.9782.813591247 thread=3 sequence=153
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_2_seq_151.6148.813591247 thread=2 sequence=151
archived log file name=+DB_ARCH/por02x/archivelog/2013_04_24/thread_4_seq_153.9610.813591249 thread=4 sequence=153
media recovery complete, elapsed time: 00:00:08
Finished recover at 24-APR-2013 14:20:36
So, it finishes the recovery. However, I did not yet try to open resetlogs because this was originally a duplicate and doing an open resetlogs would not complete all the post-duplicate operations.
Also, looking at the logs applied when running the above recover, now it only uses logs that were specified in the original PREVIEW command.
I am going to play around some more and I promise I will post back with whatever results I happen across.
Chris.. -
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
Maybe you are looking for
-
Sharing music from iTunes on an Xserve to new MacPro Desktop + MacBook Air
Hello all, Have a question here regarding sharing a central iTunes playlist/XServe and also enabling the functionality to add music to that XServe library remotely Current Setup: -- Mac XServe running iTunes 24x7, sharing one playlist containing enti
-
Hello, I installed the update to OS X 10.9.1 and ran into problems: opening the Mail app took me more than ten attempts, where the app would crash due to some proble with "Open CL". Same with Messages. After restarting, the desktop started flashing b
-
If I purchase dreamweavers one month subscription will I only be billed once?
I only need dreamweaver for 1 month.
-
I am trying to render my 3d text in after effects cs6 but when I click render, suddenly after effects starts using up 90% of my cpu which causes my computer to crash with an incomplete render. I have set my ray traced renderer quality to as low as 3
-
OS X update, now getting error while rendering
I was working on a major project last week, everything was swell. No problems. This morning I needed to make a couple of minor changes to a lower third graphic over video and I could not render. I get a box with this message: "Video Preview Error E