[
https://issues.apache.org/jira/browse/TRAFODION-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wayne Birdsall resolved TRAFODION-1714.
---------------------------------------------
Resolution: Fixed
Changed the code to use SQL_EXEC_Prepare + SQL_EXEC_ExecFetch with a printPlan
call in-between, instead of SQL_EXEC_ExecDirect with the printPlan call
afterward.
> ULOG debugging tool does not capture query plan until after execution
> ---------------------------------------------------------------------
>
> Key: TRAFODION-1714
> URL: https://issues.apache.org/jira/browse/TRAFODION-1714
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp
> Affects Versions: 2.0-incubating, 1.3-incubating
> Environment: All
> Reporter: David Wayne Birdsall
> Assignee: David Wayne Birdsall
> Fix For: 2.0-incubating
>
>
> ULOG is a diagnostic feature that we use when debugging problems with the
> UPDATE STATISTICS utility. It logs various information about the code paths
> and decisions taken by the utility during the course of its execution. One
> useful thing it does is to dump the query plans of any queries that it
> executes. Unfortunately, for the Sample Table load query, the plan isn't
> dumped until after execution completes. This is a problem because sometimes
> (due to other issues) that load query doesn't complete. So the query plan
> doesn't get logged in this case, forcing us to use other diagnostic methods
> to obtain this information. We would improve the ability to support Trafodion
> by dumping the query plans before execution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
