Trouble-shooting Client Setup
Go Up to Datasource and Server Management
If you are using native Idera drivers to connect to a datasource, improperly configured client software can lead to the following symptoms:
- Failure to Auto-Discover accessible datasources.
- Inability to properly register a datasource
- Failure to manually connect to a registered datasource
- Error messages indicating missing client software files
- Note: For details on the various ways to register and connect to datasources, see Datasource and Server Management.
Regardless of the DBMS platform, your first step in trouble-shooting client connectivity is to ensure that your client is specified in the PATH environment variable.
For DBMS-specific help:
- Trouble-shooting Sybase Connectivity
- Trouble-shooting Oracle Connectivity
- Trouble-shooting DB2 LUW and DB2 z/OS Connectivity
- Trouble-shooting SQL Server Connectivity
Trouble-shooting Sybase Connectivity
A common cause of client connectivity issues against a Sybase DBMS is the client on the workstation not being compatible with Rapid SQL or the Sybase environment on your workstation not being configured properly.
Verify that your Sybase environment variables have been set properly on your workstation. If you make any changes, restart Rapid SQL
Ensure you at least have the following variables (Environment Variables accessible through the Control Panel):
LIB - ensure that the Sybase LIB directory is listed here
INCLUDE - ensure that the Sybase INCLUDE directory is listed here
Verify that the PATH value has only ONE SET of Sybase directories listed. You can modify this from the same Environment Variable window above in the PATH value:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM;C:\PROGRA~1\Serena\vm\win32\bin;C:\PROGRA~1\Serena\vm\common\bin\win32;C:\oracle\ora92\bin;C:\oracle\ora92\jre\1.4.2\bin\client;c:\sybase\OCS-15_0\lib3p;c:\sybase\OCS-15_0\dll;c:\sybase\OCS-15_0\bin;c:\sybase\DataAccess\ADONET\dll;c:\sybase\DataAccess\OLEDB\dll;c:\sybase\DataAccess\ODBC\dll;c:\sybase\Shared\Sybase Central 4.3;c:\sybase\ua\bin;C:\Program Files\Internet Explorer;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
In order to use the Auto-Discover feature, a valid SQL.ini file must be located in the following location:
Where the version_identifier_directory is the name of the release-specific directory associated with this purpose, such as OCS-15_0 or OCS-12_5.
Trouble-shooting Oracle Connectivity
An Oracle client must be installed on the workstation. It must be defined/specified in the following locations:
- The ORACLE_HOME in the Windows Registry
- The Environment PATH value
In addition, in order for the Auto-Discover feature to work, there must be a valid Oracle tnsnames.ora and sqlnet.ora file in the Oracle client installed. They must be installed in the
%Oracle_home\Network\Admin directory. As well, the sqlnet.ora file must have the NAMES.DIRECTORY_PATH value of TNSNAMES.
A typical sqlnet.ora file:
# sqlnet.ora Network Configuration File:
# Generated by Oracle configuration tools.
# This file is actually generated by netca. But if customers choose to
# install "Software Only", this file wont exist and without the native
# authentication, they will not be able to connect to the database on NT.
SQLNET.INBOUND_CONNECT_TIMEOUT = 30
SQLNET.SEND_TIMEOUT = 30
SQLNET.RECV_TIMEOUT = 30
Trouble-shooting DB2 LUW and DB2 z/OS Connectivity
The client must be defined in the workstation PATH value.
In order to Auto-Discover or manually register DB2 datasources, they must be configured in the DB2 Configuration Assistant. If DB2 datasources are not being detected, have your DBA provide a Configuration Assistant profile.
Trouble-shooting SQL Server Connectivity
In general, SQL Server datasources rarely go undetected. Each database server sends out a ping (via a service) to the network and Rapid SQL is usually able to find this. The SQL Server client must be defined in the workstation PATH value.