SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-16
Downgrading Catalogs
from the newer-version tables to the older-version tables or use SQLCI for this
purpose. You must perform these tasks before installing the older-version software.
After preserving any necessary data, you can drop all newer-version objects. You can
also drop any programs that must be registered in a newer-version catalog; this
includes any program with a newer-version feature, which causes the program catalog
version to adopt the newer version.
Downgrading Catalogs
If you need to access objects in a newer-version user catalog, you must downgrade
the user catalog before installing the older version of SQL/MP software.
You must always downgrade a version 300 or newer system catalog when you revert
to an older version of the software, but you do not always need to downgrade version
300 user catalogs. For example, if you are temporarily reverting to version 2 from
version 310 and do not intend to access objects registered in user catalogs, you can
leave any version 310 user catalogs and objects on the node and downgrade only the
system catalog.
If, however, you need to access data from the version 310 user catalogs on the node
where you are reinstalling an older version of SQL/MP, you must downgrade these
catalogs. If you do not downgrade the catalogs on a node in which the SQL/MP
software reverts to an older version, a fallback situation results. In this situation, the
reinstalled SQL/MP software cannot access any catalogs whose versions are newer
than the version of the software or any objects or programs registered in the catalogs.
In addition, SQL/MP software on other nodes in a network can no longer access these
catalogs and objects, regardless of the versions of the software on the remote nodes.
Downgrading User Catalogs
Before downgrading a user catalog, you must:
•
Drop any protection views on the catalog tables to be downgraded.
•
Drop any object whose version would be newer than the version of the catalog
after the catalog is downgraded.
Caution. If any tables have the UNRECLAIMED FREESPACE (F) or INCOMPLETE SQLDDL
OPERATION (D) attribute set, remedy the situation before downgrading the version. Otherwise,
the table might be corrupt after the downgrade is completed. For more information, see
UNRECLAIMED FREESPACE (F) and INCOMPLETE SQLDDL OPERATION (D) Flags
on
page 7-24.
Note. You do not need to downgrade any version 2 user or system catalogs, because version
2 catalogs are compatible with version 1 SQL/MP software.
Caution. If you want to downgrade any catalogs, you must do so before you reinstall the older
version of the SQL/MP software, because only version 300 or newer software supports the
DOWNGRADE CATALOG and DOWNGRADE SYSTEM CATALOG commands.