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

ASSERTION FAILURE WHEN YOU RUN A STORED PROCEDURE THAT HAD UPDATE
STATISTICS RUN ON IT WITH PDQ ENABLED

product:
IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50
Problem description:
A stored procedure crashes a scan thread and the database 
serverif PDQ was enabled when 'update statistics for routine' 
was run. 
The stack trace in the assertion failure file will look similar 
to this: 
 
(oninit) afstack 
(oninit) mt_ex_throw_sig 
(oninit) afsig_handler 
(Linux) <signal frame> 
(oninit) gettupl 
(oninit) scan_next 
(oninit) producer_thread 
(oninit) startup
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running stored procedures with implicitly casted       * 
* lvarchar and PDQ .                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When SPL uses implicitly casted lvarchar and if PDQ was      * 
* enabled when 'update statistics for routine' was run the     * 
* server crashes in the scan thread.                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IDS 11.50.xC5 or above.                           * 
****************************************************************
Local Fix:
Disable PDQ and then run update statistic for routine.
Solution
Problem is fixed in  IDS 11.50.xC5.
Workaround
Disable PDQ before running update statistics.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.05.2009
19.01.2010
19.01.2010
Problem solved at the following versions (IBM BugInfos)
11.50.xC5
Problem solved according to the fixlist(s) of the following version(s)
11.50.xC4.W1 FixList
11.50.xC5 FixList