Preface
Understanding Domains
- Understanding Domains Overview
- Nodes
- Service Manager
- Application Services
- High Availability
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
  - Navigator Search
  - Domain
  - Folders
  - Application Services
  - Nodes
  - Grids
  - Licenses
- Manage Tab - Connections 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
  - Shutting Down a Node from the Administrator Tool
  - Starting or Stopping a Node on UNIX
- 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
- Pass-through Security
Connection Properties
- Connection Properties Overview
- Amazon Redshift Connection Properties
- Amazon S3 Connection Properties
- Greenplum Connection Properties
- Google BigQuery Connection Properties
  - Connection Modes
- Google Cloud Storage Connection Properties
- IBM DB2 Connection Properties
- IBM DB2 for i5/OS Connection Properties
- IBM DB2 for z/OS Connection Properties
- JDBC Connection Properties
- JDBC V2 Connection Properties
- JD Edwards EnterpriseOne Connection Properties
- LDAP Connection Properties
- Microsoft Azure Blob Storage Connection Properties
- Microsoft Azure Cosmos DB SQL API Connection Properties
- Microsoft Azure Data Lake Storage Gen2 Connection Properties
- MS SQL Server Connection Properties
- Netezza Connection Properties
- ODBC Connection Properties
- Oracle Connection Properties
- Salesforce Connection Properties
- Salesforce Marketing Cloud Connection Properties
- SAP Connection Properties
- Snowflake Connection Properties
- Teradata Parallel Transporter Connection Properties
- Tableau Connection Properties
- Identifier Properties in Database Connections
  - Regular Identifiers
  - Delimited Identifiers
  - Identifier Properties
- PowerExchange for PostgreSQL Connection Properties
- Microsoft Dynamics 365 for Sales Connection Properties
- PowerExchange for Oracle E-Business Suite Connection Properties
- Siebel Application Connections for Sources, Targets, and EIM Invoker Transformations
- Microsoft Dynamics CRM Connection
- PowerExchange for Essbase Connections
- Vertica Relational Connection Properties
- PowerExchange for Db2 Warehouse Connections
- PowerExchange for HANA Connections
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
- Creating a License Object
- Assigning a License to a Service
  - Rules and Guidelines for Assigning a License to a Service
- 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 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
Understanding Globalization
- Globalization Overview
  - Unicode
  - Working with a Unicode CDI-PC repository
- Locales
- Data Movement Modes
  - Character Data Movement Modes
    - ASCII Data Movement Mode
    - Unicode Data Movement Mode
  - Changing Data Movement Modes
- Code Page Overview
  - UNIX Code Pages
  - Choosing a Code Page
- Code Page Compatibility
- Code Page Validation
- Relaxed Code Page Validation
- CDI-PC Code Page Conversion
  - Choosing Characters for CDI-PC 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
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
- Operator Custom Role
- CDI-PC Repository Service Custom Roles
Appendix C: Informatica Platform Connectivity
- Informatica Platform Connectivity Overview
- Domain Connectivity
  - Model Repository Connectivity
- CDI-PC Connectivity
- Native Connectivity
- ODBC Connectivity
- JDBC Connectivity
Appendix D: Configure the Web Browser
- Configure the Web Browser

Administrator Guide

Back Next

Code Page Validation

The machines hosting the

CDI-PC Client

CDI-PC Integration Service

process, and

CDI-PC repository

database must use appropriate code pages. This eliminates the risk of data or repository inconsistencies. When the

CDI-PC Integration Service

runs in Unicode data movement mode, it enforces session code page relationships. When the

CDI-PC Integration Service

runs in ASCII mode, it does not enforce session code page relationships.

To ensure compatibility, the

CDI-PC Client

and

CDI-PC Integration Service

perform the following code page validations:

CDI-PC

restricts the use of EBCDIC-based code pages for repositories. Since you cannot install the

CDI-PC Client

CDI-PC repository

on mainframe systems, you cannot select EBCDIC-based code pages, like IBM EBCDIC, as the

CDI-PC repository

code page.

CDI-PC Client

can connect to the

CDI-PC repository

when its code page is a subset of the

CDI-PC repository

code page. If the

CDI-PC Client

code page is not a subset of the

CDI-PC repository

code page, the

CDI-PC Client

fails to connect to the

CDI-PC repository

code page with the following error:

REP_61082 <CDI-PC Client>'s code page <CDI-PC Client code page> is not one-way compatible to repository <CDI-PC repository name>'s code page <CDI-PC repository code page>.

After you set the

CDI-PC repository

code page, you cannot change it. After you create or upgrade a

CDI-PC repository

, you cannot change the

CDI-PC repository

code page. This prevents data loss and inconsistencies in the

CDI-PC repository

The

CDI-PC Integration Service

process can start if its code page is a subset of the

CDI-PC repository

code page. The code page of the

CDI-PC Integration Service

process must be a subset of the

CDI-PC repository

code page to prevent data loss or inconsistencies. If it is not a subset of the

CDI-PC repository

code page, the

CDI-PC Integration Service

writes the following message to the log files:

REP_61082 <CDI-PC Integration Service>'s code page <CDI-PC Integration Service code page> is not one-way compatible to repository <CDI-PC repository name>'s code page <CDI-PC repository code page>.

When in Unicode data movement mode, the

CDI-PC Integration Service

starts workflows with the appropriate source and target code page relationships for each session. When the

CDI-PC 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

CDI-PC 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

CDI-PC

Workflow Manager validates source, target, lookup, and stored procedure code page relationships for each session. The

CDI-PC

Workflow Manager checks code page relationships when you save a session, regardless of the

CDI-PC Integration Service

data movement mode. If you configure a session with invalid source, target, lookup, or stored procedure code page relationships, the

CDI-PC

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.

Rename Saved Search

Table of Contents

Administrator Guide

Administrator Guide

Code Page Validation

Code Page Validation