Post-installation tasks for fix packs (Linux and UNIX)

Perform the following actions:

1. If you have InfoSphere Federation Server installed, run the djxlink command.

   Perform the following tasks after installing the fix pack and before running db2iupdt:

   1. Log on as root.
   2. Remove or rename the file djxlink.out, which is located in the DB2DIR/lib directory, where DB2DIR is the DB2 installation directory.
   3. Ensure that all of the appropriate variables are set, either in your current environment or in the db2dj.ini file. For example, if you are using a federated server to connect to an Oracle data source, set the environment variable ORACLE_HOME to the Oracle home directory.
   4. Run the command:

      djxlink

2. Update instances to use the new DB2 database level.

   All existing instances in the DB2 copy must be updated after a fix pack is installed. By default, the installFixPack command updates the DB2 instances automatically. However, if an error occurs, you can update instances manually.

   Perform the following steps:

   1. Log on as root.
   2. Determine which instances are associated with the DB2 copy by issuing the command:

      DB2DIR/instance/db2ilist

      where DB2DIR represents the location where the DB2 copy is installed.
   3. If you made any changes to the db2profile or db2cshrc scripts, either back up the scripts or copy the changes into the userprofile and usercshrc scripts, respectively.

      This action is required because the db2iupdt command overwrites the db2profile and db2cshrc scripts. It does not overwrite the userprofile and usercshrc scripts.

   4. For each instance, issue the command as follows. In a DB2 pureScale® environment, skip this step.

      DB2DIR/instance/db2iupdt iname

      where iname represents the instance name and DB2DIR represents the location where the DB2 copy is installed.
   5. If the DB2 Administration Server (DAS) belongs to the DB2 copy where you installed the fix pack, issue the command:

      DB2DIR/instance/dasupdt

      where DB2DIR is the location where the DB2 copy is installed. If this DB2 copy is now running at a more recent fix pack level than all of the other DB2 copies, consider updating the DAS to belong to this DB2 copy.
3. Optional: Update the system catalog objects in your databases to support the fix pack. This task is strongly recommended if you want to use capabilities specific to the fix pack. This task is not necessary if you installed the fix pack to create a new installation, since there are no existing databases. For each instance in the DB2 copy where you applied the fix pack, perform the following actions:
   1. Log in as the instance owner.
   2. For each database, issue the command:

      db2updv105 -d dbname

      where dbname represents the name of the database.

   Note: Backup your database before running db2updv105. Some system objects might become unusable after moving back to an earlier fix pack, and your database will need to be restored.
4. Restart the DB2 instances and the DB2 Administration Server (DAS).

   This step is required if you installed a fix pack to update an existing installation. If you installed the fix pack to create a new installation, this step is not required.

   To restart an instance:

   1. Log in as the instance owner.
   2. Issue the command db2start.

   Repeat for each instance.

   To restart the DB2 administration server, log in as the DAS owner and run the db2admin start command.

5. Optional: If you issued the db2iauto command to prevent instances from auto-starting before installing the fix pack, enable auto-start for the instances again. Issue the following command while logged on as root:

   DB2DIR/instance/db2iauto -on iname

   where DB2DIR is the location where the DB2 copy is installed and iname represents the instance owner name. The command must be performed once for each instance that you altered with the db2iauto command before you installed the fix pack.
6. Optional: Bind the bind files. Binding of the database utilities and the CLI bind files occurs automatically during a new DB2 installation or when applying a fix pack. However, if an error occurs, you can manually bind the database utilities and the CLI bind files. Refer to Binding bind files after installing fix packs.
7. Optional: Recompile applications.

   To take advantage of any changes to the files linked to in the application, recompiling applications is recommended.

8. Optional: In DB2 Version 10.5 Fix Pack 5 and later fix packs, in a DB2 pureScale environment, you can enable CF self-tuning memory. For more information, see the Related Links.