There is a set of tasks that can be performed after you
install a fix pack. The tasks differ for Windows and Linux or UNIX operating systems.
Post-installation tasks for fix packs (Windows)
As part of a fix pack installation, binding of the database
utilities (IMPORT, EXPORT, REORG,
the Command Line Processor) and the CLI bind
files occurs automatically. However, if an error occurs, you can manually
bind the database utilities and the CLI bind
files. For partitioned database environments on certain Windows operating systems, you must start
the DB2 Remote Command Service
security feature. Recompiling applications is an optional task.
Post-installation tasks for fix packs (Linux and UNIX)
As part of a fix pack installation, binding of the database
utilities (IMPORT, EXPORT, REORG,
the Command Line Processor) and the CLI bind
files, DB2 instances are updated
automatically. However, if an error occurs, you can manually bind
the database utilities and the CLI bind
files and update the DB2 instances.
Depending on your database products and the fix pack installation
method used, you might need to update the DB2 instances, restart the DB2 instances, restart the DB2 Administration Server and start the djxlink command.
Binding bind files after installing fix packs
As part of a fix pack installation on the
server, binding of the database utilities (IMPORT, EXPORT, REORG,
the Command Line Processor) and the CLI bind
files occurs automatically. However, if you install a fix pack on
the client or an error occurs, you can manually bind the database
utilities and the CLI bind
files. Different subsets of bind files must be bound for DB2 Database for Linux, UNIX, and Windows and host or System i® database servers.