SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

HP NonStop SQL/MX Database and Application Migration Guide—540435-005

3-1

Upgrading to a Newer Version of

SQL/MX Release 2.x

This section assumes that you are upgrading from SQL/MX Release 2.0, or later, to a

new release of SQL/MX Release 2.x. To upgrade from SQL/MX Release 1.8 to

Release 2.x, see Part II, Migrating From SQL/MX Release 1.8 to SQL/MX Release 2.x

This section addresses these topics:

•

Planning for Fallback on page 3-1

•

Steps for Upgrading SQL/MX Release 2.x on page 3-1

•

Implementing New Functionality on page 3-2

Planning for Fallback

Before you install a newer version of SQL/MX Release 2.x, plan for a potential fallback

to a previous version of SQL/MX Release 2.x. That way, if necessary, you can fall back

more easily.

If you encounter a serious problem with a newer version of SQL/MX Release 2.x and

decide you need to fall back to a previous version of SQL/MX Release 2.x, see

Section 4, Falling Back to an Earlier Version of SQL/MX Release 2.x

It might be necessary to install fallback SPRs on the SQL/MX Release 2.x system

before migrating to a later RVU and a newer SQL/MX Release 2.x. Fallback SPRs

ensure that you can return your system to its original state if something goes wrong

during or after the upgrade. For information about installing fallback SPRs, see the

H06.nn or G06.nn Release Version Update Compendium and the Readme file for the

RVU to which you would fall back.

Steps for Upgrading SQL/MX Release 2.x

1. Install the site update tape (SUT) for the required RVU. To determine the required

RVU for a particular release of SQL/MX Release 2.x, see Table 2-1

on page 2-2 or

Table 2-2

on page 2-3. To install an RVU, see the G06.nn or H06.nn Software

Installation and Upgrade Guide.

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

for Java, the JDBC Driver for SQL/MX (JDBC/MX), or RDF.

Note. If you encounter the problem when using new features that are specific to SQL/MX

Release 2.x, consider discontinuing the use of those features instead of falling back from that

database environment.