SQL/MP Installation and Management Guide

Format 2 Partitions
HP NonStop SQL/MP Installation and Management Guide—523353-004
C-12
Interoperability Considerations
°
Fallback versions of TMFARLIB contain fallback support. If you choose to
use this approach, you should rebind before falling back.
Interoperability Considerations
Programs and utilities running on system software product versions earlier than that of
G06.13 will not be able to access or manipulate Format 2-enabled tables or their
associated indexes or views on G06.13 RVU or later systems. This limitation applies
both to SQL commands executed against these version 350 SQL objects from systems
that do not support them, in addition to utility commands that attempt to access version
350 objects because they contain wild cards.
Catalog tables themselves are Version 1 SQL objects and are accessible from systems
running earlier software product versions. The FILES catalog table has a different
schema in a Version 350 catalog than in prior versions. Therefore, queries run against
a Version 350 catalog from a system running earlier software product versions will
execute, but could encounter unexpected results because of the additional columns
and possible values in that table.
If you have any TACL scripts or OBEY command files for these utilities that run on
system software of an earlier RVU and access or manipulate files on a system running
an RVU that supports SQL Format 2-enabled tables, consider migrating the system
running the older RVU to G06.13 (or later.) Alternately, you should ensure that their
operation will not be impaired by introducing SQL Format 2-enabled tables on a
G06.13 (or later) system on disks viewed by the scripts:
•
SQLCI
•
TACL
•
FUP
•
Backup/Restore
In general, the interoperability behavior of these utilities involves:
•
Commands that return only the names of files (such as FILES and FILENAMES)
return the names of the partitions of Format 2-enabled tables and their associated
indexes and views (version 350 objects) without error.
•
Other commands return an error (several are possible, depending upon the
product and command) for each version 350 object (file) indicating that the
software is unable to support access to objects of that version. The name of the file
is included in the text describing the error. Processing then continues with the next
file in the list or wild-card expansion for that command, or, if that command is
finished, with the next command in the OBEY command file or script.
Note. TMFARLIB fallback support involves ignoring, and not returning to the
caller, audit records generated for DML changes to Format 2 partitions (changes
made to data records or blocks). Audit records for DDL changes to Format 2
partitions (changes made to labels) are still returned. Your audit-reading programs
might need modifications to tolerate this incomplete representation of the changes
made to Format 2 partitions.