You are on page 1of 3

GENERAL ANNOUNCEMENT:

The DB2 Version 9.7 Fix Pack 8 (FP8)db6_update_client.sh script and supporting directories/files
have been downloaded from the SAP Download Center and loaded onto the /ibmsapcd share as
follows:

DB2 V9.7 FP8: db2/51046542_DB2_97_Client_FP8

At this point, installation may proceed as required using userid <sapsid>adm as per section V of
SAP Note 1363169 - DB6: Installing fix packs for DB2 V9.7 (UNIX + Linuxusing the following
modified procedure:
Procedure:
1. Log on to the CI host as user "<sapsid>adm".

2. Have Unix Engineering mount the /ibmsapcd share drive onto the server
if not already mounted.

3. Go to directory/ibmsapcd/db2/db2/51046542_DB2_97_Client_FP8/CLIENT

4. Start the script "db6_update_client.sh" from this directory using the
following command:

./db6_update_client.sh -u

or

./db6_update_client.sh -j for Java-only systems (take this into account)
The script "db6_update_client.sh" updates the DB2 CLI driver and the JDBC
driver for Java in the directory global/db6 for all available operating
systems.

The installation is now complete and you can restart your SAP system.



Run R3trans d before running the script and after it to compare if the changes have taken place
as below;

BEFORE

4 ETW000 [ dev trc,00000] DB2 client driver version '09.07.0006' 40 2.025796
4 ETW000 [ dev trc,00000] Connected to DB server type 'DB2/AIX64' 50121 2.075917
4 ETW000 [ dev trc,00000] Connected to DB server version '09.07.0008'

AFTER

4 ETW000 [ dev trc,00000] DB2 client driver version '09.07.0008' 60 56.583625
4 ETW000 [ dev trc,00000] Connected to DB server type 'DB2/AIX64' 15630 56.599255
4 ETW000 [ dev trc,00000] Connected to DB server version '09.07.0008'

Check the jdbc folder to check the timestamp of the files. They change to the same as the time
when the script is run.

prdpop:pr8adm 8> ls -ltr
total 18588
-rw-r--r-- 1 pr1adm sapsys 45 Dec 14 02:09 jdbcdriver.lst
-rw-r-xr-x 1 pr1adm sapsys 1015 Dec 14 02:09 db2jcc_license_cu.jar
-rw-r-xr-x 1 pr1adm sapsys 3801792 Dec 14 02:09 db2jcc4.jar
-rw-r-xr-x 1 pr1adm sapsys 3600463 Dec 14 02:09 db2jcc.jar
prdpop34:pr1adm 9> pwd
/sapmnt/PR1/global/db6/jdbc

looks like the update has been made


ADDITIONAL INFORMATION:

As per SAP Note 101809 - DB6: Supported Fix Packs for IBM DB2 for Linux, UNIX and Windows:
If you are using DB2 V9.1 or higher, SAP still recommends torun the same software level
for client and server. You can, however, also run a lower fixpack level on your
application server but at least the same major version is required.

Example: You are running DB2 9.1 FP6 on your database server. SAP recommends that
you also use FP6 on your application servers. You can, however, also use FP5SAP or
earlier if you require so. This could, for example, be the case if you already upgraded
your database server to a newer Fix Pack and did not update your application servers so
far.

As per SAP Note 1363169 - DB6: Installing fix packs for DB2 V9.7 (UNIX + Linux):
The script "db6_update_client.sh" updates the DB2 CLI driver and the JDBC driver for
Java in the directory global/db6 for all available operating systems.

The installation is now complete and you can restart your SAP system.

Given these SAP notes, it would appear that:

1. It is recommended but not mandatory to update the clients to FP6.

2. It is mandatory that the database be updated to FP6 prior to any clients that will be
connecting to the database being updated to FP6.

3. It is not mandatory to update the clients to FP6 at the same time as the database is updated
to FP6.

4. It is not mandatory to have all clients running at the same fixpack levels at the same time (for
example, one client can be running FP6 while the other one is still running FP5SAPand waiting to
be updated).

5. It is not mandatory to stop SAP, execute db6_update_client.sh, and start SAP. The
db6_update_client.sh can be run in advance and the updated drivers will be loaded into
memory when SAP is next restarted.

As always, it is recommendedappropriate testing be done using non-production environments
prior to implementation into production.

You might also like