Translations:Troubleshooting Guide/42/en

From SEPsesam

SAP ASE

SAP ASE backup fails with Requested server name not found

Problem

  • SAP ASE backup fails with CT-LIBRARY error: ... Requested server name not found.

Cause

  • The server name hasn't been added to the interface file or the given server name does not exist.

Note

  • If source is set with {server_name} then you probably have mistyped the server name or server's port (default 5000).
  • If source is set without {server_name} then isql looks for the server specified by your DSQUERY environment variable.

Solution

  • You have to extend the source with the correct server name and if necessary also the port.
  • Source format [/{server_name}[:{port}]]/{database} For example, if the source is master, you have to add the server name as the first part, e.g. /SOL/master or /SYBASE16:5000/master.
  • Test the connection to SAP ASE server by running the isql utility. For details, see SAP ASE Utility Guide: isql.
  • isql -U<username> -P<password> -S<server_name> where <username> specifies a login name of a user with access to database (login names are case-sensitive!), <password> specifies your SAP ASE password, and <server_name> specifies the name of the SAP ASE server to which to connect. isql looks this name up in the interfaces file.
    If this test fails, use the dsedit utility that allows you to view and edit server entries in the interfaces file using a GUI in Adaptive Server Enterprise. For details, see SAP ASE Utility Guide: dsedit.

SAP ASE backup fails with Failed to load library 'libsepsybase.so' error

Problem

  • A backup fails with Failed to load library 'libsepsybase.so' or Failed to load library '%1' error.

Possible causes

  • The library libsepsybase.so is not copied to the SAP ASE lib directory.
  • A wrong binary library file is used.
  • The LD_LIBRARY_PATH is not set correctly.
  • The SAP ASE backup server is not running on the specified host.

Solution

  • Copy the library libsepsybase.so to the SAP ASE lib directory.
  • Check whether a necessary shared library is installed: file libsepsybase.so and how it is resolved: ldd libsepsybase.so.
sybase16:/opt/sap/ASE-16_0/lib # file libsepsybase.so
libsepsybase.so: symbolic link to `/opt/sesam/bin/sesam/libsepsybase.so'
sybase16:/opt/sap/ASE-16_0/lib # file /opt/sesam/bin/sesam/libsepsybase.so
/opt/sesam/bin/sesam/libsepsybase.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped
sybase16:/opt/sap/ASE-16_0/lib # ldd /opt/sesam/bin/sesam/libsepsybase.so
       linux-vdso.so.1 =>  (0x00007fffcd75c000)
       libdl.so.2 => /lib64/libdl.so.2 (0x00007f65d0fa6000)
       librt.so.1 => /lib64/librt.so.1 (0x00007f65d0d9c000)
       libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f65d0b7f000)
       libc.so.6 => /lib64/libc.so.6 (0x00007f65d0803000)
       /lib64/ld-linux-x86-64.so.2 (0x00007f65d1cf3000)
  • Check if the LD_LIBRARY_PATH variable is set correctly in the file SYBASE.env (The SAP shared libraries are located in the installed component’s lib directory).
sybase16:/opt/sap # grep LD_LIBRARY_PATH SYBASE.env
[...]
LD_LIBRARY_PATH=/opt/sap/ASE-16_0/lib:$LD_LIBRARY_PATH
  • Check if the SAP ASE backup server is running on the specified host -> check for the process named backupserver.
sybase16:/opt/sap # ps -ef | grep backupserver
root     15534 15533  0 Mar23 ?        00:00:00 /opt/sap/ASE-16_0/bin/backupserver -e/opt/sap/ASE-16_0/install/qsstor.log -N25 -C20 -I/opt/sap/interfaces -M/opt/sap/ASE-16_0/bin/sybmultbuf -Sqsstor

SAP ASE backup fails with ERROR: No Total: ... line found in LIS file

Problem

  • SAP ASE backup fails with the following error: No Total: ... line found in LIS file.

Cause

  • sm_backup tried to fetch the LIS file before the backup server has finished.

Solution

  • Use the SEP sesam Client ≥ Beefalo V2 SP2 and set the following backup option in the SAP ASE backup task properties -> Options tab -> Backup options field:
  • -a action=sleep:20
    Information sign.png Note
    If the backup option -a action=sleep:xx does not work, use the FTP interface instead of HTTP.