Informatica Power center - Changing Data Movement Modes

Changing Data Movement Modes

You can change the PowerCenter Server data movement mode in the PowerCenter Server configuration parameters.

After you change the data movement mode, the PowerCenter Server runs in the new data movement mode the next time you start the PowerCenter Server. When the data movement mode changes, the PowerCenter Server handles character data differently.

To avoid creating data inconsistencies in your target tables, the PowerCenter Server performs additional checks for sessions that reuse session caches and files.

Below table describes how the PowerCenter Server handles session files and caches after you change the data movement mode:

Table 2-1. Session and File Cache Handling After Data Movement Mode Change
Session File or Cache	Time of Creation or Use	PowerCenter Server Behavior After Data Movement Mode Change
Session Log File (*.log)	Each session.	No change in behavior. Creates a new session log for each session using the PowerCenter Server code page.
Workflow Log	Each workflow.	No change in behavior. Creates a new workflow log file for each workflow using the PowerCenter Server code page.
Reject File (*.bad)	Each session.	No change in behavior. Appends rejected data to the existing reject file using the PowerCenter Server code page.
Output File (*.out)	Sessions writing to flat file.	No change in behavior for delimited flat files. Creates a new output file for each session using the target code page.
Indicator File (*.in)	Sessions writing to flat file.	No change in behavior. Creates a new indicator file for each session.
Incremental Aggregation Files (*.idx, *.dat)	Sessions with Incremental Aggregation enabled.	When files are removed or deleted, the PowerCenter Server creates new files. When files are not removed or deleted, the PowerCenter Server fails the session with the following error message: TE_7038 Aggregate Error: ServerMode: [server data movement mode] and CachedMode: [data movement mode that created the files] mismatch. You should also remove or delete files created using a different code page.
Unnamed Persistent Lookup Files (*.idx, *.dat)	Sessions with a Lookup transformation configured for a named persistent lookup cache.	Rebuilds the persistent lookup cache.
Named Persistent Lookup Files (*.idx, *.dat)	Sessions with a Lookup transformation configured for a persistent lookup cache.	Fails the session.