You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafodion.apache.org by "Sandhya Sundaresan (JIRA)" <ji...@apache.org> on 2018/09/05 21:27:00 UTC

[jira] [Closed] (TRAFODION-1937) Trace and debug messages for tracing LOB operations

     [ https://issues.apache.org/jira/browse/TRAFODION-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandhya Sundaresan closed TRAFODION-1937.
-----------------------------------------

> Trace and debug messages for tracing LOB operations
> ---------------------------------------------------
>
>                 Key: TRAFODION-1937
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1937
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: sql-exe
>            Reporter: Sandhya Sundaresan
>            Assignee: Sandhya Sundaresan
>            Priority: Minor
>
> Use the log4cxx infrastructure to add tracing and debugging info for LOB operations. This will hhelp is debugging the numerous substeps that happen as part of any LOB operation and will help tracing where a failure  could have occurred. 
> The logging itself is controlled by an envvar .To enable 2 steps need  to be done:
> 1. set envvar TRACE_LOB_ACTIONS
> 2. In the conf/lob4cxx.trafodion.masterexe.config , uncomment the line :
> #log4j.logger.SQL.EXE=DEBUG
> The messages appear in the $MY_SQROOT/logs/master_exec<pid>.log file corresponding to the master executor  that issued the LOB related query. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)