Troubleshooting MySQL collector issues
Collector runtime and troubleshooting
The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.
If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.
A list of common issues and problems encountered when running the collectors is available here.
Issue 1: Harvested metadata is missing table descriptions
Cause: Some versions of the MySQL JDBC driver require a specific property to be set in the collector configuration to harvest table descriptions.
Solution: In the collector configuration, for cloud collector, set a JDBC property as name: useInformationSchema and value: true and for on-premise collector, set --jdbc-property=useInformationSchema=true. Rerun the collector to verify if it now harvests the missing table descriptions.