You can update an existing DB2® copy
and all instances running on that copy. You can also choose to install
a new DB2 copy and selectively
update instances to run on this new copy after installation.
Before you begin
- Ensure that you have root user authority.
- Download and uncompress a fix pack. The fix pack and the DB2 copy that you want to update
must be of the same release.
About this task
Follow these instructions to update your DB2 copies from one fix pack level to another
(within the same version level) or to install additional functionality.
If
you have DB2 Version 8, Version
9.1, Version 9.5 or Version 9.7 copies, you cannot update these copies
from previous releases to DB2 Version
9.8, you need to upgrade them.
Restrictions
Procedure
To update your DB2 copies:
- Log on with root user authority.
- Stop all DB2 processes.
- Update each DB2 copy
using one of the following choices:
- To update an existing DB2 copy
and update all the instances running on this DB2 copy, issue the installFixPack command.
You cannot install additional functionality with this command.
- To install a new DB2 copy and selectively update the instances
running on an existing DB2 copy
to the new copy after installation, issue the db2setup command
and select Install New in the Install
a Product panel. To install a new copy, you can also perform
a response file installation specifying a new location as installation
path. Any of these options allow you to also install additional functionality.
- To add functionality to an existing DB2 copy, select Work with Existing in
the Install a Product panel. Then select the DB2 copy that you want to update
with the Add new function action. This action
is only available when the DB2 copy
is at the same release level as the install image. To add functionality,
you can also perform a response file installation or issue the db2_install command.
Important: The
command db2_install is deprecated and might be
removed in a future release. Use the db2setup command
with a response file instead.
- If you installed a new DB2 copy,
use the db2iupdt command to update any instances
that are running in a different DB2 copy
of the same release that you want them to run under the new copy.
The following table shows several examples of updating instances:
Instance |
DB2 copy |
Example to update to another
copy |
db2inst1 |
/opt/IBM/db2/V9.1/ |
cd /opt/IBM/db2/V9.1_FP3/instance
./db2iupdt db2inst1
|
db2inst2 |
/opt/IBM/db2/V9.5FP2/ |
cd /home/db2/myV9.5_FP1/instance
./db2iupdt -D db2inst2a
|
db2inst3 |
/opt/IBM/db2/V9.7/ |
cd /home/db2/myV9.7/instance
./db2iupdt -k db2inst3b
|
Note: - Use the -D parameter to update an instance
from a later release level copy to a earlier release level copy.
- Use the -k parameter to keep the current
instance type during the update to a DB2 copy
that has a higher level of instance type. If you updated from WSE to ESE,
when you update the instance without this parameter the instance type wse is
converted to ese.
Results
Once you have installed or updated a DB2 copy, you can always update instances that
run in other DB2 copies of the
same release, to run on this new DB2 copy
by issuing the db2iupdt command.