English

FAQ: DB2 - Are there any issues with installing DB2 FixPack3

Question

DB2 - Are there any issues with installing DB2 FixPack3

Answer

ArcSDE for DB2 UDB Final as well as Sp1 have been certified with DB2 UDB FixPack3.

If you have a pre-existing database and you intend to apply DB2 FixPack3, you will need to rebind your DB2 utilities including the Spatial Extender ones against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of rebinding, outlined below, only needs to be performed once per database.
-----------------------------------------------
Rebind DB2 Utilities
====================
cd to to your Sqllib\bnd dir.
F:\SQLLIB\bnd>db2 CONNECT TO <dbname>
F:\SQLLIB\bnd>db2 bind gse_db.bnd blocking unambig isolation CS
F:\SQLLIB\bnd>db2 bind gse_gc.bnd blocking unambig isolation CS
F:\SQLLIB\bnd>db2 bind gse_idx.bnd blocking unambig isolation CS
F:\SQLLIB\bnd>db2 bind gse_ixpt.bnd blocking unambig isolation CS
F:\SQLLIB\bnd>db2 bind gse_layer.bnd blocking unambig isolation CS
F:\SQLLIB\bnd>db2 bind gse_sref.bnd blocking unambig isolation CS

F:\SQLLIB\bnd>db2 connect to <database> user SDE using <password>

F:\SQLLIB\bnd>cd %SDEHOME%\lib

F:\SQLLIB\bnd> db2 bind sdesrvsp.bnd blocking unambig isolation CS

After applying fixes, you must also do the following:

db2 terminate
db2 CONNECT TO <dbname>
db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC
db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC
db2 terminate
Where <dbname> is the name of a database to which the utilities should be
bound. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind
files used for DB2.