Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Re-creating a clone pair

&pagelevel(4)&pagelevel

When separate processing has been completed, the clone pair can be re-created. In this case the clone session takes the current status of the original unit as a basis and is restarted. Re-creation can be started for all clone pairs of a pubset or for individual clone pairs.

When a clone pair is re-created, all the changes on the clone units are discarded and the clone session is continued. The modified data is copied from the original units onto the clone units.

Requirements

  • For QuickOPC the clone unit is in the SPLIT status after /START-CLONE-SESSION.

  • For EC the clone unit is in the SPLIT status after /ACTIVATE-CLONE.

  • Processing has been terminated on all clone units.

  • The pubset has been exported if all clone pairs are to be re-created for a pubset.

Initiating a restart

Discard the modifications on the clone units and restart the clone session:

/RESTART-CLONE-SESSION
   UNIT=*BY-PUBSET(PUBSET=<cat-id>) / *BY-VOLUME(<vsn>) / <unit MN> /... 

Further sequence of operations

Console message NDE0060 indicates that the restart process has been completed. 

The restart process has been completed for QuickOPC when the SYNCHRONIZING status has been achieved. The clone units are accessible immediately.

The restart process has been completed for EC when the SYNCHRONIZED status has been achieved. The statuses of other clone units remain unchanged.

The clone units are not accessible. They can be activated using /ACTIVATE-CLONE.