SQL/MP Version Management Guide

Mixed Version Networks
Compaq NonStop™ SQL/MP Version Management Guide429833-001
6-7
Using Version 2 Catalogs in a Network
Using Version 2 Catalogs in a Network
These version restrictions apply to version 2 catalogs:
You cannot upgrade a version 2 catalog to version 300 or newer from a node
running version 2 SQL software. To upgrade a version 2 catalog in this situation,
you must execute the UPGRADE CATALOG or UPGRADE SYSTEM CATALOG
statement from a node running version 300 or newer SQL software.
You can upgrade a user catalog to version 300 or newer only if the catalog resides
on a node that has migrated to version 300 or newer SQL software.
You cannot downgrade a version 300 or newer catalog to version 2 from a node
running version 2 SQL software. Instead, you must execute a DOWNGRADE
CATALOG or DOWNGRADE SYSTEM CATALOG statement from a node
running version 300 or newer SQL software.
Version 2 SQL software does not recognize version 300 or newer catalogs. As a result,
you cannot enter DDL statements or utility commands from a node running version 2
software to create version 2 objects to be registered in a version 300 or newer catalog.
This restriction exists whether the catalog is on a local or remote node. You can,
however, create version 2 objects to be registered in a version 2 catalog, local or remote.
The objects and catalog must reside on the same node.
Using Version 2 Software and SQL Programs
These version restrictions apply to SQL programs operating under version 2 SQL
software:
You cannot register an SQL program in a version 300 or newer catalog on a node
running version 2 SQL software; version 2 SQL software does not recognize version
300 catalogs.
You can use a version 2 SQL executor to execute an SQL program whose program
format version is either 1 or 2, but not an SQL program whose program format
version is 300 or newer.
Using a Version 2 Message File
If you attempt to use version 2 SQLCI with a newer version message file, SQLCI
returns a message warning that the SQL message file has a version problem.
Version 1 and Newer Version Software
Version 1 SQL software can access version 1 objects and catalogs on nodes running
version 300 or newer SQL software. SQL programs running on nodes where version 1
SQL is installed can also access version 1 objects and catalogs on nodes running version
300 or newer software. However, if version 1 programs attempt to access objects or
catalogs that are version 2 or newer, the results are unpredictable.