Creating a symbolic link to access the latest GSKit library

When you install DB2 for Linux, UNIX, and Windows, on UNIX and Linux, local GSKit libraries are also installed. Those libraries are stored in <db2_install_path>/lib64/gskit_db2 or <db2_install_path>/lib32/gskit_db2. On Windows, the default location is C:\Program Files\ibm\gsk8.

During the installation of other IBM products, such as Tivoli® Storage Manager, another copy of the GSKit libraries might be installed. Depending on the product, these libraries might be either local GSKit libraries or global GSKit libraries. When DB2 for Linux, UNIX, and Windows and another IBM product that includes GSKit libraries are both installed on the same system, some interoperability issues might arise. These interoperability issues might occur because GSKit allows only libraries from a single GSKit source to exist in any single process. The interoperability issues might lead to unpredictable behavior and runtime errors.

To ensure that a single source of GSKit libraries is used, the symbolic link approach can be used. During an initial DB2 for Linux, UNIX, and Windows installation, the installer creates a symbolic link <db2_install_path>/lib64/gskit or <db2_install_path>/lib32/gskit to <db2_install_path>/lib64/gskit_db2 or <db2_install_path>/lib32/gskit_db2. These symbolic links are the default locations from where GSKit libraries are loaded. Products that bundle DB2 for Linux, UNIX, and Windows, and change the symbolic link from the default directory to the library directory of another copy of GSKit must ensure that the newly installed GSKit is at the same or a newer level. This restriction applies whether the libraries are global or local. During an upgrade or update of DB2 for Linux, UNIX, and Windows, the symbolic link is preserved. If the newly installed copy has a symbolic link to the default location, the symbolic link that is associated with the older installation copy is preserved. If the newly installed copy does not have a symbolic link to the default location, the symbolic link that is associated with the newer installation copy is preserved.

Some limitations exist since the symbolic link <db2_install_path>/lib64/gskit or <db2_install_path>/lib32/gskit is in the path of the DB2 for Linux, UNIX, and Windows installation copy. For example, if two or more instances are created for any DB2 copy, the symbolic link changes affect all the instances.

You can also modify a Domino Server GSKit in a similar manner. A Domino server does not have a GSKit folder, but it has folders C and N, and a library libgsk8iccs_64.so. You can first create soft links for these folders, and files to point to the corresponding folders on the GSKit package, where the Tivoli Storage Manager backup-archive client V8.1.2 is installed, as follows:

Next, change the DPD node's password to domdsmc CHANGEADSMPwd tvt1054_domnote2 tvt1054_domnote2 tvt1054_domnote2. Finally, run domdsmc query adsm.