DB2 - Problem description
Problem IC85627 | Status: Closed |
TRAP CALLING SQLEXECUTE FOR AN INSERT STATEMENT FOR A DB2 FOR Z/OS DATABASE. | |
product: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problem description: | |
Applications might trap while calling CLI (Call Level Interface) API function SQLExecute to issue an INSERT statement. It happens when an application calls SQLExecute for an INSERT statement if the application has previously called SQLExendedBind with the value of the rgbValue parameter as NULL. When the trap occurs, at the top of the function stack are these functions: SQLExecute2 SQLExecute The trap occurs only if the application is using Multi-Row Insert. Only CLI applications that are connected to DB2 for z/OS database can use Multi-Row Insert, so only applications that connect to a DB2 for z/OS database can get this trap. Applications use Multi-Row Insert by setting the CLI connection attribute or CLI statement attribute SQL_ATTR_COLUMNWISE_MRI toSQL_COLUMNWISE_MRI_ON. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * CLI users using MRI feature against zDB2. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1.1 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
From v10.1 FP1 if the user binds the rgbValue to NULL in the loop while using MRI won't trap. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.07.2012 02.11.2012 02.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |