SQL/MX 3.1 Installation and Management Guide (H06.23+, J06.12+)

Performing Recovery Operations
HP NonStop SQL/MX Release 3.1 Installation and Management Guide—663852-001
12-32
Using FIXUP to Correct Problem Data and Objects

You must be logged on using the super ID, be owner of the schema where the
object being verified resides, or have SELECT privilege on the object being
verified.

VERIFY obtains read-only locks on metadata while verifying an object. Other
operations that read metadata can run concurrently. Operations that change
metadata or labels such as DDL, partition management, PURGEDATA, and
UPDATE STATISTICS statements cannot run concurrently.

To verify some objects, NonStop SQL/MX might need to access remote systems.
In this case, the remote systems must be available, and you must have privileges
to view information on them.

If VERIFY tries to access objects on a remote system that were created on a
schema version later than the current system version, you receive a versioning
error.
Using INFO to Display Guardian File Information
Use the mxtool INFO command to request specific SQL/MX information for a given
Guardian file name. NonStop SQL/MX automatically generates Guardian file names
that are randomly created. Use the INFO command to determine which Guardian file
names belong to which ANSI object, without writing complex queries against metadata.
With INFO you can obtain this information even if metadata is unavailable. In addition,
you can use the MXCI SHOWLABEL command to get more details for a specific
Guardian file. See the
SQL/MX Reference Manual for command syntax and example
outputs.
Guardian files have a set of DP2 labels attached to them that contain basic
information, such as file type, extent sizes, security, and timestamps. A separate entity,
a resource fork, is attached to an SQL/MX file. A resource fork contains additional
information about an SQL/MX file, including its associated ANSI name, ANSI
namespace, versioning information, record structure, key structure, partition maps, and
so on.
INFO displays:

The ANSI file name

The ANSI namespace, including the table namespace (which includes views and
stored procedures), index namespace, and trigger namespace

Versioning elements, including the object schema version
Using FIXUP to Correct Problem Data and Objects
NonStop SQL/MX stores information about object structures in metadata, resource
forks, and DP2 file labels. DP2 file 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 descriptions of all objects in a database.