HP Integrity NonStop NS-Series Database Migration Guide Abstract This manual describes how to plan for and migrate SQL/MP, SQL/MX, and Enscribe databases and applications to the HP NonStop Integrity NS-series system. Product Version NonStop SQL/MX Releases 2.0, 2.1, and 2.2 (SPR identifier for Release 2.2: H22^ACF) Supported Release Version Updates (RVUs) This publication supports H06.04 and all subsequent H-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version 540469-001 NonStop SQL/MX Releases 2.0, 2.1, and 2.
HP Integrity NonStop NS-Series Database Migration Guide Index Tables What’s New in This Manual v Manual Information v New and Changed Information vi About This Manual vii Audience vii Organization vii Related Documentation ix Notation Conventions xii 1.
2. Migrating an SQL/MP or SQL/MX Database (continued) Contents 2.
3. Migrating an Enscribe Database (continued) Contents 3. Migrating an Enscribe Database (continued) Moving Enscribe Files to the New System 3-4 Steps for Moving an Enscribe Database Using RDF 3-4 Steps for Moving an Enscribe Database Using the BACKUP/RESTORE Utilities 3-6 Steps for Moving an Enscribe Database Using SQLCI DUP 3-6 Steps for Moving an Enscribe Database Using FUP DUP 3-7 4.
Contents 6. Falling Back an SQL/MX, SQL/MP, or Enscribe Database 6. Falling Back an SQL/MX, SQL/MP, or Enscribe Database Index Tables Table 1-1. Table 1-2. Table 1-3. Table 1-4. Table 1-5. Table 1-6. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5.
What’s New in This Manual Manual Information HP Integrity NonStop NS-Series Database Migration Guide Abstract This manual describes how to plan for and migrate SQL/MP, SQL/MX, and Enscribe databases and applications to the HP NonStop Integrity NS-series system. Product Version NonStop SQL/MX Releases 2.0, 2.1, and 2.2 (SPR identifier for Release 2.2: H22^ACF) Supported Release Version Updates (RVUs) This publication supports H06.
New and Changed Information What’s New in This Manual New and Changed Information This is a new manual. Its content was originally provided in a section of the SQL Supplement for H-Series Servers.
About This Manual This manual describes how to migrate SQL/MP, SQL/MX, and Enscribe databases to an Integrity NonStop NS-series system. Audience This manual is intended for database administrators (DBAs), HP support personnel working with customers, and others who are responsible for planning and performing database and application migration from a NonStop S-series system to an Integrity NonStop NS-series system.
Organization About This Manual Section 4, Migrating SQL/MP, SQL/MX, and Enscribe Applications Provides guidelines for migrating SQL and Enscribe applications to an Integrity NonStop NS-series system. Section 5, Post-Migration Activities Describes the activities you should perform to ensure optimal database performance after you have migrated your database and applications.
Related Documentation About This Manual Related Documentation This manual is part of the HP NonStop SQL/MX library of manuals, which includes: Introductory Guides SQL/MX Comparison Guide for SQL/MP Users SQL/MX Quick Start Reference Manuals SQL/MX Reference Manual SQL/MX Messages Manual Installation Guides SQL/MX Installation and Management Guide NSM/web Installation Guide Connectivity Manuals SQL/MX Connectivity Service Manual Migration Guides SQL/MX Database and Application Migration Guide
Related Documentation About This Manual Introductory Guides SQL/MX Comparison Guide for SQL/MP Users Describes SQL differences between NonStop SQL/MP and NonStop SQL/MX. SQL/MX Quick Start Describes basic techniques for using SQL in the SQL/MX conversational interface (MXCI). Includes information about installing the sample database. Reference Manuals SQL/MX Reference Manual Describes the syntax of SQL/MX statements, MXCI commands, functions, and other SQL/MX language elements.
About This Manual Related Documentation Data Management Guides SQL/MX Data Mining Guide Describes the SQL/MX data structures and operations to carry out the knowledge-discovery process. SQL/MX Report Writer Guide Describes how to produce formatted reports using data from an SQL/MX database. DataLoader/MX Reference Manual Describes the features and functions of the DataLoader/MX product, a tool to load SQL/MX databases.
About This Manual Notation Conventions These manuals are part of the SQL/MP library of manuals and are essential references for information about SQL/MP Data Definition Language (DDL) and SQL/MP installation and management: Related SQL/MP Manuals SQL/MP Reference Manual Describes the SQL/MP language elements, expressions, predicates, functions, and statements. SQL/MP Installation and Management Guide Describes how to plan, install, create, and manage an SQL/MP database.
About This Manual General Syntax Notation [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces.
About This Manual General Syntax Notation Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing.
1 Preparing to Migrate to an Integrity NonStop NS-Series System This section describes the methods for planning and developing a strategy for migrating an SQL/MP, SQL/MX, or Enscribe database from an HP NonStop S-series system to an HP Integrity™ NonStop NS-series system.
Preparing to Migrate to an Integrity NonStop NS-Series System HP NonStop Evolution Assessment Service Table 1-1. HP NonStop Evolution Assessment Service IT Domains (page 2 of 3) IT Domain Description of Service Data and database Obtain detailed information about data storage, the OSS file system and the current database, including the characteristics of SQL/MP or SQL/MX tables or Enscribe files.
Preparing to Migrate to an Integrity NonStop NS-Series System HP NonStop Applications and Database Migration Planning and Design Service Table 1-1. HP NonStop Evolution Assessment Service IT Domains (page 3 of 3) IT Domain Description of Service Operating system and middleware Migrating from the G-series to H-series operating system and middleware requires some changes in software.
Preparing to Migrate to an Integrity NonStop NS-Series System Planning the Migration plan, and a statement of work for services to assist in the implementation of the project plan. For more information about this service, contact your local HP NonStop account representative, or email SDIinfo@hp.com. Planning the Migration Before you begin to migrate applications and databases, you must first plan the migration.
Preparing to Migrate to an Integrity NonStop NS-Series System Assess the Current System’s Applications and Database Environments Table 1-2.
Preparing to Migrate to an Integrity NonStop NS-Series System Assess the Current System’s Applications and Database Environments Table 1-2.
Preparing to Migrate to an Integrity NonStop NS-Series System Plan the New System’s Applications and Database Environments Table 1-2. Assessing the Applications and Database on the Current System (page 3 of 3) For this environment All NonStop database environments SQL/MP or SQL/MX database Obtain this information • • • • • • • • • • Enscribe database • • Databases and data files that are candidates for migration. Provide high-level information about their size, location, and performance.
Preparing to Migrate to an Integrity NonStop NS-Series System Developing a Database Migration Strategy Table 1-3.
Preparing to Migrate to an Integrity NonStop NS-Series System Phased Migration Versus Rapid Migration Table 1-4.
Preparing to Migrate to an Integrity NonStop NS-Series System Selecting Data Movement Tools Phased (or side-by-side) migration involves careful and incremental replication of your current production database to the Integrity NonStop NS-series platform. While the NonStop S-series production system continues to operate as the primary database, preselected portions of the database are copied in phases over an Expand network to a new Integrity NonStop NS-series system.
Preparing to Migrate to an Integrity NonStop NS-Series System Selecting Data Movement Tools RDF with AutoTMF X X X X X Third-party data replication tools X X X X X HP NonStop AutoSYNC X ALTER TABLE and INDEX MOVE (SQL/MP objects) X X BACKUP/RESTORE (SQL/MP objects) X X X Backup and Restore 2 (SQL/MX objects) X X X SQLCI DUP (SQL/MP objects) X X X MXCI DUP (SQL/MX objects) X X X FUP DUP Moves Enscribe data X X Moves dynamic data X Moves static data X X X Moves data that cann
Preparing to Migrate to an Integrity NonStop NS-Series System Selecting Data Movement Tools HP Integrity NonStop NS-Series Database Migration Guide— 540469-001 1-12
2 Migrating an SQL/MP or SQL/MX Database Caution. Migrating a database from a NonStop S-series system to an Integrity NonStop NS-series system is a complex endeavor. The steps in this subsection provide a general overview of how to migrate a database using several tools. For assistance in migrating your database, consult HP migration services. For information about these services, see Using HP Migration Services on page 1-1. • • • • • • • • Migrating SQL/MX Release 1.8 to SQL/MX Release 2.
Migrating an SQL/MP or SQL/MX Database • • • SQL/MX Interoperability Between Systems If you are migrating SQL/MP tables, install NonStop SQL/MP on the Integrity NonStop NS-series system. If you are migrating SQL/MX Release 2.x and your database contains SQL/MP tables, install NonStop SQL/MP and NonStop SQL/MX on the Integrity NonStop NS-series system. If you are migrating SQL/MX Release 2.x and your database contains only SQL/MX tables, install NonStop SQL/MX on the Integrity NonStop NS-series system.
Steps for Moving an SQL/MP Database Using RDF Migrating an SQL/MP or SQL/MX Database Table 2-1. Advantages and Disadvantages of Using RDF Advantages • • Allows for quick and reliable online migration of large databases. After migration, you can continue to maintain an online copy of your database on the NonStop S-series system and immediately make it your fallback database if necessary. Disadvantages • • RDF requires that the copied database be identical to the original database.
Migrating an SQL/MP or SQL/MX Database • Steps for Moving an SQL/MX Database Using RDF If you do not have sufficient disk space and prefer to use a high-speed, high-bandwidth Expand network connection, create your empty database on the Integrity NonStop NS-series system and use SQLCI LOAD commands with the SHARE option to populate the empty database with the primary database records over the network.
Migrating an SQL/MP or SQL/MX Database • Additional Sources of Information If you have enough disk space on your NonStop S-series system to hold a copy of the primary database: ° Create temporary and permanent catalogs and schemas on the Integrity NonStop NS-series system. ° Use INSERT...SELECT statements to copy the primary SQL/MX database into the empty database on the NonStop S-series system. ° Back up the duplicate database and restore it on the Integrity NonStop NS-series system.
Migrating an SQL/MP or SQL/MX Database 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. Note. This migration method applies only to SQL/MP databases, not SQL/MX databases.
Steps for Moving an SQL/MP Database by Physically Disconnecting and Reconnecting Disk Migrating an SQL/MP or SQL/MX Database Table 2-2. Advantages and Disadvantages of Physically Disconnecting and Reconnecting Disk Storage Devices Advantages • In general, this method is faster than using a DUP or BACKUP/RESTORE method because you do not need to copy data. Disadvantages • • This method is an offline operation; it requires system downtime.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MX Database by Physically Disconnecting and Reconnecting Disk 3. 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.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MP Database by Physically Disconnecting and Reconnecting Disk disk storage devices, I/O enclosures, and their interconnections on the NonStop S-series system and Integrity NonStop NS-series system, see the hardware installation, planning, site preparation, and supported hardware manuals for these systems. 5.
Migrating an SQL/MP or SQL/MX Database 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.
Migrating an SQL/MP or SQL/MX Database Additional Sources of Information MODIFY DICTIONARY CATALOG commands in the correct order to correctly update the database. • Partitioned objects. Node numbers in the file labels of other partitions of tables and indexes are not modified unless the other partitions are specified in the MODIFY DICTIONARY LABEL command.
Steps for Moving an SQL/MP Database by Using ALTER TABLE MOVE and ALTER INDEX MOVE Migrating an SQL/MP or SQL/MX Database Table 2-3. Advantages and Disadvantages of Using ALTER TABLE MOVE and ALTER INDEX MOVE Statements Advantages • • You can keep SQL/MP database objects online during most of the move. You can increase the size of individual partitions and split partitions to take advantage of the disk storage capabilities of the Integrity NonStop NS-series system.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MP Database by Using ALTER TABLE MOVE and ALTER INDEX MOVE If the catalog version is less than 350, you might need to install the latest SQL/MP software before issuing an UPGRADE CATALOG command on the source system. For more information, see the SQL/MP Reference Manual and the SQL/MP Installation and Management Guide. 2.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MP Database by Using ALTER TABLE MOVE and ALTER INDEX MOVE ONCOMMITERROR COMMIT BY REQUEST; ... The WITH SHARED ACCESS option allows concurrent DML operations on the database object during most of the move. During the commit phase, the ALTER TABLE MOVE statement requires exclusive access to all partitions of the database object and destroys opens from applications that attempt DML operations on the database object.
Additional Sources of Information Migrating an SQL/MP or SQL/MX Database 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.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MP Database Using the BACKUP/RESTORE Utilities Steps for Moving an SQL/MP Database Using the BACKUP/RESTORE Utilities 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 the BACKUP/RESTORE utilities. For assistance in migrating your database, consult HP migration services.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MX Database Using Backup and Restore 2 Steps for Moving an SQL/MX Database Using Backup and Restore 2 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 Backup and Restore 2. For assistance in migrating your database, consult HP migration services.
Migrating an SQL/MP or SQL/MX Database Migration by Using SQLCI DUP and MXCI DUP Migration by Using SQLCI DUP and MXCI DUP Using SQLCI DUP You can use SQLCI DUP to duplicate individual SQL/MP objects (for example, a table, index, view, or an SQL program stored in a Guardian file) from one node to another, interactively, when the nodes are connected in a network and the requesting user ID has the appropriate remote security to allow the transfer.
Steps for Moving an SQL/MP Database Using SQLCI DUP Migrating an SQL/MP or SQL/MX Database Table 2-5. Advantages and Disadvantages of Using SQLCI DUP and MXCI DUP Advantages • • 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. Disadvantages • • DUP is an offline operation; it requires application downtime. The downtime required depends on the size of the database to be copied.
Migrating an SQL/MP or SQL/MX Database Steps for Moving an SQL/MX Database Using MXCI DUP 7. Verify the status of the database by using the VERIFY utility or by using catalog queries. 8. On the target node, create DEFINE names that point to the new locations of SQL/MP tables and views. 9. On the target node, SQL compile the programs that were duplicated. For information on compiling SQL programs, see Section 4, Migrating SQL/MP, SQL/MX, and Enscribe Applications. 10.
Migrating an SQL/MP or SQL/MX Database • • • Additional Sources of Information For detailed information about using the SQLCI DUP command, see the SQL/MP Reference Manual. For detailed information about using the MXCI DUP command, see the SQL/MX Reference Manual. For information about migrating a database with audited objects, see the TMF Operations and Recovery Guide.
Migrating an SQL/MP or SQL/MX Database Additional Sources of Information HP Integrity NonStop NS-Series Database Migration Guide— 540469-001 2- 22
3 Migrating an Enscribe Database This section addresses these topics: • • • • Converting Enscribe Data and Applications to SQL/MP on the New System on page 3-1 Converting Enscribe Data and Applications to SQL/MX on the New System on page 3-2 Converting DDL Dictionaries for Enscribe Applications on the New System on page 3-2 Moving Enscribe Files to the New System on page 3-4 For information about Enscribe applications, see Section 4, Migrating SQL/MP, SQL/MX, and Enscribe Applications. Note.
Migrating an Enscribe Database Converting Enscribe Data and Applications to SQL/MX on the New System During load operations, the Escort SQL Journaling Service keeps track of all changes to Enscribe records and applications on the NonStop S-series system and automatically replicates these changes to the SQL/MP tables on the Integrity NonStop NS-series system. The Journaling Service feature allows Enscribe applications to continue running until both databases are almost fully synchronized. 4.
Migrating an Enscribe Database DDL Compiler Problem Symptoms the definitions, translates the definitions to FUP commands, or generates objectdefinition source code in or more programming languages. A DDL dictionary is a repository for the DDL definitions. It helps to maintain consistency so that the same data, regardless of where it is used, is described in the same way. DDL dictionaries provide descriptions of all the applications that use an Enscribe database.
Migrating an Enscribe Database Moving Enscribe Files to the New System Output source for DDL is closed. Dictionary on subvol $DATA4.ENDICT is closed. Dictionary on subvol $DATA4.ENDICT is purged. Audited dictionary created on subvol $DATA4.ENDICT. Dictionary opened on subvol $DATA4.ENDICT for update access. In this example, the ?DDL TEMP command creates the file TEMP and uses it to store DDL SOURCE definitions.
Migrating an Enscribe Database Steps for Moving an Enscribe Database Using RDF 2. Develop the scripts that will manually create empty files for an empty database and that will load the files with that data. 3. From the NonStop S-series system, initialize, configure, and start RDF with updating disabled (START RDF, UPDATE OFF). 4.
Migrating an Enscribe Database Steps for Moving an Enscribe Database Using the BACKUP/RESTORE Utilities Steps for Moving an Enscribe Database Using the BACKUP/RESTORE Utilities 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 an Enscribe database using the BACKUP/RESTORE utilities. For assistance in migrating your database, consult HP migration services.
Migrating an Enscribe Database Steps for Moving an Enscribe Database Using FUP DUP 4. Confirm that the Enscribe data and applications were successfully migrated to the Integrity NonStop NS-series system. 5. From the Integrity NonStop NS-series system, start the Enscribe applications. 6. From the Integrity NonStop NS-series system, make new TMF online dumps of all audited Enscribe objects. For more information about using SQLCI DUP, see the SQL/MP Installation and Management Guide.
Migrating an Enscribe Database Steps for Moving an Enscribe Database Using FUP DUP HP Integrity NonStop NS-Series Database Migration Guide— 540469-001 3 -8
4 Migrating SQL/MP, SQL/MX, and Enscribe Applications You can migrate your SQL and Enscribe applications independently of the database or while migrating the database. For example, you might move specific applications to the Integrity NonStop NS-series system as part of a phased migration and test the applications extensively on the new system before migrating the production database.
Migrating SQL/MP, SQL/MX, and Enscribe Applications Enscribe Applications Enscribe Applications Applications that access Enscribe files and records can be written in these languages, which are supported on both TNS/R and TNS/E systems: • • • • • C and C++ languages COBOL language HP Transaction Application Language (TAL) Portable Transaction Application Language (pTAL) FORTRAN Note. Pascal programs are not supported on TNS/E systems.
Migrating SQL/MP, SQL/MX, and Enscribe Applications TNS Object Files of Enscribe Applications need to make some minor changes to the source code before compilation. For details on required source code changes, see the H-Series Application Migration Guide. To compile these programs on a TNS/E system... See...
Migrating SQL/MP, SQL/MX, and Enscribe Applications Preparing TNS and TNS/R Object Files of Enscribe Applications To Access SQL/MP Tables 37> escort Escort Command Interpreter - Version 1.7.0 - 01MAY2005 - System \NSKNED Copyright Carr Scott Software Incorporated 1996-2004 Escort 1? PREPARE OGET , LIBRARY libname; --- $PRPC.TEST.OGET preparation complete --- Escort SQL User Library $DATA.ESCORT.
Migrating SQL/MP, SQL/MX, and Enscribe Applications TAL and pTAL Programs That Use Embedded SQL/MP Example: Combining TNS Libraries This example combines TNS libraries. BIND @SELECT LIST * OFF @ADD * FROM myuserlb @ADD * FROM $SYSTEM.ESCORT.ESCRUNTM @SET LIKE $SYSTEM.ESCORT.ESCRUNTM @SET HIGHPIN ON @SET HIGHREQUESTERS ON @BUILD myuserlb! Use the file myuserlib as the LIBRARY libname option in the Escort SQL PREPARE command as shown in Example: Preparing a TNS File Object File on page 4-3.
Migrating SQL/MP, SQL/MX, and Enscribe Applications • • • • TAL Programs That Contain Embedded SQL/MP Statements TAL Programs That Contain Embedded SQL/MP Statements on page 4-6 pTAL Programs That Call Embedded SQL/MP Routines on page 4-6 Object Name References and Resolution on page 4-6 SQL Compilation on page 4-7 TAL Programs That Contain Embedded SQL/MP Statements As you can with other TNS object files, you can usually interpret TAL programs on TNS/E systems without recompiling the source code.
Migrating SQL/MP, SQL/MX, and Enscribe Applications SQL Compilation the new system, and omit or change the node name in the DEFINE name mappings of your script files. Before you move embedded SQL/MP programs to an Integrity NonStop NS-series system, set up commands or scripts on the TNS/E system to reestablish DEFINE names for proper object name resolution.
Migrating SQL/MP, SQL/MX, and Enscribe Applications TNS Object Files of Embedded SQL Programs to a TNS/E host or by compiling the source code directly on the TNS/E system. You might need to make some minor changes to the source code before compilation. For details on required source code changes, see the H-Series Application Migration Guide.
Migrating SQL/MP, SQL/MX, and Enscribe Applications SQL Compilation To ensure proper resolution of DEFINE names, you do not need to SQL compile each program that uses DEFINEs because these programs use the run-time DEFINEs that you set in the execution environment of the TNS/E system. However, to ensure optimal query execution plans and prevent automatic recompilation, explicitly SQL compile all embedded SQL programs on the TNS/E system. For more information, see SQL Compilation on page 4-9.
Migrating SQL/MP, SQL/MX, and Enscribe Applications • • Object Name References Default Heap and Stack Sizes on page 4-11 CLASSPATH and _RLD_LIB_PATH Environment Variables on page 4-11 Note. The NonStop Server for Java 4 on TNS/E systems has the same Java features and functions as the NonStop Server for Java 4.2 on TNS/R systems. The JDBC/MX driver on TNS/E systems has the same features and functions as the JDBC/MX driver V32 on TNS/R systems.
Migrating SQL/MP, SQL/MX, and Enscribe Applications Default Heap and Stack Sizes Default Heap and Stack Sizes The default heap and stack sizes are larger on TNS/E systems. For more information, see the NonStop Server for Java Programmer’s Reference for SDK 1.4.2.
Migrating SQL/MP, SQL/MX, and Enscribe Applications Stored Procedures in Java (SPJs) HP Integrity NonStop NS-Series Database Migration Guide— 540469-001 4- 12
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 a
Post-Migration Activities • Evaluating SQL Plans on the New System If the database is populated by SQL/MP tables that are accessed by SQL/MX, perform SQL/MP UPDATE STATISTICS on those tables and perform SQL/MX UPDATE STATISTICS, in either order. Note. To avoid locking problems, do not attempt to run SQL/MP UPDATE STATISTICS and SQL/MX UPDATE STATISTICS on the same object concurrently. SQL/MX UPDATE STATISTICS obtains far more detailed information than does SQL/MP UPDATE STATISTICS.
6 Falling Back an SQL/MX, SQL/MP, or Enscribe Database Those for whom business continuity is especially important should be prepared to fall back their database from the Integrity NonStop NS-series system to the NonStop S-series system if unforeseen problems make it necessary. The objective is to quickly and successfully get the latest good version of the database on the NonStop S-series system with little or no interruption to applications and end users.
Falling Back an SQL/MX, SQL/MP, or Enscribe Database HP Integrity NonStop NS-Series Database Migration Guide— 540469-001 6 -2
Index A Application migration 4-1/4-11 D Database migration applications 4-1/4-11 assessing the current system 1-4 by ALTER TABLE MOVE and ALTER INDEX MOVE statements 2-11/2-15 by disconnecting and reconnecting disks 2-5/2-11 by online database replication 2-2/2-5 by using BACKUP/RESTORE and Backup and Restore 2.
H Index H HP migration services HP NonStop Applications and Database Planning and Design Service 1-3 HP NonStop Evolution Assessment Service 1-1 J Java applications, migrating 4-9 JDBC/MP applications, migrating 4-9 JDBC/MX applications, migrating 4-9 M Migration See Database migration O ODBC applications, migrating 4-1 P Pascal programs 4-2 pTAL programs, migrating 4-6 S SQLJ applications 4-11 Stored procedures in Java (SPJs), migrating 4-11 T TAL programs, migrating 4-6 HP Integrity NonStop NS-Se
