SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
D-60
Examples—DOWNGRADE CATALOG
the SQL/MP software that executes it is replaced with an older version. However, if
the purpose of the DOWNGRADE CATALOG is to prepare for installation of an
older version of SQL/MP software, you will need to re-SQL-compile programs with
a newer PFV after the older software is in place. (A runtime error occurs if you
attempt to execute a program with a PFV newer than the version of the installed
SQL/MP software.)

DOWNGRADE CATALOG creates a new temporary catalog on the same volume
as each catalog being downgraded. Such volumes must have enough disk space
available to store files twice as large as the original catalog.

You cannot use DOWNGRADE CATALOG in a user-defined transaction.

An error that causes the downgrade of one catalog specified in catalogs to fail
does not necessarily cause the downgrades of other catalogs specified in
catalogs to fail. (Use GET VERSION to check the version of a specific catalog.)
In unusual failure situations (such as a system failure during a downgrade catalog
operation), temporary files with names that begin with the letters “ZZDN” might be
left on the same subvolume as the catalog. You can delete these with CLEANUP.
Examples—DOWNGRADE CATALOG

This example downgrades the catalog on the subvolume $VOL1.SVOL1 to version
2:
>> DOWNGRADE CATALOG $VOL1.SVOL1 TO 2;

This example downgrades all the catalogs on volume $VOL to version 310:
>> DOWNGRADE CATALOG $VOL.* TO 310;

This example downgrades all the catalogs on the current default node to version 2:
>> DOWNGRADE CATALOG $*.* TO 2;

This example downgrades all catalogs on a volume on a remote node to version 2:
>> DOWNGRADE CATALOG \DIST.$DATA.* TO A011;