SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide523353-004
2-18
Reverting to an Older Version of TMF
3. Make a list of all programs whose program format version or program catalog
version is 300 or newer. You can generate a list by entering a SELECT statement
like the following for each catalog on the node:
>> SELECT PROGRAMNAME, PROGRAMFORMATVERSION,
+> PROGRAMCATALOGVERSION
+> FROM $CATVOL.SYS.PROGRAMS <--PROGRAMS table in system catalog
+> WHERE PROGRAMCATALOGVERSION >= 300
+> OR PROGRAMFORMATVERSION >= 300 ;
--- SQL operation complete.
To inquire about the version of a specific program, use the GET VERSION OF
PROGRAM statement.
4. Use the DROP PROGRAM statement (or the corresponding OSS utility for OSS
programs) to drop all programs whose program catalog version is 300 or newer.
5. Use the DOWNGRADE CATALOG command to downgrade all version 300 or
newer user catalogs to version 2:
>> DOWNGRADE CATALOG catalog-name TO 2 ;
--- SQL operation complete.
6. If the system catalog is version 300 or newer, use the DOWNGRADE SYSTEM
CATALOG command to downgrade the system catalog to version 2:
>> DOWNGRADE SYSTEM CATALOG TO 2 ;
--- SQL operation complete.
7. Reinstall version 2 of the SQL/MP software as described under Reinstalling
SQL/MP Software on page 2-10.
8. If any programs you want to use were host-compiled by a version 300 or newer
host compiler, use a version 2 host compiler to recompile the source code for these
programs.
9. If any programs you want to use have a program format version of 300 or newer
(as determined in Step 3), use a version 2 SQL compiler to recompile these
programs.
Reverting to an Older Version of TMF
When moving from version 300 or newer SQL/MP software back to an older version of
software, you must also revert back to the older version of TMF software. For more
information, see the TMF Planning and Configuration Guide.