NonStop NS-Series Database Migration Guide

HP Integrity NonStop NS-Series Database Migration Guide—540469-001
5-1
5
Post-Migration Activities
After you have migrated your applications and database to the Integrity NonStop
NS-series system, perform these activities to ensure optimal database performance:
•
Ensuring Object Name Resolution on page 5-1
•
Updating Table Statistics on page 5-1
•
Evaluating SQL Plans on the New System on page 5-2
•
Monitoring Performance on the New System on page 5-2
Ensuring Object Name Resolution
When you move your database to another system, make sure that any component that
refers to another system entity uses the correct reference, including the new system
name. This requirement applies to Pathway files, scripts files, and application
programs.
On the Integrity NonStop NS-series system, SQL statements in application programs
that refer to database objects must refer to valid objects and either correctly name
those objects or correctly map to them. If database object names in programs refer to
DEFINEs, set the DEFINEs in the environment where the programs will run. If the
object names refer to SQL/MP aliases, the SQL/MP aliases must be present on the
local system. These DEFINEs and SQL/MP aliases must correctly map to existing and
accessible database objects.
For more information about object name resolution for migrated applications, see
Object Name References and Resolution on page 4-6 and Object Name References
and Resolution on page 4-8. Also see the SQL/MX Programming Manual for C and
COBOL, SQL/MP Programming Manual for C, and SQL/MP Programming Manual for
COBOL.
Updating Table Statistics
The migrated database on the Integrity NonStop NS-series system needs to be
updated to make sure that it contains accurate SQL/MP or SQL/MX table statistics:
•
If the database is populated by SQL/MX tables, perform SQL/MX UPDATE
STATISTICS on those tables.
•
If the database is populated by SQL/MP tables, perform SQL/MP UPDATE
STATISTICS on those tables.