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

RESUMPTION OF SUPPORT FOR NAMED PIPES COMMUNICATION PROTOCOL.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Due to enlargement of communication buffer size introduced by 
fix pack 2 in regards to version 9.7 on some Windows OS usage of 
Named Pipes Communication protocol wasn't possible. 
 
One can be observed it in db2 trace flow, when trying to connect 
to database via cataloged NPIPE node. 
 
5637        | | | | | | | | | | | | | sqljrCreateTransport exit 
[rc = 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI] 
5638        | | | | | | | | | | | | sqljrAssociateTransport exit 
[rc = 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI] 
5639        | | | | | | | | | | | sqljrInternalConnect exit [rc 
= 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI] 
5640        | | | | | | | | | | sqljrLookupAddressAndConnect 
exit [rc = 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI] 
5641        | | | | | | | | | | sqljrReportErrorInternal entry 
5642        | | | | | | | | | | | sqleUCsetErrInfo entry 
5643        | | | | | | | | | | | | sqlzRcToSqlca entry 
5644        | | | | | | | | | | | | | sqlzGetZRCInfo entry 
5674        | | | | | | | | | | | | | sqlzGetZRCInfo exit [rc = 
0xFFFFFC7A = -902] 
5675        | | | | | | | | | | | | | pdInvokeCatchInterface 
entry 
5676        | | | | | | | | | | | | | pdInvokeCatchInterface 
data [probe 10] 
5677        | | | | | | | | | | | | | pdInvokeCatchInterface 
exit 
5678        | | | | | | | | | | | | sqlzRcToSqlca errtrans 
[probe 40] [ ZRC = 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI 
-->  SQL0902  ] 
5679        | | | | | | | | | | | | sqlzRcToSqlca error [probe 
50] [ ZRC = 0x87360014 = -2026504172 = SQLJC_ERROR_SYSI]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP4 or newer fix pack                    * 
****************************************************************
Local Fix:
Please configure TCP/IP communications
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.11.2013
17.07.2014
17.07.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList