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.
Procedure
Perform the following actions:
- 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:
- Open the Active Directory Users and Computers window
on the domain controller, click Start and select
- In the right window panel, right-click the computer
or user to start, select Properties
- 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.
- 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
- 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:- 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.
- Perform the
following command once for each database in the instances:
db2updv105 -d dbname
where dbname represents
the name of the database.
- 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.
- Optional: Recompile applications.
To
take advantage of any changes to the files linked to in the application,
recompiling applications is recommended.
- Optional: If you have installed DB2 Text Search, you must run the db2iupdt command
with the /j "TEXT_SEARCH" option to have it configured.
Results
The fix pack installation and configuration is complete.