Post-installation tasks for fix packs (Windows)

Perform the following actions:

1. For partitioned database environments on Windows 2000 or later, start the Db2 Remote Command Service security feature to protect your data and resources.

   To be fully secure, start either the computer (if the service is running under the context of the LocalSystem account) or a user for delegation (if the service is being run under the logon context of a user).

   To start the Db2 Remote Command Service security feature:

   1. Open the Active Directory Users and Computers window on the domain controller, click Start and select Programs > Administrative tools > Active Directory Users and Computers
   2. In the right window panel, right-click the computer or user to start, select Properties
   3. Click the General tab and select the Trust computer for delegation check box. For user setting, click the Account tab and select the Account is trusted for delegation check box in the Account option group. Ensure that the Account is sensitive and cannot be delegated box has not been checked.
   4. Click OK to start the computer or user for delegation.

   Repeat these steps for each computer or user that needs to be started. You must restart your computer for the security change to take effect.

   If you want to disable the Db2 Remote Command Service security feature, enter the following command:

   db2set DB2RCMD_LEGACY_MODE=ON

2. 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. Determine which instances are associated with the Db2 copy by issuing the command:

      DB2DIR\bin\db2ilist

      where DB2DIR represents the location where the Db2 copy is installed.
   2. Perform the following command once for each database in the instances:

       db2updv115 -d dbname  

      where dbname represents the name of the database.
3. Optional: Bind the bind files.
   Binding of the database utilities and the CLI bind files occurs automatically. 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.

4. Optional: Recompile applications.

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

5. Optional: If you have not installed Db2 Text Search, then you can run the configTool upgradeConfigFolder command, which is required to configure Db2 Text Search for the current fix pack level. For more information, see Upgrading Db2 Text Search when applying Db2 fix packs.
6. Optional: If you have installed Db2 Text Search, but you have not configured the Text Search component of Db2, run the db2iupdt command with the /j "TEXT_SEARCH" option to configure Text Search. For more information on the db2iupdt, see db2iupdt - Update instances command.