SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

Correcting Problems Manually
You can correct some problems in metadata directly by manually executing inserts, updates, selects,
and deletes. Any SQL/MX user can read metadata, but only DDL and utility operations can update
it. Therefore, NonStop SQL/MX allows the super ID to fix incorrect metadata through standard
INSERT, UPDATE, and DELETE statements using a licensed MXCI process. However, use this method
only as a last resort to correct a problem.
Identifying Problem Data and Objects
NonStop SQL/MX keeps information about object structures in metadata, resource forks, and DP2
labels. DP2 labels consist of file structure information and security settings. Resource forks contain
specific SQL/MX information that includes, among other things, the ANSI name, partition maps,
row and key information, and system metadata location. Metadata contains a description of all
the objects in a database. During regular processing, information between metadata, DP2 labels,
and resource forks can become inconsistent. Use the VERIFY command to detect these problems
and report them to users. Use the INFO command with VERIFY to display various areas of the
database as described next, independent of whether a problem is detected.
VERIFY checks for:
• Inconsistencies between an SQL/MX table and its structural representation in the resource fork
• Inconsistencies between an SQL/MX table and its structural representation in corresponding
DP2 labels
• The existence of dependent partitionable objects and their correct definitions
INFO displays SQL/MX related information given a Guardian qualified file-set list
Types of Data Problems
Label Data
Table 17 (page 255) describes the information that is stored in the various labels associated with
SQL/MX format objects.
Table 17 Label Data Associated With SQL/MX Objects
ContentsLabel Field
This name matches the external file label name and is of the form ZSDXXXXXX.YYYYYY00.Data fork name
This name is similar to the data fork name, except it ends in “01” (for example,
ZSDXXXXXX.YYYYYY01)
Resource fork name
The file code that is used by NonStop SQL/MX. Unlike with SQL/MP, you cannot choose
your own file codes.
File code
Only key-sequenced (file type 3) files are supported in NonStop SQL/MX. Relative and
entry-sequenced files are not.
File type
Indicates whether the table is format 1 or format 2. The file format is always format 2 for
SQL/MX format objects.
File format
The owner of the file.Owner
FIle security setting, specified as *sql. NonStop SQL/MX supports ANSI GRANT and
REVOKE security and does not use Guardian security of the form RWEP. The Guardian
Protection
protection for all SQL/MX format objects is set to “AAAA.” Do not use this field to determine
the security attributes for the object.
The time and date when the file was created.Creation timestamp
The time and date when the file was last modified.Modification timestamp
The time and date when the file was last redefined.Redefinition timestamp
Repairing Damaged SQL/MX Metadata and Objects 255