home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC10 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 IT44152 Status: Closed

A THREAD CAN CONTINUALLY LOOP IN FIND_CACHE_ENTRY, WHILE OTHER THREADS
STATUS SHOWS MUTEX WAIT DH_ID HASH

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
If we run UPDATE STATS while running many SELECT statements on a
table, itâ ™s possible for the
distribution cache to become corrupt causing either a thread to
continually
loop in find_cache_entry or to assert. Continually running
thread neither yields the CPU VP
nor yields the latch causing the other threads running SELECT
show status as "mutex wait DH_ID hash"


Examples of stacks taken from looping threads:
0x0000000100032aa4  strcmp() + 0x24
0x00000001003ffc90  distnmcmpr() + 0x30
0x00000001003c8994  find_cache_entry() + 0x334
0x00000001003c8ae8  find_cache() + 0x68
0x00000001003c9d00  retrieve_cache() + 0xe00
0x00000001003cd268  cbgetdist() + 0x128
0x00000001003ccff4  opgetdist() + 0x54
0x000000010038e54c  IPRA.$get_distrib() + 0x4c
0x000000010038d7c8  IPRA.$selec() + 0x248
0x0000000100379a90  IPRA.$opselec() + 0x930
0x00000001003ab0d4  mc_toplevel() + 0x374
0x0000000100385760  fl_costselec() + 0x180
0x0000000100381168  makefll() + 0x408
0x0000000100380e60  makefll() + 0x100
0x000000010037e134  opinit() + 0x5b4
0x00000001003785d0  op_opinit() + 0x90
0x0000000100375000  sqoptim() + 0x19a0
0x00000001008caed8  bldstructs() + 0x2b8
0x00000001008c61c4  IPRA.$sqcmd() + 0x244
0x00000001008c9b7c  sq_cmnd() + 0x1bc
0x00000001008ca2d0  sq_prepare() + 0x30
0x0000000100819d88  sqmain() + 0x1c8
0x00000001014e0ef4  listen_verify() + 0x4b4
0x00000001014df968  spawn_thread() + 0x1028
0x000000010148d2dc  th_init_initgls() + 0x5c
0x000000010190323c  startup() + 0x1bc
0x000000010190307c  system(

#0  0x0000000000708e1c in cmprprenm ()
#1  0x0000000000709539 in distnmcmpr ()
#2  0x00000000006ac6d8 in find_cache_entry ()
#3  0x00000000006b0722 in find_cache ()
#4  0x00000000006b548a in retrieve_cache ()
#5  0x00000000006b6d34 in opgetdist ()
#6  0x00000000008c3b9f in lkeyidxstat ()
#7  0x00000000008c7a72 in lkeyidxdone ()
#8  0x00000000007c1b08 in indexp ()
#9  0x00000000007cb52d in opidxp ()
#10 0x00000000007cc40b in opscanp ()
#11 0x00000000007ddd77 in op_opinit ()
#12 0x00000000007cf96f in sqoptim ()
#13 0x0000000000a13db5 in sqbind ()
#14 0x0000000000a2a546 in sq_common_bind ()
#15 0x0000000000aeeaac in sqmain ()
#16 0x000000000154e6e9 in spawn_thread ()
#17 0x000000000140cae0 in th_init_initgls ()
#18 0x0000000001453c88 in startup ()
#19 0x0000000000000000 in ?? ()

Examples of asserting threads:

 base: 0x0000000051994000
  len:   135168
   pc: 0x000000000141b3c9
  tos: 0x0000000045aaa820
state: running
   vp: 9

0x000000000141b3c9 (oninit) afstack
0x000000000141e35c (oninit) afhandler
0x000000000141eaa2 (oninit) affail_interface
0x000000000141f091 (oninit) mt_ex_throw_sig
0x0000000001428293 (oninit) afsig_handler
0x0000003e0840e4c0 (Linux) 
0x0000000001435847 (oninit) mt_slock
0x00000000006b5d81 (oninit) retrieve_cache
0x00000000006b6d34 (oninit) opgetdist
0x00000000007a012b (oninit) get_distrib
0x00000000007bf3f5 (oninit) selec
0x00000000007c0454 (oninit) opselec
0x00000000007c80a7 (oninit) mc_toplevel
0x00000000007c8e0f (oninit) fl_costselec
0x00000000007d729f (oninit) makefll
0x00000000007d7056 (oninit) makefll
0x00000000007d7056 (oninit) makefll
0x00000000007d9556 (oninit) opinit
0x00000000007ddc35 (oninit) op_opinit
0x00000000007cf96f (oninit) sqoptim
0x0000000000a13db5 (oninit) sqbind
0x0000000000a2a546 (oninit) sq_common_bind
0x0000000000aeeaac (oninit) sqmain
0x000000000154e6e9 (oninit) spawn_thread
0x000000000140cae0 (oninit) th_init_initgls
0x0000000001453c88 (oninit) startup
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC11.         *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC11.         *
****************************************************************
Comment
Fixed in Informix Server 12.10.xC16 and 14.10.xC11.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.07.2023
27.09.2023
27.09.2023
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)