How to Limit JDBC Logging Output (Doc ID 944655.1)

Last updated on MARCH 08, 2017

Applies to:

JDBC - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Goal

How do you limit JDBC logging output?

1. Purpose

The purpose of this article is to provide techniques for limiting JDBC logging output. That is its only purpose.

It is not the intent of this article to show how to use JDBC logging. For instructions on how to use JDBC logging, see the white paper "Oracle JDBC Logging using java.util.logging" at http://www.oracle.com/technetwork/database/enterprise-edition/11-2.pdf

2. Prerequisite

Before using this article you must know how to use JDBC logging and obtain output from it.

3. When to use this article

When the problem for which you wish to obtain JDBC logging occurs intermittently and/or occurs only on an application running in an application server, one or more of the technique in Solution sections 4 to 9 may be needed to handle the large volume of logging.

These techniques are not usually needed when the problem can be reproduced consistently with a standalone java application since there is less logging output.

4. How to use this article

For most of the techniques, you will likely need to try the technique, carefully doing each step, possibly more than once, in order to understand how they work. Do not expect to master the techniques by just reading the article.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms