Oninit
Talk to an expert →

Informix Error -11092: Driver not capable.

Cause and resolution

Driver not capable.

The driver or data source does not support the function requested. For a list of supported driver functions, check the Informix CLI Programmer's Manual.

This Informix CLI error code is the same as SQLSTATE value S1C00. The following functions can return this error code:

SQLBindCol(), SQLBindParameter(), SQLColAttributes(), SQLColumnPrivileges(), SQLColumns(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetConnectOption(), SQLGetData(), SQLGetInfo(), SQLGetStmtOption(), SQLGetTypeInfo(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), SQLSetConnectOption(), SQLSetScrollOptions(), SQLSetStmtOption(), SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), SQLTables(), and SQLTransact().

For SQLBindCol(), the data source does not support the Informix CLI C data type (fCType) argument, or the icol value was 0. Set the Informix CLI C data type to a value that the data source supports and set icol to a valid value.

For SQLBindParameter(), SQLExtendedFetch(), SQLFetch(), and SQLGetData(), one of the following problems occurred: (1) It is not possible to convert the result data (the data value associated with the Informix CLI C data type (fCType) argument) to the data type of the parameter (the data value associated with the Informix CLI SQL data type (fSqlType) argument), or (2) The data source does not support the Informix CLI SQL data type or (3) The data source does not support the fetch type. Set the Informix CLI C and SQL data types to values that make it possible to convert the result data to the data type of the parameter and set the Informix CLI SQL data type and fetch type to values that the data source supports.

For SQLColAttributes(), the fDescType value is not a valid descriptor type. Use a valid value for fDescType.

For SQLColumnPrivileges(), SQLColumns(), SQLExecDirect(), SQLExecute(), SQLForeignKeys(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), SQLSpecialColumns(), SQLStatistics(), SQLTables(), and SQLTablePrivileges(), one of the following problems occurred: (1) You specified a qualifier for the procedure or table, but the data source does not support qualifiers, or (2) You specified an owner for the procedure or table, but the data source does not support owners, or (3) You specified a string search pattern for the procedure owner, procedure name, or column name, but the data source does not support search patterns for that argument, or (4) The combination of the SQL_CONCURRENCY value and the SQL_CURSOR_TYPE value is invalid. Do not set a qualifier, owner, or search pattern for a data source that does not support them and set the concurrency and cursor type values so that the combination of the values is valid.

For SQLGetConnectOption(), SQLGetStmtOption(), SQLSetConnectOption(), and SQLSetStmtOption(), the fOption value is not a valid option value. Set fOption to a valid value.

Additionally for SQLGetData(), the data source does not support the use of SQLGetData() with multiple rows in SQLExtendedFetch(), or the icol value was 0. Use SQLGetData() with multiple rows in SQLExtendedFetch() only if the data source supports this task and do not set icol to 0.

For SQLGetInfo(), the fInfoType value was not a valid information type. Set fInfoType to a valid value.

For SQLGetTypeInfo(), the data source does not support the Informix CLI SQL data type (fSqlType) argument), or the combination of the SQL_CONCURRENCY value and the SQL_CURSOR_TYPE value is invalid. Set the Informix CLI SQL data type to a value that the data source supports, and set the concurrency and cursor type values so that the combination of the values is valid.

For SQLTransact(), the data source does not support the ROLLBACK operation. Do not set fType to SQL_ROLLBACK.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-11092 fires when the driver or data source doesn't support the requested function — per the official guidance, this is the same as SQLSTATE value S1C00, returnable by a wide range of CLI functions (SQLBindCol(), SQLBindParameter(), SQLColAttributes(), SQLColumnPrivileges(), SQLColumns(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetConnectOption(), SQLGetData(), SQLGetInfo(), among others).

  1. For SQLBindCol(): the data source doesn't support the specified fCType, or icol was 0, per the official guidance — the first named case.
  2. For SQLBindParameter()/SQLExtendedFetch()/SQLFetch()/SQLGetData(): the result data can't convert to the parameter's data type, or the data source doesn't support the specified SQL data type or fetch type, per the official guidance — the second named case.
  3. For SQLColAttributes(): fDescType isn't a valid descriptor type, per the official guidance — the third named case.
  4. For the catalog-lookup functions (SQLColumnPrivileges(), SQLColumns(), SQLExecDirect(), SQLExecute(), SQLForeignKeys(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), SQLSpecialColumns(), SQLStatistics(), SQLTables(), SQLTablePrivileges()): a qualifier, owner, or search pattern the data source doesn't support, or an invalid SQL_CONCURRENCY/ SQL_CURSOR_TYPE combination, per the official guidance — the fourth named case.
  5. For SQLGetConnectOption()/SQLGetStmtOption()/SQLSetConnectOption()/ SQLSetStmtOption(): fOption isn't a valid option value, per the official guidance — the fifth named case.
  6. Additionally for SQLGetData(): the data source doesn't support using it with multiple rows in SQLExtendedFetch(), or icol was 0, per the official guidance — the sixth named case.
Solutions / Resolution
  1. For SQLBindCol(): use a fCType the data source supports, and a nonzero icol, per the official guidance.
  2. For SQLBindParameter()/SQLExtendedFetch()/SQLFetch()/SQLGetData(): set the CLI C and SQL data types to values that allow the conversion, and to values the data source supports, per the official guidance.
  3. For SQLColAttributes(): use a valid fDescType, per the official guidance.
  4. For the catalog-lookup functions: don't set a qualifier, owner, or search pattern the data source doesn't support, and set SQL_CONCURRENCY/SQL_CURSOR_TYPE to a valid combination, per the official guidance.
  5. For the get/set-option functions: set fOption to a valid value, per the official guidance.
  6. For SQLGetData(): use it with multiple rows in SQLExtendedFetch() only where the data source supports it, and don't set icol to 0, per the official guidance.
Examples
N/A

No specific triggering statement is documented beyond calling an unsupported function/feature.

Diagnostic Checks
  1. Call SQLGetFunctions()/SQLGetInfo() to check actual driver support before relying on a given function or feature.
Related Errors / Related Topics

No closely related error codes are cross-referenced for -11092 in this set yet.

The driver or data source doesn't support the requested function — check driver capability via SQLGetFunctions()/SQLGetInfo() first.