|
Problem IC99456
|
Status: Geschlossen |
WHEN STATEMENTCONCENTRATOR IS SET ALONG WITH SQL_ATTR_PARAMOPT_A TOMIC=0, CLI APP ERRORS OUT AGAINST DB2 Z/OS(-20186,-215, -312) |
| Produkt: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problembeschreibung: |
Issues fixed through this APAR:
- WHEN STATEMENTCONCENTRATOR IS ENABLED ALONG WITH
SQL_ATTR_PARAMO PT_ATOMIC=0, CLI APPLICATION RECEIVES -20186
AGAINST DB2 Z/OS
- SQL0104N error when statement concetrator and EXTENDED
INDICATORS is enabled
- when an insert statement with non-array inserts is executed
with statement concentrator enabled, server would throw -215
back to client.
- -312 error when statement concentrator is enabled and insert
statement is retried.
When Statementconcentrator is enabled along with
SQL_ATTR_PARAMOPT_ATOMIC=0, CLI application receives SQLCODE
=-20186 against DB2 z/OS
Message=[IBM][CLI Driver][DB2] SQL0969N There is no message
text corresponding to SQL error "-20186" in the message file on
this workstation. The error was returned from module "DSNXEDP
" with original tokens "". SQLSTATE=07501
Trace snippet:
21827 entry DB2 UDB call level interface SQLSetStmtAttrW api
(1.3.42.534.3)^M
pid 5056 tid 5092 cpid -1 node -1 sec 142 nsec
88846766^M
^M
bytes 24^M
^M
Data1 (PD_CLI_TYPE_HSTMT,4) Statement Handle:^M
hStmt=1:1^M
Hex:^M
0100 0100 ....^M
^M
Data2 (PD_CLI_TYPE_STMT_ATTR,4) Statement Attribute:^M
SQL_PARAMOPT_ATOMIC^M
Hex:^M
EC04 0000 ....^M
^M
DB2 trace DRDA buffer:
21988 data DB2 UDB DRDA Communication Manager sqljcSend fnc
(3.3.54.5.0.1177)
pid 5056 tid 5092 cpid -1 node -1 sec 52324 nsec 781463286
probe 1177
bytes 248
SEND BUFFER(AR):
EXCSQLIMM RQSDSS (ASCII)
(EBCDIC)
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
0123456789ABCDEF
0000 0053D0510001004D 200A004421134445 .S.Q...M ..D!.DE
..}....(........
0010 565F445354312020 2020202020202020 V_DST1
.^..............
0020 4E554C4C49442020 2020202020202020 NULLID
+.<<............
0030 2020535953534832 3030202020202020 SYSSH200
................
0040 202020205359534C 564C303100410005 SYSLVL01.A..
.......<.<......
0050 2105F1 !..
..1
SQLATTR OBJDSS (ASCII)
(EBCDIC)
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
0123456789ABCDEF
0000 0058D05300010052 245000000000484E .X.S...R$P....HN
..}......&.....+
0010 4F542041544F4D49 4320434F4E54494E OT ATOMIC CONTIN
!....!(....!+..+
0020 5545204F4E205351 4C45584345505449 UE ON SQLEXCEPTI
...!+...<....&..
0030 4F4E20434F4E4345 4E54524154452053 ON CONCENTRATE S
!+..!+..+.......
0040 544154454D454E54 532057495448204C TATEMENTS WITH L
....(.+........<
0050 49544552414C53FF ITERALS.
.....<..
SQLSTT OBJDSS (ASCII)
(EBCDIC)
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
0123456789ABCDEF
0000 002DD04300010027 2414000000001D53 .-.C...'$......S
..}.............
0010 4554204355525245 4E542053514C4944 ET CURRENT SQLID
........+....<..
0020 203D202740543030 31323027FF = '@xxxxxx'.
.... ........ |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* CLI application users connecting to DB2 zOS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 4 or higher *
**************************************************************** |
| Local-Fix: |
Remove SQL_PARAMOPT_ATOMIC=0 from the application or
SQL_PARAMOPT_ATOMIC=1 |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 10.1 Fix Pack 4. |
| Workaround |
Remove SQL_PARAMOPT_ATOMIC=0 from the application or
SQL_PARAMOPT_ATOMIC=1 |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 18.02.2014
11.06.2014
11.06.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.4
|
 |
