Troubleshooting Database Connections

From ER/Studio Data Architect
Jump to: navigation, search

Go Up to Connecting to Database Sources and Targets

Use the following checklists to resolve any connectivity problems you can encounter. Once you have confirmed your setup, if you are unable to connect please contact Embarcadero's Technical Support.

This section contains the following topics:

IBM DB2 Connectivity Checklist

  • You have configured an ODBC data source entry for each IBM DB2 database that you want to access from ER Studio Data Architect.
  • ER Studio Data Architect uses ODBC with IBM DB2 for connectivity purposes only. It does not use ODBC catalog calls; ER Studio Data Architect has complete knowledge of the DB2 system catalog.
  • You have installed the IBM DB2 Client Connection Software on your local machine
  • You have SYSADMIN, SYSCTRL, SYSMAINT or DBADM database privileges (not OS privileges) on your local machine.
  • Unlike other database platforms, local IBM DB2 data source registration requires IBM DB2 server approval.
  • Only DBADM privileges can be granted on databases using the GRANT statement. The other privileges can be assigned only through the database manager configuration.
  • Your servers have been configured in the IBM DB2 Client Configuration Assistant.
  • You have tested the connection in the IBM DB2 Client Configuration Assistant and it was a valid connection.
  • The SQLLIB\BIN subdirectory is in the Windows Path variable.
  • If you are using DBArtisan, you can see a list of servers in the server list in the Datasource Registration Wizard or in the Discover Datasource dialog box.
  • You can connect to your server through your specific client utility.
  • IBM DB2 version 5.x client utilities are installed locally. They are included on the IBM DB2 CD.
  • You have read access to SYSIBM.SYSDATABASE and SYSIBM.SYSTABLES for DB2 OS/390 SYSCAT.SCHEMATA for DB2 UDB QSYS2.SYSTABLES for AS400. You need to be able to query these tables.

Informix Connectivity Checklist

You can connect to your server through your specific client utility.

  1. You have a 32-bit Informix ODBC driver installed locally that is the correct version for the Informix server version to which you want to connect (Informix 5, Informix 7, Informix CLI for 7.2).
  2. You have 32-bit Informix SetNet installed locally and configured correctly.
  3. You have configured a data source in the ODBC Administrator using the Informix ODBC driver and pointed it to the correct SetNet information.

Interbase Connectivity Checklist

You can connect to your server through your specific client utility.

  1. You have a 32-bit InterBase 4.2 ODBC driver installed locally.
  2. You have configured a data source in the ODBC Administrator using the InterBase ODBC driver and pointed it to a valid InterBase database.

Microsoft Access Connectivity Checklist

The 32-bit Microsoft Access ODBC driver is installed locally. Search your local drives. This driver is included on the Microsoft Access media or from Microsoft website.

  1. You have configured a data source in the ODBC Data Source Administrator using the Microsoft Access ODBC driver and pointed it to your database.
  2. You are logging into your database using the Admin login ID.
  3. If your database is in a compacted mode, you have repaired the database in the ODBC setup.
  4. The database file is in standard archive mode and not locked or in read-only mode.

Microsoft SQL Server Connectivity Checklist

You can connect to your server through your specific client utility.

  1. The Microsoft SQL Server version 6.5 or 7.0 client utilities are installed locally. They are included on the Microsoft SQL Server CD.
  2. Your servers have been configured in one of the Microsoft SQL Server configuration tools, either SQL Server Client Configuration Utility or Client Network Utility.
  3. If you are using DBArtisan, you can see a list of servers in the server list in the Datasource Registration Wizard or in the Discover Datasource dialog box.
  4. For SQL Server 6.5, the following subdirectories are in the Windows Path variable: MSSQL\BIN or MSSQL\BINN and MSSQL\DLL.
  5. For SQL Server 6.5, you can ping the server from ISQLW.exe.
  6. For SQL Server 6.5, the Automatic ANSI to OEM and Use International Settings options are selected in the DBLibrary tab of the Microsoft SQL Client Configuration Utility.
  7. For SQL Server 7.0, the MSSQL7 subdirectory is in the Windows Path variable.
  8. For SQL Server 7.0, the Automatic ANSI to OEM Conversion and Use International Settings options have been selected in the DB Library Options tab of the Client Network Utility.

Oracle Connectivity Checklist

You can connect to your server through your specific client utility.

  1. Your servers have been configured in one of the Oracle configuration tools: SQL*Net Easy Config, Net8 Easy Config or Net8 Configuration Assistant.
  2. If using Net8 Easy Config or Ne8 Configuration Assistant, you can ping the server.
  3. One of the following subdirectories is in the Windows Path variable: ORANT\BIN, ORAWIN95\BIN, ORAWIN\BIN, ORA81\BIN.
  4. A least one of the following libraries in the Oracle home BIN directory: Ora73.dll, Ora803.dll, Ora805.dll or Oran8.dll.
  5. The Oracle client configuration tool points to the correct TNSNAMES file: TNSNAMES.ora. If you are using DBArtisan, you can see a list of servers from your TNSNAMES file in the Server drop-down list in the Datasource Registration Wizard or in the Discover Datasource dialog box.

Sybase Connectivity Checklist

Sybase client utilities version 11.x are installed locally. Search your local drives as it is included on the Sybase media.

  1. The Sybase network library LIBSYBDB.dll is installed locally.
  2. Your servers have been configured in one of the Sybase configuration tools: SQLEDIT or DSEDIT.
  3. You are can ping the server from either SQLEDIT.exe and SYBPING.exe or DSEDIT.exe.
  4. The following subdirectories are in the Windows Path variable: SYBASE\BIN and SYBASE\DLL.
  5. If you are running Windows 95 or 98, the Autoexec.bat file is calling the SYBSET.bat file.
  6. If you are running Windows NT, the Sybase System Environment Variable (Control Page\ System\Environment) points to only one Sybase directory.
  7. If you are using the 16-bit Open Client Software, it is installed in the same directory as the 32-bit Open Client.
  8. The Sybase client configuration tool points to the correct SQL.ini file. If you are using DBArtisan, you can see a list of servers from your SQL.ini file in the Server drop-down list in the Datasource Registration Wizard or in the Discover Datasource dialog box.

See Also

Retrieved from "https://docwiki.embarcadero.com/ERStudioDA/XE5/e/index.php?title=Troubleshooting_Database_Connections&oldid=2781"