H06.12 Software Installation and Upgrade Guide

is dependent upon a consistent size for each of the partitions. Online migration attempts will
abort when an unstructured partitioned file without mod-14 extent sizes is present on the source
disk.
Before migrating to an ESS, rebuild all partitions, using a mod-14 extent size. Perform an offline
copy to a new partition set.
The FCHECK utility (introduced in G06.24) includes a migration option that reports the files that
cannot be migrated to ESS because of this format limitation, in addition to reporting the amount
of disk space required for check block protection.
NonStop SQL/MX
NonStop SQL/MX Release 2.3, which has no G-series equivalent, introduces this functionality:
• Provides an online variant of the POPULATE INDEX and MODIFY utilities
• Generates modules files in Guardian directories
• Projects only the requested number of rows from the table instead of scanning the complete
table
• Introduces a new Control Query Default statement (CQD)
NonStop SQL/MX Release 2.3 is interoperable with compatible releases of NonStop SQL/MX.
Interoperability between G-series and H-series RVUs is supported by NonStop SQL/MX on
H06.03 through H06.12. For more information about the interoperability of NonStop SQL/MX
releases, see the SQL/MX Database and Application Migration Guide.
NonStop SQL/MX Release 2.3 is delivered with the H06.12 RVU SUT. If you have the H06.04 or
later RVU on your system, you can install SQL/MX Release 2.3. For installation information, see
the SQL/MX Installation and Management Guide.
Installing NonStop SQL/MX Release 2.3
Check that the HP NonStop Transaction Management Facility (TMF) is configured and running
on the system node where you will install NonStop SQL/MX. See the TMF Planning and
Configuration Guide for TMF installation guidelines.
NOTE: All NonStop SQL/MX objects must reside on volumes audited by TMF. NonStop SQL/MX
program files do not need to reside on audited volumes.
Before installing NonStop SQL/MX, review the instructions for preinstalling and installing
NonStop SQL/MX provided in the SQL/MX Installation and Management Guide.
OSM Uses Different User ID and Password to Monitor Maintenance Switch
and UPS
Beginning in the H06.09 RVU, OSM uses the Simple Network Management Protocol (SNMP) to
monitor the Maintenance Switch and UPS (located under the Monitored Service LAN devices
branch of the OSM Tree). The user ID and password are no longer used to start monitoring these
devices. Instead, the SNMP read Access Community password is required for monitoring the
Maintenance Switch, and both the SNMP Read Access Community and SNMP Write Access
Community passwords are required to start monitoring the UPS. These passwords are established
the administrator during initial configuration of the device. The default password for SNMP
Read Access Community is “public”; The default password for SNMP Write Access Community
is “private.”
The Identification Information attribute of the UPS is no longer displayed.
NonStop SQL/MX 43