Cannot Connect to the TimesTen Server

You have not correctly identified the system where the TimesTen Server is running.

On a Windows client, select the TimesTen Server in the TimesTen Data Source Setup dialog that is displayed as part of the ODBC Data Source Administrator. To verify the TimesTen Server:

  1. On the Windows Desktop, choose Start > Settings > Control Panel.
  2. Double click the ODBC icon. This opens the ODBC Data Source Administrator.
  3. Click the System DSN tab. This displays the System Data Sources list.
  4. Select the TimesTen Client data source. This opens the TimesTen Client DSN Setup dialog.
  5. Click Servers. This opens the TimesTen Logical Server List.
  6. Select the TimesTen Server from the list. This opens the TimesTen Logical Server Name Setup dialog.
  7. Verify that the values for the Network Address and Port Number are correct. If necessary, change the values.

    Note:

    If you typed the host name or network address directly into the Server Name field of the TimesTen Client DSN Setup, the Client tries to connect to the TimesTen Server using the default port.

If the Network Address and Port Number values are correct, the TimesTen Server may not be running. In the Oracle TimesTen In-Memory Database Operations Guide, see Testing Connections for more information about identifying this problem.

On Linux and UNIX, specify the TimesTen Server with the TTC_Server connection attribute in the odbc.ini file on the client. If the value specified for TTC_Server is an actual host name or IP address, the client tries to connect to the TimesTen Server using the default port. In TimesTen, the default port is associated with the TimesTen release number. If the value specified for TTC_Server is a logical Server Name, this logical Server Name must be defined in the ttconnect.ini file. The ttconnect.ini entry for this Server Name must correctly define the host name/IP address and port number on which the TimesTen Server is listening.

If the Network Address and Port Number values are correct, the TimesTen Server may not be running or did not start. See Testing Connections in the Oracle TimesTen In-Memory Database Operations Guide for more information about identifying this problem.