RMAN LEVEL0 BACKUP FAIL

Use scripts to do level0 backup
scripts:
run {allocate channel c1 type disk;allocate channel c2 type disk;backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%T_%s_%p.dbf' databaseinclude current controlfile;release channel c1;release channel c2;}
Backup failed. Below is the log information:
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jul 2 23:30:09 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY0 (DBID=359019005)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%T_%s_%p.dbf' database
5> include current controlfile;
6> release channel c1;
7> release channel c2;
8> }
9>
10>
allocated channel: c1
channel c1: sid=218 devtype=DISK
allocated channel: c2
channel c2: sid=279 devtype=DISK
Starting backup at 02-JUL-12
channel c1: starting incremental level 0 datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00004 name=/database/oracle/oradata/PRIMARY0/datafile/o1_mf_users_7b1my5cr_.dbf
input datafile fno=00010 name=/oradata/primary0/datafile/data02.dbf
channel c1: starting piece 1 at 02-JUL-12
channel c2: starting incremental level 0 datafile backupset
channel c2: specifying datafile(s) in backupset
input datafile fno=00005 name=/database/oracle/oradata/PRIMARY0/datafile/o1_mf_users_7b1mykwz_.dbf
input datafile fno=00011 name=/oradata/primary0/datafile/data03.dbf
channel c2: starting piece 1 at 02-JUL-12
RMAN-03009: failure of backup command on c2 channel at 07/03/2012 00:11:10
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2backup/bkp_20120627_1992_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c2 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on c1 channel at 07/03/2012 01:54:26
ORA-19510: failed to set size of 3986777 blocks for file "/backup/nissandb2backup/bkp_20120627_1991_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c1 disabled, job failed on it will be run on another channel
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c2 channel at 07/03/2012 00:11:10
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2backup/bkp_20120627_1992_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
RMAN-03009: failure of backup command on c1 channel at 07/03/2012 01:54:26
ORA-19510: failed to set size of 3986777 blocks for file "/backup/nissandb2backup/bkp_20120627_1991_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
Recovery Manager complete.
Could you please help check the reason?

Thank for your reply.
Yesterday I only modified the script.
Now the script is :
run {
allocate channel c1 type disk maxpiecesize 5120M;
allocate channel c2 type disk maxpiecesize 5120M;
backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%
T_%s_%p_%U' database
include current controlfile;
release channel c1;
release channel c2;
But still failed.The log is:
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jul 3 23:30:11 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY0 (DBID=359019005)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 type disk maxpiecesize 5120M;
3> allocate channel c2 type disk maxpiecesize 5120M;
4> backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bk
p_%T_%s_%p_%U' database
5> include current controlfile;
6> release channel c1;
7> release channel c2;
8> }
9>
10>
allocated channel: c1
channel c1: sid=250 devtype=DISK
allocated channel: c2
channel c2: sid=245 devtype=DISK
Starting backup at 03-JUL-12
channel c1: starting incremental level 0 datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00004 name=/database/oracle/oradata/PRIMARY0/datafile/o1_m
f_users_7b1my5cr_.dbf
input datafile fno=00010 name=/oradata/primary0/datafile/data02.dbf
channel c1: starting piece 1 at 03-JUL-12
channel c2: starting incremental level 0 datafile backupset
channel c2: specifying datafile(s) in backupset
input datafile fno=00005 name=/database/oracle/oradata/PRIMARY0/datafile/o1_m
f_users_7b1mykwz_.dbf
input datafile fno=00011 name=/oradata/primary0/datafile/data03.dbf
channel c2: starting piece 1 at 03-JUL-12
RMAN-03009: failure of backup command on c2 channel at 07/04/2012 07:36:34
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1994_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c2 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on c1 channel at 07/04/2012 08:47:20
ORA-19510: failed to set size of 3986905 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1993_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c1 disabled, job failed on it will be run on another channel
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c2 channel at 07/04/2012 07:36:34
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1994_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
RMAN-03009: failure of backup command on c1 channel at 07/04/2012 08:47:20
ORA-19510: failed to set size of 3986905 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1993_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
Recovery Manager complete.
Now I modify the rman parameter:
CONFIGURE MAXSETSIZE TO UNLIMITED; --> CONFIGURE MAXSETSIZE TO 5G;
Any other things, I need to check or modify? Please help.

Similar Messages

Rman level0 backup failed

Hi All,
i have scheduled inc0 backup in of the tool on windows env which is backing up my db ervery sunday,but today when i checked out the log i found backup failed becaz of bellow errors...immediate reply is appretiate
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script inc0
RMAN-03002: failure of backup plus archivelog command at 11/29/2009 01:03:59
ORA-27072: File I/O error: write error on file "\\CNNKG-FP01\SHAREFILES\DATABASE\SSC\SSCR_7UKVHBU8_1_1.BAK", blockno 172929 (blocksize=8192)
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 64) The specified network name is no longer available.
With warm Regards

We have exactly the same problem, we make daily backups from 40 databases on Windows servers and daily backups of archivelogs to a Windows server on the network. Every week we have 1 to 5 failures.
Oracle does not support backups to a server on the network, but it does work, most of the time.
On http://groups.google.com/group/comp.databases.oracle.server/browse_thread/thread/fc37eb6827962c24/db9f251077e6042e you can find this problem too, but that is not for Windows. In Oracle Support you can find a solution, but again, not for Windows. But maybe it works? Another suggestion is to use smaller backupfiles. We use 2 GB max, I will try what happens when I change this to 1 GB max.
You should be aware that restoring can give similar problems. We succeeded in restoring databases from the network server, but not always. When RMAN refuses to restore the database from the network server, it may be a solution to rename the backuppieces in the RMAN catalog, for instance:
UPDATE RMAN.BP SET HANDLE=replace(handle,'\\SRV08D1\sharename\','E:\') where tag='TAG20090828T204552';
Then you can copy the backupfiles to the new location and restore them from the new location. Oracle probably does not support this solution, but who cares if it does work?
Kees

RMAN tape backup fail

Experts...
While executing full database backup using RMAN we are getting below set of exceptions,
RMAN> backup database;
Starting backup at 12-OCT-09
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=401 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 6.5 (20090430)
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00005 name=L:\LHECCDB\CCDB
input datafile fno=00002 name=L:\LHECCDB\UNDOTBS01.DBF
input datafile fno=00006 name=L:\LHECCDB\CCDBRMAN.ORA
input datafile fno=00001 name=L:\LHECCDB\SYSTEM01.DBF
input datafile fno=00003 name=L:\LHECCDB\SYSAUX01.DBF
input datafile fno=00004 name=L:\LHECCDB\USERS01.DBF
channel ORA_SBT_TAPE_1: starting piece 1 at 12-OCT-09
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 10/12/2009 22
:30:10
ORA-19506: failed to create sequential file, name="4", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
Please help and guide where we are making mistake
Thanks,

That is an error from the MML. You may want to check http://seer.support.veritas.com/docs/281296.htm.

Rman archivelog backup fails with rman-03002,ora-19563

Hi,
D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
RMAN> backup archivelog all;
RMAN-03002: Error with backup command on 06-25-2013
ORA-19563: Header-Validation is not successful.
fails with the given errors.
11.2.0.2 PROD DB on Windows Server 2008 R2 Enterpriise.
When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
Please suggest.
Thanks a lot.
Best Regards,

Hi,
Thanks a lot.
I don't think that archivelogs were relocated, except I changed the location yesterday.
As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

FRA changed but incremental RMAN disk backup failed

This is a 11.1 test database.
There was a daily FRA RMAN backup scheduled from database control. Because of the filesystem space pressure we changed FRA destination to a new filesystem and removed old FRA directories.
But this time RMAN failed because it is trying to access the old files as base. How can I force RMAN to make a new base for daily incremental backup and not loose the already scheduled backup.
Thank you.
Connected to Oracle Database 11g Enterprise Edition Release 11.1.0.6.0
Connected as ODS
SQL> SELECT output FROM v$rman_output ORDER BY recid;
OUTPUT
connected to target database: OWB11 (DBID=373788874, not open)
using target database control file instead of recovery catalog
echo set on
run {
allocate channel oem_disk_backup device type disk;
recover
allocated channel: oem_disk_backup
channel oem_disk_backup: SID=688 device type=DISK
Starting recover at 12-JUL-08 02:01:13
no copy of datafile 5 found to recover
no copy of datafile 7 found to recover
no copy of datafile 8 found to recover
channel oem_disk_backup: starting incremental datafile backup set restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy file number=00003 name=/dwh0/app/oracle/product/flash_r
channel oem_disk_backup: reading from backup piece /ods01/owb11/flash_recovery_a
OUTPUT
released channel: oem_disk_backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/12/2008 02:01:14
ORA-19870: error while restoring backup piece /ods01/owb11/flash_recovery_area/O
ORA-19625: error identifying file /dwh0/app/oracle/product/flash_recovery_area/O
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
exit;
36 rows selected
SQL>

assuming you are using the Oracle provided backup procedure (you are pretty scarce on details) you need to make sure you don't have any backups (crosscheck backup and delete expired backup comes to mind), and run the procedure again. It will make a new level 0 backup and incrementals on the following days.
Please note if you don't use RMAN to clean up your O/S you will always ruin the RMAN catalog!!!
Sybrand Bakker
Senior Oracle DBA

RMAN Automatic backup/recovery with oracle fail safe, windows cluster

Hello,
I have question,
1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
Environment: -
a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
b. Shared disk ( RAID )
c. Oracle 10g standard edition one
d. Oracle fail safe v3.3.3 (for redundancy)
Here we have single oracle instance operating on single database whose files are located on shared disk.
2) If answer to above question is yes please specify if there is some good documentation to it.
Any help regarding this will be greatly appreciated.
Thanks in advance,
Rahul

You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
and also I want to know,
Do we need to setup another server which will have RMAN backup script running?

RMAN Backup Failed.

Hi Gurus,
My RMAN backup failed with below error.Please suggest.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
RMAN>
Recovery Manager complete.
Thanks,

The message indicates that your database is in NOARCHIVELOG mode. You cannot make an RMAN Backup of a database that is OPEN if it is in NOARCHIVELOG mode.
You have two options
1. Make consistent RMAN Backups with the database only in MOUNT mode (SHUTDOWN ; STARTUP MOUNT)
OR
2. Configure for ArchiveLogs (create a target filesystem or FRA), set the database to ARCHIVELOG mode, monitor the volume of ArchiveLog generation, configure both Database and ArchiveLog backups.
Hemant K Chitale

RMAN backup fails using OEM with no output error

I am trying to do a weekly automatic full backup of a database in noarchivelog mode using RMAN in Enterprise Manager. Every time I submit the backup job (even if I try to do an immediate backup) the job fails almost immediately. When I Iook at the job output for the failed attempt, it says that there is no output for the job. I believe I have all of the preferred credentials and priveleges correct. Does anyone have any ideas as to what the problem could be or maybe where I can find an error log for rman to get a better explanation of the error?
Thanks

please check in metalink.....
you find useful informations here:
RMAN backup using Oracle Secure Backup fails with ORA-19511 (sbt__rpc_connect)
Doc ID: Note:396046.1
Best Regards,
Shishir Tekade.
My Blog: http://shishirtekade.blogspot.com

If RMAN incremental level-1 backup fails...

Hi there,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Best regards

Hi,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Check the V$BACKUP_SET dictionary to confirm whether the last backup has been touched by data dictionary. If the failed incremental backup is picked up then the previous incremental backup will be required in case of the next DIFFERENTIAL INCREMENTAL LEVEL 1 backup.
But to be on safe side , it is recommended you take a LEVEL 01 CUMILATIVE INCREMENTAL backup from Level 0 till date. So that the recovery process can go through even if the previous backup is not valid.
Thanks &
Best Regards

Backup fails with RMAN-08132

Hi
I'm trying to run rman backup on standby db. It seems like the backup completes but i'm getting the following message at the end. I cant issue commands like "list backup;" Fails with the same error. Tried searching metalink without any luck. Anyone seen this before??
Finished backup at 25-APR-07
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of REFAF command on default channel at 04/25/2007 12:30:45
ORA-00604: error occurred at recursive SQL level 1
ORA-01219: database not open: queries allowed on fixed tables/views only
Any clues from you sharp-eyed dba's out there would be greatly appricated!!

There's an entry on metalink:
Known RMAN issues in Oracle10g
Doc ID: Note:363409.1
Inside this note search for 'WARNING: cannot update recovery area reclaimable file list'
Werner

Rman Backups Failing

Hi All,
we have hot backups of DB scheduled(DB Full backup) thru RMAN for all prod DBs.. but since some days all the backups are failing with similar error.. the sample output of one of the backup job run is given below:
set command id to 'BACKUP_PRSAL41_FUL_091007040002';
echo set on
executing command: SET COMMAND ID
connected to recovery catalog database
connected to target database: PRSAL41 (DBID=3043389771)
input datafile fno=00002 name=/prddb02/u12/oradata/prsal41/undotbs01.dbf
input datafile fno=00007 name=/prddb02/u12/oradata/prsal41/autodba8601dat0101.dbf
input datafile fno=00008 name=/prddb02/u12/oradata/prsal41/autodba8601idx0101.dbf
input datafile fno=00004 name=/prddb02/u12/oradata/prsal41/users01.dbf
channel ORA_DISK_1: starting piece 1 at 10-SEP-07
input datafile fno=00006 name=/prddb02/u12/oradata/prsal41/IIS_INDEX_01.dbf
input datafile fno=00005 name=/prddb02/u12/oradata/prsal41/IIS_DATA_01.dbf
input datafile fno=00003 name=/prddb02/u12/oradata/prsal41/sysaux01.dbf
input datafile fno=00001 name=/prddb02/u12/oradata/prsal41/system01.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: sid=147 devtype=DISK
allocated channel: ORA_DISK_1
Starting backup at 10-SEP-07
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' da
Starting Control File and SPFILE Autobackup at 10-SEP-07
Finished backup at 10-SEP-07
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:25
piece handle=/back01/prsal41/5oiricui_1_1 tag=BACKUP_PRSAL41_FUL_091007040002 comment=NONE
channel ORA_DISK_1: finished piece 1 at 10-SEP-07
Finished Control File and SPFILE Autobackup at 10-SEP-07
piece handle=/back01/prsal41/c-3043389771-20070910-00 comment=NONE
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' ar
Starting backup at 10-SEP-07
current log archived
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: sid=147 devtype=DISK
delete noprompt obsolete device type disk;
allocate channel for maintenance type disk;
Additional information: 3
Linux-x86_64 Error: 2: No such file or directory
ORA-27037: unable to obtain file status
ORA-19625: error identifying file /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
RMAN-03002: failure of backup command at 09/10/2007 04:02:55
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 2 days
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 275349 18-JUL-07 /hubudorap1/arch01/prsal41/1_132_626515083.arc
Archive Log 275350 18-JUL-07 /hubudorap1/arch01/prsal41/1_133_626515083.arc
Backup Set 383337 15-AUG-07
Backup Piece 383340 15-AUG-07 /back01/prsal41/44ipdr6h_1_1
Backup Set 383353 15-AUG-07
Backup Piece 383362 15-AUG-07 /back01/prsal41/c-3043389771-20070815-00
Backup Set 500971 07-SEP-07
Backup Piece 500974 07-SEP-07 /back01/prsal41/5iirafql_1_1
Archive Log 501025 07-SEP-07 /hubudorap1/arch01/prsal41/1_404_626515083.arc
Backup Set 500987 07-SEP-07
Backup Piece 500996 07-SEP-07 /back01/prsal41/c-3043389771-20070907-00
Archive Log 505768 07-SEP-07 /hubudorap1/arch01/prsal41/1_405_626515083.arc
Archive Log 505769 07-SEP-07 /hubudorap1/arch01/prsal41/1_406_626515083.arc
Archive Log 505770 07-SEP-07 /hubudorap1/arch01/prsal41/1_407_626515083.arc
Archive Log 505771 08-SEP-07 /hubudorap1/arch01/prsal41/1_408_626515083.arc
deleted backup piece
backup piece handle=/back01/prsal41/5iirafql_1_1 recid=178 stamp=632635222
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_404_626515083.arc recid=373 stamp=632635334
archive log filename=/hubudorap1/arch01/prsal41/1_405_626515083.arc recid=374 stamp=632661717
deleted archive log
backup piece handle=/back01/prsal41/c-3043389771-20070907-00 recid=179 stamp=632635329
deleted backup piece
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_408_626515083.arc recid=377 stamp=632718235
Deleted 7 objects
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
archive log filename=/hubudorap1/arch01/prsal41/1_407_626515083.arc recid=376 stamp=632705451
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_406_626515083.arc recid=375 stamp=632685605
deleted archive log
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece /back01/prsal41/c-3043389771-20070815-00
RMAN-06214: Backup Piece /back01/prsal41/44ipdr6h_1_1
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_133_626515083.arc
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06213: --------------- ---------------------------------------------------
release channel;
exit;
released channel: ORA_MAINT_DISK_1
I am not able to detect why the archive log is missing... can anyone help me on this please..?
btw, DBs are oracle 10g R2 non-rac
Backup type : DB Full via RMAN.
Thanks

Hi,
Have you used the CROSSCHECK command?
I am not able to detect why the archive log is missing... can anyone help me on this please..?Could someone removed them through O/S commands (manually) ?
Adith

Got error when creating a standby DB from rman: no backup or copy... Why?

We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
5> DUPLICATE TARGET DATABASE for standby
6> nofilenamecheck
7> dorecover;
8> }
9>
10> exit
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=582 devtype=DISK
allocated channel: aux2
channel aux2: sid=584 devtype=DISK
Starting Duplicate Db at 21-JUN-12
contents of Memory Script:
set until scn 12198261770353;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JUN-12
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
===========================================================================
The backups should have controlfile. There is rman show all display:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
Why and how to fix? Thanks for help!

Here is the list of command:
RMAN> list backup of controlfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
5518 Full 4.57M DISK 00:00:07 17-JUN-12
BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Full 4.57M DISK 00:00:00 18-JUN-12
BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5526 Full 4.57M DISK 00:00:01 19-JUN-12
BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5530 Full 4.57M DISK 00:00:02 20-JUN-12
BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5534 Full 4.57M DISK 00:00:02 21-JUN-12
BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
==================================================================
I tried to catalog the controlfile:
RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
====================================================================
We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
Thanks for help!

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

Quesion about the Basic concept of RMAN incremental backup

I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.

Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder

Scheduled Backup Failed

Hi All,
I performed database backup and send it as a job using EM. Upon viewing the backup jobs, i found out that the backup failed and the following is the the output log:
<<< start of output log >>>
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 26 19:41:01 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
connected to target database: ORCL (DBID=4130375234)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> set command id to 'BACKUP_ORCL_000044_072606074050';
executing command: SET COMMAND ID
RMAN> backup device type disk tag 'BACKUP_ORCL_000044_072606074050' database include current controlfile;
Starting backup at 26-JUL-06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=131 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00005 name=/data/orcl/iwspcm_tbspace.dbs
input datafile fno=00001 name=/data/orcl/system01.dbf
input datafile fno=00003 name=/data/orcl/sysaux01.dbf
input datafile fno=00002 name=/data/orcl/undotbs01.dbf
input datafile fno=00004 name=/data/orcl/users01.dbf
channel ORA_DISK_1: starting piece 1 at 26-JUL-06
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/26/2006 19:41:06
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 81920 bytes disk space from 858934592 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 control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 26-JUL-06
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/26/2006 19:41:10
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 7127040 bytes disk space from 858934592 limit
RMAN> backup device type disk tag 'BACKUP_ORCL_000044_072606074050' archivelog all not backed up delete all input;
Starting backup at 26-JUL-06
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=153 recid=133 stamp=596264115
input archive log thread=1 sequence=154 recid=134 stamp=596300278
input archive log thread=1 sequence=155 recid=135 stamp=596325630
input archive log thread=1 sequence=156 recid=136 stamp=596347055
input archive log thread=1 sequence=157 recid=137 stamp=596383253
input archive log thread=1 sequence=160 recid=140 stamp=596834017
input archive log thread=1 sequence=161 recid=141 stamp=596834021
input archive log thread=1 sequence=162 recid=142 stamp=596834029
input archive log thread=1 sequence=163 recid=143 stamp=596835597
input archive log thread=1 sequence=164 recid=144 stamp=596835671
channel ORA_DISK_1: starting piece 1 at 26-JUL-06
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/26/2006 19:41:15
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 407169024 bytes disk space from 858934592 limit
RMAN> exit;
Recovery Manager complete.
<<< end of output log >>>
I have already doubled the size of the flash_recovery_area and its the same error I am encountering. The above-posted output log is actually the latest one after increasing the size of the flash_recovery_area.
Any response will be highly appreciated.
Many Thanks,
Jiggs

Thanks again Kuljeet!
Here are the output:
SQL> show parameter db_recovery_file_dest
NAME TYPE VALUE
db_recovery_file_dest string /backup/flash_recovery_area
db_recovery_file_dest_size big integer 858934592
SQL> col name for a55
SQL> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED
SPACE_RECLAIMABLE NUMBER_OF_FILES
/backup/flash_recovery_area 858934592 1750880256
0 11
It's now obvious that I still need to increase the size of the flash_recovery_area. What is the easiest way of increasing the size aside from using the EM. Am just new in Oracle RDBMS so am still not familiar with all the stuff in this arena.
Also, do you need to delete the archivelog manually after the backup? What we are doing here is backing up the database using EM and check the 'delete archivelog....' portion during the wizard.
Many Thanks,
Jiggs

RMAN LEVEL0 BACKUP FAIL

Similar Messages

Maybe you are looking for