F Logging

F.1 Logs and Setting Log Levels

Oracle GoldenGate Veridata maintains logs for both the agent and the server, helping with monitoring, troubleshooting, and performance analysis.

  • The agent generates:
    • Main logs
    • Query logs for executed SQL queries
    • Performance logs for tracking execution efficiency

Veridata agent logs are categorized into different log levels to control the verbosity of logging:

  • TRACE – Detailed debugging information
  • NOTIFICATION – General operational messages
  • WARNING – Potential issues that may require attention
  • ERROR – Errors that impact functionality but do not stop execution
  • INCIDENT_ERROR – Critical errors requiring immediate action

  • The server generates:
    • Main logs
    • Diagnostic logs for troubleshooting issues
    • Performance logs for monitoring system performance

These log levels help in filtering relevant information based on the required level of detail.

Parent topic: Logging

F.2 Agent

Parent topic: Logging

F.2.1 Agent Logs Location

Agent logs are stored in the following directory: $AGENT_DEPLOYED_LOCATION/logs/

The main agent logs are recorded in: veridata-agent.log.

The performance logs are stored in: vdtperf-agent.log.

Parent topic: Agent

F.2.2 Updating Agent Log Settings

Agent log settings can be configured in the odl.xml file.

File Location: $AGENT_DEPLOYED_LOCATION/config/odl.xml

Parent topic: Agent

F.2.3 Enabling Performance Logs

  1. Modify the odl.xml file and change level from NOTIFICATION to TRACE for logger with name oracle.veridata.agent.performance.

    For example:

    <logger name='oracle.veridata.agent.performance' level='TRACE:1'
            useParentHandlers='false'>
            <handler name='perf-handler' />
            <handler name='my-console-handler' />
 </logger>
  2. Restart the agent.

    If this logger is not present in the odl.xml file then:

    1. Add the following log handler under <log_handlers>:
      <log_handler name='perf-handler'
      class='oracle.core.ojdl.logging.ODLHandlerFactory'>
    <property name='path' value='${agentHome}/logs/vdtperf-${agent.id}.log' />
    <property name='maxFileSize' value='10485760' />
   <property name='maxLogSize' value='104857600' />
   <property name='useSourceClassAndMethod' value='TRACE:1' />
</log_handler>
    2. Under the <loggers> tag add the following:
      <logger name='oracle.veridata.agent.performance' level='TRACE:1'
          useParentHandlers='false'>
          <handler name='perf-handler' />
          <handler name='my-console-handler' />
</logger>
  3. Restart the agent.

Parent topic: Agent

F.2.4 Enabling Trace Logs

Modify the odl.xml file and change level from NOTIFICATION to TRACE for loggers having name oracle.veridata. Restart the agent.

For example:

<logger name='oracle.veridata' level='TRACE:1'
            useParentHandlers='false'>
            <handler name='odl-handler' />
            <handler name='my-console-handler' />
</logger>

<logger name='oracle.veridata.XML'  level='TRACE:1'
            useParentHandlers='false'>
            <handler name='odl-handler' />
            <handler name='my-console-handler'/>
</logger>

Parent topic: Agent

F.2.5 Enabling Query Logs

  1. Modify the odl.xml file and change level from NOTIFICATION to TRACE for loggers having name oracle.veridata.agent.query.
    <logger name='oracle.veridata.agent.query' level='TRACE:1'
            useParentHandlers='false'>
            <handler name='odl-handler' />
            <handler name='my-console-handler' />
</logger>
  2. Restart the agent.

Parent topic: Agent

F.2.6 Modifying Log Size

The log rotation is enabled by default, and therefore older logs get deleted when log size reached a certain size. However, this can be controlled as follows:

Log size is specified per log handler in the odl.xml file. This is controlled by the following 2 properties:

  • maxFileSize - Defines the maximum size (in bytes) a log file can reach before it gets rotated and a new log file is created.
  • maxLogSize - It controls the max log size (in bytes) before rolling over.

For all the logs:

Find the log handler with name odl-handler and change values of maxFileSize and maxLogSize, and then restart the agent. 

<log_handler name='odl-handler'
            class='oracle.core.ojdl.logging.ODLHandlerFactory'>
            <property name='path' value='${agentHome}/logs/veridata-${agent.id}.log' />
            <property name='maxFileSize' value='10485760' />
            <property name='maxLogSize' value='104857600' />
            <property name='useSourceClassAndMethod' value='TRACE:1' />
        </log_handler>

For Performance Logs:

Find the log handler with name perf-handler and change values of maxFileSize and maxLogSize, then restart the agent. 

<log_handler name='perf-handler'
class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${agentHome}/logs/vdtperf-${agent.id}.log' />
<property name='maxFileSize' value='10485760' />
<property name='maxLogSize' value='104857600' /> 
<property name='useSourceClassAndMethod' value='TRACE:1' />
</log_handler>

Note:

Values of maxFileSize and maxLogSize are in bytes, therefore 10485760 is 10 MB.

Parent topic: Agent

F.3 Server

Parent topic: Logging

F.3.1 Server Log Location

All the server logs are stored in the following directory: $DOMAIN_HOME/servers/VERIDATA_server1/logs/

The main server logs are recorded in: VERIDATA_server1.log

The server Diagnostic logs are recorded in VERIDATA_server1-diagnostic.log

Server performance logs are recorded in VERIDATA_server1-perf.log.

Parent topic: Server

F.3.2 Updating Server Log Settings

Enabling Performance Logs

To enable performance logs for server, add the following log_handler in the logging.xml file: 

<log_handler name='server-perf-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-perf.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='DSID,J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,oracle.soa.tracking.FlowId,oracle.soa.tracking.InstanceId,oracle.soa.tracking.SCAEntityId,oracle.soa.tracking.FaultId,oracle.soa.tracking.RetryCount,composite_name'/>
</log_handler>
Add the following logger and then restart the server
<logger name='oracle.veridata.server.performance' level='TRACE:1'useParentHandlers='false'><handler name='server-perf-handler' />
    </logger>

Parent topic: Server

F.3.3 Enabling Trace Logging

By default, the TRACE level logging is disabled for the Oracle GoldenGate Veridata Server. Oracle GoldenGate Veridata generates several messages at the TRACE level. Therefore, this should be enabled only for debugging purpose.

To enable server trace, add the following line in the logging.xml file under the loggers tag and then restart the server.
<logger name='oracle.veridata.server' level='TRACE:1' useParentHandlers='true'/>
    <logger name='oracle.veridata.shared' level='TRACE:1' useParentHandlers='true'/>

Parent topic: Server

F.3.4 Changing Log Size

Log rotation is enabled by default, ensuring older logs are deleted when they reach a specified size.

Log size is controlled in the logging.xml file, where each log handler has two key properties:

  • maxFileSize - Defines the maximum size (in bytes) a log file can reach before it gets rotated and a new log file is created.
  • maxLogSize - It controls the max log size (in bytes) before rolling over.

To adjust log size for all logs, find log_handler named console-handler in the logging.xml file and modify these properties accordingly: 

<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' level='WARNING:32' formatter='oracle.core.ojdl.weblogic.Con$
  <log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
   <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
   <property name='maxFileSize' value='10485760'/>
   <property name='maxLogSize' value='104857600'/>

Change values of maxFileSize and maxLogSize

For performance logs: Find the following log_handler: server-perf-handler and change its properties. 

<log_handler name='server-perf-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
    <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-perf.log'/>
    <property name='maxFileSize' value='10485760'/>
    <property name='maxLogSize' value='104857600'/>

Note:

Values of maxFileSize and maxLogSize and are in bytes, therefore '10485760' is 10 MB.

Parent topic: Server