Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Success
Manage your Success Plans and Engagements, gain key insights into your implementation journey, and collaborate with your CSMs
Customer Experience Accelerators
Accelerate your Purchase to Value by engaging with Informatica for Customer Success
My Engagements
All your Engagements at one place
 Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
 Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Experience Lounge
Self-guided, intuitive experience platform for outcome-focused product capabilities and use cases
 Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
SupportFlash
Monthly support newsletter
Product Availability Matrix
Product Availability Matrix statements of Informatica products
Product Lifecycle
End of Life statements of Informatica products
Pulse
Monitor the status of your Informatica services across regions
Events
Change Request Tracking
Marketplace
Trust Platform
English
  • Cloud Data Integration for PowerCenter
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Domains
  3. Managing Your Account
  4. Using Informatica Administrator
  5. Using the Domain View
  6. Domain Management
  7. Nodes
  8. High Availability
  9. Connections
  10. Connection Properties
  11. Domain Object Export and Import
  12. License Management
  13. Monitoring
  14. Log Management
  15. Domain Reports
  16. Understanding Globalization
  17. Managing Distribution Packages
  18. Appendix A: Code Pages
  19. Appendix B: Custom Roles
  20. Appendix C: Informatica Platform Connectivity
  21. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Back Next

Choosing Characters for CDI-PC repository Metadata

Choosing Characters for
CDI-PC repository
 Metadata

You can use any character in the
CDI-PC repository
 code page when inputting
CDI-PC repository
 metadata. If the
CDI-PC repository
 uses UTF-8, you can input any Unicode character. For example, you can store German, Japanese, and English metadata in a UTF-8 enabled
CDI-PC repository
. However, you must ensure that the
CDI-PC Integration Service
 can successfully perform SQL transactions with source, target, lookup, and stored procedure databases. You must also ensure that the
CDI-PC Integration Service
 can read from source and lookup files and write to target and lookup files. Therefore, when you run a session, you must ensure that the
CDI-PC repository
 metadata characters are encoded in the source, target, lookup, and stored procedure code pages.

Example

The
CDI-PC Integration Service
,
CDI-PC repository
, and
CDI-PC Client
 use the ISO 8859-1 Latin1 code page, and the source database contains Japanese data encoded using the Shift-JIS code page. Each code page contains characters not encoded in the other. Using characters other than 7-bit ASCII for the
CDI-PC repository
 and source database metadata can cause the sessions to fail or load no rows to the target in the following situations:
  • You create a mapping that contains a string literal with characters specific to the German language range of ISO 8859-1 in a query. The source database may reject the query or return inconsistent results.
  • You use the
    CDI-PC Client
     to generate SQL queries containing characters specific to the German language range of ISO 8859-1. The source database cannot convert the German-specific characters from the ISO 8859-1 code page into the Shift-JIS code page.
  • The source database has a table name that contains Japanese characters. The
    CDI-PC
     Designer cannot convert the Japanese characters from the source database code page to the
    CDI-PC Client
     code page. Instead, the
    CDI-PC
     Designer imports the Japanese characters as question marks (?), changing the name of the table. The
    CDI-PC Repository Service
     saves the source table name in the
    CDI-PC repository
     as question marks. If the
    CDI-PC Integration Service
     sends a query to the source database using the changed table name, the source database cannot find the correct table, and returns no rows or an error to the
    CDI-PC Integration Service
    , causing the session to fail.
Because the US-ASCII code page is a subset of both the ISO 8859-1 and Shift-JIS code pages, you can avoid these data inconsistencies if you use 7-bit ASCII characters for all of your metadata.
0 COMMENTS
We’d like to hear from you!