[
https://issues.apache.org/jira/browse/TRAFODION-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wayne Birdsall resolved TRAFODION-2927.
---------------------------------------------
Resolution: Fixed
Fix Version/s: 2.3
> Keep log information for UPDATE STATISTICS in case of errors
> ------------------------------------------------------------
>
> Key: TRAFODION-2927
> URL: https://issues.apache.org/jira/browse/TRAFODION-2927
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp
> Affects Versions: 2.3
> Reporter: David Wayne Birdsall
> Assignee: David Wayne Birdsall
> Priority: Major
> Fix For: 2.3
>
>
> Presently, UPDATE STATISTICS keeps a detailed log of its internal activities
> if one has specifed "update statistics log on" in advance.
> In production scenarios, this is typically not done. That means when a
> long-running UPDATE STATISTICS command fails on a large table, one has to
> redo it with logging turned on in order to troubleshoot.
> A better practice might be to always log, and delete the log if the operation
> succeeds.
> Another issue with UPDATE STATISTICS logs is their location. The directory is
> different than other Trafodion logs and is sometimes hard to find. As part of
> this JIRA, consideration should be given to writing the logs to the Trafodion
> logs directory instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
