Maintaining BMC Software Administrative Products
BMC Software, Inc., Confidential and Proprietary Information
Chapter 3 Performing Additional Installation Tasks 3-39
To maintain BMC Software Administrative Products when you create a new
DB2 Version 5 catalog, use the guidelines in Table 3-18.
using catalog
indirection and
ALTER, CHANGE
MANAGER,
PATROL DB-Alter,
or PATROL
DB-Change
Manager in
toleration mode
1. Perform a Full installation of ALTER or
CHANGE MANAGER 6.2D. Then, you
will be operating in exploitation mode.
2. Reinstall catalog indirection.
1. Provided that the previous indirection
still exists, remove the indirect copy or
view in exploitation mode.
2. 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 to remove the product
in exploitation mode.
3. Rebind all indirect packages and
plans for the previous version by using
prdssid
Z (bind packages) and
prdssid
B (bind plans) (where
ssid
is
the subsystem ID).
using catalog
indirection and
CATALOG
MANAGER
Reinstall catalog indirection. 1. Provided that the previous indirection
still exists, remove the indirect copy or
view in exploitation mode.
2. Rebind all indirect packages and
plans for the previous version by using
prdssid
Z (bind packages) (where
ssid
is the subsystem ID).
Table 3-18 Creating a New DB2 Version 5 Catalog
If You Are Then
using any of the
Administrative Products
Perform a Full installation of the following
Administrative Products:
• ALTER or CHANGE MANAGER 6.2D
• CATALOG MANAGER 6.2
• DASD MANAGER PLUS 6.1
Then, you will be operating in exploitation mode.
using catalog indirection Install catalog indirection.
Table 3-17 Migrating DB2 Version 4 to Version 5 (Part 5 of 5)
If You Are Then To Fall Back Then
