Topics | How To | Troubleshoot | Related Topics
Backup Failure Due to Database Block Corruption
Avoiding Intermittent Backup Failures for Oracle on Linux Platforms
Offline Backup with Lights Out Option Fails When Using Default Tries Number
File spfile.ora or init<SID>.ora Must be Populated Correctly Before you Select Log Destinations
If an Oracle database backup operation fails due to corrupted database blocks, an error message will be displayed. For example:
LISTING 2: r_20030520213618.log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on d1 channel at 05/20/2003 21:36:26
ORA-19566: exceeded limit of 0 corrupt blocks for file
/u01/app/Oracle/oradata/MRP/sales_data_01.dbf
In such cases, you should make sure that the Enter the maximum database block corruptions value is set in the Advanced Backup Options (Oracle Options) tab. It is recommended that you set this value to match the number of corrupted database blocks identified by RMAN for the database file being backed up. To identify the number of corrupted database blocks in a data file, refer Oracle documentation.
In order to avoid intermittent backup failures for Oracle on Linux platforms, some additional configuration steps may be needed. Specifically, if the library libobk.so fails to load, then the backup may fail. Provided below are steps to take to ensure that this essential library is loaded in the system configuration.
ldconfig /<Base_directory_name>
For example: # ldconfig <software installation path>/Base
If the Oracle instance has the NLS_LANG set to a non American_America.US7ASCII character, the Oracle backup operations fail with the following error:
Character conversion not supported
To solve this problem, you need to set the NLS_LANG environment variable on the client computer using the <oracle_SID>_NLS _LANG registry key, where oracle_SID is the Oracle instance name. For example,
rman10g_NLS_LANG <non American_America.US7ASCII character>
If the registry key is not set, the NLS_LANG variable will be set to American_America.US7ASCII character by default.
In the case of Oracle RAC iDataAgent, the registry key need to be set in all the RAC instance nodes.
Offline Backup with Lights Out Option Fails When Using Default Tries Number
If the Oracle offline backup with lights out option fails when you use the default value for Tries Number in the Subclient Properties (Backup Arguments) window, then increase the value to a number greater than or equal to 5.
Oracle Log Destinations are set up in the spfile.ora or init<SID>.ora file, and they are displayed in the Add list for the following: Select ArchiveLog Destinations for Backup/Delete fields in the Subclient Properties (Log Destinations) tab and the Select ArchiveLog Destinations field in both the Advanced Backup Options (Back up Archive Logs) tab and the Advanced Backup Archive Options (Delete Archive Logs) tab. However, if the spfile.ora or init<SID>.ora file does not include any log destinations, the lists will show USE_DB_RECOVERY_FILE_DEST by default, and the backup job will fail if you select this parameter. Therefore, either do not select log destinations if none are defined in the spfile.ora or init<SID>.ora file or include the log destinations in either file and then refresh the database from the Subclient Properties (Contents) tab.