Verifying the RMAN setup (UNIX, Linux)

Edit online

In the following description, you must replace the directory name orabit in the installation path. Depending on the version that you install, you must replace it with ora64 for the 64bit version of IBM Storage Protect™ for Enterprise Resource Planning.

Procedure

  1. Make sure that Oracle is linked to the correct library: /usr/lib/libobk.ext /usr/tivoli/tsm/tdp_r3/orabit/libtdp_r3.ext.
    This link is not required in a distributed file system.
  2. Remove the library that is specified in /$ORACLE_HOME/rdbms/lib/libobk.ext.
  3. Make sure that the installed Oracle Server is a 64-bit version.
  4. Examine the sbtio.log in the directory that is specified in the user_dump_dest keyword within the Oracle profile initSID.ora. This file is at oracle/SID/saptrace/usertrace/sbtio.log.
  5. Check the log file sbtio.log for lines that start with BKI. The first message for each RMAN session is: BKI7060I: Data Protection for SAP session: process ID
    If you cannot find any such message in the file, the library is not correctly linked with Oracle.
  6. Examine the dsierror.log in the directory that is specified with the environment variable DSMI_LOG or in the file that is denoted by keyword ERRORlogname in the first stanza of file dsm.sys.
  7. To get a IBM Storage Protect API trace file, set the following entries in the client system options file dsm.sys: tracefile /path/trace file traceflags api api_detail config policy
    The additional soft link might help: ln -s /usr/tivoli/tsm/tdp_r3/orabit/libtdp_r3.ext /usr/lib/libtdp_r3.ext.1