MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Upgrading to SQL/MX Release 3.0

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002

4-2

Installing SQL/MX 3.0

TMF 3> STOP TMF

These steps are necessary to avoid volume recovery when TMF is started after the

system upgrade. TMF recovery of SQL/MX database objects will access the RCBs of

the affected objects. TMF shutdown must be done because the RCBs of the affected

objects are not immediately compatible after an upgrade to SQL/MX Release 3.0.

Installing SQL/MX 3.0

1. Install the Site Update Tape (SUT) for the required RVU. To determine the required

RVU for a SQL/MX Release 3.0, see Table 3-1

on page 3-2. To install an RVU, see

the

H06.nn or J06.nn Software Installation and Upgrade Guide.

2. Install any necessary Independent Software Products, such as the NonStop Server

for Java, the JDBC/MX Driver for NonStop SQL/MX, and RDF.

3. Install, configure, and start TMF, which must be running on the system node where

you install NonStop SQL/MX. For more information, see the TMF Planning and

Configuration Guide.

Accessing the Database

After the initial system load on the target release, RCBs are still incompatible. To allow

regular access to database objects, an explicit RCB fixup must be executed using the

following command:

mxtool fixrcb

FIXRCB is an OSS command-line utility run from mxtool. It performs a RCB fixup for

all the required database objects in catalogs that have an automatic reference on the

local system. The

mxtool fixrcb command must be executed by the local super ID.

This command regenerates RCBs for SQL/MX objects in all catalogs that were

originally created on the system.

If the system upgrade is performed for a clustered or networked environment, you must

upgrade all affected systems simultaneously and run the

mxtool fixrcb command

on each involved system.

An error might occur while running the mxtool fixrcb command due to one of the

following reasons:



An involved node has an incompatible version.



A user other than the local super ID performed the operation.