Execution Trace Information¶
When executing a query using the Administration tool, you can see a graphical representation of the execution trace of the query, by clicking the button View execution trace.
The following tables explain the meaning of the information provided by the trace:
- Icons of the execution trace and their meaning provides the meaning of the icons displayed in the execution trace.
- Color code of the nodes of the execution trace provides the meaning of the color of the trace’s nodes.
- Values of the “State” attribute of the nodes of a query’s execution trace lists the possible values of the attribute “State” of the trace’s nodes.
|Void. This branch of the execution plan has not been executed.|
|Intermediate results were swapped to disk|
|Data was obtained from the cache of the view.|
The node has additional information such as:
|Virtual Plan: node that appears in the execution trace when the execution of a derived view is entirely pushed down to the data source.|
|Root node of
|Data Movement. It indicates that the data obtained from a view has been “temporary” inserted into another data source. The section Data Movement explains the Data Movement optimization.|
|and||JDBC data source and base view|
|and||ODBC data source and base view|
|and||Multidimensional data source|
|and||Web service data source|
|and||XML data source|
|and||JSON data source|
|and||DF data source|
|and||WWW data source (ITPilot)|
|and||LDAP data source|
|and||Google Search data source|
|and||BAPI data source (SAP ERP)|
|and||Custom data source (Custom wrapper)|
The following table lists the possible values of the attribute “State” of the nodes of a query’s execution trace.
|INIT||The query has started, but the node has not begun processing any result.|
|PROCESSING||The node is currently processing results generated by the nodes below.|
|STOPPED||The execution was cancelled by the user.|
|OK||The execution of the node finished correctly.|
|ERROR||There was an error during the execution of the query.|
The Server requested a thread to the Threads Pool, but the timeout was reached before obtaining one.
You can increase the timeout of the threads in the “Thread Pool” dialog of the “Administration > Server configuration” menu.
The Server has reached the maximum number of threads.
You can increase the maximum number of threads in the “Thread Pool” dialog of the “Administration > Server configuration” menu.
|PARSE_ERROR||There was an error while parsing the input data. E.g., the query involves a JSON base view and the input JSON document is not well formed.|
|INVALID_ROUTE||The connection details of the data source are not valid.|
|CONNECTION_ERROR||There was an error while trying to connect with the source. E.g., the view queries a Web service base view and the Web service server cannot be reached.|
The query reached the timeout.
All the clients of the Virtual DataPort server establish a timeout for the queries. That applies to clients that connect to Virtual DataPort via JDBC and ODBC and to the Administration Tool.
To change the query timeout of the Administration Tool, open the “Connection” tab of the “Tools > Admin Tool preferences” menu.
Read the sections “Access through JDBC” and “Access through ODBC” of the Developer Guide to know how to change the query timeout of JDBC or ODBC clients.
|LICENSE_QUERY_TIMEOUT||The query reached the timeout set by the current license of the Denodo Platform.|
|ROW_LIMIT_REACHED||The execution finished correctly but
not all the rows of the result set
have been returned. That is because
the query contains the
|ENOUGH_ROWS_RETRIEVED||The node was stopped because no more rows from this node were needed to complete the request.|
|INTERFACE_NOT_IMPLEMENTED||The query failed because the query involves an interface view that does not have an implementation view assigned.|
|INCOMPATIBLE_QUERY_VIEW||The node was not executed because the simplification engine detected that the selected query will not return results|
|CACHE_LOAD_ERROR||The cache load process finished with error|