Databases Reference
In-Depth Information
Apart from logging, it is also important to have the proven methodologies in
place, so that you can follow these methods/procedures to conduct your
troubleshooting practice.
In this section, you will learn the following topics:
•
Understanding BAM logging concepts
•
Understanding the methodologies for troubleshooting
Understanding BAM logging concepts
BAM provides a set of loggers, which are associated with BAM Java packages/
classes. Like Java, these loggers are named by following the dot convention,
and are organized hierarchically.
Let's take a look at an example.
oracle.bam.adc
is the root logger for
the Active Data Cache. All the loggers for the sub-modules within the Active
Data Cache should be named after
oracle.bam.adc
, and therefore become
descendants of the root logger. For instance,
oracle.bam.adc.security
,
which is the logger that tracks Active Data Cache security logs, is the child log-
ger of
oracle.bam.adc
.
The logging level for the descendant/child (for example,
or-
acle.bam.adc.security)
inherits from the ancestor/par-
ent (for example,
oracle.bam.adc)
by default, unless its
logging level is explicitly specified. Thus, you should be care-
ful when setting a root or parent logger to a low level (for ex-
ample,
TRACE:32)
, which may produce a large amount of
log entries in the
log
file.
