Replication detail info
This section defines the replication detail values.
The following values can be returned when the REPLICATION_DETAIL column in
QSYS2.MIRROR_INFO contains the value SUSPENDED:
REPLICATION_DETAIL_INFO | REPLICATION_DETAIL_TEXT |
---|---|
200 | Suspended due to warm clone in progress on this node |
202 | Suspended due to suspend for maintenance made on this node |
204 | Suspended due to save and restore clone in progress on this node |
![]() 205
206 207 ![]() |
![]() ![]() |
210 | Suspend pending restart of limited connections between nodes |
212 | Suspended due to user initiated suspend request |
214 | Suspended due to reclone replicated objects required |
216 | Suspended due to reclone replicated objects in progress |
218 | Suspended due to auto resume disabled for *SYSBAS |
220 | Suspended due to NRG down on this node |
222 | Suspended due to restricted state on this node |
224 | Suspended due to end TCP/IP on this node |
226 | Suspended due to node powered down |
228 | Suspended due to end of the QMRDBECTLR job on this node |
230 | Suspended while waiting for started NRGs to become active on this node |
232 | Suspended while waiting for connections between QMRDBECTLR jobs on both nodes |
234 | Suspended while waiting for environment checks to complete on this node |
240 | Primary replication role forced while suspended |
242 | Suspended due to suspend for maintenance made on the other node |
244 | Suspended due to reclone replicated objects in progress on the other node |
262 | Suspended due to restricted state on the other node |
264 | Suspended due to end TCP/IP on the other node |
266 | Suspended due to the other node powered down |
268 | Suspended due to end of the QMRDBECTLR job on the other node |
282 | Suspended due to auto resume disabled for the IASP |
284 | Suspended due to *SYSBAS replication is suspended on this node |
286 | Suspended due to the IASP is unavailable on one of the nodes |
288 | Suspended due to resume IASP replication verification pending between the nodes |
290 | TRACKING state forced while suspended |
8100 | Permanently suspended due to main store loss on this node |
8102 | Permanently suspended due to invalid engine data on this node |
8104 | Permanently suspended due to invalid RCL data on this node |
8106 | Permanently suspended due to invalid clone data |
8110 | Permanently suspended due to invalid replication role between both nodes |
8112 | Permanently suspended due to invalid lock source setting between both nodes |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
8140 | Suspended due to permanent suspend on the other node |
8200 | Suspended due to synchronization failure for *SYSBAS |
8202 | Suspended due to synchronization failure on the other node |
8210 | Suspended due to an existing synchronization job for *SYSBAS |
8212 | Suspended due to shared engine data synchronization failure for *SYSBAS |
8214 | Suspended due to synchronization job failure for *SYSBAS |
8216 | Suspended due to RCL synchronization failure for *SYSBAS |
8218 | Suspended due to synchronization failure for the QSECOFR password |
8220 | Suspended due to OTL synchronization preparation failure |
8222 | Suspended due to MVL synchronization failure for *SYSBAS |
![]() ![]() |
![]() ![]() |
8240 | Suspended due to synchronization failure getting OTL status |
8242 | Suspended due to synchronization cannot proceed with potential OTL conflicts |
8244 | Suspended due to OTL phase 1 synchronization failure for *SYSBAS |
8246 | Suspended due to OTL phase 1 synchronization not completed for *SYSBAS |
8248 | Suspended due to OTL synchronization failure for *SYSBAS |
8250 | Suspended due to OTL synchronization failure for *SYSBAS due to a change in the RCL |
8260 | Suspended due to relcone replicated objects failure for *SYSBAS |
8262 | Suspended due to relcone replicated objects failure for *SYSBAS on the other node |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
8300 | Permanently suspended due to main store loss for the database IASP |
8302 | Permanently suspended due to invalid engine data on the database IASP |
8304 | Permanently suspended due to invalid RCL data on the database IASP |
8306 | Permanently suspended due to invalid clone data for the database IASP |
8310 | Permanently suspended due to failure detected during vary on of the database IASP |
8312 | Permanently suspended due to invalid replication state for the database IASP |
8314 | Permanently suspended due to invalid configuration state for the database IASP |
8400 | Suspended due to synchronization failure for the database IASP |
8402 | Suspended due to synchronization failure for the database IASP on the other node |
8410 | Suspended due to an existing synchronization job for the database IASP |
8412 | Suspended due to synchronization job failure for the database IASP |
8414 | Suspended due to RCL synchronization failure for the database IASP |
![]() ![]() |
![]() ![]() |
8440 | Suspended due to synchronization failure getting OTL status for the database IASP |
8442 | Suspended due to synchronization cannot proceed with potential OTL conflicts for the database IASP |
8444 | Suspended due to OTL phase 1 synchronization failure for the database IASP |
8446 | Suspended due to OTL phase 1 synchronization not completed for the database IASP |
8448 | Suspended due to OTL synchronization failure for the database IASP |
8450 | Suspended due to OTL synchronization failure for the database IASP due to a change in the RCL |
8460 | Suspended due to reclone replicated objects failure for the database IASP |
8462 | Suspended due to reclone replicated objects failure for the database IASP on the other node |
8480 | Suspended due to an error preventing IASP resume |
8484 | Suspended due to an object replication failure for the database IASP |
8486 | Suspended due to an object restore failure for the database IASP |
8488 | Suspended due to user restore cancellation for the database IASP |
8600 | Suspended due to one or more NRGs failed to start |
8602 | Suspended due to QMRDBECTLR job connection failure |
8604 | Suspended due to QMRDBECTLR job detected communication loss – the other node may be down |
8606 | Suspended due to QMRDBECTLR job communication failure |
8608 | Suspended due to loss of access to storage |
8610 | Suspended due to loss of access to storage on the other node |
8612 | Suspended due to detected communication loss - the other node may be down |
8620 | Suspended due to QMRDBORM job failure |
8640 | Suspended due to a severe database IASP error |
8642 | Suspended due to a database IASP synchronization error |
8644 | Suspended due to a database IASP error |
8660 | Suspended due to jobs existing which have not completed processing for a prior suspend |
8680 | Suspended due to an object restore failure for *SYSBAS |
8682 | Suspended due to user restore cancellation for *SYSBAS |
8684 | Suspended due to an object replication failure for *SYSBAS |
8686 | Suspended due to QDBMLSTN job is not active |
8688 | Suspended due to QMRDBORM job is not active |
8690 | Suspended due to storage threshold reached |
8692 | Suspended due to storage threshold reached on the other node |
8700 | Suspended due to Boss Option 48 not installed |
8702 | Suspended due to Boss Option 48 does not have a valid license key |
8704 | Suspended due to IBM® Db2® Mirror for i not installed |
8706 | Suspended due to IBM Db2 Mirror for i does not have a valid license key |
8708 | Suspended due to an NTP client or SNTP client is not running on this node |
8710 | Suspended due to an excessive time difference between the nodes |
8712 | Suspended due to an NTP client or SNTP client is not running on either node |
8714 | Suspended for maintenance due to a failure upgrading internal data on this node |
8716 | Suspended for maintenance due to a QMRDBECTLR job failure on this node |
8800 | Suspended due to an error on the other node |
The following values can be returned when the REPLICATION_DETAIL column in
QSYS2.MIRROR_INFO contains the value SYNCHRONIZING:
REPLICATION_DETAIL_INFO | REPLICATION_DETAIL_TEXT |
---|---|
310 | Synchronization phase 1 processing in progress |
320 | Synchronization phase 2 processing in progress |
The following values can be returned when the REPLICATION_DETAIL column in
QSYS2.MIRROR_INFO contains the value STARTING or
RESUMING:
REPLICATION_DETAIL_INFO | REPLICATION_DETAIL_TEXT |
---|---|
400 | Waiting for NRGs to be configured and ready to use on this node |
402 | Waiting for configuration initialization to complete on this node |
410 | Waiting for TCP/IP to become available on this node |
412 | Waiting for started NRGs to be up on this node |
414 | Waiting for connections between QMRDBECTLR jobs on both nodes |
416 | Waiting for validation message from the QMRDBECTLR on the other node |
420 | Waiting for Quorum operation to get status to complete on this node |
422 | Waiting for Quorum operation to clear entry to complete on this node |
430 | Waiting for secondary ready message from the QMRDBECTLR job on the other node |
432 | Waiting for synchronization to start |
![]() ![]() |
![]() ![]() |