G06.27 Software Installation and Upgrade Guide

Overview of Installing G06.27
G06.27 Software Installation and Upgrade Guide—540067-001
1-28
C++ (G06.20)
To back up and restore SQL/MX tables and OSS files, see the Backup and Restore 2.0
Manual.
C++ (G06.20)
The G06.20 RVU includes a fully ANSI 98-compliant C++ run-time library, designated
as the C++ v3 run-time library (v3 RTL). Starting in G06.20, you have a choice of three
different C++ language dialects: v1, v2, and v3. The default compiler dialect setting is
changed from v1 to v3. The build file for any product that invokes a TNS/R native C++
must be examined and changed according to certain rules that are documented in the
Interactive Upgrade Guide.
DSM/SCM (G06.18 through G06.27)
Since the introduction of G06.18, if you had to fall back from an RVU that did not have
installed the D46 DSM/SCM PVU, you had to run the DSM/SCM FALLBACK macro
from the ZDSMSCM subvolume. If a D46 PVU existed, you did not have to run the
FALLBACK macro. However, for the G06.27 RVU, you must run the FALLBACK macro
if you have not installed the T6031D46^ABK SPR introduced in G06.25. The
interactive macro must be run by the DSM/SCM owner or by super ID (255,255). The
FALLBACK macro reverts the DSM/SCM Host or Target, or both, database back to a
pre-T6031G02 state.
If you perform a backout to your previous pre-T6031D46^ABK SPR after having
installed T6031G02, the FALLBACK macro only removes the Safeguard alias and
Guardian user security profile information. DSM/SCM still retains OSS management
information. New users must be reconfigured in DSM/SCM. See the DSM/SCM Users’
Guide for more information and DSM/SCM and the G06.27 RVU on page 1-7.
DP2 (G06.16, G06.23, G06.24, G06.27)
If you set the AUDITTRAILBUFFER or the SQLMXBUFFER attribute to 128 or more,
you need to reset these values to 0 before falling back to G06.16 or an earlier RVU. If
you fail to do so, TMF might not start, or a disk volume might go offline. You can
recover from this situation by using the SCF ALTER command. See the Interactive
Upgrade Guide for details.
If you are planning to use SQL/MX Release 2.0 or later, HP recommends that you
apply one of these DP2 fallback SPRs on your current SYSnn before upgrading to
G06.27:
•
T9053APO, if the system uses the online disk remirror feature
•
T9053APG, if the node does not use the online disk remirror feature
After installing the fallback SPR, test it sufficiently for production use. Then, migrate to
G06.27. If you are using SQL/MX Release 2.0, and you have to fall back to a previous
RVU, and you have created SQL/MX objects or audit records, you must have this
fallback SPR installed on your current SYSnn.