Source:Troubleshooting Oracle

Oracle

Testing the Oracle extension with sbttest on AIX does not work

Problem

• Testing the Oracle extension with sbttest on AIX will not work unless the full path to the library with argument -libname is specified.

⇒ Solution

• When running sbttest on AIX, specify the full path to the library with argument -libname, e.g.,
  sbttest test1 -libname /opt/sesam/bin/sesam/libobk.so or ... -libname $ORACLE_HOME/lib/libobk.so.

Errors when attempting to perform a backup on AIX

Problem

• Running RMAN command on AIX ends with errors.

⇒ Solution

• RMAN command on AIX requires that the full path to the library is set in the script via PARMS SBT_LIBRARY={full_path_to_libobk.so}. For details, see RMAN specific parameters.

Rerunning the sbttest script ends with duplicate key error

Problem

• When rerunning the sbttest script with the same backup_file_name parameter, SEP sesam returns duplicate key error.

Cause

• This happens because the sbttest is using the same backup_file_name argument on the next run. SEP sesam interprets backup_file_name as the save_set_id and compares it with the IDs in the results table. When the same save_set_id is found, SEP sesam returns duplicate key error.

⇒ Solution

• When running sbttest, make sure that the backup_file_name argument is set to a different value for each run of the script.

Running bash script on AIX results in bad interpreter: No such file or directory error

Problem

• When running a bash script, a bad interpreter: No such file or directory error message is shown, for example:
-sh: ./sbc_oracle_rman.sh: /bin/bash: bad interpreter: No such file or directory

Cause

• Typically, on AIX bash is not included in the list of valid shells.

⇒ Solution

• Change the first line in sbc_oracle_rman.sh to
  #!/bin/sh.

ORACLE_HOME and ORACLE_SID variables are not set in the user environment

Problem

• If ORACLE_HOME and ORACLE_SID are not defined, SEP sesam script cannot connect to the target database.

⇒ Solution
Set ORACLE_HOME and ORACLE_SID variables using any of the following:

• Add the lines
  export ORACLE_HOME=/u01/app/oracle/product/10gR2/db_1 and export ORACLE_SID=PROD_DB.
• Use oraenv to set the appropriate environment, for example:
export ORACLE_SID=TEST export ORAENV_ASK=NO . oraenv

SAP Oracle: "item from input file does not exist"

Problem

• brbackup backint log on Windows reports "item from input file does not exist". The following error messages appear:
In backint_<SID>.log SSB:(3620): 121043: backint_back.c:( 331):: WARNING: item from input file does not exist: F:\ORACLE\T11\SAPDATA1\ERPUSR_1\ERPUSR.DATA1. In sbc_<SID>.log SSB:(3620): 121242: backint_func.c:(1928):: 2013-06-18 12:12:42: sbc-3008: Info: Processing item: [F:\ORACLE\T11\SAPDATA1\ERPUSR_1\ERPUSR.DATA1]... SSB:(3620): 121242: backint_func.c:(1928):: 2013-06-18 12:12:42: sbc-4000: Trace: GetFileSecurityInfo: Opening file [\\?\F:\ORACLE\T11\SAPDATA1\ERPUSR_1\ERPUSR.DATA1] with CreateFileW() function failed. Error code: 1314 SSB:(3620): 121242: backint_func.c:(1928):: 2013-06-18 12:12:42: sbc-2046: Warning: Cannot get item security data for [F:\ORACLE\T11\SAPDATA1\ERPUSR_1\ERPUSR.DATA1].

Possible causes

• The user starting the brbackup process does not have permission to access the security data (ACL) of the file F:\ORACLE\T11\SAPDATA1\ERPUSR_1\ERPUSR.DATA1 in Windows. Typically, only local group administrators have permission to read or write an object's SACL, which is controlled by the privilege or user right (SeSecurityPrivilege).

⇒ Solution

• Assign the user to the local administrator group of the SAP server.
• Ensure that the user right (SeSecurityPrivilege) is implicitly or explicitly given to the user.
• It may also be necessary to set the User Account Control Settings to Never notify through the Control Panel.

The RMAN file name is too long

Problem

• You receive the warning:

ORA-19506: failed to create sequential file, name="full_COMP1_1953897796_55938_1.bck", parms=""

Possible causes

• The file name of the backup set created by the RMAN is longer than 32 characters. For example, if the Oracle backup file format is set to format 'full_%d_%I_%s_%p.bck', when the parameter %s (backup set number) is integrated into the filename, the backup set number increases with every backup. As a consequence, the count of characters of that string will increase. Increasing the number to over 32 characters will cause the backup to fail.

⇒ Solution

• Make sure that the character length of the backup set does not exceed 32 characters.

See also

Oracle