Troubleshooting Backup - Oracle RAC iDataAgent

Sometimes, jobs fail due to increase in the size of sbtio.log file in the $UDUMP directory.

To resolve this, set the size limit for thesbtio.log file using the sMAXORASBTIOLOGFILESIZE registry key. Once the specified size limit is reached, the sbtio.log file gets pruned automatically.

• Make sure if the required media resource is available and then run the backups once again.
• For on demand backups, you can run more than one script for an instance. However, backup jobs will fail if there are more than one instance in the argument file.
• For Oracle on Windows, it is recommended to avoid using a space after a comma in the argument file. A backup job will fail if you leave a space after a comma in the argument file.
• RMAN command line backup fails with the following error

  "Unable to open lock file /opt/calypso/Base/Temp/locks/.dir_lock: Permission denied"

  This may occur if the unmask parameter is set as 022 in the .profile file for the Oracle instance. As a workaround, change the unmask to 000 or 002 and try the backup again.

• Offline backups using lights out script fails with the following error:

  RMAN error "ORA-12528 TNS listener - all appropriate instances are blocking new connections

  As a workaround, add a reference to the database in the listener.ora file as shown in the example below:

  SID_LIST_LISTENER =

  (SID_LIST =

  (SID_DESC =

  (SID_NAME = PLSExtProc)

  (ORACLE_HOME = C:\oracle\product\10.1.0\db_1)

  (PROGRAM = extproc)

  )

  (SID_DESC =

  (SID_NAME = rman10g)

  (ORACLE_HOME = C:\oracle\product\10.1.0\db_1)

  (SID = rman10g)

  )

  )

  Oracle offline backup with lights out option fails when you use the default value for retry attempts for the subclient. As a workaround, increase the retry attempts by setting the Tries number value greater than or equal to 5. See Configuring Lights Out Script for Offline Backups for more details.

• If the following line is present in the $ORACLE_HOME/sqlplus/admin/glogin.sql file, it may cause the SrvOraAgent server process on the CommServe to fail when browsing database contents or executing a backup.

  set linesize 80

  To avoid such failures, comment out that line from the file and re-try the browse or backup operation.

• Backup fails with following error:

  Character conversion not supported

  By default, the NLS_LANG variable on the client computer is set to American_America.US7ASCII character. If the Oracle instance uses NLS_LANG set to a non American_America.US7ASCII character, the Oracle backup operations will fail.

  In such cases, use the <oracle_SID>_NLS _LANG registry key to set the NLS_LANG environment variable to the non American_America.US7ASCII character on the client computer.

  In the case of Oracle RAC iDataAgent, the registry key need to be set in all the RAC instance nodes.

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

Make sure that the maximum value for database block corruptions is set for the backup. 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.

As a workaround, do the following steps:

1. Log in to the Oracle client computer as root.
2. From the system prompt, enter the following command:

   ldconfig /<Base_directory_name>

   For example: # ldconfig <software installation path>/Base

This will ensure that the libobk.so library is loaded so that backups for Oracle on Linux can run successfully.

1. From Windows Explorer, right-click Calypso folder and then select Properties.
2. Click the Security tab.
3. Select the user and click Edit.
4. Click the Allow checkbox for Full Control permission for the user, and then click OK.
5. From the Registry Editor, navigate to HKEY_LOCAL_MACHINE | SOFTWARE.
6. Right click CommVault Systems and select Permissions...
7. Select the user and click Allow checkbox for Full Control permission.

• If the Oracle database is configured to save the archive logs in the Flash recovery area, and Oracle subclients having both Protect backup recovery area and Archive Delete enabled at the same time then the backup will fail.

  To resolve this, there should be two different subclients, one for Protect backup recovery area and the other for Archive Delete.

• Log backup fails if you select the default  USE_DB_RECOVERY_FILE_DEST entry as a log destination for the backup.

  To resolve this, make sure that the log destinations are included in the PFile(init<SID>.ora) or SPFile (spfile.ora) file. Also ensure that the correct log destination is selected for the backup.