SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-11
Migrating to a Newer Software Version
•
Test the features available with the newer version of the software. Create test
catalogs and objects for testing purposes, rather than altering existing objects. For
example, collations require a version 300 or newer catalog to register the collation.
Before adding a collation, create a test catalog to associate with the collation.
Similarly, do not add a column with a new data type to an existing production table,
because the table will not be accessible if you need to revert to an older software
version.
If you need to revert to the older RVU, you can do it easily at this point because the
versions of production catalogs and objects are unchanged, and there are no
incompatible TMF audit records. (Guidelines for reverting are discussed under
Reverting to an Older Software Version on page 2-15.)
•
When you migrate to an RVU that supports SQL Format 2-enabled tables and the
SQL Format 2 partitions they contain, the only consideration that might affect you
is which RVU you migrate from. For more information on planning for Format 2
partitions, operational and fallback considerations, and interoperability, see
Appendix C, Format 2 Partitions.
Do not perform any of these actions until you are reasonably sure you do not want to
return to the older version of SQL/MP software:
•
Create a production catalog whose version is newer than your previous version of
the SQL/MP software. A newer version catalog is created automatically when you
create a catalog on a node running the new version of the software.
•
Create a production table using features that cause the version of the table to be
newer than your previous version of SQL/MP software.
•
Compile a program using the newer version of the SQL/MP compiler. If you do
recompile a program and decide to return to an older version of the software, you
must recompile the program with the older version of the SQL compiler after
reverting back to the older version. If you decide to compile programs with the
newer version of the software, keep track of which programs you compile.
When you are reasonably sure you do not want to revert to the older version of the
software, perform these steps as needed, based on your use of new features available
in the newer version of the software:
1. Upgrade catalogs. After you finish testing the newer version of the SQL/MP
software, upgrade the user catalogs on your node as needed to use version 300 or
newer features.
Note. You do not need to upgrade user catalogs until you are ready to register objects or
programs with newer-version features. You can also continue to use your older-version
system catalog indefinitely unless you register newer-version user objects or programs in
the system catalog, because newer-version user catalogs can be registered in a older-
version system catalog. For example, you can register version 300 catalogs in a version 1
or version 2 system catalog. You cannot, however, register version 300 or newer objects in
a version 1 or version 2 system catalog.