G06.32 Software Installation and Upgrade Guide

G06.32 Installation and Fallback Alerts
G06.32 Software Installation and Upgrade Guide—546068-002
2-28
TMF
If you use the new feature that allows you to add one or more auxiliary audit trails while
TMF is started, it is possible to fall back only to G06.24 or a later RVU. This is because
the TMF audit reading facilities prior to G06.24 cannot handle auxiliary pointer
(AUXPTR) records that specify a variable number of audit trails.
If you issue an ADD AUDITTRAIL AUXnn command while TMF 3.3 is started, the next
AUXPTR record generated contains information for a different number of audit trails
than did the preceding AUXPTR record.
For G06.26 and later TMF 3.3 fallback and migration issues, see the
Interactive Upgrade Guide 2 and the TMF Planning and Configuration Guide .
TMF Migration Considerations for NonStop SQL/MX
Release 2.0
If you initially install NonStop SQL/MX Release 2.0, fallback and migration concerns
could apply if you have to fall back to a previous RVU. See the T8607AFH or later
softdoc for detailed migration information for TMF. See also the TMF Planning and
Configuration Guide and the TMF Operations and Recovery Guide .
If you have not run the Install SQL/MX script on your system while running the new
RVU, and you have not created any native-format SQL/MX metadata tables (or their
resource forks) or audit records for them, there are no TMF fallback considerations.
Otherwise, you must use the appropriate DP2 (T9053) fallback SPR if you have not
performed a clean TMF shutdown.
You must successfully complete a clean TMF shutdown (with all audited disks up)
before falling back to a prior RVU. This step is particularly important whenever the RVU
you are falling back from supports any new format files or objects or audit records for
them, and the fallback RVU does not.
To establish complete TMF file recovery protection for your SQL/MX metadata tables,
update your TMF online dump (and Backup) scripts to include the names of all
SQL/MX metadata tables, including those that are SQL objects and their resource
forks. The TMFCOM DUMP FILES and RECOVER FILES commands support all the
new SQL/MX metadata tables (using their Guardian names).
TMF Migration Considerations for Format 2 Audit Trails
TMF provides the capability to create much larger audit-trail files with the introduction
of the G06.24 RVU, but TMF must be stopped in a clean state to execute the
TMFCOM command that enables this ability. If audit-trail files greater than 2 GB are
part of the long-term audit-trail configuration strategy, consider altering the audit-trail
format at migration time, given that TMF is already stopped. If not done at this time,
altering the audit-trail configuration to enable format 2 audit-trail files will require a
STOP TMF command at some later date.