Maintaining BMC Software Administrative Products
BMC Software, Inc., Confidential and Proprietary Information
Chapter 3 Performing Additional Installation Tasks 3-31
using ALTER or
CHANGE
MANAGER
5.4.04D installed
on DB2 Version 5,
or using PATROL
DB-Alter or
PATROL
DB-Change
Manager server
3.0.02 through
3.1.02 installed on
DB2 Version 5
1. Migrate the DB2 catalog.
2. Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) packages and
plans by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID).
3. For PATROL DB-Alter (ALU) and
PATROL DB-Change Manager (ACM),
rebind all PATROL DB-Alter or
PATROL DB-Change Manager
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).
Then, you will be operating in toleration
mode.
1. Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) packages and
plans by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID).
2. For PATROL DB-Alter (ALU) and
PATROL DB-Change Manager (ACM),
rebind all PATROL DB-Alter or
PATROL DB-Change Manager
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).
As an alternative, you can perform a Full
installation of ALTER or CHANGE
MANAGER 6.2E. Then, you will be
operating in exploitation mode.
Provided that ALTER, CHANGE
MANAGER, PATROL DB-Alter, or
PATROL DB-Change Manager still exists
in toleration mode, use the fallback
procedures described for toleration mode
and remove the product in exploitation
mode. Any data that you added while you
were in exploitation mode will not be
available in toleration mode.
using ALTER or
CHANGE
MANAGER 6.1D or
later installed on
DB2 Version 5
1. Migrate the DB2 catalog.
2. Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) packages and
plans by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID).
Then, you will be operating in toleration
mode.
Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) 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).
As an alternative, you can perform a Full
installation of ALTER or CHANGE
MANAGER 6.2E. Then, you will be
operating in exploitation mode.
Provided that ALTER, CHANGE
MANAGER, PATROL DB-Alter, or
PATROL DB-Change Manager still exists
in toleration mode, use the fallback
procedures described for toleration mode
and remove the product in exploitation
mode. Any data that you added while you
were in exploitation mode will not be
available in toleration mode.
Table 3-15 Migrating DB2 Version 5 to Version 6 (Part 2 of 4)
If You Are Then To Fall Back Then
