Troubleshooting Database Connections for 32 bits Version

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 IDERA's Technical Support.

This section contains the following topics:

IBM DB2 Connectivity Checklist

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

  • Install the IBM DB2 Client Connection Software on your local machine.
  • Install locally the IBM DB2 client utilities. They are included on the IBM DB2 CD.
  • Configure 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 need to have SYSADMIN, SYSCTRL, SYSMAINT or DBADM database privileges (not OS privileges) on your local machine. Only DBADM privileges can be granted on databases using the GRANT statement.
    The other privileges can be assigned only through the database manager configuration.
  • Unlike other database platforms, local IBM DB2 data source registration requires IBM DB2 server approval.
  • Configure your servers in the IBM DB2 Client Configuration Assistant.
  • Test the connectivity in the IBM DB2 Client Configuration Assistant. You need to be able to connect to your server through your specific client utility.
  • The SQLLIB\BIN subdirectory is in the Windows Path variable.
  • You need to have read access to SYSIBM.SYSDATABASE and SYSIBM.SYSTABLES for DB2 z/OS SYSCAT.SCHEMATA for DB2 UDB QSYS2.SYSTABLES for AS400. You need to be able to query these tables.
  • 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.

Informix Connectivity Checklist

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

  • Install 32-bit Informix ODBC driver locally.
  • Install and configure 32-bit Informix SetNet locally.
  • Configure a data source in the ODBC Administrator using the Informix ODBC driver and point it to the correct SetNet information.

Interbase Connectivity Checklist

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

  • Install a 32-bit InterBase ODBC driver locally.
  • Configure a data source in the ODBC Administrator using the InterBase ODBC driver and point it to a valid InterBase database.

Microsoft Access Connectivity Checklist

  • Install 32-bit Microsoft Access ODBC driver locally.
  • Configure a data source in the ODBC Data Source Administrator using the Microsoft Access ODBC driver and point it to your database.
  • Log into your database using the Admin login ID.
  • Repair the database in the ODBC setup if it is in a compacted mode.
  • Make sure the database file is in standard archive mode and is not locked or in read-only mode.

Microsoft SQL Server Connectivity Checklist

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

  • Install Microsoft SQL Server client utilities locally. They are included on the Microsoft SQL Server CD.
  • Configure your server in one of the Microsoft SQL Server configuration tools, either SQL Server Client Configuration Utility or Client Network Utility.
  • 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.

Oracle Connectivity Checklist

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

  • Configure your server in one of the Oracle configuration tools: SQL*Net Easy Config, Net Easy Config or Net Configuration Assistant.
  • If you are using Net Easy Config or Net Configuration Assistant, ping the server.
  • Check the Windows Path variable. One of the following subdirectories is in it: ORANT\BIN, ORAWIN95\BIN, ORAWIN\BIN, ORA81\BIN.
  • Check 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

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

  • Install 32-bit Sybase client utilities locally.
  • For Sybase ASE 15.5, go to from cmd to the path C:\Sybase\OCS-15_0\scripts and run command: "copylibs.bat create" before setting up the connection to the server in the Open Client Directory Service Editor(dsedit.exe).
  • Check that the Sybase network library LIBSYBDB.dll is installed locally.
  • Configure your servers in one of the Sybase configuration tools: SQLEDIT or DSEDIT.
  • Check that you can ping the server from either SQLEDIT.exe and SYBPING.exe or DSEDIT.exe.
  • Check the Windows Path variable. The following subdirectories are in it: SYBASE\BIN and SYBASE\DLL.
  • Check that 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 "http://docwiki.embarcadero.com/ERStudioDA/184/e/index.php?title=Troubleshooting_Database_Connections_for_32_bits_Version&oldid=5268"