|
Problem IT44064
|
Status: Closed |
CREATING OR EXECUTING SOME STORED PROCEDURES CAN ASSERT IN CMPREXPRTREE2 WITHIN SQOPTIM
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
Creating a stored procedure will succeed but cause an assertion
with a stack like:
0x00000000014ddefd (oninit) afstack
0x00000000014db969 (oninit) afhandler
0x00000000014d86a2 (oninit) affail_interface
0x00000000014e0e52 (oninit) mt_ex_throw_sig
0x00000000014e2828 (oninit) afsig_handler
0x00007fbec7e325e0 (Linux)
0x0000000000aa1d6b (oninit) cmprexprtree2
0x0000000000aa26bd (oninit) cmprexprtree
0x0000000000827dcd (oninit) oi_search_idx_expr
0x000000000082a146 (oninit) oporindex
0x000000000097378f (oninit) opjoinp
0x000000000096ecc2 (oninit) opdojoin
0x000000000098353b (oninit) chk_dir_oj
0x000000000096db0a (oninit) opjoin
0x000000000097e811 (oninit) op_join
0x0000000000982768 (oninit) op_phasejoin
0x000000000080d753 (oninit) sqoptim
0x00000000009e9f91 (oninit) optsubq
0x00000000009e9dd1 (oninit) oplooksubq
0x00000000006e2659 (oninit) ip_exproptim
0x000000000070451b (oninit) cmp_stmt
0x00000000007037d5 (oninit) pr_compile
0x0000000000a80fe4 (oninit) creatproc
0x0000000000721015 (oninit) aud_creatproc
0x0000000000606b92 (oninit) excommand
0x0000000000ab211c (oninit) sq_execute_workhorse
0x0000000000ab286d (oninit) sq_execute
0x0000000000b9701e (oninit) sqmain
0x0000000001611e39 (oninit) spawn_thread
0x00000000014cafd3 (oninit) th_init_initgls
0x0000000001513bff (oninit) startup
Attempting to execute this procedure thereafter will also cause
an assert with a stack like:
0x00000000014ddefd (oninit) afstack
0x00000000014db969 (oninit) afhandler
0x00000000014d86a2 (oninit) affail_interface
0x00000000014e0e52 (oninit) mt_ex_throw_sig
0x00000000014e2828 (oninit) afsig_handler
0x00007fbec7e325e0 (Linux)
0x0000000000aa1d6b (oninit) cmprexprtree2
0x0000000000aa26bd (oninit) cmprexprtree
0x0000000000827dcd (oninit) oi_search_idx_expr
0x000000000082a146 (oninit) oporindex
0x000000000097378f (oninit) opjoinp
0x000000000096ecc2 (oninit) opdojoin
0x000000000098353b (oninit) chk_dir_oj
0x000000000096db0a (oninit) opjoin
0x000000000097e811 (oninit) op_join
0x0000000000982768 (oninit) op_phasejoin
0x000000000080d753 (oninit) sqoptim
0x00000000009e9f91 (oninit) optsubq
0x00000000009e9dd1 (oninit) oplooksubq
0x00000000006e2659 (oninit) ip_exproptim
0x00000000006e039b (oninit) ip_evalexpr
0x00000000006dd2b0 (oninit) runproc
0x00000000006f1359 (oninit) udrlm_spl_execute
0x0000000000b11210 (oninit) udrlm_exec_routine
0x000000000072de0d (oninit) udr_execute
0x0000000000739dc6 (oninit) exroutine
0x00000000006097ac (oninit) execproc
0x00000000007212de (oninit) aud_execproc
0x0000000000606aee (oninit) excommand
0x0000000000ab211c (oninit) sq_execute_workhorse
0x0000000000ab286d (oninit) sq_execute
0x0000000000b9701e (oninit) sqmain
0x0000000001611e39 (oninit) spawn_thread
0x00000000014cafd3 (oninit) th_init_initgls
0x0000000001513bff (oninit) startup |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC11. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.06.2023
01.06.2024
01.06.2024 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
