PowerExchange message log files

. PowerExchange writes all runtime messages to the PowerExchange message log file by default. PowerExchange creates this log file if it does not exist. PowerExchange writes each message, as it occurs, to this single log file. If the message log file becomes full, you must clear it.

If you enable alternative logging of messages, this primary message log file contains only the DBMOVER statements and any trace information.

PowerExchange legacy message log files

. If the DBMOVER configuration file does not contain a TRACING statement, PowerExchange generates legacy message log files.

PowerExchange alternative log files

. If you enable alternative logging by defining the TRACING statement in the DBMOVER configuration file, PowerExchange writes runtime messages from PowerExchange components, programs, and commands to a set of alternative message log files that are used on a rotating basis. PowerExchange dynamically allocates these alternative log files if they do not exist. When an alternative log file becomes full, PowerExchange switches to another alternative log file and begins overwriting any data in that file. Also, with alternative logging, PowerExchange buffers messages and writes them to disk files based on a customized flush interval, thereby reducing I/O activity on these files. Informatica recommends that you use alternative logging to prevent out-of-space conditions on log files, to mprove logging performance, and to control the amount of data that is logged for long-running jobs.