As part of the overall process of upgrading your DB2® database server to DB2 Version 10.1, you must upgrade your Version 9.8 instances.
Before you begin
- Your DB2 Version 9.8 instance
must be a DB2 pureScale® instance.
- You must have root user authority on Linux and UNIX operating
systems.
- You must install any DB2 database
add-on products that were installed in the DB2 copy from which you are upgrading.
- Before running the db2iupgrade command, the
following steps are recommended:
- Verify that databases are ready for DB2 upgrade. This step is important in DB2 pureScale environments because
the db2ckupgrade command might return an error
in one member and cause the instance upgrade to fail. Refer to Verifying that your databases are ready for upgrade.
- On Linux and UNIX operating systems, ensure that
there is 5GB of free space in the /tmp directory.
The instance upgrade trace file is written to /tmp.
- Gather
pre-upgrade diagnostic information to help diagnose any problem that
might occur after the upgrade. For
details, see Gathering pre-upgrade diagnostic information.
About this task
On Linux and UNIX operating systems, you must
manually upgrade your DB2 pureScale instances
from Version 9.8.
Restrictions
Procedure
To manually upgrade your existing Version 9.8 instances
to DB2 Version 10.1 using the db2iupgrade command:
- Log on to the DB2 server
with root user authority.
- Upgrade your existing Version 9.8 instances
by issuing the db2iupgrade command from the target DB2 Version 10.1 copy location. You should issue the db2iupgrade command
from the Version 10.1 installation path from all the members first and then
from the CFs. The following example shows how to use this command:
$DB2DIR/instance/db2iupgrade [ -u fencedID ] InstName
Where
DB2DIR is
set to the location that you specified during DB2
Version 10.1 installation,
fencedID is the user
name under which the fenced user-defined functions (UDFs) and stored
procedures will run, and
InstName is the login
name of the instance owner.
If you did not install all DB2 database add-on products that
were installed in the DB2 copy
from which you are upgrading, the instance upgrade fails and returns
a warning message. If you plan to install these products later on
or you no longer need the functionality provided by these products,
use the -F parameter to upgrade the instance.
Note: You
must stop the Version 9.8 instance using the db2stop command
before issuing the db2iupgrade command. If you
do not stop Version 9.8 instance before using the db2iupgrade command,
your instance upgrade might fail.
- Log on to the DB2 database
server as a user with sufficient authority to start your instance.
- Restart the DB2 instance
on all members and CFs with updated resources for the cluster management
software and the cluster file system software by issuing the db2start
instance on <hostname> command, and then issue the db2start command. If you find inconsistencies between the cluster manager resource
model and the db2nodes.cfg repair the cluster manager resources by
using the db2cluster -cm -repair -resources command.
- Verify that your instances are running on to DB2 Version 10.1 by running the db2level command: The Informational tokens should include a string like "DB2 Version 10.1.X.X" where X is
a digit number.
- Rebuild the contents of the network resiliency condition and
response resources in the cluster by issuing the db2cluster
-cfs -repair -network_resiliency -all command.
What to do next
After upgrading your Version 9.8 DB2 pureScale instance,
you must upgrade your database. For more details. see Upgrading databases.
DB2 Version 10.1 for Linux, UNIX, and Windows