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

UDI Query might produce SQL0901N when extended indicator option is on

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might give SQL0901N error message in 
function sqlnq_fixup_src_expr_for_ext_ind 
 
The problem happens when the following conditions are met: 
1. EXTENDED INDICATORS is turned on. 
2. The query is prepared and executed using JDBC 
3. The query is of type update/delete/insert on a view 
containing outer joins 
 
You will come across the following message from db2diag.log: 
 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 58 
 sqlerrmc: sqlnq_fixup_src_expr_for_e[125]:rc(     0) 
 sqlerrp : SQLNN067 
 sqlerrd : (1) 0x8031010C      (2) 0x0000010C      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFDA8      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
<StackTrace> 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[100] 
sqlnq_sem_update[200] 
sqlnq_udi[154] 
sqlnq_fixup_src_expr_for_e[125] 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 Cancun Release 10.5.0.4                * 
****************************************************************
Local Fix:
Disable EXTENDED INDICATORS. 
 
This can be done by passing in the new value through Properties 
as follows: 
String url = "jdbc:default:connection"; 
Properties prop = new Properties(); 
prop.put("enableExtendedIndicators", "2"); 
... 
try {       con = DriverManager.getConnection(url, prop); 
 
Impact of disabling EXTENDED INDICATORS: 
If you do not use any of the methods that are described in this 
following document, then you can safely disable Extended 
Indicators with no impact. 
http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db 
2z10.doc.java/src/tpc/imjcc_c0056853.htm
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in DB2 Cancun Release 10.5.0.4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
03.11.2014
03.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList