RMAN Qn
While opening database with resetlogs option got error
ORA - 01152 : File 1 was not restored from sufficiently old backup
ORA - 01110 : Data file 1: 'usr3/ oracle/.../system01.dbf'
Looks like I need to recover database from old backups.
How do I instruct RMAN to use previous backups instead of current ones.
Your help is much appreciated. Thanks
You didn't tell us the database version, hopefully you are already on 10g, because recovery through resetlogs is tricky for earlier versions, especially if you don't have a recovery catalog. This document describes the harder way:
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrecov.htm#1007678
This is for 10g:
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen004.htm#sthref1856
Similar Messages
-
How can i do a RMAN backup of my database from the network ?
i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus -
Issue in configuring Standby Database from Active database in 11g by RMAN
POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PMHello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg -
Issue in creating the standby database from Active database using RMAN
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN
-
Dear friends,
Is it passible that we take logical backup(i.e Export/Impot)
in Rman.
If yes then.
Why?
[email protected]Pixels.
For a 1" x 1" photo first crop the photo square. Then export with Kind = Current with JPEF Quality = Maximum and Size = Full size.
Then when you go to print the photo select a 1" x 1" print size. This will squeeze all available pixels in each dimension into the 1" dimension giving you the highest DPI resolution available from your image file.
More about DPI can be found here: All About Digital Photos - The Arithmetic of DPI and All About Digital Photos - The Myth of DPI
OT -
Can not recover table from rman backup
For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backupHi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH -
RMAN duplicate target using set until telling me it can not find data files
I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
However, whenever I try to execute the rman clone, it tells me for each datafile:
RMAN-06023: no backup or copy of datafile 1 found to restore
Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
Here is the RMAN script:
spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
#connect to catalog <catalog info>
# target is the source and auxiliary is destination
#connect target <put in source info here>
#connect auxiliary /
run {
allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
##Archivelog number get from sql archive log list command
#set until sequence 831;
set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
duplicate target database to CSPRSUM1 nofilenamecheck
logfile
group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
Exit
Here is the output:
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog <redacted info>>
2> # target is the source and auxiliary is destination
3> #connect target <redacted info>
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> #set until sequence 831;
14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
starting full resync of recovery catalog
full resync complete
allocated channel: d1
channel d1: SID=534 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=532 device type=DISK
allocated channel: d4
channel d4: SID=531 device type=DISK
allocated channel: a1
channel a1: SID=530 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 15-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 260398799;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
"+data";
set newname for datafile 3 to
"+data";
set newname for datafile 4 to
"+data";
set newname for datafile 5 to
"+data";
set newname for datafile 6 to
"+data";
set newname for datafile 7 to
"+data";
set newname for datafile 8 to
"+data";
set newname for datafile 9 to
"+data";
set newname for datafile 10 to
"+data";
set newname for datafile 11 to
"+data";
set newname for datafile 12 to
"+data";
set newname for datafile 13 to
"+data";
set newname for datafile 14 to
"+data";
set newname for datafile 15 to
"+data";
set newname for datafile 16 to
"+data";
set newname for datafile 17 to
"+data";
set newname for datafile 18 to
"+data";
set newname for datafile 19 to
"+data";
set newname for datafile 20 to
"+data";
set newname for datafile 21 to
"+data";
set newname for datafile 22 to
"+data";
set newname for datafile 23 to
"+data";
set newname for datafile 24 to
"+data";
set newname for datafile 25 to
"+data";
set newname for datafile 26 to
"+data";
set newname for datafile 27 to
"+data";
set newname for datafile 28 to
"+data";
set newname for datafile 29 to
"+data";
set newname for datafile 30 to
"+data";
set newname for datafile 31 to
"+data";
set newname for datafile 32 to
"+data";
set newname for datafile 33 to
"+data";
set newname for datafile 34 to
"+data";
set newname for datafile 35 to
"+data";
set newname for datafile 36 to
"+data";
set newname for datafile 37 to
"+data";
set newname for datafile 38 to
"+data";
set newname for datafile 39 to
"+data";
set newname for datafile 40 to
"+data";
set newname for datafile 41 to
"+data";
set newname for datafile 42 to
"+data";
set newname for datafile 43 to
"+data";
set newname for datafile 44 to
"+data";
set newname for datafile 45 to
"+data";
set newname for datafile 46 to
"+data";
set newname for datafile 47 to
"+data";
set newname for datafile 48 to
"+data";
set newname for datafile 49 to
"+data";
set newname for datafile 50 to
"+data";
set newname for datafile 51 to
"+data";
set newname for datafile 52 to
"+data";
set newname for datafile 53 to
"+data";
set newname for datafile 54 to
"+data";
set newname for datafile 55 to
"+data";
set newname for datafile 56 to
"+data";
set newname for datafile 57 to
"+data";
set newname for datafile 58 to
"+data";
set newname for datafile 59 to
"+data";
set newname for datafile 60 to
"+data";
set newname for datafile 61 to
"+data";
set newname for datafile 62 to
"+data";
set newname for datafile 63 to
"+data";
set newname for datafile 64 to
"+data";
set newname for datafile 65 to
"+data";
set newname for datafile 66 to
"+data";
set newname for datafile 67 to
"+data";
set newname for datafile 68 to
"+data";
set newname for datafile 69 to
"+data";
set newname for datafile 70 to
"+data";
set newname for datafile 71 to
"+data";
set newname for datafile 72 to
"+data";
set newname for datafile 73 to
"+data";
set newname for datafile 74 to
"+data";
set newname for datafile 75 to
"+data";
set newname for datafile 76 to
"+data";
set newname for datafile 77 to
"+data";
set newname for datafile 78 to
"+data";
set newname for datafile 79 to
"+data";
set newname for datafile 80 to
"+data";
set newname for datafile 81 to
"+data";
set newname for datafile 82 to
"+data";
set newname for datafile 83 to
"+data";
set newname for datafile 84 to
"+data";
set newname for datafile 85 to
"+data";
set newname for datafile 86 to
"+data";
set newname for datafile 87 to
"+data";
set newname for datafile 88 to
"+data";
set newname for datafile 89 to
"+data";
set newname for datafile 90 to
"+data";
set newname for datafile 91 to
"+data";
set newname for datafile 92 to
"+data";
set newname for datafile 93 to
"+data";
set newname for datafile 94 to
"+data";
set newname for datafile 95 to
"+data";
set newname for datafile 96 to
"+data";
set newname for datafile 97 to
"+data";
set newname for datafile 98 to
"+data";
set newname for datafile 99 to
"+data";
set newname for datafile 100 to
"+data";
set newname for datafile 101 to
"+data";
set newname for datafile 102 to
"+data";
set newname for datafile 103 to
"+data";
set newname for datafile 104 to
"+data";
set newname for datafile 105 to
"+data";
set newname for datafile 106 to
"+data";
set newname for datafile 107 to
"+data";
set newname for datafile 108 to
"+data";
set newname for datafile 109 to
"+data";
set newname for datafile 110 to
"+data";
set newname for datafile 111 to
"+data";
set newname for datafile 112 to
"+data";
set newname for datafile 113 to
"+data";
set newname for datafile 114 to
"+data";
set newname for datafile 115 to
"+data";
set newname for datafile 116 to
"+data";
set newname for datafile 117 to
"+data";
set newname for datafile 118 to
"+data";
set newname for datafile 119 to
"+data";
set newname for datafile 120 to
"+data";
set newname for datafile 121 to
"+data";
set newname for datafile 122 to
"+data";
restore
clone database
executing Memory Script
executing command: SET until clause
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
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
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
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
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
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
Starting restore at 15-JUN-11
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 122 found to restore
RMAN-06023: no backup or copy of datafile 121 found to restore
RMAN-06023: no backup or copy of datafile 120 found to restore
RMAN-06023: no backup or copy of datafile 119 found to restore
RMAN-06023: no backup or copy of datafile 118 found to restore
RMAN-06023: no backup or copy of datafile 117 found to restore
RMAN-06023: no backup or copy of datafile 116 found to restore
RMAN-06023: no backup or copy of datafile 115 found to restore
RMAN-06023: no backup or copy of datafile 114 found to restore
RMAN-06023: no backup or copy of datafile 113 found to restore
RMAN-06023: no backup or copy of datafile 112 found to restore
RMAN-06023: no backup or copy of datafile 111 found to restore
RMAN-06023: no backup or copy of datafile 110 found to restore
RMAN-06023: no backup or copy of datafile 109 found to restore
RMAN-06023: no backup or copy of datafile 108 found to restore
RMAN-06023: no backup or copy of datafile 107 found to restore
RMAN-06023: no backup or copy of datafile 106 found to restore
RMAN-06023: no backup or copy of datafile 105 found to restore
RMAN-06023: no backup or copy of datafile 104 found to restore
RMAN-06023: no backup or copy of datafile 103 found to restore
RMAN-06023: no backup or copy of datafile 102 found to restore
RMAN-06023: no backup or copy of datafile 101 found to restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
RMAN-06023: no backup or copy of datafile 98 found to restore
RMAN-06023: no backup or copy of datafile 97 found to restore
RMAN-06023: no backup or copy of datafile 96 found to restore
RMAN-06023: no backup or copy of datafile 95 found to restore
RMAN-06023: no backup or copy of datafile 94 found to restore
RMAN-06023: no backup or copy of datafile 93 found to restore
RMAN-06023: no backup or copy of datafile 92 found to restore
RMAN-06023: no backup or copy of datafile 91 found to restore
RMAN-06023: no backup or copy of datafile 90 found to restore
RMAN-06023: no backup or copy of datafile 89 found to restore
RMAN-06023: no backup or copy of datafile 88 found to restore
RMAN-06023: no backup or copy of datafile 87 found to restore
RMAN-06023: no backup or copy of datafile 86 found to restore
RMAN-06023: no backup or copy of datafile 85 found to restore
RMAN-06023: no backup or copy of datafile 84 found to restore
RMAN-06023: no backup or copy of datafile 83 found to restore
RMAN-06023: no backup or copy of datafile 82 found to restore
RMAN-06023: no backup or copy of datafile 81 found to restore
RMAN-06023: no backup or copy of datafile 80 found to restore
RMAN-06023: no backup or copy of datafile 79 found to restore
RMAN-06023: no backup or copy of datafile 78 found to restore
RMAN-06023: no backup or copy of datafile 77 found to restore
RMAN-06023: no backup or copy of datafile 76 found to restore
RMAN-06023: no backup or copy of datafile 75 found to restore
RMAN-06023: no backup or copy of datafile 74 found to restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 72 found to restore
RMAN-06023: no backup or copy of datafile 71 found to restore
RMAN-06023: no backup or copy of datafile 70 found to restore
RMAN-06023: no backup or copy of datafile 69 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restore
RMAN-06023: no backup or copy of datafile 66 found to restore
RMAN-06023: no backup or copy of datafile 65 found to restore
RMAN-06023: no backup or copy of datafile 64 found to restore
RMAN-06023: no backup or copy of datafile 63 found to restore
RMAN-06023: no backup or copy of datafile 62 found to restore
RMAN-06023: no backup or copy of datafile 61 found to restore
RMAN-06023: no backup or copy of datafile 60 found to restore
RMAN-06023: no backup or copy of datafile 59 found to restore
RMAN-06023: no backup or copy of datafile 58 found to restore
RMAN-06023: no backup or copy of datafile 57 found to restore
RMAN-06023: no backup or copy of datafile 56 found to restore
RMAN-06023: no backup or copy of datafile 55 found to restore
RMAN-06023: no backup or copy of datafile 54 found to restore
RMAN-06023: no backup or copy of datafile 53 found to restore
RMAN-06023: no backup or copy of datafile 52 found to restore
RMAN-06023: no backup or copy of datafile 51 found to restore
RMAN-06023: no backup or copy of datafile 50 found to restore
RMAN-06023: no backup or copy of datafile 49 found to restore
RMAN-06023: no backup or copy of datafile 48 found to restore
RMAN-06023: no backup or copy of datafile 47 found to restore
RMAN-06023: no backup or copy of datafile 46 found to restore
RMAN-06023: no backup or copy of datafile 45 found to restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 41 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN> Exit
Recovery Manager complete.
Edited by: kerrygm on Jun 15, 2011 11:36 AMMaybe making progress.
I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
BS Key Type LV Size Device Type Elapsed Time Completion Time
965689 Full 19.86M DISK 00:00:01 16-JUN-11
BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
SPFILE Included: Modification time: 16-JUN-11
SPFILE db_unique_name: CSPROD
Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
BS Key Size Device Type Elapsed Time Completion Time
966218 403.84M DISK 00:00:00 20-MAY-11
BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
List of Archived Logs in backup set 966218
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2112 237027300 20-MAY-11 237046947 20-MAY-11
1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
1 2114 237059284 20-MAY-11 237216514 20-MAY-11
1 2115 237216514 20-MAY-11 237709545 20-MAY-11
1 2116 237709545 20-MAY-11 237722825 20-MAY-11
1 2117 237722825 20-MAY-11 237730431 20-MAY-11
1 2118 237730431 20-MAY-11 237860199 20-MAY-11
I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog 'rmancat/rmancat@rmancat';
2> # target is the source and auxiliary is destination
3> #connect target sys/<pwd>@csprod
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> set until sequence 237046947;
14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
allocated channel: d1
channel d1: SID=532 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=531 device type=DISK
allocated channel: d4
channel d4: SID=555 device type=DISK
allocated channel: a1
channel a1: SID=534 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 17-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 373021170;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
Starting restore at 17-JUN-11
channel d1: starting datafile backup set restore
channel d1: specifying datafile(s) to restore from backup set
channel d1: restoring datafile 00003 to +DATA
channel d2: restoring datafile 00122 to +DATA
channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
channel d3: starting datafile backup set restore
channel d3: specifying datafile(s) to restore from backup set
channel d3: restoring datafile 00002 to +DATA
channel d3: restoring datafile 00020 to +DATA
channel d4: restoring datafile 00120 to +DATA
channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
channel d1: restored backup piece 1
channel d1: restore complete, elapsed time: 00:01:15
channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
channel d4: restored backup piece 1
channel d4: restore complete, elapsed time: 00:03:15
channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
channel d2: restored backup piece 1
channel d2: restore complete, elapsed time: 00:03:35
channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
channel d3: restored backup piece 1
channel d3: restore complete, elapsed time: 00:04:55
Finished restore at 17-JUN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
MAXLOGFILES 23
MAXLOGMEMBERS 3
MAXDATAFILES 1021
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
DATAFILE
'+DATA/csprsum1/datafile/system.1535.754067379'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
datafile 121 switched to datafile copy
input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
datafile 122 switched to datafile copy
input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
contents of Memory Script:
set until scn 373021170;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-JUN-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/csprsum1/datafile/system.1535.754067379'
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
RMAN> Exit
Recovery Manager complete.
What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
(e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
Also, as you can see it was not able to do a media recovery.
Thanks in advance for your help. -
Unable to restore and recover my Database from RMAN Backup
Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
MahiAll you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;" -
RMAN, RAC, NFS, and server lock ups
Good day. My environment is:
--a 2-node RAC
--Enterprise Edition 11.2.0.3
--RHEL 5.1
The goal is to use RMAN to push backups to a shared NFS mount (on a different server). Both nodes will have access to this location (in the event one node goes down, the other can still run backups). Easy, right?
Wrong.
I've tried every NFS mount option in the book. Most work just fine, some don't. When I use the recommended NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0
or
rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid
The mount works normally. I can "ls" and "mkdir" and "touch" and "vi" and "cp" files back and forth from the NFS backup location to the RAC node all day long. No problems. However, when I try to do almost anything in RMAN which requires writing to the NFS backup location such as the command "backup archive all delete input;" (or even things as simple as a Crosscheck or RMAN configuration change which writes any changes back to the autobackup ControlFile) the node locks up. There are no errors (or if there are, I don't know where to find them), even when I use RMAN log.
Just to recap: I run a Crosscheck (or any RMAN process that writes to the NFS backup location), the node will lock up, and I can let it sit for a day, inaccessible, with CRSCTL on the other node saying it's offline, and the node will never come out of a "frozen" state. It cannot be pinged or connected to.
I think I can safely rule out NFS mount options at this point.
I understand (after extensive reading of MOS docs and testing) that RAC RMAN can and does suffer from inefficient I/O when writing to an NFS mount. I don't think that's the culprit either. The autobackup ControlFile is not that big and I cannot see how running a simple Crosscheck would lock an entire node.
I am hoping someone has encountered this in the past and hopefully it's just a simple misconfiguration somewhere.My NFS line in /etc/fstab is (these options are for supporting 11.2.0.3, 11.1.0.7, and 10.2.0.4/5 simultaneously): server.domain:/NFS_Export /backup nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
Before you installed GI, did you by chance do a yum update? I've encountered a similar issue which ended up being due to mkinitrd creating a corrupted kernel; mkinitrd is invoked during the GI installation when the ADVM drivers are added and in my case mkinitrd created a new kernel prior to the new kernel being installed. Second to that, make sure you have the matching kernel headers to your kernel version. If they are different then you could probably get away with just creating a new kernel with mkinitrd and relinking GI/RDBMS homes, but be prepared to wipe GI and reinstall. -
Using rman to backup a remote database
I am after a good guide or advice on how (what) to install and (how to) run Oracle RMAN
to backup a remote Oracle database.
RMAN must be installed and run on a Solaris (SunOS 5.8) box remote from the Solaris
box (also SunOS 5.8) running the Oracle database but connected to it via a TCP/IP
network.
The Oracle Recovery Manager and Database version is 9.2.0.1.0.
RMAN must perform the backup of the remote database over the network and store
the backup on a disk local to the RMAN box.
The backups may be full or incremental and may be "hot" backups taken while the
Oracle database is open.
The disk files are to be then backed up to tape using Veritas.
What software do I need to install on the RMAN box ?
What software do I need to install on the remote Oracle database box ?
Thanks,
Brett Morgan.writes to a NFS-mounted diskRman is writing to disk or tape (when is bundled (libraries needed) with some backup software for tapes such as Veritas). The disk device could be local, or mounted disk form other host or storage (over NFS as Werner mentioned, SMB and others).
-
I am having issue with RMAN
I have Oracle 11gR2 database on HP-UX. when I issue any command in RMAN prompt, its displaying the information but it's not returning to RMAN prompt, I have to hit CTRL+C to come out. But I have 2 more database on the same home, and I don't have this problem on that database.
oracle@hublhp10:/home/oracle$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Mar 19 15:00:53 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: IMGPROD (DBID=2867365220)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name IMGPROD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/imgback/RMAN/cf-IMGPROD-%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/imgback/RMAN/snapcf_imgprod.f';
RMAN>
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Archive Log 1 19-MAR-12 /imgarch/ORACLE/imgprod/al_imgprod_1_283_777982948.dbfI traced the session, see the following
WAIT #2: nam='control file sequential read' ela= 143 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515395399
WAIT #2: nam='control file sequential read' ela= 143 file#=0 block#=1 blocks=1 obj#=-1 tim=11750515395853
WAIT #2: nam='control file sequential read' ela= 144 file#=0 block#=15 blocks=1 obj#=-1 tim=11750515396024
WAIT #2: nam='control file sequential read' ela= 145 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515396192
WAIT #2: nam='control file sequential read' ela= 206 file#=0 block#=1 blocks=1 obj#=-1 tim=11750515396719
WAIT #2: nam='control file sequential read' ela= 142 file#=0 block#=15 blocks=1 obj#=-1 tim=11750515396909
WAIT #2: nam='control file sequential read' ela= 168 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515397102
FETCH #2:c=0,e=16905,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=1,plh=818693323,tim=11750515397527
WAIT #2: nam='SQL*Net message from client' ela= 450 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=11750515398178
CLOSE #2:c=0,e=27,dep=0,type=3,tim=11750515398262
=====================
PARSING IN CURSOR #4 len=205 dep=0 uid=0 oct=3 lid=0 tim=11750515399507 hv=1796820951 ad='c0000004fe449f88' sqlid='gq4u3dppjkmyr'
select /*+ rule */ round(sum(MBYTES_PROCESSED)), round(sum(INPUT_BYTES)), round(sum(OUTPUT_BYTES)) from V$RMAN_STATUS START WITH RECID = :row_id and STAMP = :row_stamp CONNECT BY PRIOR RECID = parent_recid
END OF STMT
PARSE #4:c=0,e=556,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,plh=0,tim=11750515399506 -
Backing up and restoring tablespaces with RMAN
We have some tables that we want to backup and other tables that we don't.
We are separating these tables by tablespaces and schema.
SchemaA uses tablespaceA
SchemaB uses tablespacesB
We are also backing up
sys
sysaux
undo
tablespaces.
Lets say we lose our tablespaces and do a restore. I am assuming that all my stored procedures can be restored no matter which schema I save them in. even if I save them in a schema that has a default tablespace that is not being backed up because the code in is in the System tablespace.
Is my assumption correct?Here the key concept is Mean Time To Recover(MTTR), usually it is faster and easier to use an export backup file for this purpose, but this doesn't mean RMAN is bad :) RMAN was, is and will be the best practice for Oracle's B&R.
Still you may assist your RMAN backup with a daily norows export backup and also maybe a file system backup depending on your environment and application's need. Backup's backup do not harm :) -
Can you help me? I meet errors when I do incomplete recovery with RMAN
In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: 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-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
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-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.which o.s u are using i can't help you as i never worked on ver 8i,i can tell you incomplete recovery on oracle 9i on win 2000 server.
thanks : alok kumar -
Can you help me? I meet some errors when I do incomplete recovery with RMAN
In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: 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-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
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-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.You are correct. In RMAN8i, you should add the "alter system archive log current; command before you backup the archive logs.
You are running into the case where Oracle needs additional redo to make the database consistent that was located in the current online log at the time of the backup.
If you set UNTIL TIME to an earlier time does the recover work?
In Oracle9i, if you issue the command, "backup database plus archive logs", RMAN will automatically archive the current online log before performing the archive log backups.
Thanks, Tammy -
RMAN issue, any feedback appreciated
Guys,
Sorry, i shouldn't have posted it here..
We currently use the following script to take backup of our database on production. But this morning i've noticed that the RETENTION POLICY was set to redundancy 1 and it was deleting all backup prior to a day old, although the image copy script says, retain a recovery window of up to 3 days..
run {allocate channel daily_backup device type disk;recover copy of database with tag 'DAILY_BKP' until time 'SYSDATE - 3';backup incremental level 1 cumulative copies=1 for recover of copy with tag 'DAILY_BKP' database;}So, i set the RENTENTION POLICY to 3 days and deleted all old backup pieces and started a fresh one.. But i am gobsmacked to see that the output below still shows it as incrmental level 1,( it should have been level 0) and the size of 890M for a database of size 50+ Gb.
What's going wrong ? Is RMAN doing something wrong ?
here is the output after the backup..
RMAN> list backup;using target database control file instead of recovery catalogList of Backup Sets===================BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------205 Incr 1 847.98M DISK 00:00:24 24-JAN-07 BP Key: 201 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095347 Piece Name: ORARECO/vfprod/backupset/2007_01_24/nnndn1_tag20070124t095347_0.2441.612698029 List of Datafiles in backup set 205 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 1 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/system.262.604149337 2 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/undotbs1.261.604149337 3 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/sysaux.263.604149337 4 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/users.268.604149337 5 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/undotbs2.260.604149411 6 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_data_01.258.604153527 7 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_data_02.259.604158465 8 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_index_02.266.604158515 9 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/backup_01.265.607712919 10 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_index_01.256.604158593 11 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/reports_01.269.604160179 12 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_data_03.270.607340425 13 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_data_04.271.607342515 14 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_index_03.272.607342557 15 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/prod_index_04.273.607342857 16 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/swe_data_01.285.611322965 17 1 Incr 58614445 24-JAN-07 ORADATA/vfprod/datafile/swe_index_01.286.611323027BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------206 Full 15.48M DISK 00:00:01 24-JAN-07 BP Key: 202 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095413 Piece Name: +ORARECO/vfprod/autobackup/2007_01_24/s_612698053.2423.612698053 Control File Included: Ckp SCN: 58614605 Ckp time: 24-JAN-07 SPFILE Included: Modification time: 22-JAN-07RMAN> exitAny comments will be valuable.
Thanks
G'RMAN' seems to be a good work and is doing an incremental backup after the first full backup (this is the correct way).</BR>If you look to the files size you'll see that incremental backup is taking only 15.48M.</BR>It's normal a backup (or incremental backup) take more few space than a "conventional backup" because RMAN compress data.</BR></BR></BR>
[Please, in future format properly your code: lines with more than 2048 characters are difficult to read, format and understand.] -
RMAN issue - any feedback would be appreciated
Guys,
Sorry, i shouldn't have posted it here..
We currently use the following script to take backup of our database on production. But this morning i've noticed that the RETENTION POLICY was set to redundancy 1 and it was deleting all backup prior to a day old, although the image copy script says, retain a recovery window of up to 3 days..
run {
allocate channel daily_backup device type disk;
recover copy of database with tag 'DAILY_BKP' until time 'SYSDATE - 3';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'DAILY_BKP' database;
}So, i set the RENTENTION POLICY to 3 days and deleted all old backup pieces and started a fresh one.. But i am gobsmacked to see that the output below still shows it as incrmental level 1,( it should have been level 0) and the size of 890M for a database of size 50+ Gb.
What's going wrong ? Is RMAN doing something wrong ?
here is the output after the backup..
RMAN> list backup;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
205 Incr 1 847.98M DISK 00:00:24 24-JAN-07
BP Key: 201 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095347
Piece Name: +ORARECO/vfprod/backupset/2007_01_24/nnndn1_tag20070124t095347_0.2441.612698029
List of Datafiles in backup set 205
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/system.262.604149337
2 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/undotbs1.261.604149337
3 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/sysaux.263.604149337
4 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/users.268.604149337
5 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/undotbs2.260.604149411
6 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_01.258.604153527
7 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_02.259.604158465
8 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_02.266.604158515
9 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/backup_01.265.607712919
10 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_01.256.604158593
11 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/reports_01.269.604160179
12 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_03.270.607340425
13 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_04.271.607342515
14 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_03.272.607342557
15 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_04.273.607342857
16 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/swe_data_01.285.611322965
17 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/swe_index_01.286.611323027
BS Key Type LV Size Device Type Elapsed Time Completion Time
206 Full 15.48M DISK 00:00:01 24-JAN-07
BP Key: 202 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095413
Piece Name: +ORARECO/vfprod/autobackup/2007_01_24/s_612698053.2423.612698053
Control File Included: Ckp SCN: 58614605 Ckp time: 24-JAN-07
SPFILE Included: Modification time: 22-JAN-07
RMAN> exitAny comments will be valuable.
Thanks
GGuys,
Sorry, i shouldn't have posted it here..
We currently use the following script to take backup of our database on production. But this morning i've noticed that the RETENTION POLICY was set to redundancy 1 and it was deleting all backup prior to a day old, although the image copy script says, retain a recovery window of up to 3 days..
run {
allocate channel daily_backup device type disk;
recover copy of database with tag 'DAILY_BKP' until time 'SYSDATE - 3';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'DAILY_BKP' database;
}So, i set the RENTENTION POLICY to 3 days and deleted all old backup pieces and started a fresh one.. But i am gobsmacked to see that the output below still shows it as incrmental level 1,( it should have been level 0) and the size of 890M for a database of size 50+ Gb.
What's going wrong ? Is RMAN doing something wrong ?
here is the output after the backup..
RMAN> list backup;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
205 Incr 1 847.98M DISK 00:00:24 24-JAN-07
BP Key: 201 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095347
Piece Name: +ORARECO/vfprod/backupset/2007_01_24/nnndn1_tag20070124t095347_0.2441.612698029
List of Datafiles in backup set 205
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/system.262.604149337
2 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/undotbs1.261.604149337
3 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/sysaux.263.604149337
4 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/users.268.604149337
5 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/undotbs2.260.604149411
6 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_01.258.604153527
7 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_02.259.604158465
8 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_02.266.604158515
9 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/backup_01.265.607712919
10 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_01.256.604158593
11 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/reports_01.269.604160179
12 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_03.270.607340425
13 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_data_04.271.607342515
14 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_03.272.607342557
15 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/prod_index_04.273.607342857
16 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/swe_data_01.285.611322965
17 1 Incr 58614445 24-JAN-07 +ORADATA/vfprod/datafile/swe_index_01.286.611323027
BS Key Type LV Size Device Type Elapsed Time Completion Time
206 Full 15.48M DISK 00:00:01 24-JAN-07
BP Key: 202 Status: AVAILABLE Compressed: NO Tag: TAG20070124T095413
Piece Name: +ORARECO/vfprod/autobackup/2007_01_24/s_612698053.2423.612698053
Control File Included: Ckp SCN: 58614605 Ckp time: 24-JAN-07
SPFILE Included: Modification time: 22-JAN-07
RMAN> exitAny comments will be valuable.
Thanks
G
Maybe you are looking for
-
Hi All, Please help to elaborate the difference between Insert All and Insert in oracle 10g. Thanks, regards,
-
Can't install iTunes on PC running Windows 7
Can someone please give me step by step instructions to download iTunes to my PC? It keeps stalling on me with a few minutes left in the download. Many Thanks to Any Help!
-
Windows XP can't print to my Mac's printer?
Why not? I have Printer Sharing enabled, and printing is fine with my Mac. What do I need to do to fix this? My printer is an HP DeskJet 932C.
-
Adding a merge field to an email hyperlink in a word 2010 email mailmerge
I am using word 2010, excel 2010, and outlook 2010 to send out the following email with email mailmerge to 50 + people. The highlighted names in the greeting are two merge fields - First_Name and Last_Name. The hyperlink is an email hyperlink to the
-
How to disable "Use Default If Unwired" by default?
When scanning part of my code, I noticed a wire output tunnel set to Use Default If Unwired, that would have really messed things up if I'd tried to run the program. Is there a way to have that setting disabled by default? I'd prefer to conciously