Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Verifying the Code Page Mapping File

Verifying the Code Page Mapping File

When you create a FastExport connection, you select the PowerCenter code page that FastExport uses to read Teradata sources. FastExport uses the fexpcodepagemapfile.dat file to map the PowerCenter code page name to the Teradata character set that FastExport supports. For example, if you select “MS Windows Latin 1 (ANSI), superset of Latin1” as the connection code page, PowerCenter uses the code page named “MS1252” while Teradata uses the character set named “Latin1252_0A.”
The fexpcodepagemapfile.dat file maps the most appropriate Teradata character sets to PowerCenter code pages as specified in
Teradata International Character Set Support
. Teradata character sets must be enabled on the database before you can use them. By default, only the following character sets are enabled on a Teradata database:
  • ASCII
  • EBCDIC
  • UTF8
  • UTF16
If the PowerCenter code page you select in the FastExport connection does not exist in fexpcodepagemapfile.dat or if the assigned Teradata character set is not enabled on the database, the Integration Service fails the session.
The fexpcodepagemapfile.dat file is located in
<PowerCenter installation directory>\server\bin
. Verify that the file includes the PowerCenter code page you select in the FastExport connection and that the assigned character set is enabled on the Teradata database. You can use a text editor to assign additional PowerCenter code pages to Teradata character sets or to modify the existing mappings. Assign a PowerCenter code page to a Teradata character set by entering the names on a single line in the following format:
<PowerCenter_code_page> = <Teradata_character_set>.
For example,
MS1252 = Latin1252_0A
Use the following rules and guidelines when you edit the file:
  • To designate a comment, start a line with an exclamation point (!).
  • A line cannot consist of blank spaces or tab characters only.
  • If the file maps a single PowerCenter code page to multiple Teradata character sets, FastExport uses the character set that is assigned last in the file.
Teradata does not distinguish between Big Endian and Lower Endian for UTF-16 encoding of Unicode. If you process UTF-16 characters, select the “UTF-16 encoding of Unicode (Platform Endian)” code page when creating the FastExport connection in the Workflow Manager.


Updated August 27, 2020