Using Log and Trace Files to Resolve Issues
When an error or problem occurs, use log and trace files to troubleshoot the cause.
- Review the log file, which contains a record of all data errors.
- To prevent problems caused by excessive trace and log file size, use the max_file_size parameters to limit file size. On UNIX, the client will crash if the trace file exceeds the system imposed limit.
- If you are having problems and contact Technical Support, Technical Support may request a copy of the log file. It is recommended that you use a compression utility before sending the log file.
- If Technical Support requests a trace, make sure that the old trace files are deleted before starting the client with the -t nnn (or -d) option. You will need to use a compression utility before sending the trace file (which can be quite large). You can use the splitter utility to break up big trace files into smaller, more manageable files. For help on running the splitter program, type splitter with no parameters.
The splitter program can also split binary files (for example, WinZip® files) that are too large to ship as an e-mail attachment. The original file can be reconstructed from the split files by using the copy /B Windows command. When splitting binary files, you must specify the -B option for the splitter program.