NonStop NS-Series Database Migration Guide

Migrating an SQL/MP or SQL/MX Database
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
2-10
Steps for Moving an SQL/MP Database by
Physically Disconnecting and Reconnecting Disk
the new system. The result is a faster migration but slower performance due to
the audit trails on the old disk drives.)
4. Reconnect the disk storage devices.
°
If the new system contains a TMF configuration: Reconnect the disk storage
devices containing the database volumes. Update the TMF configuration on
the new system by adding the migrated database volumes. TMF automatically
starts audit trails for the migrated database.
°
If the new system does not contain a TMF configuration: Make sure TMF is
stopped on the new system, then reconnect the disk storage devices
containing the database volumes, the TMF audit volumes, and the TMF
configuration. Map TMF to the correct configuration subvolume, then start
TMF.
5. Use the SQLCI MODIFY DICTIONARY LABEL command to change node numbers
in file labels of the SQL/MP objects and SQL/MP object programs on the new
system.
6. Use the SQLCI MODIFY DICTIONARY CATALOG command to change node
names in the catalogs (user-defined or system) on the new, local node.
7. Use the SQLCI MODIFY DICTIONARY REGISTER command to register user-
defined catalogs in the new, local system catalog.
8. Use the VERIFY utility to verify that the database is in a consistent state.
9. If necessary, change DEFINE name mappings for programs to reflect the new
location of the objects and object programs, and recompile the programs.
MODIFY DICTIONARY Limitations
•
Remote nodes. Catalog tables and file labels on remote nodes are not modified.
•
User-defined SQL/MP object files. Node names in user-defined SQL/MP objects
are not modified. For example, MODIFY DICTIONARY does not modify a node
name that is stored in a column of a user-defined SQL/MP table.
•
SQL program files. SQL programs can refer to an SQL/MP object using either a
DEFINE or the Guardian file name of the object. If DEFINEs are used, both the
DEFINE name and the Guardian file name of the SQL/MP object that the DEFINE
refers to are stored in the program file (not in the label). If Guardian file names are
used, they are stored in the program file in internal network form. MODIFY
DICTIONARY does not change node numbers in these names that are stored in
the SQL program file.
•
Dependent objects. Node numbers in the file labels of dependent objects are not
modified unless the dependent object is specified in the MODIFY DICTIONARY
LABEL command. The MODIFY DICTIONARY CATALOG command does not
modify information about dependent objects in other catalogs unless the other
catalogs are specified. You must run the MODIFY DICTIONARY LABEL and the