|
Problem IT13450
|
Status: Closed |
SQLEXECUTE() MAY RETURN SQL_ERROR INSTEAD OF SQL_SUCCESS_WITH_INFO WHEN USING ENABLEINSERTCURSORS
|
| product: |
IBM CSDK / 5724C2381 / 410 - CSDK 4.10 |
| Problem description: |
Having an ODBC program that inserts multiple rows by binding
arrays of values and you have set the parameter
ENABLEINSERTCURSORS
if not all rows are inserted successfully, SQLExecute() or
SQLExecDirect () returns SQL_ERROR instead of
SQL_SUCCESS_WITH_INFO.
A side effect of this is that when the application calls
SQLRowCount() to find out how many rows were processed, this
call will also fail with SQL_ERROR returning the error
description "Function sequence error".
This problem only appears if the reason for the failure is
detected within the ODBC driver (before sending the rows to the
Informix engine).
If the failure is detected within the engine (e.g. constraint
violation) the error returned is the expected
SQL_SUCCESS_WITH_INFO (APAR IC89882). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Application using Informix ODBC driver trying to insert *
* value in batch *
****************************************************************
* PROBLEM DESCRIPTION: *
* Problem occurs in application using Informix ODBC driver *
* trying to insert value in batch by enabling *
* ENABLEINSERTCURSORS. *
* If a client side error happens in the middle of this process *
* the driver returns SQL_ERROR instead of *
* SQL_SUCCESS_WITH_INFO. *
****************************************************************
* RECOMMENDATION: *
* The problem has been fixed with CSDK 4.10.xC7. Please *
* upgrade CSDK to this version or higher. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
For download information, go to:
http://www.ibm.com/support/fixcentral |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.01.2016
29.06.2016
29.06.2016 |
| Problem solved at the following versions (IBM BugInfos) |
4.10.xC7
|
| Problem solved according to the fixlist(s) of the following version(s) |
