1. Administering Oracle GoldenGate for Big Data
  2. Understanding Oracle GoldenGate for Big Data
  3. Configuring Logging

3 Configuring Logging

Parent topic: Understanding Oracle GoldenGate for Big Data

3.1 Oracle GoldenGate Java Adapter Default Logging

Parent topic: Configuring Logging

3.1.1 Default Logging Setup

Logging is enabled by default for the Oracle GoldenGate for BigData. The logging implementation is log4j. By default, logging is enabled at the info level.

Parent topic: Oracle GoldenGate Java Adapter Default Logging

3.1.2 Log File Name

The log output file is created in the standard report directory. The name of the log file includes the replicat group name and has an extension of log.

If the Oracle GoldenGate Replicat process group name is JAVAUE, then the log file name in the report directory is: JAVAUE.log.

Parent topic: Oracle GoldenGate Java Adapter Default Logging

3.1.3 Changing Logging Level

To change the recommended log4j logging level, add the configuration shown in the following example to the Java Adapter Properties file: 
gg.log.level=error

You can set the gg.log.level to none, error, warn, info, debug, or trace. The default log level is info. Oracle recommends the debug and trace log levels only for troubleshooting as these settings can adversely impact the performance.

Parent topic: Oracle GoldenGate Java Adapter Default Logging

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.

Parent topic: Configuring Logging

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. 

gg.log=log4j
gg.log.level=info

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: 

javaue_debug_log4j.log

Parent topic: Recommended Logging Settings