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-8
Installing SQL/MX Release 3.0
objects are not immediately compatible after a change from SQL/MX Release 3.1 to an
earlier release.
Installing SQL/MX Release 3.0
To fall back to SQL/MX Release 3.0, complete the following steps:
1. Install SQL/MX Release 3.0. For information on installing SQL/MX Release 3.0,
see Installing NonStop SQL/MX in the
SQL/MX Installation and Management
Guide
.
2. Install the fallback SPRs referred to in the SQL/MX Release 3.1 softdoc.
3. Perform the required changes to your system after falling back. See Changes
required after falling back on page 5-9.
4. Perform the operations described in Accessing the database
on page 5-8.
5. Perform the operations described in Migrating applications after system fallback
on
page 5-9.
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 referred to in the SQL/MX Release 3.1 softdoc.
3. Perform the required changes to your system after falling back. See Changes
required after falling back on page 5-9.
4. Perform the operations described in Accessing the database
.
5. Perform the operations described in Migrating applications after system fallback
on
page 5-9.
Accessing the database
After the initial system load on the target fallback release, RCBs are still incompatible.
Shutting down TMF twice prior to the fallback simply prevents TMF volume recovery
from encountering those RCBs after the fallback. To enable regular access to database
objects, run the
mxtool fixrcb command before any other SQL activity.
Note. Do not fall back from SQL/MX Release 3.1 immediately after a system crash. In case of
a system crash, you must restart the system with the version that was running at the time of
the crash, start TMF, and then shut down TMF twice before falling back.










