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

STATEMENT MAY FAIL WITH FOLLOWING ERROR: PERMANENT TAOB FOR MDC BIXA OBJECT
IS NULL

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Complex SQL statement that has nested IXA operations could fail 
with SQL0901N "permanent TAOB for MDC BIXA object is NULL" 
db2diag.log: 
 
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 43 
sqlerrmc: permanent TAOB for MDC BIXA object is NULL 
sqlerrp : SQLNG0AE
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 iFix002 or higher       * 
****************************************************************
Local Fix:
apply this fix or try changing plan using optguidelines
available fix packs:
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1 Mod 2 Fix Pack 2 iFix002
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.12.2017
22.12.2017
22.12.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)