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-6
Migrating Disks Between Systems With the Same
Name and Systems With Different Names
same name and node number. If they do, then the migration is much easier, but the
two systems cannot be connected to the same Expand network at the same time. If
they have different node names and numbers, they can coexist on the same Expand
network, but data migration is more complex.
Migrating Disks Between Systems With the Same Name and
Systems With Different Names
SQL/MP stores system-specific information, such as the node name and number, in
the catalog entries and file labels of the database. SQL/MX stores this system-specific
information in its system catalog. If the disk storage devices are reconnected to a new
system with the same node name and number as the old system, the system migration
is transparent to the database. Migrating SQL/MP or SQL/MX databases between
systems that have the same node name and number requires that the two systems are
not connected simultaneously to the same Expand network.
If the disk storage devices are reconnected to a system with a different node name and
number, you must update the database metadata on the new system to reflect the new
node name and number. Although this approach is more laborious and time
consuming, migrating between systems that have different node names and numbers
allows the two systems to be connected to the same Expand network. You cannot
migrate an SQL/MX database between systems with a different node name and
number.
SQL/MP uses the MODIFY DICTIONARY command to update the database file labels,
the SQL catalog, and user-defined catalogs. The information that the MODIFY
DICTIONARY utility modifies cannot be modified by any other SQL/MP utility
command.
Advantages and Disadvantages
Before choosing this method of migration, consider the advantages and disadvantages
of physically disconnecting and reconnecting disk storage devices as described in
Table 2-2.
Note. This migration method applies only to SQL/MP databases, not SQL/MX databases.
Tools for updating and registering SQL/MX metadata after reconnecting disk storage devices
are currently unavailable.