SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-15
Reverting to an Older Software Version
no user or program can access any catalogs or objects on the node. For this reason,
you might want to upgrade catalogs individually.
This example upgrades three user catalogs, one catalog at a time:
>> UPGRADE CATALOG \SYS1.$VOL1.SALES TO 310;
--- SQL operation complete.
>> UPGRADE CATALOG \SYS1.$VOL1.INVENT TO 310;
--- SQL operation complete.
>> UPGRADE CATALOG \SYS1.$VOL1.PERSNL TO 310;
--- SQL operation complete.
You can continue using the existing system catalog and create versions of catalogs
that are newer than the current system catalog (but not newer than the SQL/MP
software version on the node on which the catalog resides). For example, you can
create a version 310 catalog to be registered in a version 1 or version 2 system catalog
residing on a version 310 SQL/MP node.
If you decide to register objects and programs in the system catalog, instead of in user
catalogs, you must upgrade the system catalog before registering objects or SQL
programs that have a newer version than the system catalog. To do this, use the
UPGRADE SYSTEM CATALOG command, identifying the system catalog as the one
to be upgraded.
For the syntax and other examples of UPGRADE CATALOG and UPGRADE SYSTEM
CATALOG, see the SQL/MP Reference Manual. For more information about catalog
versions, see the SQL/MP Version Management Guide.
Reverting to an Older Software Version
If you have upgraded the system catalog to a newer version and you want to revert to
an older version of SQL/MP, you must first drop all objects whose versions are newer
than the version of SQL/MP to be reinstalled. You must then downgrade the system
catalog and any user catalog with a version newer than the version of SQL/MP to
which you are reverting. After you reinstall the older version of SQL/MP software, you
must recompile newer-version programs.
Dropping Newer-Version Objects
To preserve data in tables that have a newer version than the software to which you
are reverting, you must create each of the tables again, omitting any features that
caused the table to have the newer version. For example, if tables use extended
partition arrays, re-create them with standard partition arrays. If the tables you want to
preserve are defined with new features, write a program to move the required data
Caution. Because of database administration overhead, you should not register user objects
in the system catalog. Also, the impact of upgrading a system catalog in a mixed-node
environment can make this system inaccessible to other nodes in the network.