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

Falling Back from SQL/MX Release 3.1
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
5-7
Migrating the Database for a System Fallback

Migrating the Database for a System Fallback

Stopping TMF
Migrating the Database for a System Fallback
You might have to use the DOWNGRADE utility when you perform a system fallback
from SQL/MX Release 3.1 to SQL/MX Release 3.0 and to SQL/MX Release 2.3.4.
Consider the following scenarios for system fallback:

Executing the DOWNGRADE command is not necessary in the following
scenarios:

The fallback version is SQL/MX Release 3.0 and the database contains v3000
and v1200 schemas only.

The fallback version is SQL/MX Release 2.3.x and the database contains
v1200 schemas only.

If you are using new database features for some objects in v3100 schemas, you
must perform the following steps:

Use the FEATURE_VERSION_INFO function to obtain the name and object
type of database objects that use new features. Such objects prevent a
downgrade operation. For more information, see SQL/MX Functions and
Expressions in the
SQL/MX Reference Manual.

Convert the old unsupported objects to the corresponding copy objects without
new features.

Drop the old unsupported objects before executing the DOWNGRADE
command.

Downgrade to the required version. For information on how to use the
downgrade utility, see SQL/MX Utilities in the
SQL/MX Release 3.1 Reference
Manual.
Stopping TMF
Before a system fallback, stop TMF twice with no database activity between the two
stops:
TMF 1> STOP TMF
<stop tmf output>
TMF 2> START TMF
<start tmf output>
TMF 3> STOP TMF
<stop tmf output>
These steps are necessary to avoid volume recovery when TMF is started after the
system fallback. TMF recovery of SQL/MX database objects will access the RCBs of
the affected objects. You must shut down TMF because the RCBs of the affected