Troubleshooting Analytics Support
Monitoring Analytics Server
The SQL CLI is recommended for troubleshooting analytics connection and configuration issues.
Launch the CLI in debug mode:
./presto --server <local-ip OR localhost>:8989 --debug
Checking Analytics Server Status
In the debug CLI, run the following system queries:
SHOW SCHEMAS FROM system; SHOW TABLES FROM system.runtime;
If these queries work correctly, your analytics-gateway and analytics system are up and functioning correctly.
If you do not see results from these queries, you should verify your analytics configuration.
Troubleshooting Configuration Issues
If you encounter a
schemaName is null error when using the CLI,
you may have a catalog or metaschema configuration issue.
Run the following query in the debug CLI:
SELECT * FROM system.metadata.catalogs;
The results of this query will include all catalogs that are available in the
analytics system. You should see your catalog
listed in the results. If you do not, you should ensure that you have
synced your catalog properties file correctly. Be sure
that you have run sync with the correct directory structure (a
catalog and a
Another possible cause of this error is that your metaschema file is not properly formatted edn or is not correctly located. Also, verify that your metaschema file ends with a .edn extension.
If you are able to connect using your catalog and schema, but don't see your expected tables, you likely have a misconfiguration of your metaschema file.
Metaschemas are dynamically associated with Datomic databases and errors or typos in metaschemas can prevent association, resulting in the lack of any Presto tables.
Start the SQL CLI with your catalog and schema names and run the following:
You should see at least two tables:
db__attrs, which are both automatically generated
for any Datomic database.
You can examine the contents of these tables with:
SELECT * FROM db__idents; SELECT * FROM db__attrs;
The contents of these tables indicate the attributes and idents that Datomic analytics was able to read
from your Datomic database. If you do not see any additional tables, your metaschema does not match the
schema of this Datomic database. Ensure that all attributes listed in your metaschema file exist in your
Datomic database (or in the two
db__ tables in Presto) and that you have not accidentally mistyped or
included an attribute that is not present in your database.