2 Error Messages
Error messages can be generated from:
An error reported on an ODBC driver has the following format:
where ODBC_component is the component in which the error occurred. For example, an error message from a DataDirect Oracle driver would look like this:
If you receive this type of error, check the last ODBC call made by your application for possible problems or contact your ODBC application vendor.
An error that occurs in the data source includes the data store name, in the following format:
With this type of message, ODBC_component is the component that received the error specified by the data store. For example, you may receive the following message from an Oracle data store:
This type of error is generated by 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.
On Windows, the Microsoft 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:
For example, an error from the Microsoft Driver Manager might look like this:
If you receive this type of error, consult the Programmer's Reference for the Microsoft ODBC Software Development Kit available from Microsoft.
On UNIX and Linux, the Driver Manager is provided by DataDirect. For example, an error from the DataDirect Driver Manager might look like this:
UNIX and Linux error handling follows the X/Open XPG3 messaging catalog system. Localized error messages are stored in the subdirectory:
locale/localized_territory_directory/LC_MESSAGES
where localized_territory_directory depends on your language.
For instance, German localization files are stored in locale/de/LC_MESSAGES, where de is the locale for German.
If localized error messages are not available for your locale, then they will contain message numbers instead of text. For example: