SQL/MP Installation and Management Guide

Format 2 Partitions
HP NonStop SQL/MP Installation and Management Guide—523353-004
C-10
Fallback Scenario 3
•
You can fall back only to a supported fallback RVU (G06.03 through G06.12) to
which all the appropriate fallback SPRs have been applied.
•
After falling back, note that:
°
You cannot open, alter, or rename, or issue SQL statements or SQL utility
commands against any Format 2-enabled tables (both Format 1 and Format 2
partitions) remaining on the system. The only operations allowed against these
tables are GOAWAY and FILEINFO. All other operations are disallowed, and
appropriate errors are returned.
°
You can purge partitions of Format 2-enabled tables individually by using the
GOAWAY utility, but you cannot downgrade SQL catalogs from version 350.
°
You cannot access any SQL objects registered in any version 350 SQL
catalogs remaining on the system. This includes all Format 1 enabled tables
registered in them, in addition to Format 2-enabled tables.
°
Because of this restriction, you might want to initially register all new Format
2-enabled tables in a separate version 350 SQL catalog. When a previously
existing SQL table is altered to Format 2-enabled, however, you cannot move
its registration to the new catalog without re-creating the table.
°
TMF backout and volume recovery will not be able to restore consistency to
Format 2-enabled tables on disk (both Format 1 and Format 2 partitions)
during TMF startup. Furthermore, TMF is not able to restore their consistency
after a subsequent migration back to an RVU that supports Format 2-enabled
tables except by using file recovery to a specific position in the audit before the
fallback.
°
The TMFCOM DUMP FILES command will not dump any partitions of Format
2-enabled tables (both Format 1 and Format 2 partitions) or their associated
index partitions and views. If you explicitly include any of them by name in the
file-set list for this command, TMFDR logs an EMS message, drops them from
the set of files being dumped, and continues with the next file. Wild-card file
sets in this command also exclude each of the previously mentioned items and
Note. If you are not running a supported fallback RVU and you want to ensure that you
can fall back to the RVU from which you migrated (in the scenario where one or more
Format 2-enabled tables remain on your system), you must follow a two-step migration
plan:
1. Upgrade or migrate to a supported fallback RVU (with all appropriate fallback SPRs
applied) and run that RVU long enough to verify that your important applications still
function correctly.
2. Migrate to the RVU that supports SQL Format 2-enabled tables.
Note. Because of this TMF limitation, HP strongly recommends against falling back if
you cannot achieve a clean TMF shutdown (with all disks up), or if you cannot at least
close all important Format 2-enabled tables and ensure that all changes pertaining to
them have been flushed to those files on disk.