Siebel Analytics Message Reference > Siebel Analytics Messages >

ODBC Access Messages

This category contains message numbers 16xxx.

16001

ODBC error state: @1%s code: @2%d message: @3%s.

Cause. The data source reported an ODBC error.

Response. Examine the error message text to determine the cause of the problem. Consult the vendor's documentation using the error number to determine the cause and response. If necessary, contact Siebel Systems Technical Support for assistance.

16002

Cannot obtain number of columns for the query result.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16003

Column description failed.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16004

Cannot obtain the number of columns for the input parameter.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16005

Input parameter description failed.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16006

Setting the statement option for extended fetch failed.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16007

ODBC error occurred while freeing statement resources.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16008

ODBC error occurred while canceling a statement execution.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16009

ODBC error occurred while binding the columns of a SQL statement.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16010

ODBC error occurred while retrieving information about the columns of a SQL procedure.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16011

ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16012

ODBC error occurred while binding the parameters of a SQL statement.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16013

Statement handle allocation error.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16014

SQL statement preparation failed.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16015

SQL statement execution failed.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16016

No connection pool for database @1%s.

Cause. An ODBC error occurred. No connection pool exists for the named database.

Response. Use the Administration Tool to define a connection pool for the database and retry your actions. If the problem persists, contact Siebel Systems Technical Support for assistance.

16017

Memory allocation error occurred while allocating ODBC environment.

Cause. An ODBC error occurred. The system may be short on resources.

Response. Close unnecessary applications and retry your actions. If the problem persists, contact Siebel Systems Technical Support for assistance.

16018

Database @1%s version @2%s is not supported.

Cause. An ODBC error occurred. The specified database version is not currently supported.

Response. Contact Siebel Systems Technical Support for assistance.

16019

Client @1%s version @2%s is not supported.

Cause. An ODBC error occurred. The specified client version is not currently supported.

Response. Contact Siebel Systems Technical Support for assistance.

16020

Metadata Database Type: @1%sData Source Name: @2%sData Source Type: @3%s.

Cause. The database server version is logged on first successful connection since start up.

Response. This is an informational message. No action is required.

16021

ODBC error occurred while resetting the parameters buffer of a SQL statement.

Cause. An ODBC error occurred.

Response. Contact Siebel Systems Technical Support for assistance.

16022

A bulkInsert statement has failed after successfully inserted @1%d rows but failed in batch @2%d. Maximum batch size @3%d. Current batch size @4%d.

Cause. Errors happen when you insert data in the back-end database.

Response. Check the detailed information with the native ODBC error code. You may need to delete inconsistent records from the database.