While troubleshooting any issues, you require to view the required trace files to analyze the issue. Ensure the following trace files are collected to help you analyze any issue:
Fanout driver trace: This is a common trace file that can be configured using Designer or iManager.
To configure using Designer, go to Driver Properties > Trace and set the trace level and trace file name.
To configure using iManager, click the driver icon, select Edit Properties > Misc and configure the trace level and trace file path.
Fanout agent trace: This trace file contains the processing logs performed by the Fanout agent. The trace file is located at <fanout agent root directory>\logs.
To configure the Fanout agent trace level and the trace path, modify the following parameter in the Fanout agent configuration file:
NOTE: By default, trace level is set to 5 and file name is fanout_trace.txt.
netiq.fanoutagent.trace.level=5
netiq.fanoutagent.trace.file=fanout_trace.txt
JDBC driver instance trace: This trace contains the JDBC instance level tracing, that can be configured using Designer or iManager. These trace files are located in the server where the Fanout agent is installed.
To configure using Designer, provide the trace level and trace file path for the particular JDBC instance, while configuring the connection object.
To configure using iManager, navigate to the driver object and open the connection instance object. Update the following xml attributes in the connection instance object xml:
<trace-info>
<driverTraceFile>trace-file-path</driverTraceFile>
<driverTraceLevel>trace-level</driverTraceLevel>
<driverTraceFileSize>trace-file-size</driverTraceFileSize>
</trace-info>