Troubleshooting the Hyper-Q Installation
The Hyper-Q installation troubleshooting topics provide solutions to problems that you might encounter during the Hyper-Q deployment process.
For support FAQs and troubleshooting information, visit the Datometry Help Center at: https://support.datometry.com/
Collecting Log Files for Troubleshooting a Hyper-Q Installation
Hyper-Q logs critical startup messages as well as errors at runtime to the file error_log-date_time.csv located in the directory /opt/datometry/logs.
At startup and at midnight a new log file is created with the current date and time as part of the filename.
Hyper-Q Fails to Start
Hyper-Q will fail to start for the following reasons.
Missing license file
Copy a valid license file to /opt/datometry/config/dtm.lic.
Duplicate license file
Ensure only one file ending in .lic is located in /opt/datometry/config.
Expired license
If your Hyper-Q license is expired:
Request a new license file from Datometry Support.
Ensure the new license has not expired by inspecting the file, then install the license file.
To learn more, see Install the Hyper-Q License File.
Client Cannot Connect to Hyper-Q
If your client cannot connect to verify that the endpoint is correctly configured.
Ensure the database name and port configuration in the [endpoints] section of the file /opt/datometry/config/dtm.ini is correct.
Client Connects to Hyper-Q but Cannot Connect to the Database
The connection to the database instance is not configured correctly.
Ensure database name and port configuration in the [gateways] section of the file /opt/datometry/config/dtm.ini is correct.
The Metadata Store is Not Accessible
If the Metadata Store is not accessible, the client receives the error “DTM5306: Invalid MDStore table”.
Ensure that the database, username, and password configuration in the [metadata_stores] section of the file /opt/datometry/config/dtm.ini is correct, and that the credentials being used can access Metadata Store in Azure Synapse.
Unassigned Metadata Store Permissions
If permissions have not been assigned to Metadata Store, queries involving the catalog (Information Schema, DBC) will fail.
Grant SELECT permissions on the Metadata Store schema to PUBLIC. See Create a Dedicated User to Access Metadata Store.
Data Encryption Enabled
Either the client cannot log in the database or executing queries on the session fails with “Cannot call a method on closed connection” or a similar error message.
Ensure the client is not requesting data encryption.