Code Page Validation
The machines hosting the PowerCenter Client, PowerCenter Integration Service process, and PowerCenter repository database must use appropriate code pages. This eliminates the risk of data or repository inconsistencies. When the PowerCenter Integration Service runs in Unicode data movement mode, it enforces session code page relationships. When the PowerCenter Integration Service runs in ASCII mode, it does not enforce session code page relationships.
To ensure compatibility, the PowerCenter Client and PowerCenter Integration Service perform the following code page validations:
- •PowerCenter restricts the use of EBCDIC-based code pages for repositories. Since you cannot install the PowerCenter Client or PowerCenter repository on mainframe systems, you cannot select EBCDIC-based code pages, like IBM EBCDIC, as the PowerCenter repository code page.
- •PowerCenter Client can connect to the PowerCenter repository when its code page is a subset of the PowerCenter repository code page. If the PowerCenter Client code page is not a subset of the PowerCenter repository code page, the PowerCenter Client fails to connect to the PowerCenter repository code page with the following error:
REP_61082 <PowerCenter Client>'s code page <PowerCenter Client code page> is not one-way compatible to repository <PowerCenter repository name>'s code page <PowerCenter repository code page>.
- •After you set the PowerCenter repository code page, you cannot change it. After you create or upgrade a PowerCenter repository, you cannot change the PowerCenter repository code page. This prevents data loss and inconsistencies in the PowerCenter repository.
- •The PowerCenter Integration Service process can start if its code page is a subset of the PowerCenter repository code page. The code page of the PowerCenter Integration Service process must be a subset of the PowerCenter repository code page to prevent data loss or inconsistencies. If it is not a subset of the PowerCenter repository code page, the PowerCenter Integration Service writes the following message to the log files:
REP_61082 <PowerCenter Integration Service>'s code page <PowerCenter Integration Service code page> is not one-way compatible to repository <PowerCenter repository name>'s code page <PowerCenter repository code page>.
- •When in Unicode data movement mode, the PowerCenter Integration Service starts workflows with the appropriate source and target code page relationships for each session. When the PowerCenter Integration Service runs in Unicode mode, the code page for every source in a session must be a subset of the target code page. This prevents data loss during a session.
If the source and target code pages do not have the appropriate relationships with each other, the PowerCenter Integration Service fails the session and writes the following message to the session log:
TM_6227 Error: Code page incompatible in session <session name>. <Additional details>.
- •The PowerCenter Workflow Manager validates source, target, lookup, and stored procedure code page relationships for each session. The PowerCenter Workflow Manager checks code page relationships when you save a session, regardless of the PowerCenter Integration Service data movement mode. If you configure a session with invalid source, target, lookup, or stored procedure code page relationships, the PowerCenter Workflow Manager issues a warning similar to the following when you save the session:
CMN_1933 Code page <code page name> for data from file or connection associated with transformation <name of source, target, or transformation> needs to be one-way compatible with code page <code page name> for transformation <source or target or transformation name>.
If you want to run the session in ASCII mode, you can save the session as configured. If you want to run the session in Unicode mode, edit the session to use appropriate code pages.