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 IT21811 Status: Closed

FEDERATION AND DBMS_SQL MAY RECEIVE SIGSEGV AT SQLEUCTRUSTEDLVLINIT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
An associated trap file has stack trace backs as below.
-----
sqleUCtrustedLvlInit
sqlriFedOneTimeInitRtn
sqlriFedInvokeInvoker
sqlqg_Call_FMP_Thread
sqlqgDeleteServer
sqlqgDeleteWrapper
sqlqgApplicationTerminationv
sqle_term_app_dj_cb
sqlrr_appl_free_appl_cbs
sqlrr_appl_term
sqeApplication
sqlesrspWrp
sqleUCagentConnectReset
----

There is a timing hole which may lead a sigsegv and crash.
It may be occurred where the system calls DBMS_SQL.* routines
and federated procedures.

There are two potential workarounds.

- It should not happen by avoiding to call DBMS_SQL
  routines and federated procedures same timing.

- It should not happen if creating a DARA wrapper with
DB2_FENCE='Y'
  and use federated procedures with it only.  And also avoiding
  to call DBMS_SQL.* routines with this wrapper.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 Version 11.1                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 Version 11.1 Mod 2 Fix Pack 2.                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT18043 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2017
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)