IT07599: DR_PRPING THREAD MAY BECOME STUCK IN RUNNING STATE FOLLOWING HDR CONNECTION FAILURE

APAR status

• Closed as program error.

Error description

• The dr_ping thread may become stuck in a continuously running
  state following a connection failure with the HDR secondary
  server. The stack for this thread will be similar to the
  following:
  
  mt_spin_lock_wait()
  asf_checkexp()
  sqscb_cleanup()
  destroy_session()
  dr_primary_ping()
  startup()
  
  In addition the command onstat -g ath will show the dr_prsend
  thread waiting on the dr_prping thread, for example:
  
  ifx$ onstat -g ath | grep dr_
   202      7000000501f80d0  700000020423e68  1    join wait  1116
  10cpu      dr_prsend
   1116     700000050741028  700000020429cf0  1    running
  10cpu      dr_prping
  
  Once in this state the HDR connection cannot be re-established
  until the primary server is restarted.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Informix users                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to IBM Informix Server 12.10.xC6                      *
  ****************************************************************
  

Problem conclusion

• Problem Fixed In IBM Informix Server 12.10.xC6
  

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

• RA10 PSY

     UP