What problem are you observing?
The Documentation for the JDBC Connector does not mention that the SQL cannot end with a semicolon. Having a Semicolon at the end of the SQL Statement will cause a general error message to appear, which does not provide any details about the cause without contacting SailPoint Professional Services to have them decode the error TraceId.
Query Documentation that could use a note: https://documentation.sailpoint.com/connectors/jdbc/help/integrating_jdbc/account_query_settings.html
Schema Attribute details that could use a note about this: https://documentation.sailpoint.com/connectors/jdbc/help/integrating_jdbc/schema_attributes.html
Aggregating the Schema - Could use a note that if an error occurs, to check that the query does not have a semicolon at the end: https://documentation.sailpoint.com/connectors/jdbc/help/integrating_jdbc/account_schemas.html
Schema Documentation that could use details of both the Discover Schema option and reference to this issue: https://documentation.sailpoint.com/saas/help/accounts/schema.html
What is the correct behavior?
The documentation should mention this limitation so user do not make this mistake. Additional details would be helpful for Discover Schema in the general documentation as well.
What product feature is this related to?
JDBC Direct Connector for IdentityNow, however it might also be the same for IIQ.
What are the steps to reproduce the issue?
Create a JDBC Direct Connector source
Configure the basic details
Add an account SQL Query and include the semicolon at the end of it.
Save it and then attempt to do the “Discover Schema” action
Notice there is an error that pops up.
Do you have any other information about your environment that may help?
Tested with an Oracle DB.