SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
U-12
Considerations—UPGRADE CATALOG
specify must be newer than the current version of the catalogs you specify with
catalogs. In addition, version must not specify a version newer than the
version of the SQL/MP software executing UPGRADE CATALOG or newer than
the version of the SQL/MP software running on the node of the catalog being
upgraded.
The default is the version of the SQL/MP software installed on the node on which
the catalogs reside, or the version of the SQL/MP software executing UPGRADE
CATALOG, whichever is older.
For more information about NonStop SQL/MP product versions, see Versions on
page V-6 or the SQL/MP Version Management Guide.
Considerations—UPGRADE CATALOG

To upgrade a catalog, you must be a generalized owner of the catalog. You must
also have authority to write to the CATALOGS table in the system catalog.
UPGRADE CATALOG requires exclusive access to the catalogs being upgraded.
Other processes cannot access the catalogs during the upgrade. The upgrade fails
if another process has one of the tables in the catalogs open when you execute
UPGRADE CATALOG. In addition, all indexes, views, and programs registered in
the catalogs must be available for read access.
For performance reasons, SQLCI sometimes keeps catalog files open for five
minutes after the SQLCI command or statement that uses them finishes. This
strategy can interfere with a subsequent UPGRADE CATALOG operation in the
SQLCI session. If such interference occurs, exit SQLCI and start a new SQLCI
session.

Unless UPGRADE CATALOG executes within a user-defined transaction, an error
that causes the upgrade of one catalog specified in catalogs to fail does not
necessarily cause the upgrades of other catalogs specified in catalogs to fail.
(Use GET VERSION if you want to check the version of a specific catalog.)

UPGRADE CATALOG invalidates any program that refers to a catalog table in the
upgraded catalogs, but does not invalidate a program merely because it is
registered in an upgraded catalog or because it accesses objects registered in an
upgraded catalog.
Examples—UPGRADE CATALOG

This example converts the current default catalog to the same version as the
current SQL/MP software:
>> UPGRADE CATALOG;

Either of these commands converts the catalog on subvolume $VOL.SVOL to
version 320:
>> UPGRADE CATALOG $VOL.SVOL TO 320;
>> UPGRADE CATALOG $VOL.SVOL TO A320;