SQL/MX 3.1 Reference Manual (H06.23+, J06.12+)

SQL/MX Utilities

HP NonStop SQL/MX Release 3.1 Reference Manual—663850-001

5-92

Considerations for MODIFY

TMF online dumps of that location (data fork and RFork). File recovery cannot cross a

rename operation.

TMF backout and volume recovery are both fully supported after the rename

operations are performed.

MODIFY and RDF

Rename

RDF does not replicate the file label changes occurred due to Guardian rename

operations on the SQL/MX objects. You must perform corresponding rename

operations on the backup system to synchronize primary and backup systems. You

must ensure that consistency is maintained between the primary and backup

environments when Guardian rename operation is performed.

MODIFY and Redefinition Timestamp

The Guardian rename operation changes the redefinition timestamp of the object but it

is the same physical object with a different Guardian name. Therefore, after Guardian

rename operation is performed, the similarity check will pass. The following example

illustrates this occurrence:

>>prepare q from select * from t1;

--- SQL command prepared.

>>modify table t1

+>rename location <existing location> to <new file name

part>;

--- SQL operation complete.

>>execute q;

*** WARNING[8578] Similarity check passed.

In the example, although execute q uses the original name to access the renamed

table t1, the similarity check passes because table t1 remains the same physical table.

The Guardian rename of a base table changes the redefinition timestamp of the table

but not indexes. However, the Guardian rename of an index changes the redefinition

timestamp of the index, but not the base table and other indexes on that table.

Note. To retain recoverability, HP recommends making new TMF online dumps, immediately

after a Guardian rename operation is performed..

Note. You must stop the RDF updaters to perform Guardian rename on the backup system.

After the rename operation is complete, restart the RDF updaters.