| Latest versions | fixlist |
| 14.10.xC10 |
 |
| 12.10.xC16.X5 |
|
| 11.70.xC9.XB |
|
| 11.50.xC9.X2 |
|
| 11.10.xC3.W5 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
Informix - Problem description
| Problem IT17763 | Status: Closed |
ST_POINT() COULD FAIL WITH ASSERT FAILED: CONDITION FAILED (BAD POOL POINTER) WHEN PDQ IS USED | |
| product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
| Problem description: | |
A call of st_point() could fail with
10:10:33 Assert Failed: Condition Failed (Bad pool pointer
0x46155f40), In (mt_shm_malloc_segid)
10:10:33 Who: Session(5, user@machine, 32547, 0x44c73048)
Thread(63, scan_1.0, 44c36bb0, 1)
File: mtshpool.c Line: 4828
(oninit) mem_asfail
(oninit) mt_shm_malloc_segid
(oninit) mt_malloc
(oninit) mi_dalloc_internal
(/opt/informix/1210FC7W1/extend/spatial.8.22.FC2/spatial.bld)
UdrInfoInit
(/opt/informix/1210FC7W1/extend/spatial.8.22.FC2/spatial.bld)
ST_PointFromValues
(oninit) udrlm_clang_execute_internal
(oninit) udrlm_clang_execute
(oninit) udrlm_exec_routine
(oninit) udr_execute
(oninit) exroutine
(oninit) geval
(oninit) qd_update_params
(oninit) vti_update_params
(oninit) vii_beginscan
(oninit) vii_getnext
when PDQ is used.
Select fails with:
243: Could not position within a table
Not owner | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Spatial DataBlade with PDQ * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC9 * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.11.2016 10.07.2017 10.07.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
12.10.xC9 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
