The document discusses resolving common RMAN errors ORA-19505 and ORA-19588. For ORA-19505, which occurs when an archive log file is missing, the suggested steps are to run CROSSCHECK and DELETE EXPIRED to clean up expired archives, then take a fresh archive log backup. For ORA-19588, which occurs when an archive is already backed up, the recommendations are to check for other backups running concurrently and avoid scheduling archive and full backups simultaneously.
The document discusses resolving common RMAN errors ORA-19505 and ORA-19588. For ORA-19505, which occurs when an archive log file is missing, the suggested steps are to run CROSSCHECK and DELETE EXPIRED to clean up expired archives, then take a fresh archive log backup. For ORA-19588, which occurs when an archive is already backed up, the recommendations are to check for other backups running concurrently and avoid scheduling archive and full backups simultaneously.
The document discusses resolving common RMAN errors ORA-19505 and ORA-19588. For ORA-19505, which occurs when an archive log file is missing, the suggested steps are to run CROSSCHECK and DELETE EXPIRED to clean up expired archives, then take a fresh archive log backup. For ORA-19588, which occurs when an archive is already backed up, the recommendations are to check for other backups running concurrently and avoid scheduling archive and full backups simultaneously.
The document discusses resolving common RMAN errors ORA-19505 and ORA-19588. For ORA-19505, which occurs when an archive log file is missing, the suggested steps are to run CROSSCHECK and DELETE EXPIRED to clean up expired archives, then take a fresh archive log backup. For ORA-19588, which occurs when an archive is already backed up, the recommendations are to check for other backups running concurrently and avoid scheduling archive and full backups simultaneously.
Download as TXT, PDF, TXT or read online from Scribd
Download as txt, pdf, or txt
You are on page 1/ 3
rman
DBA’s will feel bad when they got any error. It’s common for any 🙂
Lets say you got below error
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ch00 channel at 01/17/2011 13:01:03 ORA-19505: failed to identify file “/dwh1/oraarch/arch/1_1100721_664058960.dbf” ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3
Don’t be panic, nothing happened to your backup or database. If you read the error, its saying particular archive logfile is not available. This may be due to file deleted at OS level due to some reason.
In this situation, do the following
1. Run crosscheck command against archivelogs
RMAN> crosscheck archivelog all;
2. If you find any archives marked as EXPIRED, then delete those expired archives using below command
RMAN> delete expired archivelog all;
This will prompt you YES or NO. If you don’t want a prompt, use below command
RMAN> delete noprompt archivelog all;
3. Take a fresh archivelog backup
RMAN> backup archivelog all; (you can use delete input clause also)
Posted in RMAN | Tagged: how to solve ora-19505 in RMAN, ORA-19505: failed to
identify file, resolving ORA-19505 | 4 Comments »
Resolving ORA-19588: archived log recid stamp is no longer valid
Sometimes you may find the following error in RMAN archive backup or online backup logfile
ORA-19588: archived log recid 24909 stamp 740658206 is no longer valid
This is not an error but a warning. The reason for this is archive logfile which this process is trying to take backup, is already been backed up by another process and file is deleted
This situation will occur if both archive backup job and full database backup (including archives) are executing at same time or two archive backup jobs executing at same time.
So to avoid this we have two ways
1. If you want to run a manual backup, just check whether any other RMAN backups are in execution phase. you can do this by [oracle@viadbscph014 logs]$ ps -ef | grep rman
If any backup process is running, you will see a similar output as below
[oracle@viadbscph014 logs]$ ps -ef | grep rman
root 3022 3015 0 00:15 ? 00:00:00 su – oracle -c ? ORACLE_HOME=/opt/oracle/oracle/product/10.2.0?export ORACLE_HOME?ORACLE_SID=dwh2? export ORACLE_SID?/opt/oracle/oracle/product/10.2.0/bin/rman target / nocatalog msglog /opt/oracle/admin/DWH2/backup/logs/online_backup_20110118.out append << EOF? RUN {?ALLOCATE CHANNEL ch00 TYPE sbt PARMS=’ENV=(NB_ORA_SCHED=Default-Application- Backup,NB_ORA_CLIENT=viadbscph014)’;?ALLOCATE CHANNEL ch01 TYPE sbt PARMS=’ENV=(NB_ORA_SCHED=Default-Application-Backup,NB_ORA_CLIENT=viadbscph014)’;? BACKUP? INCREMENTAL LEVEL=0? SKIP INACCESSIBLE? FILESPERSET 5? # recommended format? FORMAT ‘bk_%s_%p_%t_%U’? DATABASE;? sql ‘alter system archive log current’;?RELEASE CHANNEL ch00;?RELEASE CHANNEL ch01;?# backup all archive logs?ALLOCATE CHANNEL ch00 TYPE sbt PARMS=’ENV=(NB_ORA_SCHED=Default- Application-Backup,NB_ORA_CLIENT=viadbscph014)’;?ALLOCATE CHANNEL ch01 TYPE sbt PARMS=’ENV=(NB_ORA_SCHED=Default-Application-Backup,NB_ORA_CLIENT=viadbscph014)’;? BACKUP? filesperset 20? FORMAT ‘al_%s_%p_%t_%U’? ARCHIVELOG ALL DELETE INPUT;? # ARCHIVELOG ALL;?RELEASE CHANNEL ch00;?RELEASE CHANNEL ch01;?#?# Note: During the process of backing up the database, RMAN also backs up the?# control file. This version of the control file does not contain the?# information about the current backup because nocatalog has been specified.?# To include the information about the current backup, the control file should?# be backed up as the last step of the RMAN section. This step would not be?# necessary if we were using a recovery catalog.?#?ALLOCATE CHANNEL ch00 TYPE sbt PARMS=’ENV=(NB_ORA_SCHED=Default-Application-Backup,NB_ORA_CLIENT=viadbscph014)’;? BACKUP? # recommended format? FORMAT ‘cntrl_%s_%p_%t_%U’? CURRENT CONTROLFILE;? sql ‘alter database backup controlfile to trace’;? sql “alter database backup controlfile to ”/opt/oracle/oracle/product/10.2.0/dbs/dwh2_backup_controlfile.ctl” reuse”;?? RELEASE CHANNEL ch00;?}?EOF? Note: Output may differ. In my case RMAN backup is initiated through Netbackup tool
2. Don’t schedule archive backup job during full database backup (including archivelog). Always make sure you have only one RMAN backup in process
Posted in RMAN | Tagged: how to solve ora-19588, ORA-19588: archived log recid stamp is no longer valid, resolving ora-19588 | 8 Comments »
RMAN no channel allocated for maintenance
Posted by Pavan DBA on December 23, 2010
Rate This
Many a times, when you issue some commands in RMAN you may receive following error
RMAN> run { allocate channel c1 device type sbt_tape; delete noprompt obsolete; }
released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of crosscheck command at 12/23/2010 10:57:21 RMAN-06091: no channel allocated for maintenance (of an appropriate type)
Cause: This is because of command change across versions especially between 9i and 10g. The command which we used above is for 10g and will not work in 9i.
Solution: Use the below way to use rman commands in 9i
RMAN> allocate channel for maintenance type sbt_tape;
