Installation Instructions for Hot Fix G12001

DB2 on Linux 64

Hot fix G12001 addresses the issue(s) in SAS Embedded Process 9.31 for DB2 on Linux 64 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/G12.html#G12001

The hot fix downloaded, G12001dl.zip, contains the updated files required to address the documented issues.
Do NOT extract the contents of G12001dl.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. You must have SAS Embedded Process 9.31 installed on your system before applying this hot fix. Refer to SN-35968 for instructions on how to determine which product releases you have installed.

2. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

3. You must have Administrator Privileges on your CLIENT or SERVER machine.

4. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

5. This hot fix should be installed using the same userid who performed the initial software installation.

INSTALLATION

After downloading G12001dl.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide; see the Apply Hot Fixes section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

1. After the hot fix has been installed on the client machine, locate the file tkdb2srv.so in /SASTKInDatabaseServer/9.31/DB2onLinux64/sasexe.

2. Use FTP (set the file transfer type to binary) or SCP to copy tkdb2srv.so to a temporary location on the target Database Server.

3. Login to the target DB2 server as the DB2 instance owner. From the command line, execute the DB2SET command to find the LIBRARY_PATH location of the SAS DB2 Embedded Process scoring files:

   $ db2set
   DB2_SAS_SETTINGS=ENABLE_SAS_EP:true;LIBRARY_PATH:<db2instance-home>/SAS/SASTKInDatabaseServerForDB2/9.31/sasexe.
   

4. Submit the following command to determine if the SAS DB2 Embedded Process is running.

   $ ps -ef | grep db2sasep

   If the SAS Embedded Process was started, lines similar to the following are displayed.

   db2v9 23265382 20840668 0 Oct 06 - 4:03 db2sasep
   db2v9 27983990 16646196 1 08:24:09 pts/10 0:00 grep db2sasep

5. If the SAS DB2 Embedded Process is not running, skip to step 6. Otherwise, stop the database manager instance. This will stop the SAS Embedded Process.

   $ db2stop

   A message indicating that the stop was successful displays.

   If the database manager instance cannot be stopped because application programs are still connected to databases, use the FORCE APPLICATION command to disconnect all users, use the TERMINATE command to clear any background processes, and then use the DB2STOP command.

   $ db2 list applications
   $ db2 force applications all
   $ db2 terminate
   $ db2stop

6. Change directory to the LIBRARY_PATH location and rename the current version of the tkdb2srv.so file.

7. Copy the new version of the file (tkdb2srv.so) from step 2 to the LIBRARY_PATH location

8. Restart the database manager instance

   $ db2start

9. Verify that the SAS Embedded Process started

   $ ps -ef | grep db2sasep

   If the SAS Embedded Process was started, lines similar to the following are displayed.

   $ ps -ef | grep db2sasep
   db2v9 23265382 20840668 0 Oct 06 - 4:03 db2sasep
   db2v9 27983990 16646196 1 08:24:09 pts/10 0:00 grep db2sasep

   You can also verify if the SAS Embedded Process log file was created in the DB2 instance’s diagnostic directory.

   $ cd <db2instance-home>/sqllib/db2dump
   $ ls -al sasep0.log

This completes the installation of hot fix G12001 for DB2 on Linux 64.