4 Configuring Logging

This chapter describes the default logging for the Oracle GoldenGate Adapters and explains how to configure a different logging option.

4.1 Application Adapters Default Logging

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

4.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 (JUL).

4.1.2 Default Message Logging

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

An overview of a problem is written to the Extract Report file and the details of the problem are written to the log file. Log File Name

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

4.2 Changing the Default Logging

The logging for Oracle GoldenGate Adapters can be changed from JUL to another type, debug can be turned on, and the configuration file can be specified.

4.2.1 Changing the Logging Type

The Java-based logging utility, Log4,j is the preferred method of logging for Oracle GoldenGate Application Adapters.

To change the logging implementation type, set the gg.log property to log4j or logback. For example set:


4.2.2 Changing the Logging Configuration

To designate a specific configuration file, set jvm.bootoptions to the system property that defines it. This will implicitly set the implementation type and append the appropriate binding to the class path. Contact Oracle Support for help using this option.

4.2.3 Enabling Debug

To enable debug logging, set the gg.log.level property to debug as shown below.