All Collections
ETO Results 4.3
Fixing Errors
SQL Error when Running Report
SQL Error when Running Report

#Results #Errors

Updated over a week ago

What is a SQL Error and How Can I Remove it?


What is a SQL error and how can I remove it?


The "SQL is not ready" error is a generic error that Webi presents when it does not have a specific description of an error it is experiencing. It can be quite difficult to narrow down the specific cause.

If the error occurs prior to the refresh prompt, causes in Group A (see below) are more likely.
If the error occurs after the report has been refreshed, causes in Group B (see below) are more likely.

When testing for an error, be sure to follow these steps:

Step 1 – Make changes to the report

Make changes to the report and save it before proceeding to the next step.

Step 2 – Save the report

Save the report and close it completely.

Step 3 – Close the report completely

Close the report completely, by either clicking the 'X' in the top corner or by going to File > Exit.

Step 4 – Re-run the report in View mode (do not edit or “Modify” when opening)

Run the report in view mode to see if the error still appears. To run in view mode, go to File > Run > Run in View Mode.

If the SQL error does not return, you have resolved the problem! If it does, continue looking for issues following these guidelines. Please contact Customer Support if you need more information or additional assistance.

Group A

Potential Cause: Re-Query source that returns NULL data

Solution: Reconstruct the Filtering so that some data returns, ensuring that the re-Query data retrieval is not NULL.

Potential Cause: Incompatible Filters in a Query (for example: the Caseload Filter with a TouchPoint Filter)

Solution: Remove one Filter at a time and run again. If there is an incompatibility, register this with Customer Support.

Potential Cause: Null simple Filter

Solution: When the simple Filter has been enabled, ensure the Object in place returns some values (no NULL value).

Potential Cause: Multiple changes to the Query structure of the report including deleting/adding Queries, changing Result Objects, etc.


Group B

Potential Cause: Use of variables that combine elements from different Queries without appropriate merging

Solution: While Webi typically disallows this type of construction, loopholes exist in which it can still occur. A table should only contain either Objects from a single Query, Objects from a single Query combined with merged Objects/Details, or merged Objects and Details only.

Be sure that you have Merged Dimensions (typically [Subject Unique Identifier], [Participant Site Identifier], or [Response ID]). Each of these has a companion Object that it can be merged with.

Potential Cause: Too much or incorrect relative positioning

Solution: Relative positioning is used to position one table or block “relative” to another one or to the top, bottom, or sides of the report or section. Too many of these can cause page corruption. Also, blocks that are all positioned relative to the top or bottom of the report or section are problematic. Be sure to position blocks relative to the Objects directly around it rather than relative to the top of the page.

Potential Cause: Formulas that don't match a Webi syntax

Solution: While Webi may accept formula syntax that is not specified in the Help Manual, this has been known to cause SQL errors. Be sure to check the Help Manual from the Variable Editor (click on the function, then “More on this Topic” button) to ensure you are using the recommended syntax.

Group A or B

No identified cause:

Solution: If you cannot narrow down the error, we recommend rebuilding the report, and checking for errors after each addition to the Report Objects and Query Filter.

Did this answer your question?