RMAN Failure

Hi,
Any body pz help here what may be the issue and solution
Tonight’s RMAN backup has failed with the following errors:
Starting backup at 07-OCT-09
could not read file header for datafile 5 error reason 1
could not read file header for datafile 6 error reason 1
could not read file header for datafile 9 error reason 1
could not read file header for datafile 10 error reason 1
could not read file header for datafile 11 error reason 1
could not read file header for datafile 12 error reason 1
could not read file header for datafile 13 error reason 1
could not read file header for datafile 14 error reason 1
could not read file header for datafile 15 error reason 1
could not read file header for datafile 16 error reason 1
could not read file header for datafile 17 error reason 1
could not read file header for datafile 18 error reason 1
could not read file header for datafile 22 error reason 1
could not read file header for datafile 23 error reason 1
could not read file header for datafile 24 error reason 1
could not read file header for datafile 30 error reason 1
could not read file header for datafile 31 error reason 1
could not read file header for datafile 32 error reason 1
could not read file header for datafile 33 error reason 1
could not read file header for datafile 43 error reason 1
could not read file header for datafile 44 error reason 1
could not read file header for datafile 45 error reason 1
could not read file header for datafile 46 error reason 1
could not read file header for datafile 49 error reason 1
could not read file header for datafile 5 error reason 1
could not read file header for datafile 6 error reason 1
could not read file header for datafile 9 error reason 1
could not read file header for datafile 10 error reason 1
could not read file header for datafile 11 error reason 1
could not read file header for datafile 12 error reason 1
could not read file header for datafile 13 error reason 1
could not read file header for datafile 14 error reason 1
could not read file header for datafile 15 error reason 1
could not read file header for datafile 16 error reason 1
could not read file header for datafile 17 error reason 1
could not read file header for datafile 18 error reason 1
could not read file header for datafile 22 error reason 1
could not read file header for datafile 23 error reason 1
could not read file header for datafile 24 error reason 1
could not read file header for datafile 30 error reason 1
could not read file header for datafile 31 error reason 1
could not read file header for datafile 32 error reason 1
could not read file header for datafile 33 error reason 1
could not read file header for datafile 43 error reason 1
could not read file header for datafile 44 error reason 1
could not read file header for datafile 45 error reason 1
could not read file header for datafile 46 error reason 1
could not read file header for datafile 49 error reason 1
could not read file header for datafile 5 error reason 1
released channel: node_1
released channel: node_2
released channel: node_3
released channel: node_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 10/07/2009 22:31:32
RMAN-06056: could not access datafile 5
RMAN>
Thanks,

Error:     RMAN 6169
Text:     could not read file header for datafile %s error reason %s
Cause:     The specified datafile could not be accessed. The reason codes are: 1
     - filename is MISSINGxx in the controlfile 2 - file is offline 3 - file
     is not verified 4 - DBWR could not find the file 5 - unable to open
     file 6 - I/O error during read 7 - file header is corrupt 8 - file is
     not a datafile 9 - file does not belong to this database 10 - file
     number is incorrect 12 - wrong file version 15 - controlfile is not
     current
Action:     If the error can be corrected, do so and retry the operation. The SKIP
     option can be used to ignore this error during a backup.
Khurram

Similar Messages

Rman : 'failure during compilaton of command'

Hello friends,
I am new to Rman backup.
However, I attempted one for the first time, with a script file 'full_backup.sh'. I am having oracle 8i in Unix server.
Rman did run and some files have been created in the backup directory. But towards the end, there was this message.
RMAN-03022 : compiling command : backup
RMAN-03026 : error recovery releasing channel resources
RMAN- 08031 : released channel : c1
RMAN- 08031 : released channel : c2
RMAN- 08031 : released channel : c3
ERROR MESSAGE STACK FOLLOWS
RMAN - 03002 : failure during compilation of command
RMAN - 03013 : command type : backup
RMAN - 06089 : archival log /home2/oracle/arch/arch_1_14932.arc not found or out of sync with catalog.
I would like to know
1. whether I have successfully completed backup using the RMAN script
2. What is the significance of the above message.
3. Of course, I have deleted some archive log files, of which the last one could be /arch_1_14932.arc, before ever running RMAN.
please help,
regards,
thomaskprakash

Hi,
can you paste the content of the script on the board? well here i am not in a position to comment on anything.for a instance i guess that you have some archivelog missingm,and this is the reason the rman came up with these texts.
thanks
Alok

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

Rman backup error in oracle grid control

Hi,
I am able to find rman failure and status is Failed so where we can find the error messages in oracle enterprise manager 10g grid control to make sure that it should not happen in future.
Appreciated for your inputs.
Thanks
Prakash

Hi,
I am able to find rman failure and status is Failed so where we can find the error messages in oracle enterprise manager 10g grid control to make sure that it should not happen in future.Refer Link below:
http://www.oracle.com/technology/pub/articles/havewala-rman-grid.html
Check from point 15
Regards,
X A H E E R

Rman duplication fails with RMAN-00600

Hi All,
I'm trying to perform a database duplication from a prod server to a non prod one with ORacle 11gR2.
I'm performing a backup-based duplication without target connection from DEV3 database to DEV1 database. I followed the steps mentionned in the "backup & Recovery Guide" http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmdupdb.htm
Here are the steps I followed:
1. I configured my spfile of the auxiliary database like the target one. I also added these lines to change the location of the restores:
SQL> alter system set log_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DE V1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo' scope=spfile;
SQL> alter system set db_file_name_convert='/u04/DEV3/rdo','/u04/DEV1/rdo','/u03/DEV3/rdo','/u03/DEV1/rdo','/u02/DEV3/rdo','/u02/DEV1/rdo','/u02/DEV3/dbf/DEV3','/u02/DEV1/dbf/DEV1' scope=spfile;
2. I then shutdown the database, and start it in nomount mode.
3. I connect to the auxiliary database, and the recovery catalog
4. I run the following rman duplication command:
RUN{
DUPLICATE DATABASE DEV3 to DEV1;
The restore succeeds but at the end, the recovery ends with the following error:
channel ORA_AUX_DISK_6: reading from backup piece /RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman
channel ORA_AUX_DISK_4: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_136.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_4: restored backup piece 2
channel ORA_AUX_DISK_4: restore complete, elapsed time: 02:24:10
channel ORA_AUX_DISK_6: piece handle=/RMAN/DEV3/DEV3_0_14:27:01-05-31-2011_2_138.rman tag=LVL0_DB_BKP
channel ORA_AUX_DISK_6: restored backup piece 2
channel ORA_AUX_DISK_6: restore complete, elapsed time: 02:25:09
Finished restore at 06/06/11 15:22:58
contents of Memory Script:
catalog clone datafilecopy "/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile 3 to datafilecopy
"/u02/DEV1/dbf/DEV1/undotbs01.dbf";
switch clone datafile all;
executing Memory Script
cataloged datafile copy
datafile copy file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf RECID=70 STAMP=753117778
datafile 3 switched to datafile copy
input datafile copy RECID=70 STAMP=753117778 file name=/u02/DEV1/dbf/DEV1/undotbs01.dbf
datafile 1 switched to datafile copy
input datafile copy RECID=71 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=72 STAMP=753117780 file name=/u02/DEV1/dbf/DEV1/sysaux01.dbf
contents of Memory Script:
set until scn 7241504550365;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 06/06/11 15:23:15
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
using channel ORA_AUX_DISK_3
using channel ORA_AUX_DISK_4
using channel ORA_AUX_DISK_5
using channel ORA_AUX_DISK_6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Can someone please help me resolve this issue???it's quite urgent.
Thank you,
Farah

I am facing same error, did any of you find a resolution yet?
contents of Memory Script:
set until scn 7243533883622;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 10/12/11 19:33:12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [8029] [1] [] [] []
Wed Oct 12 19:33:14 CEST 2011 Remove the lock file
ERROR: RMAN FAILUR
I see many kblockd processes, can this be an indication:
applprod@gvaebsdb3:~ $ ps -ef|grep kblockd
root 231 211 0 Oct05 ? 00:00:00 [kblockd/0]
root 232 211 0 Oct05 ? 00:00:00 [kblockd/1]
root 233 211 0 Oct05 ? 00:00:00 [kblockd/2]
root 234 211 0 Oct05 ? 00:00:00 [kblockd/3]
root 235 211 0 Oct05 ? 00:00:00 [kblockd/4]
root 236 211 0 Oct05 ? 00:00:00 [kblockd/5]
root 237 211 0 Oct05 ? 00:00:00 [kblockd/6]
root 238 211 0 Oct05 ? 00:00:00 [kblockd/7]
root 239 211 0 Oct05 ? 00:00:00 [kblockd/8]
root 240 211 0 Oct05 ? 00:00:00 [kblockd/9]
root 241 211 0 Oct05 ? 00:00:00 [kblockd/10]
root 242 211 0 Oct05 ? 00:00:00 [kblockd/11]
root 243 211 0 Oct05 ? 00:00:00 [kblockd/12]
root 244 211 0 Oct05 ? 00:00:00 [kblockd/13]
root 245 211 0 Oct05 ? 00:00:00 [kblockd/14]
root 246 211 0 Oct05 ? 00:00:00 [kblockd/15]
Thanks,
Horia

Active duplication question

I tried to use active duplication recently and ran into an issue. When I ran the job from the auxiliary database server it failed. When I ran it from the target(source) database server, it ran fine. Seems odd and am wondering why.
Here is the log I got when running on the auxiliary database server:
channel c1: starting datafile copy
copying current control file
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: x5
released channel: x6
released channel: x7
released channel: x8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/23/2011 11:32:41
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on c1 channel at 03/23/2011 11:32:41
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
ORA-17629: Cannot connect to the remote database server
RMAN>
Recovery Manager complete.
So the job connected to both databases, created the script, created the control files on the auxiliary server an stopped and restarted that but failed when it got into the copy file section of the script.
Again, running the exact same thing from the target( source) server ran without issue.
FYI...here is the duplicaiton which was run from both servers
$ORACLE_HOME/bin/rman <<EOF>> dev1-2011-03-23_1.out
connect auxiliary sys/samepass@dev1
connect target sys/samepass@prod
run
allocate channel c1 device type DISK;
allocate channel c2 device type DISK;
allocate channel c3 device type DISK;
allocate channel c4 device type DISK;
allocate auxiliary channel x5 device type DISK;
allocate auxiliary channel x6 device type DISK;
allocate auxiliary channel x7 device type DISK;
allocate auxiliary channel x8 device type DISK;
duplicate target database to dev1 from active database NOFILENAMECHECK;
EOF
echo "finished"
exit

Hi Werner,
Sorry for my badly phrased question.
True initially it works from both sides.
But halfway it stops working if ran from the aux server.
The question should have been:
Does sqlplus than still works ? (so just after the rman failure)
Maybe the OP can align both tnsnames.ora files and spot a difference?
If the listener(s) or the instance(s) is/are the problem it wouldn't work from both sides.
Regards,
Tycho

RMAN-03009: failure of delete command on ... ORA-19606: Cannot copy or rest

one server using 11.2.0.1.0 under Suse Linux
configured catalog db, main db & jobs & ... almost everything with enterprise manager
keep backups 14 days
To make 14 full online dumps I had to aktive the archive mode and try to get rid of thoose unwanted additional files.
Additional I make every night (less til no db activity) a dump and compress it myself.
After some days the backupjob complain that it can not delete old files.
EM / manage all backups / crosscheck all(
CROSSCHECK BACKUPSET;
CROSSCHECK COPY;
sucessful
EM / manage all backups / delete old backups
DELETE NOPROMPT OBSOLETE;
failed.
script result
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 17:20:55 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: <SID> (DBID=773091283)
RMAN>
connected to recovery catalog database
RMAN>
echo set on
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=196 device type=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_<SID>.f
Backup Set 18750 23-AUG-10
Backup Piece 18754 23-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/backupset/2010_08_23/o1_mf_nnndf_BACKUP_<SID>CH0_673c0hbp_.bkp
Backup Set 18751 23-AUG-10
Backup Piece 18755 23-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/backupset/2010_08_23/o1_mf_nnndf_BACKUP_<SID>CH0_673c0hbo_.bkp
Backup Set 19479 24-AUG-10
Backup Piece 19482 24-AUG-10 /tmp/o0lm3qh9_1_1
Backup Set 19490 24-AUG-10
Backup Set 20087 24-AUG-10
Backup Piece 20089 24-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/autobackup/2010_08_24/o1_mf_s_727891232_677n40r3_.bkp
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/07/2010 17:20:57
ORA-19606: Cannot copy or restore to snapshot control file
exit;
Recovery Manager complete.
google found some questions, but not fittung answers.
So far:
- I checked the folder & users rights.
- I found some /tmp/ files - yes I "backup" the backuped archivelogs to-delete files in /tmp - I only active archivelogmode so I can onlinebackup
- I managed to login via rman and execute DELETE OBSOLETE manual - result above.
- Actual I delete the set one by one to find the problem set. (delete backupset 12345 ) from the list manually.
Some a good idea what went wrong?
additional: Is there a way to let oracle delete the empy archvielog-directories after deleting the logs within?
18:00- the command "RMAN> BACKUP CURRENT CONTROLFILE" also fails.
Edited by: 793286 on 07.09.2010 09:00

Meanwhile I managed to delete all backupsets one by one.
The problem with $ORACLE_HOME/dbs/snapcf_<SID>.f persists.
cd $ORACLE_HOME/dbs
mv snapcf_<SID>.f snapcf_<SID>.f.bak
# replaced actual dbsidname with <SID>
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_TARMED1P.f
Do you really want to delete the above objects (enter YES or NO)? y
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/08/2010 09:44:07
ORA-19606: Cannot copy or restore to snapshot control file
mv snapcf_<SID>.f.bak snapcf_<SID>.fRMAN> backup current controlfile;
Starting backup at 08-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 08-SEP-10
channel ORA_DISK_1: finished piece 1 at 08-SEP-10
piece handle=/srv/ora/data/flash_recovery_area/TARMED1P/backupset/2010_09_08/o1_mf_ncnnf_TAG20100908T095000_68gj1b2m_.bkp tag=TAG20100908T095000 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 08-SEP-10
Starting Control File and SPFILE Autobackup at 08-SEP-10
piece handle=/srv/ora/data/flash_recovery_area/TARMED1P/autobackup/2010_09_08/o1_mf_s_729165003_68gj1d1b_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 08-SEP-10
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_<SID>.f
Do you really want to delete the above objects (enter YES or NO)? y
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/08/2010 09:52:37
ORA-19606: Cannot copy or restore to snapshot control file
No different effect, if I changed the filename via 2nd terminal to .bak or not.
RMAN> delete controlfilecopy 3831;
will fail, if the file exists or not.
Any chance to reset/kill that file?
Is there a need to restart the dbms after rename the file?

Error while taking RMAN back up - RMAN-03009: failure of backup command ..

Hi Experts,
I am trying to take RMAN back up but at the end I get this error message.. I found a solution at http://www.oracle-base.com/articles/9i/RecoveryManager9i.php
But this is of oracle 9i. Can I use it on 10g too ?
So is this Step correct ?
1) First create a user to hold the recovery catalog:
a) CONNECT sys/password@w2k1 AS SYSDBA
b) GRANT connect, resource, recovery_catalog_owner TO rman;
2) Then create the recovery catalog:
a) C:>rman catalog=rman/rman@w2k1
b) RMAN> create catalog tablespace "RMAN";
c) RMAN> exit
3) Register Database
a) C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
b) RMAN> register database;
c) Existing user-created backups can be added to the catalog using: (*So far no Back up taken so I guess this step can be ignored*)
i) RMAN> catalog datafilecopy 'C:\Oracle\Oradata\TSH1.dbf';
ii) RMAN> catalog archivelog 'log1', 'log2', 'log3', ... 'logN';
4) Full Backup Configuration
RMAN> configure retention policy to recovery window of 7 days;
RMAN> configure default device type to disk;
RMAN> configure controlfile autobackup on;
RMAN> configure channel device type disk format 'C:\Oracle\Admin\W2K2\Backup%d_DB_%u_%s_%p';
5) Full back up
RMAN> run {
backup database plus archivelog;
delete noprompt obsolete;
6) RMAN> resync catalog;
Starting backup at 15-MAY-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00006 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
60430230208_DB.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\UNDOTBS01.DB
F
input datafile fno=00007 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
60430230208_IND.DBF
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSAUX01.DBF
input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\EXAMPLE01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 15-MAY-10
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
03
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
channel ORA_DISK_1: starting piece 1 at 15-MAY-10
channel ORA_DISK_1: finished piece 1 at 15-MAY-10
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\BACKUPSET\2010_05
_15\O1_MF_NCNNF_TAG20100515T045136_5YX3TTFT_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:17
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/15/2010 05:11:21
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
03
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
RMAN>
Thanks & Regards,
Ranjith John

Provided you consult the 10g RMAN documentation and the online error documentation: yes.
But apparently you didn't check documentation, not even the error messages!!!!! Why?
You are backing up to the Flash Recovery Area, and the error messages mean too much space is occupied.
How to configure the Flash Recovery Areea is fully documented in the Backup and Recovery manual for 10g at http://tahiti.oracle.com
READ IT.
Please do not ask a volunteer to abstract it.
Sybrand Bakker
Senior Oracle DBA

Problem in recovery from RMAN backup in case of disk failure

Hi
I have Oracle 9.2.0.1.0 on Windows. Full Hot RMAN backup of database is scheduled on daily basis. I am taking backup on disks. And then i do manually copy them on tapes. If any disk failure occurs than can i recover database completely in this scenario. If tried restoing that backup on different machine as given below
set ORACLE_SID=<name>
rman target sys/<pwd>@ORACLE_SID nocatalog
startup nomount
restore spfile
create pfile from spfile
startup nomount pfile
alter database mount
restore database
Everything worked fine till above steps. Now i will execute last step.
recover database
Here it gives error:-RMAN-06054: media recovery requesting unknown log: thread 1 scn 264750
Still i typed
alter database open resetlogs
Now i can open my database, But is it recovered completely? Or there is loss of some data? Why it is giving this error?
Thanks in advance. Waiting for reply.

I can understand the confusion with this whole concept.
What I meant by all archivelogs is all the archivelogs that were backed up with the backup itself. Again, it is essential to ensure that you archive the current redo log AFTER the backup is performed and then back those archivelogs too. Good thing is, RMAN will take care of this for you if you backup the archivelogs with the BACKUP DATABASE command and/or backup the archivelogs AFTER you run the BACKUP DATABASE command.
Once you've mounted the controlfile and CATALOG the archivelogs, you can go into SQL*Plus and issue the following query:
select SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE# from v$archived_log
order by FIRST_TIME;This will tell you what archivelog is the latest. Logs generated during the backup may also provide the necessary information. Performing Disaster Recovery should help to understand the full process.
The ONLINELOG directory in FRA is only populated if you've configured your redo logs to be stored there. However, you are on 9i...right? If so 9i doesn't utilize a FRA.
HTH
Edited by: ebrian on Oct 3, 2008 1:08 PM

RMAN (DP6.0) backup failure on Oracle10g

Hello,
I am using DP6.0 with Oracle10g environment for backup.
While I was able to successfully able to allocate the channels I am getting the below error message stack when the backup script is executed.
Thanks
RMAN> CONNECT TARGET *
2> run {
3> allocate channel 'dev_0' type 'sbt_tape'
4> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=<SID>,OB2BARLIST=<SID>BAZAORACLE,OB2BARHOSTNAME=server.xx.yy)';
5> backup incremental level 0
6> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
7> database;
8> sql 'alter system archive log current';
9> backup
10> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
11> archivelog all;
12> delete archivelog until time 'sysdate-1';
13> backup
14> format '<SID>BAZAORACLE<<SID>_%s:%t:%p>.dbf'
15> current controlfile;
16> }
17> EXIT
connected to target database: <SID> (DBID=3497973964)
using target database control file instead of recovery catalog
allocated channel: dev_0
channel dev_0: sid=134 devtype=SBT_TAPE
channel dev_0: Data Protector A.06.00/DPWIN_00268
released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/21/2007 12:00:20
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_7:625838365:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     The database reported error while performing requested operation.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/21/2007 12:00:20
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_7:625838365:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     Oracle Recovery Manager completed with errors.
[Major] From: [email protected] "<SID>" Time: 21.6.2007 12:00:20
     Backup of target database failed
*************************************************************************************

I changed the tapes and backup drive but problem is standing. Now the message is:
released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 07/04/2007 09:11:48
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_15:627037853:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
[Critical] From: [email protected] "LTO2-1_server" Time: 4.7.2007 9:12:01
IPC Cannot Allocate Shared Memory Segment
     The database reported error while performing requested operation.
[Normal] From: [email protected] "LTO2-1_server" Time: 4.7.2007 9:12:07
     scsi5:0:1:0C
     Medium header verification completed, 0 errors found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 07/04/2007 09:11:48
ORA-19506: failed to create sequential file, name="<SID>_BAZA_ORACLE<<SID>_15:627037853:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(8010)
Recovery Manager complete.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
     Oracle Recovery Manager completed with errors.
[Major] From: [email protected] "<SID>" Time: 4.7.2007 9:11:49
     Backup of target database failed.
Please help me.... I don't have backup 20 days...

NEED TO RECOVER A DATABASE USING RMAN with CONTROL FILE AND NO RMAN CATALOG, DISK FAILURE..

Hello All,
The disk failure caused our production data on the disk to be resotred with the backup data available and recovered through RMAN with cotrolfile , and no catalog DB is configured.
I had the restored the spfile and control file then recovered the database,
startup nomount;
RESTORE SPFILE FROM ' path ' ;
Shutdown immediate;
startup nomount
Restore controfile from autobackup;
restore database;
[AT POINT , A MESSAGE PROMPTED LIKE " failur of restored command - some targets not found" (thinking may be few archives are not found, i proceeded to incomeplete recovery of DB) ]
recover database;
Finished reocvery .
Now in the Grid control i see that 60 blocks of a particular datafile are corrupted and needs recovery. Do i need to get the data file resotred again and recover it or any simple way to recover this data file
When i perform the block recovery , it says recovery failed and when i run the data file recovery it succeeds. Please provide you inputs to recover the database as it is production BI database and pretty critical to our client.
Thanks for your valuable time in advance.
Regards,
Ran G.

These is a common problem if the object are created due to NOLOGGIN option. If you check most of the object which are facing block corruption is indexes .
Use the below query to check the objects :
It will map each block from v$database_block_corruption to either a segment or if the block is free.
$ sqlplus / as sysdba
set pagesize 2000
set linesize 250
SELECT e.owner, e.segment_type, e.segment_name, e.partition_name, c.file#
, greatest(e.block_id, c.block#) corr_start_block#
, least(e.block_id+e.blocks-1, c.block#+c.blocks-1) corr_end_block#
, least(e.block_id+e.blocks-1, c.block#+c.blocks-1)
- greatest(e.block_id, c.block#) + 1 blocks_corrupted
, null description
FROM dba_extents e, v$database_block_corruption c
WHERE e.file_id = c.file#
AND e.block_id <= c.block# + c.blocks - 1
AND e.block_id + e.blocks - 1 >= c.block#
UNION
SELECT s.owner, s.segment_type, s.segment_name, s.partition_name, c.file#
, header_block corr_start_block#
, header_block corr_end_block#
, 1 blocks_corrupted
, 'Segment Header' description
FROM dba_segments s, v$database_block_corruption c
WHERE s.header_file = c.file#
AND s.header_block between c.block# and c.block# + c.blocks - 1
UNION
SELECT null owner, null segment_type, null segment_name, null partition_name, c.file#
, greatest(f.block_id, c.block#) corr_start_block#
, least(f.block_id+f.blocks-1, c.block#+c.blocks-1) corr_end_block#
, least(f.block_id+f.blocks-1, c.block#+c.blocks-1)
- greatest(f.block_id, c.block#) + 1 blocks_corrupted
, 'Free Block' description
FROM dba_free_space f, v$database_block_corruption c
WHERE f.file_id = c.file#
AND f.block_id <= c.block# + c.blocks - 1
AND f.block_id + f.blocks - 1 >= c.block#
order by file#, corr_start_block#;
Below oracle support note will help you :
ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING - Error explanation and solution (Doc ID 794505.1)
The Gains and Pains of Nologging Operations (Doc ID 290161.1)
SQL> select d.NAME as DBF_NAME, t.NAME as TS_NAME, d.UNRECOVERABLE_CHANGE# as NOLOG_CHNG#, to_char(d.UNRECOVERABLE_TIME, 'Dy DD-Mon-YYYY HH24:MI:SS') as NOLOG_TIME from V$DATAFILE d join V$TABLESPACE t on d.TS# = t.TS# order by t.NAME;
Thanks,
gssdba.wordpress.com

RMAN Cloning - Active Duplication failure

Platform : HP-UX B.11.31 U ia64
Oracle Version: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
connected to auxiliary database (not started)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/07/2012 09:35:41
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01078: failure in processing system parameters
ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENERS_SALES_DB'
Any idea on how to resolve this error / what causes this error much appreciated.

I am facing issue on active database duplication and has below issue. Can any one help me on this?
RMAN> connect target sys@Pa305
connected to target database: PA305 (DBID=2787277616)
RMAN> connect auxiliary sys@Pb305
connected to auxiliary database: PB305 (not mounted)
RMAN> DUPLICATE TARGET DATABASE
TO 'PB305'
FROM ACTIVE DATABASE
2> 3> 4> ;
Starting Duplicate Db at 31-JUL-2012 17:20:07
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=2838 instance=PB3051 device type=DISK
contents of Memory Script:
sql clone "alter system set control_files =
''+DG_075_DATA01/PB305/controlfile/current.270.790104009'', ''+DG_075_FRA01/PB305/controlfile/current.286.790104009'' comment=
''Set by RMAN'' scope=spfile";
sql clone "alter system set db_name =
''PA305'' comment=
''Modified by RMAN duplicate'' scope=spfile";
sql clone "alter system set db_unique_name =
''PB305'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
backup as copy current controlfile auxiliary format '+DG_075_DATA01/PB305/controlfile/current.269.790104009';
restore clone controlfile to '+DG_075_FRA01/PB305/controlfile/current.288.790104009' from
'+DG_075_DATA01/PB305/controlfile/current.269.790104009';
sql clone "alter system set control_files =
''+DG_075_DATA01/PB305/controlfile/current.269.790104009'', ''+DG_075_FRA01/PB305/controlfile/current.288.790104009'' comment=
''Set by RMAN'' scope=spfile";
shutdown clone immediate;
startup clone nomount;
alter clone database mount;
executing Memory Script
sql statement: alter system set control_files = ''+DG_075_DATA01/PB305/controlfile/current.270.790104009'', ''+DG_075_FRA01/PB305/controlfile/current.286.790104009'' comment= ''Set by RMAN'' scope=spfile
sql statement: alter system set db_name = ''PA305'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''PB305'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/31/2012 17:20:18
RMAN-06174: not connected to auxiliary database
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
RMAN>

RMAN-03002: failure of Duplicate Db command at 06/01/2013 16:47:33

sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/01/2013 16:47:33
RMAN-05501: aborting duplication of target database
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 8064 and starting SCN of 13048058320848 found to restore
i am trying to duplicate a database, at the end it is getting finished with this error.
can any one help me fixing this one?

It is preferable to set an UNTIL point (to the latest available archivelog) when doing a DUPLICATE. Else, Oracle attempts a complete recovery and fails after the last archivelog it finds.
Hemant K Chitale

RMAN-03002: failure of recover command

Hi all,
I am testing a new backup and restore mechanism of a 11.2 system in Linux. A third mirror of the disks from the database server has been split and mounted in a media server. An RMAN backup was taken then, on tape, using HP Data Protector. Then, in the media server again, I mounted all the disk groups and removed all the files from ASM via asmcmd. With everything cleared, I proceeded in doing the following:
1. Started up nomount using an old PFILE.
2. Initiated an RMAN session and SET DBID, connected to the target and the catalog. Restore the SPFILE in a PFILE.
3. Shutdow and started up nomount with PFILE the newly created file (edited it first to comment out CLUSTER_DATABASE parameter, as the media server is not configured for this).
4. Restored the contorl file. This was done successfully.
5. Restored the database. This was done successfully.
6. Mounted the database and attempted to recover it. I received the following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/12/2013 09:42:24
RMAN-06094: datafile 1 must be restored
7. I attempted a recover from SQL*Plus; the error message was a little more helpful:
SQL> recover database using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
8. I checked my source database and the file name is as it appears above. But in the restored system, the file has a different name:
ASMCMD> pwd
+BT1_A_SYSTEM/BT1_A/DATAFILE
ASMCMD> ls -l SYSTEM*
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE JUL 11 16:00:00 Y SYSTEM.257.820514399
9. OK. I presume that this happened because we are using OMF. But, I was expecting RMAN to specify the full file names and thus restore them with their original names. The problem is now that the control file has the original file names, which cannot be found in the media server, where the restore took place. I am wondering if I should MOUNT the database after the control file restore and before I start the database restore, so RMAN might have the opportunity of renaming the file names in the control file.
Has anyone encountered this problem? I would appreciate some help.
Regards,
Takis.

That is correct Hemant. I latter realised my mistake.
When I mounted the database, the control file was opened. Then I repeated the restore. RMAN, this time was able to access the control file and rename dynamically the files, as they were restored and getting their new names.
So, I think, the correct sequence of events may be:
1, Check in ASM if the disk groups are mounted (lsdg). If not, mount the disk groups (alter diskgroup <dg_name> mount;).
2. Startup nomount (if no PFILE available, create a simple one with only db_name in it).
3. From RMAN, set DBID and then connect to target and catalog.
4. restore spfile to pfile from autobackup
5. restore control file(s) from autobackup
6. alter database mount
7. restore database
8. restore archivelog all
9. recover database
10. alter database open resetlogs
In my case, this worked, by enslarge. RMAN stopped when it run out of archived redo logs.
I then attempted, via SQL*Plus:
recover database using backup controlfile until cancel
When prompted, I typed: CANCEL
That was fine, but then, when I attempted:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 525336576 bytes disk space from 2147483648 limit
So, I needed to increase the parameter db_recovery_file_dest_size which I did (in the pfile; luckily I had available space in the disk group). I shut down and started up (mount). Then:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-00392: log 24 of thread 2 is being cleared, operation not allowed
ORA-00312: online log 24 thread 2: '+BT1_A_RECO'
So:
SQL> alter database clear unarchived logfile group 24;
Database altered.
SQL> alter database open resetlogs;
Database altered.
SQL> select * from dual;
D
X
Happy days!
Regards,
Takis.

RMAN-03002: failure of delete command

DB:10.2.0.3.0
OS:AIX 64 bits
Hi All,
We have configured backup default device on Disk.
On using the command within run block:
delete noprompt obsolete;
We get the error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 02/06/2009 11:07:04
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN>
Recovery Manager complete.
Return Code: 1
Now when we use the commmand :RMAN> delete noprompt obsolete device type disk;
We do not get the above error.
Question: Is it necessary to issue the command - "device type disk"; as above with "delete noprompt obsolete " though default backup device type is configured to DISK.Won't RMAN itself identify the default device type - Disk.
Thanks for your time!
Regards,

RMAN> show all;
starting full resync of recovery catalog
full resync complete
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%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 CHANNEL DEVICE TYPE DISK FORMAT '/production_dump/database/EW01/Backup%d_DB_%u_%s_%p_%T';
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 '/apps/ew01/oracle/10.2.0/dbs/snapcf_ew01.f'; # default
RMAN>
RMAN>

RMAN Failure

Similar Messages

Maybe you are looking for