MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Falling Back to SQL/MX Release 2.x

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002

5-6

Stopping TMF

After a system fallback, stop TMF twice with no database activity between the two

stops:

TMF 1> STOP TMF

TMF 2> START TMF

TMF 3> STOP TMF

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

objects are not immediately compatible after a change from SQL/MX Release 3.0 to an

earlier release.

Installing SQL/MX Release 2.3.4

To fall back to SQL/MX Release 2.3.4, complete the following steps:

1. Install SQL/MX Release 2.3.4. For information on installing SQL/MX Release 2.3.4,

see Installing NonStop SQL/MX in the

SQL/MX Installation and Management

Guide.

2. Install the fallback SPRs mentioned in the SQL/MX Release 3.0 softdoc.

3. Perform the required changes to your system after falling back. See Changes

Required After Falling Back on page 5-7.

4. If you have compiled embedded SQL/MX applications and modules in the SQL/MX

Release 3.0 environment, you must recompile them after you fall back to SQL/MX

Release 2.3.4.

5. Perform the operations described in Accessing the Database

Accessing the Database

After the initial system load on the target release, RCBs are still incompatible. TMF

shutdown simply prevents TMF volume recovery from encountering those RCBs. To

allow regular access to database objects, run the

mxtool fixrcb command before

any other SQL activity:

mxtool fixrcb

Note. You must not fall back from SQL/MX Release 3.0 immediately after a system crash

under any circumstances. If the system crashes, you must restart the system with the version

that was running at the time of the crash, start TMF, and shut down TMF twice before falling

back.