RMAN vs SQL

is there any difference between
RMAN "BACKUP CURRENT CONTROLFILE" and
SQL "ALTER DATABASE BACKUP CONTROLFILE"
is the output file of both same?

It's not the same.
RMAN "BACKUP CURRENT CONTROLFILE" generates an RMAN copy of the controlfile.
SQL "ALTER DATABASE BACKUP CONTROLFILE to trace" generates a trace file in the directory pointed by the USER_DUMP_DEST parameter : you can use this one to recreate the controlfile.

Similar Messages

FLASHBACK Database : rman vs sql command differnces

I am new to Oracle and want understand the difference and which is the correct way of flashing back the database?
RMAN command vs SQL Command on using FLASHBACK DATABASE
SQL> FLASHBACK DATABASE TO RESTORE POINT BEFORE_ONLINE_TEST; {CODE} Vs rman> run{
     flashback database to restore point BEFORE_TEST_320130313;
     sql "alter database open resetlogs"; }
Referring this article on http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmflash.htm#BGBDCAFA it says we can use both RMAN and SQL command for database flashback.
Questions:
1. Difference between using RMAN and SQL command on database flashback?
2. When to use RMAN or SQL on the database flashback?
3. Which is the Oracle recommended or best way ?
Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:28 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:29 PM

When I issue the SQL Plus command of
SQL> flashback database to restore point BEFORE_TEST_20130313 ;
flashback database to restore point BEFORE_TEST_20130313
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38762: redo logs needed for SCN 87612483975 to SCN 87612485856
ORA-38761: redo log sequence 1 in thread 1, incarnation 3 could not be accessedHowever on running this on RMAN
RMAN>
list backup of archivelog scn between 87612483975 and 87612485856
RMAN> ;
starting full resync of recovery catalog
full resync complete
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
5212758 19.75M     SBT_TAPE    00:00:04     13-MAR-2013 16:36:17
        BP Key: 5212765   Status: AVAILABLE Compressed: NO Tag: TAG20130313T163611
        Handle: <TestDB_60:809973373:1>.al   Media: 945c30b6:506c6cd2:3a14:0001
List of Archived Logs in backup set 5212758
Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
1    1       87612468290 13-MAR-2013 13:28:19 87612484321 13-MAR-2013 16:36:06
1    2       87612484321 13-MAR-2013 16:36:06 87612484339 13-MAR-2013 16:36:09
BS Key Size       Device Type Elapsed Time Completion Time
5212759 896.50M    SBT_TAPE    00:00:17     13-MAR-2013 16:36:30
        BP Key: 5212766   Status: AVAILABLE Compressed: NO Tag: TAG20130313T163611
        Handle: <TestDB_59:809973373:1>.al   Media: 945c30b6:506c6cbd:39f5:0001
List of Archived Logs in backup set 5212759
Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
1    5       87612363812 12-MAR-2013 14:22:26 87612659040 13-MAR-2013 03:04:08
run {
allocate CHANNEL dev_2 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_3 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_4 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
flashback database to restore point BEFORE_TEST_20130313;
sql "alter database open resetlogs";
release channel dev_2;
release channel dev_3;
release channel dev_4;
starting media recovery
archived log for thread 1 with sequence 2 is already on disk as file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_2.3612.810054205
archived log for thread 1 with sequence 3 is already on disk as file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_3.1588.810054205
channel dev_2: starting archived log restore to default destination
channel dev_2: restoring archived log
archived log thread=1 sequence=1
channel dev_2: reading from backup piece <TestDB_60:809973373:1>.al
channel dev_2: piece handle=<TestDB_60:809973373:1>.al tag=TAG20130313T163611
channel dev_2: restored backup piece 1
channel dev_2: restore complete, elapsed time: 00:00:46
channel dev_2: deleting archived log(s)
archived log file name=+DG_PERF_FLASH_02/TestDB/archivelog/2013_03_15/thread_1_seq_1.2969.810106317 RECID=49 STAMP=810106318
media recovery complete, elapsed time: 00:00:05
Finished flashback at 10-MAR-2013 05:32:07
database reset to incarnation 5215723
When we issue the SQL Plus command, if there is need of old database backup of archive log, how does that SQL Plus communicate with rman recovery catalog and retrieve?

Recover Database in RMAN vs SQL*PLUS

Hello,
Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
Thanks.
h3. Solution Summary:
The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
Edited by: Dude on Jan 7, 2011 12:30 PM

Dude wrote:
I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
C:\Documents and Settings\chinar>rman target sys/sm
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area     138412032 bytes
Fixed Size                     1247708 bytes
Variable Size                 71304740 bytes
Database Buffers              58720256 bytes
Redo Buffers                   7139328 bytes
RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
2> ;
Starting restore at 07-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
Finished restore at 07-JAN-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 07-JAN-11
Starting implicit crosscheck backup at 07-JAN-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 07-JAN-11
Starting implicit crosscheck copy at 07-JAN-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 07-JAN-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
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 D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
Finished restore at 07-JAN-11
RMAN> recover database;
Starting recover at 07-JAN-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
2.0\ORADATA\T\REDO02.LOG
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
media recovery complete, elapsed time: 00:00:03
Finished recover at 07-JAN-11
RMAN> exit
Recovery Manager complete.
C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL> And above you see lines as
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
*2.0\ORADATA\T\REDO02.LOG*
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
parallel recovery started with 2 processes
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Fri Jan 07 17:50:34 2011
alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
Fri Jan 07 17:50:34 2011
Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
Fri Jan 07 17:50:34 2011
Incomplete recovery applied all redo ever generated.
Recovery completed through change 665263
Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start until cancel using backup controlfile)
And these is not any difference.
Hope that help you and you got answer.

Databse start up via rman or sql

how to connect with Oracle after you shut down DB?

Hi,
Could you please elaborate your question?
To startup the database in a previously connected rman-session, you just do
RMAN> startup [nomount]If you've terminated the rman-session, you might need to first do a "set dbid=$DATABASEID".
In sqlplus, you connect locally, and issue the startup-command.
sqlplus / as sysdba
startupRecommended reading:
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/toc.htm
HtH
Johan

Sql commands in RMAN

I tried to execute in Rman this SQL statement
sql 'alter session set NLS_DATE_FORMAT='MM-DD-YYYY'';
but rman gives me an error.
MM is a "bad identifier"...
I know that single quotes make some trouble....but I tried all
escape sequences (duoble quotes, Backslash etc)
None of them worked....
what can i do???
thx in advance.

From Oracle8i Recovery manager User's Guide and Reference,
p. 10-150
If the string that RMAN passes to PL/SQL contains a filename,
then the filename must be enclosed in duplicate single
quotes and the entire string following the sql parameter
must be enclosed in double quotes.
Try
RMAN> sql "alter session set nls_date_format=''DD-MON-YY''";
Regards,
Sev

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 backup

Hi,
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

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-05556: not all datafiles have backups that can be recovered to SCN

Oracle 11.2.0.2 SE-One
Oracle Linux 5.6 x86-64
Weekly refresh of a test db from prod, using rman DUPLICATE DATABASE, failed with “RMAN-05556: not all datafiles have backups that can be recovered to SCN”
Background Summary:
Weekly inc 0 backup of production starts on Sunday at 0100, normally completes around 1050. Includes backups of archivelogs
Another backup of just archivelogs runs on Sunday at 1200, normally completes NLT 1201.
On the test server, the refresh job starts on Sunday at 1325. In the past this script used a set until time \"to_date('`date +%Y-%m-%d` 11:55:00','YYYY-MM-DD hh24:mi:ss')\"; -- hard-coded for ‘today at 11:55’.
For a variety of reasons I decided to replace this semi-hard coding of the UNTIL with a value determined by querying the rman catalog, getting the completion time of the inc 0 backup. This tested out just fine in my vbox lab, even when I deliberately drove some updates and log switches during the period the backup was running. But the first time to go live I got the above reported error.
Details:
The key part of the inc 0 backup is this (run from a shell script)
export BACKUP_LOC=/u01/backup/dbprod
$ORACLE_HOME/bin/rman target=/ catalog rman/***@rmcat<<EOF
configure backup optimization on;
configure default device type to disk;
configure retention policy to recovery window of 2 days;
crosscheck backup;
crosscheck archivelog all;
delete noprompt force obsolete;
delete noprompt force expired backup;
delete noprompt force expired archivelog all;
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '$BACKUP_LOC/%d_%F_ctl.backup';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '$BACKUP_LOC/%U.rman' MAXPIECESIZE 4096 M;
sql "alter system archive log current";
show all;
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
backup as compressed backupset incremental level 0 database tag tag_dbprod;
sql "alter system archive log current";
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
list recoverable backup;
EOF
The archivelog-only backup (runs at noon) looks like this:
export BACKUP_LOC=/u01/backup/dbprod
$ORACLE_HOME/bin/rman target=/ catalog rman/***@rmcat<<EOF
configure backup optimization on;
configure default device type to disk;
configure retention policy to recovery window of 2 days;
crosscheck backup;
crosscheck archivelog all;
delete noprompt force obsolete;
delete noprompt force expired backup;
delete noprompt force expired archivelog all;
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '$BACKUP_LOC/%d_%F_ctl.backup';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '$BACKUP_LOC/%U.rman' MAXPIECESIZE 4096 M;
sql "alter system archive log current";
show all;
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
list recoverable backup;
EOF
And the original refresh looked like this:
>> a step to ftp the backups from the prod server to the test server, and some other housekeeping <<, then
cd /backup/dbtest
echo "connect catalog rman/***@rmcat" > /backup/dbtest/dbtest_refresh.rman
echo "connect target sys/*******@dbprod" >> /backup/dbtest/dbtest_refresh.rman
echo "connect auxiliary /"             >> /backup/dbtest/dbtest_refresh.rman
echo "run {"                           >> /backup/dbtest/dbtest_refresh.rman
echo "set until time \"to_date('`date +%Y-%m-%d` 11:55:00','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbtest/dbtest_refresh.rman
echo "duplicate target database to DBTEST;" >> /backup/dbtest/dbtest_refresh.rman
echo "}" >> /backup/dbtest/dbtest_refresh.rman
So, my mod to the refresh was
bkup_point=`sqlplus -s rman/***@rmcat <<EOF1
set echo off verify off feedback off head off pages 0 trimsp on
select to_char(max(completion_time),'yyyy-mm-dd hh24:mi:ss')
from rc_backup_set_details
where db_name='DBPROD'
and backup_type='D'
and incremental_level=0
exit
EOF1`
cd /backup/dbtest
echo "connect catalog rman/***@rmcat"     > /backup/dbtest/dbtest_refresh.rman
echo "connect target sys/*******@dbprod"    >> /backup/dbtest/dbtest_refresh.rman
echo "connect auxiliary /"                >> /backup/dbtest/dbtest_refresh.rman
echo "run {"                              >> /backup/dbtest/dbtest_refresh.rman
echo "set until time \"to_date('${bkup_point}','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbtest/dbtest_refresh.rman
echo "duplicate target database to DBTEST;" >> /backup/dbtest/dbtest_refresh.rman
echo "}"                                  >> /backup/dbtest/dbtest_refresh.rman
Now the fun begins.
First, an echo in the refresh script confirmed the ‘bkup_point’:
=======================================================
We will restore to 2013-08-25 10:41:38
=======================================================
Internally, rman reset the ‘until’ as follows:
executing command: SET until clause
Starting Duplicate Db at 25-Aug-2013 15:35:44
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=162 device type=DISK
contents of Memory Script:
   set until scn 45633141350;
Examining the result of LIST BACKUP (the last step of all of my rman scripts) the full backup shows this:
BS Key Type LV Size       Device Type Elapsed Time Completion Time
5506664 Full 61.89M     DISK        00:00:03     25-Aug-2013 02:11:32
        BP Key: 5506678   Status: AVAILABLE Compressed: NO Tag: TAG20130825T021129
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-00_ctl.backup
SPFILE Included: Modification time: 24-Aug-2013 22:33:08
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45628880455   Ckp time: 25-Aug-2013 02:11:29
BS Key Type LV Size       Device Type Elapsed Time Completion Time
5507388 Incr 0 206.03G    DISK        08:30:00     25-Aug-2013 10:41:30
List of Datafiles in backup set 5507388
File LV Type Ckp SCN    Ckp Time             Name
1    0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/datafile/system.258.713574775
>>>>>>>>> snip lengthy list <<<<<<<<<
74   0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/event_i2.dbf
Backup Set Copy #1 of backup set 5507388
Device Type Elapsed Time Completion Time      Compressed Tag
DISK        08:30:00     25-Aug-2013 10:41:36 YES        TAG_DBPROD
    List of Backup Pieces for backup set 5507388 Copy #1
    BP Key Pc# Status      Piece Name
    5507391 1   AVAILABLE   /u01/backup/dbprod/eeoi55iq_1_1.rman
    >>>>>>>>>>>>> snip lengthy list <<<<<<<<<<<
    5507442 52 AVAILABLE   /u01/backup/dbprod/eeoi55iq_52_1.rman
Notice the slight difference in time between what is reported in the LIST BACKUP and what was reported by my query to the catalog.
Continuing with the backup list, the second archivelog backup in the script generated six backupsets. The fifth set showed:
BS Key Size       Device Type Elapsed Time Completion Time
5507687 650.19M DISK        00:02:18     25-Aug-2013 10:54:53
        BP Key: 5507694   Status: AVAILABLE Compressed: YES Tag: TAG20130825T104156
Piece Name: /u01/backup/dbprod/ekoi643j_1_1.alog
List of Archived Logs in backup set 5507687
Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
1    1338518 45632944587 25-Aug-2013 05:58:18 45632947563 25-Aug-2013 05:58:20
    >>>>>>>>>>>>> snip lengthy list <<<<<<<<<<<
1    1338572 45633135750 25-Aug-2013 10:08:21 45633140240 25-Aug-2013 10:08:24
1    1338573 45633140240 25-Aug-2013 10:08:24 45633141350 25-Aug-2013 10:30:06
1    1338574 45633141350 25-Aug-2013 10:30:06 45633141705 25-Aug-2013 10:41:51
1    1338575 45633141705 25-Aug-2013 10:41:51 45633141725 25-Aug-2013 10:41:55
Notice the availability of the archivelogs including the referenced scn.
Investigation of the ftp portion of the refresh script confirmed that all backup pieces were copied from the prod server.
So what am I overlooking? Having reverted back to the original script to get the refresh completed,

HemantKChitale wrote:
So, technically, you only need the database and archivelogs backed up by the database script and not the noon run of the archivelog backup.
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
backup as compressed backupset incremental level 0 database tag tag_dbprod;
sql "alter system archive log current";
backup as compressed backupset archivelog all delete all input format "$BACKUP_LOC/%U.alog";
Yet, why does backupset 5 of the noon archivelog backup show archivelogs from 10:30 to 10:40 if they had been deleted by the database backup script which has a delete input ? It is as if the database backup script did NOT delete the archivelogs and the noon run was the one to backup the archivelogs (again ?)
No, that is from the morning full backup. Note the 'Completion Time" of 25-Aug-2013 10:54:53
However, the error message seems to point to a datafile. Why would reverting the recovery point to 11:55 make a difference, I wonder.
As do I.
Also puzzling to me are the times associated with the completion of the backups. I don't recall ever having to scrutinize a backup listing this closely so I'm sure it's just a matter of filling in some gaps in my understanding, but I noticed this. The backup report (list backup;) shows this for the inc 0 backup:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507388 Incr 0 206.03G
DISK
08:30:00
25-Aug-2013 10:41:30   ------- NOTE THE COMPLETION TIME ----
List of Datafiles in backup set 5507388
File LV Type Ckp SCN
Ckp Time
Name
1
0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/datafile/system.258.713574775
------ SNIP ------
74   0 Incr 45628880495 25-Aug-2013 02:11:38 +SMALL/dbprod/event_i2.dbf
Backup Set Copy #1 of backup set 5507388
Device Type Elapsed Time Completion Time
Compressed Tag
DISK
08:30:00
25-Aug-2013 10:41:36 YES
TAG_DBPROD   ------- NOTE THE COMPLETION TIME ----
List of Backup Pieces for backup set 5507388 Copy #1
BP Key Pc# Status
Piece Name
5507391 1   AVAILABLE   /u01/backup/dbprod/eeoi55iq_1_1.rman
------ SNIP ------
5507442 52 AVAILABLE   /u01/backup/dbprod/eeoi55iq_52_1.rman
Then the autobackup of the control file immediatly following:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507523 Full
61.89M
DISK
00:00:03
25-Aug-2013 10:41:47   ------- NOTE THE COMPLETION TIME ----
BP Key: 5507587   Status: AVAILABLE Compressed: NO Tag: TAG20130825T104144
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-01_ctl.backup
SPFILE Included: Modification time: 25-Aug-2013 05:57:15
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45633141671   Ckp time: 25-Aug-2013 10:41:44
Then the archivelog backup immediately following (remember, this created a total of 5 backupset, I'm showing number 4)
BS Key Size
Device Type Elapsed Time Completion Time
5507687 650.19M
DISK
00:02:18
25-Aug-2013 10:54:53   ------- NOTE THE COMPLETION TIME ----
BP Key: 5507694   Status: AVAILABLE Compressed: YES Tag: TAG20130825T104156
Piece Name: /u01/backup/dbprod/ekoi643j_1_1.alog
List of Archived Logs in backup set 5507687
Thrd Seq
Low SCN
Low Time
Next SCN   Next Time
1
1338518 45632944587 25-Aug-2013 05:58:18 45632947563 25-Aug-2013 05:58:20
------ SNIP ------
1
1338572 45633135750 25-Aug-2013 10:08:21 45633140240 25-Aug-2013 10:08:24
1
1338573 45633140240 25-Aug-2013 10:08:24 45633141350 25-Aug-2013 10:30:06
1
1338574 45633141350 25-Aug-2013 10:30:06 45633141705 25-Aug-2013 10:41:51
1
1338575 45633141705 25-Aug-2013 10:41:51 45633141725 25-Aug-2013 10:41:55
and the controlfile autobackup immediately following:
BS Key Type LV Size
Device Type Elapsed Time Completion Time
5507984 Full
61.89M
DISK
00:00:03
25-Aug-2013 10:55:07   ------- NOTE THE COMPLETION TIME ----
BP Key: 5508043   Status: AVAILABLE Compressed: NO Tag: TAG20130825T105504
Piece Name: /u01/backup/dbprod/DBPROD_c-3960114099-20130825-02_ctl.backup
SPFILE Included: Modification time: 25-Aug-2013 05:57:15
SPFILE db_unique_name: DBPROD
Control File Included: Ckp SCN: 45633142131   Ckp time: 25-Aug-2013 10:55:04
and yet, querying the rman catalog
SQL> select to_char(max(completion_time),'yyyy-mm-dd hh24:mi:ss')
2 from rc_backup_set_details
3 where db_name='DBPROD'
4 and backup_type='D'
5 and incremental_level=0
6 ;
TO_CHAR(MAX(COMPLET
2013-08-25 10:41:38
SQL>
which doesn't match (to the second) the completion time of either the full backup or the associated controlfile autobackp.
Hemant K Chitale
I hope this posts in a readable, understandable manner. I really struggeled with the 'enhanced editor', which I normally use. When I pasted in blocks from the rman report, it kept trying to make some sort of table structure out of it .... guess I'll have to follow that up with a question in the Community forum ....

Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

I will explain my scenario below:
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
Please suggest me the best way forward...
Many Thanks
Nukesh

Hi Asif,
I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
RMAN> exit
TEST1DB-> rman target sys@MYTEST1
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: MYTEST (DBID=2433328848, not open)
RMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> run {
2> restore database until scn 10000;
3> recover database until scn 10000;
4> alter database open resetlogs;
5> };
Starting restore at 07-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/07/2010 11:45:18
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
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 '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
RMAN> exit
SQL> select name from v$database;
NAME
MYTEST
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>

RMAN Best Practices

Hi RMAN guys,
i´m thinking about the BEST strategy to make a full rman backup WITHOUT the catalog.
I would like anybody to comment my experiences:
1. I had a recovery case (but it´s more then 10 months ago, and i´m not remembering anything in detail, sorry) where i lost nearly anything.
In this case i needed the DB-ID for recovery, so i think it´s good know, what db-id you have
=>SELECT dbid,name FROM v$database;
2. RMAN needs the database to be at least in nomount, so you should have a spfile copy outside of your rman backup
=> sql "CREATE PFILE=''c:\bak\init.ora'' FROM spfile";
3. A Checkpoint at the beginning of your Backup is always good
=> sql "Alter system checkpoint";
or would say let´s make a log-switch?
=> sql "alter system switch logfile";
4. If you loose everything INCLUDING all Controlfile Copies, you should know which datafiles/controlfile/redologs you had:
=>
SELECT file_name,tablespace_name FROM dba_data_files;
SELECT member FROM v$logfile;
SELECT name FROM v$controlfile;
Than you could use the dbms_backup_restore.restoreDataFileTo Package-Procedure
5. Make a full backup of the database;
But what special parameters are important?
+ MAXCORRUPT?
+ FORMAT '....' or Default?
+ PLUS ARCHIVELOG DELETE INPUT ?
+???
5a. Make also copy of:
Listener.ora, tnsnames.ora, sqlnet.ora
pwd<sid>.ora
Windows: Registry of Oracle-Tree
UNIX: oratab
+???
6. Validate the backup
7. DELETE OBSOLETE Backups;
8. Send yourself an email with the rman-log
utl_mail ....
9.x -Y.x ???
Any Comments ?
Thanks
Marco

1. OK
2. OK: spfile or pfile
3. Ok but not mandatory: Re: alter system checkpoint necessary?
4. OK. Or use the CATALOG command to 'register' them in the control file.
5. All parameters can be important. I will suggest to note the FORMAT ... so that you know where the backups are. With the following script you backup all possible ;-)
RMAN> run {
allocate channel ch1 type disk format '/db/ARON/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
allocate channel ch2 type disk format '/db/ARON/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup
incremental level 0
database
plus archivelog delete input;
backup current controlfile;
backup spfile;
release channel ch1;
release channel ch2;
}5a. That is always good. Don't forget ORACLE_HOME.
6. Always good.
7. To save space that is good.
Bye, Aron

RMAN failure for "archive-log ... not found in controlfile"

Recovery Manager: Release 8.1.6.0.0 - Production
RMAN> connect target sys/XXXX@cldb;
2> connect catalog rman/XXXX@rmandb1;
3>
4> resync catalog;
5>
6> # Backup the database
7> run {
8> allocate channel ch1 type disk;
9> backup incremental level 0 format
10> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_%t_%s_%p' database;
11> sql 'alter system archive log current';
12> }
13>
14> # Backup the archived redo logs
15> run {
16> allocate channel ch1 type disk;
17>
18> backup incremental level 0 format
19> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_%t_%s_%p' archivelog all;
20> sql 'alter system archive log current';
21> }
22>
23> # Backup the control file
24> run {
25> allocate channel ch1 type disk;
26> sql 'alter database backup controlfile to trace';
27> copy current controlfile to
28> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/controlfile.bak';
29> }
30>
31>
RMAN-06005: connected to target database: CLDB (DBID=1292102281)
RMAN-06008: connected to recovery catalog database
RMAN-03022: compiling command: resync
RMAN-03023: executing command: resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel ch1: starting incremental level 0 datafile backupset
RMAN-08502: set_count=816 set_stamp=422358010 creation_time=22-FEB-01
RMAN-08010: channel ch1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00001 name=/opt/orabase/oradata/cldb/system01.dbf
---snip----
more like this
---snip----
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_422358010_816_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:01:46
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql
RMAN-08031: released channel: ch1
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: backup
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=817 set_stamp=422358179 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=85 recid=2610 stamp=422352397
RMAN-08504: input archivelog thread=1 sequence=86 recid=2611 stamp=422352397
----snip----
more similar stuff here
----snip----
RMAN-08504: input archivelog thread=1 sequence=140 recid=2732 stamp=422358121
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_422358179_817_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:00:17
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=818 set_stamp=422358197 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
----snip----
more like this
----snip----
RMAN-08504: input archivelog thread=1 sequence=164 recid=2756 stamp=422358123
RMAN-08504: input archivelog thread=1 sequence=165 recid=2757 stamp=422358123
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAG E STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel ch1
RMAN-10035: exception raised in RPC: ORA-19571: archived-log recid 2011 stamp 419161314 not found in controlfile
RMAN-10031: ORA-19571 occurred during call to DBMS_BACKUP_RESTORE.BACKUPARCHIVEDLOG
I added the resync catalog command to the backup. But I am still getting this error. What is happening? I have the control_file_record_keep_time = 14 in the paramater file. Do I need to change this to something greater?
null

The error message is pointing to an inconsistency between what RMAN "thinks"
should be there and what is in control files.
There are a few things you can try to do
1. Compare V$LOG, V$LOGFILE, etc. Some of these views are based on control files
2. Shutdown and restart the instance.
This may help in synchronizing control files
with internal structures.
3. Trace RMAN session using oradebug and even 10046 to find out what it is doing
4. Dump entire controlfile to trace using
alter session set events 'immediate trace name controlf level 10';
Or dump loghist only
alter session set events 'immediate trace name loghist level 4';
This will dump 2**level entries.
5. Re-create controlfiles with CREATE CONTROLFILE
Regards,
Sev

Scheduling Rman backup in windows

Hi all,
I need to configure backup in Rman using the task scheduler in windows. I have placed 2 scripts 1 is batch file and 2nd is sql file with the below contents. When i ran the batch file the process is only getting logged into RMAN prompt but not executing the sql statements, how can i schedule it?
Version: 9i
OS: Windows server 2003
Bat file
rman target=sys/oracle@orcl1
@'d:\oracle\rman\backup.sql'
sql file
run
backup archivelog all;
delete noprompt obsolete;
}

user10724679 wrote:
Hi all,
I need to configure backup in Rman using the task scheduler in windows. I have placed 2 scripts 1 is batch file and 2nd is sql file with the below contents. When i ran the batch file the process is only getting logged into RMAN prompt but not executing the sql statements, how can i schedule it?
Version: 9i
OS: Windows server 2003
Bat file
rman target=sys/oracle@orcl1
@'d:\oracle\rman\backup.sql'
sql file
run
backup archivelog all;
delete noprompt obsolete;
}Change it like below and it will work
Bat file
rman target=sys/oracle@orcl1 @'d:\oracle\rman\backup.sql'

Rman, no datafile backup.

Dear...
I have one scenario.
RMAN Backup - Yesterday.
Datafile added today, and it lost in evening. How can one restore/recover datafile using RMAN, as datafile was not backed up in last RMAN backup.
Version : 10.2.0.1.0
Regards.

YES, here is below.
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC thread=1 sequence=18
creating datafile file number=7 name=C:\ORACLE\ORADATA\ORCL\USERS03.DBF
RMAN> backup database;
Starting backup at 21-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
input datafile file number=00002 name=C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
input datafile file number=00003 name=C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
input datafile file number=00005 name=C:\ORACLE\ORADATA\ORCL\EXAMPLE01.DBF
input datafile file number=00006 name=C:\ORACLE\ORADATA\ORCL\USERS02.DBF
input datafile file number=00004 name=C:\ORACLE\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 21-FEB-12
channel ORA_DISK_1: finished piece 1 at 21-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_21\O1_MF_NNNDF_TAG20120221T132643_7N6MKWPX_.BKP tag=TAG20120221T132643 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 21-FEB-12
Starting Control File and SPFILE Autobackup at 21-FEB-12
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_21\O1_MF_S_775834060_7N6MMO5Q_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 21-FEB-12
RMAN> exit
SQL> alter tablespace users add datafile 'C:\ORACLE\ORADATA\ORCL\USERS03.dbf' size 10m;
Tablespace altered.
SQL>
SQL> alter system switch logfile;
System altered.
SQL> startup force mount exclusive restrict;
ORACLE instance started.
Total System Global Area 778387456 bytes
Fixed Size                  1374808 bytes
Variable Size             310379944 bytes
Database Buffers          461373440 bytes
Redo Buffers                5259264 bytes
Database mounted.
SQL> drop database;
Database dropped.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>    exit
C:\Users\bn2676>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 21 13:51:27 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 778387456 bytes
Fixed Size                  1374808 bytes
Variable Size             310379944 bytes
Database Buffers          461373440 bytes
Redo Buffers                5259264 bytes
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\Users\bn2676>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Feb 21 13:51:52 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (not mounted)
RMAN> restore controlfile from 'C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_21\O1_MF_S_775834060_7N6MMO5Q_.BKP';
Starting restore at 21-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=63 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL
output file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL
Finished restore at 21-FEB-12
RMAN> sql 'alter database mount';
sql statement: alter database mount
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 21-FEB-12
Starting implicit crosscheck backup at 21-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=63 device type=DISK
Crosschecked 8 objects
Finished implicit crosscheck backup at 21-FEB-12
Starting implicit crosscheck copy at 21-FEB-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 21-FEB-12
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC
File Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_19_7N6NXV4M_.ARC
File Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_21\O1_MF_S_775834060_7N6MMO5Q_.BKP
File Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_02_21\O1_MF_S_775834547_7N6N2WHN_.BKP
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to C:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
channel ORA_DISK_1: restoring datafile 00002 to C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
channel ORA_DISK_1: restoring datafile 00003 to C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
channel ORA_DISK_1: restoring datafile 00004 to C:\ORACLE\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: restoring datafile 00005 to C:\ORACLE\ORADATA\ORCL\EXAMPLE01.DBF
channel ORA_DISK_1: restoring datafile 00006 to C:\ORACLE\ORADATA\ORCL\USERS02.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_21\O1_MF_NNNDF_TAG20120221T132643_7N6MKWPX_.BKP
channel ORA_DISK_1: piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_02_21\O1_MF_NNNDF_TAG20120221T132643_7N6MKWPX_.BKP tag=TAG20120221T132643
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:56
Finished restore at 21-FEB-12
R recover database;
Starting recover at 21-FEB-12
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 18 is already on disk as file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC
archived log for thread 1 with sequence 19 is already on disk as file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_19_7N6NXV4M_.ARC
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC thread=1 sequence=18
creating datafile file number=7 name=C:\ORACLE\ORADATA\ORCL\USERS03.DBF
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_18_7N6MQBWS_.ARC thread=1 sequence=18
archived log file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_02_21\O1_MF_1_19_7N6NXV4M_.ARC thread=1 sequence=19
unable to find archived log
archived log thread=1 sequence=20
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/21/2012 13:54:04
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 20 and starting SCN of 1226889
RMAN> sql 'alter database open resetlogs';
sql statement: alter database open resetlogs
RMAN> exit
Recovery Manager complete.
C:\Users\bn2676>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 21 13:54:42 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select file_name from dba_data_files where tablespace_name='USERS';
FILE_NAME
C:\ORACLE\ORADATA\ORCL\USERS01.DBF
C:\ORACLE\ORADATA\ORCL\USERS02.DBF
C:\ORACLE\ORADATA\ORCL\USERS03.DBF
SQL>

Restore tablespace in RMAN is not working

Friends,
OS: RHEL AS 3.0
DB: 9iR2
New to RMAN
I am testing RMAN in our R&D server.
I just deleted one table in scott which is in the users tablespace.
then i went to rman.
SQL 'ALTER TABLESPACE users OFFLINE IMMEDIATE';
RESTORE TABLESPACE users;
RECOVER TABLESPACE users;
SQL 'ALTER TABLESPACE users ONLINE';
after that, i logged in to sqlplus as scott.
but i didnt find the table which i deleted.
I know i can restore the table by point in time recovery using SCN.
but why the above rman command is not working?
where im making mistake?
thanks

Hi there,
This wont work as the recovery you tried and did was a "complete recovery".The dropped table will come back with an "incomplete recovery".You just restored the datafile from the backup.Table drop is not an "error".You wanted it to happen , you did that.Its not an error for oracle.So you need to do "incomplete recovery".
I guess following might be useful for you.yo u need to recover till the time when the table was existing and you will lose data beyond that point.so thats why it is called incomplete recovery.
http://www.oracle-base.com/articles/9i/RecoveryManager9i.php
http://download-uk.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmconc2.htm
Cheers,
Aman....

RMAN vs SQL

Similar Messages

Maybe you are looking for