Title | Contents | Previous | Next

Chapter 1

Overview of Error Codes and Messages

This chapter provides general information about SequeLink's error handling strategy and describes the types of errors that can occur when using SequeLink.

Each generated error message includes the following information:

For information about the types of errors that can occur when:

SequeLink ODBC Driver

The following types of errors can occur when you are using the SequeLink ODBC Driver:

SequeLink ODBC Driver Errors

An error generated by the SequeLink ODBC Driver has the following format:

[INTERSOLV] [ODBC SequeLink driver] message



For ex ample:

[INTERSOLV] [ODBC SequeLink driver] Invalid 



precision specified.



The native error code is always zero (0).

If you receive this type of error, check the last ODBC call your application made. Contact your ODBC application vendor, or refer to the ODBC 2.0 Programmer's Reference and SDK Guide or the ODBC 3.0 Programmer's Reference and SDK Guide, both available from Microsoft Press.

SequeLink Client Errors

An error generated by the SequeLink ODBC Edition Client has the following format:

[INTERSOLV] [ODBC SequeLink driver] [SequeLink 



Client] message



For exam ple:

[INTERSOLV] [ODBC SequeLink driver] [SequeLink 



Client] The specified transliteration module is 



not found.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions."

SequeLink Server Errors

An error generated by SequeLink Server has the following format:

[INTERSOLV] [ODBC SequeLink driver] [SequeLink 



Server] message



For ex ample:

[INTERSOLV] [ODBC SequeLink driver] [SequeLink 



Server] This SequeLink server service is not 



active.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions."

Database Errors

An error generated by the database has the following format:

[INTERSOLV] [ODBC SequeLink driver] [...] message



For ex ample:

[INTERSOLV] [ODBC SequeLink driver] [Oracle] 



ORA-00942:table or view does not exist.



Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.

SequeLink OLE DB Provider

The following types of errors can occur when you are using the SequeLink OLE DB Provider:

SequeLink OLE DB Provider Errors

An error generated by the SequeLink OLE DB Provider has the following format:

[INTERSOLV] [OLE DB SequeLink provider] message



For ex ample:

[INTERSOLV] [OLE DB SequeLink provider] Invalid 



precision specified.



The native error code is always zero (0).

If you receive this type of error, check the last OLE DB call your application made. Contact your OLE DB application vendor, or refer to the OLE DB 2.0 Programmer's Reference and SDK Guide, available from Microsoft Press.

SequeLink Client Errors

An error generated by the SequeLink OLE DB Edition Client has the following format:

[INTERSOLV] [OLE DB SequeLink provider] [SequeLink 



Client]message



For ex ample:

[INTERSOLV] [OLE DB SequeLink provider] [SequeLink 



Client] Memory allocation error occurred.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions."

SequeLink Server Errors

An error generated by SequeLink Server has the following format:

[INTERSOLV] [OLE DB SequeLink provider] [SequeLink 



Server] message



For ex ample:

[INTERSOLV] [OLE DB SequeLink provider] [SequeLink 



Server] This SequeLink server service is not 



active.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions."

Database Errors

An error generated by the database has the following format:

[INTERSOLV] [OLE DB SequeLink provider] [...] 



message



For ex ample:

[INTERSOLV] [OLE DB SequeLink provider] [Oracle] 



ORA-00942:table or view does not exist.



Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.

SequeLink JDBC Driver

The SequeLink JDBC Driver reports errors to the calling application by returning SQLExceptions. Errors can be generated by the following components:

SequeLink JDBC Driver Errors

An error generated by the SequeLink JDBC Driver has the following format:

[INTERSOLV] [SequeLink JDBC Driver] message



For ex ample:

[INTERSOLV] [SequeLink JDBC Driver] Timeout 



expired.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions." Sometimes, you may need to check the last JDBC call you application made and refer to the JDBC specification for recommended action.

SequeLink Server Errors

An error generated by SequeLink Server has the following format:

[INTERSOLV] [SequeLink JDBC Driver] [SequeLink 



Server] message



For ex ample:

[INTERSOLV] [SequeLink JDBC Driver] [SequeLink 



Server] This SequeLink server service is not 



active.



Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, see Chapter 3, "Error Codes and Descriptions."

Database Errors

An error generated by the database has the following format:

[INTERSOLV] [SequeLink JDBC Driver] [...] message



For ex ample:

[INTERSOLV] [SequeLink JDBC Driver] [Oracle] 



ORA-00942:table or view does not exist.



Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.



Title | Contents | Previous | Next

SequeLink Error Codes and Messages Reference

1999, MERANT. All rights reserved.