SQL/MX 2.x Reference Manual (G06.24+, H06.03+)

SQL/MX Utilities

HP NonStop SQL/MX Reference Manual—523725-004

5-14

Considerations for FIXUP Operation

If you change the redefinition timestamp of the label, all executor opens are

invalidated. The next time the executor tries to open the file, a similarity check is

performed. If it fails, programs are recompiled. The redefinition timestamp is

updated whenever the corrupt attribute, broken attribute, or audit attribute is

changed.

If the table has remote partitions, you must run FIXUP on each remote node. To

perform FIXUP operations on remote partitions, go to the remote node and run

FIXUP there.

Examples of FIXUP Operation

You must be the super ID to run FIXUP.

Suppose that you create a table, FIXUPtable, located in catalog mycat and schema

mysch. It has three partitions, two of which are located on the local node \local and

one located on a remote node \remote. It contains a trigger which requires a trigger

temporary table. That table exists on the local node. There are two indexes associated

with the table, index1 and index2. Each index has three partitions, organized like

the table.

•

Suppose a partition on FIXUPtable is broken. To fix the problem, you need to

turn off the audit attribute, fix the problem, reset the broken attribute, and turn audit

back on.

Partition \LOCAL2.$DATA02.ZSD1123U.SUEIFO00 is marked broken. Run FIXUP

to turn off the audit attribute:

mxtool FIXUP LABEL \LOCAL2.$DATA02.ZSD1123U.SUEIFO00 -a=off

Determine the problem and fix it. Then run FIXUP to reset the broken attribute and

to turn the audit attribute back on:

mxtool FIXUP LABEL \LOCAL2.$DATA02.ZSD1123U.SUEIFO00 -rb

mxtool FIXUP LABEL \LOCAL2.$DATA02.ZSD1123U.SUEIFO00 -a=on

Suppose that several of the timestamps on FIXUPtable do not match the value

on the label. Run FIXUP to reset the timestamps:

mxtool FIXUP TABLE mycat.mysch.FIXUPtable -rt -d