I cannot connect successfully with a client application

Early stage - no specific error message in client

If connecting with a client application fails in an early stage, Hyper-Q cannot deliver an error message to the client application. It is necessary to consult Hyper-Q's log file for details on the error. The most common errors causing connection attempts to fail early are:

  • missing or invalid license: look for errors in the log file pertaining to licenses and ensure a valid license is installed
  • misconfiguration: Hyper-Q is not listening to the expected port (e.g., 1025 default for Teradata); look for "Connection Server starting up on NNNN" in the log file and ensure that NNNN is the expected port
  • unsuccessful startup: Hyper-Q was not able to start up successfully; ensure no errors are printed when starting up Hyper-Q

Later stage - specific error message in client

If connecting with a client application fails in a later stage, Hyper-Q will send the error message to the client application. The most common errors causing connection attempts to fail in a later stage are:

  • invalid credentials: Hyper-Q passes credentials provided by the client application to the downstream database for authentication; ensure the credentials are valid for authenticating with the downstream database
  • unable to establish connection to downstream database (see also specific error message):
    • the downstream database is not available: check that the downstream database is up an accepting connections
    • the downstream database cannot be reached: ensure that Firewalls are configured to pass traffic between the Hyper-Q host and the database
    • the ODBC driver cannot be loaded successfully: ensure the ODBC driver for the downstream database is correctly installed and can be used to connect to the downstream database using the desired credentials
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.