Oninit
Talk to an expert →

Informix Error -11094: Timeout expired.

Cause and resolution

Timeout expired.

The time-out period expired before the connection to the data source completed. The time-out period is set through SQL_SetConnectionOption, SQL_LOGIN_TIMEOUT.

This Informix CLI error code is the same as SQLSTATE value S1T00. The following functions can return this error code: SQLBrowseConnect(), SQLColAttributes(), SQLColumnPrivileges(), SQLColumns(), SQLConnect(), SQLDescribeCol(), SQLDriverConnect(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetData(), SQLGetInfo(), SQLGetTypeInfo(), SQLMoreResults(), SQLNumParams(), SQLNumResultCols(), SQLParamData(), SQLPrepare(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), SQLPutData(), SQLSpecialColumns(), SQLStatistics(), SQLTablePrivileges(), and SQLTables().

For SQLBrowseConnect(), SQLConnect(), and SQLDriverConnect(), the time-out period expired before the function could complete the connection to the data source. Call SQLSetConnectOption() to change SQL_LOGIN_TIMEOUT.

For all other functions, the time-out period expired before the data source could process the information and, if necessary, return a result set or requested information. Call SQLSetConnectOption() to change SQL_QUERY_TIMEOUT.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-11094 fires when the connection's timeout period expires before it completes — per the official guidance, this is the same as SQLSTATE value S1T00, returnable by a wide range of CLI functions (SQLBrowseConnect(), SQLColAttributes(), SQLColumnPrivileges(), SQLColumns(), SQLConnect(), SQLDescribeCol(), SQLDriverConnect(), SQLExecDirect(), SQLExecute(), SQLExtendedFetch(), SQLFetch(), SQLForeignKeys(), SQLGetData(), SQLGetInfo(), SQLGetTypeInfo(), SQLMoreResults(), SQLNumParams(), SQLNumResultCols(), SQLParamData(), SQLPrepare(), SQLPrimaryKeys(), among others).

  1. The connection timeout, set via SQL_SetConnectionOption's SQL_LOGIN_TIMEOUT, expiring before the connection completed, per the official guidance — the direct, only cause.
Solutions / Resolution
  1. Increase SQL_LOGIN_TIMEOUT, per the official guidance's implication, if the connection legitimately needs more time.
  2. Check why the connection is taking longer than expected (network latency, server load) if increasing the timeout isn't appropriate.
Examples
N/A

No specific triggering statement is documented beyond an expired connection timeout.

Diagnostic Checks
  1. Check the SQL_LOGIN_TIMEOUT value, and check network/server conditions that might be slowing the connection.
Related Errors / Related Topics

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

The connection's timeout period expired before it completed — check SQL_LOGIN_TIMEOUT and network/server conditions.