home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC90452 Status: Closed

DB2 MIGHT CRASH WHEN RUNNING DBMS_ALERT.SET_DEFAULTS() SQL FUNCTION.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
It is possible that DB2 can crash when the system module 
function DBMS_ALERT.SET_DEFAULTS() routine is run.  The function 
takes a single argument (the polling interval that you want to 
set for use with other DBMS_ALERT module functions), but the 
actual value chosen as the input argument does not influence the 
chances of hitting this trap. 
 
The following is an example stack traceback that you might see 
if this trap is encountered: 
 
0x09000000407BC0E0 sqlemlGetModuleCb__F13sqlrSysModulePPvPb + 
0x80 
0x09000000407BC1C0 packageStateGet__F13sqlrSysModulePb + 0x40 
0x09000000407BC344 getSessionState__Fv + 0x124 
0x09000000407BE79C sqleml_dbms_alert_set_defaults + 0x13C 
0x0900000028D2077C sqloInvokeFnArgs + 0x11C 
0x090000002A909054 
sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0xD74 
0x090000002A91D930 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x5F0 
0x090000002A9216D4 sqlricall__FP8sqlrr_cb + 0x8F4 
0x0900000029742150 sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 
0x5D0 
0x0900000029744374 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0xE34 
0x0900000029AE9810 sqlrr_process_execute_request__FP8sqlrr_cbib 
+ 0x1CF0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v101 FP3                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fix will be available in v101 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.02.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList