BMC Software, Inc., Confidential and Proprietary Information
3-30 Administrative Products for DB2 Installation Guide
Maintaining BMC Software Administrative Products
Maintaining BMC Software Administrative Products
The tables in this section provide guidelines that help you to maintain BMC
Software Administrative Products when you migrate between the following
versions of DB2:
• version 5 to version 6
• version 4 to version 5
Migrating from DB2 Version 5 to Version 6
To maintain BMC Software Administrative Products when you migrate to
DB2 Version 6 or when you fall back to DB2 Version 5, use the guidelines in
Table 3-15.
Table 3-15 Migrating DB2 Version 5 to Version 6 (Part 1 of 4)
If You Are Then To Fall Back Then
using ALTER or
CHANGE
MANAGER 5.4.03
or earlier, or using
PATROL DB-Alter
or PATROL
DB-Change
Manager server
3.0.01 or earlier
Perform a Full installation of ALTER or
CHANGE MANAGER 6.2E. Then, you will
be operating in exploitation mode.
1. Provided that the previous version of
ALTER, CHANGE MANAGER,
PATROL DB-Alter, or PATROL
DB-Change Manager still exists,
remove the product in exploitation
mode.
2. For ALTER (ALU) or CHANGE
MANAGER (ACM), rebind all
packages and plans for the previous
version by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID). Any data
that you added while you were in
exploitation mode will not be available
in toleration mode.
3. For PATROL DB-Alter (ALU) or
PATROL DB-Change Manager (ACM),
rebind all packages and plans for the
previous version by using
prdssid
P
(bind packages) and
prdssid
B (bind
plans) (where
prd
is the product code
and
ssid
is the subsystem ID). Any
data that you added while you were in
exploitation mode will not be available
in toleration mode.
