H06.08 Software Installation and Upgrade Guide

H06.08 Installation, Migration, and Fallback
Considerations
H06.08 Software Installation and Upgrade Guide—543573-001
2-3
NonStop SQL/MX
Partitioned unstructured files cannot be migrated to an ESS without first performing a
migration of all partitions of the unstructured file set to a mod-14 extent boundary.
Partitioned unstructured files must use the same extent size and maximum extents for
all partitions because positioning 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.2, which has no G-series equivalent, introduces this
functionality:
•
ANSI Names support in FUP for INFO, RELOAD, LISTLOCKS, and LISTOPENS
commands
•
ANSI Names support in DP2 EMS messages
•
FCHECK support for ANSI Names
•
FCHECK support for verifying the integrity of individual SQL/MX data rows
•
UPDATE STATISTICS - partitioned sample table for improved performance
•
SQL/MX plan size reduction in unique queries for SQLMXBUFFER
•
Dynamic SQL performance enhancement in JDBC/MX type 2 driver
NonStop SQL/MX Release 2.2 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.08. 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.2 is delivered with the H06.08 RVU SUT. If you have the
H06.08 RVU on your system, you can install SQL/MX Release 2.2. For installation
information, see the SQL/MX Installation and Management Guide.
Installing NonStop SQL/MX Release 2.2
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.