IBM Support

QSYS2.TERMINATE_MIRROR()

News


Abstract

The TERMINATE_MIRROR procedure ends all replication between the primary and secondary nodes and resets the replication state of both nodes to NOT MIRRORED. A clone operation is required to restart replication.

This procedure is used to permanently stop replication by deleting all Db2 Mirror configuration information. It can also be used to temporarily stop replication with the intent of cloning SYSBAS and all database IASPs from one node to the other. In-flight changes to replicated objects might not be successfully replicated to the other node. However, any active operations on the local node are completed. All tracked changes in the Object Tracking List are cleared, so those tracked changes are not made to the objects on the other node. After this procedure is run, both nodes are available for stand-alone operation, and either node can become the source for cloning a new Db2 Mirror pair.

Content

Db2 Mirror

For complete detail, view the IBM Documentation page: TERMINATE_MIRROR procedure
 

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSLLPF","label":"IBM Db2 Mirror for i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"},{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"}]

Document Information

Modified date:
14 December 2022

UID

ibm16829951

Page Feedback