NonStop SQL/MP Reference Manual

Table Of Contents
NonStop SQL/MP Reference Manual142115
D-58
Examples—DOWNGRADE CATALOG
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.
Not allowed in user-defined transactions
You cannot use DOWNGRADE CATALOG in a user-defined transaction.
Failure situations
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
The following command downgrades the catalog on the subvolume $VOL1.SVOL1
to version 2:
>> DOWNGRADE CATALOG $VOL1.SVOL1 TO 2;
The following command downgrades all the catalogs on volume $VOL to version
310:
>> DOWNGRADE CATALOG $VOL.* TO 310;
The following command downgrades all the catalogs on the current default node to
version 2:
>> DOWNGRADE CATALOG $*.* TO 2;
The following command downgrades all catalogs on a volume on a remote node to
version 2:
>> DOWNGRADE CATALOG \DIST.$DATA.* TO A011;
DOWNGRADE SYSTEM CATALOG Command
DOWNGRADE SYSTEM CATALOG is an SQLCI utility command that allows a user
with super ID authority to convert a local system catalog to an older version so the
system catalog can be accessed by an older version of NonStop SQL/MP software.
version
is the catalog format version for the downgraded system catalog.
DOWNGRADE SYSTEM CATALOG TO version ;