Fixes are available
DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 2a - interim special build 2a
DB2 Version 9.1 Fix Pack 1 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 2 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
When using the historical analysis functionality of Query Patroller, the error DQP0007E (internal error) may be returned with the stack like the following. DQP0007E An internal error error has occurred. "com.ibm.xml.b2b.util.IOExceptionWrapper at ...b2b.util.CharConversionError.doThrow at ...b2b.util.CharConversionError.invalidUTF8CharacterEncoding at ...b2b.util.UTF8EncodingSupport.charConversionFailure at ...b2b.util.UTF8EncodingSupport.decodeCharacter <snipped...> at com.ibm.db2.qp.xml.B2BHandler.parse(B2BHandler.java:108) at com.ibm.db2.qp.data.HistoricalAnalysisData.callRetrieve( HistoricalAnalysisData.java:211) <snipped...> The problem occurs when using non-English character set, especially MBCS characters like Korean and Japanese. Here's one scenario where this problem occurs. 1. Create a database using MBCS character set. 2. Create a table with non-English name. For example, "?" in Korean. 3. Run some queries against this table. 4. From QP center, generate the historical report. 5. Try to access "Tables Hit"->"Columns Hit" data. This fails with the error above.
Local fix
Problem summary
Users Affected: Query Patroller users Problem Description: See ERROR DESCRIPTION above. Problem Summary: See ERROR DESCRIPTION above.
Problem conclusion
First fixed in DB2 UDB Version 9, Fixpack 1
Temporary fix
Comments
APAR Information
APAR number
IY87974
Reported component name
DB2 UDB QP AIX
Reported component ID
5724E2500
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-08-10
Closed date
2006-12-21
Last modified date
2006-12-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB QP AIX
Fixed component ID
5724E2500
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
07 January 2022