RMAN problem resolution

Edit online

To isolate problems that occur when you use RMAN, there are a series of checks to complete.

About this task

The following graphic provides information to isolate problems that occur when you use RMAN.

Figure 1. Problem isolation for RMAN

This flow chart shows the path for tracking errors. Decision points are numbered and described by numbers in the following text.
After Data Protection for SAP and Oracle are configured to work together (Step 1.1), attempt to start Oracle by using the server manager svrmgrl (on UNIX™ or Linux™) or svrmgr30 (on Windows™) with Oracle 8.x. Use SQL Plus (sqlplus) with Oracle 9.x. When an error occurs while you use RMAN, always view the sbtio.log file first. This file is in the directory that is specified by the user_dump_dest keyword in the Oracle initSID.ora profile (at $ORACLE_HOME/saptrace/usertrace/sbtio.log by default). If the sbtio.log file does not exist (Step 2.2), then either Oracle was unable to load the shared library that contains the RMAN connector for Data Protection for SAP or an error was encountered before the Data Protection for SAP library was called. In both cases, an Oracle error message exists in the brbackup log file that begins with ORA-, PLS-, or RMAN-. Try to resolve this problem by using the Oracle and SAP® documentation. If the sbtio.log file exists, search for a message beginning with BKIXXXXY where XXXX is a four-digit number and Y is the letter I, W, or E. When such a message occurs, the RMAN connector for Data Protection for SAP loaded correctly and was called by RMAN. This is the first message for every new session in Step 2.3: 
 BKI7060I: Data Protection for SAP version and build number session: 764
If this message is not available, Oracle loaded an incorrect library.

Perform these tasks on Windows when an incorrect library is loaded by Oracle:

Procedure

  1. Remove or rename all occurrences of the file orasbt.dll except the one in the Data Protection for SAP installation directory. Then, copy this one to %ORACLE_HOME%\bin.
  2. Stop the OracleServiceSID and restart it.

Results

Several factors must be considered when an incorrect library is loaded by Oracle on UNIX or Linux. For example, the RMAN library libtdp_r3.ext is not located by the Oracle executable file. Oracle suggests using the SBT_LIBRARY variable to specify the library. However, do not use this variable for a version of Oracle before Oracle 9.2. Oracle recommends not to issue the make command. However, this recommendation is not applicable for all combinations of operating system and Oracle combinations. As a result, issuing the make command on any UNIX or Linux system with Data Protection for SAP is acceptable. When issued correctly, this command can confirm that the library and the Oracle executable files are compatible. Also, make sure the library and soft link that is entered during the command exists and that the soft link is valid: 
make -f ins_rdbms.mk ioracle LLIBMM=lib or link
It might be helpful to add the location of the link or library to the LIBPATH environment variable (on AIX®) or to the LD_LIBRARY_PATH environment variable (on other UNIX or Linux systems).

On Windows based systems, the location of orasbt.dll must be in the PATH. Also, ensure that you have only one orasbt.dll in your system's PATH. Check if a core file is written or if Oracle wrote a trace within the saptrace/usertrace directory.

In (Step 2.4) the file sbtio.log is written and you find an error message that starts with BKI. Using the backint executable file to determine any problems might make it easier because you can see all messages on the screen. Also, if something goes wrong, you do not disturb Oracle. If backint is working as expected, return to problem determination with RMAN.

There must be a connection that is established to ProLE and the IBM Storage Protect™ server, and a password must be set (by using backint) as well. If some of these steps fail, you get the same error messages with RMAN as you get with backint.