SQL/MP Version Management Guide

Overview of Version Management
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
1-7
Reinstalling an Older Version
enhancements available to the newer-version SQL compiler, you must SQL-compile
your programs.
When you migrate to a newer version of SQL/MP, you can continue to use existing
older-version user catalogs and the objects registered in older-version catalogs. You do
not need to upgrade user catalogs until you are ready to register in the catalogs any
objects or programs with newer-version features. You can continue to use your older-
version system catalog indefinitely, unless you register newer-version user objects or
programs in the system catalog.
For detailed instructions on how to install a new version of SQL/MP software, see the
NonStop SQL/MP Installation and Management Guide. For information on upgrading
catalogs, see SQL/MP Catalog Versions
on page 3-1. For information on program and
compiler versions, see Section 5, Program Versions.
Reinstalling an Older Version
After you have installed a newer version of SQL/MP software, occasionally you might
need to reinstall an older version. For example, you might need to reinstall an older
version of SQL/MP to run or update older software.
Before you revert to an older version of SQL/MP software, you must downgrade your
user and system catalogs among other preparatory tasks.
If you do not first downgrade your catalogs, you will not be able to access:
•
Objects or programs registered in your user catalogs, even if the versions of the
objects and programs are the same as or older than the version of the reinstalled
software
•
Catalogs registered in the system catalog, even if the versions of the catalogs are the
same as or older than the version of the reinstalled software
For detailed instructions on how to reinstall an older version of SQL/MP software, see
the NonStop SQL/MP Installation and Management Guide. For information on
downgrading catalogs, see Section 3, Database Versions
.
Version Considerations in a Network
Version management in a network is simplest if all nodes support the same version of
SQL/MP software. In fact, the need for version management only occurs when different
versions of the software are installed on different nodes of the network.
If nodes on your network are running different versions of SQL/MP software and
different versions of SQL catalogs, objects, and programs, these restrictions apply:
•
You cannot access objects or execute programs registered in a remote catalog whose
version is newer than the SQL/MP software on the node where the catalog resides.
This restriction is true even if the objects or programs are the same version as the
SQL/MP software. For example, from a node running version 310, you cannot issue
a command to access a version 310 object registered in a version 310 catalog on a
node running version 2.