SQL/MP Version Management Guide

Mixed Version Networks
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
6-5
Partitioned Objects in a Mixed Version Network
Partitioned Objects in a Mixed Version Network
All partitions of a given object have the same version number. Each partition must obey
the version-management rules for objects outlined in Section 3, Database Versions.
Specifically, the version of every partition of an object must have a version that is the
same as or older than the version of the catalog in which the partition is registered. The
version of the partition must also be the same as or older than the version of SQL/MP
software on the node where the partition resides. The versions of catalogs and the
versions of the software do not have to be the same.
To illustrate, suppose that a version 310 table is divided into three partitions and that
each partition resides on a different node in a network. Then suppose that two of the
nodes migrate to a newer version of the software.
When these operations are complete, the table’s partitions are registered in catalogs with
two different version numbers and reside on nodes running two different versions of the
software. This scenario results in a valid configuration for a partitioned table, as
illustrated in Figure 6-4
. However, you can perform most operations (such as ALTER
TABLE ADD COLUMN) only from a node running software of a version at least as
new as the newest catalog version.
Because partitioned objects can be registered in different versions of catalogs on nodes
running different versions of the software, you can upgrade your software on different
nodes at different times, while maintaining the ability to access existing partitioned
objects.
For more details on the version requirements for version 2 partitions, see Version 2 and
Newer Version Software.
DDL Operations in a Mixed Version Network
To avoid version errors when you are managing a database from one node in a mixed
version network, perform all Data Definition Language (DDL) operations for the
network on the node with the newest version of SQL/MP software.
If a DDL operation in a mixed version environment fails and returns a version error,
retry the DDL operation from the node in your network that is running the newest-
version SQL/MP software.
Figure 6-4. Partitioned Objects in a Network
Node Running
Version > 310 NonStop(TM) SQL
Node Running
Version > 310 NonStop(TM) SQL
Node Running
Version 310 NonStop(TM) SQL
VST014.vsd
V310 Table
Partition 1
Version 310 Catalog
Version 310 Catalog
V310 Table
Partition 2
V310 Table
Partition 3
Version > 310 Catalog