HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide Abstract This manual explains how to migrate databases and applications from SQL/MX Release 2.3.x and SQL/MX Release 3.0 to SQL/MX Release 3.1, and how to manage different versions of NonStop SQL/MX. Product Version NonStop SQL/MX Release 3.1 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.
Document History Part Number Product Version Published 540435-002 NonStop SQL/MX Releases 2.0, 2.1, 2.2 February 2006 540435-005 NonStop SQL/MX Release 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.3.3, 2.3.4 April 2010 666210-001 NonStop SQL/MX Release 3.0 June 2011 663853-001 NonStop SQL/MX Release 3.
Legal Notices Copyright 2011 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
What’s New in This Manual Manual Information HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide Abstract This manual explains how to migrate databases and applications from SQL/MX Release 2.3.x and SQL/MX Release 3.0 to SQL/MX Release 3.1, and how to manage different versions of NonStop SQL/MX. Product Version NonStop SQL/MX Release 3.1 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.
What’s New in This Manual New and Changed Information Added Removing Security Administrator Grants on page A-1. Added Identifying Tables That Contain an IDENTITY Column on page B-1. Added Identifying tables where the ownership has changed on page C-1 Made minor modifications throughout the manual. HP NonStop SQL/MX Release 3.
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide Index Legal Notices Figures Tables 1 What’s New in This Manual 3 Manual Information 3 New and Changed Information 3 About This Manual v Audience v What This Manual Does Not Cover Organization vi Related Documentation vi Notation Conventions viii v 1.
Contents 4. Upgrading to SQL/MX Release 3.
Contents A. Removing Security Administrator Grants Stopping TMF 5-7 Installing SQL/MX Release 3.0 5-8 Installing SQL/MX Release 2.3.4 5-8 Accessing the database 5-8 Installing SQL/MX Release 2.x 5-9 Migrating applications after system fallback Changes required after falling back 5-9 5-9 A. Removing Security Administrator Grants B. Identifying Tables That Contain an IDENTITY Column C. Identifying tables where the ownership has changed Index Figures Figure 2-1. Figure 2-2. Figure 2-3. Figure 4-1.
Contents HP NonStop SQL/MX Release 3.
About This Manual This manual explains how to migrate databases and applications from SQL/MX Release 2.3.x and SQL/MX Release 3.0 to SQL/MX Release 3.1, and how to manage different versions of SQL/MX. NonStop SQL/MX is a relational database management system for the HP NonStop server and is based on the ANSI/ISO/IEC 9075:1999 SQL standard, commonly referred to as SQL:1999. Throughout this manual, references to SQL/MX Release 2.x indicate SQL/MX Release 2.0, SQL/MX Release 2.1, SQL/MX Release 2.
About This Manual Organization Organization Section 1, Overview of SQL/MX Migration Defines migration terminology, provides planning considerations, and describes where you can go for further assistance. Section 2, Considerations for upgrading to SQL/MX Release 3.1 Discusses the factors that you must consider before upgrading to SQL/MX Release 3.1.
About This Manual SQL/MX Glossary Related Documentation Defines SQL/MX terminology. Installation Guides SQL/MX Installation and Management Guide Describes how to plan for, install, create, and manage a SQL/MX database. Explains how to use installation and management commands and utilities. NSM/web Installation Guide Describes how to install NSM/web and troubleshoot NSM/web installations.
About This Manual Notation Conventions Application Development Guides SQL/MX Programming Manual for C and COBOL Describes how to embed SQL/MX statements in ANSI C and COBOL programs. SQL/MX Query Guide Describes how to understand query execution plans and write optimal queries for a SQL/MX database. SQL/MX Queuing and Publish/Subscribe Services Describes how NonStop SQL/MX integrates transactional queuing and publish/subscribe services into its database infrastructure.
About This Manual General Syntax Notation UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words.
About This Manual General Syntax Notation … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation.
About This Manual !i:i. Notation for Messages In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length , filename2:length ) ; !i:i !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
About This Manual Change Bar Notation either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
1 Overview of SQL/MX Migration This section introduces the process of migrating to SQL/MX Release 3.1 and discusses the following topics: Migration terminology on page 1-1 Planning for migration on page 1-1 Guidelines for conducting the migration on page 1-2 Assistance with migration on page 1-3 Migration terminology You must be familiar with the following terms, which are used throughout the manual: Version. A product version or the version of a software component. Release.
Overview of SQL/MX Migration Guidelines for conducting the migration If the migration can be broken into phases, each phase must include its own complete plan: Migration Plan Plan for migrating applications Plan for fallback Plan for updating disaster recovery or RDF configuration and procedures Plan for validating that migration is successful For more information, see... Section 4, Upgrading to SQL/MX Release 3.1 Section 5, Falling Back from SQL/MX Release 3.
Overview of SQL/MX Migration Assistance with migration Assistance with migration Specific strategies for migrating to SQL/MX Release 3.1 depend on your specific database environment and business needs. Without the help of migration experts and special tools, determining and implementing a migration strategy can be timeconsuming and costly.
Overview of SQL/MX Migration NonStop solutions development and implementation HP NonStop SQL/MX Release 3.
2 Considerations for upgrading to SQL/MX Release 3.1 If you are currently using SQL/MX, to obtain new functionalities, performance enhancements, and bug fixes, you might want to upgrade to a newer version. This section discusses the factors that you must consider before upgrading to SQL/MX Release 3.1, and addresses the following topics: Migration path on page 2-1 Compatibility of SQL/MX 3.1 systems on page 2-1 Working with v3100, v3000, and v1200 objects in SQL/MX Release 3.
Considerations for upgrading to SQL/MX Release 3.1 Compatibility of SQL/MX 3.1 systems Figure 2-2. Compatibility of SQL/MX releases in a network R2.3.x OR R3.1 R3.0 R3.1 R3.1 If your network includes multiple versions of SQL/MX, such as SQL/MX Release 2.3.3 and SQL/MX Release 2.3.4, you must migrate all of them to SQL/MX Release 3.1 to ensure compatibility, as shown in Figure 2-3. Figure 2-3. Compatibility of SQL/MX releases in a network after migration Before migration After migration R2.3.
Considerations for upgrading to SQL/MX Release 3.1 Working with v3100, v3000, and v1200 objects in SQL/MX Release 3.1 Working with v3100, v3000, and v1200 objects in SQL/MX Release 3.1 In SQL/MX Release 3.1, a catalog can contain v1200, v3000, or v3100 schemas, but not a mixture of the versions. A CREATE SCHEMA statement will create a new schema of the same version as those schemas in the catalog. For example, suppose that a catalog contains some v3000 schemas.
Considerations for upgrading to SQL/MX Release 3.1 Conversions from numeric to char or varchar Example 1 >>create table tnumeric (a numeric (18,6)); --- SQL operation complete. >> >>insert into tnumeric values (123456789012.345678); --- 1 row(s) inserted. >> >>select cast(a * 10 as char(18)) from tnumeric; *** ERROR[8402] A string overflow occurred during the evaluation of a character expression.
Considerations for upgrading to SQL/MX Release 3.1 New features in SQL/MX Release 3.1 Value:123456789012345678 to Target Type:VARCHAR(REC_BYTE_V_ASCII). --- 0 row(s) selected. >> >>select cast(a * a as char(18)) from tnumeric; (EXPR) -----------------9.000000000000 *** ERROR[8402] A string overflow occurred during the evaluation of a character expression.
Considerations for upgrading to SQL/MX Release 3.1 New metadata in SQL/MX Release 3.1 New metadata in SQL/MX Release 3.1 The change of ownership and separation of privileges features require new metadata tables to store privilege information. These new metadata tables are created when SQL is initialized on SQL/MX Release 3.1 or when the metadata is upgraded. The UPGRADE command creates the SYSTEM_SECURITY_SCHEMA in the system catalog, and then creates and initializes the tables in that schema.
3 Version management and interoperability This section covers these topics: NonStop SQL/MX releases on page 3-1 Interoperability of SQL/MX releases on page 3-7 Versions of SQL/MX software components on page 3-7 NonStop SQL/MX releases A SQL/MX release identifies a set of SQL/MX products as belonging to a given version of NonStop SQL/MX.
Version management and interoperability SQL/MX releases on systems running H-Series RVUs and J-Series RVUs Release 3.1. Table 3-1. SQL/MX releases on systems running H-Series or J-series RVUs SQL/MX Release Product Version Identifier SPR Identifier Availability Date of Initial Release 3.1 H31 N/A General 10/2011 Delivery Supported RVUs Scout or H06.23 SUT H06.23, J06.12 HP NonStop SQL/MX Release 3.
Version management and interoperability Naming scheme for SQL/MX releases Naming scheme for SQL/MX releases NonStop SQL/MX contains many individual products, which are identified by T-numbers. A SQL/MX release name identifies a set of SQL/MX products as belonging to a given release of NonStop SQL/MX. Each SQL/MX release is identified by a three-part release identifier. The following is an example of a release identifier: SQL/MX Release 3.0.
Version management and interoperability Naming scheme for SQL/MX releases Maintenance releases Maintenance releases introduce bug fixes and minimal new functionality. These releases occur most frequently and rarely affect all the component products in the SQL/MX product set. This manual refers to maintenance releases only when they introduce new functionality that requires mentioning.
Version management and interoperability Product version and SPR identifiers For example, this VPROC command displays information for the T1051 product that is associated with SQL/MX Release 3.0.0 for H-series RVUs: T1051H30_14FEB2011_H30_300_1130 The SQL/MX Master Softdoc (T0650) for each SQL/MX release refers to the release name and VPROC information. Product version and SPR identifiers Each SQL/MX release is associated with a product version identifier and possibly an SPR identifier.
Version management and interoperability Delivery of SQL/MX releases Delivery of SQL/MX releases Each SQL/MX release is delivered as a set of Software Product Revisions (SPRs). Some SQL/MX SPRs are first available for downloading from Scout for NonStop Servers and are later available on the next RVU’s site update tape (SUT). Other SQL/MX SPRs are available only on specific RVU SUTs and are not available in Scout for NonStop Servers. Rarely, as is the case for SQL/MX Release 3.
Version management and interoperability Interoperability of SQL/MX releases Interoperability of SQL/MX releases SQL/MX 3.1 does not interoperate with other versions of SQL/MX in an EXPAND network. All systems in the EXPAND network must have SQL/MX 3.1 software installed. Versions of SQL/MX software components Each SQL/MX software component and persistent entity has a version identifier that identifies its software release and that can be understood by other SQL/MX releases.
Version management and interoperability SQL/MX system software version (MXV) Table 3-3. Software version identifiers for SQL/MX Release 3.1 Version Item SQL/MX release version identifier 3.1 Current MXV 3100 Earliest supported MXV 3100 Current schema version and OSV 3100 Earliest supported schema version 1200 Default compiler version 3100 Current plan version 3100 Earliest supported plan version 3000 For more information, see...
Version management and interoperability SQL/MX database object versions Schema version and Object Schema Version A schema version is assigned to each user schema at creation time and is based on the version of the SQL/MX compiler that creates the schema. The Object Schema Version (OSV) of a SQL/MX database object is inherited from the schema where the object resides and determines if the object can be accessed by a particular version of NonStop SQL/MX.
Version management and interoperability SQL/MX query plan and module versions Displaying the OSV and OFV The following example displays the OSV and OFV of a specified database object, where the table name, tlarge, is a value that you specify: >>get version of table tlarge; OBJECT SCHEMA VERSION: 3100 OBJECT FEATURE VERSION: 3100 --- SQL operation complete.
Version management and interoperability Interoperability across schema versions compiled the module. The SQL/MX Release 3.1 compiler produces the module version 3100. For a module to be executed on a node, the module version must be higher than or equal to the earliest supported plan version and lower than or equal to the current plan version. Otherwise, SQL/MX generates a versioning error. Note. SQL/MX Release 3.1 supports v3100 and v3000 plans and modules. However, it does not support SQL/MX Release 2.
Version management and interoperability Interoperability across schema versions HP NonStop SQL/MX Release 3.
4 Upgrading to SQL/MX Release 3.1 This section addresses the following topics: Planning for fallback on page 4-1 Upgrading from SQL/MX Release 2.3.x to SQL/MX Release 3.1 on page 4-1 Upgrading from SQL/MX Release 3.0 to SQL/MX Release 3.1 on page 4-5 Upgrading the database and using new features on existing and new databases on page 4-8 Implementing the new functionality on page 4-9 Planning for fallback Before you install SQL/MX Release 3.1, plan for a fallback to an earlier version.
Upgrading to SQL/MX Release 3.1 Upgrade sequence Figure 4-1. Sequence to upgrade from SQL/MX 2.3.x to SQL/MX 3.1 App1 Start cat1 sch1 R2.3.x V1200 Starting version Stop applications Stop TMF, Start, Stop TMF Install R3.1 and cold load App1 cat1 sch1 R3.1 V1200 Resulting version Start TMF Run mxtool fixrcb Recompile applications Take new TMF dumps HP NonStop SQL/MX Release 3.
Upgrading to SQL/MX Release 3.1 Preinstallation Preinstallation Complete the following prerequisites: 1. Stop all applications that access the database. 2. Stop the HP NonStop Transaction Monitoring Facility (TMF) twice with no database activity between the two stops: TMF 1> STOP TMF TMF 2> START TMF TMF 3> STOP TMF To avoid volume recovery when TMF is started after the system upgrade, you must perform these steps.
Upgrading to SQL/MX Release 3.1 Migrating the database after system upgrade An error might occur while running the mxtool fixrcb command due to one of the following reasons: An involved node has an incompatible version. A user other than the local super ID performed the operation. Note. The FIXRCB operation does not handle the objects in catalogs that have a manual reference on the local system.
Upgrading to SQL/MX Release 3.1 Upgrading from SQL/MX Release 3.0 to SQL/MX Release 3.1 SQL/MX Release 3.1 enables upgrading of applications from an SQL/MX Release 2.3.x system to a SQL/MX Release 3.1 system without requiring you to recreate and reload the database. You do not need to preprocess, compile the host language, and link when you migrate from SQL/MX Release 2.3.x to SQL/MX Release 3.1. However, SQL/MX Release 3.1 does not support user modules and query plans from SQL/MX 2.3.
Upgrading to SQL/MX Release 3.1 Upgrade sequence Upgrade sequence To upgrade from SQL/MX Release 3.0 to SQL/MX Release 3.1, you must follow the sequence shown in Figure 4-2. Note. The steps to upgrade from SQL/MX Release 3.0 to SQL/MX Release 3.1 are simpler than the corresponding steps to upgrade from SQL/MX R2.3.x. Figure 4-2. Sequence to upgrade from SQL/MX 3.0 to SQL/MX 3.1 App1 Start cat1 sch1 Starting version R3.0 V1200 OR V3000 Stop applications Stop TMF Install R3.
Upgrading to SQL/MX Release 3.1 Installing SQL/MX Release 3.1 2. Stop the HP NonStop Transaction Monitoring Facility (TMF). Note. When upgrading from SQL/MX Release 3.0 to SQL/MX Release 3.1, you do not have to stop TMF twice before the installation. Installing SQL/MX Release 3.1 For information on how to install SQL/MX Release 3.1, see Installing SQL/MX Release 3.1 on page 4-3. Accessing the database After the initial system load on the target release, the database is ready for use. Note.
Upgrading to SQL/MX Release 3.1 Upgrading the database and using new features on existing and new databases Execute the user modules and SQL queries compiled in SQL/MX Release 3.0 without any change. Use the RCBs generated on SQL/MX Release 3.0 without any change. Omit running the mxtool fixrcb. command. Note. An automatic recompilation of a SQL query with plan version 3000 will result in a query with plan version 3100.
Upgrading to SQL/MX Release 3.1 created databases and applications can coexist with the databases and applications from the earlier release. Note. Scenario 2 does not involve a metadata upgrade. Figure 4-4. Coexistence of new and old databases App2 App1 V1200 cat1 sch1 OR cat2 sch2 V3100 V3000 App3 Scenario 3 - New features offered by SQL/MX Release 3.1 are not required: If you do not want to use any of the new features offered by SQL/MX Release 3.
Upgrading to SQL/MX Release 3.1 Implementing the new functionality HP NonStop SQL/MX Release 3.
5 Falling Back from SQL/MX Release 3.1 This section describes falling back from SQL/MX Release 3.1 to SQL/MX Release 3.0 and to SQL/MX Release 2.x. Note. When using new features, if you encounter an issue that is specific to SQL/MX Release 3.1, discontinue the use of those features instead of falling back from that version.
Falling Back from SQL/MX Release 3.1 Fallback sequence To fall back from SQL/MX Release 3.1 to a supported SQL/MX 2.x version earlier than SQL/MX Release 2.3.4, you must first fall back to SQL/MX Release 2.3.4 and then to the required version, as shown in Figure 5-2. Figure 5-2. Falling back to a SQL/MX 2.x version earlier than SQL/MX 2.3.4 SQL/MX R3.1 SQL/MX R2.3.4 SQL/MX R2.
Falling Back from SQL/MX Release 3.1 Fallback sequence Figure 5-3. The v3000 or v1200 objects are not upgraded and new objects are not created on SQL/MX 3.1 App1 Start Stop applications cat1 sch1 R3.1 V1200 OR V3000 Starting version Stop TMF, Start, Stop TMF Install R3.0 or R2.3.4 and fallback SPRs R3.0 V3000 App1 cat1 sch1 Resulting version Run OR R2.3.4 V1200 mxtool fixrcb Recompile applications Install 2.x, if required App1 cat1 sch1 R2.x Final version HP NonStop SQL/MX Release 3.
Falling Back from SQL/MX Release 3.1 Fallback sequence If you have upgraded the metadata to v3100 and created objects using new features, you must fall back as shown in Figure 5-4. Figure 5-4. New database objects are created on SQL/MX Release 3.1 Start Stop applications R3.1 App1 App2 cat1 sch1 cat2 sch2 Copy and drop unsupported objects Run downgrade command V1200 OR V3000 V3100 Starting version Stop TMF, Start, Stop TMF Install R3.0 OR R2.3.4 and fallback SPRs R2.3.4 OR R3.
Falling Back from SQL/MX Release 3.1 Fallback considerations Figure 5-5. The v1200 or v3000 objects are upgraded to v3100 App1 Start Stop applications cat1 sch1 R3.1 V3100 Starting version Run downgrade command Stop TMF, Start, Stop TMF Install R3.0 OR R2.3.4 and fallback SPRs App1 cat1 sch1 Resulting version R3.0 V3000 OR R2.3.4 V1200 Run mxtool fixrcb Recompile applications Install 2.x, if required App1 cat1 sch1 R2.
Falling Back from SQL/MX Release 3.1 Preinstallation Applications that are compiled using the SQL/MX Release 3.1 compiler must be preprocessed, recompiled, and then linked with an earlier release of the SQL/MX compiler after the fallback. Note. Recompiling programs might result in different execution plans, causing a change in performance. The online dumps taken on SQL/MX Release 3.1 cannot be used by TMF recovery on SQL/MX Release 3.0 or on SQL/MX Release 2.x.
Falling Back from SQL/MX Release 3.1 Migrating the Database for a System Fallback Migrating the Database for a System Fallback Stopping TMF Migrating the Database for a System Fallback You might have to use the DOWNGRADE utility when you perform a system fallback from SQL/MX Release 3.1 to SQL/MX Release 3.0 and to SQL/MX Release 2.3.4.
Falling Back from SQL/MX Release 3.1 Installing SQL/MX Release 3.0 objects are not immediately compatible after a change from SQL/MX Release 3.1 to an earlier release. Note. Do not fall back from SQL/MX Release 3.1 immediately after a system crash. In case of a system crash, you must restart the system with the version that was running at the time of the crash, start TMF, and then shut down TMF twice before falling back. Installing SQL/MX Release 3.0 To fall back to SQL/MX Release 3.
Falling Back from SQL/MX Release 3.1 Installing SQL/MX Release 2.x This command regenerates RCBs for SQL/MX objects in all catalogs that were originally created on the system. If the system fallback is performed for a clustered or networked environment, you must fall back all affected systems simultaneously and must run the mxtool fixrcb command on each involved system.
Falling Back from SQL/MX Release 3.1 Changes required after falling back HP NonStop SQL/MX Release 3.
A Removing Security Administrator Grants In the following steps, queries create a command file containing SQL REVOKE statements targeting all grants that were performed by security administrators. You can then use the command file as input to mxci to remove the grants. To effectively use these queries, carefully read and follow the directions embedded within the comments as some variables must be modified prior to execution. These queries must be run against version 3100 metadata.
Removing Security Administrator Grants and tbl_privileges2.is_grantable = 'Y' ); insert into $$GRANTS_TABLE$$ select col_privileges.table_uid,col_privileges.grantor,col_privileges.grantee, col_privileges.privilege_type, col_privileges.column_number, ?CATALOG_NAME from definition_schema_version_3100.col_privileges as col_privileges where col_privileges.grantor != -2 and not exists ( select col_privileges2.table_uid,col_privileges2.grantor,col_privileges2.grantee, col_privileges2.
Removing Security Administrator Grants objects.object_uid = grants.table_uid and cols.object_uid = grants.table_uid and (grants.column_number = -1 OR cols.column_number = grants.column_number); -- End Repeat for every catalog on the system... -- Execute the following three statements only after repeating the above loop -- for every catalog in the system... log $$COMMANDS_FILE$$ clear; select * from $$COMMANDS_TABLE$$; log; --------- Exit mxci and logon as a security administrator.
Removing Security Administrator Grants HP NonStop SQL/MX Release 3.
B Identifying Tables That Contain an IDENTITY Column The following steps use queries to extract names of tables with an IDENTITY column. These queries must be run against version 3100 metadata. -- Execute all of the following from within mxci. -- Set pattern $$SYSTEM$$ to the name of the system on which the queries are -- executing.
Identifying Tables That Contain an IDENTITY Column HP NonStop SQL/MX Release 3.
C Identifying tables where the ownership has changed If the ownership of database objects is changed after upgrading to SQL/MX Release 3.1, you must revert the changes before fallback, because earlier releases do not support this feature. To revert the ownership, the schema owner must be an existing Guardian user. To revert the changes prior to fallback, complete the following steps for each user catalog on the system: 1.
Identifying tables where the ownership has changed object owners are as described in step 1, and the catalog name is 'CAT', complete the following steps: 1. Logon as SUPER.SUPER (whose Guardian ID is 65535), the schema owner for schema 'SCH'. 2. Run the following command for the view SCH.V1: GIVE VIEW CAT.SCH.V1 to "SUPER.SUPER"; --- SQL operation complete. 3. Logon as SQL.USER1 (whose Guardian ID is 44801), the schema owner for schema 'USER1'. 4. Run the following command for table USER1.
Index A Assistance 1-3 C CA release See Controlled availability (CA) release Controlled availability (CA) release 3-5 D Database object versioning 3-8 Default compiler version 3-8 Downgrade, definition of 1-1, 2-1 GCSC See Global Customer Support Center (GCSC) General availability (GA) release 3-5 Global Customer Support Center (GCSC) 1-3 I Incremental releases 3-3 Independent products fallback to SQL/MX Release 2.x 5-9 migrating to SQL/MX Release 2.
Index O O SDI Object feature version (OFV) description of 3-9 displaying 3-10 Object schema version (OSV) description of 3-9 displaying 3-9 OFV See Object feature version (OFV) OSV See Object schema version (OSV) P Plan version 3-8, 3-10 Planning, migration phases 1-1 Product version identifiers 3-5 Product version update (PVU) 3-5 PV See Initial product version (PV) PVU See Product version update (PVU) Q QL 1-1 Query plan versioning description of 3-10 See NonStop Solutions Development and Implement
Index V V Version definition of 1-1 identification 3-7 modules 3-10 query execution plan 3-10 schema 3-9 SQL/MX database object 3-9 SQL/MX software 3-8 Versioned persistent entities 3-7 Versioned software components 3-7 Versioning SQL/MX software components 3-7 VPROC information date 3-4 final build date 3-4 product version identifier 3-4 SPR identifier 3-4 SQL/MX release number 3-4 HP NonStop SQL/MX Release 3.
Index V HP NonStop SQL/MX Release 3.
