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

JCC DRIVER RETURNS -4499 ERROR ON A SELECT QUERY WITH THREE PARTNAME FOR
DB2 Z/OS V11 NFM->V11 CM OR V10 NFM CONNECTIVITY

product:
DB2 JDBC SQLJ D / DB2DSDRVR / A50 - DB2
Problem description:
When a JCC thread connects to a DB2 z/OS V11 NFM and hops to a 
z/OS V11 CM using an explicit three-part name in the SQL 
statement, a -4499 occurs. 
The driver is trying to parse something which was meant for 
SQLAM11 even though the override says the current SQLAM level as 
10, resulting in an error. 
 
[jcc][SystemMonitor:start] 
[jcc][Time:2016-03-14-10:27:19.843][Thread:Worker-5][Statement@d 
f3c1450]execute (SELECT * FROM XXX1.SYSIBM.SYSDUMMY1  FOR FETCH 
ONLY  OPTIMIZE FOR 30000 ROWS ) called 
[jcc][t4][time:2016-03-14-10:27:19.843][Thread:Worker-5][tracepo 
int:1][Request.flush] 
[jcc][t4]        SEND BUFFER: PRPSQLSTT              (ASCII) 
(EBCDIC) 
 
[jcc][t4][time:2016-03-14-10:27:19.845][Thread:Worker-5][tracepo 
int:2][Reply.fill] 
[jcc][t4]        RECEIVE BUFFER: SQLDARD             (ASCII) 
(EBCDIC) 
: 
[jcc][Time:2016-03-14-10:27:19.846][Thread:Worker-5][Statement@d 
f3c1450]execute () returned true 
: 
[jcc][Time:2016-03-14-10:27:19.932][Thread:Worker-5][Statement@a 
a0c29a5]execute ( 
SELECT * FROM XXX2.SYSIBM.SYSDUMMY1  FOR FETCH ONLY  OPTIMIZE 
FOR 30000 ROWS ) called 
[jcc][t4][time:2016-03-14-10:27:19.932][Thread:Worker-5][tracepo 
int:1][Request.flush] 
[jcc][t4]        SEND BUFFER: PRPSQLSTT              (ASCII) 
(EBCDIC) 
 
 
[jcc][t4] 
[time:2016-03-14-10:27:19.932][Thread:Worker-5][tracepoint:101]R 
equest flushed. 
[jcc][t4] 
[time:2016-03-14-10:27:19.932][Thread:Worker-5][tracepoint:102]R 
eply to be filled. 
[jcc][t4][time:2016-03-14-10:27:19.950][Thread:Worker-5][tracepo 
int:2][Reply.fill] 
[jcc][t4]        RECEIVE BUFFER: MGRLVLOVR           (ASCII) 
(EBCDIC) 
 
[jcc][t4]        RECEIVE BUFFER: SQLDARD             (ASCII) 
(EBCDIC) 
 
 
  DDM Format: d0 RECV(AR) OBJDSS - Object Data Stream Structure 
  LL: 14  CORR: 0001  CHAINED: y  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: y 
 
    NM: MGRLVLOVR - Manager Level Overrides 
      LL: 8    CP: 1C03 
      * SQLAM - SQL Application Manager 
        LEVEL OF SUPPORT: 10 
 
 
 
    SEND BUFFER(AR): 
 
            EXCSAT RQSDSS 
        * SQLAM - SQL Application Manager 
          LEVEL OF SUPPORT: 11 
 
 
 
[jcc][t4][time:2016-03-14-10:27:19.969][Thread:Worker-5][tracepo 
int:2][Reply.fill] 
 
    RECEIVE BUFFER(AR): 
 
            EXCSATRD OBJDSS 
 
 
        * SQLAM - SQL Application Manager 
          LEVEL OF SUPPORT: 11 
 
[jcc][t4] 
[time:2016-03-14-10:27:19.954][Thread:Worker-5][tracepoint:202] 
closing non-pooled Transport: 
[jcc][t4] 
[time:2016-03-14-10:27:19.954][Thread:Worker-5][tracepoint:530]c 
ompleteLocalRollback 0 
[jcc][Time:2016-03-14-10:27:19.954][Thread:Worker-5][ResultSet@d 
3b4e518]completeLocalRollback (true, false) called 
[jcc][Time:2016-03-14-10:27:19.954][Thread:Worker-5][ResultSet@d 
3b4e518]markClosed () called 
 
[jcc] BEGIN TRACE_DIAGNOSTICS 
[jcc][Thread:Worker-5][SQLException@613abcd] 
java.sql.SQLException 
[jcc][Thread:Worker-5][SQLException@613abcd] SQL state  = null 
[jcc][Thread:Worker-5][SQLException@613abcd] Error code = -4499 
[jcc][Thread:Worker-5][SQLException@613abcd] Message    = 
[jcc][t4][2085][11336][4.19.26] Mutually exclusive fields cannot 
both contain non-null values. ERRORCODE=-4499, SQLSTATE=null 
[jcc][Thread:Worker-5][SQLException@613abcd] Stack trace follows 
com.ibm.db2.jcc.am.DisconnectRecoverableException: 
[jcc][t4][2085][11336][4.19.26] Mutually exclusive fields cannot 
both contain non-null values. ERRORCODE=-4499, SQLSTATE=null 
        at com.ibm.db2.jcc.am.kd.a(Unknown Source) 
        at com.ibm.db2.jcc.am.kd.a(Unknown Source)
Problem Summary:
First fixed in JDBC driver version 3.69.66 /4.19.62 (included 
in DB2 v10.5 FP8)
Local Fix:
Solution
Upgrade to JDBC driver version 3.69.66 /4.19.62 (included 
in DB2 v10.5 FP8) or higher
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.2016
25.05.2017
25.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)