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 IT43586 Status: Closed

A THREAD CAN FAIL IN STMP_CHOOSEDBS_INTERNAL AFTER DROPPING A TEMP DBSPACE
THAT EXISTS IN ENV DBSPACETEMP

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
Consider an onconfig file with the DBSPACETEMP setting:

DBSPACETEMP temp1,temp2

If you set the environment variable, DBSPACETEMP like:

$ export DBSPACETEMP=temp2

and then start a dbaccess session:

$ dbaccess stores_demo -

  Database selected.

  >

Now if you modify the effective value of DBSPACETEMP via
onmode:
$  sudo   onmode -wm DBSPACETEMP=temp1

and then drop the dbspace temp2:
$ onspaces -d temp2 -y

and then try to run a query that creates a temp table in the
open session that you started above:

> select * from customer into temp tmptbl;

You will assert with a stack like below:

0x000000000141b3c9 (oninit) afstack
0x000000000141e35c (oninit) afhandler
0x000000000141eaa2 (oninit) affail_interface
0x000000000141f091 (oninit) mt_ex_throw_sig
0x0000000001428293 (oninit) afsig_handler
0x0000003e0840e4c0 (Linux) 
0x0000000000dc382c (oninit) stmp_choosedbs_internal
0x000000000081290f (oninit) itbldins
0x000000000081dc2e (oninit) itbldroot
0x00000000007d1851 (oninit) sqoptim
0x0000000000a1411a (oninit) bldstructs
0x0000000000a1743e (oninit) sqcmd
0x0000000000a19eda (oninit) sq_cmnd
0x0000000000a1a034 (oninit) sq_prepare
0x0000000000aeeaac (oninit) sqmain
0x000000000154e6e9 (oninit) spawn_thread
0x000000000140cae0 (oninit) th_init_initgls
0x0000000001453c88 (oninit) startup

The session will also be holding the mutex:

Locked mutexes:
mid      addr             name               holder   lkcnt
waiter   waittime
5143     45cc7e90         globltmpdbs        61       0

and may keep the server from going down.

Many variations of stacks are possible depending on when
stmp_choosedbs_internal is called,
for instance, another reported stack was:

0x00000000014104d9 (oninit) afstack
0x00000000014134b1 (oninit) afhandler
0x0000000001413c92 (oninit) affail_interface
0x0000000001414221 (oninit) mt_ex_throw_sig
0x000000000141de93 (oninit) afsig_handler
0x00007fae12ef0630 (Linux) 
0x0000000000dbbc6c (oninit) stmp_choosedbs_internal
0x0000000000d03fc2 (oninit) rspnbuild_sz
0x00000000005ffbb9 (oninit) bldpartn
0x00000000005ffd8c (oninit) bldtmpfile
0x00000000007fe819 (oninit) prepselect
0x000000000087bf49 (oninit) subqprep
0x000000000087c135 (oninit) exsubqm
0x000000000087c79e (oninit) subqcmp
0x000000000164e0f6 (oninit) ev_anyall
0x000000000164d6be (oninit) new_eval
0x00000000007f396b (oninit) readidx_new
0x00000000007f7de4 (oninit) gettupl
0x00000000007faa64 (oninit) scan_next
0x00000000008251c8 (oninit) merge_next
0x0000000000821ee2 (oninit) sort_open
0x00000000007fe8dd (oninit) prepselect
0x0000000000a1ffae (oninit) open_cursor
0x000000000069316b (oninit) ip_scurstart
0x000000000069761c (oninit) ip_evalcursor
0x0000000000699ff8 (oninit) runproc
0x000000000069b691 (oninit) udrlm_spl_execute
0x0000000000a630be (oninit) udrlm_exec_routine
0x00000000006d6e19 (oninit) udr_execute
0x000000000069c39c (oninit) ip_curnext
0x000000000069db12 (oninit) ip_evalcurnext
0x0000000000699fca (oninit) runproc
0x000000000069b691 (oninit) udrlm_spl_execute
0x0000000000a630be (oninit) udrlm_exec_routine
0x00000000006d6e19 (oninit) udr_execute
0x00000000006dd5e5 (oninit) exroutine
0x00000000008761eb (oninit) geval
0x000000000164d261 (oninit) ev_geval
0x000000000164d6be (oninit) new_eval
0x0000000000694770 (oninit) ip_evalexpr
0x0000000000699cc4 (oninit) runproc
0x000000000069b691 (oninit) udrlm_spl_execute
0x0000000000a630be (oninit) udrlm_exec_routine
0x00000000006d6e19 (oninit) udr_execute
0x00000000006dd5e5 (oninit) exroutine
0x00000000005cc700 (oninit) execproc
0x00000000006c5f3e (oninit) aud_execproc
0x00000000005d3fe4 (oninit) excommand
0x0000000000a27753 (oninit) sq_execute_workhorse
0x0000000000a27d6e (oninit) sq_execute
0x0000000000ae7b71 (oninit) sqmain
0x000000000154298b (oninit) spawn_thread
0x0000000001401cf0 (oninit) th_init_initgls
0x0000000001448a17 (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 (when
available).
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 (when
available).
Comment
Fixed in Informix Server 12.10.xC16 and 14.10.xC11.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.04.2023
18.05.2023
18.05.2023
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)