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-15
Additional Sources of Information
information, see the SQL/MX Reference Manual and SQL/MP Reference Manual,
respectively.
11. In the application source code, verify that hard-coded Guardian object names refer
to the new node of the database and explicitly recompile those applications.
12. To produce optimal query execution plans and ensure proper resolution of
SQL/MP aliases, explicitly SQL compile each embedded SQL program that queries
the moved database.
13. Restart applications that were terminated during the migration.
Additional Sources of Information
•
For more information about the ALTER TABLE MOVE and ALTER INDEX MOVE
statements, see the SQL/MP Reference Manual.
•
For information about managing partitions, see the SQL/MP Installation and
Management Guide.
Migration by Using the BACKUP/RESTORE
and Backup and Restore 2 Utilities
These offline data movement tools can be used to migrate a relatively small and static
database or a small static portion of a large database to the Integrity NonStop
NS-series system.
Advantages and Disadvantages
Before choosing this method of migration, consider the advantages and disadvantages
of using BACKUP/RESTORE on SQL/MP objects and Backup and Restore 2 on
SQL/MX objects as described in Table 2-4.
Table 2-4. Advantages and Disadvantages of Using the BACKUP/RESTORE
Utilities and Backup and Restore 2
Advantages Disadvantages
•
You can use BACKUP/RESTORE
or Backup and Restore 2 when
the two systems are not
connected by a network.
•
The tape backup of the database
is available for use whenever it is
needed.
•
The system must be offline during database
migration.
•
Moving large databases can take a long time.
•
During RESTORE operations, you must have
the same exact number of volumes on the
new system as the old system.