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-19
Steps for Moving an SQL/MP Database Using
SQLCI DUP
Steps for Moving an SQL/MP Database Using SQLCI DUP
1. Determine the name of the SQL catalogs involved in the move by querying the
CATALOGS table.
2. Determine the names of the SQL/MP objects involved in this move by querying the
catalogs identified in Step 1. The TABLES catalog table can be queried to obtain a
list of tables.
3. Determine the dependencies by using the DISPLAY USE OF command or by
using catalog queries. It is important that you consider the interdependencies of
the database for the move.
The layout of the dependencies determines the structure of the correct DUP
command to be used in Step 6. For more information about interpreting
dependencies, see the information about catalog mapping schemes for DUP in the
SQL/MP Installation and Management Guide.
4. If you need a consistent copy of the database, make sure that SQL/MP objects are
not in use, and stop all applications that access the database.
5. Because DUP requires that you create new catalogs before you perform the move
operation, you may want to create an OBEY command file that creates the new
catalogs and duplicates the database.
6. Using the table names identified in Step 2, use the SQLCI DUP command to
duplicate the SQL/MP database from the source node to the target node.
Table 2-5. Advantages and Disadvantages of Using SQLCI DUP and MXCI DUP
Advantages Disadvantages
•
In general, DUP is faster than
using a BACKUP/RESTORE
method.
•
DUP creates new objects on the
target system and creates the
necessary metadata for the new
objects.
•
DUP is an offline operation; it requires
application downtime. The downtime required
depends on the size of the database to be
copied.
•
You must DUP all objects in the database.
For a large database, this action can be
time-consuming and cumbersome. However,
using wildcard characters for SQL/MP file
names can help reduce the difficulty.
Wildcard characters are not permitted for
MXCI DUP.
Caution. Migrating a database from a NonStop S-series system to an Integrity NonStop
NS-series system is a complex endeavor. These steps provide a general overview of how to
migrate a database using SQLCI DUP. For assistance in migrating your database, consult HP
migration services. For information about these services, see Using HP Migration Services
on
page 1-1.
Note. Make sure to log the commands and information returned in the DUP operations.