IBM Support

dataserver: error while loading shared libraries: libsbgse2.so: cannot open shared object file: No such file or directory activating ATAP for SYBASE in IBM Security Guardium

Troubleshooting


Problem

You are activating ATAP for SYBASE in IBM Security Guardium using the grdctl command, for example : /opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl --db-instance= activate Command fails with error below: /bin/dataserver: error while loading shared libraries: libsbgse2.so: cannot open shared object file: No such file or directory where is the SYBASE directory The error indicates it can't find the library libsbgse2.so but the library exists on the server, in one of the paths specified in the environment variable for libraries when you login to the server with the SYBASE account. For example, it may exist on below path: /DataAccess64/ODBC/lib/libsbgse2.so or on any other path specified in the library environment variable (name of variable depends on the platform but it is usually LD_LIBRARY_PATH or LIBPATH for most platforms) for the SYBASE's account environment.

Symptom

grdctl command fails with error:

<SYBASE HOME>/bin/dataserver: error while
loading shared libraries: libsbgse2.so: cannot open shared object file: No such file or directory

Cause

SYBASE environment is not loaded so it can't find the library needed to complete the activation.

Diagnosing The Problem

You are in presence of this issue If the library exists but the grdctl activate command fails indicating it can not find the library. You confirm the library exists by:

1. login to the server with the SYBASE's account

2. check value for the library environment variable, example, LD_LIBRARY_PATH for Linux but variable name may be different in other platforms:

env | grep LD_LIBRARY_PATH

3. You confirm library libsbgse2.so exists in at least one of the paths listed in the library environment variable

Resolving The Problem

One of the following:

- load the SYBASE account environment before running the grdctl command. You can do this in different ways, the most usual one is to add the SYBASE environment to the root's .profile. Another method is to manually run a script that loads the SYBASE account's environment before you run the grdctl command.

- specify the full sybase version to grdctl command:

/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
db-instance=<instance name> db_type=sybase db_base=<base dir> db-version=157 db_user=sybase db-home=<sybase home> store-conf


/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
--db-instance=<instance name>  activate

For example, for SYBASE 15.7 installed with base directory on /home/sybase, instance name A1, and sybase instance home directory on /local/a1/sybase/ase157

Command fails:


/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
db-instance=A1 db_type=sybase db_base=/home/sybase  db-version=15 db_user=sybase db-home=/local/A1/sybase/ase157 store-conf

/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
--db-instance=A1  activate

<SYBASE HOME>/bin/dataserver: error while loading shared libraries: libsbgse2.so: cannot open shared object file: No such file or directory

Command works (note db-version=157 versus db-version-15):


/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
db-instance=A1 db_type=sybase db_base=/home/sybase  db-version=157 db_user=sybase db-home=/local/A1/sybase/ase157 store-conf

/opt/IBM/guardium/modules/ATAP/current/files/bin/guardctl
--db-instance=A1  activate

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21965542

Page Feedback