Information Technology Reference
In-Depth Information
QuickTrace logging
The logging options discussed so far will have some form of impact on performance.
Oracle Fusion Applications has a flight recorder kind of functionality, which provides
an in-memory option for logging. This form of logging is called
QuickTrace
. With this
approach, all the log information is written to a memory buffer, which is recycled in a
circular manner.
QuickTrace is usually deployed as a rapid debugging mechanism. If a user is having a
performance issue and has enabled user-level logging, QuickTrace can be enabled to
identify what else is running at the system level. By taking this approach, the system-
wide logging does not need to be enabled.
It is important to note that QuickTrace logs information about all processes and re-
quests running on one WebLogic Server. This logging takes place for a specific time
period. Hence, it can get difficult to isolate log entries related to a particular problem.
Configuring QuickTrace
By default, QuickTrace is enabled at the
Fine
level. You can enable/disable Quick-
Trace by using the
AFLOG_QUICKTRACE_ENABLED
profile, and to increase/de-
crease the logging level, you can use the
AFLOG_QUICKTRACE_LEVEL
profile op-
tions.
Generating the QuickTrace log
Oracle dumps the QuickTrace log whenever an incident occurs, and the logfile will be
a part of the incident directory. An alternate option is to simulate the incident, which is
useful in a scenario where you are diagnosing the performance issues.
How to manually dump the QuickTrace log
To manually create a QuickTrace logfile, perform the following steps:
1.
Log
in
to
Fusion
Applications
Control
at
ht-
tp://hostname.domainname.com:port/em
.
Search WWH ::
Custom Search