Databases Reference
In-Depth Information
Setting up BAM loggers
Setting
up
BAM
loggers
with
appropriate
logging
levels
is
the
key
for
troubleshooting BAM issues.
BAM loggers can be set up to the following levels (Java logging):
SEVERE,
WARNING, INFO, CONFIG, FINE, FINER
, and
FINEST
. In a normal situ-
ation, all the BAM loggers are set to
INFO
, by default. In the case of debugging,
it is recommended to increase the level to
FINER
or
FINEST
.
Loggers contain hierarchies. You need to be careful when setting up root level
loggers to
FINE, FINER
, or
FINEST
. Suppose that you want to troubleshoot
a login issue with the BAM start page using the root logger
oracle.bam.adc
,
which is set to
FINEST
. In this case, all the descendants that inherit from it have
the same logging level. As a result, a large amount of unused log entries are pro-
duced, which is not helpful for troubleshooting, and can also impact the overall
performance. Therefore, you should set up the corresponding child logger
(or-
acle.bam.adc.security)
without enabling the root
logger.Collecting
information and debugging.
Once the problem is identified and BAM loggers are set up appropriately, it is
time to collect the logs to analyze the problem.
The following table lists the files that can be used to troubleshoot BAM issues:
Name
Description
<server_name>.out
This is the standard output file redirected by the Node
Manager. If the server is started using the
startManagedWebLogic.sh
script directly, you
need to refer to the standard output (either the com-
