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>

Similar Messages

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?

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

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

Failure of release command

Hi All
Please your assistance is needed to interpret what is going on with below and what should be done
RMAN-03009: failure of backup command on ch_tape2 channel at 11/26/2011 08:30:14
ORA-19502: write error on file "hist10g_rman_full_upmsjhke_1_1", blockno 577452545 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1017E (RC-50) Session rejected: TCP/IP connection failure
channel ch_tape2 disabled, job failed on it will be run on another channel
channel ch_tape1: finished piece 1 at 26-NOV-11
released channel: ch_tape1
released channel: ch_tape2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 11/27/2011 05:18:51
RMAN-06012: channel: ch_tape2 not allocated
Recovery Manager complete.
OS type and version : AIX Version 5
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

thanks for your response tycho,
quite appreciated. however querrying v$rman_status shows that the backup completed with errors,
0 2011-11-25T15:03:01 DELETE COMPLETED 25-NOV-11 25-NOV-11 ARCHIVELOG
0 2011-11-25T20:10:00 RMAN COMPLETED WITH ERRORS 25-NOV-11 27-NOV-11
0 2011-11-25T20:10:00 BACKUP COMPLETED WITH ERRORS 25-NOV-11 27-NOV-11 DB INCR SBT_TAPE
0 2011-11-26T09:00:01 RMAN COMPLETED 26-NOV-11 26-NOV-11
and as learnt in a case of channel failover, RMAN attempts to complete the work on another channel, hence in this case how can i really tell if the backups were successful in this other channel.

RMAN-05001 - RMAN-03002 | Duplicating Database fails | Redo-Logs

Sorry guys,
first of all...my english is the worsteds you´ve ever seen...
I got some kind of problem using rman duplicating a DB called cs2t into cs2b.
Starting Duplicate Db at 17.05.2006 07:54:10
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/17/2006 07:54:10
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo05.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo04.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo03.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo02.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo01.log conflicts with a file used by the target database
Recovery Manager complete.
Therefore I found on metalink some informations about using UNTIL TIME.
I´ve tryed it....but now...there are some other erros on my rman.log
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/17/2006 08:22:14
ORA-01830: date format picture ends before converting entire input string
Recovery Manager complete.
and now: no ideas anymore...i´ve googled for it about 3hours...nothing found....may anybody help me - please?
P.S. I hope you´ll understand anything i´ve wrote into this message ;-)

hi,
you have to use db_file_name_convert and db_log-filename_convert parameter in the auxiliary database parameter file and use nofilenamecheck parameter with the duplicate command.
This is also recommended that you create new redo og files for auxiliary databse just like --
RMAN> run{
2> allocate auxiliary channel c1 device type disk;
3> duplicate target database to prod1 pfile='c:\oracle\ora92\database\initprod1.ora'
4> logfile 'c:\oracle\oradata\prod1\redo01.log' size 50m,
5> 'c:\oracle\oradata\prod1\redo02.log' size 50m,
6> 'c:\oracle\oradata\prod1\redo03.log' size 50m ;}
i hope it solve your problem..
Navneet

Failure of backup command, please help

hi,
My last backup to give mi error :(
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/19/2010 07:31:50
ORA-19506: failed to create sequential file, name="software_inc0_T20100119_t708679906_s6348_p1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
nwora_open_backup: unable to start save session with server
localhost: system error

user487449 wrote:
$ pwd
/d01/orabackup/oradata/mydb
$ ls -ltrc
total 2
2 drwxrwxrwx 2 orarman dba 2048 Aug 30 08:43 archThis shows permissions for arch directory inside mydb folder and you are creating files in mydb directory.
Do this:
$ cd /d01/orabackup/oradata/
$ ls -lartd mydbThis will show us the permissions set on mydb directory. You need to make sure that the OS user who is running RMAN script has write permissions on the mydb folder.
If you wish to grant 777 permissions on my db folder, do this:
chmod -R 0777 /d01/orabackup/oradata/mydb

RMAN-11003: failure during parse/execution of SQL statement: alter session

without doing any changes I have started getting the following error in the RMAN logs.
i didnt any changes related to sort_area_size but getting the error below
plz help guys
RMAN logs
=====================
connected to recovery catalog database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 12/03/2007 22:00:01
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 12/03/2007 22:00:01
RMAN-11003: failure during parse/execution of SQL statement: alter session set sort_area_size=10485760
ORA-00068: invalid value 10485760 for parameter sort_area_size, must be between 0 and 1

Hi:
It seems when you are starting RMAN it's executing some commands (one 'ALTER SESSION...'. It's seems to be a batch which has a bad value for SORT_AREA_SIZE. Find it and modify to a proper value as message shows. If you can't find start RMAN by calling directly the executable ($ORACLE_HOME/bin/rman or %ORACLE_HOME%/bin/rman.exe).

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.

RMAN backup archivelog all delete input

Hello DBAs,
what does this command will do?
RMAN> backup archivelog all delete input;
DN

I have set cron job for RMAN> backup archivelog all delete input; and its work.
But I got following message in my log file.
Please give ur feed back.
Recovery Manager: Release 10.1.0.4.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN>
connected to target database: SIDNAME (DBID=XXXXXXXX)
using target database controlfile instead of recovery catalog
RMAN>
Starting backup at 10-FEB-06
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=269 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=268 devtype=DISK
channel ORA_DISK_1: starting compressed archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=5701 recid=2412 stamp=581958928
input archive log thread=1 sequence=5702 recid=2413 stamp=581961105
input archive log thread=1 sequence=5703 recid=2414 stamp=581964532
input archive log thread=1 sequence=5704 recid=2415 stamp=582025325
input archive log thread=1 sequence=5705 recid=2416 stamp=582029976
input archive log thread=1 sequence=5706 recid=2417 stamp=582031922
channel ORA_DISK_1: starting piece 1 at 10-FEB-06
channel ORA_DISK_2: starting compressed archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=5707 recid=2418 stamp=582037207
input archive log thread=1 sequence=5708 recid=2419 stamp=582038471
input archive log thread=1 sequence=5709 recid=2420 stamp=582043538
input archive log thread=1 sequence=5710 recid=2421 stamp=582048518
input archive log thread=1 sequence=5711 recid=2422 stamp=582055205
channel ORA_DISK_2: starting piece 1 at 10-FEB-06
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_1 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/6fhb2t97_1_1", blockno 6145
(blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
RMAN>
Recovery Manager complete.
DN

Rman tivoli failure: create sequential file, Authentication Failure

New db instance, not writing to tape.
DB is 10.2.0.4
run {
allocate channel sbt_backup1 type 'SBT_TAPE' format '%U' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/ora
cle/bin64/tdpo_mydb.opt)';
backup tablespace users;
release channel sbt_backup1;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on sbt_backup1 channel at 10/02/2009 11:17:42
ORA-19506: failed to create sequential file, name="0tkqpi6l_1_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
ANS1025E (RC137) Session rejected: Authentication failure
Settings
/usr/tivoli/tsm/client/oracle/bin64
dsm_mydb.opt
SErver_name MYDBPRD
tdpo_mydb.opt
DSMI_ORC_CONFIG /usr/tivoli/tsm/client/oracle/bin64/dsm_mydb.opt
TDPO_NODE MYDBPRD
/usr/tivoli/tsm/client/api/bin64
dsm.sys
NODENAME MYDBPRD
ERRORLOGNAME /usr/local/tsm/logs/IFSDBS_MYDBPRD_error.log
SCHEDLOGNAME /usr/local/tsm/logs/IFSDBS_MYDBPRD_sched.log
Note: Several db/clients are working on this server. This is a new setup and not working.

This is not an Oracle/RMAN problem,contact your TSM administrator:
http://www-01.ibm.com/support/docview.wss?uid=swg21216057
Werner

RMAN-03002 RMAN Error !

Hello,For testing purposes I am duplicating my database from 11gR1 to 11gR2 on Windows XP.
The Oracle Sid of my database SOurce, which is in 11gR1 is : DB01.
The Oracle Sid of my auxiliary database , which is in 11gR2 is : DB02.
I am using RMAN for the duplication.
First of all, I have create a pfile from the DB01 and modified it as following :
*.audit_trail='DB_EXTENDED'
*.compatible='11.1.0.0.0'
*.control_files=('C:\app\werner\oradata\db02\CONTROL01.CTL','C:\app\werner\oradata\db02\CONTROL02.CTL','C:\app\werner\oradata\db02\CONTROL03.CTL')
*.db_file_name_convert=('F:\app\werner\oradata\db01','C:\app\werner\oradata\db02')
*.log_file_name_convert=('F:\app\werner\oradata\db01','C:\app\werner\oradata\db02')
*.db_block_size=8192
*.db_domain=''
*.db_name='db01'
*.db_recovery_file_dest_size=21474836480
*.dispatchers='(PROTOCOL=TCP) (SERVICE=db01XDB)'
*.memory_target=857735168
*.nls_numeric_characters=',.'
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.undo_tablespace='UNDOTBS1'The I startup my DB02 in nomount state with :
startup nomount pfile=C:\app\werner\product\11.2.0\dbhome_1\pfile.orafrom RMAN :
I have backup the whole DB01 (the target database) database with Archivelog all. and connect to the auxiliary nomount DB02 database and
I issue the command duplicate target database to db01 but I have the following Error which means I think the auxiliary database stop at mount state
RMAN> duplicate target database to db01;
Iniciando Duplicate Db en 13/09/10
canal asignado: ORA_AUX_DISK_1
canal ORA_AUX_DISK_1: SID=10 tipo de dispositivo=DISK
contenido del archivo de comandos de memoria:
   set until scn 10225405;
   set newname for datafile 1 to
"C:\APP\WERNER\ORADATA\DB02\SYSTEM01.DBF";
   set newname for datafile 2 to
"C:\APP\WERNER\ORADATA\DB02\SYSAUX01.DBF";
   set newname for datafile 3 to
"C:\APP\WERNER\ORADATA\DB02\UNDOTBS01.DBF";
   set newname for datafile 4 to
"C:\APP\WERNER\ORADATA\DB02\USERS01.DBF";
   set newname for datafile 5 to
"C:\APP\WERNER\ORADATA\DB02\EXAMPLE01.DBF";
   set newname for datafile 6 to
"C:\APP\WERNER\ORADATA\DB02\DATA01.DBF";
   set newname for datafile 7 to
"C:\APP\WERNER\ORADATA\DB02\REPOSITORY_FOR_RMAN.DBF";
   restore
   clone database
ejecutando archivo de comandos de memoria
ejecutando el comando: SET until clause
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
ejecutando el comando: SET NEWNAME
Iniciando restore en 13/09/10
usando el canal ORA_AUX_DISK_1
canal ORA_AUX_DISK_1: iniciando restauraci¾n del juego de copias de seguridad de
archivos de datos
canal ORA_AUX_DISK_1: especificando archivo(s) de datos para restaurar del juego
de copias de seguridad
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00001 a C:\APP\WERNER\O
RADATA\DB02\SYSTEM01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00002 a C:\APP\WERNER\O
RADATA\DB02\SYSAUX01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00003 a C:\APP\WERNER\O
RADATA\DB02\UNDOTBS01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00004 a C:\APP\WERNER\O
RADATA\DB02\USERS01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00005 a C:\APP\WERNER\O
RADATA\DB02\EXAMPLE01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00006 a C:\APP\WERNER\O
RADATA\DB02\DATA01.DBF
canal ORA_AUX_DISK_1: restaurando el archivo de datos 00007 a C:\APP\WERNER\O
RADATA\DB02\REPOSITORY_FOR_RMAN.DBF
canal ORA_AUX_DISK_1: leyendo desde la parte de copia de seguridad F:\APP\DB01\FLASH_RECOVERY_AREA\DB01\BACKUPSET\2010_09_13\O1_MF_NNNDF_TAG20100913T21141
8_68WY0CBQ_.BKP
canal ORA_AUX_DISK_1: manejador de parte=F:\APP\DB01\FLASH_RECOVERY_AREA\DB01\BACKUPSET\2010_09_13\O1_MF_NNNDF_TAG20100913T211418_68WY0CBQ_.BKP etiqueta=T
AG20100913T211418
canal ORA_AUX_DISK_1: parte 1 de la copia de seguridad restaurada
canal ORA_AUX_DISK_1: restauraci¾n terminada, tiempo transcurrido: 00:04:45
restore terminado en 13/09/10
sentencia sql: CREATE CONTROLFILE REUSE SET DATABASE "DB01" RESETLOGS ARCHIVE
LOG
MAXLOGFILES     16
MAXLOGMEMBERS      3
MAXDATAFILES      100
MAXINSTANCES     8
MAXLOGHISTORY      292
LOGFILE
GROUP 1 ( 'C:\APP\WERNER\ORADATA\DB02\REDO01.LOG' ) SIZE 50 M REU
SE,
GROUP 2 ( 'C:\APP\WERNER\ORADATA\DB02\REDO02.LOG' ) SIZE 50 M REU
SE,
GROUP 3 ( 'C:\APP\WERNER\ORADATA\DB02\REDO03.LOG' ) SIZE 50 M REU
SE
DATAFILE
'C:\APP\WERNER\ORADATA\DB02\SYSTEM01.DBF'
CHARACTER SET AL32UTF8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando Duplicate Db en 09/13/2010 21:21:29
RMAN-06136: error ORACLE en la base de datos auxiliar: ORA-01503: CREATE CONTROL
FILE ha fallado
ORA-01158: base de datos ya montada
RMAN>
RMAN>Can you help me please,
Thank you

Hemant K Chitale wrote:
duplicate target database to db01That is wrong. you would be duplicating the target (db01) to the auxiliary (db02).
You have the database connections and command the wrong-way around.
Hemant K ChitaleIn have got this error now, using duplicate target database to db02;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: error fatal al ejecutar el comando
RMAN-10041: No se ha podido volver a crear el contexto del canal de sondeo despuÚs del fallo.
RMAN-10024: error al crear la configuraci¾n para el sondeo rpc
RMAN-10005: error al abrir el cursor
RMAN-10002: error ORACLE: ORA-03114: not connected to ORACLE
RMAN-03002: fallo del comando Duplicate Db en 09/14/2010 12:28:48
RMAN-03015: se ha producido un error en el archivo de comandos Memory Script almacenado
RMAN-06136: error ORACLE en la base de datos auxiliar: ORA-01092: ORACLE instance terminated. Disconnection
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Identificador de Proceso: 3696
Identificador de Sesi¾n: 125 N·mero de Serie: 9

RMAN-03002, ORA-2707, OSD-04008

Hi,
RMAN Backup is failing due to below error
MAN-03002: failure of backup plus archivelog command at 03/02/2011 07:15:58
ORA-19502: write error on file "D:\ORADATA\RMAN\BACKUP\DF_WEBCT_4938_1_QAM66FNI", blockno 8380545 (blocksize=8192)
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 112) There is not enough space on the disk.
This is windows 2003 64-bit server. I have checked the space and it is showing 264G available. Is it because the datafiles is of 317G size.
please help resolving this issue.
Thanks.
Edited by: user12045167 on Mar 2, 2011 12:07 AM

O/S-Error: (OS 112) There is not enough space on the disk.
Your available space is 264 GB and your datafile size is 317 GB. So, increase the space for that mount point and try again.
Regards
Asif Kabir

UCS manager blade memory "Delete" command

I have a question, and I cannot seem to find an answer in documentation or other questions on the support community. In UCS Manager, if you click a blade server, click the inventory tab, click the memory subtab, you see a graphical display of the memory modules. If you click on a moduleto select it then right-click it, the menu available includes a "Delete" command. Does this shut down that particular module, or does it just keep UCS Manager from monitoring it? Or is it something else more damaging or permanent? Is it possible to "Add" the module back once that command was issued? If possible, please provide any documentation or links that would answer this definitively. Thanks!
Gil

Thanks for the information! I work with a group that is performing some failure testing, and we were trying to figure a way to fail a memory module while the blade is running. We were not sure of the purpose of the mentioned command in UCS manager and did not want to try it without knowing if it had serious consequences.

RMAN-03002: failure of delete command

Similar Messages

Maybe you are looking for