How to enable ODBC tracing for the branded DataDirect driver for Advanced Authentication servers for a Linux platform?
CA Advanced Authentivation for RHEL(Red Hat Linux) platform:
- CA Strong Authentivation(previously Webfort or AuthMinder)
- CA Risk Authentivation(previously Riskfort or RiskMinder)
Any supported DB versions(Oracle or MS SQL Server)
Request For Information
1. Take a backup of $ARCOT_HOME/odbc<vesrion>/odbc.ini file.
2. Open $ARCOT_HOME/odbc<vesrion>/odbc.ini file.
3. Set below configurations under [ODBC] section which it around the beginning of the odbc.ini file
-->change "Trace" from 0 to 1
-->change "TraceDll" as <<ARCOT_HOME>>/odbc<version>/lib/WFtrcXX.so
Below is an example with [ODBC] section populated
4. Restart the server
5. Perform the test to reproduce issue
6. This will generate "odbctrace.out" log file. Logs will be created at a location as defined in "TraceFile" configuration above.
Note 1: Make sure the trace file(TraceDll=) exists. If it does not, configure one trace dll that is available in <<ARCOT_HOME>>/odbc32<version>wf/lib/ folder. The trace dll name is like WFtrcXX.so.
Note 2: TraceOptions=[0 | 1 | 2 | 3]
The ODBCTraceOptions keyword specifies whether to print the current timestamp, parent process id, process id, and thread id for all ODBC functions to the output file. The default is 0.
If set to 0, the driver uses standard ODBC tracing.
If set to 1, the log file includes a timestamp on ENTRY and EXIT of each ODBC function.
If set to 2, the log file prints a header on every line. By default, the header includes the parent process ID and process ID.
If set to 3, both TraceOptions=1 and TraceOptions=2 are enabled. The header includes a timestamp as well as a parent process ID and process ID.