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

Preparing to Migrate From SQL/MX Release 1.8 to

SQL/MX Release 2.x

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

5-3

Installing Fallback SPRs

To ensure a successful fallback, you must install these fallback SPRs (or superseding

SPRs) on the SQL/MX Release 1.8 system before migrating to G06.23 (or a later RVU)

and SQL/MX Release 2.x:

These fallback SPRs ensure that you can return your system to its original state if

something goes wrong during or after the migration. These fallback SPRs are

necessary for the SQL/MP GOAWAY utility to be able to remove SQL/MX files after

fallback to SQL/MX Release 1.8. For information about installing fallback SPRs, see

the

G06.nn Release Version Update Compendium and the Readme file for the RVU to

which you would fall back.

Planning New Feature Implementation

It is important that you fully understand the new features provided in SQL/MX Release

2.x and make effective use of those features. You must also understand how to use the

new features successfully with earlier persistent entities. For example, earlier

applications and query plans should continue to work in the new environment, within

the limits of interoperability. For more information, see Versions of SQL/MX Software

Components on page 2-9.

To ensure effective use of the features of SQL/MX Release 2.x, follow this two-phase

strategy for installing SQL/MX Release 2.x on system nodes:

1. Install SQL/MX Release 2.x on the relevant production nodes. For installation

procedures, see the

SQL/MX Installation and Management Guide.

2. After you successfully install SQL/MX Release 2.x on

all relevant nodes and it is

known to work satisfactorily, begin using the new features of SQL/MX Release 2.x

on those nodes.

One of the major features of SQL/MX Release 2.x is the ability to create SQL/MX

tables and use new features supported by those tables. To learn about the new

functionality and enhancements in a particular version of SQL/MX Release 2.x, see

the SQL/MX Master Softdoc (T0560) for that particular release.

This strategy effectively separates the installation phase from the feature development

and utilization phase. If fallback becomes necessary, it is most likely to occur during or

shortly after the installation phase, before you start using new features.

If you modify or create new SQL/MP aliases, defaults, or stored procedures in Java

(SPJs) in the SQL/MX Release 2.x environment, there are no automated tools for

moving the associated SQL/MX metadata back to SQL/MP metadata tables.

Fallback SPR Description

T9053APO DP2 SPR if the system uses the online disk remirror features

T9053APG DP2 SPR if the system does not use the online disk remirror feature

T9195ADD SQL/MP GOAWAY SPR available in G06.28 and later RVUs

T9196ADU SQL/MX GOAWAY SPR available in G06.28 and later RVUs