English

Problem: Unsuccessful connections to a DBMS across platforms

Solution or Workaround

What are the possible causes of unsuccessful connections to a DBMS on another platform, and what methods can be used to diagnose the problem?

Answer:

ESRI certifies peer-to-peer connectivity (connection between two systems of the same type). Non-peer-to-peer connection failures are usually related to the DBMS connection code from the DBMS vendor.

1) Test the connection with the connectivity tools provided by the DBMS vendor (ex. SQL*Plus or Isql). If this connection is successful, the ArcInfo connection should also work. If the connection using the vendor's connectivity product fails, contact the DBMS vendor's technical support for assistance.

2) If the connection using the vendor's connectivity product is successful, and the ArcInfo connection fails, ESRI will need to contact the DBMS vendor to resolve the issue.

For example, to connect an ArcInfo client running on a Sun workstation to Oracle on a Mac, first test the connection with Oracle's SQL*Plus product. If the connection works, the ArcInfo connection should work as well. If it does not, ESRI needs to get a library patch from Oracle which will compile with the development version of ArcInfo.

Notes:

Please note that ESRI only certifies peer-to-peer connectivity (connection between two systems of the same type) for the supported DBMS revisions listed in the 'Installing ArcInfo Guide'.

ESRI does not certify non-peer-to-peer connection, or connections to unsupported DBMS revisions. There is no guarantee that these types of connections will work, and attempting such connections is the client's own responsibility.