IT00587: PRIMARY SERVER CAN BLOCK WAITING ON NEXT LOG FILE TO BE FREED IFTHE SECONDARY HAS FAILED DURING LOG CATCHUP PHASE

APAR status

• Closed as program error.

Error description

• The DR ping time out check does not take place while the
  secondary node is in catch up mode, this is when the secondary
  is recovering the logical logs from the primary. If the
  secondary fails during this phase and does not recover, the
  primary will continue oblivious to the problem, and eventually
  cycle through the logical logs up to the log currently being
  copied to the secondary. At this point it is unable to proceed
  into the next logical log and becomes hung, with the message
  "Waiting for Next Logical Log File to be Freed" appearing in the
  online.log.
  
  
  # Example online.log from the secondary
  
    16:11:35  DR: Failure recovery from disk in progress ...
    16:11:35  Logical Recovery Started.
    16:11:35  10 recovery worker threads will be started.
    16:11:35  Warning: Invalid (non-existent/blobspace/disabled)
  dbspace listed
                       in DBSPACETEMP: 'tempdbs'
    16:11:35  Start Logical Recovery - Start Log 9, End Log ?
    16:11:35  Starting Log Position - 9 0x70b5a8
    16:11:36  Started processing open transactions on secondary
  during startup
    16:11:36  Finished processing open transactions on secondary
  during startup.
    16:11:36  Logical Log 9 Complete, timestamp: 0x498bc.
  
    - at this point, if a failure or hardware problem occurs, the
  primary is unaware of this and continues regardless.
  
  # Example online.log from the primary
  
    16:11:35  DR: Sending log 9, size 2500 pages, 100.00 percent
  used
    16:11:36  DR: Sending log 10, size 2500 pages, 100.00 percent
  used
    16:11:36  Logical Log 13 Complete, timestamp: 0x65b11.
    16:11:39  DR: Sending log 11, size 2500 pages, 100.00 percent
  used
    ...
  
    16:58:58  Checkpoint Completed:  duration was 1 seconds.
    16:58:58  Tue Mar 18 - loguniq 24, logpos 0x9bd018, timestamp:
  0x79e9e Interval: 116
  
  
  16:58:58  Maximum server connections 3
  16:58:58  Checkpoint Statistics - Avg. Txn Block Time 0.000, #
  Txns blocked 1, Plog used 38, Llog used 6
  
  16:59:02  Waiting for Next Logical Log File to be Freed
  16:59:02  Checkpoint Completed:  duration was 1 seconds.
  16:59:02  Tue Mar 18 - loguniq 24, logpos 0x9c1018, timestamp:
  0x79eeb Interval: 117
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of High Availability Replication environment           *
  * consisting of a primary and a HDR secondary.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to IDS-11.70.xC9                                      *
  ****************************************************************
  

Problem conclusion

• Problem Fixed In IDS-11.70.xC9
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INFORMIX SERVER

• Fixed component ID

  5725A3900

Applicable component levels

• RB70 PSY

     UP