SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—523723-004
12-25
Strategies for Repairing Damaged Metadata and
Objects
For information about using FIXUP, see Using FIXUP to Correct Problem Data and
Objects on page 12-31.
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-35.
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-30.
VERIFY
Use the mxtool VERIFY utility to check consistency within the database between
metadata, resource forks, and file labels. For information about using VERIFY, see
Using VERIFY to Check Data Consistency on page 12-29.
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.