Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Unexpected Data in a Code Page

Unexpected Data in a Code Page

If you load data in a code page other than the one that the database metadata specifies, problems might occur when you try to convert data using PowerExchange or any conversion tool that the database provides. If the code page is already supported, you do not need to add a user-defined code page.
You can use the ICUALIAS statement in the DBMOVER configuration file on the system where the PowerExchange Listener runs to replace the default internal code page number with the required internal code page number. Because this procedure remaps all data for the problem CCSID to the new code page, you might need to run multiple PowerExchange Llisteners on different ports if you have problem data in multiple code pages.
You can also associate individual data maps with different code pages. For CDC processing, you can then merge the DB2 data maps into the corresponding extraction maps. Using this method, you do not need to use multiple Listeners on different ports.
To test your code page mappings, you can first run a database row test. If the row test produces the expected results, you can then create a PowerCenter workflow with a flat file target in a UTF8 code page. If that workflow produces the desired results, you can then create a workflow with a relational target.


We’d like to hear from you!