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 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 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )
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
.NET application will fail with CLI0108E error and SQL30020 error messages are found in db2diag log file. This occurs when the precision of the DB2.NET data type is greater than 31 as DB2 only supports a maximum precision of 31 digits. The reason behind this malfunction is because there is a lack of checking for a maximum precision value for DB2.NET data type. Eventually, this causes the .NET application to abend.
Local fix
Problem summary
USERS AFFECTED: ALL PROBLEM DESCRIPTION: .NET application will fail with CLI0108E error and SQL30020 error messages are found in db2diag log file. This occurs when the precision of the DB2.NET data type is greater than 31 as DB2 only supports a maximum precision of 31 digits. The reason behind this malfunction is because there is a lack of checking for a maximum precision value for DB2.NET data type. Eventually, this causes the .NET application to abend. PROBLEM SUMMARY: SQL30020 error occurs due to lack of checking for maximum precision with DB2.NET data. This leads application to abend.
Problem conclusion
First fixed in DB2 UDB Version 8.1, FixPak 15
Temporary fix
Comments
APAR Information
APAR number
JR25400
Reported component name
DB2 UDB EXE WIN
Reported component ID
5724E4901
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-11-29
Closed date
2007-08-22
Last modified date
2007-08-22
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 EXE WIN
Fixed component ID
5724E4901
Applicable component levels
R810 PSY
UP
R820 PSY
UP
Document Information
Modified date:
08 January 2022