I switch from direct mode to spice mode
The error I got is :
“Your database generated a SQL exception. This can be caused by query timeouts, resource constraints, unexpected DDL alterations before or during a query, and other database errors. Check your database settings and your query, and try again.”
need to resolve this , I cannot see any data in my visual
Can anyone please help me to fix this?
Hi @priyanka1
The error message you are encountering when switching from direct query mode to SPICE mode indicates that there is likely an issue with how the query or data is being handled in the SPICE dataset. Here are some steps to troubleshoot and resolve the issue.
Ensure that the data source and the tables involved haven’t been modified (like schema changes) since creating the dataset. Any DDL (Data Definition Language) changes, such as altering table structure or dropping tables, can cause this error.
SPICE has certain resource limits, and complex queries (involving joins, subqueries, or large datasets) may exceed those limits. Review your dataset’s query structure and consider simplifying it if possible.
If possible, reduce the dataset size or number of columns by excluding unnecessary fields.
Sometimes, refreshing the dataset or re-importing it into SPICE can resolve issues. Go to Datasets and select Refresh Now for the problematic dataset. If this doesn’t work, try editing and save the dataset or deleting the dataset and re-creating it from scratch.
Verify that the data source is reachable and that any credentials, permissions, or firewall settings are configured correctly. Sometimes, database connection issues can lead to failed queries.
If your data source allows, try increasing the query timeout limit. In cases where the database queries take longer, the default timeout settings may not be sufficient.
If you have access to your database logs, check for any errors or warnings during the query execution time. It can give insights into whether there are resource constraints, locks, or other issues that might have caused this exception.
Please refer the below documentation this might be helpful for you.
Hi @priyanka1,
It’s been awhile since we last heard from you. Did you have any additional questions regarding your initial topic or was Xclipse’s response helpful for your case?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Thank you!
Hi @priyanka1,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for any relevant information that may be needed.
Thank you!