SQL/MX 3.x Installation and Management Guide (H06.22+, J06.11+)

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—640325-001
12-26
Strategies for Repairing Damaged Metadata and
Objects
•
Section 5, Planning Database Security and Recovery
•
Section 8, Querying SQL/MX Metadata
•
The SQL/MX Reference Manual
FIXUP
Use the mxtool FIXUP command to perform limited repair operations that enable you
to fix problems, such as inconsistencies between metadata and labels, by adjusting the
label or resource fork. FIXUP does not repair all problems with inconsistencies,
however. For example, if the ANSI name does not match metadata, you cannot use
FIXUP. Instead, you must restore the file that contains the problem.
For information about using FIXUP, see Using FIXUP to Correct Problem Data and
Objects on page 12-32.
GOAWAY
Use the mxtool GOAWAY command to remove SQL/MX format file labels for both the
resource and data forks associated with a Guardian file. Use GOAWAY to remove
objects that are broken or cannot be dropped by normal DDL operations. GOAWAY
does not remove corresponding metadata entries. However, when a GOAWAY
operation completes, you must manually change metadata tables to remove the
associated metadata. If you use MXCI to manually change the metadata tables, you
must use a licensed MXCI process.
Use GOAWAY only when no other method of dropping an object works. You must log
on as the super ID to run GOAWAY.
For information about using GOAWAY, see Using GOAWAY to Delete Damaged
Objects on page 12-37.
INFO
Use the mxtool INFO command to request specific SQL/MX information for a
Guardian file without writing complex queries against metadata. You can use INFO to
display information about SQL/MX files, including the Guardian file name, the
corresponding ANSI file name, the ANSI namespace, and the object schema version.
INFO also enables you to obtain this information if metadata is unavailable. Any user
can perform the INFO operation on files on a remote node if the remote system is
available. Note, however, that if you try to use INFO to access objects on a remote
system that were created on a schema with a version later than the current system
version, you receive a versioning error.
For information about using INFO, see Using INFO to Display Guardian File
Information on page 12-32.