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

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—544536-007
12-11
Recovering Tables
MXGNAMES utility. This utility can also be used to build lists of these Guardian
files for use with TMFCOM commands.
•
For the recovered objects, use the mxtool VERIFY command to verify that the
redefinition timestamps, catalog UIDs, schema UIDs, and object UIDs in the file
labels or resource forks match those in the SQL/MX metadata.
•
For every mismatch that mxtool VERIFY identifies, use mxtool FIXUP to update
the file labels and resource forks to make the object consistent.
•
If any views were dropped because of the CASCADE option, be sure to re-create
them.
•
Update the statistics for the recovered table.
•
SQL compile any SQL/MX modules that access this table.
Example: Recovering Table Privileges
Suppose you create an SQL/MX table using the following DDL, and then the table is
dropped accidentally:
CREATE TABLE CAT.SCH.T039UC3
(
A INT NO DEFAULT -- NOT NULL NOT DROPPABLE
, CONSTRAINT CAT.SCH.T039UC3_100345126_0022 CHECK
(CAT.SCH.T039UC3.A IS NOT NULL) NOT DROPPABLE
)
LOCATION \NSK.$DATA4.ZSDADHFW.AL0P3N00
;
-- The following index is a system created index --
CREATE UNIQUE INDEX T039UC3_103704950_0023 ON CAT.SCH.T039UC3
(
A ASC
)
LOCATION \NSK.$DATA4.ZSDADHFW.BGSB3N00
;
ALTER TABLE CAT.SCH.T039UC3
ADD CONSTRAINT CAT.SCH.T039UC3_103704950_0023 UNIQUE (A)
DROPPABLE;