SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

Installing SQL/MX Release 3.2
1. Install the Site Update Tape (SUT) for the required RVU. Determine the required RVU for a
SQL/MX Release 3. See Table 4 (page 60). To install an RVU, see the H06.25 or J06.14
Software Installation and Upgrade Guide.
2. Install any necessary Independent Software Products, such as the NonStop Server for Java,
the JDBC/MX Driver for SQL/MX, and RDF.
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.
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.
NOTE: The FIXRCB operation does not handle the objects in catalogs that have a manual reference
on the local system. RCB fixup for objects in such catalogs must be performed on the system where
the automatic reference is located.
The FIXRCB operation is available on systems running J06.12 or later J-series RVUs, or H06.23 or
later H-series RVUs, and on fallback SPR (H06.21-ANC).
To ensure database recoverability after a system upgrade to SQL/MX Release 3.2, you must take
a full set of online dumps after executing the mxtool fixrcb command successfully.
NOTE: TMF file recovery on SQL/MX Release 3.2 using online dumps from SQL/MX Release
2.3.x has some restrictions. HP recommends that you take new TMF online dumps when the SQL
database is ready (after running mxtool fixrcb).
Converting the CPU list format from SQL/MX Release 2.3.x to SQL/MX Release 3.2
The format of the CPU lists stored in the ODBC/MX metadata in the SQL/MX Release 2.3.x is
different from the format of the CPU lists stored in SQL/MX Release 3.2. The SQL/MX Release
2.3.x CPU list format is not recognized in SQL/MX Release 3.2. Starting with SQL/MX Release
3.2, mxtool includes the fixmxcsmd option. The fixmxcsmd option supports the conversion
of the SQL/MX Release 2.3.x CPU list format to the SQL/MX Release 3.2 CPU list format in the
ENVIRONMENTVALUES MXCS metadata table. To convert the SQL/MX Release 2.3.x CPU list
format to the SQL/MX Release 3.2 CPU list format, you must run the mxtool command with the
fixmxcsmd option.
To convert the SQL/MX Release 2.3.x CPU list format to the SQL/MX Release 3.2 CPU list format,
you must run the mxtool command with the fixmxcsmd option after cold loading with SQL/MX
Release 3.2 objects.
The fixmxcsmd option also supports the conversion of the SQL/MX Release 3.2 CPU list format
to the SQL/MX Release 2.3.x CPU list format in the ENVIRONMENTVALUES MXCS metadata table.
Upgrading the system from SQL/MX Release 2.3.x to SQL/MX Release 3.2 39