Early Stage: No Specific Error Message via Client Application
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 Application
If connecting with a client application fails in a later stage, Hyper-Q sends 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):
- Downstream database is not available: Verify that the database is up an accepting connections.
- Downstream database cannot be reached: Ensure that firewalls are configured to pass traffic between the Hyper-Q host and the database.
- 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.