Using the ttTraceMon Utility
Use the ttTraceMon utility to log various trace information on a number of TimesTen components. Each TimesTen component can be traced at different levels of detail. You can list all of the traceable TimesTen components and their current tracing level by specifying ttTraceMon with the show subcommand. See ttTraceMon in the Oracle TimesTen In-Memory Database
Reference for a list of options.
TimesTen tracing severely impacts application performance and consumes a great deal of file system space if trace output is directed to a file. In addition, when using AWT cache groups, you must restart the replication agent when trying to trace the ORACON component with ttTraceMon. Use the ttTraceMon utility only when diagnosing problems. When you are finished, reset tracing to the default values.
This example shows that the levels for most tracing components are set to level 0 (off) for the database1 database. Both the ERR and DEADLOCK components are set to 1 for tracing by default. See ERR Tracing for information.
% ttTraceMon -e show database1 AGING ... 0 API ... 0 ASYNCMV ... 0 AUTOREFRESH ... 0 BULKLOAD ... 0 BLK ... 0 CG ... 0 CKPT ... 0 DBG0 ... 0 DBG1 ... 0 DEADLOCK ... 1 DIST ... 0 EE ... 0 ERR ... 1 EXTTBLLOAD ... 0 FLOW ... 0 GRID ... 0 GRIDAS ... 0 HEAP ... 0 INTERRUPT ... 0 IX ... 0 IXGC ... 0 IXHEAP ... 0 LATCH ... 0 LBCU ... 0 LOB ... 0 LOCK ... 0 LOG ... 0 LOGF ... 0 MEM ... 0 ODBC ... 0 OPT ... 0 ORACON ... 0 PLOAD ... 0 PREP ... 0 PT ... 0 REPL ... 0 SM ... 0 SQL ... 0 TEST ... 0 TRACE ... 1 XA ... 0 XACT ... 0 XLA ... 0
The output for most TimesTen components is only of interest to TimesTen Customer Support. However, the output for the SQL, API, LOCK, ERR, AGING and AUTOREFRESH components may be useful to you when you are troubleshooting application problems.
The rest of this section includes the following topics: