3 Configuring Logging

This chapter includes the following sections.


3.1 Oracle GoldenGate Java Adapter Default Logging

Logging is set up by default for the Oracle GoldenGate Adapters.

3.1.1 Default Implementation Type

The default type of implementation for the Oracle GoldenGate Adapters is the jdk option. This is the built-in Java logging called java.util.logging.

3.1.2 Default Message Logging

The default log file is created in the standard report directory. It is named for the associated Replicat process. Problems are logged to the report file and the log file.

3.1.3 Log File Name

By default log files are written to the installation_directory/dirrpt directory. The name of the log file includes the Replicat group_name and it has an extension of log.

3.1.4 Logging Problems

An overview of a problem is written to the Replicat Report file and the details of the problem are written to the log file.

3.2 Recommended Logging Settings

Oracle recommends that you use log4j logging instead of the JDK default for unified logging for the Java user exit. Using log4j provides unified logging for the Java module when running with the Oracle GoldenGate Replicat process.

3.2.1 Changing to the Recommended Logging Type

To change the recommended log4j logging implementation, add the configuration shown in the following example to the Java Adapter Properties file.


The gg.log level can be set to none, error, warn, info, debug, or trace. The default log level is info. The debug and trace log levels are only recommended for troubleshooting as these settings can adversely affect performance.

The result is that a log file for the Java module will be created in the dirrpt directory with the following naming convention:

<process name>_<log level>log4j.log

Therefore if the Oracle GoldenGate Replicat process is called javaue, and the gg.log.level is set to debug, the resulting log file name is: