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-36
Using GOAWAY to Delete Damaged Objects
Partition
(add first key (1000) location \local.$data02 name
i1part2,
Add first key (4000) location \remove.$data02 name
i1part3);
3. Create three partitions with these names:
•
\LOCAL.$DATA02.ZSDJFKEO.SJDIFL00
•
\LOCAL.$DATA04.ZSDJFKEO.SJDIFM00
•
\REMOTE.$DATA04.ZSDFHKEO.SJDIFN00
CREATE INDEX index2 (col3) on table1
Location \local $data02 name i2part1
Hash partition (add location \local.$data04 name i2part2,
Add location \remote.$data04 name i2part3);
4. Create a work file with the name \LOCAL.$DATA02.ZSDLSKFE.IEOFKS00:
CREATE TRIGGER...
Example 1: Repairing a Broken Partition
Partition \LOCAL.$DATA02.ZSD1123U.SUEIFO00 is marked broken. To fix the
problem, turn off the audit bit, use TANDUMP to fix the problem, reset the broken bit,
and turn the audit bit back on:
mxtool FIXUP LABEL \LOCAL.$DATA02.ZSD1123U.SUEIFO00 -a=off
Determine the problem and use TANDUMP to fix it.
mxtool FIXUP LABEL \LOCAL.$DATA02.ZSD1123U.SUEIFO00 -rb
mxtool FIXUP LABEL \LOCAL.$DATA02.ZSD1123U.SUEIFO00 -a=on
Example 2: Correcting Mismatched Timestamps
Several of the timestamps on table1 do not match the value on the label. To fix the
problem, change the redefinition timestamps:
mxtool FIXUP TABLE cat.sch.table1 -rt -d
NonStop SQL/MX MXTOOL Utility 2.0
(c) Copyright 2003 Hewlett-Packard Development Company, LP. All Rights
Reserved.
Operation successfully completed
Using GOAWAY to Delete Damaged Objects
SQL/MX files consist of two physical Guardian files: data fork and resource fork.
Normally, when the data fork is dropped, DP2 automatically drops the corresponding
resource fork. In some cases, either an orphaned resource fork or data fork can exist.