SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-14
Upgrading Catalogs
For parallel index creation or parallel index load operations that access base table
partitions on nodes running older versions of SQL/MP, specify the LOCALONLY option
at the start of the CREATE INDEX configuration file to force RECGEN processes to run
on the local node. Alternatively, start the CREATE INDEX operation from the node
running the older version of software.
Upgrading Catalogs
You must upgrade or create at least one user catalog on a node running the new
version of SQL/MP software before you can do any of these:
•
Create an object with attributes that cause the object version to be newer than the
current version of the user catalog. For example, you cannot create an object that
refers to a version 320 feature and registers the object in a version 1 or version 2
catalog.
•
Alter an object by adding attributes that cause the object version to be newer than
the current version of the user catalog. For example, you cannot add a column with
a version 310 data type to a table registered in a version 1 or version 2 catalog.
•
Register programs with a program catalog version newer than the current version
of the user catalog. For example, you cannot register a program that contains a
version 320 feature in a version 1 or version 2 catalog.
To create a version 300 or newer catalog, use the CREATE CATALOG command.
To upgrade an existing user catalog to version 300 or newer, use the UPGRADE
CATALOG command. This command requires exclusive access to the catalogs being
upgraded and to the objects to be registered in the catalogs. Specifically, to use
UPGRADE CATALOG, you must be the local owner of the catalog, the local super ID,
the group manager, or the remote owner with authority to purge the catalog tables. You
must also have authority to write to the CATALOGS system catalog table.
SQL/MP automatically requests the TMF subsystem to protect the integrity of the
database during the upgrade operation. If a user-defined TMF transaction (a
transaction explicitly defined by using language statements such as BEGIN WORK and
COMMIT WORK) is not in progress when you enter the UPGRADE CATALOG
command, SQL/MP begins and ends a TMF transaction for each catalog being
upgraded.
For statements issued within a user-defined TMF transaction, SQLCI does not initiate a
system-defined TMF transaction. You should allow SQLCI to initiate TMF transactions
for DDL commands.
You can use a single UPGRADE SYSTEM CATALOG command to upgrade all the
catalogs on a node. However, doing so can take several minutes, and during this time,
Caution. If an SQL object has the UNRECLAIMED FREESPACE (F) or INCOMPLETE
SQLDDL OPERATION (D) attribute set, do not attempt to back up, move, or duplicate the
object until the attribute is reset. For more information, see UNRECLAIMED FREESPACE (F)
and INCOMPLETE SQLDDL OPERATION (D) Flags on page 7-24.