A fix is available
APAR status
Closed as program error.
Error description
DB2DDF defect pm29560 dpm29560 In a coexisting group(DV2 V9 and V10), DB2 V10 member receives the following error message when application tries to insert XML data: DSNT408I SQLCODE = -20398, ERROR: ERROR ENCOUNTERED DURING XML PARSING AT LOCATION 32752 An incorrect character is found in element contentRC=000C,RSN=30 DSNT418I SQLSTATE = 2200M SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNNOPAR SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = -490 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'FFFFFE16' X'00000000' X'00000000' X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION ************************************************************ Additional symptoms and keywords: SQLCODE20398 SQL20398N -20398
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using XML. * **************************************************************** * PROBLEM DESCRIPTION: A local DB2 application fetches a large * * (>32K) XML column data from a remote * * DB2 for z/OS server. When the local DB2 * * attempts to insert the large XML column * * data, it receives the following: * * SQLCODE = -20398 * * SQLSTATE = 2200M * * SQLERRP = DSNNOPAR * * SQLERRD = -490 0 0 -1 0 0 * **************************************************************** * RECOMMENDATION: * **************************************************************** An application uses DB2 for z/OS as the client to fetch a 64K XML data value from a remote DB2 for z/OS server and attempts to insert the data into a local DB2 table. Since the value being fetched is larger than 32K, the DB2 requester needs to expand the output buffer to hold the large amount of XML data but DB2 incorrectly passes the old freed output buffer, containing residual data, to the application. This causes the application to receive SQLCODE -20398 when it tries to insert the XML value from an invalid output buffer address into the local DB2 server.
Problem conclusion
DB2 for z/OS client processing for XML is changed to return the correct buffer address to the application, in case of buffer expansion.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM29560
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2010-12-28
Closed date
2011-01-21
Last modified date
2011-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK64143 UK64144
Modules/Macros
DSNLCCLO
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 March 2011