Page History

Table of Contents
maxLevel 4 indent 20px

...

Logs for SeaQuest processes are found in $MY_SQROOT/logs (soon to be renamed $TRAFin $TRAF_HOME/logs). You can get there using the “cdl” command from a trafodion logon. If you are debugging UPDATE STATISTICS by using the "update statistics log on" SQL statement, the log for that will be written to the ~/sqllogs directory (where ~ is the "trafodion" user) on the node where the master executor is running. If you are using trafci, you’ll have to hunt for the node where your mxosrvr is running. (See details on how to do that above.) If you are using sqlci, it is on the node where you are running sqlciNote that there is one of these directories per node in the cluster. If you know which node your process of interest is running on, you can go directly to that node.

For many uses, a single log file is kept per node. For example, all C++ SQL compiler and executor logic on a given node writes to the file trafodion.sql_0.log. Similarly, Java SQL compiler and executor logic write to trafodion.sql.java.log.

UPDATE STATISTICS behaves a bit differently. Its logging is very chatty. So, in normal operation a log file is generated for each command, and deleted on completion if there were no severe errors in that command. If there was a severe error (e.g. 9200, internal error), then the log is kept. This behavior can be changed using UPDATE STATISTICS LOG OFF (in which case no log is generated) or UPDATE STATISTICS LOG ON (in which case a log is kept for the life of the process). Log files for UPDATE STATISTICS have file names of the form ustat.[node number].[Linux pid].[timestamp].txt.

Scripts

Scripts can be found in the $MY_SQROOT/sql/scripts (soon to be $TRAF_HOME/sql/scripts). You can ge there using the “cds” command from a trafodion logon.

...