home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT07599 Status: Closed

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

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem 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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Informix users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.xC6                      * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IBM Informix Server 12.10.xC6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.03.2015
30.12.2015
30.12.2015
Problem solved at the following versions (IBM BugInfos)
12.10.xC6
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC5.W1 FixList
12.10.xC6 FixList