|
Problem IT33728
|
Status: Closed |
SEGV ASSERTION FAILURE IN UDR_EXECUTE, RESULTING IN -9791 ERROR ON EXECUTE PROCEDURE CALL
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
This is the stack of the failing thread at the time of the
assertion:
afsig_handler
udr_execute
udr_spl_curnext
ip_curnext
ip_evalcurnext
runproc
udrlm_spl_execute
udrlm_exec_routine
udr_execute
udr_spl_curnext
ip_curnext
ip_fetch
getrow
fetchrow
exfetch
sql_nfetch
sq_nfetch
sqmain
spawn_thread
th_init_initgls
startup
The current SQL from the failing session:
Stored procedure stack :
context proc-counter opcode name
----------------------------------------------------------------
--
0x0000000046f22058 0x46e68d38+0x0008 RETURN db1:qryt3
0x0000000046f1d890 0x46e59998+0x0008 RETURN db1:qryt2
0x0000000046f15058 0x46e39e08+0x0008 RETURN db1:qryt1
0x0000000046f0e058 0x46e399f0-0x0010 CURNEXT db1:proc3
Current SQL statement (21) in procedure db1:qryt3
proc-counter 0x0x46e68cd0 opcode CURSOR
"0$c_t3" is select c1
from t2
where (= c1, i1)
To encounter this problem, the session would have to have 2
cursors declared for the same statement, as illustrated by the
following onstat -g stm output for the session:
session 34
---------------------------------------------------------------
sdblock heapsz flags statement ('*' = Open cursor)
468c4028 14040 ----- *execute procedure proc3(?)
468c42e0 4960 -----
468c4598 11328 -----
468c4850 11232 -----
468c4b08 12352 -----
468c4dc0 12256 -----
468c5078 12352 -----
468c5330 12256 ----- *
468c55e8 14040 ----- *execute procedure proc3(?)
468c58a0 11328 -----
468c5b58 11232 ----- *
468c5e10 12376 -----
468c60c8 12256 ----- *
So you can see the "execute procedure proc3()" shows up twice in
the list. This is because there are 2 cursors for that same
statement. Additionally i believe that the SPL code in the
procedure has to have foreach execute procedure statements as
part of the code. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC5. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC5. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC5. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC15 and 14.10.xC5. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.07.2020
22.01.2021
22.01.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
