No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The oracle outdated archive logs in the Linux cause the BE hot backup database is failed

Publication Date:  2012-12-11 Views:  77 Downloads:  0
Issue Description
1. The backup software: Symc backup exec 11d software
The client system: redflag DC5.0
The database software: oracle10g
2. There appears the “rman” error while implementing the backup. To see the detail information, please refer to the attachment.
Alarm Information
tarting backup at 07-MAR-08
current log archived
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/07/2008 16:58:21
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/oracle/product/10.2.0/db_1/dbs/arch1_30_644799531.dbf
ORA-27037: unable to obtain file status
Handling Process
Firstly, delete the outdated logs, make a backup of the archive log and then delete the archive log directly; secondly make a full backup and then make the increment backup.

Make a backup of the archive log:
backup tag ‘alog’ format ‘/bak/archivebak/arcbak_%u_%s_%p’ archivelog all delete input;
Delete the outdated archive log:
1. Enter in to the “rman”.
2. connect target /
3. crosscheck archivelog all
4. delete expired archivelog all

Root Cause
The log “archivelog” is outdated.

Use the Symantec back exec 11d to make a backup for the oracle, in fact the BE just uses the “rman” of the oracle to implement the backup, so we should understand the “rman” of the Oracle.