Informix Error -11275: Cursor operation conflict
Cause and resolution
Cursor operation conflict
This Informix ODBC error code is the same as SQLSTATE value 01001. The following functions can return this error code: SQLExecDirect, SQLExecute, and SQLSetPos.
For SQLExecute and SQLExecDirect, StatementText contained a positioned update or delete statement and no rows or more than one row were updated or deleted. (For more information about updates to more than one row, see the description of the SQL_ATTR_SIMULATE_CURSOR Attribute in SQLSetStmtAttr.) (Function returns SQL_SUCCESS_WITH_INFO.)
For SQLSetPos, the Operation argument was SQL_DELETE or SQL_UPDATE, and no rows or more than one row were deleted or updated. (For more information about updates to more than one row, see the description of the SQL_ATTR_SIMULATE_CURSOR Attribute in SQLSetStmtAttr.) (Function returns SQL_SUCCESS_WITH_INFO.)
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-11275 fires when a positioned UPDATE/DELETE affects zero or more than one row — per
the official guidance, this is the same as SQLSTATE value 01001, returnable by
SQLExecDirect, SQLExecute, and SQLSetPos.
- A positioned
UPDATE/DELETEstatement matching no rows or more than one row, per the official guidance — the direct, only cause; the function returnsSQL_SUCCESS_WITH_INFO.
Solutions / Resolution
- Confirm the cursor's positioning and targeting criteria, per the official guidance's implication, so exactly one row is affected.
- Check
SQL_ATTR_SIMULATE_CURSORinSQLSetStmtAttrfor detail on multi-row update behavior, per the official guidance.
Examples
N/A
No specific triggering statement is documented beyond a positioned statement affecting the wrong row count.
Diagnostic Checks
- Check the cursor's current position and the underlying query's row uniqueness before the positioned statement executes.
Related Errors / Related Topics
- -11008 — "No rows updated or deleted." The same underlying condition, specific to the zero-rows case.
- -11009 — "More than one row updated or deleted." The same underlying condition, specific to the multiple-rows case.
A positioned UPDATE/DELETE affected zero or more than one row — check the cursor's position and the query's row uniqueness.