G06.27 Software Installation and Upgrade Guide

Preparing to Fall Back
G06.27 Software Installation and Upgrade Guide—540067-001
13-5
SMF
SMF
The record format of the system configuration database sometimes changes between
RVUs and is automatically converted to the new format the first time the system is
loaded. To ensure system configuration integrity, always:
1. Save the system configuration after SMF configuration changes are made.
2. Reload the system from the current system configuration file or the latest version
with SMF changes.
See the Storage Management Foundation User’s Guide for more information.
SQL/MX 2.0 or 2.0.1
Metadata tables created and used by SQL/MX Release 2.0 running on or after G06.23
are different than those metadata tables used on prior SQL/MX releases, and the
tables are very different than those used by SQL/MP. You must be on at least Release
1.8 to migrate or to fall back. Migration and fallback considerations do apply. See TMF
(G06.23, G06.24, G06.25, and G06.26) on page 1-43 and DP2.
Before attempting to fall back, you should remove all SQL/MX objects and their
resource forks. See NonStop SQL/MX Release 2.1.1 (G06.27) on page 1-33.
TMF
Falling back to RVUs prior to G06.24, with format 2 audit trails, will cause serious audit
trail problems and requires a DELETE TMF, as well as other steps.
Fallback steps depend on whether you chose to alter the audit trail file size or format,
or both. If you do not alter the audit trail file size or format, there are no fallback issues
with TMF for G06.27. If the audit trail file size is altered, but still within the 2,047
megabyte limit, fallback is still not a major issue, but you must take steps before or
after fallback to prevent deterioration in some algorithms. See TMF (G06.23, G06.24,
G06.25, and G06.26) on page 1-43 and DP2.
Caution. Create a saved version of the configuration before loading a new RVU. If this step is
omitted, you cannot fall back to a previous RVU.