A fix is available
APAR status
Closed as program error.
Error description
DB2 Log Analysis can output SQL that contain column strings that are over 32,000 bytes. If a statement with such a string also has long table names and long column names, it is possible for Fast Apply SQL to issue a return code of 8 with a "Failed parsing SQL statement." message because the input buffer size was not large enough for the SQL. Additionally, variation 9 type log records supporting these large SQL stmts may be generated with separate UNDO and REDO log records, which required modifications as these log records are documented as occurring in one log record only. Prior to this modification, a PUT error on the ROWDATA file could occur.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Log Analysis Tool. * **************************************************************** * PROBLEM DESCRIPTION: DB2 Log Analysis can output SQL that * * contain column strings that are over * * 32,000 bytes. If a statement with such * * a string also has long table names and * * long column names, it is possible for * * Fast Apply SQL to issue a return code * * of 8 with a "Failed parsing SQL * * statement." message because the input * * buffer size was not large enough for * * the SQL. * * * * Additionally, variation 9 type log * * records supporting these large SQL * * stmts may be generated with separate * * UNDO and REDO log records, which * * required modifications as these log * * records are documented as occurring * * in one log record only. Prior to this * * modification, a PUT error on the * * ROWDATA file could occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** Apply the PTF.
Problem conclusion
Apply the PTF.
Temporary fix
Comments
APAR Information
APAR number
PM04469
Reported component name
DB2 LOG ANALYSI
Reported component ID
5655E6601
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-01-05
Closed date
2011-01-12
Last modified date
2011-02-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ALA@FSP
Fix information
Fixed component name
DB2 LOG ANALYSI
Fixed component ID
5655E6601
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]
Document Information
Modified date:
12 April 2021