G06.25 Software Installation and Upgrade Guide

Overview of Installing G06.25

G06.25 Software Installation and Upgrade Guide—529430-001

1-42

TMF (G06.23 and G06.24)

TMF Migration Considerations for SQL/MX Release 2.0

If you install 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 the Install SQL/MX Script has not been run on your system while running on the new

RVU, and no native-format SQL/MX metadata tables (or their resource forks) or audit

records for them have been created, 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.

HP strongly recommends that you successfully complete a clean TMF shutdown (with

all audited disks up) before falling back to a prior RVU. This 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 2GB 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,

then altering the audit-trail configuration to enable format 2 audit-trail files will require a

STOP TMF command at some later date.

TMF Fallback from G06.25

If you are migrating to G06.25 from G06.24, there are no migration issues. If you are

on a pre-G06.24 RVU and you do not plan to make changes to the TMF audit-trail

configuration, there are no issues related to fallback associated for TMF. However, if

you are on a pre-G06.24 RVU and you do plan to change the audit-trail configuration,

such as altering the file size of a given trail or changing the audit-trail configuration to

use format 2 files, you must understand the fallback issues.

After you execute either the ALTER AUDITTRAIL command with the new FILESIZE

option, or the ALTER TMF command with the new ATFORMAT option, the fallback to a

prior RVU involves a series of steps that must be followed precisely. Executing a