Error messages
Error messages can come from the following:
• An ODBC driver
An error reported on an ODBC driver has the following format:
[vendor] [ODCB_component] message
ODBC_component is the component in which the error occurred. For example, an error message from INTERSOLV's SQL Server driver would look like this:
[INTERSOLV] ODCB SQL Server driver] login incorrect.
If you get this type of error, check the last ODBC call your application made for possible problems or contact Instantiations Support.
• The database system
An error that occurs in the data source includes the data source name in the following format:
[vendor] [ODBC_component] data source] message
With this type of message, ODBC_component is the component that received the error from the data source indicated. For example, you may get the following message from an Oracle data source:
[INTERSOLV] ODBC Oracle driver] Oracle] message
ORA-0919: specified length too long for CHAR column
If you get this type of error, you did something incorrectly with the database system. Check your database system documentation for more information or consult your database administrator. In this example, you would check your Oracle documentation.
• The driver manager
The driver manager is a DLL that establishes connections with drivers, submits requests to drivers, and returns results to applications. An error that occurs in the driver manager has the following format:
[vendor] [ODBC DLL] mmessage
vendor can be Microsoft or INTERSOLV. For example, an error from the Microsoft driver manager might look like this:
[Microsoft] ODBC DLL] Driver does not support this function
If you get this type of error, consult the Programmer's Reference for the Microsoft ODBC Software Development Kit, available from Microsoft.
Last modified date: 07/25/2020