1. Support
  2. Knowledge base
  3. 100018438

Backup of Oracle database fail with the error "0xe0000340 - The Database script returned an error. Refer to the Database script output section in job logs for more details."

Article: 100018438
Last Published: 2019-12-13
Ratings: 0 0
Product(s): Backup Exec

Problem

Backup of Oracle database fail with the error "0xe0000340 - The Database script returned an error. Refer to the Database script output section in job logs for more details."
 

Error Message

ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile
ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices.
 

ERROR MESSAGE 1 - ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile:
 
Missing archive log(s) in the Control File on the Oracle server causes the job to fail with the above error message and BERemote log on the Oracle server shows the following message:
 
***********************************************************************************************************
procMsg: RMAN-03002: failure of backup plus archivelog command at 05/12/2008 08:20:15
procMsg: RMAN-03009: failure of backup command on ch0 channel at 05/12/2008 08:19:32
procMsg: ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile
***********************************************************************************************************

 
ERROR MESSAGE 2 - ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when Duplexing to sequential devices:
 
If RMAN is configured incorrectly to use Duplexing then backup fails with the above error message in job log and beremote log on the Oracle server shows the following message:

***********************************************************************************************************
 {4348] 01/07/09 12:29:22 procMsg: RMAN-03009: failure of backup command on ch0 channel at 01/07/2009 12:29:19
 [4348] 01/07/09 12:29:22 end of linebuf
 [4348] 01/07/09 12:29:22 procMsg: ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when Duplexing to sequential devices
 [4348] 01/07/09 12:29:22 end of linebuf
 ************************************************************************************************************
 

Cause

CAUSE :ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when Duplexing to sequential devices:

The above issue is encountered if all of the following conditions have been met:
  1. RMAN has been configured to create copies of each backup piece
  2. The above copies are set to backup to sbt i.e. to Tape 
  3. Initialization parameter BACKUP_TAPE_IO_SLAVES is not set to True
  4. Tape drive is either not available or is in use.
     
CAUSE : ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile:
Above issue may be encountered if value for the parameter CONTROL_FILE_RECORD_KEEP_TIME is lesser than the retention policy in Oracle causing the reusable records to be overwritten before these records are made obsolete in RMAN metadata. Oracle recommends that the CONTROL_FILE_RECORD_KEEP_TIME should be set to a higher value than the Backup Retention Policy. For more details on CONTROL_FILE_RECORD_KEEP_TIME and Backup retention policy refer to the: Database Backup and Recovery Basics
 

Solution

 
Backup Exec is using Oracle Recovery Manager(RMAN) to backup Oracle Databases.
Backup of Oracle database(s) may fail with the above mentioned generic error message.
Refer to the RMAN output section in job logs for more details.
 
The job log may not show anything under RMAN output section. To find out the exact cause enable debugging for Backup Exec Remote Agent and Backup Exec Agent for Oracle on the target Oracle server and check the Beremote and Vxbsa logs (default location: C:\Program files\Symantec\Backup Exec\RAWS\Logs) for details. 
 
Note: Refer to the article in the Related Documents section for information on how to enable debugging for Backup Exec Agent for Oracle.
 
RESOLUTION :ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile:
To resolve the issue follow either of the steps listed below:
  1. Set the value for CONTROL_FILE_RECORD_KEEP_TIME such that it is greater than the Backup Retention Period. The default value for CONTROL_FILE_RECORD_KEEP_TIME is 7. SQLPLUS Command to change the value of CONTROL_FILE_RECORD_KEEP_TIME is as follows: ALTER SYSTEM SET CONTROL_FILE_RECORD_KEEP_TIME=14 (In this example value for CONTROL_FILE_RECORD_KEEP_TIME is being changed to 14.)
OR
  1. Re-catalog the Archived Logs.
    Contact Oracle Support for assistance in following the above steps accurately.
NOTE:
  1. The backup and the deletion of the archived logs should only be done by RMAN. Select the option "Delete backed up archived log files" in backup job under Oracle in backup job properties.
  2. The archiving should be set to AUTO.
  3. Always use a catalog database so that the information is there in the catalog even if the information is aged out from control file.
     
RESOLUTION :ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when Duplexing to sequential devices:
If Duplexing is configured in RMAN and copies are targeted to sbt, then ensure that initialization parameter BACKUP_TAPE_IO_SLAVE is set to true.
 
For more details on Duplexing and BACKUP_TAPE_IO_SLAVES refer to the link below: Configuring the recovery manager environment.

 

Was this content helpful?

Article Languages