SQL/MP Version Management Guide

Mixed Version Networks
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
6-9
SQL Utilities and Fallback Nodes
attempt to access objects or programs on a fallback node or attempt to register
version 300 or newer objects or programs in older version catalogs.
•
These SQL utilities can operate successfully on older version objects, programs, or
catalogs residing on nodes running version 300 or newer SQL software. In this
situation, version errors occur only if the SQL utilities attempt to operate on an
object, program, or catalog whose version is newer than 300.
SQL Utilities and Fallback Nodes
When SQL utilities interact with objects and programs on a node whose SQL software
has reverted to an older version, these operations cause version errors:
•
An SQL utility attempts to access an SQL object whose version is newer than the
version of the SQL software on the node where the object resides. For example, a
version error results if you use any SQL utility of any version to access a version
310 table that resides on a version 2 node, or to access a version 2 table registered in
a version 310 catalog on a version 2 node.
•
An SQL utility attempts to access an SQL program whose catalog version is newer
than the version of the SQL software on the node where the program resides. For
example, a version error occurs if you use any version of any SQL utility to access
an SQL program whose catalog version is 310 and that resides on a version 2 node.
SQL Utilities and Older Version Catalogs
When SQL utilities attempt to create new objects of version 300 or newer and to register
them in older version catalogs, a version error occurs. (This restriction violates the
relationship of object version to catalog version described in Section 3, Database
Versions.)
Because the DUP utility creates objects, it also tests the version of the catalog in which
the target object is to be registered. The version of the target object must be the same as
or older than the version of the catalog tested. A version error occurs, for example, if
you use the version 300 DUP utility to duplicate a version 300 collation and register it in
a version 2 catalog, even if the catalog is on a version 300 node.
Because CONVERT does not create or access SQL objects directly (it merely creates an
EDIT file containing SQLCI commands), CONVERT does not test the object version.
You should check the EDIT file created by CONVERT to make sure the definitions in
the file do not create tables or indexes with a version newer than the version of the
catalog in which the objects are to be registered.
For more information about the SQL utilities, see the NonStop SQL/MP Reference
Manual.
The RESTORE Utility and Older Version Catalogs
The RESTORE utility cannot restore an object or a program to a catalog with a version
older than the object or program being restored. The following situations cause version
errors: