SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

Upgrading to SQL/MX Release 3.1

HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001

4-3

Preinstallation

Complete the following prerequisites:

1. Stop all applications that access the database.

2. Stop the HP NonStop Transaction Monitoring Facility (TMF) twice with no database

activity between the two stops:

TMF 1> STOP TMF

TMF 2> START TMF

TMF 3> STOP TMF

To avoid volume recovery when TMF is started after the system upgrade, you must

perform these steps. 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.1.

Installing SQL/MX Release 3.1

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

RVU for a SQL/MX Release 3. 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 then 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

enable regular access to database objects, you must execute an explicit RCB fixup by

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 local super ID must execute the

mxtool fixrcb command. 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.