Restriction: This topic applies only when the Enterprise Server feature is enabled.
- SQL Server, PostgreSQL, and ODBC
- The SQL Server and ODBC switch modules have been coded to use the Consolidated Trace Facility (CTF) to aid in debugging any
errors returned during operation. The CTF component name for tracing RM switch modules is
We have provided a configuration file,
ctf.cfg, located by default in the
directory, to serve as a starting point. To enable this facility:
- Edit the
ctf.cfg file using any text editor and change the location parameter on line 6 to the directory where you want to store your trace
- Create a new system environment variable named MFTRACE_CONFIG, and set its value to the full path where
ctf.cfg is located.
- Reboot your system to register MFTRACE_CONFIG.
- Start Enterprise Server.
Once enabled, the Consolidated Trace Facility writes SQLCODE, SQLSTATE and any associated SQL error messages to a trace file
cassi.textfile.processid.log, located in the directory you specified.
Processid is the process ID under which the Enterprise Server SEP was running when the logfile was created.
For more information, see
The Consolidated Trace Facility and
Components Traced by CTF.
- SQL Server
- Microsoft provides a downloadable tool,
DTCPing, to help diagnose MSDTC configuration problems. We suggest that you use this tool and review relevant Microsoft MSDTC documentation
as required to troubleshoot the SQL Server switch module.