RMAN Restore Error - media recovery requesting unknown log: thread 1 seq 7
Im using RMAN to copy a database to another server. The new server is IDENTICAL to the old one. By identical I mean it has the same sever name, ip address, operating system, Oracle version and directory structure.
The new server already has the instance created, (same name as the old server instance, paths etc)
The backup files have been manually restored to the new server, same locations as they were on the old one. ( RMAN did an automatic controlfile backup and also the archivelogs on the old server ).
Ive restored the control file on the new server from the RMAN backup pieces.
Ive catalogued the RMAN backup pieces on the new server.
I know the last sequence available in the archivelogs backup by running on the new server :
list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
5 14.43M DISK 00:00:03 11-MAY-11
BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163502
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163502_6WOC5833_.BKP
List of Archived Logs in backup set 5
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 550217 10-MAY-11 556559 11-MAY-11
1 3 556559 11-MAY-11 559776 11-MAY-11
1 4 559776 11-MAY-11 560093 11-MAY-11
1 5 560093 11-MAY-11 560794 11-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
7 15.50K DISK 00:00:01 11-MAY-11
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163653
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
List of Archived Logs in backup set 7
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 560794 11-MAY-11 560851 11-MAY-11
So far its all going swimmingly well.
Now I want to restore the datafiles and recover. So I ran :
RMAN run { restore database; recover database; alter database open resetlogs; }
This gave me the output below which goes great but I get a final error, I think the error is because its looking for an archive log thats not in the backup set, but it should be. However, I think SCN 560851 is for a log that hadnt been created yet on the old server when the backup was ran ?
How do I address resolving the error ? Its worth pointing out log, "archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741" isnt on the old server either which is why its not in the backup set.
I can do a alter database open reset logs but Id prefer to know why its failing.
Any help would be much appreciated.
RMAN> run { restore database; recover database; alter database open resetlogs; }
Starting restore at 11-MAY-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 C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSTEM01.DBF
restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\UNDOTBS01.DBF
restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSAUX01.DBF
restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\USERS01.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP tag=TAG20110511T163507
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 11-MAY-11
Starting recover at 11-MAY-11
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=6
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP tag=TAG20110511T163653
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC thread=1 sequence=6
channel default: deleting archive log(s)
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741
unable to find archive log
archive log thread=1 sequence=7
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/11/2011 18:15:42
RMAN-06054: media recovery requesting unknown log: thread 1 seq 7 lowscn 560851
RMAN>
Edited by: user12173666 on 11-May-2011 10:28
You need to do incomplete recovery i.e. to ask RMAN to restore/recover to some specific point in time. This is usually done with some UNTIL clause or SET UNTIL statement. Example in your case:
SET UNTIL SEQUENCE 7;See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta065.htm#RCMRF160.
Similar Messages
-
RMAN-06054: media recovery requesting unknown log: thread 1 seq 300 lowscn
Got it dropped and recretaed - dont know why didnt work
Edited by: user3489571 on 14-Apr-2010 18:46The ALTER DATABASE REGISTER LOGFILE command in SQLPlus is for Standby and Streams implementation.
You should be using the CATALOG command in RMAN. -
RMAN-06054: media recovery requesting unknown archived log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
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 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve thisIn addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
Edited by: user11989003 on May 29, 2013 10:17 AM -
Standby media recovery waiting for inactive thread
Hi,
Please let me know any idea on this scenario. Thanks.
Environment:
Oracle 11.2.0.2
primary: 3 node RAC
standby: 3 node RAC
Problem:
there is thread 5 (not registered instance or did not show in srvctl) that generates archivelog. but the lag apply stopped because of this when the instance (of thread 5) is shutdown.
question: somehow an instance is registered in the cluster but in srvctl only 3 instance is running. it should have 4 instance but 1 is not running. How can I remove the thread 5 so when someone startup then shutdown instance#4 it will not create archivelog that will stopped the apply of archivelog in standby.
note: this is perf environment server so someone and "other" DBA is accessing this environment which I am not aware what are they doing with the cluster.
looking in alert log file: - it is waiting for thread 5 sequence 510. But the instance is down so log is not shipped to standby database and this resulted to lag in other threads.
Sat Aug 03 18:54:47 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
THREAD# LAST_SEQ_RECEIVED LAST_SEQ_APPLIED
1 13745 13717
2 17728 17664
3 15527 15464
5 509 509
what I did is:
1. primary (asm copy to file system)
2. scp primary to standby
3. standby (file system copy to asm)
4. rman target / -> catalog archivelog <thread 5 sequence 510)
5. then looking into alert log file; it performed media recovery
Sat Aug 03 23:03:13 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
Sat Aug 03 23:15:21 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_5_seq_510
Sat Aug 03 23:15:32 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15466.10925.822316315
Sat Aug 03 23:17:18 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17666.853.822333143
Sat Aug 03 23:18:39 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15467.834.822333553
Sat Aug 03 23:20:54 2013in Standby, thread 4 and 5 are both UNUSED, and size is incorrect (not equal to other redo log). I want to recreate it but cannot drop redo log. I follow Doc ID 740675.1.
any idea what are the missing steps? thanks.
ORA-01624: needed for crash recovery of instance UNNAMED_INSTANCE_5 (thread 5)
select group#,thread#,archived,status,bytes from v$log;
primary DB:
GROUP# THREAD# ARC STATUS BYTES
1 1 YES INACTIVE 1073741824
2 1 YES INACTIVE 1073741824
3 2 NO CURRENT 1073741824
4 2 YES INACTIVE 1073741824
5 3 YES INACTIVE 1073741824
6 3 YES INACTIVE 1073741824
7 2 YES INACTIVE 1073741824
8 1 NO CURRENT 1073741824
9 3 NO CURRENT 1073741824
10 4 YES INACTIVE 1073741824
11 4 NO CURRENT 1073741824
GROUP# THREAD# ARC STATUS BYTES
12 4 YES INACTIVE 1073741824
13 5 YES INACTIVE 1073741824
14 5 YES INACTIVE 1073741824
15 5 NO CURRENT 1073741824
standby DB:
GROUP# THREAD# ARC STATUS BYTES
1 1 YES INACTIVE 1073741824
2 1 YES INACTIVE 1073741824
3 2 NO CURRENT 1073741824
4 2 YES INACTIVE 1073741824
5 3 YES INACTIVE 1073741824
6 3 YES INACTIVE 1073741824
7 2 YES INACTIVE 1073741824
8 1 NO CURRENT 1073741824
9 3 NO CURRENT 1073741824
10 4 YES INACTIVE 1073741824
11 4 NO CURRENT 1073741824
GROUP# THREAD# ARC STATUS BYTES
12 4 YES INACTIVE 1073741824
13 5 YES INACTIVE 1073741824
14 5 YES INACTIVE 1073741824
15 5 NO CURRENT 1073741824 -
RMAN Restore on Test DB Fails - ORA-01152:file 1 was not restored from blah
Calling all RMAN Gurus!
I'm having trouble recovering an RMAN backup on my test DB server. Please Help!
Solaris 10/Oracle 10.2.0.4 Standard Edition (Both Servers)
Part one - Step by Step
Primary Server
1. Perform full backup: backup database plus archivelog;
2. Copy Backupset & Controlfile to test server: "RSYNC/NFS Mount"
Test Server
1. rman target /
2. startup nomount;
3. restore controlfile blah blah
4. alter database mount;
5. catalog backuppiece
6. restore database; - no issues
*7. recover database noredo; - no issues*
*8. alter database open resetlogs;*
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/09/2009 08:48:22
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/data/oracle/oradata/planodb/system01.dbf'
All is good until I try and open the database. What am I missing?? Why doesn't this work???
Because .... If I go through the exact steps but I perform a "recover database" instead of "recover database noredo", I can open the database!!!
Example :
6. restore database; no issues
7. recover database;
Starting recover at 09-SEP-09
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=34
channel ORA_DISK_1: reading from backup piece /data/oracle/orabase/backup/backup
set/2009_09_09/o1_mf_annnn_BACKUP_PLANODB_000_0_5bgkffqq_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/data/oracle/orabase/backup/backupset/2009_09_09/o1_mf_annnn_BACKUP
PLANODB000_0_5bgkffqq_.bkp tag=BACKUP_PLANODB_000_090909010005*
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
archive log filename=/data/oracle/oradata/arch/PLANODB/archivelog/2009_09_09/o1_
mf_1_34_5bhdkwd4_.arc thread=1 sequence=34
channel default: deleting archive log(s)
archive log filename=/data/oracle/oradata/arch/PLANODB/archivelog/2009_09_09/o1_
mf_1_34_5bhdkwd4_.arc recid=42 stamp=697106925
unable to find archive log
archive log thread=1 sequence=35
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/09/2009 08:48:52
RMAN-06054: media recovery requesting unknown log: thread 1 seq 35 lowscn 1425007
This is ok because seq 35 doesn't actually exist!
8. alter database open resetlogs;
database opened!You could also explore the UNTIL clause of the RECOVER DATABASE command to specify Recovery until a specific Log, SCN or Timestamp.
Since you are cloning a Hot Backup to another server the Recovery has to be an Incomplete Recovery. So, it will be to a Log, SCN or Timestamp -- either of which you could also explicitly specify with the UNTIL clause.
Hemant K Chitale
http://hemantoracledba.blogspot.com -
first, i backup all datafiles. then i delete the datafile of system tablesapce.
then i recover database by recovery manager. it makes these errors.i do not
how slove it.i nees help,i will thank ereryone who help me
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
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-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06054: media recovery requesting unknown log: thread 1 scn 1869941
nullWhy don't review your syntax of your recover statements? Maybe there're some surprises waiting for you.
-
Error installing recovery catalog
Hi,
Inorder to implement RMAN in oracle 10g in windows environment I created a separate table space for rman and created a user as rman1;
then I issued the following commands :
GRANT connect, resource, recovery_catalog_owner TO rman1
grant create session to rman1;
grant create type to rman1;
then i entered into rman from dos prompt,
rman catalog=rman1/rman1@tc
from rman prompt I issued the command,
create catalog tablespace RMAN1;
then the following error occurs,
RMAN> create catalog tablespace RMAN1;
ORACLE error from recovery catalog database: ORA-01031: insufficient privileges
RMAN-00571: ====================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ====================================
RMAN-06433: error installing recovery catalog
Due to this error I am unable to proceed further and let me know the solution.
Thanks in advance.
Regards,
A.Mohammed Rafi.Hi,
Thanks for the help and the problem is solved.
Now I am facing another problem,
RMAN-03009: failure of catalog command on default channel
ORA-19657: cannot inspect current datafile D:\ORACLE\PRODUCT\10.1.0\DB_2\TC\EXAMPLE01.DBF
Could you please help me in this regard. -
my iphone says an unknown error occurred (9) when trying to restore in iphone recovery mode
Hey there ejs11201,
I see that you are getting an error code when attempting to restore your iPhone. Here is an article that addresses that specific code with some troubleshooting steps and will help you resolve the issue:
Check your security software
Related errors: 2, 4, 6, 9, 1611, 9006. Sometimes security software can stop your device from communicating with either the Apple update server or with your device.
Check your security software and settings to make sure that they aren't blocking a connection to the Apple servers.
Get help with iOS update and restore errors - Apple Support
https://support.apple.com/en-gb/TS3694
Thanks for coming to the Apple Support Communities!
Regards,
Braden -
Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AMThis Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete. -
Hi Guys,
10.2.0.4
Scenario:
DELETED: REDO LOGS, ARCHIVE LOGS, DATAFILES
STILL IN PLACE: CURRENT CONTROLFILES, INIT FILE
If I have my current controlfiles with me but no re-do logs, I won't be able to use the controlfiles for recovery right as it won't be able to find the redo logs? I still have to restore the controfile from the database or use the create controlfile statement?
Please advise.
thanksHi Guys,
After i startup mount the database. I did a restore database followed by recover database. However, there's error as below:
RMAN> run
2> {
3> allocate channel c1 type disk;
4> recover database;
5> }
allocated channel: c1
channel c1: sid=157 devtype=DISK
Starting recover at 24-JAN-11
starting media recovery
media recovery failed
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/24/2011 18:54:46
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\REDO0
2.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
thanks -
Media Recovery failed with error 1111
Hi,
on 10g R2 on Unix I have :
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
Fri Jun 24 10:56:52 2011
Media Recovery failed with error 1111
From alert.log :
Errors in file /data01/oracle/mydb/admin/bdump/hhhh_17637.trc:
ORA-01111: name for data file 523 is unknown - rename to correct file
ORA-01110: data file 523: '/oracle/product/10g/db_1/dbs/UNNAMED00523'
ORA-01157: cannot identify/lock data file 523 - see DBWR trace file
ORA-01111: name for data file 523 is unknown - rename to correct file
ORA-01110: data file 523: /oracle/product/10g/db_1/dbs/UNNAMED00523'
Any idea ?
Thanks.here is one test case, i ran into same issue. and reolved as below.
When Standby_file_management is set to “MANUAL” , if any data files added on primary database, These changes certainly won’t be altered in standby database.
After starting MRP process, it dies and terminated with the following errors.
Errors from Alert log file:-
Errors in file /oracle/app/oracle/admin/CC/bdump/cc_mrp0_22294.trc:
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
Errors from Trace file:-
MRP0: Background Media Recovery terminated with error 1111
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ARCH: Connecting to console port...
Check out from SQL, Which files need to be recovered on standby database?
SQL> select * from v$recover_file where error like '%FILE%';
FILE# ONLINE ONLINE_ ERROR CHANGE# TIME
+536 ONLINE ONLINE FILE MISSING 0+
SQL>
On Primary check out for actual naming convention:-
SQL> select file#,name from v$datafile where file#=536;
FILE# NAME
+536 DATA/c/datafile/undotbs9.595.750444337
SQL>
On Standby check datafile name:-
SQL> select file#,name from v$datafile where file#=536;
FILE# NAME
+536 /oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536+
SQL>
Make sure still standby_file_management is set to “MANUAL”, After performing media recovery again can be enabled to “AUTO”.
Rename datafile from standby database:-
SQL> alter database create datafile '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536' as 'DATA3/cc/datafile/undotbs9_595_750444337';+
Database altered.
Start the MRP Now:-
SQL> alter database recover managed standby database disconnect from session;
Database altered.
After creating the file, MRP will start applying archives on standby database. -
Block corruptioin after rman restore/recovery
Thanks for taking my question!
Oracle Enterprise Edition 11.1.0.7 on Windows 2008. Using Rman on-line backups COMPRESSED.
Can anyone give me any ideas on why SYSAUX data block corruption should occur after a rman recovery?
Below is my script. Am I missing something? Should I be physically removing the redo? Any ideas welcome?
Thanks!
Kathie
rman> restore until seq = 123
recover until seq = 123
alter database open resetlogs;
Background:
I had to do a rman recovery the other day to restore our database back to the previous day. After the recovery the sysaux table became logically corrupted. I tried to fix data corruption with rman but it said it couldn't after reading thru 6 days of backups. I ended up deleting the database, recreating the database and restoring from an export takien a few hours prior.
I now have a database to test rman recovery. Database has been up and rman backups (compressed) running for several days. I tried to recover back to previouse day and again SYSAUX has logical corruption. I tried to use Rman to recover data corruption but it failed.
I deleted database and recreated it. Took several rman on-line backups (this time not compressed). Did 3rd recovery this time only a few hours back. This time everything worked - no sysaux block corruption but why? The only difference is the recovery used non compressed backups and recovery was a shorter time frame. why ???I agree the errors are not identical but I am going to stop performing compressed backups until I am sure that is not the issue.
My first two recoveries had logical block corruption and this last one without compression set had no block corruption. I performed the same recovery process for all recoveries and the big difference was the successfull recovery did not have compressed backups. I checked v$database_block_corruption and it shows no errors. I also, performed a backup and verify to double check.
The only issue I can see is below. I am hoping someone can confirm this is normal after "alter database open resetlogs". Can anyone verify that?
Thanks!
Kathie
Thu Aug 27 10:17:49 2009
alter database open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 3587892
Resetting resetlogs activation ID 3129052671 (0xba818dff)
Thu Aug 27 10:17:50 2009
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO01.LOG'
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 2 of thread 1, type 0 in header is not log file
ORA-00312: online log 2 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO02.LOG'
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO03.LOG'
Thu Aug 27 10:17:53 2009
Setting recovery target incarnation to 3 -
RMAN-06172 error when restoring to a DR system
Hello,
I am not a trained DBA, I only have some basic understandings and what I can figure out from the manuals and googling.
I have a production 10G R2 database, on Red Hat 5, that I backup using Backup Exec 2010.
I perform weekly live Full backups followed by 6 days of incrementals. I also perform a month offline backup once a month.
Archive logs are used.
RMAN setting are at the default.
In getting my Disaster Recover site up and tested I performed a restore of the cold last coldl backup and a live full.
Both where successful except for a minor issue that was fixed with restoring the Archive logs
recently I was testing my procedures again and ran into this error
RMAN-03002
RMAN-06172
I have attempted to research this issue but I am having issues understanding what I need to do?
I have looked into these MetaLink articles 351826.1, 735115.1, 369680.1, 274237.1, 261426.1, 292835.1
I am confused as to why I was able to restore one full live backup but not the next one.
Thank you for any insight you can give.Here is the RMAN log from one of the restore attempts.
All restores are done as if the production server had been lost and I had only the tapes to restore with.
===========================================================
# RMAN command section
RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND 'BSA_SERVICE_HOST=10.1.1.35,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={C5D98C8E-5E64-4587-97EB-DDD9351E13B5},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\server.domain\SID';
RESTORE CONTROLFILE FROM 'BE_bulsuqdc_1_1';
RELEASE CHANNEL ch0;
connected to target database: webct (not mounted)
using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: sid=483 devtype=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0
sent command to channel: ch0
Starting restore at 22-NOV-10
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/22/2010 15:00:16
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Recovery Manager complete.
===========================================================
Thanks,
William -
Media Recovery failed with error 368
The following error occurs on standby database---
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log x.0000008973.arc
Recovery interrupted.
Redo code 6 enountered during in-flux buffer recovery
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
some error occurred during recovering in-flux buffers
Recovered data files restored to a consistent state at change 138445558.
Media Recovery failed with error 368
Please advice. Thanks in advanceHere you have the complete reference for the command
that you executed :
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_15a.htm#SQLRF00802
[email protected]
Joel P�rez -
Hi,
Db :11.2.0.1
Os : Aix 6
we are doing refresh from production to test server using rman.We started instance and restored the control file.
we got the following error when execute restore script.
MAN> connect target *
2> RUN
3> {
4> allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_iit6.opt)';
5> allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_iit6.opt)';
6> allocate channel t3 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_iit6.opt)';
7> allocate channel t4 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_iit6.opt)';
8> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/system01.dbf' TO '+P7_DATAGROUP01/P7/system01.dbf';
9> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/sysaux01.dbf' TO '+P7_DATAGROUP01/P7/sysaux01.dbf';
10> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/undotbs01.dbf' TO '+P7_DATAGROUP01/P7/undotbs01.dbf';
11> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/users01.dbf' TO '+P7_DATAGROUP01/P7/users01.dbf';
12> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/tools01.dbf' TO '+P7_DATAGROUP01/P7/tools01.dbf';
13> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/two_kb_tbs.dbf' TO '+P7_DATAGROUP01/P7/two_kb_tbs.dbf';
14> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/wwfdata01.dbf' TO '+P7_DATAGROUP01/P7/wwfdata01.dbf';
15> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/wwfindex01.dbf' TO '+P7_DATAGROUP01/P7/wwfindex01.dbf';
16> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/ntwksdata01.dbf' TO '+P7_DATAGROUP01/P7/ntwksdata01.dbf';
17> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/ntwksindex01.dbf' TO '+P7_DATAGROUP01/P7/ntwksindex01.dbf';
18> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/emadata01.dbf' TO '+P7_DATAGROUP01/P7/emadata01.dbf';
19> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/emaindex01.dbf' TO '+P7_DATAGROUP01/P7/emaindex01.dbf';
20> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/scpodata01.dbf' TO '+P7_DATAGROUP01/P7/scpodata01.dbf';
21> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/scpoindex01.dbf' TO '+P7_DATAGROUP01/P7/scpoindex01.dbf';
22> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/igpdata01.dbf' TO '+P7_DATAGROUP01/P7/igpdata01.dbf';
23> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/ikeadata01.dbf' TO '+P7_DATAGROUP01/P7/ikeadata01.dbf';
24> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/ikeaindex01.dbf' TO '+P7_DATAGROUP01/P7/ikeaindex01.dbf';
25> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/fedata01.dbf' TO '+P7_DATAGROUP01/P7/fedata01.dbf';
26> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/indx01.dbf' TO '+P7_DATAGROUP01/P7/indx01.dbf';
27> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/prefstat01.dbf' TO '+P7_DATAGROUP01/P7/prefstat01.dbf';
28> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/support01.dbf' TO '+P7_DATAGROUP01/P7/support01.dbf';
29> SET NEWNAME FOR DATAFILE '+IIT6_DATAGROUP01/iit6/tmpscpix01.dbf' TO '+P7_DATAGROUP01/P7/tmpscpix01.dbf';
30> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01a.log'' TO ''+P7_REDOGROUP01/P7/redo01a.log'' ";
31> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo02a.log'' TO ''+P7_REDOGROUP01/P7/redo02a.log'' ";
32> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo03a.log'' TO ''+P7_REDOGROUP01/P7/redo03a.log'' ";
33> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01b.log'' TO ''+P7_REDOGROUP01/P7/redo01b.log'' ";
34> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo02b.log'' TO ''+P7_REDOGROUP01/P7/redo02b.log'' ";
35> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo03b.log'' TO ''+P7_REDOGROUP01/P7/redo03b.log'' ";
36> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo04a.log'' TO ''+P7_REDOGROUP01/P7/redo04a.log'' ";
37> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo04b.log'' TO ''+P7_REDOGROUP01/P7/redo04b.log'' ";
38> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo05a.log'' TO ''+P7_REDOGROUP01/P7/redo05a.log'' ";
39> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo05b.log'' TO ''+P7_REDOGROUP01/P7/redo05b.log'' ";
40> RESTORE DATABASE until time "to_date('2012-10:28-11:15:40','YYYY-MM-DD-HH24:MI:SS')";
41> SWITCH DATAFILE ALL;
42> release channel t1;
43> release channel t2;
44> release channel t3;
45> release channel t4;
46> }
47>
connected to target database: iit6 (DBID=3947283088, not open)
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=4975 device type=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.5.2.1
allocated channel: t2
channel t2: SID=5427 device type=SBT_TAPE
channel t2: Data Protection for Oracle: version 5.5.2.1
allocated channel: t3
channel t3: SID=5879 device type=SBT_TAPE
channel t3: Data Protection for Oracle: version 5.5.2.1
allocated channel: t4
channel t4: SID=6331 device type=SBT_TAPE
channel t4: Data Protection for Oracle: version 5.5.2.1
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
sql statement: ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01a.log'' TO ''+P7_REDOGROUP01/P7/redo01a.log''
sql statement: ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo02a.log'' TO ''+P7_REDOGROUP01/P7/redo02a.log''
sql statement: ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo03a.log'' TO ''+P7_REDOGROUP01/P7/redo03a.log''
sql statement: ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01b.log'' TO ''+P7_REDOGROUP01/P7/redo01b.log''
released channel: t1
released channel: t2
released channel: t3
released channel: t4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/28/2012 12:47:47
RMAN-11003: failure during parse/execution of SQL statement: ALTER DATABASE RENAME FILE '+IIT6_REDOGROUP01/iit6/redo01b.log' TO '+P7_REDOGROUP01/P7/redo01b.log'
ORA-01511: error in renaming log/data files
ORA-01516: nonexistent log file, data file, or temporary file "+IIT6_REDOGROUP01/iit6/redo01b.log"
Recovery Manager complete.
we have the following data group in target machine.
P7_ARCHGROUP01/
P7_DATAGROUP01/
P7_REDOGROUP01/
P7_REDOGROUP02/
Any suggestions.
Thanks30> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01a.log'' TO ''+P7_REDOGROUP01/P7/redo01a.log'' ";
31> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo02a.log'' TO ''+P7_REDOGROUP01/P7/redo02a.log'' ";
32> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo03a.log'' TO ''+P7_REDOGROUP01/P7/redo03a.log'' ";
33> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo01b.log'' TO ''+P7_REDOGROUP01/P7/redo01b.log'' ";
34> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo02b.log'' TO ''+P7_REDOGROUP01/P7/redo02b.log'' ";
35> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo03b.log'' TO ''+P7_REDOGROUP01/P7/redo03b.log'' ";
36> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo04a.log'' TO ''+P7_REDOGROUP01/P7/redo04a.log'' ";
37> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo04b.log'' TO ''+P7_REDOGROUP01/P7/redo04b.log'' ";
38> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo05a.log'' TO ''+P7_REDOGROUP01/P7/redo05a.log'' ";
39> SQL "ALTER DATABASE RENAME FILE ''+IIT6_REDOGROUP01/iit6/redo05b.log'' TO ''+P7_REDOGROUP01/P7/redo05b.log'' ";Check v$logfile and see the location of the member and use
SQL>ALTER DATABASE RENAME FILE '<old path>' TO 'new path';after do this comment the above lines and run script again .
Maybe you are looking for
-
HT1212 i cant restart my ipad so could u tell me how to
i cant restart my ipad could u tell me how
-
HT1414 will the ipod touch 4g be able to support siri with an update
will the ipod touch 4g support siri with an update?
-
GRC 5.3 CUP auto provisioning of Mitigation Assignment in RAR
Hello, Is there any other workflow that needs to be triggered for the auto provisioning of the Mitigation control id assignment to the userid in RAR system from CUP, upon request completion? I created a request that after the final stage of sox appr
-
I have a side-by-side bar chart with three series. Two of the series are represented by risers and the third series is a line showing the percent difference between the first two series. There are two y axes. The 2nd's y axis shows the third serie
-
How to install NetBeans6.5 in Solaris
Hi All, I am new to the forum and this is my first question. I have installed NetBeans 6.5 in windows system. But my source code is in Solaris can be accessed using clearCase vobs.I have two questions to ask:- 1. How to install NetBeans 6.5 in Solari