Preface
Understanding Domains
- Understanding Domains Overview
- Nodes
- Service Manager
- Application Services
- High Availability
- Informatica Data Usage Policy
  - Configuring Informatica DiscoveryIQ Proxy Details
  - Disabling Informatica Data Usage
Managing Your Account
- Managing Your Account Overview
- Password Management
  - Changing Your Password
- Preferences
- Informatica Network Credentials
  - Enter Informatica Network Credentials
  - Searching Informatica Knowledge Base
Using Informatica Administrator
- Using Informatica Administrator Overview
- Log In to Informatica Administrator
  - Informatica Administrator URL
  - Troubleshooting the Login to Informatica Administrator
- Manage Tab
- Manage Tab - Domain View
  - Details Panel
  - Resource Usage Indicators
- Manage Tab - Services and Nodes View
- Manage Tab - Connections View
- Manage Tab - Schedules View
- Monitor Tab
- Monitor Tab - Summary Statistics View
- Monitor Tab - Execution Statistics View
- Logs Tab
- Reports Tab
- Security Tab
- Service States
- Process States
- Job States
- Informatica Administrator Accessibility Overview
  - Keyboard Shortcuts
Using the Domain View
- About the Domain View
- Dependency Graph
  - Viewing Dependencies for Application Services, Nodes, and Grids
  - Recycling or Disabling Downstream Services
- Command History
- History View
  - Viewing History
  - Viewing Events
Domain Management
- Domain Management Overview
- Alert Management
- Folder Management
- Domain Security Management
- User Security Management
- Application Service Management
- Gateway Configuration
  - Configuring the Gateway and Worker Nodes
- Domain Configuration Management
- Rename the Domain
- Shutting Down a Domain
- Domain Properties
Nodes
- Nodes Overview
- Node Types
- Node Roles
- Define and Add Nodes
  - Adding Nodes to the Domain
- Configuring Node Properties
- Shutting Down and Restarting the Node
- Removing the Node Association
- Removing a Node
High Availability
- High Availability Overview
- Resilience
- Restart and Failover
  - Domain Failover
  - Application Service Restart and Failover
- Recovery
- Configuration for a Highly Available Domain
- Oracle RAC Database Failover
- Troubleshooting High Availability
Connections
- Connections Overview
- Connection Management
- Pass-through Security
  - Pass-Through Security with Data Object Caching
  - Adding Pass-Through Security
- Pooling Properties in Connection Objects
Connection Properties
- Connection Properties Overview
- Adabas Connection Properties
- Amazon Redshift Connection Properties
- Amazon S3 Connection Properties
- Blockchain Connection Properties
- Cassandra Connection Properties
- Confluent Kafka Connection
  - General Properties
  - Confluent Kafka Broker Properties
  - SSL Properties
  - Creating a Confluent Kafka Connection Using infacmd
- Databricks Connection Properties
- Greenplum Connection Properties
- Google Analytics Connection Properties
- Google BigQuery Connection Properties
  - Connection Modes
- Google Cloud Spanner Connection Properties
- Google Cloud Storage Connection Properties
- Google PubSub Connection Properties
- Hadoop Connection Properties
  - Hadoop Cluster Properties
  - Common Properties
  - Reject Directory Properties
  - Blaze Configuration
  - Spark Configuration
- HBase Connection Properties
- HDFS or View File System (ViewFS) Connection Properties
- HBase Connection Properties for MapR-DB
- Hive Connection Properties
- HTTP Connection Properties
- IBM DB2 Connection Properties
- IBM DB2 for i5/OS Connection Properties
- IBM DB2 for z/OS Connection Properties
- IMS Connection Properties
- JDBC Connection Properties
- JDBC V2 Connection Properties
- JD Edwards EnterpriseOne Connection Properties
- Kafka Connection Properties
  - General Properties
  - Kafka Broker Properties
  - SSL Properties
  - Creating a Kafka Connection Using infacmd
- Kudu Connection Properties
- LDAP Connection Properties
- Microsoft Azure Blob Storage Connection Properties
- Microsoft Azure Cosmos DB SQL API Connection Properties
- Microsoft Azure Data Lake Storage Gen1 Connection Properties
- Microsoft Azure Data Lake Storage Gen2 Connection Properties
- Microsoft Azure SQL Data Warehouse Connection Properties
- MS SQL Server Connection Properties
- Netezza Connection Properties
- OData Connection Properties
- ODBC Connection Properties
- Oracle Connection Properties
- Salesforce Connection Properties
- Salesforce Marketing Cloud Connection Properties
- SAP Connection Properties
- Sequential Connection Properties
- Snowflake Connection Properties
- Teradata Parallel Transporter Connection Properties
- Tableau Connection Properties
- Tableau V3 Connection Properties
- Twitter Streaming Connection Properties
- VSAM Connection Properties
- Web Services Connection Properties
- Identifier Properties in Database Connections
  - Regular Identifiers
  - Delimited Identifiers
  - Identifier Properties
Schedules
- Schedules Overview
- Create and Edit Schedules
  - Creating a Schedule
  - Editing a Schedule
- Pausing and Resuming a Schedule
- Removing Jobs from a Schedule
- Deleting a Schedule
Domain Object Export and Import
- Domain Object Export and Import Overview
- Export Process
  - Rules and Guidelines for Exporting Domain Objects
- View Domain Objects
  - Viewable Domain Object Names
- Import Process
  - Rules and Guidelines for Importing Domain Objects
  - Conflict Resolution
License Management
- License Management Overview
- Types of License Keys
  - Original Keys
  - Incremental Keys
- Creating a License Object
- Assigning a License to a Service
  - Rules and Guidelines for Assigning a License to a Service
- Unassigning a License from a Service
- Updating a License
- Removing a License
- License Properties
Monitoring
- Monitoring Overview
- Configuring Monitoring
  - Step 1. Configure Monitoring Settings
  - Step 2. Configure Reports and Statistics Views
- Optimizing Monitoring Performance
- Summary Statistics
  - Viewing Summary Statistics
- Monitor Data Integration Services
  - Properties View for a Data Integration Service
  - Reports View for a Data Integration Service
- Monitor Ad Hoc Jobs
- Monitor Applications
  - Properties View for an Application
  - Reports View for an Application
- Monitor Deployed Mapping Jobs
- Monitor Logical Data Objects
- Monitor SQL Data Services
- Monitor Web Services
- Monitor Workflows
- Job Status After Application Service Restart or Failover
- Monitoring a Folder of Objects
Log Management
- Log Management Overview
- Log Manager Architecture
- Log Location
- System Logs
- Log Management Configuration
- Using the Logs Tab
- Log Events
- Mapping Task Logs
Domain Reports
- Domain Reports Overview
- License Management Report
- Web Services Report
Node Diagnostics
- Node Diagnostics Overview
- Informatica Network Login
  - Logging In to the Informatica Network
- Generating Node Diagnostics
- Downloading Node Diagnostics
- Uploading Node Diagnostics
- Analyzing Node Diagnostics
  - Identify Bug Fixes
  - Identify Recommendations
Understanding Globalization
- Globalization Overview
  - Unicode
  - Working with a Unicode PowerCenter Repository
- Locales
- Data Movement Modes
  - Character Data Movement Modes
    - ASCII Data Movement Mode
    - Unicode Data Movement Mode
  - Changing Data Movement Modes
- Code Page Overview
- Code Page Compatibility
- Code Page Validation
- Relaxed Code Page Validation
- PowerCenter Code Page Conversion
  - Choosing Characters for PowerCenter Repository Metadata
- Case Study: Processing ISO 8859-1 Data
  - Configuring the ISO 8859-1 Environment
- Case Study: Processing Unicode UTF-8 Data
  - Configuring the UTF-8 Environment
Managing Distribution Packages
- Managing Distribution Packages Overview
- Before You Begin
- Install or Remove Distribution Packages in Console Mode
- Install or Remove Distribution Packages in Silent Mode
- After You Install
Appendix A: Code Pages
- Supported Code Pages for Application Services
- Supported Code Pages for Sources and Targets
Appendix B: Custom Roles
- Analyst Service Custom Role
- Metadata Manager Service Custom Roles
- Operator Custom Role
- PowerCenter Repository Service Custom Roles
- Test Data Manager Custom Roles
Appendix C: Informatica Platform Connectivity
- Informatica Platform Connectivity Overview
- Domain Connectivity
  - Model Repository Connectivity
- PowerCenter Connectivity
- Native Connectivity
- ODBC Connectivity
- JDBC Connectivity
Appendix D: Configure the Web Browser
- Configure the Web Browser

Administrator Guide

10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

Code Page Compatibility

Compatibility between code pages is essential for accurate data movement when the PowerCenter Integration Service runs in the Unicode data movement mode.

A code page can be compatible with another code page, or it can be a subset or a superset of another:

Compatible. Two code pages are compatible when the characters encoded in the two code pages are virtually identical. For example, JapanEUC and JIPSE code pages contain identical characters and are compatible with each other. The PowerCenter repository and PowerCenter Integration Service process can each use one of these code pages and can pass data back and forth without data loss.

Superset. A code page is a superset of another code page when it contains all the characters encoded in the other code page and additional characters not encoded in the other code page. For example, MS Latin1 is a superset of US-ASCII because it contains all characters in the US-ASCII code page.

Informatica considers a code page to be a superset of itself and all other compatible code pages.

Subset. A code page is a subset of another code page when all characters in the code page are also encoded in the other code page. For example, US-ASCII is a subset of MS Latin1 because all characters in the US-ASCII code page are also encoded in the MS Latin1 code page.

For accurate data movement, the target code page must be a superset of the source code page. If the target code page is not a superset of the source code page, the PowerCenter Integration Service may not process all characters, resulting in incorrect or missing data. For example, Latin1 is a superset of US-ASCII. If you select Latin1 as the source code page and US-ASCII as the target code page, you might lose character data if the source contains characters that are not included in US-ASCII.

When you install or upgrade a PowerCenter Integration Service to run in Unicode mode, you must ensure code page compatibility among the domain configuration database, the Administrator tool, PowerCenter Clients, PowerCenter Integration Service process nodes, the PowerCenter repository, the Metadata Manager repository, and the machines hosting pmrep
and pmcmd
. In Unicode mode, the PowerCenter Integration Service enforces code page compatibility between the PowerCenter Client and the PowerCenter repository, and between the PowerCenter Integration Service process and the PowerCenter repository. In addition, when you run the PowerCenter Integration Service in Unicode mode, code pages associated with sessions must have the appropriate relationships:

For each source in the session, the source code page must be a subset of the target code page. The PowerCenter Integration Service does not require code page compatibility between the source and the PowerCenter Integration Service process or between the PowerCenter Integration Service process and the target.

If the session contains a Lookup or Stored Procedure transformation, the database or file code page must be a subset of the target that receives data from the Lookup or Stored Procedure transformation and a superset of the source that provides data to the Lookup or Stored Procedure transformation.

If the session contains an External Procedure or Custom transformation, the procedure must pass data in a code page that is a subset of the target code page for targets that receive data from the External Procedure or Custom transformation.

Informatica uses code pages for the following components:

Domain configuration database. The domain configuration database must be compatible with the code pages of the PowerCenter repository and Metadata Manager repository.

Administrator tool. You can enter data in any language in the Administrator tool.

PowerCenter Client. You can enter metadata in any language in the PowerCenter Client.

PowerCenter Integration Service process. The PowerCenter Integration Service can move data in ASCII mode and Unicode mode. The default data movement mode is ASCII, which passes 7-bit ASCII or 8-bit ASCII character data. To pass multibyte character data from sources to targets, use the Unicode data movement mode. When you run the PowerCenter Integration Service in Unicode mode, it uses up to three bytes for each character to move data and performs additional checks at the session level to ensure data integrity.

PowerCenter repository. The PowerCenter repository can store data in any language. You can use the UTF-8 code page for the PowerCenter repository to store multibyte data in the PowerCenter repository. The code page for the PowerCenter repository is the same as the database code page.

Metadata Manager repository. The Metadata Manager repository can store data in any language. You can use the UTF-8 code page for the Metadata Manager repository to store multibyte data in the repository. The code page for the repository is the same as the database code page.

Sources and targets. The sources and targets store data in one or more languages. You use code pages to specify the type of characters in the sources and targets.

PowerCenter command line programs. You must also ensure that the code page for pmrep
is a subset of the PowerCenter repository code page and the code page for pmcmd
is a subset of the PowerCenter Integration Service process code page.

Most database servers use two code pages, a client code page to receive data from client applications and a server code page to store the data. When the database server is running, it converts data between the two code pages if they are different. In this type of database configuration, the PowerCenter Integration Service process interacts with the database client code page. Thus, code pages used by the PowerCenter Integration Service process, such as the PowerCenter repository, source, or target code pages, must be identical to the database client code page. The database client code page is usually identical to the operating system code page on which the PowerCenter Integration Service process runs. The database client code page is a subset of the database server code page.

For more information about specific database client and server code pages, see your database documentation.

Understanding Globalization

Domain Configuration Database Code Page

Administrator Tool Code Page

PowerCenter Client Code Page

PowerCenter Integration Service Process Code Page

PowerCenter Repository Code Page

Metadata Manager Repository Code Page

PowerCenter Source Code Page

PowerCenter Target Code Page

Command Line Program Code Pages

Code Page Compatibility Summary