Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide528593-005
1-39
TNOS Server and TNOS Utility (G06.17 through
G06.24)
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 G06.24, 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.24
If no changes to the TMF audit-trail configuration are planned, then there are no issues
related to fallback associated for TMF with G06.24. You should be able to migrate to
G06.24 from a prior RVU and then fall back to that same RVU without issues related to
TMF. However, if any changes to the audit-trail configuration are planned, such as
altering the file size of a given trail or changing the audit-trail configuration to use
format 2 files, then it becomes very important to 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, then the
fallback to a prior RVU involves a series of steps that must be followed precisely.
Executing a DELETE TMF command may also be one of the required steps if you alter
the audit-trail format and then find it necessary to fallback.
Refer to the HP NonStop TMF Supplement for Large Audit-Trail Files for details related
to falling back after using these new TMF command options in G06.24.
TNOS Server and TNOS Utility (G06.17 through G06.24)
The TNOS Server (T8666) and the TNOS Utility (T8667), two components of HP
NonStop ODBC/MP, have been updated in G06.17 and later to correct data alignment
problems. To avoid data alignment problems, users of the TNOS Server and TNOS
Utility who are migrating to an RVU before G06.17 must also upgrade their TNOS
Server and TNOS Utility to these new versions:
T8666ACL or later (for TNOS Server)
T8667ACL or later (for TNOS Utility)
The marketing ID for the new versions is SJ08V1, and the Independent Product (IP)
name is NonStop ODBC Server and Client.