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-3

Migrating the Database After System Upgrade

To verify the database recoverability after a system upgrade to SQL/MX Release 3.0,

you must take a full set of online dumps after executing the

mxtool fixrcb

command successfully.

Migrating the Database After System Upgrade

After upgrading the system to SQL/MX Release 3.0, you do not need to perform

additional database migration activities apart from executing the

mxtool fixrcb

command. However, v1200 schemas cannot accommodate new database features

introduced in SQL/MX Release 3.0, such as large rows and extended numeric data

types.

To use the SQL/MX Release 3.0 database features:



Create new catalogs and schemas. By default, the new catalogs and schemas are

v3000.



Upgrade the metadata for all schemas in all catalogs that are visible on the local

system, including schemas in the system catalog. To upgrade, run the following

command:

>> upgrade all metadata;

For more information on the UPGRADE command, see MXCI Commands in the

SQL/MX Reference Manual.

Migrating Applications after System Upgrade

Embedded SQL-based programs, ODBC and JDBC-based programs that use Module

File Caching (MFC) can create modules. The embedded modules that were generated

on SQL/MX Release 2.3.4 or earlier are no longer compatible. Therefore, all such

modules must be compiled after the system is upgraded to SQL/MX Release 3.0 and

before the applications are started.

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.11 or later J-series RVUs, or

H06.22 or later H-series RVUs, and on fallback SPR (H06.21-ANC).

Note. Recovery on SQL/MX Release 3.0 using pre SQL/MX Release 3.0 TMF dumps has

some restrictions because of the changes made by

fixrcb. HP recommends that you take

new TMF online dumps when the SQL database is ready, that is after running

mxtool

fixrcb