Informatic Installationguide

Installation and
Configuration Guide
INFORMATICA
POWERCENTER
6
INFORMATICA
POWERMART
6
(VERSION 6.0)
Informatica PowerCenter/PowerMart Installation and Configuration Guide
Version 6.0
June 2002
Copyright (c) 2002 Informatica Corporation.
All rights reserved. Printed in the USA.
This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement
containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. No
part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise)
without prior consent of Informatica Corporation.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software
license agreement as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR
12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to
us in writing. Informatica Corporation does not warrant that this documentation is error free.
Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug, PowerBridge, ZL Engine, and MX are
trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other
company and product names may be trade names or trademarks of their respective owners.
Portions of this software are copyrighted by MERANT, 1991-2000.
Apache Software
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
The Apache Software is Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms of the Apache Software, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product
includes software developed by the Apache Software Foundation (http://www.apache.org/).
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names Xerces and Apache Software Foundation must not be used to endorse or promote products without prior written
permission of the Apache Software Foundation.
5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission
of the Apache Software Foundation.
THE APACHE SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Apache Software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was
originally based on software copyright (c) 1999, International Business Machines, Inc.,
http://www.ibm.com. For more information on the Apache Software foundation, please see http://www.apache.org/.
DISCLAIMER: Informatica Corporation provides this documentation as is without warranty of any kind, either express or implied,
including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information
provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or
changes in the products described in this documentation at any time without notice.
i i i
Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Transformation Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
About PowerCenter and PowerMart . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Accessing the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xxv
Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Chapter 1: Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
iv Table of Contents
Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
The Design Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Designer Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Workflow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2: Installation and Configuration Overview . . . . . . . . . . . . . 19
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PowerCenter and PowerMart Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . 21
Informatica Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Informatica Repository Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Informatica Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
PowerCenter and PowerMart Installation Steps . . . . . . . . . . . . . . . . . . . . . . 25
Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Upgrading from a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 3: Globalization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
System Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
User Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Input Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Character Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Changing Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Code Page Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Operating System Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Choosing a Code Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Informatica Code Page Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Relaxed Data Code Page Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Troubleshooting for Relaxed Code Page Validation . . . . . . . . . . . . . . . . . . . 52
Tabl e of Contents v
Case Study: Processing 7-bit ASCII Data . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring the 7-bit ASCII Environment . . . . . . . . . . . . . . . . . . . . . . 54
ASCII Case Study: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Case Study: Processing ISO 8859-1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The ISO 8859-1 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuring the ISO 8859-1 Environment . . . . . . . . . . . . . . . . . . . . . . 58
ISO 8859-1 Case Study: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 4: Installing and Configuring the Informatica Client . . . . . . 63
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Step 1. Installing ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Merant ODBC 3.7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Uninstalling Merant ODBC 3.7 Drivers . . . . . . . . . . . . . . . . . . . . . . . . 66
Step 2. Installing the Informatica Client Tools . . . . . . . . . . . . . . . . . . . . . . 67
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Connecting to a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . 70
Connecting to a Sybase Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . 74
Connecting to Microsoft Access97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Connecting to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Connecting to a Teradata Source Database . . . . . . . . . . . . . . . . . . . . . . 76
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 5: Installing and Configuring the Windows Repository
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Creating Repository Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Step 1. Installing the Repository Server on Windows . . . . . . . . . . . . . . . . . . 82
Step 2. Configuring the Repository Server on Windows . . . . . . . . . . . . . . . . 83
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting to a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . 86
Connecting to a Sybase Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
vi Table of Contents
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . 89
Step 4. Starting the Repository Server on Windows . . . . . . . . . . . . . . . . . . . 91
Starting the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Verifying Repository Server Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Verifying the Repository Server is Running . . . . . . . . . . . . . . . . . . . . . . 93
Stopping the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 6: Installing and Configuring the UNIX Repository Server. . 99
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Step 1. Installing the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Step 2. Configuring the Repository Server on UNIX . . . . . . . . . . . . . . . . . 103
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Connecting to a Sybase Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . 109
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . 110
Step 4. Starting the Repository Server on UNIX . . . . . . . . . . . . . . . . . . . . 112
Starting the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Verifying the Repository Server is Running . . . . . . . . . . . . . . . . . . . . . 112
Stopping the UNIX Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Chapter 7: Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Chapter 8: Installing and Configuring the Informatica Windows
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating Informatica Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Informatica Server Variable Directories . . . . . . . . . . . . . . . . . . . . . . . . 127
Tabl e of Contents vii
Step 1. Installing the Informatica Windows Server . . . . . . . . . . . . . . . . . . 129
Step 2. Configuring the Informatica Windows Server . . . . . . . . . . . . . . . . 131
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Connecting to a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . 141
Connecting to Microsoft Access97 . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Connecting to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Connecting to a Teradata Source Database . . . . . . . . . . . . . . . . . . . . . 147
Step 4. Starting and Stopping the Informatica Server . . . . . . . . . . . . . . . . . 148
Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
pmcmd Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Chapter 9: Installing and Configuring the Informatica UNIX
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
DHCP (TCP/IP Connections Only) . . . . . . . . . . . . . . . . . . . . . . . . . 158
Informatica Server Variable Directories . . . . . . . . . . . . . . . . . . . . . . . . 158
Step 1. Installing the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Step 2. Configuring the Informatica Server on UNIX . . . . . . . . . . . . . . . . 162
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Step 4. Starting and Stopping the Informatica Server on UNIX . . . . . . . . . 175
UNIX Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
pmcmd Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Installing and Configuring ODBC for UNIX . . . . . . . . . . . . . . . . . . . . . . 177
Connecting to ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 178
viii Table of Contents
Chapter 10: Registering the Informatica Server . . . . . . . . . . . . . . . 183
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Registering the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Informatica Server Code Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Server Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Steps for Registering an Informatica Server . . . . . . . . . . . . . . . . . . . . . 188
Chapter 11: Upgrading a Repository . . . . . . . . . . . . . . . . . . . . . . . . 191
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Chapter 12: Using ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
ODBC and the Informatica Client and Server . . . . . . . . . . . . . . . . . . . . . . 196
Database ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Client ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Server ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Creating an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Configuring ODBC for Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . 202
Configuring ODBC for Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Configuring ODBC for Microsoft SQL Server . . . . . . . . . . . . . . . . . . 203
Configuring an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Deleting an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Appendix A: Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Code Page Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Informatica Code Page Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Supported Code Pages and Related Code Pages . . . . . . . . . . . . . . . . . . 216
Converting from MS Latin1 to Latin1 . . . . . . . . . . . . . . . . . . . . . . . . 225
Converting from Latin1 to MS Latin1 . . . . . . . . . . . . . . . . . . . . . . . . 225
Converting from IBM EBCDIC US English to Latin1 . . . . . . . . . . . . . 226
Converting from Latin1 to IBM EBCDIC US English . . . . . . . . . . . . . 227
Converting from MS Shift JIS to JapanEUC . . . . . . . . . . . . . . . . . . . . 227
Tabl e of Contents ix
Converting from JapanEUC to MS Shift JIS . . . . . . . . . . . . . . . . . . . . 230
Converting from IBM EBCDIC Japanese to JapanEUC . . . . . . . . . . . . 235
Converting from JapanEUC to IBM EBCDIC Japanese . . . . . . . . . . . . 236
Converting from IBM EBCDIC Japanese to MS Shift JIS . . . . . . . . . . 241
Converting from MS Shift JIS to IBM EBCDIC Japanese . . . . . . . . . . 242
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
x Table of Contents
List of Fi gures xi
List of Figures
Figure 1-1. PowerCenter/PowerMart Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 1-2. Connectivity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 1-3. Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 1-4. Repository Manager Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 1-5. Sample Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 1-6. Designer Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 1-7. Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 1-8. Debugger Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 1-9. Workflow Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 1-10. Workflow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2-1. PowerCenter and PowerMart Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 3-1. Required Code Page Relationships for Unicode Data Movement Mode . . . . . . . . . 39
Figure 3-2. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 3-3. 7-bit ASCII Mode Case Study Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 3-4. ASCII Case Study Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 3-5. ISO 8859-1 Case Study Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 3-6. Summary of ISO 8859-1 Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 12-1. ODBC Connectivity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 12-2. ODBC Microsoft Excel Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 12-3. ODBC Sybase Driver Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 12-4. ODBC Microsoft SQL Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
xii Li st of Fi gures
Li st of Tabl es xi ii
List of Tables
Table 2-1. Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 2-2. Informatica Client Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 2-3. Native Connect String Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 2-4. Repository Server Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 2-5. Informatica Server Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 3-1. Session and File Cache Handling After Data Movement Mode Change . . . . . . . . . 34
Table 3-2. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 4-1. ODBC Drivers for Source and Target Databases . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 4-2. Informatica Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 4-3. Informix SetNet32 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 5-1. Repository Server Configuration Parameters on Windows . . . . . . . . . . . . . . . . . . . 83
Table 5-2. Informix SetNet32 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 6-1. Library Path for Repository Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 6-2. Configuration Parameters for Repository Server on UNIX . . . . . . . . . . . . . . . . . . 103
Table 6-3. Library Path for Repository Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 7-1. Repository Database Connectivity Configuration . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 7-2. Repository Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 7-3. Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 8-1. Installation Parameters for Informatica Server on Windows . . . . . . . . . . . . . . . . . 129
Table 8-2. Keys Configuration for Informatica Server on Windows . . . . . . . . . . . . . . . . . . . 132
Table 8-3. Server Configuration for Informatica Server on Windows . . . . . . . . . . . . . . . . . . 133
Table 8-4. Repository Configuration for Informatica Server on Windows . . . . . . . . . . . . . . . 135
Table 8-5. Compatibility and Database Configuration for Informatica NT Server . . . . . . . . . 136
Table 8-6. Miscellaneous Configuration for Informatica Server on Windows . . . . . . . . . . . . 138
Table 8-7. Informix SetNet32 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 9-1. Library Path for Informatica Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Table 9-2. Configuration Parameters for Informatica Server on UNIX . . . . . . . . . . . . . . . . . 162
Table 9-3. Library Path for Informatica Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 10-1. TCP/IP Settings to Register a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 12-1. ODBC Connection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 12-2. Database ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Table 12-3. Informatica Client ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 12-4. Informatica Server ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table A-1. Code Page Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Table A-2. Code Pages by Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Table A-3. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Table A-4. Compatible Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Table A-5. Supported Code Pages and Related Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table A-6. MS Latin1 to Latin1 Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Table A-7. Latin1 to MS Latin1 Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
xiv Li st of Tabl es
Table A-8. IBM EBCDIC US English to Latin1 Character Conversion . . . . . . . . . . . . . . . . . .226
Table A-9. Latin1 to IBM EBCDIC US English Character Conversion . . . . . . . . . . . . . . . . . .227
Table A-10. MS Shift JIS to JapanEUC Character Conversion . . . . . . . . . . . . . . . . . . . . . . . .227
Table A-11. JapanEUC to MS Shift JIS Character Conversion . . . . . . . . . . . . . . . . . . . . . . . .230
Table A-12. IBM EBCDIC Japanese to JapanEUC Character Conversion . . . . . . . . . . . . . . . .235
Table A-13. JapanEUC to IBM EBCDIC Japanese Character Conversion . . . . . . . . . . . . . . . .236
Table A-14. IBM EBCDIC Japanese to MS Shift JIS Character Conversion . . . . . . . . . . . . . .241
Table A-15. MS Shift JIS to IBM EBCDIC Japanese Character Conversion . . . . . . . . . . . . . .242
xv
Preface
Welcome to PowerCenterRT, PowerCenter, and PowerMart, Informaticas integrated suite of
software products that delivers an open, scalable data integration solution addressing the
complete life cycle for data warehouse and analytic application development. PowerCenter
and PowerMart combine the latest technology enhancements for reliably managing data
repositories and delivering information resources in a timely, usable, and efficient manner.
The PowerCenter/PowerMart metadata repository coordinates and drives a variety of core
functions including extracting, transforming, loading, and managing. The Informatica Server
can extract large volumes of data from multiple platforms, handle complex transformations
on the data, and support high-speed loads. PowerCenter and PowerMart can simplify and
accelerate the process of moving data warehouses from development to test to production.
Note: Unless otherwise indicated, when this guide mentions PowerCenter, it refers to both
PowerCenter and PowerCenterRT.
xvi Preface
New Features and Enhancements
This section describes new features and enhancements to PowerCenter 6.0 and PowerMart
6.0.
Designer
Compare objects. The Designer allows you to compare two repository objects of the same
type to identify differences between them. You can compare sources, targets,
transformations, mapplets, mappings, instances, or mapping/mapplet dependencies in
detail. You can compare objects across open folders and repositories.
Copying objects. In each Designer tool, you can use the copy and paste functions to copy
objects from one workspace to another. For example, you can select a group of transformations
in a mapping and copy them to a new mapping.
Custom tools. The Designer allows you to add custom tools to the Tools menu. This
allows you to start programs you use frequently from within the Designer.
Flat file targets. You can create flat file target definitions in the Designer to output data to
flat files. You can create both fixed-width and delimited flat file target definitions.
Heterogeneous targets. You can create a mapping that outputs data to multiple database
types and target types. When you run a session with heterogeneous targets, you can specify
a database connection for each relational target. You can also specify a file name for each
flat file or XML target.
Link paths. When working with mappings and mapplets, you can view link paths. Link paths
display the flow of data from a column in a source, through ports in transformations, to a
column in the target.
Linking ports. You can now specify a prefix or suffix when automatically linking ports between
transformations based on port names.
Lookup cache. You can use a dynamic lookup cache in a Lookup transformation to insert
and update data in the cache and target when you run a session.
Mapping parameter and variable support in lookup SQL override. You can use mapping
parameters and variables when you enter a lookup SQL override.
Mapplet enhancements. Several mapplet restrictions are removed. You can now include
multiple Source Qualifier transformations in a mapplet, as well as Joiner transformations
and Application Source Qualifier transformations for IBM MQSeries. You can also include
both source definitions and Input transformations in one mapplet. When you work with a
mapplet in a mapping, you can expand the mapplet to view all transformations in the
mapplet.
Metadata extensions. You can extend the metadata stored in the repository by creating
metadata extensions for repository objects. The Designer allows you to create metadata
extensions for source definitions, target definitions, transformations, mappings, and
mapplets.
New Features and Enhancements xvii
Numeric and datetime formats. You can define formats for numeric and datetime values
in flat file sources and targets. When you define a format for a numeric or datetime value,
the Informatica Server uses the format to read from the file source or to write to the file
target.
Pre- and post-session SQL. You can specify pre- and post-session SQL in a Source Qualifier
transformation and in a mapping target instance when you create a mapping in the Designer.
The Informatica Server issues pre-SQL commands to the database once before it runs the
session. Use pre-session SQL to issue commands to the database such as dropping indexes
before extracting data. The Informatica Server issues post-session SQL commands to the
database once after it runs the session. Use post-session SQL to issue commands to a database
such as re-creating indexes.
Renaming ports. If you rename a port in a connected transformation, the Designer propagates
the name change to expressions in the transformation.
Sorter transformation. The Sorter transformation is an active transformation that allows
you to sort data from relational or file sources in ascending or descending order according
to a sort key. You can increase session performance when you use the Sorter transformation
to pass data to an Aggregator transformation configured for sorted input in a mapping.
Tips. When you start the Designer, it displays a tip of the day. These tips help you use the
Designer more efficiently. You can display or hide the tips by choosing Help-Tip of the
Day.
Tool tips for port names. Tool tips now display for port names. To view the full contents
of the column, position the mouse over the cell until the tool tip appears.
View dependencies. In each Designer tool, you can view a list of objects that depend on a
source, source qualifier, transformation, or target. Right-click an object and select the View
Dependencies option.
Working with multiple ports or columns. In each Designer tool, you can move multiple ports
or columns at the same time.
Informatica Server
Add timestamp to workflow logs. You can configure the Informatica Server to add a
timestamp to messages written to the workflow log.
Expanded pmcmd capability. You can use pmcmd to issue a number of commands to the
Informatica Server. You can use pmcmd in either an interactive or command line mode.
The interactive mode prompts you to enter information when you omit parameters or
enter invalid commands. In both modes, you can enter a command followed by its
command options in any order. In addition to commands for starting and stopping
workflows and tasks, pmcmd now has new commands for working in the interactive mode
and getting details on servers, sessions, and workflows.
Error handling. The Informatica Server handles the abort command like the stop
command, except it has a timeout period. You can specify when and how you want the
Informatica Server to stop or abort a workflow by using the Control task in the workflow.
After you start a workflow, you can stop or abort it through the Workflow Monitor or
pmcmd.
xviii Preface
Export session log to external library. You can configure the Informatica Server to write
the session log to an external library.
Flat files. You can specify the precision and field length for columns when the Informatica
Server writes to a flat file based on a flat file target definition, and when it reads from a flat
file source. You can also specify the format for datetime columns that the Informatica
Server reads from flat file sources and writes to flat file targets.
Write Informatica Windows Server log to a file. You can now configure the Informatica
Server on Windows to write the Informatica Server log to a file.
Metadata Reporter
List reports for jobs, sessions, workflows, and worklets. You can run a list report that lists
all jobs, sessions, workflows, or worklets in a selected repository.
Details reports for sessions, workflows, and worklets. You can run a details report to view
details about each session, workflow, or worklet in a selected repository.
Completed session, workflow, or worklet detail reports. You can run a completion details
report, which displays details about how and when a session, workflow, or worklet ran, and
whether it ran successfully.
Installation on WebLogic. You can now install the Metadata Reporter on WebLogic and
run it as a web application.
Repository Manager
metadata extensions for repository objects. The Repository Manager allows you to create
metadata extensions for source definitions, target definitions, transformations, mappings,
mapplets, sessions, workflows, and worklets.
pmrep security commands. You can use pmrep to create or delete repository users and
groups. You can also use pmrep to modify repository privileges assigned to users and
groups.
Tips. When you start the Repository Manager, it displays a tip of the day. These tips help
you use the Repository Manager more efficiently. You can display or hide the tips by
choosing Help-Tip of the Day.
Repository Server
The Informatica Client tools and the Informatica Server now connect to the repository
database over the network through the Repository Server.
Repository Server. The Repository Server manages the metadata in the repository
database. It accepts and manages all repository client connections and ensures repository
consistency by employing object locking. The Repository Server can manage multiple
repositories on different machines on the network.
New Features and Enhancements xi x
Repository connectivity changes. When you connect to the repository, you must specify
the host name of the machine hosting the Repository Server and the port number the
Repository Server uses to listen for connections. You no longer have to create an ODBC
data source to connect a repository client application to the repository.
Transformation Language
New functions. The transformation language includes two new functions, ReplaceChr and
ReplaceStr. You can use these functions to replace or remove characters or strings in text
data.
SETVARIABLE. The SETVARIABLE function now executes for rows marked as insert or
update.
Workflow Manager
The Workflow Manager and Workflow Monitor replace the Server Manager. Instead of
creating a session, you now create a process called a workflow in the Workflow Manager. A
workflow is a set of instructions on how to execute tasks such as sessions, emails, and shell
commands. A session is now one of the many tasks you can execute in the Workflow Manager.
The Workflow Manager provides other tasks such as Assignment, Decision, and Event-Wait
tasks. You can also create branches with conditional links. In addition, you can batch
workflows by creating worklets in the Workflow Manager.
DB2 external loader. You can use the DB2 EE external loader to load data to a DB2 EE
database. You can use the DB2 EEE external loader to load data to a DB2 EEE database.
The DB2 external loaders can insert data, replace data, restart load operations, or
terminate load operations.
Environment SQL. For relational databases, you may need to execute some SQL
commands in the database environment when you connect to the database. For example,
you might want to set isolation levels on the source and target systems to avoid deadlocks.
You configure environment SQL in the database connection. You can use environment
SQL for source, target, lookup, and stored procedure connections.
Email. You can create email tasks in the Workflow Manager to send emails when you run a
workflow. You can configure a workflow to send an email anywhere in the workflow logic,
including after a session completes or after a session fails. You can also configure a
workflow to send an email when the workflow suspends on error.
Flat file targets. In the Workflow Manager, you can output data to a flat file from either a
flat file target definition or a relational target definition.
Heterogeneous targets. You can output data to different database types and target types in
the same session. When you run a session with heterogeneous targets, you can specify a
database connection for each relational target. You can also specify a file name for each flat
file or XML target.
xx Preface
metadata extensions for repository objects. The Workflow Manager allows you to create
metadata extensions for sessions, workflows, and worklets.
Oracle 8 direct path load support. You can load data directly to Oracle 8i in bulk mode
without using an external loader. You can load data directly to an Oracle client database
version 8.1.7.2 or higher.
Partitioning enhancements. To improve session performance, you can set partition points
at multiple transformations in a pipeline. You can also specify different partition types at
each partition point.
Server variables. You can use new server variables to define the workflow log directory and
workflow log count.
Teradata TPump external loader. You can use the Teradata TPump external loader to load
data to a Teradata database. You can use TPump in sessions that contain multiple
partitions.
Tips. When you start the Workflow Manager, it displays a tip of the day. These tips help
you use the Workflow Manager more efficiently. You can display or hide the tips by
choosing Help-Tip of the Day.
Workflow log. In addition to session logs, you can configure the Informatica Server to
create a workflow log to record details about workflow runs.
Workflow Monitor. You use a tool called the Workflow Monitor to monitor workflows,
worklets, and tasks. The Workflow Monitor displays information about workflow runs in
two views: Gantt Chart view or Task view. You can run, stop, abort, and resume workflows
from the Workflow Monitor.
About Inf ormat ica Document ati on xxi
About Informatica Documentation
The complete set of printed documentation for PowerCenterRT, PowerCenter, and
PowerMart includes the following books:
Designer Guide. Provides information needed to use the Designer. Includes information to
help you create mappings, mapplets, and transformations. Also includes a description of
the transformation datatypes used to process and transform source data.
Getting Started. Provides basic tutorials for getting started. Also contains documentation
about the sample repository.
Installation and Configuration Guide. Provides information needed to install and
configure the PowerCenter and PowerMart tools, including details on environment
variables and database connections.
Metadata Reporter Guide. Provides information on how to install and use the web-based
Metadata Reporter to generate reports on the metadata in PowerCenter and PowerMart
repositories.
Repository Guide. Provides information needed to administer the repository using the
Repository Manager or the pmrep command line program. Includes details on
functionality available in the Repository Manager, such as creating and maintaining
repositories, folders, users, groups, and permissions and privileges.
Transformation Language Reference. Provides syntax descriptions and examples for each
transformation function provided with PowerCenter and PowerMart.
Transformation Guide. Provides information on how to create and configure each type of
transformation in the Designer.
Troubleshooting Guide. Lists error messages that you might encounter while using
PowerCenter or PowerMart. Each error message includes one or more possible causes and
actions that you can take to correct the condition.
Workflow Administration Guide. Provides information to help you create and run
workflows in the Workflow Manager, as well as monitor workflows in the Workflow
Monitor. Also contains information on administering the Informatica Server and
performance tuning.
Documentation available with our other products includes:
Informatica
Metadata Exchange SDK User Guide. Provides information about the

second generation of Metadata Exchange interfaces for PowerCenter and PowerMart
repositories.
Informatica
PowerChannel
User Guide. Provides information on how to transport

compressed and encrypted data through a secure channel.
PowerConnect
for IBM
MQSeries
User and Administrator Guide. Provides

information to install PowerConnect for IBM MQSeries, build mappings, extract data
from message queues, and load data to message queues.
xxii Preface
PowerConnect
for PeopleSoft
User and Administrator Guide. Provides information to

install PowerConnect for PeopleSoft, extract data from PeopleSoft systems, build
mappings, and run workflows to load PeopleSoft source data into a warehouse.
PowerConnect
for SAP
BW User and Administrator Guide. Provides information to

install and configure PowerConnect for SAP BW to load source data into an SAP Business
Information Warehouse.
PowerConnect
for SAP
R/3

Analytic Business Components
Guide. Provides
information on installing and working with Analytic Business Components for
PowerConnect for SAP R/3, including descriptions of repository objects and how you can
use them to load a data warehouse.
PowerConnect
for SAP
R/3

install PowerConnect for SAP R/3, build mappings, and run workflows to extract data
from SAP R/3 and load data into SAP R/3.
PowerConnect
for Siebel

install PowerConnect for Siebel, extract data from Siebel systems, build mappings, and run
workflows to load Siebel source data into a data warehouse.
PowerConnect
for TIBCO

install PowerConnect for TIBCO, build mappings, extract data from TIBCO messages,
and load data into TIBCO messages.
PowerConnect
Software Development Kit Developer Guide. Provides information to

install PowerConnect SDK and build plug-ins to extract data from third-party applications
and load data into third-party applications.
Metadata Exchange for Data Models User Guide. Provides information on how to extract
metadata from leading data modeling tools and import it into PowerCenter/PowerMart
repositories through Informatica Metadata Exchange SDK.
Metadata Exchange for OLAP User Guide. Provides information on how to use export
multi-dimensional metadata from PowerCenter/PowerMart repositories into the Hyperion
Integration Server through Informatica Metadata Exchange SDK.
About thi s Book xxi ii
About this Book
The Installation and Configuration Guide is written for the system administrators who are
responsible for installing and configuring the PowerCenter or PowerMart product. This guide
assumes you have knowledge of your operating systems, relational database concepts, and the
database engines, flat files, or mainframe systems in your environment. This guide also
assumes you are familiar with the interface requirements for your supporting applications.
The material in this book is available for online use.
About PowerCenter and PowerMart
This guide contains information about PowerCenterRT, PowerCenter, and PowerMart. The
documentation explicitly mentions software features that differ between the products.
If You Are Using PowerCenterRT
With PowerCenterRT, you receive all product functionality, including the ability to register
multiple servers, share metadata across repositories, and partition pipelines. PowerCenterRT
includes the Zero Latency engine, which enables real-time, high performance, data
integration for business analytics and operational data stores.
A PowerCenterRT license lets you create a single repository that you can configure as a global
repository, the core component of a PowerCenterRT domain.
When this guide mentions a PowerCenterRT Server, it is referring to an Informatica Server
with a PowerCenterRT license.
If You Are Using PowerCenter
With PowerCenter, you receive all product functionality, including the ability to register
multiple servers, share metadata across repositories, and partition pipelines.
A PowerCenter license lets you create a single repository that you can configure as a global
repository, the core component of a PowerCenter domain.
When this guide mentions a PowerCenter Server, it is referring to an Informatica Server with
a PowerCenter license.
If You Are Using PowerMart
This version of PowerMart includes all features except distributed metadata, multiple
registered servers, and pipeline partitioning. Also, the various PowerConnect products
available with PowerCenter or PowerCenterRT are not available with PowerMart.
When this guide mentions a PowerMart Server, it is referring to an Informatica Server with a
PowerMart license.
xxiv Preface
Document Conventions
This guide uses the following formatting conventions:
If you see It means
italicized text
The word or set of words are especially emphasized.
boldfaced text
Emphasized subjects.
italicized monospaced text This is the variable name for a value you enter as part of an
operating system command. This is generic text that should be
replaced with user-supplied values.
Note: The following paragraph provides additional facts.
Tip: The following paragraph provides suggested uses.
Warning: The following paragraph notes situations where you can overwrite
or corrupt data, unless you follow the specified procedure.
monospaced text This is a code example.
bold monospaced text This is an operating system command you enter from a prompt to
execute a task.
Other Informat ica Resources xxv
Other Informatica Resources
In addition to the product manuals, Informatica provides these other resources:
Informatica Webzine
Informatica web site
Informatica Developer Network
Informatica Technical Support
Accessing the Informatica Webzine
The Informatica Documentation Team delivers an online journal, the Informatica Webzine.
This journal provides solutions to common tasks, conceptual overviews of industry-standard
technology, detailed descriptions of specific features, and tips and tricks to help you develop
data warehouses.
The Informatica Webzine is a password-protected site that you can access through the
Customer Portal. The Customer Portal has an online registration form for login accounts to
its webzine and web support. To register for an account, go to the following URL:
http://my.Informatica.com/
If you have any questions, please email webzine@informatica.com.
To better serve your needs, the Informatica Documentation Team welcomes all comments and
suggestions. You can send comments and suggestions to:
documentation@informatica.com
Visiting the Informatica Web Site
You can access Informaticas corporate web site at http://www.informatica.com. The site
contains information about Informatica, its background, upcoming events, and locating your
closest sales office. You will also find product information, as well as literature and partner
information. The services area of the site includes important information on technical
support, training and education, and implementation services.
Visiting the Informatica Developer Network
The Informatica Developer Network is a web-based forum for third-party software
developers. You can access the Informatica Developer Network at
http://devnet.informatica.com. The site contains information on how to create, market, and
support customer-oriented add-on solutions based on Informaticas interoperability
interfaces.
xxvi Preface
Obtaining Technical Support
There are many ways to access Informatica technical support. You can call or email your
nearest Technical Support Center listed below or you can use our WebSupport Service.
Both WebSupport and our Customer Site require a user name and password. To receive a user
name and password, please contact us at support@informatica.com or call 866-563-6332 or
650-385-5800.
North America / South America Africa / Asia / Australia / Europe
Informatica Corporation
2100 Seaport Blvd.
Redwood City, CA 94063
Phone: 866.563.6332 or 650.385.5800
Fax: 650.213.9489
Hours: 6 a.m. - 6 p.m. (PST/PDT)
email: support@informatica.com
Informatica Software Ltd.
6 Waltham Park
Waltham Road, White Waltham
Maidenhead, Berkshire
SL6 3TN
Phone: 44 870 606 1525
Fax: +44 1628 511 411
Hours: 9 a.m. - 5:30 p.m. (GMT)
email: support_eu@informatica.com
Belgium
Phone: +32 15 281 702
Hours: 9 a.m. - 5:30 p.m. (local time)
France
Phone: +33 1 41 38 92 26
Germany
Phone: +49 1805 702 702
Netherlands
Phone: +31 306 082 089
Singapore
Phone: +65 322 8589
Hours: 9 a.m. - 5 p.m. (local time)
Switzerland
Phone: +41 800 81 80 70
Hours: 8 a.m. - 5 p.m. (local time)
1
C h a p t e r 1
Product Overview
This chapter covers the following topics:
Introduction, 2
Using the Repository Manager, 7
The Design Process, 10
Loading Data, 14
Getting Started, 17
2 Chapter 1: Product Overview
Introduction
PowerCenter and PowerMart provide an environment that allows you to load data into a
centralized location, such as a datamart, data warehouse, or operational data store (ODS).
You can extract data from multiple sources, transform the data according to business logic you
build in the client application, and load the transformed data into file and relational targets.
Informatica provides the following integrated components:
Informatica repository. The Informatica repository is at the center of the Informatica
suite. You create a set of metadata tables within the repository database that the
Informatica applications and tools access. The Informatica Client and Server access the
repository to save and retrieve metadata.
Informatica Repository Server. The Informatica Repository Server manages connections
to the repository from client applications. It inserts, updates, and fetches objects from the
repository database tables. It also maintains object consistency.
Informatica Client. Use the Informatica Client to manage users, define sources and
targets, build mappings and mapplets with the transformation logic, and create workflows
to run the mapping logic. The Informatica Client has four client applications: Repository
Manager, Designer, Workflow Manager, and Workflow Monitor.
Informatica Server. The Informatica Server extracts the source data, performs the data
transformation, and loads the transformed data into the targets.
Figure 1-1 illustrates the architecture of PowerCenter and PowerMart:
Sources
PowerCenter and PowerMart access the following sources:
Relational. Oracle, Sybase, Informix, IBM DB2, Microsoft SQL Server, and Teradata.
Figure 1-1. PowerCenter/PowerMart Architecture
Server Source Target
Repository
Instructions
from
metadata
Source
data
Transformed
data
Introducti on 3
File. Fixed and delimited flat file, COBOL file, and XML.
Application. If you use PowerCenter, you can purchase additional PowerConnect products
to access business sources such as PeopleSoft, SAP R/3, Siebel, IBM MQSeries, and Tibco.
Mainframe. If you use PowerCenter, you can purchase PowerConnect for Mainframe for
faster access to IBM DB2 on MVS.
Other. Microsoft Excel and Access.
Note: The Designer imports relational sources, such as Microsoft Excel, Microsoft Access, and
Teradata using ODBC and native drivers.
For more information about sources, see Working with Sources in the Designer Guide.
Targets
PowerCenter and PowerMart can load data into the following targets:
Relational. Oracle, Sybase, Sybase IQ, Informix, IBM DB2, Microsoft SQL Server, and
Teradata.
File. Fixed and delimited flat file and XML.
Application. If you use PowerCenter, you can purchase additional PowerConnect products
to load data into SAP BW. You can also load data into IBM MQSeries message queues and
Tibco.
Other. Microsoft Access.
You can load data into targets using ODBC or native drivers, FTP, or external loaders.
For more information about targets, see Working with Targets in the Designer Guide.
Repository
The Informatica repository resides on a relational database. The repository database tables
contain the instructions required to extract, transform, and load data. Informatica client
applications access the repository database tables through the Repository Server.
You add metadata to the repository tables when you perform tasks in the Informatica Client
application such as creating users, analyzing sources, developing mappings or mapplets, or
creating workflows. The Informatica Server reads metadata created in the Client application
when you run a workflow. The Informatica Server also creates metadata such as start and
finish times of a session or session status.
When you use PowerCenter, you can develop global and local repository to share metadata:
Global repository. The global repository is the hub of the domain. Use the global
repository to store common objects that multiple developers can use through shortcuts.
These objects may include operational or Application source definitions, reusable
transformations, mapplets, and mappings.
Local repositories. A local repository is within a domain that is not the global repository.
Use local repositories for development. From a local repository, you can create shortcuts to
objects in shared folders in the global repository. These objects typically include source
definitions, common dimensions and lookups, and enterprise standard transformations.
You can also create copies of objects in non-shared folders.
You can connect to a repository, back up, delete, or restore repositories using pmrep, a
command line program. For more information on pmrep, see Using pmrep in the Repository
Guide.
For more information about global repositories, see Understanding the Repository in the
Repository Guide.
You can view much of the metadata in the Repository Manager. You can also through the
Metadata Reporter. For more information about the Metadata Reporter, see the Metadata
Reporter Guide.
Repository Server
The Repository Server manages repository connection requests from client applications. For
each repository database registered with the Repository Server, it configures and manages a
Repository Agent process. The Repository Server also monitors the status of running
Repository Agents, and sends repository object notification messages to client applications.
The Repository Agent is a separate, multi-threaded process that accepts performs the action
needed to retrieve, insert, and update metadata in the repository database tables. The
Repository Agent ensures the consistency of metadata in the repository by employing object
locking.
For more information about the Repository Server, see Understanding the Repository in the
Repository Guide.
Informatica Client
The Informatica Client is comprised of three applications that you use to manage the
repository, design mappings, mapplets, and create sessions to load the data.
Repository Manager. Use the Repository Manager to create and administer the metadata
repository. You can create repository users and groups, assign privileges and permissions,
and manage folders and locks.
Designer. Use the Designer to create mappings that contain transformation instructions
for the Informatica Server. Before you can create mappings, you must add source and
target definitions to the repository. The Designer has five tools that you use to analyze
sources, design target schemas, and build source-to-target mappings:
Source Analyzer. Import or create source definitions.
Warehouse Designer. Import or create target definitions.
Transformation Developer. Develop reusable transformations to use in mappings.
Mapplet Designer. Create sets of transformations to use in mappings.
Introducti on 5
Mapping Designer. Create mappings that the Informatica Server uses to extract,
transform, and load data.
Workflow Manager. Use the Workflow Manager to create, schedule, and run workflows. A
workflow is a set of instructions that describes how and when to run tasks related to
extracting, transforming, and loading data. The Informatica Server runs workflow tasks
(such as the Session task) according to the links connecting the tasks. You can run a task by
placing it in a workflow.
Workflow Monitor. Use the Workflow Monitor to monitor scheduled and running
workflows for each Informatica Server. You can choose a Gantt Chart or Task view. You
can also access details about those workflow runs.
Install the client tools on a Microsoft Windows machine. For more information about
installation requirements, see Installation and Configuration Overview in the Installation
and Configuration Guide.
Informatica Server
The Informatica Server reads mapping and session information from the repository. It extracts
data from the mapping sources and stores the data in memory while it applies the
transformation rules that you configure in the mapping. The Informatica Server loads the
transformed data into the mapping targets.
The Informatica Server can achieve high performance using symmetric multi-processing
systems. The Informatica Server can start and run multiple workflows concurrently. It can
also concurrently process partitions within a single session. When you create multiple
partitions within a session, the Informatica Server creates multiple database connections to a
single source and extracts a separate range of data for each connection, according to the
properties you configure.
The Informatica Server manages the scheduling and execution of workflows. It moves data
from sources to targets based on mapping and session information stored in the repository.
You can install the Informatica Server on a Windows or UNIX server machine. For more
information about installation requirements, see Installation and Configuration Overview
in the Installation and Configuration Guide.
You can communicate with the Informatica Server using the pmcmd program. For more
information, see Using pmcmd in the Workflow Administration Guide.
Connectivity
PowerCenter and PowerMart use the following types of connectivity:
Network protocol
Native drivers
ODBC
The Informatica Client uses ODBC and native drivers to connect to source and target
databases. It uses TCP/IP to connect to the Repository Server. The Repository Server uses
native drivers to connect to the repository database. The Workflow Manager and the
Informatica Server use TCP/IP to communicate with each other.
The Informatica Server uses native drivers to connect to the databases to move data. You can
optionally use ODBC to connect the Informatica Server to the source and target databases. It
uses TCP/IP to connect to the Informatica Client.
Figure 1-2 shows the connectivity used within the PowerCenter/PowerMart architecture:
Metadata Reporter
PowerCenter and PowerMart provide the Metadata Reporter, a web-based application that
allows you to run reports against repository metadata. It gives you insight into your repository
that enhances your ability to analyze and manage your repository efficiently.
The Metadata Reporter provides a number of reports, including reports on executed sessions,
lookup table dependencies, mappings, and source or target schemas.
You can install the Metadata Reporter on a server with any type of operating system running a
compatible web server. You can run the Metadata Reporter from a browser on any
workstation, even without the Informatica tools installed on the workstation. For more
information, see the Metadata Reporter Guide.
Figure 1-2. Connectivity Overview
Usi ng the Reposit ory Manager 7
Using the Repository Manager
Use the Repository Manager to administer your repositories. The Repository Manager allows
you to navigate through multiple folders and repositories, and perform the following tasks:
Manage the repository. You can perform repository management functions such as
copying, creating, starting, and shutting down repositories. You connect to the Repository
Server to perform these functions.
Implement repository security. You can create, edit, and delete repository users and user
groups. You can assign and revoke repository privileges and folder permissions.
Perform folder functions. You can create, edit, copy, and delete folders. All the work you
perform in the Designer is stored in folders. If you want to share metadata, you can
configure a folder to be shared.
View metadata. You can analyze sources, targets, mappings, and shortcut dependencies,
search by keyword, and view the properties of repository objects.
Customize the Repository Manager. You can add, edit, and remove repositories in the
Navigator, view or hide windows.
For more information about the repository and the Repository Manager, see the Repository
Guide.
Repository Manager Windows
The Repository Manager can display the following windows:
Navigator. Displays all objects that you create in the Repository Manager, the Designer,
and the Workflow Manager. It is organized first by repository, then by folder and folder
version. Viewable objects include sources, targets, dimensions, cubes, mappings, mapplets,
transformations, sessions, and workflows. You can also view folder versions and business
components.
Main. Provides properties of the object selected in the Navigator window. The columns in
this window change depending on the object selected in the Navigator window.
Dependency. Shows dependencies on sources, targets, mappings, and shortcuts for objects
selected in either the Navigator or Main window.
Output. Provides the output of tasks executed within the Repository Manager, such as
creating a repository.
Figure 1-3 shows the windows in the Repository Manager:
Figure 1-3. Repository Manager Windows
Navigator
Status Bar
Main
Output
Dependency
Usi ng the Reposit ory Manager 9
Figure 1-4 shows the Repository Manager Navigator:
Repository Objects
You create repository objects using the Repository Manager, Designer, and Workflow
Manager client tools. You can view the following objects in the Navigator window of the
Repository Manager:
Source definitions. Definitions of database objects (tables, views, synonyms) or files that
provide source data.
Target definitions. Definitions of database objects or files that contain the target data.
Multi-dimensional metadata. Target definitions that are configured as cubes and
dimensions.
Mappings. A set of source and target definitions along with transformations containing
business logic that you build into the transformation. These are the instructions that the
Informatica Server uses to transform and move data.
Reusable transformations. Transformations that you can use in multiple mappings.
Mapplets. A set of transformations that you can use in multiple mappings.
Sessions and workflows. Sessions and workflows store information about how and when
the Informatica Server moves data. A workflow is a set of instructions that describes how
and when to run tasks related to extracting, transforming, and loading data. A session is a
type of task that you can put in a workflow. Each session corresponds to a single mapping.
Figure 1-4. Repository Manager Navigator
Sessions
Mappings
Shared Folder
Repository
Nodes
Folders
Version
Worklets
Workflows
The Design Process
The goal of the design process is to create mappings that depict the flow of data between
sources and targets, including changes made to the data before it reaches the targets. However,
before you can create a mapping, you must first create or import source and target definitions.
You might also want to create reusable objects such as reusable transformations or mapplets.
For a list of objects you create in the Design process, see Repository Objects on page 9.
Perform the following design tasks in the Designer:
1. Import source definitions. Use the Source Analyzer to connect to the sources and import
the source definitions.
2. Create or import target definitions. Use the Warehouse Designer to define relational,
flat file, or XML targets to receive data from sources. You can import target definitions
from a relational database or a flat file, or you can manually create a target definition.
3. Create the target tables. If you add a target definition to the repository that does not
exist in a relational database, you need to create target tables in your target database. You
do this by generating and executing the necessary SQL code within the Warehouse
Designer.
4. Design mappings. Once you have source and target definitions in the repository, you can
create mappings in the Mapping Designer. A mapping is a set of source and target
definitions linked by transformation objects that define the rules for data transformation.
A transformation is an object that performs a specific function in a mapping, such as
looking up data or performing aggregation.
5. Create mapping objects. Optionally, you can create reusable objects for use in multiple
mappings. Use the Transformation Developer to create reusable transformations. Use the
Mapplet Designer to create mapplets. A mapplet is a set of transformations that may
contain sources and transformations.
6. Debug mappings. Use the Mapping Designer to debug a valid mapping to gain
troubleshooting information about data and error conditions.
7. Import and export repository objects. You can import and export repository objects,
such as sources, targets, transformations, mapplets, and mappings to archive or share
metadata.
Figure 1-5 shows a sample mapping with source and target definitions and transformations:
For more information about the Designer, see the Designer Guide.
Figure 1-5. Sample Mapping
Source Definition Transformations Target Definition
The Desi gn Process 11
Designer Windows
You can display the following windows in the Designer:
Navigator. Connect to repositories, and open folders within the Navigator. You can also
copy objects and create shortcuts within the Navigator.
Workspace. Open different tools in this window to create and edit repository objects such
as sources, targets, mapplets, transformations, and mappings.
Output. View details about tasks you perform, such as saving your work or validating a
mapping.
Status bar. Displays the status of the operation you perform.
Overview. An optional window to simplify viewing a workspace that contains a large
mapping or multiple objects. Outlines the visible area in the workspace and highlights
selected objects in color.
Instance data. View transformation data while you run the Debugger to debug a mapping.
Target data. View target data while you run the Debugger to debug a mapping.
Figure 1-6 shows the default Designer windows:
Figure 1-6. Designer Windows
Navigator
Workspace
Status Bar
Output
Figure 1-7 shows the Overview window:
Figure 1-7. Overview Window
Visible Area in
Workspace
Selected Objects
in Color
Overview Window
The Desi gn Process 13
Figure 1-8 shows the Debugger window in the Designer:
Figure 1-8. Debugger Window
Loading Data
In the Workflow Manager, you define a set of instructions to execute tasks such as sessions,
emails and shell commands. This set of instructions is called a workflow.
After you create a new workflow in the Workflow Designer, the next step is to add tasks to the
workflow. The Workflow Manager includes tasks such as the Session task, the Command task,
and the Email task so you can design your workflow. The Session task is based on a mapping
you build in the Designer.
You then connect tasks with links to specify the order of execution for the tasks you created.
Use conditional links and workflow variables to create branches in the workflow.
When the workflow start time arrives, the Informatica Server retrieves the metadata from the
repository to execute the tasks in the workflow.
You can monitor the workflow status in the Workflow Monitor.
Workflow Manager
The Workflow Manager consists of three tools to help you develop a workflow:
Task Developer. Create tasks you want to accomplish in the workflow in the Task
Developer.
Workflow Designer. Create a workflow by connecting tasks with links in the Workflow
Designer. You can also create tasks in the Workflow Designer as you develop the workflow.
Worklet Designer. Create a worklet in the Worklet Designer. A worklet is an object that
groups a set of tasks. A worklet is similar to a workflow, but without scheduling
information. You can execute a batch of worklets inside a workflow.
Before you create a workflow, you must configure the following connection information:
Informatica Server connection. Register the Informatica Server with the repository before
you can start it or create a session to run against it.
Database connections. Create connections to source and target systems.
Other connections. If you want to use external loaders or FTP, you configure these
connections in the Workflow Manager.
For more information about configuring the Workflow Manager, see Configuring the
Workflow Manager in the Workflow Administration Guide.
Workflow Manager Windows
The Workflow Manager displays the following windows to help you create and organize
workflows:
Navigator. Allows you to connect to and work in multiple repositories and folders.
Workspace. Allows you to create, edit, and view tasks, workflows, and worklets.
Loadi ng Dat a 15
Output. Displays messages from the Informatica Server and the Repository Server. The
Output window also displays messages when you save or validate task and workflows.
Overview. An optional window that makes it easier to view workbooks containing large
workflows. Outlines the visible area in the workspace and highlights selected objects in
color. Choose View-Overview Window to display this window.
The Workflow Manager also displays a status bar that shows the status of the operation you
perform.
Figure 1-9 shows the Workflow Manager windows:
Workflow Monitor
After you create a workflow, you run the workflow in the Workflow Manager and monitor it
in the Workflow Monitor. The Workflow Monitor is a tool that displays details about
workflow runs in two views: Gantt chart view and Task view. You can monitor workflows in
online and offline modes.
The Workflow Monitor consists of the following windows:
Navigator window. Displays monitored repositories, servers, and repositories objects.
Output window. Displays messages from the Informatica Server.
Time window. Displays progress of workflow runs.
Figure 1-9. Workflow Manager Windows
Navigator Workspace
Overview
Output
Status Bar
Gantt chart view. Displays details about workflow runs in chronological (Gantt chart)
format.
Task view. Displays details about workflow runs in a report format.
Figure 1-10 shows the Workflow Monitor:
Figure 1-10. Workflow Monitor
Time
Window
Output Window
Gantt
Chart
View
Task View
Navigator
window
Get ti ng Started 17
Getting Started
Before you can begin using PowerCenter or PowerMart, you must create the environment and
perform the following administration tasks to allow access to the repository and the
Informatica Server:
1. Configure the sources. If you extract from relational sources, ask the database
administrator to create user profiles with read access. This allows you to import source
definitions into the repository and access the sources at runtime.
If you extract from file sources, the files must be accessible to the Informatica Server and
Client machines.
2. Configure the targets. Ask the database administrator to create user profiles with read
and write access. This allows you to import target definitions into the repository and
write to the targets at runtime.
If the target database does not exist, create it using the database administration tools
included with your RDBMS. After you create the target database, you can use the
Designer to design and create target tables.
For flat file targets, you need a target directory large enough to process the resulting files.
3. Choose globalization settings and data movement modes. The data movement mode
you use depends on whether you want the Informatica Server to process single-byte data
or multibyte character data. You select code pages for the repository, Informatica Client
and Informatica Server.
4. Create repository database. Create a database for the repository. Users accessing the
repository database need full rights in that database. If you upgrade the repository to a
new version, you need database rights to drop or modify these tables.
5. Install the Informatica Client. Install the client software on a machine that accesses the
sources, targets, and repository databases, as well as the Informatica Server.
6. Install and configure the Repository Server. Install and configure the Repository Server
on a machine that accesses the repository database, the Informatica Client, and the
Informatica Server.
7. Install and configure the Informatica Server. Install the Informatica Server on a
Windows or UNIX system that accesses the sources, targets, and the repository database.
8. Configure connectivity. Configure network, native, and ODBC connectivity. Create
ODBC data sources to connect to the Informatica Clients to the sources and targets. You
must also have network connections between all databases and Informatica Servers.
9. Create the repository. After you configure connectivity between source, target, and
repository databases, you can create the metadata repository. Connect to the Repository
Server from within the Repository manager to create the metadata repository. The
Repository Server connects to the repository database and runs the SQL needed to create
the repository tables. All the objects you create with PowerCenter or PowerMart are
stored as metadata in the repository.
10. Create repository users and groups. Create groups and user profiles, then assign
privileges and permissions that determine tasks that users can perform.
11. Register the Informatica Server. Before you can start the Informatica Server you must
register the Informatica Server so the Workflow Manager can direct the Informatica
Server to the repository.
19
C h a p t e r 2
Installation and
Configuration Overview
This chapter includes the following topics:
Before You Begin, 20
PowerCenter and PowerMart Connectivity, 21
PowerCenter and PowerMart Installation Steps, 25
20 Chapter 2: Install ati on and Confi gurati on Overvi ew
Before You Begin
Installing and configuring PowerCenter and PowerMart requires some understanding of the
different components of the product. Before you begin installation, read:
Product Overview on page 1. This chapter provides an overview of the product and
product tools.
This chapter. Before you install the product, review the installation steps and connectivity
requirements.
Minimum System Requirements
Before you install PowerCenter or PowerMart, verify system requirements. For an updated list
of minimum system requirements, see Installing and Configuring PowerCenter and
PowerMart in the Supplemental Guide.
Table 2-1 shows the minimum system requirements to run PowerCenter or PowerMart:
Informatica recommends a screen resolution of 1024 x 768 or higher for all machines running
the Informatica Client.
Table 2-1. Minimum System Requirements
Informatica
Client
Repository Server
Informatica
Repository Database
Informatica Server
Operating
system
Windows 98,
Windows 2000,
Windows XP, or
Windows NT 4.0
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
(Solaris, HP-UX, AIX)
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
Disk space 70 MB 40 MB 100 MB of database
space*
40 MB
RAM 256 MB 32 MB
plus
16 MB per managed
repository
128 MB 256 MB
Database
connectivity
ODBC drivers Native drivers Native drivers Native drivers or
ODBC
* Although you can create a repository with a minimum of 100 MB of database space, Informatica recommends allocating up to 150 MB
for repositories.
PowerCenter and PowerMart Connecti vi ty 21
PowerCenter and PowerMart Connectivity
The following sections describe the necessary connections between the Informatica Client
tools, the repository, and the Informatica Server.
Figure 2-1 shows the PowerCenter and PowerMart components and connectivity:
For detailed information on configuring connectivity for the Informatica Client tools and
Informatica Server, see the appropriate installation chapters in this guide.
Informatica Client Connections
The Informatica Client uses two software layers to communicate with each source and target
database:
ODBC drivers
Native database client connectivity software
Informatica Client tools pass all source and target database calls to the ODBC driver, which
interprets the information and sends it to the native database client connectivity software.
From there the information passes to the database, which processes the command and sends
the desired information back to the Informatica Client tool.
For example, when you import a source definition in the Designer, the Designer issues a call
to the ODBC driver. The ODBC driver translates the call and passes it to the native database
connectivity software, which in turn passes it to the database. The database processes the
request and sends the information back to the Designer (passing through the native software
layer and ODBC software), which displays the source definition.
Figure 2-1. PowerCenter and PowerMart Connectivity
Informatica Client tools communicate with the repository through the Repository Server. The
Informatica Client tools connect to the Repository Server over TCP/IP.
For each database, make note of the native connect string that you define through the
database connectivity software. Reference these connect strings in the Informatica Server
configuration utility, Repository Manager, and Workflow Manager.
The Workflow Manager communicates directly with the Informatica Server each time you
schedule or edit a session, display session details, and request session logs. The Workflow
Manager communicates with the Informatica Server through TCP/IP. You create the
connection by defining the port number in the Workflow Manager and in the Informatica
Server configuration.
Table 2-2 summarizes the software you need to connect the Informatica Client to the
repository, source, target databases, and the Informatica Server:
Informatica Repository Connections
The Repository Server manages the metadata in the Informatica repository database. All
applications that connect to the repository must connect to the Repository Server. The
Repository Server uses native drivers to connect to the repository database. You must create a
repository configuration to connect the Repository Server to the repository database. The
repository configuration, such as database type, connect string, and database username and
password, contains the information the Repository Server uses to connect to the database.
The Repository Server requires a connect string to communicate with the repository. You
define the native connect string in the native database client connectivity software on the
machine hosting the repository database.
Table 2-3 lists the native connect string syntax for each supported RDBMS:
Table 2-2. Informatica Client Connectivity Requirements
To connect the Informatica Client to the... You need...
Repository Server TCP/IP
Source databases ODBC connection for each source database
Target databases ODBC connection for each target database
Informatica Server TCP/IP
Table 2-3. Native Connect String Syntax
Database Connect String Syntax Example
IBM DB2 dbname mydatabase
Informix dbname@servername mydatabase@informix
Microsoft SQL Server servername@dbname sqlserver@mydatabase
PowerCenter and PowerMart Connecti vi ty 23
For Teradata connect string syntax, see the Supplemental Guide.
The Repository Server connects repository client applications such as the Informatica Client
tools and the Informatica Server over the network. When you configure the Repository
Server, specify a port number the Repository Server uses to accept connections.
Table 2-4 summarizes the software you need to connect the Informatica Server to the
repository, source, and target databases:
Informatica Server Connections
The Informatica Server needs a connection to the repository. Use the Workflow Manager to
register the Informatica Server with the repository. You cannot start the Informatica Server
without first configuring it to connect to the repository. The Informatica Server connects to
the repository through the Repository Server.
Table 2-5 summarizes the software you need to connect the Informatica Server to the
Repository Server and the source and target databases:
For Windows, the Informatica Server includes ODBC libraries that you can use to connect to
other ODBC source databases.
Oracle dbname.world (same as TNSNAMES entry) oracle.world
Sybase servername@dbname sambrown@mydatabase
Table 2-4. Repository Server Connectivity Requirements
To connect the Repository Server to the... You need...
Repository Database Native database drivers
Informatica Client TCP/IP
Informatica Server TCP/IP
Table 2-5. Informatica Server Connectivity Requirements
To connect the Informatica Server to the... You need...
Repository Server TCP/IP
Source databases Native database drivers or ODBC
Target databases Native database drivers or ODBC
Informatica Client TCP/IP
Note: Both the Windows and UNIX versions of the Informatica Server can also use ODBC drivers to connect to
databases. However, Informatica recommends using native drivers when possible to improve performance.
Table 2-3. Native Connect String Syntax
Database Connect String Syntax Example
For flat file or COBOL sources, you can either access data with network connections (such as
NFS) or transfer data to the Informatica Server machine through FTP software. For
information on connectivity software for other ODBC sources, refer to your database
documentation.
PowerCenter and PowerMart Install ati on Steps 25
PowerCenter and PowerMart Installation Steps
This section outlines the steps for installing PowerCenter and PowerMart. These steps differ
depending on whether you are:
Installing for the first time
Upgrading from a previous version
These steps refer to additional chapters in this guide where you can obtain details for each
installation task.
Installing for the First Time
If you are installing PowerCenter or PowerMart for the first time, complete each of the
following tasks in the order listed below.
Note: Do not install the Metadata Reporter with the Informatica Client or Informatica Server.
Metadata Reporter installation is tightly integrated with the installation of a suitable web
server. See the Metadata Reporter Guide for details.
Follow these steps to install PowerCenter or PowerMart:
1. Install the Informatica Client tools.
For more information, see Installing and Configuring the Informatica Client on
page 63.
2. Configure the Informatica Client tools to connect to each database you need to access.
page 63.
3. Create an ODBC connection for each source and target database.
The Merant 3.7 32-bit ODBC closed drivers are designed for use with PowerCenter and
PowerMart only. If you use them with other software, these drivers generate warning
messages about violating licensing agreements. For details, see Using ODBC on
page 193.
4. Install and configure the Repository Server.
See the appropriate installation chapter for your platform. The chapters are Installing
and Configuring the Windows Repository Server on page 79 and Installing and
Configuring the UNIX Repository Server on page 99.
5. Start the Repository Server.
6. Create a repository.
Before you can start the Informatica Server, you must create a repository. The
Informatica Server needs a connection to the repository. For more information, see
Creating a Repository on page 115.
7. Configure the machine on which you plan to install the Informatica Server to connect to
each source and target database, the Repository Server, and the Informatica Client tools.
and Configuring the Informatica UNIX Server on page 157 and Installing and
Configuring the Informatica Windows Server on page 125.
8. Install and configure the Informatica Server.
9. Use the Workflow Manager to register the Informatica Server with the repository.
For more information, see Registering the Informatica Server on page 183.
10. Start the Informatica Server.
Upgrading from a Previous Version
You can upgrade to PowerCenter 6.0 and PowerMart 6.0 from PowerCenter 1.7/5.0/5.1 or
from PowerMart 4.7/5.0/5.1. The PowerCenter 6.0 and PowerMart 6.0 repository upgrade
process creates several new metadata object types. The upgrade also changes the functionality
of some existing repository objects. For details on upgrading repository objects, see
Upgrading a Repository on page 191.
Follow these steps to upgrade to PowerCenter 6.0 or PowerMart 6.0:
1. Use your existing version of the Repository Manager to back up each repository you want
to upgrade.
2. Create a new database for each repository you want to upgrade to PowerCenter 6.0 or
PowerMart 6.0.
See your database documentation for details.
Note: The PowerCenter 6.0 and PowerMart 6.0 repository is approximately 30 percent
larger than a PowerCenter 5.1 and PowerMart 5.1 repository and approximately 60
percent larger than a PowerCenter 4.7 and PowerMart 1.7 repository. Before you upgrade
the repository, check the repository database size and available disk space.
3. Use your existing version of the Repository Manager to make a copy of each existing
repository.
Important: We recommend that you make a copy of all existing repositories in your
existing version of the Repository Manager before upgrading to PowerCenter 6.0 or
PowerMart 6.0. Upgrade the copy of your existing repository to PowerCenter 6.0/
PowerMart 6.0 to evaluate it without altering your existing repository. For more
information, see Upgrading a Repository on page 191.
4. Upgrade the Informatica Client tools.
PowerCenter and PowerMart Install ati on Steps 27
page 63.
5. Configure the Informatica Client tools to connect to each source or target database you
need to access.
page 63.
6. Create an ODBC connection for each source and target database.
The Merant 3.7 32-bit ODBC closed drivers are designed for use with PowerCenter and
PowerMart only. If you use them with other software, these drivers generate warning
messages about violating licensing agreements. For details, see Using ODBC on
page 193.
7. Install and configure the Repository Server.
For more information, see Installing and Configuring the Windows Repository Server
on page 79 and Installing and Configuring the UNIX Repository Server on page 99.
9. In the Repository Manager, create a repository configuration for each repository database
managed by the Repository Server.
For more information, see Managing the Repository in the Repository Guide.
10. Upgrade each repository. If you are upgrading multiple repositories in a domain, upgrade
and start the global repository first.
For more information, see Upgrading a Repository on page 191.
11. Configure the machine on which you plan to install the Informatica Server to connect to
each database, the Repository Server, and the Informatica Client tools.
12. Install and configure the Informatica Server.
13. Use the Workflow Manager to register the Informatica Server with the repository.
For details, see Registering the Informatica Server on page 183.
29
C h a p t e r 3
Globalization Overview
Overview, 30
Locales, 32
Data Movement Modes, 33
Code Page Overview, 36
Relaxed Data Code Page Validation, 48
Troubleshooting for Relaxed Code Page Validation, 52
Case Study: Processing 7-bit ASCII Data, 53
Case Study: Processing ISO 8859-1 Data, 57
30 Chapter 3: Globalization Overview
Overview
The Informatica Server can process single-byte data or multibyte data. PowerCenter and
PowerMart support multibyte character data movement, which means you can write multiple
language source data to targets. The Informatica Client user interface allows you to enter
multibyte character data in mappings.
When you install PowerCenter or PowerMart, you must decide if you want the Informatica
Server to process single-byte data or multibyte data. To help you decide, this chapter describes
how the system locale affects data movement and code page settings, summarizes the
differences between the Informatica Server data movement modes and describes what happens
when you change data movement modes. It also includes background information about code
pages and details on code page validation and code page compatibility. You can easily change
the Informatica Server data movement mode at a later time.
When you install PowerCenter or PowerMart, use the operating system locale, which specifies
the language, code pages, territory, and collation order. Code pages distinguish between 7-bit
ASCII, ISO 8859-1 (8-bit ASCII), and multibyte characters in the Informatica Client and
Server, repository, source, and target databases.
The Informatica Server can transform character data in two modes: ASCII and Unicode. The
default data movement mode is ASCII, which passes US-ASCII character data. To pass 8-bit
or multibyte character data from sources to targets, use the Unicode data movement mode.
When you run the Informatica Server in Unicode mode, it uses two bytes for each character
to move data and performs additional checks at the session level to ensure data integrity.
Code pages contain the encoding to specify characters in a set of one or more languages. You
select a code page based on the type of character data in the mappings. Character data can
vary from one to eight bytes in size. Compatibility between code pages is essential for accurate
data movement.
To ensure data passes accurately through your data warehouse environment, the following
components must work together:
Operating system locale settings
Operating system code page
Informatica Server data movement mode
Informatica Server code page
Informatica Client code page
Informatica repository code page
Informatica Repository Server code page
Source and target database code pages
PowerCenter and PowerMart also allow you to configure the Informatica Server for relaxed
data code page validation. Relaxed validation lifts restrictions on source and target data code
pages.
Overvi ew 31
This chapter also provides two case studies to illustrate how you can configure data
warehouses to process 7-bit ASCII using the ASCII data movement mode and ISO 8859-1 (8-
bit ASCII) data using the Unicode data movement mode.
Locales
Every machine has a locale, a set of preferences related to the user environment. PowerCenter
and PowerMart use locale settings on each machine to run in the local environment. You can
set three locale settings in the Windows operating system Control Panel Regional Settings and
System Properties dialog boxes:
System locale. Determines the language, code pages, and associated bitmap font files that
are used as defaults for the system.
User locale. Determines the default formats to display date, time, currency, and number
formats.
Input locale. Describes the input method, such as using the keyboard, of the system
language.
Locales allow you flexibility in setting up the Informatica Client, Informatica Server, and
Repository Server on Windows machines.
System Locale
The system locale is also referred to as the system default locale. It determines which ANSI
and OEM code pages, as well as bitmap font files, are used as defaults for the system. The
system locale is already set on your system and you do not need to change settings to run
PowerCenter and PowerMart.
The system locale also contains the language setting that displays in the user interface,
including in dialog boxes and error messages. A message catalog file defines the language in
which messages display.
User Locale
The user locale is a setting that displays date, time, currency, and number formats for each
user. You can specify different user locales on a single machine. Create a user locale if you are
working with data on a machine that is in a different language than the operating system. For
example, you might be an English user working in Japan on a Japanese operating system. You
can set English as the user locale to use English standards in your work in Japan.
When you create a new user account, the machine uses a default user locale. You can change
this default setting once the account is created.
Input Locale
An input locale specifies the keyboard layout of a particular language. You can set an input
locale in the Regional Settings on a Windows machine to type characters of a specific
language. For example, if you are working on a Japanese operating system and need to type
text in English, you can set an English input locale for the keyboard setting. The keyboard
allows you to type English text on the Japanese operating system.
Dat a Movement Modes 33
Data Movement Modes
The data movement mode you use depends on whether you want the Informatica Server to
process single-byte data or multibyte character data. The data movement mode you select can
affect the enforcement of appropriate code page relationships and code page validation in the
Informatica Client, Informatica Server, and Repository Server.
Character Data Movement Modes
The Informatica Server runs in two modes:
Unicode. The universal character-encoding standard that supports all major languages.
When the Informatica Server runs in Unicode data movement mode, it allots two bytes for
each character. The Informatica Server uses the additional byte for non-ASCII characters,
such as Japanese characters. Run the Informatica Server in Unicode mode when source
data contains multibyte or ISO 8859-1 (8-bit ASCII) data.
ASCII. (American Standard Code for Information Interchange) 7-bit ASCII contains a set
of 128 characters is the one common denominator contained in all other character sets.
When the Informatica Server runs in the ASCII data movement mode, it holds all data in
a single byte.
When you select a data movement mode, code pages used for sessions must have appropriate
relationships. For details on code page compatibility, see Code Page Compatibility on
page 38.
In ASCII mode, the Informatica Server processes single byte characters and does not perform
code page conversions. In Unicode mode, the Informatica Server recognizes multibyte
character data and allocates 2 bytes to every character. The Informatica Server performs code
page conversions from sources to targets. When you set the Informatica Server to Unicode
data movement mode, it uses the Unicode character set to process characters in a specified
code page, such as ISO 8859-1 (8-bit ASCII) or Shift-JIS.
When you run the Informatica Server in ASCII mode, it does not enforce session code page
relationships. When you run the Informatica Server in Unicode mode, it enforces session code
page relationships. For details on how the Informatica Server enforces session code page
relationships in Unicode data movement mode, see Informatica Code Page Validation on
page 44.
Other character modes are defined as follows:
MBCS. (Multibyte Character Set) A mixed-width character set that contains characters of
more than one byte.
UTF-8. Characters range from one to three bytes in size. If you enable code page
validation, you can use UTF-8 for target database code pages only.
ISO 8859-1 (8-bit ASCII). Most European languages use this mode for accented Roman
characters.
Changing Data Movement Modes
You can change the Informatica Server data movement mode in the Informatica Server
configuration parameters. After you change the data movement mode, the Informatica Server
runs in the new data movement mode the next time you start the Informatica Server. When
the data movement mode changes, the Informatica Server handles character data differently.
To avoid creating data inconsistencies in your target tables, the Informatica Server performs
additional checks for sessions that reuse session caches and files.
Table 3-1 describes how the Informatica Server handles session files and caches after you
change the data movement mode:
Table 3-1. Session and File Cache Handling After Data Movement Mode Change
Session File or
Cache
Time of Creation or
Use
Informatica Server Behavior After Data Movement
Mode Change
Session Log File
(*.log)
Each session. No change in behavior. Creates a new session log for each
session using the Informatica Server code page.
Workflow Log Each workflow. No change in behavior. Creates a new workflow log file for
each workflow using the Informatica Server code page.
Reject File (*.bad) Each session. No change in behavior. Appends rejected data to the existing
reject file using the Informatica Server code page.
Output File (*.out) Sessions writing to flat
file.
No change in behavior for delimited flat files. Creates a new
output file for each session using the target code page.
Indicator File (*.in) Sessions writing to flat
file.
No change in behavior. Creates a new indicator file for each
session.
Incremental
Aggregation Files
(*.idx, *.dat)
Sessions with
Incremental
Aggregation enabled.
When files are removed or deleted, the Informatica Server
creates new files.
When files are not removed or deleted, the Informatica
Server fails the session with the following error message:
TE_7038 Aggregate Error: ServerMode: [server
data movement mode] and CachedMode: [data
movement mode that created the files]
mismatch.
You should also remove or delete files created using a
different code page.
Unnamed
Persistent Lookup
Files (*.idx, *.dat)
Sessions with a
Lookup transformation
configured for a
named persistent
lookup cache.
Rebuilds the persistent lookup cache.
Named Persistent
Lookup Files (*.idx,
*.dat)
Sessions with a
Lookup transformation
configured for a
persistent lookup
cache.
Fails the session.
Dat a Movement Modes 35
If you are not sure how you want to run the Informatica Server, install and configure
PowerCenter and PowerMart for Unicode data movement mode. This allows you the
flexibility to change the Informatica Server data movement mode from Unicode to ASCII,
and from ASCII to Unicode.
Code Page Overview
A code page contains the encoding to specify characters in a set of one or more languages. An
encoding is the assignment of a number to a character in the character set. You use code pages
to identify data that might be in different languages. For example, if you are importing
Japanese data into a mapping, you must select a Japanese code page for the source data.
When you choose a code page, the program or application for which you set the code page
refers to a specific set of data that describes the characters the application recognizes. This
influences the way that application stores, receives, and sends character data.
Operating System Code Pages
Most machines use one of the following code pages:
US-ASCII (7-bit ASCII)
MS Latin1 (MS 1252) for Windows operating systems
Latin1 (ISO 8859-1) for UNIX operating systems
IBM EBCDIC US English (IBM037) for mainframe systems
The US-ASCII code page is the most basic of all code pages, with support for United States
English. The US-ASCII code page is compatible only with itself. When you install the
Informatica Client, Server, or repository on an US-ASCII system, you must install each
Informatica Client, Server, and repository on US-ASCII systems. You must also run the
Informatica Server in ASCII mode.
MS Latin1 and Latin1 both support English and most Western European languages and are
compatible with each other. When you install the Informatica Client, Server, or repository on
a system using one of these code pages, you can install the rest of the components on any
machine using the MS Latin1 or Latin1 code pages.
The IBM EBCDIC code page is also compatible with MS Latin1 and Latin1. However, you
cannot install the Informatica Client, Server, or repository on mainframe systems, so you will
not use the IBM EBCDIC code page for Informatica Client, Server, or repository
installations.
UNIX Code Pages
In the United States, most UNIX operating systems have more than one code page installed
and use the US-ASCII code page by default. If you want to run PowerCenter or PowerMart in
a US-ASCII-only environment and run the Informatica Server in ASCII mode, you can use
the US-ASCII code page.
UNIX systems allow you to change the code page by changing the LANG_C, LC_CTYPE, or
LC_ALL environment variable. For example, suppose you want to find the code page used by
Code Page Overvi ew 37
an HP-UX machine. You use the following command in the C-shell to view your
environment:
locale
This results in the following output, in which C implies ASCII:
LANG="C"
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C"
To change the language to English and require the system to use the Latin1 code page, you
can use the following command:
setenv LANG en_US.iso88591
When you check the locale again, it has been changed to use Latin1 (ISO 8859-1):
LANG="en_US.iso88591"
LC_CTYPE="en_US.iso88591"
LC_NUMERIC="en_US.iso88591"
LC_TIME="en_US.iso88591"
LC_ALL="en_US.iso88591"
For details on changing the locale or code page of your UNIX system, see your UNIX
documentation.
Windows Code Pages
Windows 98, NT, 2000, and XP do not display the code page used by the operating system in
the environment settings. However, you can make an educated guess based on the country in
which you purchased the system and the language the system uses.
Microsoft sells Windows 98 as a fully-localized product with a default code page. Windows
NT/2000/XP has two code pages:
ANSI Code Page. Windows NT/2000/XP uses the ANSI code page for Win32
applications that interact with the operating system through the Windows GUI.
Applications such as Microsoft SQL Server are considered ANSI servers if they use code
pages MS1252-MS1259. The Informatica Client and Informatica Server use the ANSI
code page of the machine they are installed on.
OEM Code Page. Windows NT/2000/XP uses the OEM code page for Win32
applications that interact with the operating system through the Windows console.
Applications such as Microsoft SQL Server are considered OEM servers if they use any
code page other than MS1252-MS1259.
If you purchase English Windows 98 in the United States, your operating system uses the MS
Latin1 (MS1252) ANSI code page and the MS437 US English code page by default.
However, if you add other display or input languages and use those languages, the operating
system might use a different code page.
Windows NT/2000/XP operating systems are based on Unicode, but use only one local code
page at a time as the ANSI code page. If you purchase Windows in the United States and use
English as an input and display language, your operating system ANSI and OEM code pages
use MS Latin1 (MS1252) by default. However, if you install additional display or input
languages from the Windows NT/2000/XP installation CD and use those languages, the
operating system might use a different code page.
For details on the default code page for your Windows system, contact Microsoft.
Choosing a Code Page
Choose code pages based on the character data you use in mappings. Character data can be
represented by character modes based on the character size.
Character Sizes
Character size is measured by the amount of storage space a character requires in the database.
Different character sizes can be defined as follows:
Single byte. A character represented as a unique number between 0 and 255. One byte is
eight bits. ASCII characters are single byte characters.
Double byte. A character exactly two bytes or 16 bits in size represented as a unique
number 256 or greater. Many Asian languages, such as Japanese, have double byte
characters.
Multibyte. A character two to eight bytes in size represented as a unique number 256 or
greater. Many Asian languages, such as Japanese, have multibyte characters.
Code Page Compatibility
Compatibility between code pages is essential for accurate data movement when the
Informatica Server runs in the Unicode data movement mode. When two code pages are
compatible, the characters encoded in the two code pages are virtually identical. For example,
IBM EBCDIC US English and Latin1 code pages contain identical characters and are
compatible with each other. The repository and Informatica Server can each use one of these
code pages and can pass data back and forth without data loss.
One code page can be a subset or superset of another:
Superset. A code page is a superset of another code page when it contains characters
encoded in the other code page. The superset can also contain additional characters not
contained in the other code page. For example, MS Latin1 is a superset of the ASCII code
page because it contains all characters in the US-ASCII code page.
A code page can also be considered 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, the US-ASCII code page is a subset
of the MS Latin1 code page 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 source database code page is a superset of the target code page, the Informatica Server
cannot process the characters because they cannot be encoded in the target code page. The
target then results in incorrect or missing data. For example, Latin1 is a superset of US-
ASCII. It contains all US-ASCII character encoding in addition to its own character set
encoding. You can select US-ASCII for the source code page and Latin1 for the target code
page. However, if you select Latin1 as the source code page and US-ASCII as the target code
page, you might lose character data.
Figure 3-1 illustrates the necessary relationship between source and target database code pages
when you run the Informatica Server in Unicode data movement mode:
When you install or upgrade to run the Informatica Server in Unicode mode, you need to
ensure code page compatibility between the Informatica Client, Informatica Server,
Repository Server, and repository database machines. In Unicode mode, the Informatica
Server enforces code page compatibility between the Informatica Client, Server, and
repository. In addition, when you run the Informatica Server 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 Informatica
Server code page.
The target code page must be a superset of the Informatica Server code page.
If the session contains a Lookup transformation, the lookup database must use a code page
that is compatible with the Informatica Server.
If the session contains a Stored Procedure transformation, the stored procedure database
must use a code page that is compatible with the Informatica Server.
If the session contains an External Procedure or Advanced External Procedure
transformation, the data returned by the procedure must be in the Informatica Server code
page.
Figure 3-1. Required Code Page Relationships for Unicode Data Movement Mode
Source Code Page
Informatica Server Code Page
Target Code Page
If you have existing source and target database connections registered in the repository and
you want to run the Informatica Server in Unicode mode, you might need to reconfigure the
Informatica Server machine or choose a different machine for the Informatica Server to
ensure the appropriate session code page relationships.
For a list of compatible code pages, see Informatica Code Page Relationships on page 214.
Set code pages for the following components:
Informatica Client. The code page of the Informatica Client operating system. Clients
connected to different repositories might have different code pages.
Informatica Server. The code page of the Informatica Server operating system. When you
register the Informatica Server in the Workflow Manager, select the same code page as the
operating system code page.
Informatica Repository Server. The code page of the Repository Server operating system.
The Repository Server uses this code page automatically when you configure the Windows
or UNIX locale.
Informatica repository. The code page of data in the repository. When you create or
upgrade a repository, you select a code page.
Source and target files. The code page of the operating system on which source or target
files reside. Different operating systems can have different code pages.
XML source and target files. XML files contain an encoding declaration that indicates the
code page used in the file. XML source definitions use the repository code page. XML
target definitions use the code page declared in the XML file.
Source and target databases. The code page of the database for relational sources or
targets. Different databases can have different code pages.
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 Informatica Server interacts with the database client code page only. Thus,
code pages used by the Informatica Server, such as the 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 Informatica Server is running.
For details on specific database client and server code pages, consult your database
documentation.
Informatica Client Code Page
The Informatica Client code page is the code page of the operating system of the Informatica
Client. To communicate with the Informatica Server and repository, the Informatica Client
code page must be:
Compatible with the repository code page
Compatible with the Informatica Server code page
The Informatica Server code page is the code page of the operating system of the Informatica
Server. When you register the Informatica Server in the Workflow Manager, you enter the
identical code page. The Workflow Manager stores this information as metadata in the
repository.
When the Informatica Server runs in Unicode mode, it validates code pages when you start a
session to ensure accurate data movement. It uses session code pages to convert character data.
When the Informatica Server runs in ASCII mode, it does not validate session code pages. It
reads all character data as ASCII characters and does not perform code page conversions.
The Informatica Server code page must be:
A superset of the source code page
A subset of the target code page
Each code page has associated sort orders. When you configure a session, the Workflow
Manager allows you to select one of the sort orders associated with the Informatica Server
code page. When you run the Informatica Server in Unicode mode, it uses the selected session
sort order to sort character data. When you run the Informatica Server in ASCII mode, it
sorts all character data using a binary sort order.
If you run the Informatica Server in Unicode mode, you must enter the session code page
information in the session configuration. If a session contains a Lookup or Stored Procedure
transformation, the databases on which the lookup table or stored procedure reside must be
compatible with the Informatica Server code page. If a session contains an External Procedure
or Advanced External Procedure transformation, the external or advanced external procedure
must pass data in the Informatica Server code page.
If you run the Informatica Server in the United States on Windows, Informatica recommends
using MS Windows Latin1 (ANSI) as the Informatica Server code page.
If you run the Informatica Server in the United States on UNIX, Informatica recommends
using ISO 8859-1 as the Informatica Server code page.
If you use pmcmd to communicate with the Informatica Server, the code page of the operating
system hosting pmcmd must be identical to the Informatica Server code page.
The Informatica Server generates session log files, reject files, caches and cache files, and
performance detail files based on the Informatica Server code page.
Repository Server Code Page
The Repository Server code page is the same as the code page of the Repository Server
operating system. The Repository Server code page must be:
Compatible with the Informatica Client code page
Repository Code Page
The repository code page is the code page of the data in the repository. The Repository Agent
process uses the repository code page to insert metadata in and retrieve metadata from the
repository database. Choose the repository code page when you create or upgrade a repository.
The repository code page must be:
Compatible with the Informatica Client code page
Compatible with the Repository Server code page.
A global repository code page must be a subset of the local repository code page so you can
create shortcuts to the local repository. To copy objects from a local repository to a global
repository, the code pages of both repositories must be compatible.
Source Code Page
The source code page is the code page associated with the source database, flat file or XML
file, or the source operating system. The source code page must be:
A subset of the Informatica Server code page
A subset of the target code page
Note: Select IBM EBCDIC as your source database connection code page only if you access
EBCDIC data, such as data from a mainframe extract file.
Target Code Page
The target code page is the code page of the target database or flat file or XML file operating
system. The target code page must be:
A superset of the source code page
A superset of the Informatica Server code page
The Informatica Server creates session indicator files, session output files, and external loader
control and data files using the target flat file code page.
Note: Select IBM EBCDIC as your target database connection code page only if you access
Code Page Compatibility Summary
Figure 3-2 illustrates code page compatibility between sources, targets, the repository, the
Repository Server, the Informatica Client and the Informatica Server:
Table 3-2 summarizes code page compatibility between sources, targets, the repository, the
Repository Server, the Informatica Client and the Informatica Server:
Figure 3-2. Code Page Compatibility
Table 3-2. Code Page Compatibility
Component Code Page Code Page Compatibility
Source (including relational, flat file,
and XML file)
Subset of target.
Subset of Informatica Server.
Target (including relational, XML files,
and flat files)
Superset of source.
Superset of Informatica Server.
External loader data and control files are created using the target flat file code
page.
Informatica Server Superset of source.
Subset of target.
Identical to Informatica Server operating system and machine hosting pmcmd.
Compatible with repository and Informatica Client.
Compatible with database connection code page used by Lookup and Stored
Procedure transformations.
Repository Server Compatible with repository.
Compatible with Informatica Client and Informatica Server.
Informatica Code Page Validation
For PowerCenter and PowerMart, the machines hosting the Informatica Client, Server,
Repository Server and repository database must use compatible code pages. This eliminates
the risk of data or repository inconsistencies. When the Informatica Server runs in Unicode
data movement mode, the Informatica Server also enforces session code page relationships.
When the Informatica Server runs in ASCII mode, it does not enforce session code page
relationships.
To ensure compatibility, the Informatica Client and Server perform the following code page
validation both during installation and upgrade and during daily use:
Repository Server restricts the use of EBCDIC-based code pages for repositories. Since
you cannot install the Informatica Client, Informatica Server, Repository Server, or
repository database on mainframe systems, the Repository Server does not allow you to
select EBCDIC-based code pages, like IBM EBCDIC, as the repository code page.
Informatica Client restricts use of EBCDIC-based code pages for the Informatica Server.
The Workflow Manager does not allow you to select EBCDIC-based code pages for the
Informatica Server code page.
Repository Server restricts repository code page choices to those compatible with the
Repository Server. The Repository Server code page must be compatible with the
repository code page to prevent data loss or inconsistencies. After you install the
Repository Server, it uses the operating system code page as the Repository Server code
page. When you create a new repository or upgrade an existing repository, you select a
code page for the repository. The Repository Server restricts code page choices to those
compatible with the Repository Server code page.
Informatica Client connects to the repository only when its code page is compatible
with the repository code page. If the Informatica Client code page is not compatible with
the repository code page, the Informatica Client fails to connect to the repository code
page with the following error:
REP_12782 The repository <repository name>s code page <code page name>
and <Informatica Client>s code page <code page name> are incompatible.
Once selected, you cannot change the repository code page. After you create or upgrade a
repository, the Repository Manager does not allow you to change the repository code page.
Global Repository Compatible with local repository. Can also be a subset of local repository.
Compatible with Informatica Client and Server.
Local Repository Compatible with global repository. Can also be a superset of global repository.
Standalone Repository Compatible with Informatica Client and Server.
Informatica Client Compatible with Informatica Server and repository.
Machine hosting pmcmd Identical to Informatica Server.
Table 3-2. Code Page Compatibility
This prevents data loss and inconsistencies in the repository. If necessary, you can change
the repository code page to a compatible code page by copying your existing repository to
a new database. However, if the new code page is not compatible with the original
repository code page, the Repository Manager does not copy the repository.
The Informatica Server starts only when the Informatica Server code page is compatible
with the repository code page. The Informatica Server code page must be compatible with
the repository code page to prevent data loss or inconsistencies. Like the Informatica
Client, the Informatica Server uses the operating system code page as the Informatica
Server code page. If it is not compatible, the Informatica Server writes the following
message in the Windows Event Viewer or the UNIX server log or server error log:
Error: Server can only obtain a read-only connection with the repository.
Please make sure the code page where the server is running is two way
compatible with the repository code page.
The Informatica Server starts only when the Informatica Server code page is registered
correctly in the Workflow Manager. To ensure accurate session validation, the Informatica
Server code page must be registered correctly in the Workflow Manager. After you install
or upgrade the Informatica Client and repository, the Workflow Manager sets the code
page for each registered server to the repository code page. The Informatica Server starts
only when the code page registered in the Workflow Manager matches the Informatica
Server code page.
If the code page does not match the Informatica Server code page, the Informatica Server
writes the following message in the Windows Event Viewer or UNIX server or server error
log:
LM_36011 Error: codepage mismatch. Server is running in codepage
<Informatica Server code page> whereas the server is configured in the
Workflow Manager to run in codepage <user-configured code page>.
Informatica Client restricts Informatica Server code page choices to those compatible
with the Informatica Client. The Informatica Server code page must be compatible with
the Informatica Client code page to prevent data loss or inconsistencies. When you register
an Informatica Server, the Workflow Manager restricts code page choices to those
compatible with the Informatica Client code page.
When in Unicode data movement mode, the Informatica Server starts workflows with
the appropriate source and target code page relationships for each session. When the
Informatica Server runs in Unicode mode, the code page for every session source must be a
subset of the Informatica Server code page, and the code page for each target must be a
superset of the Informatica Server code page. This prevents data loss during a workflow.
For details on code page relationships, subsets, and supersets, see Supported Code Pages
and Related Code Pages on page 216.
If the source and target code pages do not have the appropriate relationships to the
Informatica Server code page, the Informatica Server fails the session and writes the
following message to the session log:
TM_6227 Error: Code page incompatible in session <session name>.
<Additional details>.
Workflow Manager validates source and target code page relationships for each session.
Source and target code page relationships are critical when the Informatica Server runs in
Unicode mode. As a result, the Workflow Manager always checks code page relationships
when you save a session, regardless of the Informatica Server data movement mode. The
Workflow Manager alerts you to inappropriate code page relationships in case you change
the Informatica Server to Unicode mode or run the workflow containing the session on a
different Informatica Server.
If you configure a session with invalid source or target code page relationships, the
Workflow Manager issues a warning similar to the following when you save the session:
If you want to run the workflow containing the session on an Informatica Server in ASCII
mode, you can save the session as configured. If you want to run the workflow on an
Informatica Server in Unicode mode, perform the most appropriate of the following
actions:
Change the relational source or target database connections to those with appropriate
code pages, or change the file source or target code page and location. You can set the
code page for file sources and targets in the file properties dialog boxes in the session
properties. The Workflow Manager restricts source file code page choices to those that
are subsets of the Informatica Server code page. The Workflow Manager also restricts
target file code page choices to those that are subsets of the Informatica Server code
page. The Workflow Manager also restricts target file code page choices to those that are
supersets of the Informatica Server code page.
Correct the configured code pages in the database connections. Edit the code page for
relational sources and targets in the Workflow Manager database connection dialog box.
Because you can use the same database connection as a source or target, the Workflow
Manager restricts code page choices to those that are either subsets or supersets of the
Informatica Server code page.
Correct the configured code page for the registered server.
Workflow Manager validates code pages for lookup and/or stored procedure databases in
a session. When the Informatica Server runs in Unicode mode, the database hosting a
lookup table or stored procedure for a session must use a code page that is compatible with
the Informatica Server code page. As with source and target code pages, the Workflow
Manager always checks these code page relationships.
When you configure the session with invalid lookup or stored procedure code page
relationships, the Workflow Manager issues the following warning:
The database <lookup or stored procedure database name> and server <server
name> do not have compatible code pages. Do you want to save the session?
If you want to run the workflow containing this session on an Informatica Server in ASCII
mode, you can save the session as configured. If you want to run the workflow on an
Informatica Server in Unicode mode, perform the most appropriate of the following
actions:
Change the lookup or stored procedure database connections to those with appropriate
code pages. You can configure the database used for the Lookup and Stored Procedure
transformation in the transformation property sheet or enter a session override on the
Transformations tab of the session properties.
Correct the code page for the database connection. You can configure the database code
page in the Workflow Manager.
Correct the configured code page for the registered server.
Relaxed Data Code Page Validation
Your environment may require you to process data from different sources using character sets
from different languages. For example, you might need to process data from English and
Japanese sources using the same repository, or you may wish to extract source data encoded in
a Unicode character set such as UTF-8. Configuring the Informatica Server for relaxed data
code page validation lifts code page restrictions. This allows you to process data using sources
and targets with incompatible code page, or sources and targets with code pages incompatible
with the Informatica Server code page.
Although relaxed data code page validation lifts source and target code page restrictions, be
aware that relaxed code page validation does not safeguard against possible data
inconsistencies when you move data between two incompatible code pages.
PowerCenter and PowerMart include the following relaxed data code page validation features
when you run the Informatica Server in Unicode data movement mode:
Lifted restrictions for source and target data code page. You can use any code page
supported by PowerCenter and PowerMart for your source and target data.
Lifted restrictions for session sort order. You can use any sort order supported by
PowerCenter and PowerMart when you configure a session.
Informatica Server writes multibyte characters to the session log. You can configure the
Informatica Server to write to the session log using the UTF-8 character set. This ensures
that multibyte characters display properly when you view the session log.
Configuring the Informatica Server
To configure the Informatica Server on Windows for data code page relaxation, you must
complete the following tasks:
Disable data code page validation.
Configure the Informatica Server for Unicode data movement mode.
Configure the Informatica Server to write to the session log using the UTF-8 character set.
You can configure the Informatica Server on Windows for data code page relaxation in the
Informatica Server setup program. On the Configuration tab of the Informatica Server setup
program, select UNICODE as the data movement mode, clear the Validate Data Code Pages
check box, and select the Session Log in UTF-8.
To configure the Informatica Server on UNIX for data code page relaxation, run pmconfig
and set DataMovementMode to UNICODE, ValidateDataCodePages to No, and
SessionLogInUTF8 to Yes.
Relaxed Code Page Validation
Configuring the Informatica Server for relaxed data code page validation lifts restrictions on
source and target data code pages. However, the Informatica Server and Informatica Client
Relaxed Dat a Code Page Val idati on 49
continue to prevent data inconsistencies between PowerCenter and PowerMart components
by enforcing code page compatibility between the Informatica Server, Informatica Client,
Repository Server, and the repository.
When you configure the Informatica Server to relax data code page validation, the
Informatica Server lifts code page compatibility restrictions on sources and targets, allowing
you to extract, transform, and load data from source definitions imported or created in the
Designer. Although the Informatica Server lifts source and target code page restrictions, it
enforces other code page relationships and checks query conversions at runtime.
When you start the Informatica Server, it enforces the following code page relationships:
The Informatica Server code page must be two-way compatible with the repository and
Repository Server code pages.
The Informatica Server code page must be the same code page as operating system the
Informatica Server is installed on.
When you run a workflow with relaxed data code page validation, the Informatica Server
writes the following message to the session log:
TM_6185 WARNING! Data codepage validation is disabled in this session.
When you relax data code page validation, the Informatica Server writes descriptions of the
code pages selected for source and target files and database connections to the session log. The
Informatica Server also writes descriptions of code pages for lookup and stored procedure
databases to the session log. The following example shows these descriptions as they appear in
a session log:
TM_6186 Repository codepage: [MS Windows Latin 1 (ANSI), superset of Latin
1]
TM_6188 Target file [$PMTargetFileDir\passthru.out] codepage: [MS Windows
Traditional Chinese, superset of Big 5]
TM_6190 Target database connection [Japanese Oracle] codepage: [MS
Windows Japanese, superset of Shift-JIS]
TM_6189 Source database connection [Japanese Oracle] code page: [MS
Windows Japanese, superset of Shift-JIS]
TM_6191 Lookup [LKP_sjis_lookup] uses database connection [Japanese
Oracle] in codepage [MS Windows Japanese, superset of Shift-JIS]
TM_6192 Stored procedure [J_SP_INCREMENT] uses database connection
[Japanese Oracle] in codepage [MS Windows Japanese, superset of Shift-JIS]
The Informatica Server operates internally using UCS-2. The Informatica Server converts
source data encoded in other code pages to the UCS-2 character set before processing, and
converts the processed data from UCS-2 to the target warehouse code page before loading.
When you run a workflow that contains a session, Informatica Server converts source, target,
and lookup queries from the repository code page to the source, target, or lookup database
code page. The Informatica Server also converts the name and call text of stored procedures
from the repository code page to the stored procedure database code page. At runtime, the
Informatica Server performs checks on the following code page conversions:
The source query must convert from the Informatica Server code page to the source
database code page without any loss of data in conversion.
The name and call text of stored procedures in stored procedure transformations, pre-
source and post-source stored procedures, and pre-target and post-target stored procedures
must convert from the Informatica Server code page to the stored procedure database code
page without loss of data in conversion.
Lookup queries must convert from the Informatica Server code page to the lookup
database code page without loss of data in conversion.
Target SQL queries must convert from the Informatica Server code page to the target
database code page without loss of data in conversion.
If the Informatica Server cannot correctly convert data, it writes an error message to the
session log.
Selecting Compatible Source and Target Data Code Pages
Although the Informatica Server allow you to use any supported code page, you should select
compatible code pages for your source and target data. Your target data code page should be a
superset of your source data code page. If your target data code page is not a superset of your
source data code page, you risk inconsistencies in your target data because your source data
may contain characters not encoded in the target warehouse code page.
For example, suppose your source data contains Japanese characters encoded using the
JapanEUC code page. You cannot load this data to a target warehouse using the Latin1 code
page because the Latin1 code page does not contain Japanese characters in its character set.
If you are familiar with your data and are confident that it will convert safely from one code
page to another, you can run workflows with incompatible source and target data code pages.
It is your responsibility to ensure your data will convert properly.
For example, suppose your source data is encoded in a database with a UTF-8 code page, and
you want to load this data to a target database with a MS Latin1 code page. If you are certain
that all of your source data is a subset of the MS Latin1 code page, you can load data to the
target without inconsistencies. However, if your data contains any character not included in
the Latin1 character set, such as Chinese characters or Greek letters, these characters will be
loaded to the target as garbage data, or may cause transformation errors.
Using 7-bit ASCII Characters for Repository Metadata
Informatica recommends that you use 7-bit ASCII data for all repository metadata. This
allows the Informatica Server to successfully perform SQL transactions with source, target,
lookup, and stored procedure databases. You can store the repository on a database with any
code page that is a superset of the ASCII code page. In this case, ensure that the ASCII
metadata characters fall between code points 32 and 126 in the repository database code page.
For example, suppose your Informatica Server, Repository Server, repository, and Informatica
Client use the ISO 8859-1 code Latin1 code page, and your 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 your repository and source database
Relaxed Dat a Code Page Val idati on 51
metadata could cause the Informatica Server to fail sessions or load no rows to the target in
situations like the following:
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 Informatica Client to generate SQL queries containing characters specific to
the German language range of ISO 8859-1. When you try to execute this query in the
source database, the source database may not recognize the query because it may not be
able to convert the German-specific characters from the ISO 8859-1 code page into the
Shift-JIS code page.
Your source database has a table name that contains Japanese characters. When you import
this table into your repository as a source definition, the Designer cannot convert the
Japanese characters from the source database code page to the Informatica Client code
page. Instead, the Designer imports the Japanese characters as question marks (?),
changing the name of the table. When you save the source definition to the repository, the
repository saves the source definition with question marks instead of Japanese characters.
If the Informatica Server 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 Informatica Server, possibly causing the session to fail.
Because the 7-bit 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.
Troubleshooting for Relaxed Code Page Validation
The Informatica Server failed a session and wrote the following message to the session log:
TM_6188 Session sort order [sort order name] is incompatible with the Informatica
Server's codepage [code page name].
Cause: The specified sort order is incompatible with the Informatica Server code
page.
Action: If you want to validate data code pages, select a sort order compatible with the
Informatica Server code page. If you want to relax data code page validation,
configure the Informatica Server to relax data code page validation in Unicode
data movement mode. For details on configuring the Informatica Server, see
Configuring the Informatica Server on page 48.
I tried to view the session log, but it contains garbage characters.
Cause: Your Informatica Server is not configured to write to the session log using the
UTF-8 character set.
Action: Enable the Session Log in UTF-8 option on the Configuration tab of the
Informatica Server setup program.
Case St udy: Processi ng 7-bi t ASCII Data 53
Case Study: Processing 7-bit ASCII Data
This case study describes how you can configure your environment to process 7-bit ASCII
data using the Informatica Client and Server. You might want to configure your data
warehouse for 7-bit ASCII data if you only want to process ASCII data and want to benefit
from increased performance gained from the Informatica Server ASCII data movement mode.
For this case study, the environment contains the following machines and data sources:
Informatica PowerCenter/PowerMart Clients running on Windows 2000 machines
The Informatica Server running on a Windows NT machine
The Repository Server and Repository Agent process on a Windows NT machine
The repository tables residing on a Microsoft Windows SQL Server database on Windows
NT
A source database server
A target database server
A lookup database
All character data in the data warehouse environment is U.S. English, 7-bit ASCII data.
Figure 3-3 illustrates the 7-bit ASCII data environment:
Figure 3-3. 7-bit ASCII Mode Case Study Environment
Informatica Server
(Windows NT)
Sources
(7-bit ASCII Data)
Targets
(7-bit ASCII Data)
Lookup Database
(7-bit ASCII Data)
External Procedures
(7-bit ASCII Data)
Repository Database
(Microsoft SQL Server on
Windows NT)
Informatica Client Tools
(Windows 2000)
Repository Server
Repository Agent
(Windows NT)
Configuring the 7-bit ASCII Environment
When you configure the globalization properties for this environment, you must follow these
guidelines:
1. Verify Informatica Client, Repository Server and Informatica Server code page
compatibility.
2. Verify repository database client and database server compatibility.
3. Set the Informatica Server data movement mode.
4. Verify session code page relationships.
5. Set the session sort order.
Step 1. Verify PowerCenter and PowerMart Code Page Compatibility
Informatica Client, Informatica Server, and Repository Server code pages must be compatible.
In this case, because the Informatica Client, Repository Server, and Informatica Server
Windows systems were purchased in the United States, and use English as the input and
display language, the Windows NT and 2000 machines use MS Windows Latin1 as the
operating system code page.
Since the Informatica Client, Repository Server, and Informatica Server use the same code
page as the operating system each is installed on, the Informatica Client, Repository Server
and Informatica Server also use MS Windows Latin1 as code pages.
To verify a Windows operating system input and display language, open the Regional Settings
Properties dialog box from the Windows Control Panel. Regional Settings and Input Locale
should both be configured for English (United States).
Step 2. Verify Repository Database Client and Server Compatibility
The repository database client and database server storing the repository tables must be able
to communicate without data loss. In this case, the repository resides in a Microsoft SQL
Server 7.0 database. When you install Microsoft SQL Server, you select the default code page
for the database server. By default, Microsoft SQL Server uses MS Windows Latin1, the same
as the Informatica Client and Server code pages in this case study.
You can use the sp_helpsort stored procedure to determine the code page and sort order the
database server uses.
To ensure the Microsoft SQL Server client utilities convert data from the client machine to
the server properly, make sure the following options are selected. They are selected by default
in Microsoft SQL Server 7.0:
Automatic ANSI to OEM Conversion. In the SQL Server Client Network Utility, enable
or disable this setting in the DB Library Options tab.
Perform Translation for Character Data. In the Enterprise Manager, choose Tools-
Options, then open the Connection tab to enable or disable this setting.
See your Microsoft SQL Server documentation for details or updates.
Case St udy: Processi ng 7-bi t ASCII Data 55
Step 3. Set the Informatica Server Data Movement Mode to ASCII
In the Informatica Server setup program, open the Miscellaneous tab and set the Data
Movement Mode to ASCII. When you set the data movement mode to ASCII, the
Informatica Client and Server do not enforce code page relationships through validation.
Step 4. Verify Session Code Page Relationships
When you run the Informatica Server in ASCII mode, the Informatica Server assumes all data
is 7-bit ASCII. It executes sessions and does not validate session code page relationships.
However, because you can change the Informatica Server data movement mode to Unicode,
or (with PowerCenter) register another server that might run in Unicode mode, the Workflow
Manager always validates session code page relationships when you save a session.
When the Workflow Manager detects an inappropriate code page relationship, it issues a
warning then saves the session. Because the Informatica Server ignores session code page
relationships when it runs in ASCII mode, you can ignore the warning.
Step 5. Select Session Sort Order
When you run the Informatica Server in ASCII mode, it uses a binary sort order for all
sessions. In the session property sheet, the Workflow Manager lists all sort orders associated
with the Informatica Server code page. You can select a sort order for the session.
ASCII Case Study: Summary
Figure 3-4 summarizes the required code page settings for processing 7-bit ASCII data in the
sample data environment:
Figure 3-4. ASCII Case Study Summary
Informatica Server
-Configure ASCII Data Movement
Mode
-Set code page in Workflow
Manager to MS Windows Latin 1
Sources (7-bit
ASCII Data)
Targets (7-bit
ASCII Data)
Lookup Database
External Procedures
Informatica Clients
(Windows 2000: MS Windows
Latin 1 default)
Repository Database
(Microsoft SQL Server on
Windows NT)
Repository Server
Repository Agent
(Windows NT: MS Windows
Latin 1 default)
(Set code page to MS Windows
Latin 1 or ISO 8859-1 when you
create or upgrade the repository)
Case Study: Processi ng ISO 8859-1 Data 57
Case Study: Processing ISO 8859-1 Data
This case study describes how a data warehouse environment that processes ISO 8859-1
multibyte data might be set up. You might want to configure your data warehouse this way if
you need to process data from different Western European languages with character sets
contained in the ISO 8859-1 code page. This example describes a data warehouse that
processes English and German language data.
For this case study, the ISO 8859-1 data warehouse environment consists of the following
elements:
The Informatica Server on a UNIX Solaris machine.
Informatica Clients on Windows NT systems, purchased in the United States.
The Repository Server and Repository Agent process on a UNIX Solaris machine.
The repository stored on an Oracle database on UNIX.
A source database server contains English language data.
A source database server contains German and English language data.
A target database server contains German and English language data.
A lookup database contains English language data.
The ISO 8859-1 Environment
The data environment must process English and German character data.
Figure 3-5 illustrates the ISO 8859-1 data environment:
Configuring the ISO 8859-1 Environment
Use the following guidelines when you configure an environment like that used in this case
study for ISO 8859-1 data processing:
1. Verify Informatica Client, Repository Server and Informatica Server code page
compatibility.
2. Verify repository database client and server code page compatibility.
3. Configure the Informatica Server for Unicode data movement mode.
4. Verify code page compatibility for sources and targets.
5. Verify lookup and stored procedure database code page compatibility.
6. Verify data processed by External Procedure or Advanced External Procedure
transformations.
7. Configure session sort order.
Figure 3-5. ISO 8859-1 Case Study Environment
Informatica Server
(UNIX)
Sources
(English Data)
Targets
(English and
German Data)
Lookup Database
(English Data)
External Procedures
(English Data)
Sources
(German and
English Data)
(Windows NT)
Repository Database
(Oracle on UNIX)
Repository Server
Repository Agent
(UNIX))
The ISO 8859-1 Environment 59
Step 1. Verify PowerCenter/PowerMart Code Page Compatibility
The Informatica Client, Informatica Server, and Repository Server code pages must be
compatible. Because the Informatica Client, Informatica Server, and Repository Server each
use the system code pages of the machines they are installed on, you must verify that the
system code pages are compatible.
In this case, the Informatica Client Windows NT systems were purchased in the United
States. Thus, the system code pages for the Informatica Client machines are set to MS
Windows Latin1 by default. To verify system input and display languages, open the Regional
Settings Properties dialog box from the Windows Control Panel. For systems purchased in the
United States, the Regional Settings and Input Locale should be configured for English
(United States).
The Informatica Server is installed on a UNIX Solaris machine. The default code page for
UNIX operating systems is ASCII. In this environment, the UNIX system code page must be
changed to ISO 8859-1 Western European in order to be compatible with the MS Windows
Latin1. To verify code page compatibility, check the code page compatibility tables in Code
Pages on page 207. For details on changing the UNIX system code page, see UNIX Code
Pages on page 36.
The Repository Server is also installed on a UNIX Solaris machine. The default code page for
UNIX operating systems is ASCII. In this environment, the UNIX system code page must be
changed to ISO 8859-1 Western European in order to be compatible with MS Windows
Latin1. To verify code page compatibility, check the code page compatibility tables in Code
Pages on page 207. For details on changing the UNIX system code page, see UNIX Code
Pages on page 36.
Step 2. Verify Repository Database Client and Server Code Page
Compatibility
The database client and server hosting the Informatica repository must be able to
communicate without data loss.
The repository resides in an Oracle database. With Oracle, you can use NLS_LANG to set the
locale (language, territory, and character set) you want the database client and server to use
with your login:
NLS_LANG = LANGUAGE_TERRITORY.CHARACTERSET
By default, Oracle configures NLS_LANG for U.S. English, U.S. date formats, and the U.S.
English code page:
NLS_LANG = AMERICAN_AMERICA.US7ASCII
Change the default configuration to write ISO 8859-1 data to the repository using the Oracle
WE8ISO8859P1 code page.
See your repository database documentation for details on verifying and changing the
repository database code page. For details on repository database code pages, see Repository
Code Page on page 42.
Step 3. Configure the Informatica Server for Unicode Data Movement
Mode
You must configure the Informatica Server to process ISO 8859-1 data. On the Miscellaneous
tab of the Informatica Server setup, select Unicode as the data movement mode. The
Informatica Server allots an extra byte for non-ASCII characters when processing multibyte
data. For details on the Unicode data movement mode, see Character Data Movement
Modes on page 33.
Step 4. Verify Session Code Page Compatibility
When you run a workflow in Unicode data movement mode, the Informatica Server enforces
source and target code page relationships. For details on code page validation when running
workflows, see Informatica Code Page Validation on page 44.
To guarantee accurate data conversion, the source database code page must be a subset of the
Informatica Server code page. In this case, the data environment contains a source database
containing German and English data. When you configure a source database connection in
the Workflow Manager, the code page for the connection must be identical to the source
database code page and must be a subset of the Informatica Server code page. Since both the
MS Windows Latin1 and the ISO 8859-1 Western European code pages contain German
characters, you would most likely use one of these code pages for source database connections.
In a valid session, target code pages must be a superset of the Informatica Server ISO 8859-1
Western European code page. In this case, we could use either ISO 8859-1 Western
European, MS Windows Latin1, or UTF-8 for target database connection or flat file code
pages. To ensure data consistency, the configured target code page must match the target
database or flat file system code page.
If you configure the Informatica Server and Informatica Client for relaxed data code page
validation, the Informatica Server lifts restrictions on source and target code page
compatibility. You can select any supported code page for source and target data.
Note: When you configure the Informatica Server to validate data code pages, use UTF-8 for
target code pages only.
Step 5. Verify Lookup and Stored Procedure Database Code Page
Compatibility
Lookup and stored procedure database code pages must be compatible with the Informatica
Server code page. In this case, all lookup and stored procedure database connections must use
a code page compatible with the ISO 8859-1 Western European code page.
Step 6. Verify Data Processed by External Procedures or Advanced
External Procedures
Data processed by External Procedure or Advanced External Procedure transformations
should be in a code page compatible with the Informatica Server code page. In this case, all
The ISO 8859-1 Environment 61
data processed by the External Procedure or Advanced External Procedure transformations
must be in the ISO 8859-1 Western European code page.
Step 7. Configure Session Sort Order
When you run the Informatica Server in Unicode mode, it sorts session data using the sort
order configured for the session. By default, sessions are configured for a binary sort order.
In this case, to sort English and German data when the Informatica Server uses the ISO 8859-
1 Western European code page, you most likely want to use the default binary sort order. ISO
8859-1 Western European does not contain a sort order for German.
ISO 8859-1 Case Study: Summary
Figure 3-6 summarizes the guidelines set forth in this case study to configure a data warehouse
environment to process ISO 8859-1 data:
Figure 3-6. Summary of ISO 8859-1 Case Study
Informatica Server
(UNIX: ASCII default)
Set UNIX code page to ISO 8859-1.
Change Data Movement Mode
to Unicode.
Set code page in Workflow Manager
to ISO 8859-1.
Sources
(English Data)
Targets
(English and
German Data)
Lookup Database
(English Data)
External Procedures
(English Data)
Sources
(German and
English Data)
(Windows NT: MS
Windows Latin 1 default)
Repository Server
Repository Agent
Repository Database
(Oracle on UNIX)
(UNIX: ASCII default)
Set UNIX code page to ISO
8859-1.
(Set code page to ISO 8859-1
when you create or upgrade the
repository)
63
C h a p t e r 4
Installing and Configuring
the Informatica Client
Step 1. Installing ODBC Drivers, 65
Step 2. Installing the Informatica Client Tools, 67
Step 3. Connecting to Databases, 69
Troubleshooting, 78
64 Chapter 4: Install ing and Configuring the Informatica Client
Before You Begin
You need to complete the following steps to install and configure the Informatica Client tools
for the first time:
1. Install the Merant 3.7 32-bit closed ODBC drivers.
2. Install the Informatica Client tools.
3. Connect to each database.
If you are upgrading the Informatica Client tools, you need to complete the following steps:
1. Replace existing Merant 32-bit closed ODBC drivers with Merant 3.7 32-bit closed
ODBC drivers.
2. Upgrade the Informatica Client tools.
3. Connect to each database.
Before you install the Informatica Client tools, make sure you have 30 MB of disk space
available on the Windows boot drive. The Informatica Platform Setup requires this space for
temporary files.
Before you begin, locate the PowerCenter/PowerMart product license key. Use the same
product license key to install the Informatica Server, Repository Server, Informatica Client
tools, and Metadata Reporter.
Note: Please read the release notes for last minute changes to the Informatica Client
installation and connectivity issues.
Step 1. Inst al l i ng ODBC Dri vers 65
Step 1. Installing ODBC Drivers
Open Database Connectivity (ODBC) provides a common way to communicate with many
different database platforms. Many database applications, such as the Informatica Client
tools, use ODBC to communicate with databases.
Before you run the Informatica Client tools, you need to create an ODBC data source on the
client machine for each source and target database. You do not need to create an ODBC data
source to connect to the repository database.
Table 4-1 shows the ODBC drivers to use with each database:
Note: The Merant 3.7 32-bit ODBC closed drivers are designed for use with PowerCenter and
PowerMart only. If you use them with other software, they generate warning messages about
violating licensing agreements.
For a complete description of supported databases and ODBC drivers, see Using ODBC on
page 193.
Merant ODBC 3.7 Installation
The Merant 3.7 32-bit ODBC installation is compatible with Informix, Oracle, and Sybase
databases. It includes:
ODBC Administrator
Merant 3.7 32-bit ODBC closed drivers
Uninstall program
If the installation program finds an earlier version of the driver installed on your system, it
replaces the old driver with the Merant 3.7 32-bit ODBC closed driver. Likewise, if it finds
an earlier version of the ODBC Administrator, it automatically overwrites it with the version
included on the Informatica installation CD.
Table 4-1. ODBC Drivers for Source and Target Databases
Database ODBC driver
IBM DB2 IBM ODBC driver
Informix Merant 3.7 32-bit closed ODBC driver
Microsoft SQL Server Microsoft SQL Server ODBC driver
Microsoft Access97 Microsoft Access driver
Microsoft Excel Microsoft Excel driver
Oracle Merant 3.7 32-bit closed ODBC driver
Sybase Merant 3.7 32-bit closed ODBC driver
Teradata Teradata ODBC driver
To install Merant 3.7 32-bit ODBC closed drivers:
1. Close all open applications.
2. From Windows, run setup.exe, located on the Informatica installation CD.
The Welcome screen displays.
3. Click Next.
4. Enter your name, company name, and PowerCenter/PowerMart license key.
5. Click Next.
6. Select ODBC and click Next.
The program launches the ODBC installation.
7. Click Next.
The program installs the ODBC 3.7 drivers.
8. Click Finish when the installation completes.
After you install the Merant 3.7 32-bit ODBC closed drivers, you need to create an ODBC
data source for each source and target database accessed by the client tools. Refer to the
appropriate section in this chapter for details on connecting to databases.
Uninstalling Merant ODBC 3.7 Drivers
The Merant uninstall program deletes only the Merant 3.7 32-bit ODBC closed drivers
installed from the Informatica installation CD.
To uninstall the Merant 3.7 32-bit ODBC closed drivers:
1. Open the Windows Control Panel.
2. Select Add/Remove programs.
3. Select ODBC 3.7 and click Add/Remove.
A message prompts you to remove these ODBC drivers.
4. Click OK to uninstall the Merant 3.7 32-bit ODBC closed drivers.
St ep 2. Install i ng t he Informat ica Cli ent Tool s 67
Step 2. Installing the Informatica Client Tools
You can install the Informatica Client tools on a Windows system.
The installation program allows you to choose which components you want to install. A
complete installation of all components installs the following:
All the program files you need to run the Designer, Repository Manager, Workflow
Manager, and Workflow Monitor
Informatica product manuals in PDF format
Sample repository
SQL scripts for the hands-on tutorials included in Getting Started
Release notes
Online help file for the Designer, Repository Manager, Workflow Manager, and Workflow
Monitor
The custom installation allows you to choose the components you want to install.
Informatica recommends that you make a backup and copy of all existing repositories before
upgrading to PowerCenter 6.0 or PowerMart 6.0. You should upgrade the copy of your
existing repository so you can evaluate it without altering your existing repository.
You can install multiple versions of the Informatica Client tools on the same machine. To
determine which version starts when you launch the Designer, Repository Manager,
Workflow Manager, or Workflow Monitor, edit the following entry in the system win.ini file:
[Informatica PowerMart]
home=<Informatica_Client_installation_directory>
Edit the entry with the name of the installation directory of the Informatica Client version
you want to use.
Note: You must be the Administrator on the local machine to install the Informatica Client
tools.
To install the Informatica Client tools:
1. Close all open applications.
2. From Windows, run setup.exe, located on the Informatica installation CD.
The Welcome screen displays.
Note: If installing from your network, the Windows system must be mapped to the root
directory of the CD to run the setup program.
3. Click Next.
4. Enter your name, company name, and PowerCenter/PowerMart license key.
5. Click Next.
6. Select Client.
7. Click Next to launch the client installation.
8. The client tools setup welcome screen displays.
9. Click Next.
10. Choose the directory where you want to install the Informatica Client tools.
If you have an existing version of the Informatica Client tools installed on the machine,
the existing version installation directory displays as the default installation directory.
The installation program overwrites any existing Informatica Client tools files in the
installation directory.
11. Click Next.
12. Specify the program folder in which the client icons will appear.
13. Click Next.
14. Select the components you want to install. By default, all components are selected.
Table 4-2 describes the components you can install:
15. Click Next.
16. The PowerCenter/PowerMart Client Tools Setup copies the selected components to your
installation directory.
17. When the installation completes, select View Readme if you want to read the
PowerCenter/PowerMart release notes.
18. Click Finish to exit the Client Tools Setup.
19. Click Finish to exit the Informatica Platform Setup and return to Windows.
Table 4-2. Informatica Client Components
Component Description
Program and Configuration Files The files required to run and configure the Informatica Client, including
the readme file and online help.
Documentation Files Informatica product manuals in PDF format.
Tutorial Files Sample SQL scripts you can use to create the source tables and stored
procedures used in the tutorial lessons in Getting Started.
Sample Repository A sample repository file, stored in an .rep backup file.
Step 3. Connecti ng t o Databases 69
Step 3. Connecting to Databases
To communicate with databases, the Informatica Client tools use both native database
connectivity software and ODBC.
Connecting to an Oracle Database
You need to connect each Informatica Client to each Oracle source and target database.
You must install the same version of the Oracle Client on each machine hosting the Oracle
database server, the Informatica Client, and the Informatica Server.
Use the following steps as a guideline to connect to an Oracle database through Oracle Net
Services or Net8. For specific connectivity instructions, refer to your database documentation.
To connect to an Oracle database with Oracle Net Services or Net8:
1. Install the Oracle software.
2. Configure the Oracle client. You can use the Oracle Net Services or Net8 utility or copy
an existing TNSNAMES.ORA and SQLNET.ORA file and modify it as needed.
TNSNAMES.ORA and SQLNET.ORA are stored in the
<oracle_home>\NETWORK\ADMIN directory.
Enter the correct syntax for the Oracle connect string, typically, databasename.world.
Use TCP/IP as the network protocol. PowerCenter and PowerMart support only the
TCP/IP protocol for Oracle databases.
Here is a sample TNSNAMES.ORA:
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world)
(PROTOCOL = TCP)
(Host =mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
Make sure the SID entered here matches the database server instance ID defined on the
Oracle server.
3. Verify that the system path includes the Oracle bin directory.
For example, if you install Net8 on a Windows system, your path might include the
following entry:
C:\ORACLE\ORA8\BIN
4. Launch SQL*Plus and try to connect to the database.
Use the correct connect string (as defined in TNSNAMES.ORA) and username. Make
sure SQL*Plus connects correctly before continuing.
5. Create an ODBC connection for each Oracle database.
Use the Merant 3.7 32-bit ODBC closed driver included on the Informatica installation
CD.
The Oracle server name must be the same in both the ODBC Administrator and
TNSNAMES.ORA. Oracle server names usually have the following format:
databasename.world.
6. In the Workflow Manager, create a database connection for each database.
See Configuring the Workflow Manager in the Workflow Administration Guide.
7. On Oracle databases, if the database character set is not the default, configure the
database to use the U.S. English character set:
On Windows 98, add the following entry to the autoexec.bat file:
SET NLS_LANG=american_america.UTF8
On other Windows systems, double-click System in the Control Panel. In the
Environment tab, set the System Variable to NLS_LANG and the value to
american_america.UTF8.
Connecting to a Microsoft SQL Server Database
Use the following steps as a guideline to connect each Microsoft SQL Server source or target
database to the Informatica Client tools. For specific connectivity instructions, refer to your
database documentation.
The Informatica Client can communicate with Microsoft SQL Server 7.0 with Service Pack 1
or later and Microsoft SQL Server 2000. Install the SQL Client version 7.x or 2000 on each
client, server, and repository machine. Do not use the Merant driver included on the
Informatica installation CD.
To connect to a Microsoft SQL Server database:
1. Install the SQL Client software, including the Microsoft OLE DB Provider for SQL
Server.
2. Verify that the system path includes the Microsoft SQL Server directory.
For example, your path might include the following entry:
PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
For Windows 98, if your path does not include the Microsoft SQL Server directory, edit
your AUTOEXEC.BAT file.
3. Open the Client Network Utility. On the General tab, verify that the Default Network
Library matches the default network for your Microsoft SQL Server database.
4. Launch ISQL_w, enter the necessary information, and connect to the Microsoft SQL
Server database.
If you connect to the database, continue with the next step. If you fail to connect to the
database, verify that you correctly entered all of the connectivity information.
Tip: Usernames and database names are case-sensitive.
5. Create an ODBC connection for each Microsoft SQL Server source and target database.
6. In the Workflow Manager, create a database connection for each source and target
database. The Informatica Server uses database connections to connect to the source and
target databases.
For more information, see Configuring the Workflow Manager in the Workflow
Administration Guide.
Connecting to a Sybase Database
Use the following steps as a guideline to connect each Sybase SQL Server source or target
database to the Informatica Client tools. For specific connectivity instructions, refer to your
To connect to a Sybase database:
1. Install the Open Client software.
Install the same version of the Open Client client on the machines hosting the database
and the Informatica Server. You may encounter problems reading from and writing to the
database if you use different versions of Open Client.
2. Use SQLEDIT to configure the Sybase client, or copy an existing SQL.INI file (which is
located in %SYBASE%\ini directory) and make any necessary changes.
Select NLWNSCK as the Net-Library driver.
Enter the host name and port number for the Sybase Server. If you do not know the host
name and port number, check with your system administrator.
3. Verify that the system path includes the Sybase directory.
For example, if you install Open Client on a Windows system, your path might have the
following entry:
PATH=C:\SYBASE\BIN;C:\SYBASE\DLL
On Windows 98, if your path does not include the Sybase directory, edit your
AUTOEXEC.BAT file.
4. Verify that the SYBASE environment variable refers to the Sybase installation directory,
for example:
SYBASE=C:\SYBASE
5. Launch SYBPING, enter the connectivity information, and connect to the database. If
you connect to the database, continue to step 6. If you fail to connect to the database,
verify that you correctly entered all of the connectivity information.
Usernames and database names may be case-sensitive.
6. Create an ODBC connection for each Sybase SQL Server database.
Install the Sybase 32-bit driver included on the Informatica installation CD. For more
information, see Using ODBC on page 193.
For details on creating source and target database connections, see Configuring the
Workflow Manager in the Workflow Administration Guide.
Connecting to an Informix Database
Use the following steps as a guideline to connect each Informix source or target database to
the Informatica client tools, complete the following steps. For specific connectivity
instructions, refer to your database documentation.
To connect to an Informix database:
1. Install the ESQL for C, Informix Client SDK, or any other Informix client software.
Install compatible versions of ESQL/runtime or iconnect on the machine hosting the
Informatica Client and Informatica Server.
2. Launch the Informix SetNet32 to configure connectivity information. On the
Environment tab, verify that INFORMIXDIR is set.
For example:
INFORMIXDIR=C:\Informix
3. In SetNet32, on the Server Information tab, configure the Informix server connectivity
information.
Table 4-3 describes the options available in the Server Information tab:
Table 4-3. Informix SetNet32 Configuration
Setting Description
Informix Server Name of the Informix database server.
Host Name Host machine name or IP address where Informix database server is running.
In the Host tab, enter the following information for each Informix server:
4. Verify that the system path includes the %INFORMIXDIR%\bin directory.
For example:
PATH=%INFORMIXDIR%\bin;%PATH%
On Windows 98, if your path does not include the Informix directory, edit your
AUTOEXEC.BAT file.
5. Enable transaction logging for each repository database. Perform a level-0 archive using
ontape. The syntax is:
ontape -s -B <dbname>
This command performs the archive and turns buffered logging on at the same time.
You can also create the database with logging turned on. You can set logging to buffered
or unbuffered.
6. Launch ILogin Demo or SQLEditor, enter the necessary information, and connect to the
Informix database.
This step assumes you created the demonstration database on the machine where the
Informix database is installed. To create the demonstration database on a UNIX machine,
run dbaccessdemo7. This creates a small database called stores7, which you can use to run a
variety of tests. To create a demonstration database on Windows, run dbaccessdemo7.bat
in %INFORMIXDIR%\bin.
Note: If you connect to the database, continue with the next step. If you fail to connect to
the database, verify that you correctly entered all of the connectivity information. You
need to connect to the database before you can create an ODBC data source. For more
Protocol Name Protocol the server uses, usually onsoctcp. Ask your Informix Administrator.
Service Name Service name the Informix server uses. Ask your Informix Administrator. The
Informix server must also be defined in the services file for the following operating
systems:
Windows 98: %WINDIR%\Services
Windows NT/2000/XP: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr 1525/tcp
Setting Description
Current Host Name of the host where Informix server is running.
User Name Enter the user name for the Informix server.
Password Option Enter the password.
Password Enter the password for the Informix server.
Setting Description
information about connecting to an Informix database, refer to your Informix
documentation.
Usernames and database names may be case-sensitive. Be sure to enter the correct connect
string. The syntax is dbname@servername (for example, informixdb@myserver).
7. Create an ODBC data source for each Informix source and target database.
Install the Merant 3.7 32-bit ODBC closed driver included on the Informatica
installation CD. For details, see Using ODBC on page 193.
Connecting to an IBM DB2 Universal Database
Use the following steps as a guideline to connect each DB2 database on Windows or UNIX to
the Informatica Client tools, complete the following steps. For specific connectivity
instructions, refer to your database documentation.
To connect to a DB2 database:
1. Install or verify that you have already installed IBM DB2 Client Application Enabler
(CAE), Version 6.1 or above.
Verify that the following environment variable settings have been established by DB2
Client Application Enabler:
DB2INSTANCE = DB2
DB2CODEPAGE = 437 (Sometimes required. Use only if you encounter problems)
DB2HOME=C:\SQLLIB (where the client is installed)
Verify that the PATH environment variable includes the \BIN and \FUNCTION
subdirectories of your DB2 Client Application Enabler (CAE) installation directory
(default C:\SQLLIB). For example:
PATH=C:\WINNT\SYSTEM32;....C:\SQLLIB\BIN;C:\SQLLIB\FUNCTION;....
2. Configure or verify the configuration of the DB2 Client Application Enabler (CAE). At
least one database must be configured and set up as an ODBC source to access DB2
tables:
Open the DB2 Client Configuration Assistant program. For example, Start-Programs-
DB2 for Windows NT. A list of databases appears.
If the required database is not listed, click the Add button and follow instructions in
the DB2 Add Database SmartGuide. Remember to check Register this Database for
ODBC.
If the required database is listed, but states [Not registered] in the ODBC Name
column, you must register it. Select the database name and click Properties. Select
Register this database for ODBC and click OK.
Verify you can connect to the required database by selecting the database name and
clicking Test. Then supply a valid username and password and click OK. The
following message displays: The connection test was successful, followed by some
database details. If you cannot connect to the database, consult the DB2
documentation and/or your system administrator.
3. From the Informatica Client tools, use the data source name as registered by the DB2
client configuration tool for ODBC. Use the entry with the name labeled IBM DB2
ODBC driver. Use only this driver, and not any DB2 driver from the Merant ODBC
package supplied on the Informatica installation CD.
database.
Connecting to Microsoft Access97
These steps are provided as a guideline. For specific connectivity instructions, refer to your
Microsoft Access documentation.
To connect to an Access97 database:
1. Install Access97 on the same machine as the Informatica Server.
2. Create an ODBC connection for each Access97 database.
Microsoft Access97 installs the ODBC driver that you need to use. Select the database for
which you want to create an ODBC connection.
database.
Connecting to Microsoft Excel
PowerCenter and PowerMart treat a Microsoft Excel source as a relational database, not a flat file.
To connect to a Microsoft Excel source, you need to install the Microsoft Excel ODBC driver
provided with the software. Use the 32-bit ODBC Administrator to create a data source for each
Microsoft Excel file. You do not need database permissions to connect to Microsoft Excel.
Microsoft Excel documentation.
To connect to a Microsoft Excel source:
1. Install Microsoft Excel on the same machine as the Informatica Server.
2. Install the Microsoft Excel ODBC driver provided with Microsoft Excel.
3. Launch the 32-bit ODBC Administrator.
You can either open the Control Panel and double-click the icon for 32-bit ODBC, or
run the ODBC Administrator.
4. Click Add.
5. Select the Microsoft Excel Driver from the list of drivers and click Finish.
The ODBC Microsoft Excel Setup window appears.
6. Enter a data source name.
7. To access the Microsoft Excel file, select the version of the application.
8. Click Select Workbook and browse for the file that contains the source data. You must
create an ODBC data source for each source file.
9. Click OK to exit the ODBC Administrator.
database.
Connecting to a Teradata Source Database
To connect each Teradata source database to the Informatica Client, complete the following
steps.
Teradata documentation.
To connect to a Teradata source database:
1. Install WinDDI, Teradata Client, Teradata ODBC driver, and any other Teradata
software you might need.
2. Launch the ODBC 32-bit Data Source Administrator by selecting ODBC Data Sources
from the Control Panel.
3. From the ODBC Data Source Administrator, create and configure ODBC data sources.
Click Select Workbook to browse
for the Microsoft Excel source.
Choose the
Microsoft Excel
version.
4. To create a data source name (DSN), click the System DSN tab, and click Add.
5. Select the Teradata ODBC driver, and click Finish.
6. Enter the name for the new ODBC data source and the name of the Teradata server or its
IP address.
If necessary, enter the username and password to open a connection to the default
database.
7. Click OK twice to close the ODBC Data Source Administrator dialog box.
Troubleshooting
Creating or restoring a repository on an Oracle 8 or 8i database displays the following
error:
ORA 01026 Multiple Buffers of size > 4 K in the bind list.
In addition, Informatica Clients do not accurately display non-ASCII characters.
Set the language parameter NLS_LANG to the database character set.
For example, if an Oracle 8i database has UTF-8 as the character set, set the language
parameter as follows:
On Windows NT/2000/XP double-click System in the Control Panel. In the Environment
tab, set the System Variable to NLS_LANG and the value to american_america.UTF8.
79
C h a p t e r 5
Installing and Configuring the
Windows Repository Server
Step 1. Installing the Repository Server on Windows, 82
Step 2. Configuring the Repository Server on Windows, 83
Step 4. Starting the Repository Server on Windows, 91
Troubleshooting, 95
80 Chapter 5: Install ing and Configuring the Windows Repository Server
Before You Begin
Complete the following steps to install and configure the Repository Server on Windows:
1. Install the Repository Server.
2. Configure the Repository Server.
3. Configure database client connectivity software to connect to the repository database.
You can install one Repository Server on a Windows machine. Before you begin, locate the
PowerCenter/PowerMart product license key. Use the same product license key to install the
Repository Server, the Informatica Server, and the Informatica Client tools.
Note: Please read the release notes for last minute changes to the Repository Server installation
and connectivity issues.
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select for each PowerCenter/PowerMart component are compatible with each other. For more
information, see Globalization Overview on page 29.
Installation Guidelines
Use the following guidelines before you install the Repository Server on a Windows system:
1. To optimize performance, do not install the Repository Server on a Primary Domain
Controller (PDC) or a Backup Domain Controller (BDC).
2. Make sure you have 30 MB of disk space available on the Windows boot drive. The
Informatica Platform Setup requires this space for temporary files.
3. Verify you have the appropriate Windows user accounts to install the Repository Server,
run the Repository Server service, and access the managed repository databases.
Creating Repository Server Users
When you install the Repository Server on a Windows system, you need three different user
accounts:
1. Windows user with administrator rights. To install the Repository Server, log on to the
Windows system as a member of the Administrators group in the local domain.
2. Windows user that runs the Repository Server service. Before you install the Repository
Server, create a user account with the right to run services, known as the Service Start
Account. Verify this account has the Logon as a service right. Create this account
Bef ore You Begin 81
specifically to run the Repository Server. Do not run the Repository Server as the System
account.
For details on creating a user account to run the Repository Server service, see
Troubleshooting on page 95.
Note: You can create either a local or domain account. To manage repositories on a
Microsoft SQL Server database that uses Windows integrated security, you must create a
domain account.
3. Database user for each managed repository. When you configure the repository, you
enter a username and password to access the database containing the repository. This is
the owner name defined by the database. The Informatica Server uses this name to
connect to the repository database. This user is not a Windows or repository account.
The password must be in US-ASCII only.
Step 1. Installing the Repository Server on Windows
After you install the Informatica Client tools, you can install the Repository Server.
You can install one Repository Server on a Windows system.
To install the Repository Server, run the setup program on the Informatica installation CD as
described in this section.
To install the Repository Server:
1. Log on to the Windows machine as a user who is a member of the local Administrators
group.
2. Run setup.exe from the Informatica installation CD.
Note: If you want to install from the network, you must map the Windows system to the
root directory of the CD to run the setup program. Click Next.
3. Enter your name, your company name, and platform license key in the User Informatica
dialog box. Click Next.
4. In the Select Components dialog box, select Informatica Repository Server. Click Next.
5. The Repository Server setup application starts. Click Next.
6. In the Edit Service Account dialog box, enter the domain, username, and password for
the user account that will run the Informatica Repository Server service. The user
account must have the Logon as a service right. Click Next.
7. In the Destination Location dialog box, select the directory where you want to install the
Repository Server. Click Next.
8. In the Select Program Folder dialog box, select the program folder in the Start Menu
where you want to install the Repository Server shortcuts. Click Next.
The setup application copies files to the destination directory and installs the Repository
Server service.
9. When setup application finishes installing the Repository Server service, it starts the
Repository Server setup program. Enter the Repository Server configuration parameters
and click OK, or click Cancel to configure the Repository Server later.
For more information on configuring the Repository Server, see Step 2. Configuring the
Repository Server on Windows on page 83.
10. Select View Readme if you want to read the PowerCenter/PowerMart release notes.
11. Click Finish to complete the setup.
12. If the Repository Server is the only platform component you wish to install, click Finish
to exit the Informatica Platform setup and return to Windows.
Step 2. Confi guri ng the Reposi tory Server on Windows 83
Step 2. Configuring the Repository Server on Windows
When you install the Repository Server, you must configure it before you can start it.
You can edit the Repository Server configuration parameters when the Repository Server is
running. However, you need to stop the Repository Server and restart it for changes to the
configuration to take effect.
To configure the Repository Server on Windows:
1. If you want to configure the Repository Server after the installation program finishes
choose Informatica Repository Server-Repository Server Setup from the Windows Start
Menu.
2. The Configure Repository Server dialog box appears.
3. Enter the Repository Server configuration parameters.
Table 5-1 describes the options available in the Configure Repository Server dialog box:
Table 5-1. Repository Server Configuration Parameters on Windows
Option
Required/
Optional
Description
Server Port Number Required The port number the Repository Server uses to connect to
repository client applications. By default, this value is set to
5001.
Administrative Password Required The password you use to connect to the Repository Server from
the Repository Manager. Must be in US-ASCII.
Minimum Port Number Required The minimum port number the Repository Server can assign to
the Repository Agent process. By default, this value is set to
5002.
Maximum Port Number Required The maximum port number the Repository Server can assign to
the Repository Agent process. By default, this value is set to
65535.
Configuration Directory Required The name of the directory in which the Repository Server stores
repository configuration information files. You can specify either
a relative path or an absolute path. By default, this option
specifies Config.
Backup Directory Required The name of the directory in which the Repository Server stores
repository backup files. You can specify either a relative path or
an absolute path. By default, this option specifies Backup.
Plugin Directory Required The name of the directory in which the Repository Server stores
repository plugin files. You can specify either a relative path or
an absolute path. By default, this option specifies Plugin.
Severity Level Required The level of error messages written to the Repository Server
log. Specify one of the following:
- Error. Writes ERROR code messages to the log.
- Warning. Writes WARNING and ERROR code messages to
the log.
- Information. Writes INFO, WARNING, and ERROR code
messages to the log.
- Tracing. Writes TRACE, INFO, WARNING, and ERROR code
- Debug. Writes DEBUG, TRACE, INFO, WARNING, and
ERROR code messages to the log.
Output to Event Log Optional Enable this option if you want to write Repository Server
messages to the Windows Event Log. This option is disabled by
default.
Output to File Optional Enable this option if you want to write Repository Server log
messages to a file. When you enable this option, enter a file
name for the Repository Server log. This option is enabled by
default. The default Repository Server log file name is
pmrepserver.log. The Repository Server stores the Repository
Server log file in the Repository Server installation directory.
Table 5-1. Repository Server Configuration Parameters on Windows
Option
Required/
Optional
Description
The Repository Server uses native drivers to communicate with the repository database.
You must install and configure native database client connectivity software on the machine
hosting the Repository Server. To ensure compatibility between the Repository Server and the
repository database, use 32-bit database client libraries only.
For information on connecting to a Teradata database, see the Supplemental Guide.
You need to connect the Repository Server to each Oracle repository database.
database server and Informatica Server.
an existing TNSNAMES.ORA and SQLNET.ORA files and modify them as needed.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
You must use TCP/IP as the network protocol. PowerCenter and PowerMart support
only the TCP/IP protocol for Oracle databases.
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
)
Make sure the SID entered here matches the server instance ID defined on the Oracle
server.
For example, if you install Net8, your path might include the following entry:
C:\ORANT8\BIN
5. In the Repository Manager, create a repository configuration to connect the Repository
Server to the repository database. Enter all the necessary information to connect to the
Oracle database. For more information on configuring the repository, see Managing the
Repository in the Repository Guide.
database to use the U.S. English character set. In the Windows Control Panel, double-
click System. In the Environment tab, set the System Variable to NLS_LANG and the
value to american_america.UTF8.
Use the following steps as a guideline to connect each Microsoft SQL Server repository
database to the Repository Server. For specific connectivity instructions, refer to your
The Repository Server can communicate with Microsoft SQL Server 7.0 with Service Pack 1
or later and Microsoft SQL Server 2000. Install the SQL Client version 7.x or 2000 on the
Repository Server machine.
Server.
PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
4. Launch ISQL_w, and enter a database name, username, and password. Try to connect to
the Microsoft SQL Server database. If you fail to connect to the database, verify that you
correctly entered all of the connectivity information. Usernames and database names are
case-sensitive.
Use the following steps as a guideline to connect to a Sybase repository database. For specific
connectivity instructions, refer to your database documentation.
Note: If you want to create, restore, or upgrade a Sybase repository, set allow nulls by default to
TRUE at the database level. Setting this option changes the default null type of the column to
null in compliance with the SQL standard.
You must install the same version of Open Client on the machines hosting the Sybase
database and the Informatica Server. You may encounter problems reading from and
writing to the database if you use different versions of Open Client.
2. Use SQLEDIT to configure the Sybase client, or copy an existing SQL.INI file (located
in the %SYBASE%\INI directory) and make any necessary changes.
Select NLWNSCK as the Net-Library driver and include the Sybase server name.
Enter the host name and port number for the Sybase server. If you do not know the host
3. Verify that the SYBASE environment variable refers to the Sybase directory.
For example:
SYBASE=C:\SYBASE
following entry:
5. Launch SYBPING, enter the connectivity information, and attempt to connect to the
database. If you fail to connect to the database, verify that you correctly entered all of the
connectivity information.
Use the following steps as a guideline to connect to an Informix database. For specific
On Windows, Informix settings are for each user.
For Informix databases, you must install the ESQ/L version that is compatible with your
Informix database engine. Contact Informix to verify compatibility between your version of
ESQL/C and your Informix database.
Install compatible versions of ESQL/runtime or iconnect on machines hosting the
Repository Server.
For example:
3. In SetNet32, on the Server Information tab, enter the server connectivity information for
each server.
Table 5-2 describes the options available on the Server Information tab:
On the Host tab, enter the host connectivity information for the Informix Server:
Setting Description
Host Name Host machine name (or IP address) where Informix database server is
running.
Protocol Name Protocol the Informix database server uses (usually onsoctcp). Ask your
Informix Administrator.
Service Name Service name the Informix server uses. Ask your Informix Administrator.
The Informix server must also be defined in the services file for the
following operating systems:
Windows NT/2000/XP: %WINDIR%\System32\Drivers\etc\Services
inflsnr 1525/tcp
Setting Description
User Name User name for the Informix server.
Password Option Password.
Password Password for the Informix server.
For example:
If your path does not include the Informix directory, edit your AUTOEXEC.BAT file.
Informix database.
documentation.
Usernames and database names are case-sensitive. Enter the correct connect string. The
syntax is dbname@servername (for example, informixdb@myserver).
Use the following steps as a guideline to connect to an IBM DB2 Universal Database. For
specific connectivity instructions, refer to your database documentation.
To connect to an IBM DB2 database:
(CAE), Version 6.1 (or above).
DB2INSTANCE = DB2
DB2CODEPAGE = 437 (Sometimes required. Use only if you encounter
problems).
DB2HOME=C:\SQLLIB (directory where the client is installed)
Verify that the PATH environment variable includes the \BIN subdirectories of your
DB2 Client Application Enabler (CAE) installation directory (default C:\SQLLIB). For
example:
PATH=C:\WINNT\SYSTEM32;C:\SQLLIB\BIN;...
2. Configure or verify the configuration of the DB2 Client Application Enabler (CAE).
Open the DB2 Client Configuration Assistant utility. For example, Start-Programs-
DB2 for Windows. A list of databases appears.
If the required database is not listed, click the Add button and follow the instructions
in the DB2 Add Database SmartGuide.
Step 4. Starti ng the Reposi tory Server on Windows 91
Step 4. Starting the Repository Server on Windows
Start the Repository Server from the Windows Control Panel. You can specify manual or
automatic startup type for the Repository Server.
When you select the automatic startup type, the Repository Server starts automatically at
system boot time. You might want to start the Repository Server automatically if a user
without system administrator rights uses the Repository Server machine.
When you select the manual startup type, you must start the Repository Server from the
Services control panel each time you boot the Repository Server machine. You might want to
start the Repository manually if you also manually start the repository database when you
boot the machine and want to prevent repository clients from attempting to connect to the
repository until you start the database.
After you start the Repository Server, you can start the repository.
Starting the Repository Server
Complete the following steps to start the Repository Server:
To start the Repository Server:
1. Verify that the repository database is running.
2. Log on to the Windows machine as a user who can start services.
3. From the Start menu, choose Settings-Control Panel.
4. Double-click the Services icon.
5. From the scrolling list of services installed on the Windows machine, select Informatica
Repository Server.
6. Click Start.
The Repository Server might take a moment to start.
7. If you would like the Repository Server service to run every time the computer starts,
choose Automatic as the Startup Type.
8. Click OK to close the Services dialog box.
Verifying Repository Server Startup
You can verify the Repository Server started by looking in the Repository Server log file or in
the Windows Event Viewer.
If you configured the Repository Server to write messages to a file, open the file and look for
the following message:
INFO : SF_34003 Server initialization completed.
If you configured the Repository Server to write messages to the Windows event log, use the
Windows Event Viewer to verify the Repository Server started.
To verify the Repository Server started in the Windows Event Viewer:
1. Open the Event Viewer.
2. Select the Application Log.
Look for the PmRepServer source:
Event
PmRepServer
34003 displays
if the Repository
Server
successfully
starts.
Step 4. Starti ng the Reposi tory Server on Windows 93
You should see several events in the Application log for PmRepServer. Select the latest
event. It should indicate it completed initialization:
Verifying the Repository Server is Running
You can verify that the Repository Server is running and accepting client connections by using
the Repository Server ping command from the command line. You can also use the
Repository Server ping command to verify if another Repository Server on the network is
running and you can connect to it.
To ping a Repository Server from the Windows command prompt:
1. Log on to a machine with an installed Repository Server.
2. Open the Windows command prompt.
3. Switch to the Repository Server installation directory and enter the following command:
pmrepserver -p -h <hostname>:<port_number>
Specify the host name of the machine running the Repository Server you want to ping,
and the port number it uses for connections.
The Repository Server returns the following message when it pings a running Repository
Server:
Informatica Repository Server running at <hostname>:<port number>
Stopping the Repository Server
You can shut down the Repository Server from the Windows Control Panel, from the
Repository Manager, or from the Windows command prompt. You must have system
administrator rights to stop the Repository Server.
To stop the Repository Server from the Windows Control Panel:
1. Choose Services in the Control Panel.
2. Select Informatica Repository Server and click Stop.
To stop the Repository Server from the Repository Manager:
1. Launch the Repository Manager and choose Repository-Configure Repository Servers.
2. In the Configure Servers dialog box, choose the Repository Server you want to stop from
the Hostname list.
3. Enter the Repository Server administration password.
4. Click Connect.
5. Confirm that all repositories managed by the Repository Server are shut down. For details
on shutting down the repository, see Managing the Repository in the Repository Guide.
6. In the Manage Repositories dialog box, click Shutdown Server.
The Repository Server shuts down.
7. Click Close to return to the Repository Manager.
Use the following steps to shut down the Repository Server from the Windows command
prompt:
To stop the Repository Server from the Windows command prompt:
1. Log on to the Windows machine as the user who has rights to start and stop the
Repository Server service.
2. Open the Windows command prompt.
3. Switch to the Repository Server installation directory and enter the following command.
pmrepserver -s -h <host_name>:<port_number>
Specify the Repository Server administrative password, the host name of the machine
running the Repository Server, and the port number it uses for connections.
A message indicates the shutdown request was sent.
To verify that the Repository Server stopped, check the Repository Server log file. The
Repository Server writes the following message to the log file if it successfully stops:
INFO : SF_34014 Server shut down.
Troubl eshooti ng 95
Troubleshooting
This section contains information on troubleshooting the Repository Server on Windows.
I installed the Repository Server on a Windows NT system, but I cannot start the
Repository Server.
If you cannot start the Repository Server, you may receive the following message:
Error 1069 (The service did not start due to a logon failure)
Use the Windows Event Viewer to check the Application log. If possible, correct any errors
described in the application log. Also, verify the service start information.
The Service Start Account needs the advanced NT user right Log on as a service on the
Windows system. Follow these steps to verify that the account with proper rights also starts
the Repository Server:
1. In the Control Panel, double-click the Services icon.
2. In the Services dialog box, double-click Informatica Repository Server.
The following dialog box appears:
3. Select This Account, and enter the account name and password assigned to the
Repository Server service.
If the correct account user is displayed, reenter the account user to have NT verify the
rights assigned to this user.
4. Click OK.
If the user has the necessary rights to run the Repository Server, the dialog box closes.
If the user does not have the correct rights, a message appears asking if you want this user
to have the Log on as a service right. Select OK to assign the Log on as a service right to this
user.
Try to start the Repository Server again. If it does not start, call Informatica Technical
Support.
I installed the Repository Server on a Windows 2000 system, but I cannot start it.
If you cannot start the Repository Server, you may receive the following message:
Error 1069 (The service did not start due to a logon failure)
Use the Windows 2000 Event Viewer to check the Application log. If possible, correct any
errors described in the application log. Also, verify the service start information.
The Service Start Account needs the Windows 2000 user right Log on as a service on the
Windows 2000 system. Follow these steps to verify that the account has the correct rights to
start the Informatica Server:
1. In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2. Double-click the Local Security Policy icon.
3. In the Local Security Settings dialog box, expand Local Policies and select User Rights
Assignment.
4. Find the policy Log on as a service. Double click on the policy to open the Local Security
Policy Setting dialog box.
The dialog box lists the users assigned the right to Log on as a service.
5. If you need to add a user account, click Add.
6. Click OK when finished and close the Local Security Settings dialog box.
Use the following steps to verify that the account with the right to log on as a service also
starts the Informatica Repository Server service:
3. In the Services dialog box, double-click Informatica Repository Server.
The Informatica Repository Server Properties dialog box appears.
4. Open the Log On tab.
Informatica Repository Server service. You can also click Browse to search for an account
name.
If the correct account user is displayed, reenter the account user to have Windows 2000
verify the rights assigned to this user.
6. Click OK.
7. Close the Informatica Repository Server Properties dialog box and start the Informatica
Repository Server service again.
If the Repository Server does not start, call Informatica Technical Support.
99
C h a p t e r 6
UNIX Repository Server
Step 1. Installing the Repository Server, 101
Step 2. Configuring the Repository Server on UNIX, 103
Step 4. Starting the Repository Server on UNIX, 112
100 Chapter 6: Install ing and Configuring the UNIX Repository Server
Before You Begin
Complete the following steps to install and configure the Repository Server on UNIX:
1. Install the Repository Server.
2. Configure the Repository Server.
3. Configure database client connectivity software to connect to the repository database.
product license key to install the Repository Server, Informatica Server, and Informatica
Client tools.
Please read the release notes for last minute changes to the Repository Server installation and
connectivity issues.
Code Pages
select in each component of PowerCenter and PowerMart are compatible with each other. For
more information, see Globalization Overview on page 29.
Step 1. Instal l ing t he Reposi tory Server 101
Step 1. Installing the Repository Server
After you install the Informatica Client tools, you can install the Repository Server.
You can install multiple Repository Servers on the same UNIX system. However, you need to
install each Repository Server in a separate directory and use different ports.
Before you install the Repository Server, you might want to create a user in the UNIX system
to run the Repository Server. You might want to create a new user if you want to restrict the
number of users on the UNIX system who can run the Repository Server. You can grant the
new user exclusive privileges to run the Repository Server.
If you are running other Repository Server processes on the UNIX system, stop them before
installing the Repository Server.
For information on installing the Repository Server on Linux, see Installing and Configuring
PowerCenter and PowerMart in the Supplemental Guide.
To install the Repository Server on UNIX:
1. Log on to the UNIX machine.
2. Set the library path to the absolute directory path where the Repository Server is to be
installed for the following operating systems:
Table 6-1 describes the library paths for different UNIX operating systems:
3. On the Informatica installation CD, locate the directory specific to the product.
For example, if you are installing the Repository Server on a Solaris system, switch to the
unixserv/pc/solaris directory.
4. Run install.
Using a Bourne shell, type ./install.
Using a C-shell, type sh install.
5. Select the language you want to run the installation:
English
Japanese
If you are running one or more Repository Server processes, a message displays warning
you that the install may cause problems.
Table 6-1. Library Path for Repository Server on UNIX
Operating System Library Path
Solaris LD_LIBRARY_PATH
AIX LIBPATH
HP SHLIB_PATH
6. Select Repository Server from the list of components available to install.
7. Enter the Informatica product license key.
8. Enter the absolute target directory path where you want to install the Repository Server.
9. The installation program now extracts and installs the files.
10. Type Y if you want to view the readme file, or N if you wish to read it later.
11. The installation program starts the pmrsconfig configuration utility. Configure the
Repository Server.
For details on configuring the Repository Server on UNIX, see Step 2. Configuring the
Repository Server on UNIX on page 103.
12. Exit from the Informatica Platform installation.
See the next section for Repository Server configuration details. You need to configure
the Repository Server before you can start it.
Step 2. Conf iguring the Reposit ory Server on UNI X 103
Step 2. Configuring the Repository Server on UNIX
After you install the Repository Server on UNIX, you need to configure it with the
pmrsconfig utility. This utility writes your configuration parameters to the file
pmrepserver.cfg. You configure the connectivity, logging, and administration password
information in pmrsconfig.
By default, this file is stored in the same directory as pmrepserver. If you rename
pmrepserver.cfg or move it to another directory, you must include the name and path when
you open the configuration file in pmrsconfig.
You need to include an entry for all required parameters before you can start the Repository
Server.
To configure the Repository Server on UNIX:
1. Run the pmrsconfig utility and open pmrepserver.cfg.
2. Enter the following settings to configure the Repository Server:
Table 6-2. Configuration Parameters for Repository Server on UNIX
Option
Required/
Optional
Description
ServerPort Required The port number the Repository Server uses for repository client
connections. By default, this value is set to 5001.
AdminPasswd Required The administrative password used to access the Repository Server.
Must be in US-ASCII only.
RaMinPort Required The minimum port number the Repository Server can assign to the
Repository Agent process. By default, this value is set to 5002.
RaMaxPort Required The maximum port number the Repository Server can assign to the
Repository Agent process. By default, this value is set to 65535.
ConfigDir Required The name of the directory in which the Repository Server stores
repository configuration information files. You can specify either a
relative path or an absolute path. By default, this option specifies
Config.
BackupDir Required The name of the directory in which the Repository Server stores
repository backup files. You can specify either a relative path or an
absolute path. By default, this option specifies Backup.
PluginDir Required The name of the directory in which the Repository Server stored
repository plugin files. You can specify either a relative path or an
absolute path. By default, this option specifies Plugin.
3. Save your changes and close the file.
ErrorSeverityLevel Required The level of error messages written to the Repository Server log.
Specify one of the following:
- Warning. Writes WARNING and ERROR code messages to the
log.
- Tracing. Writes TRACE, INFO, WARNING, and ERROR code
- Debug. Writes DEBUG, TRACE, INFO, WARNING, and ERROR
code messages to the log.
This option is set to Information by default.
LogFileName Required The name of the Repository Server log file. The default Repository
Server log file name is pmrepserver.log.
Table 6-2. Configuration Parameters for Repository Server on UNIX
Option
Required/
Optional
Description
The Repository Server uses native drivers to communicate with the repository database.
You must install and configure native database client connectivity software on the machine
hosting the Repository Server. To ensure compatibility between the Repository Server and the
repository database, use 32-bit database client libraries only.
You need to configure the Repository Server to communicate with the database server
managing each repository database. This section outlines specific steps for each database.
However, the following steps provide a brief overview of the tasks you need to complete to
configure the Repository Server:
1. Install the native client software on the machine hosting Repository Server.
2. Set the database environment variable to the database installation directory.
3. Set the PATH variable to include the directory where the Repository Server is installed.
4. Set the shared library environment variable:
Follow these guidelines when you use a UNIX shell:
For example, if you have an Oracle repository and the Repository Server is installed on
Solaris, you could set the shared library variables as follows:
Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmrepserver_dir:$ORACLE_HOME/
lib; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
pmrepserver_dir:$ORACLE_HOME/lib
5. Verify the system path includes the database installation directory.
6. Test connectivity through the native tool, such as SQL*Plus.
Table 6-3. Library Path for Repository Server on UNIX
Operating System
Shared Library
Environment Variable
AIX LIBPATH
HP SHLIB_PATH
Shell To Modify Environment Variable
C-shell setenv PATH ${PATH}:/usr/mypath
Bourne Shell PATH=${PATH}:/usr/mypath; export PATH
For information on supported datatypes for each database see Datatype Reference in the
Designer Guide.
You need to connect each Repository Server to each Oracle repository database.
To connect to an Oracle database through Oracle Net Services or Net8:
Install the same version of Oracle Net Services or Net8 on the machine hosting the
Oracle database and Repository Server. If you have different versions installed, you may
experience difficulties reading from and writing to the database.
2. Set the ORACLE_HOME environment variable to the Oracle installation directory. For
example:
Using a Bourne Shell:
$ ORACLE_HOME=/HOME2/ORACLE; export ORACLE_HOME
Using a C-shell:
$ setenv ORACLE_HOME=/HOME2/ORACLE
3. Set the shared library environment variable.
The shared library path must include the database library path as well as the
PowerCenter/PowerMart library path.
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Repository Server
installation directory. If you installed the Repository Server in the $HOME/pmrepserver
directory, you could type:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmrepserver_dir:$ORACLE_HOME/
lib; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/pmrepserver_dir
:$ORACLE_HOME/lib
4. Set the TNS_ADMIN environment variable to the path for TNSNAMES. For example:
$ TNS_ADMIN=/HOME2/NETWORK/ADMIN; export TNS_ADMIN
Using a C-shell:
$ setenv TNS_ADMIN=/HOME2/NETWORK/ADMIN
Note: This step is optional, and might vary depending on your configuration.
5. Ensure that the system path includes an entry for Oracle.
$ PATH ${PATH}:$ORACLE_HOME/BIN; export PATH
Using a C-shell:
$ setenv $PATH ${PATH}:ORACLE_HOME/BIN
6. Configure the Oracle client. Use the SQL*Net Easy Configuration Utility or copy an
existing TNSNAMES.ORA file and modify it as needed.
TNSNAMES.ORA is stored in the <oracle_home>/NETWORK/ADMIN directory.
Enter the correct syntax for the Oracle connect string, that is databasename.world.
Here is a sample TNSNAMES.ORA. You need to enter the information for your
database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
7. Launch SQL*Plus and try to connect to the database. If you fail to connect to the
Use the correct connect string (as defined in TNSNAMES.ORA) and username.
Usernames and database names are case-sensitive.
database to use the U.S. English character set:
On other Windows systems, double-click System in the Control Panel. In the
Environment tab, set the System Variable to NLS_LANG and the value to
american_america.UTF8.
Install the same version of Open Client on the machines hosting the database and the
Repository Server. You may encounter problems reading from and writing to the database
if you use different versions of Open Client.
For example, if you install Open Client on a UNIX system, you might use the following
entry:
$ PATH=${PATH}:/usr/sybase/bin; export PATH
Using a C-shell:
$ setenv PATH ${PATH}:/usr/sybase/bin
For example, on Solaris, set the LD_LIBRARY_PATH variable to the Repository Server
installation directory. For example, if you installed the Repository Server in the $HOME/
pmrepserver directory, you could type:
$ LD_LIBRARY_PATH=$HOME/pmrepserver_dir:$SYBASE/lib; export
LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmrepserver_dir:$SYBASE/lib
Note: $SYBASE is the directory where Sybase is installed.
4. Verify the Sybase server name in the Sybase interfaces file (stored in the $SYBASE/
interfaces).
5. Launch ISQL, enter the connectivity information, and connect to the database.
If you fail to connect to the database, verify that you correctly entered all of the
1. Install the ESQL/C client software.
Install compatible versions of ESQL/C on the machines hosting the Repository Server
and Informix databases.
2. Set the environment variables:
INFORMIXDIR (where Informix is installed, for example /databases/informix)
INFORMIXSERVER (the name of the Informix server, for example, INFSERVER)
3. Make sure INFORMIXSERVER matches one of the servers defined in
$INFORMIXDIR/etc/sqlhosts file.
4. Make sure the Service (last column entry for the server named in the sqlhosts file) is
defined in the services file (usually /etc/services). If not, define the Informix Services
name in the Services file.
Enter the Services name and port number. The default port number is 1525, which
should work in most cases.
See your Informix and UNIX documentation for details.
5. Verify that the system path includes the $INFORMIXDIR/bin directory.
$ PATH=${PATH}=$INFORMIXDIR/bin; export PATH
Using a C-shell:
$ setenv PATH ${PATH}:$INFORMIXDIR/bin
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Repository Server
installation directory. If you installed the Repository Server in the $HOME/pmrepserver
$ LD_LIBRARY_PATH=$HOME/pmrepserver_dir:$INFORMIXDIR/lib:$INFORMIXDIR/
lib/esql; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmrepserver_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql
7. Optional. Set the $ONCONFIG environment variable to the Informix configuration file
name.
8. If you plan to call Informix stored procedures in mappings, set all of the date parameters
to the Informix datatype Datetime year to fraction(5).
9. On UNIX platforms only, make sure the DBDATE environment variable is not set.
For example, to check if DBDATE is set, you might type the following at a UNIX
prompt:
$ env | grep -i DBDATE
If DBDATE=MDY2/ appears, unset DBDATE by typing:
$ unsetenv DBDATE
10. Launch dbaccess, enter the necessary information, and connect to the Informix database.
If a DB2 database server is running, or the DB2 Connect option is installed, database
connections may already be available. If not, complete the following steps. These
examples use the C-shell and assume you are logged in as the user where you intend to
run the Repository Server (pmrepserver).
2. Install or verify that the UNIX IBM DB2 software, including the Client Application
Enabler (CAE), is installed at different locations, depending on the operating system
platform. The DB2DIR environment variable should always be set to point at this base
installation directory. The IBM DB2 Version 6.1 defaults are as follows:
For Solaris:
$ setenv DB2DIR /opt/IBMdb2/v6.1
For HP-UX:
For AIX:
$ setenv DB2DIR /usr/lpp/db2_06_01
3. The UNIX IBM DB2 software always has an associated user login, often db2admin,
which serves as a holder for database configurations. This user holds the instance for
DB2. Set the following environment variables to enable access to the instance:
$ setenv DB2INSTANCE db2admin [The name of the instance holder]
$ setenv INSTHOME ~db2admin [db2admin's home directory path]
4. The UNIX IBM DB2 software uses a number of shared library components that are
loaded dynamically by the Repository Server. To locate the shared libraries at run-time,
the shared library environment variable requires alteration, depending on operating
system platform:
For example, on Solaris:
$ setenv LD_LIBRARY_PATH $DB2DIR/lib:${LD_LIBRARY_PATH}
5. To run IBM DB2 command line programs, the PATH environment variable should be
edited as follows:
$ setenv PATH $DB2DIR/bin:${PATH}
6. Edit into your (.cshrc) the complete set of shell commands appropriate to your operating
system platform. Either log out and in again, or issue the command:
$ source .cshrc
7. If you are configuring a new DB2 installation, you need to set up a remote database. Run
the DB2 Command Line Processor (db2) and issue the CATALOG <protocol> NODE
and CATALOG DATABASE commands to set up a remote database.
Consult the DB2 installation guide for details.
8. Verify the name of your remote database. Run the DB2 Command Line Processor (db2)
and issue the LIST DATABASE DIRECTORY command for a list of available databases.
It is recommended that database entries for use with Repository Server exactly match
those in the client tools.
9. Verify you can connect to the DB2 database. Run the DB2 Command Line Processor
(db2) and issue the command:
CONNECT TO <databasename> USER <username> USING <password>
If connection is successful, disconnect and cleanup with the TERMINATE command.
Step 4. Starting the Repository Server on UNIX
The procedure for starting the Repository Server is the same for all UNIX platforms. You can
start the Repository Server from the UNIX command line.
Starting the Repository Server
Use the following steps to start the Repository Server on UNIX.
To start the Repository Server:
1. Connect to the UNIX machine on which the Repository Server is installed.
Log on as a user who has rights to start and stop the Repository Server.
2. Type the following command:
pmrepserver [configuration_file_name]
By default, the Repository Server uses the pmrepserver.cfg configuration file
automatically when it starts. If you want to use a different configuration file, specify the
configuration file name.
The Repository Server displays a message indicating that is has started.
To verify that the Repository Server started, check the Repository Server log file. The
Repository Server writes the following message to the log file if it successfully starts:
INFO : SF_34003 Server initialization completed.
Verifying the Repository Server is Running
You can verify that the Repository Server is running and accepting client connections by using
the Repository Server ping command from the command line. You can also use the
Repository Server ping command to verify if another Repository Server on the network is
running and you can connect to it.
To ping a Repository Server from the command prompt:
1. Log on to a machine with an installed Repository Server.
2. Switch to the Repository Server installation directory and enter the following command:
pmrepserver -p -h <hostname>:<port_number>
Specify the host name of the machine running the Repository Server you want to ping,
and the port number it uses for connections.
The Repository Server returns the following message when it pings a running Repository
Server:
Informatica Repository Server running at <hostname>:<port number>
St oppi ng the UNIX Reposit ory Server 113
Stopping the UNIX Repository Server
You can stop the UNIX Repository Server from the UNIX command prompt or from the
Repository Manager. When you stop the Repository Server, it also shuts down all repositories
it manages. Before you shut down the Repository Server, verify that no users are connected to
managed repositories.
Use the following steps to stop the Repository Server from the UNIX command prompt.
To stop the Repository Server from the command prompt:
1. Connect to the UNIX machine on which the Repository Server is installed.
Log on as the user who has rights to start and stop the Repository Server.
2. Switch to the Repository Server installation directory and enter the following command.
pmrepserver -s -h <host_name>:<port_number>
Specify the Repository Server administrative password, the host name of the machine
running the Repository Server, and the port number it uses for connections.
A message indicates the shutdown request was sent.
To verify that the Repository Server stopped, check the Repository Server log file. The
Repository Server writes the following message to the log file if it successfully stops:
INFO : SF_34014 Server shut down.
Use the following steps to stop the Repository Server from the Repository Manager.
To stop the Repository Server from the Repository Manager:
2. In the Configure Servers dialog box, choose the Repository Server you want to stop from
the Hostname list.
4. Click Connect.
5. Confirm that all repositories managed by the Repository are shut down.
6. In the Manage Repositories dialog box, click Shutdown Server.
The Repository Server shuts down.
115
C h a p t e r 7
Creating a Repository
Overview, 116
Creating a Repository, 117
Tips, 123
116 Chapter 7: Creating a Repository
Overview
After you install and configure the Informatica Client and Repository Server, you can create a
repository. A repository contains metadata you create using the Informatica Client tools and
the Informatica Server uses to move and transform data from sources to targets.
Use the Repository Manager to create and administer the repository. The Repository Manager
connects to the repository database through the Repository Server, so you must install and
configure the Repository Server before working with repositories. There are three different
types of repository:
Standalone repository. A repository that functions individually, unrelated and
unconnected to other repositories.
Global repository. (PowerCenter only.) The centralized repository in a domain, a group of
connected repositories. Each domain can contain one global repository. The global
repository can contain common objects to be shared throughout the domain through
global shortcuts.
Local repository. (PowerCenter only.) A repository within a domain that is not the global
repository. Each local repository in the domain can connect to the global repository and
use objects in its shared folders.
Once you create a global repository, you cannot change it to a local repository. However, you
can promote an existing local repository to a global repository.
Warning: The Informatica repository tables have an open architecture. Although you can view
the repository tables, Informatica strongly advises against altering the tables or data within the
tables. Informatica is not responsible for corrupt data that is caused by customer alteration of
the repository tables or data within those tables.
Creati ng a Reposi tory 117
Creating a Repository
Before you can create a repository, you must first create and configure the database to contain
the repository and install and configure the Repository Server and Informatica Client tools.
You can locate the repository on the source or target database systems. However, to protect
your repository, consider keeping the repository separate from overloaded machines. Verify
the following requirements for the repository database:
Windows NT/2000/XP or UNIX operating system
100 MB disk space (100-150 MB is recommended)
You can locate the Repository Server on the source or target database systems. To improve
repository performance, consider installing the Repository Server on a machine with a fast
network connection. The Repository Server can manage repositories on different machines on
the network. Verify the following requirements for the Repository Server machine:
Windows NT/2000/XP, or UNIX operating system
40 MB disk space
32 MB RAM, plus 16 MB RAM for each repository the Repository Server manages
For more information on installing and configuring the Repository Server, see Installing and
Configuring the UNIX Repository Server on page 99, and Installing and Configuring the
Windows Repository Server on page 79.
When you create a repository, you must have the following information available:
Database username and password. This login must have the appropriate database
permissions to create the repository. In the new repository, this login becomes a default
user with full privileges in the repository. The username may be in other languages, but the
password must be in US-ASCII only.
Code page. When you create a repository, you must specify a code page from a list of code
pages that are compatible with the Informatica Client. The code page contains the
character set of the data in the repository. Once specified, you cannot change the code
page. The Informatica Client and Server code pages must be compatible with the
repository code page.
For more information on code pages, see Globalization Overview on page 29.
Do not use the following characters when creating a repository name:
\ / : * ? < > " | .
To create a repository:
2. Enter the host name and port number of the machine running the Repository Server, and
enter the Repository Server administration password.
3. Click Connect. The Manage Repositories dialog box appears.
4. Choose Repository-Create. The Repository Server prompts you to complete a repository
configuration.
5. Click OK. The Repository Configuration dialog box appears, displaying the Repository
tab.
6. Enter the Repository parameters.
Table 7-1 describes the repository connectivity options available on the Repository tab:
7. Click the Network tab.
8. Edit the Network configuration parameters.
Table 7-1. Repository Database Connectivity Configuration
Option
Required/
Optional
Description
DatabaseType Required The type of database storing the repository.
CodePage Required The repository code page. This option is set to MS Windows Latin
1 by default.
RepositoryName Required The name of the repository.
ConnectString Required The native connect string the Repository Server uses to access the
database containing the repository. Note that this is not an ODBC
data source name, but a native connect string (for example,
servername@dbname for Microsoft SQL Server, or dbname.world
for Oracle). For a list of native connect string syntax for supported
repository databases, see Table 2-3 on page 23.
DBUser Required The account for the database containing the repository. Set up this
account using the appropriate database client tools.
DBPassword Required The repository database password corresponding to the database
user. Must be in US-ASCII only.
Table 7-2 describes the repository Server network settings available on the Network tab:
9. Click the Configuration tab.
10. Edit the repository configuration parameters.
Table 7-2. Repository Network Configuration
Option
Required/
Optional
Description
MessageReceiveTimeout Required Amount of time in seconds the Repository Server waits to receive a
message from a client application before timing out. This option is set
to 3 seconds by default.
MessageSendTimeout Required Amount of time in seconds the Repository Server waits while
attempting to send a message to a client application before timing
out. This option is set to 3 seconds by default.
Table 7-3 describes the repository configuration options available on the Configuration
tab:
11. Click OK. The Repository Server begins building the repository. You can see the progress
in the Repository Manager Output window.
12. If you use PowerCenter, the Repository Manager prompts you to create a global
repository. To create a global repository, click Yes. To create a local repository, click No.
Once created, you cannot change a global repository to a local repository. If you are not
sure you want to create a global repository, click No. You can promote an existing local
repository to a global repository later.
Table 7-3. Repository Configuration
Option
Required/
Optional
Description
MaximumConnections Required The maximum number of connections the repository accepts from
repository client applications. By default, this value is set to 200.
ErrorSeverityLevel Required The level of error messages written to the repository log file. Specify
one of the following:
- Error. Writes ERROR code messages to the log file.
- Warning. Writes WARNING and ERROR code messages to the log
file.
- Information. Writes INFO, WARNING, and ERROR code messages
to the log file.
- Trace. Writes TRACE, INFO, WARNING, and ERROR code
messages to the log file.
Informatica recommends using the Trace and Information logging
levels for troubleshooting purposes only. Default is Warning.
DateDisplayFormat Required If specified, the Repository Server validates the date display format
and uses it when writing entries to the repository log file. If the date
display format is invalid, the Repository Server uses the
PowerCenter/PowerMart default date display format. The default date
display format is DY MON DD HH 24:MI:SS YYYY.
DynamicConfig
RefreshInterval
Required The number of seconds the repository waits to poll for updates to its
configuration. By default, this value is set to 10 seconds.
ThreadWaitTimeout Required The number of seconds the repository waits for a thread to complete
a process before timing out. By default, this value is set to 10
seconds.
MaximumLocks Required The maximum number of locks the repository places on metadata
objects. By default, this value is set to 55555.
LogFileName Required The path and name of the Repository Agent process log file. If you do
not specify a unique log file name, the Repository Agent process
automatically writes messages to pmrepagent.log. By default, this
option specifies pmrepagent.log.
13. In the Manage Repositories dialog box, select the repository and click Start. The
Repository Server starts the repository.
Ti ps 123
Tips
The following tips help you create a repository:
Set Oracle storage parameters to prevent the repository from using excessive amounts of
disk space.
When creating a repository in an Oracle database, make sure the storage parameters specified
for the tablespace that contains the repository are not set too large. Since many target
tablespaces are initially set for very large INITIAL and NEXT values, large storage parameters
cause the repository to use excessive amounts of space. Also verify that the default tablespace
for the user that owns the repository tables is set correctly.
The following example shows how to set the recommended storage parameters, assuming the
repository is stored in the REPOSITORY tablespace:
ALTER TABLESPACE REPOSITORY DEFAULT STORAGE ( INITIAL 10K NEXT 10K
MAXEXTENTS UNLIMITED PCTINCREASE 50 );
These parameters should be verified or changed before the repository is created.
To change a global repository to a local repository, back up and restore the repository.
If you want to change a global repository to a local repository, back up the global repository to
a backup file. When you restore the repository, click No when the Repository Server prompts
you to create a global repository.
For details on backing up and restoring the repository, see Managing the Repository in the
Repository Guide.
125
C h a p t e r 8
Informatica Windows Server
Step 1. Installing the Informatica Windows Server, 129
Step 2. Configuring the Informatica Windows Server, 131
Step 4. Starting and Stopping the Informatica Server, 148
Troubleshooting, 152
126 Chapter 8: Install ing and Configuring the Informatica Windows Server
Before You Begin
Complete the following steps to install and configure the Informatica Server on Windows:
1. Install the Informatica Server.
2. Configure the Informatica Server.
3. Configure database connectivity for source and target databases.
4. Register the Informatica Server in the Workflow Manager.
product license key to install the Informatica Server and Informatica Client tools.
Note: Please read the release notes for any last minute changes to the Informatica Server
installation and connectivity issues.
Code Pages
DHCP
When configuring the Informatica Server, avoid using the Dynamic Host Configuration
Protocol (DHCP) for machine hosting the Informatica Server.
DHCP dynamically assigns a new IP address each time you start a machine on the network. If
you use DHCP on the Informatica Server machine, each time you start the Informatica
Server, you must re-register the Informatica Server with the repository so the Informatica
Client can communicate with the Informatica Server at the new address.
If the Informatica Server machine has only one network card, after starting the Informatica
Server, edit the existing Informatica Server connection information in the Workflow Manager.
You may need to resolve the Informatica Server IP address in the Server Editor dialog box in
the Workflow Manager.
If the Informatica Server machine has multiple network cards, configure the Informatica
Server with the desired IP address in the Informatica Server setup program. After you
configure the Informatica Server with the correct IP address, you can start it. You may also
need to resolve the Informatica Server IP address in the Server Editor dialog box in the
Workflow Manager.
Installation Guidelines
Use the following guidelines before you install the Informatica Server on a Windows system:
1. To optimize performance, do not install the Informatica Server on a Primary Domain
Controller (PDC) or a Backup Domain Controller (BDC).
2. Verify that the date and time are correct on the host computer task bar. Make sure the
time zone is correct to ensure that your workflows run when you expect. The Workflow
Manager displays the date and time based on the machine hosting the Informatica Server.
Note: You must set the short date format to MM/DD/YYYY on Windows.
3. Make sure you have 30 MB of disk space available on the Windows boot drive. The
Informatica Platform Setup requires this space for temporary files.
4. If you are upgrading your version of the Informatica Server, stop the Informatica service
before running the installation program.
Creating Informatica Server Users
When you install the Informatica Server on a Windows system, you need the following user
accounts:
1. Windows user with administrator rights. To install the Informatica Server, log on to the
Windows system as a member of the Administrators group in the local domain.
2. Windows user that runs the Informatica Server service. Before you install the
Informatica Server, create a user account with the right to run services, known as the
Service Start Account. To see if this account has the correct rights, run User Manager for
Domains and select the user. Select User Rights from the Policies menu. The user must
have the Logon as a service right. Create this account specifically to run the Informatica
Server. Do not run the Informatica Server as the System account.
Note: You can create either a local or domain account. To send email when you run a
workflow or access a repository on a Microsoft SQL Server database that uses Windows
integrated security, you must create a domain account.
3. Repository user. When you configure the Informatica Server, you enter a repository
username and password specific to the Informatica Client and Informatica Server tools.
This is created using Repository Manager and is not a Windows account.
Informatica Server Variable Directories
The installation program creates the following directories under the installation directory to
store session files and caches associated with each Informatica Server:
BadFiles
Cache
ExtProc
SessLogs
SrcFiles
Temp
TgtFiles
WorkflowLogs
All workflows configured to run on the registered Informatica Server use these directories by
default. For details, see Registering the Informatica Server on page 183.
If you are running the Informatica Server on Windows 2000, you must have write, full
control, and modify permissions on the session log file directory to start the Informatica
Server.
Step 1. I nstal li ng the I nf ormati ca Wi ndows Server 129
Step 1. Installing the Informatica Windows Server
After you install the client tools, install the Repository Server, and create a repository, you can
install the Informatica Server.
You can install only one Informatica Server on a Windows system.
To install the Informatica Server, run the setup program on the Informatica installation CD as
described in this section.
To install the Informatica Server:
1. Log on to the Windows machine as a user who is a member of the local Administrators
group.
2. Run setup.exe from the Informatica installation CD.
Note: If installing from the network, you must map the Windows system to the root
directory of the CD to run the setup program. Click Next.
3. Enter your name, company name, and product license key. Click Next.
4. Select Server. Click Next.
The Server setup application starts. Click Next.
5. When the Edit Service Account dialog box appears, enter the Service Start Account
information for the Informatica service.
Table 8-1 describes the options available in the Edit Service Account dialog box:
6. Click Next.
Table 8-1. Installation Parameters for Informatica Server on Windows
Option
Required/
Optional
Description
Domain Optional The domain for the Windows system where you want to install the
Informatica Server. If the user account for the Informatica service is
a local user account, you can leave this field blank, enter a .
(single period, no quotes), or enter the name of the machine on
which you are running the installation program.
User Required The Windows user with rights to run the Informatica service
(Service Start Account). This user must have the Log on as a
service right.
Password Required The password for the Service Start Account. Must be in US-ASCII
only.
Confirm
Password
Required The password for the Service Start Account.
7. When prompted, select the directory where you want to install the Informatica Server.
You can either select an existing directory or have the installation program create a new
directory.
8. Click Next.
The setup application copies files to the destination directory and installs the Informatica
Server service. When the setup application finishes installing the Informatica Server
service, it starts the Informatica Server setup program.
9. Click Continue to configure the Informatica Server, or click Exit to configure the
Informatica Server later.
For more information on configuring the Informatica Server, see Step 2. Configuring
the Informatica Windows Server on page 131.
10. Click Finish to exit the PowerCenter/PowerMart Server Setup.
11. On Windows NT, the installation program prompts you to restart Windows. You must
restart Windows before you can start the Informatica Server service.
12. If the Informatica Server is the only platform component you wish to install, click Finish
to exit the Informatica Platform setup.
St ep 2. Confi guri ng the I nf ormati ca Wi ndows Server 131
Step 2. Configuring the Informatica Windows Server
After you complete the installation, you must configure the Informatica Server before you can
start it. Make note of the settings you enter for the Informatica Server. You need to enter the
same settings when you create database connections and register the Informatica Server in the
Workflow Manager. You must include an entry for all required configuration parameters
before you start the Informatica Server.
You can make changes to the Informatica Server configuration parameters. These changes
take effect when you stop and restart the Informatica Server.
Before you can run a workflow, you need to complete the following steps in the Workflow
Manager:
Register the Informatica Server in the repository.
Configure the source and target database connections.
For details, see Registering the Informatica Server on page 183.
Note: ODBC databases, such as Microsoft Access97 and Excel, are compatible with the
Informatica Server on a Windows system. However, they are not compatible with the
Informatica Server installed on a UNIX system.
For information on additional Informatica Server configuration parameters, see Installing
and Configuring PowerCenter and PowerMart in the Supplemental Guide.
To configure the Informatica Server on Windows:
1. If the configuration screen is not displayed from the installation, choose Programs-
Informatica Server-Informatica Server Setup from the Windows Start Menu.
2. Select the Configure Informatica Service option and click Continue.
The Configure Informatica Service dialog box appears, displaying the Keys tab.
3. Enter the keys needed to run the Informatica Server against your particular database
platforms.
For information about entering the license key for Teradata, see the Supplemental Guide.
Table 8-2 describes the options available in the Keys Tab:
Table 8-2. Keys Configuration for Informatica Server on Windows
Option
Required/
Optional
Description
Platform Key Required The Windows platform key. Required when you install the
Informatica Server on a Windows system.
Oracle Key Optional The Oracle platform key. Required if the Informatica
Server accesses Oracle databases.
Sybase Key Optional The Sybase platform key. Required if the Informatica
Server accesses Sybase databases.
Informix Key Optional The Informix platform key. Required if the Informatica
Server accesses Informix databases.
Microsoft SQL Server Key Optional The Microsoft SQL Server platform key. Required if the
Informatica Server accesses Microsoft SQL Server
databases.
4. Click the Server tab.
Table 8-3 describes the options available on the Server tab:
DB2 Key Optional The DB2 platform key. Required if the Informatica Server
accesses IBM DB2 databases.
ODBC Key Optional The platform key for ODBC databases (such as Teradata).
Required if the Informatica Server accesses ODBC
databases.
Table 8-3. Server Configuration for Informatica Server on Windows
TCP/IP Option
Required/
Optional
Description
Server Name Required The name of the Informatica Server to register with the
repository. This name must match the name you specify
when you use the Workflow Manager to register the
Informatica Server.
TCP/IP Host Address Optional The TCP/IP host address as an IP number (such as
123.456.789.1), or a local host name (such as RECDB), or a
fully qualified name (such as RECDB.INVOICE.COM). If you
leave this field blank, the Informatica Server uses the default
local host address.
Table 8-2. Keys Configuration for Informatica Server on Windows
Option
Required/
Optional
Description
Max No. of Concurrent
Sessions
Required The maximum number of sessions the Informatica Server
runs at a time. Increase this value only if you have sufficient
shared memory. By default, this value is set to 10.
Shared Memory Required The amount of shared memory available for use by the
Informatica Server Load Manager process. For every 10
sessions in Max Sessions, you need at least 2,000,000 bytes
reserved in Load Manager Shared Memory. Default is
2,000,000 bytes.
Error Severity Level for
Log Files
Required The level of error messages written to the Informatica Server
log. Specify one of the following:
- Warning. Writes WARNING and ERROR code messages to
the log.
- Tracing. Writes TRACE, INFO, WARNING, and ERROR
Fail Session if Maximum
Number of Concurrent
Sessions Reached
Optional Enable this option if you want the Informatica Server to fail
the session if the number of sessions already running is
equal to the value configured for Maximum Number of
Concurrent Sessions. If you disable this option, the
Informatica Server places the session in a ready queue until
a session slot becomes available. This option is disabled by
default.
Allow mapping/session
debugging
Optional If selected, you can run the Debugger. This option is enabled
by default.
Time Stamp Workflow
Log
Optional Enable this option if you want to append a time stamp to
messages written to the workflow log. This option is disabled
by default.
Output to Event Log Optional Enable this option if you want to write Informatica Server
messages to the Windows Event Log. This option is enabled
by default.
Output to File Optional Enable this option if you want to write Informatica Server log
messages to a file. When you enable this option, enter a file
name for the Informatica Server log.
Table 8-3. Server Configuration for Informatica Server on Windows
TCP/IP Option
Required/
Optional
Description
5. Click the Repository tab.
Table 8-4 describes the options available on the Repository tab:
Table 8-4. Repository Configuration for Informatica Server on Windows
Option
Required/
Optional
Description
Repository Name Required The name of the repository when it is created in the Repository
Manager.
Repository User Required The account used to access the repository. This account is set up
in Repository Manager.
Repository Password Required The repository password corresponding to the repository
username. Must be in US-ASCII only.
Repository Server Host
Name
Required The host name of the machine hosting the Repository Server.
Repository Server Port
Number
Required The port number the Repository Server uses to communicate with
repository client applications.
6. Click the Compatibility and Database tab.
Enter the optional information needed to maintain compatibility with previous versions
of the Informatica Server and databases.
Table 8-5 describes the options available on the Compatibility and Database Tab:
Table 8-5. Compatibility and Database Configuration for Informatica NT Server
Setting
Required/
Optional
Description
PMServer 3.X
aggregate
compatibility
Optional If selected, the Informatica Server handles Aggregator
transformations as it did in PowerMart 3.x. This overrides both
Aggregate treat nulls as zero and Aggregate treat rows as insert.
If you select this option, the Informatica Server treats nulls as zeros in
aggregate calculations and performs aggregate calculations before
flagging records for insert, update, delete, or reject in Update Strategy
expressions. If you do not select this option, the Informatica Server
treats nulls as nulls and performs aggregate calculations based on the
Update Strategy transformation.
Aggregate Treat Nulls
as Zero
Optional If selected, the Informatica Server treat nulls as zero in Aggregator
transformations. If you do not select this option, the Informatica
Server treats nulls as nulls in aggregate calculations.
Aggregate Treat Rows
as Insert
Optional If selected, the Informatica Server performs aggregate calculations
before flagging records for insert, update, delete, or reject in Update
Strategy expressions. If you do not select this option, the Informatica
Server performs aggregate calculations based on the Update Strategy
transformation.
PMServer 4.0 date
handling compatibility
Optional If selected, the Informatica Server handles dates as in PowerCenter
1.0/PowerMart 4.0. If not selected, the Informatica Server handles
dates as defined in PowerCenter 6.0/PowerMart 6.0.
Date handling significantly improved in PowerCenter 1.5 and
PowerMart 4.5. If you need to revert to PowerCenter 1.0 or
PowerMart 4.0 behavior, you can configure the Informatica Server to
handle dates as in PowerCenter 1.0 and PowerMart 4.0.
Treat CHAR as CHAR
on Read
Optional If you have PowerConnect for PeopleSoft, you can use this option for
PeopleSoft sources on Oracle. You cannot, however, use it for
PeopleSoft lookup tables on Oracle or PeopleSoft sources on
Microsoft SQL Server.*
Max LKP/SP DB
Connections
Optional Allows you to specify a maximum number of connections to a lookup
or stored procedure database when you start a workflow. If the
number of connections needed exceeds this value, session threads
must share connections. This can result in a performance loss. If you
do not specify a value, the Informatica Server allows an unlimited
number of connections to the lookup or stored procedure database.
If the Informatica Server allows an unlimited number of connections,
but the database user does not have permission for the number of
connections required by the session, the session fails.
By default, this value is not specified.
Max Sybase
Connections
Optional Allows you to specify a maximum number of connections to a Sybase
database when you start a session. If the number of connections
required by the session is greater than this value, the session fails. By
default, this value is set to 100.
Max MSSQL
Connections
Optional Allows you to specify a maximum number of connections to a
Microsoft SQL Server database when you start a workflow. If the
number of connections required by the workflow is greater than this
value, the workflow fails. By default, this value is set to 100.
Number of Deadlock
Retries
Optional Allows you to specify the number of times the Informatica Server
retries a target write on a database deadlock. By default, this value is
set to 10.
Deadlock Sleep
Before Retry
(seconds)
Optional Allows you to specify the number of seconds before the Informatica
Server retries a target write on database deadlock. By default, this
value is set to 0 and the Informatica Server retries the target write
immediately.
*PowerConnect for PeopleSoft is a separate Informatica product. For more information on this product, see the
PowerConnect for PeopleSoft User and Administrator Guide.
Table 8-5. Compatibility and Database Configuration for Informatica NT Server
Setting
Required/
Optional
Description
7. Click the Configuration tab.
Enter additional miscellaneous Informatica Server configuration settings.
Table 8-6 describes the options available on the Miscellaneous tab:
Table 8-6. Miscellaneous Configuration for Informatica Server on Windows
Setting
Required/
Optional
Description
Data Movement
Mode
Required Choose ASCII or Unicode. The default data movement mode is ASCII,
which passes US-ASCII character data. To pass 8-bit ASCII and
multibyte character data from sources to targets, use Unicode mode.
Validate Data Code
Pages
Optional If you enable this option, the Informatica Server enforces data code page
compatibility. If you disable this option, the Informatica Server lifts
restrictions for source and target data code page selection, stored
procedure and lookup database code page selection, and session sort
order selection. This option is only available when the Informatica Server
runs in Unicode data movement mode.
By default, this option is enabled.
Output Session
Log In UTF8
Optional If you enable this option, the Informatica Server writes to the session log
using the UTF-8 character set. If you disable this option, the Informatica
Server writes to the session log using the Informatica Server code page.
This option is available when the Informatica Server runs in Unicode
data movement mode. By default, this option is disabled.
Warn About
Duplicate XML
Rows
Optional If you enable this option, the Informatica Server writes duplicate row
warnings and duplicate rows for XML targets to the session log. By
default, this option is enabled.
8. Click OK to save the configuration options. Click Exit to close the Server Setup dialog
box.
Create Indicator
Files for Target Flat
File Output
Optional If you enable this option, the Informatica Server creates indicator files
when you run a session with a flat file target.
Export Session Log
Lib Name
Optional If you want the Informatica Server to write session log messages to an
external library, enter the name of the library file.
Microsoft
Exchange Profile
Optional Microsoft Exchange profile used by the Service Start Account to send
post-session email. The Service Start Account must be set up as a
Domain account to use this feature.
Date Display
Format
Required If specified, the Informatica Server validates the date display format and
uses it in session log and server log entries. If the date display format is
invalid, the Informatica Server uses the default date display format. The
default date display format is DY MON DD HH 24:MI:SS YYYY. When
you specify a date display format, it displays in the test window. An
invalid date display format is marked invalid.
Table 8-6. Miscellaneous Configuration for Informatica Server on Windows
Setting
Required/
Optional
Description
To communicate with databases, the Informatica Server uses either native database
connectivity software or ODBC.
Informatica recommends using native database drivers to connect to the source and target
databases. To connect through native drivers, you must install and configure native database
client connectivity software on the machine hosting the Informatica Server. To ensure
compatibility between the Informatica Server and your source and target databases, use 32-bit
database client libraries only.
Informatica Servers running on a Windows machine can use ODBC to connect to databases.
For more information on ODBC connections, see Using ODBC on page 193.
You need to connect each Informatica Server to each Oracle source and target database.
an existing TNSNAMES.ORA and SQLNET.ORA files and modify them as needed.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
You must use TCP/IP as the network protocol. PowerCenter and PowerMart support
only the TCP/IP protocol for Oracle databases.
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
)
Make sure the SID entered here matches the server instance ID defined on the Oracle
server.
For example, if you install Net8, your path might include the following entry:
C:\ORANT8\BIN
5. In the Informatica Client tools, configure each source and target database. Enter all the
necessary information to connect to each Oracle database.
6. If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
Use the following steps as a guideline to connect each Microsoft SQL Server source or target
database to the Informatica Server. For specific connectivity instructions, refer to your
The Informatica Server can communicate with Microsoft SQL Server 7.0 with Service Pack 1
or later and Microsoft SQL Server 2000. Install the SQL Client version 7.x or 2000 on each
client, server, and repository machine. Do not use the Merant driver included on the
Server.
C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
4. Launch ISQL_w, and enter a database name, username, and password. Try to connect to
the Microsoft SQL Server database. If you fail to connect to the database, verify that you
correctly entered all of the connectivity information.
Use the following steps as a guideline to connect to a Sybase database. For specific
You must install the same version of Open Client on the machines hosting the Sybase
database and the Informatica Server. You may encounter problems reading from and
writing to the database if you use different versions of Open Client.
2. Use SQLEDIT to configure the Sybase client, or copy an existing SQL.INI file (located
in the %SYBASE%\INI directory) and make any necessary changes.
Select NLWNSCK as the Net-Library driver and include the Sybase server name.
Enter the host name and port number for the Sybase server. If you do not know the host
3. Verify that the SYBASE environment variable refers to the Sybase directory.
For example:
SYBASE=C:\SYBASE
following entry:
5. Launch SYBPING, enter the connectivity information, and attempt to connect to the
database. If you fail to connect to the database, verify that you correctly entered all of the
Use the following steps as a guideline to connect to an Informix database. For specific
On Windows, Informix settings are for each user.
For Informix databases, you must install the ESQ/L version that is compatible with your
Informix database engine. Contact Informix to verify compatibility between your version of
ESQL/C and your Informix database.
When you configure the Informatica Server to connect to an Informix database, log in as the
NT user with rights to run the Informatica service (Service Start Account).
Install compatible versions of ESQL/runtime or iconnect on machines hosting the
Informatica Client and Server.
For example:
3. In SetNet32, on the Server Information tab, enter the server connectivity information for
each server.
Table 8-7 describes the options available on the Server Information tab:
Setting Description
Host Name Host machine name (or IP address) where Informix database server is
running.
Protocol Name Protocol the Informix database server uses (usually onsoctcp). Ask your
Informix Administrator.
Service Name Service name the Informix server uses. Ask your Informix Administrator.
The Informix server must also be defined in the services file for the
following operating systems:
Windows: %WINDIR%\System32\Drivers\etc\Services
inflsnr 1525/tcp
On the Host tab, enter the host connectivity information for the Informix Server:
For example:
Informix database.
documentation.
Usernames and database names are case-sensitive. Enter the correct connect string. The
syntax is dbname@servername (for example, informixdb@myserver).
Use the following steps as a guideline to connect to an IBM DB2 Universal Database. For
specific connectivity instructions, refer to your database documentation.
To connect to an IBM DB2 database:
DB2INSTANCE = DB2
Setting Description
User Name User name for the Informix server.
Password Option Password.
Password Password for the Informix server.
DB2CODEPAGE = 437 (Sometimes required. Use only if you encounter
problems).
DB2HOME=C:\SQLLIB (directory where the client is installed)
Verify that the PATH environment variable includes the \BIN subdirectories of your
DB2 Client Application Enabler (CAE) installation directory (default C:\SQLLIB). For
example:
PATH=C:\WINNT\SYSTEM32;C:\SQLLIB\BIN;...
2. Configure or verify the configuration of the DB2 Client Application Enabler (CAE). At
least one database must be configured and set up as an ODBC source to access DB2
tables.
Open the DB2 Client Configuration Assistant utility. For example, Start-Programs-
DB2 for Windows. A list of databases appears.
If the required database is not listed, click the Add button and follow the instructions
in the DB2 Add Database SmartGuide. Remember to check Register this Database for
ODBC.
If the required database is listed, but states [Not registered] in the ODBC Name
column, you must register it. Select the database name and click Properties. Check
Register this database for ODBC and click OK.
Connecting to Microsoft Access97
Use the following steps as a guideline to connect to a Microsoft Access97 database. For
specific connectivity instructions, refer to your Microsoft Access documentation.
To connect to a Microsoft Access97 database:
1. Install Access97 on the same machine as the Informatica Server.
2. Create an ODBC connection for each Access97 database.
Microsoft Access97 installs the ODBC driver that you need to use. Select the database for
which you want to create an ODBC connection.
3. If you did not enter the ODBC key in the Informatica Server configuration, see Step 2.
Connecting to Microsoft Excel
PowerCenter and PowerMart treat a Microsoft Excel source as a relational database, not a flat file.
To connect to a Microsoft Excel source, you need to install the Microsoft Excel ODBC driver
provided with the software. Use the 32-bit ODBC Administrator to create a data source for each
Microsoft Excel file. You do not need database permissions to connect to Microsoft Excel.
However, to create the database connection in the Workflow Manager, you must enter a username
and password. Use the reserved words PmNullUser for the username and PmNullPasswd for the
password. These words indicate no username and password.
Use the following steps as a guideline to connect to a Microsoft Excel source. For specific
connectivity instructions, refer to your Microsoft Excel documentation.
To connect to a Microsoft Excel source:
1. Install Microsoft Excel on the same machine as the Informatica Server.
2. Install the Microsoft Excel ODBC driver provided with Microsoft Excel.
3. Launch the 32-bit ODBC Administrator.
4. Click Add.
5. Select the Microsoft Excel Driver from the list of drivers and click Finish.
The ODBC Microsoft Excel Setup window appears.
6. Enter a data source name.
7. To access the Microsoft Excel file, select the version of the application.
8. Click Select Workbook and browse for the file that contains the source data. You must
create an ODBC data source for each source file.
9. Click OK to exit the ODBC Administrator.
10. If you did not enter the ODBC key in the Informatica Server configuration, see Step 2.
Choose the
Microsoft Excel
version.
Connecting to a Teradata Source Database
The Informatica Server on Windows uses ODBC to connect to each Teradata source
database.
Use the following steps as a guideline to connect to a Teradata source database. For specific
connectivity instructions, refer to your Teradata documentation.
To connect to a Teradata source database:
1. Install WinDDI, Teradata Client, Teradata ODBC driver, and any other Teradata
software you might need on the Informatica Server machine.
2. Launch the ODBC 32-bit Data Source Administrator by selecting ODBC Data Sources
from the Control Panel.
3. From the ODBC Data Source Administrator, create and configure ODBC data sources.
4. To create a data source name (DSN), click the System DSN tab, and click Add. (You
must use a system data source name.)
5. Select the Teradata ODBC driver, and click Finish.
6. Enter the name for the new ODBC data source.
7. Enter the name of the Teradata server or its IP address.
If necessary, enter the username and password to open a connection to the default
database.
8. Click OK twice to close the ODBC Data Source Administrator dialog box.
9. Before you run a session, test the ODBC connection using an ODBC query tool, such as
WinDDI. Before you test the ODBC connection, log into Windows as the advanced user
with the Log on as a service right.
Step 4. Starting and Stopping the Informatica Server
You have three methods of starting and stopping the Informatica Server:
Windows Control Panel (start and stop the Informatica Server)
Workflow Manager (stop the Informatica Server)
pmcmd program (stop the Informatica Server)
Before you can start the Informatica Server, you must register it in the Workflow Manager.
You must also install, configure, and start the Repository Server. For more information, see
Registering the Informatica Server on page 183, Installing and Configuring the Windows
Repository Server on page 79, and Installing and Configuring the UNIX Repository Server
on page 99.
When you start a PowerMart Server, it verifies that it is the only Informatica Server registered
in the repository. It does not start if there are other Informatica Servers registered in the
repository.
When you send a request to stop the Informatica Server, the Informatica Server first removes
all workflows scheduled to run in the future. It then attempts to stop all running workflows.
If any workflow fails to respond within a certain period of time, the Informatica Server aborts
the remaining workflows. Allow 1 to 2 minutes for the Informatica Server to complete all
processes. When you restart the Informatica Server, you must reschedule all workflows.
Windows Control Panel
You can start and stop the Informatica Server from the Windows control panel. When you
stop the Informatica Server from the Windows Control Panel, the Informatica Server aborts
any running workflows before it stops.
To start the Informatica Server:
1. Verify that the repository database and Repository Server managing the repository are
running.
2. In the Workflow Manager, verify the Informatica Server is registered in the repository.
If the Informatica Server is not registered in the repository, use the Workflow Manager to
register it.
3. Log on to the Windows machine as a user who can start services.
4. From the Start menu, choose Settings-Control Panel.
5. Double-click the icon for Services.
6. From the scrolling list of services installed on the Windows machine, select Informatica.
7. Click Start.
The Informatica Server might take a moment to start.
St ep 4. St arti ng and St oppi ng the Informati ca Server 149
8. If you would like the Informatica service to run every time the computer starts, choose
Automatic as the Startup Type. Be sure that access to all necessary database services and
the Repository Server are available at boot time from the host.
9. Click OK to close the Services dialog box.
10. Wait for one minute, then choose Programs-Administrative Tools-Event Viewer from the
Start menu.
11. Select Log-Application.
Look for the PowerMart source:
You should see several events in the Application log for PowerMart. Select the latest
event. It should contain the following:
If not, see Troubleshooting on page 152 for possible solutions. Also see the
Troubleshooting Guide for more information.
Event LM 34003
displays if the
Informatica
Server
successfully
starts.
To stop the Informatica Server:
1. Choose Services in the Control Panel.
2. Select Informatica and click Stop.
Automatically Starting the Informatica Server
The Informatica Server service can be set to start automatically at system boot time.
To automatically start the Informatica Server:
1. From Windows, select Start-Settings-Control Panel.
2. Click the Services icon.
3. Select Informatica service and click Startup.
4. In the Service dialog box, select Startup Type as Automatic.
5. Click OK.
Once the Informatica Server starts it connects to the Repository Server. If the Repository
Server is installed on the same machine, the Informatica Server might start before the
Repository Server and consequently fail to connect to the Repository Server.
If the repository is stored in a database on a local database server and the database server also
runs as a service, the Informatica Server might start before the database server and
consequently fail to connect to the database server.
Workflow Manager
With the Workflow Manager, you can stop the Informatica Server. However, you must first
configure the Workflow Manager to communicate with the Informatica Server.
You can shut down the Informatica Server in the complete, stop, or abort mode. In the
complete mode, the Informatica Server allows currently running workflows to complete
before shutting down the Informatica Server. In the stop mode, the Informatica Server stops
the running workflows. In the abort mode, the Informatica Server aborts the running
workflows.
You must have one of the following privileges to shutdown:
Administer Server
Super User
To shut down the Informatica Server from the Workflow Manager:
1. Launch the Workflow Manager and connect to the repository.
2. In the Navigator window, right-click on the Informatica Server and choose Shutdown
Server-Complete, Shutdown Server-Stop, or Shutdown Server-Abort from the menu.
St ep 4. St arti ng and St oppi ng the Informati ca Server 151
The Workflow Manager executes the command. In the Output window, you should see
the following text:
{server_name} Shutdown Server: Request acknowledged
{server_name} Shutdown Server: Completed
pmcmd Program
The shutdownserver command stops the Informatica Server. You must have one of the
following privileges to use this command:
Administer Server
Super User
workflows.
Use the following syntax to stop the Informatica Server:
pmcmd shutdownserver <-serveraddr|-s>[host:]portno <<-user|-u>
username|<-uservar|-uv> userEnvVar> <<-password|-p> password|<-
passwordvar|-pv> passwordEnvVar> <-complete|-stop|-abort>
For more details on using pmcmd, see Using pmcmd in the Workflow Administration Guide.
Troubleshooting
This section contains information on troubleshooting the Informatica Server on Windows.
I installed and registered the Informatica Server, but I get an internal error when I try to
start the service.
Verify that the Repository Server is running. You must start the Repository Server before you
can start the Informatica Server.
I installed the Informatica Server on a Windows system, but I cannot start the Informatica
Server.
If you cannot start the Informatica Server, or you receive the message Error 1069 (The
service did not start due to a logon failure), use the Windows Event Viewer to check the
Application log. If possible, correct any errors described in the application log. Also, verify the
service start information.
The Service Start Account needs the advanced NT user right Log on as a service on the
Windows system. Follow these steps to verify that the account with proper rights also starts
the Informatica Server.
1. In the Control Panel, double-click the Services icon.
2. In the Services dialog box, double-click Informatica.
The following dialog box appears:
Informatica service.
If the correct account user is displayed, reenter the account user to have NT verify the
rights assigned to this user.
4. Click OK.
If the user has the necessary rights to run the Informatica Server, the dialog box closes.
If the user does not have the correct rights, a message appears asking if you want this user
to have the Log on as a service right. Select OK to assign the Log on as a service right to this
user.
In addition, verify the connectivity settings you specify in the Informatica Server Setup and
the Server dialog box in the Workflow Manager are correct:
1. Make sure you entered the correct information on the Repository tab of the Informatica
Server Setup program. The Informatica Server needs the exact repository name,
Repository Server hostname and port number, and repository username and password to
start.
2. Make sure you registered the Informatica Server in the Workflow Manager.
3. Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Workflow Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
Informatica Technical Support.
I installed the Informatica Server on a Windows 2000 system, but I cannot start the
Informatica Server.
If you cannot start the Informatica Server, or you receive the message Error 1069 (The
service did not start due to a logon failure), use the Windows 2000 Event Viewer to check
the Application log. If possible, correct any errors described in the application log. Also, verify
the service start information.
The Service Start Account needs the Windows 2000 user right Log on as a service on the
Windows 2000 system. Follow these steps to verify that the account has the correct rights to
start the Informatica Server:
2. Double-click the Local Security Policy icon.
3. In the Local Security Settings dialog box, expand Local Policies and select User Rights
Assignment.
4. Find the policy Log on as a service. Double click on the policy to open the Local Security
Policy Setting dialog box.
The dialog box lists the users assigned the right to Log on as a service.
5. If you need to add a user account, click Add.
6. Click OK when finished and close the Local Security Settings dialog box.
Use the following steps to verify that the account with the right to log on as a service also
starts the Informatica service:
3. In the Services dialog box, double-click Informatica.
The Informatica Properties dialog box appears.
4. Open the Log On tab.
Informatica service. You can also click Browse to search for an account name.
If the correct account user is displayed, reenter the account user to have Windows 2000
verify the rights assigned to this user.
6. Click OK.
7. Close the Informatica Properties dialog box and start the Informatica service again.
In addition, verify the connectivity settings you specify in the Informatica Server Setup and
the Server dialog box in the Workflow Manager are correct:
1. Make sure you entered the correct information on the Repository tab of the Informatica
Server Setup program. The Informatica Server needs the exact repository name,
Repository Server hostname and port number, and repository username and password to
start.
2. Make sure you registered the Informatica Server in the Workflow Manager.
3. Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Workflow Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
Informatica Technical Support.
I started the Informatica Server, but it does not connect to the repository.
Verify that the Informatica Server and the system on which you installed the Informatica
Server are configured to connect to the Repository Server. Also verify that the Repository
Server is running.
The Workflow Manager cannot connect to the Informatica Server.
Verify that the Informatica Server is running. Make sure you have the correct connectivity
settings specified in the Server dialog box in the Workflow Manager.
The Informatica Server does not start after rebooting the machine.
In the Services configuration, make sure the Startup Type is set to automatic.
The Services dialog box shows that the Informatica Server started, but it does not seem to
be running.
After you start the Informatica Server, the Services dialog box displays the status as Started.
This does not necessarily indicate the Informatica Server is running. If the Informatica Server
stops because of an error, the status does not change automatically in this dialog box.
To determine if the Informatica Server started, either:
Check the event log in the Event Viewer Application Log.
Look for the process PmServer in the Task Manager.
157
C h a p t e r 9
Informatica UNIX Server
Step 1. Installing the Informatica Server, 160
Step 2. Configuring the Informatica Server on UNIX, 162
Step 4. Starting and Stopping the Informatica Server on UNIX, 175
Installing and Configuring ODBC for UNIX, 177
158 Chapter 9: Install ing and Configuring the Informatica UNIX Server
Before You Begin
Complete the following steps to install and configure the Informatica Server on UNIX:
1. Install the Informatica Server on UNIX.
2. Configure the Informatica Server.
3. Configure the Informatica Server machine to connect to each source and target database.
4. Register the Informatica Server in the Workflow Manager.
product license key to install the Informatica Server and Informatica Client tools.
Please read the release notes for any last minute changes to the Informatica Server installation
and connectivity issues.
Code Pages
DHCP (TCP/IP Connections Only)
When configuring the Informatica Server, avoid using the Dynamic Host Configuration
Protocol (DHCP) for the machine hosting the Informatica Server.
DHCP dynamically assigns a new IP address each time you start a machine on the network. If
you use DHCP on the Informatica Server, each time you start the Informatica Server, you
must reregister the Informatica Server with the Workflow Manager so the client can
communicate with the Informatica Server at its new address.
After you start the Informatica Server, edit the existing Informatica Server connection
information in the Workflow Manager. You may need to resolve the Informatica Server IP
address in the Server Editor dialog box in the Workflow Manager.
Informatica Server Variable Directories
The installation program creates the following directories under the installation directory to
store session files and caches associated with each Informatica Server:
BadFiles
Cache
ExtProc
SessLogs
SrcFiles
Temp
TgtFiles
WorkflowLogs
All workflows configured to run on the registered Informatica Server use these directories by
default. For details, see Registering the Informatica Server on page 183.
Step 1. Installing the Informatica Server
After you create a repository database, install the client tools, install the Repository Server,
and create a repository, you can install the Informatica Server.
You can install multiple Informatica Servers on the same UNIX system. However, you need to
install each Informatica Server in a separate directory and use different ports.
Before you install the Informatica Server, you might want to create a user in the UNIX system
to run the Informatica Server.
For information on installing the Informatica Server on Linux, see Installing and
Configuring PowerCenter and PowerMart in the Supplemental Guide.
To install the Informatica Server on UNIX:
1. Log on to the UNIX machine.
2. Set the library path to the absolute directory path where the Informatica Server is to be
installed for the following operating systems.
Table 9-1 describes the library paths for different UNIX operating systems:
3. On the Informatica installation CD, locate the directory specific to the product.
For example, if you are installing the PowerCenter Server on a Solaris system, switch to
the unixserv/pc/solaris directory.
4. Run install.
Using a Bourne shell, type ./install.
Using a C-shell, type sh install.
5. Select the language in which you want to run the installation:
English
Japanese
If you are running one or more server processes, a message displays warning you that the
install or upgrade may cause problems.
6. Enter the Informatica product license key.
7. Select PowerCenter Server from the list of components available to install.
Table 9-1. Library Path for Informatica Server on UNIX
Operating System Library Path
AIX LIBPATH
HP SHLIB_PATH
Step 1. I nstal li ng t he Informati ca Server 161
8. Enter the absolute target directory path where you want to install the Informatica Server.
9. The installation program now extracts and installs the files. The upgrade preserves your
configuration settings.
10. Type Y if you want to view the readme file, or N if you wish to read it later.
11. When the installation completes, type Y to configure the Informatica Server, or N to
configure it later.
12. Exit from the Informatica Platform Installation.
See the next section for details. You need to configure the Informatica Server before you
can start it.
Step 2. Configuring the Informatica Server on UNIX
After you install the Informatica Server on UNIX, you need to configure it with the pmconfig
utility. This utility writes your configuration parameters to the file pmserver.cfg. You
configure the connectivity information for the repository in pmconfig.
By default, this file is stored in the same directory where the Informatica Server is installed. If
you rename pmserver.cfg or move it to another directory, you must include the name and
path when you open the configuration file in pmconfig.
You need to include an entry for all required parameters before you can start the Informatica
Server.
You can make changes to the Informatica Server configuration parameters. These changes
take effect when you stop and restart the Informatica Server.
Before you can start the Informatica Server you need to register the Informatica Server in the
repository. For more information, see Registering the Informatica Server on page 183.
Note: ODBC databases, such as Microsoft Access97 and Excel, are not compatible with the
Informatica Server installed on a UNIX system.
For information on additional Informatica Server configuration parameters, see Installing
To configure the UNIX Informatica Server:
1. Run the pmconfig utility and open pmserver.cfg.
Note: On Solaris, run ./pmconfig to avoid running the Solaris system command by the
same name. The PM_HOME environment variable must point to the PowerMart
directory.
2. Enter the settings needed to configure the Informatica Server.
For information about entering the license key for Teradata, see the Supplemental Guide.
Table 9-2 describes the setting required to configure the Informatica Server on UNIX:
Table 9-2. Configuration Parameters for Informatica Server on UNIX
Option
Required/
Optional
Description
ServerName Required The name of the Informatica Server registered with the
repository.
RepositoryName Required The exact repository name, the repository name entered
when creating or upgrading a repository.
PMUser Required The repository username specific to the Informatica
Client and Informatica Server tools to connect to the
repository.
Step 2. Confi guring the Informat ica Server on UNI X 163
PMPassword Required The password corresponding to the repository user
(PMUser). Must be in US-ASCII only.
RepServerHostName Required The host name of the machine hosting the Repository
Server.
RepServerPortNumber Required The port number the Repository Server uses to
communicate with repository client applications.
LogFileName Optional The filename of the Informatica Server log file. Default is
pmserver.log.
DataMovementMode Required Choose between ASCII and Unicode. The default data
movement mode is ASCII, which passes US-ASCII
character data. To pass 8-bit ASCII and multibyte
character data from sources to targets, use Unicode
mode.
ValidateDataCodePages Required If you configure this option to Yes, the Informatica Server
enforces data code page compatibility. If you configure
this option to No, the Informatica Server lifts restrictions
for source and target data code page selection, stored
procedure and lookup database code page selection, and
session sort order selection. The Informatica Server
performs data code page validation in Unicode data
movement mode only. By default, this option is set to Yes.
SessionLogInUTF8 Required If you configure this option to Yes, the Informatica Server
writes to the session log using the UTF-8 character set. If
you set this option to No, the Informatica Server writes to
the session log using the Informatica Server code page.
The Informatica Server writes the session log in UTF-8
when it runs in Unicode data movement mode only. By
default, this option is set to No.
MaxSessions Required The maximum number of sessions stored in shared
memory. This sets the maximum number of sessions that
the Informatica Server can run in parallel. Default is 10.
LMSharedMem Required The amount of shared memory available for use by the
Informatica Server Load Manager process. For every 10
sessions in MaxSessions, you need at least 2,000,000
bytes reserved in LMSharedMem. Default is 2,000,000
bytes.
PMCacheDir Optional The default directory for caches and cache files. Use for
backward compatibility for mappings created in
PowerMart 3.5. For mappings created in later versions of
PowerCenter and PowerMart, use the server variable
$PMCacheDir. Configure $PMCacheDir when you
configure the Informatica Server in the Workflow
Manager.
Option
Required/
Optional
Description
PlatformKey Required The UNIX platform key. Required when you install the
Informatica Server on a UNIX system.
OracleKey Optional The Oracle platform key. Required if the Informatica
Server accesses Oracle databases.
SybaseKey Optional The Sybase platform key. Required if the Informatica
Server accesses Sybase databases.
InformixKey Optional The Informix platform key. Required if the Informatica
Server accesses Informix databases.
DB2Key Optional The DB2 platform key. Required if the Informatica Server
accesses DB2 databases.
ODBCKey Optional The ODBC platform key. Required if the Informatica
Server accesses any of the supported databases (such
as Informix or Sybase) through ODBC drivers.
TimeStampWorkflowLogMessages Optional Set this option to Yes if you want to append a time stamp
to messages written to the workflow log. This option is set
to No by default.
FailSessionIfMaxSessionsReached Optional Set to Yes to have the Informatica Server fail the session
if the number of sessions already running is equal to the
value configured for MaxSessions. If you set this option
to No, the Informatica Server places the session in a
ready queue until a session slot becomes available. This
option is set to No by default.
ExportSessionLogLibName Optional If you want the Informatica Server to write session log
messages to an external library, enter the name of the
library file.
ErrorSeverityLevel Optional The level of error messages written to the Informatica
Server log. Specify one of the following:
- Warning. Writes WARNING and ERROR code
- Tracing. Writes TRACE, INFO, WARNING, and ERROR
Option
Required/
Optional
Description
Step 2. Confi guring the Informat ica Server on UNI X 165
DateHandling40Compatibility Optional Set to Yes if you want the Informatica Server to handle
dates as in PowerCenter 1.0/PowerMart 4.0. Set to No if
you want the Informatica Server to handle dates as
defined in PowerCenter 6.0/PowerMart 6.0.
Date handling significantly improved in PowerCenter 1.5
and PowerMart 4.5. If you need to revert to PowerCenter
1.0 or PowerMart 4.0 behavior, you can configure the
Informatica Server to handle dates as in PowerCenter 1.0
and PowerMart 4.0.
This option is set to No by default.
PMServer3XCompatibility Optional Set to 1 to have the Informatica Server handle
Aggregator transformations as it did in PowerMart 3.5.
This overrides both Aggregate treat nulls as zero and
Aggregate treat rows as insert.
If you set this option to 1, the Informatica Server treats
nulls as zeros in aggregate calculations and performs
aggregate calculations before flagging records for insert,
update, delete, or reject in Update Strategy expressions.
Set to 0 to have the Informatica Server treat nulls as nulls
and performs aggregate calculations based on the
Update Strategy transformation.
This option is set to 0 by default.
AggregateTreatNullAsZero Optional Set to 1 to have the Informatica Server treat nulls as zero
in Aggregator transformations. Set to 0 to have the
Informatica Server treat nulls as nulls in aggregate
calculations.
AggregateTreatRowAsInsert Optional Set to 1 to have the Informatica Server perform
aggregate calculations before flagging records for insert,
update, delete, or reject in Update Strategy expressions.
Set to 0 to have the Informatica Server perform
aggregate calculations based on the Update Strategy
transformation. See Update Strategy Transformation in
the Transformation Guide.
DateDisplayFormat Required If specified, the Informatica Server validates the date
display format and uses it in session log and server log
entries. If the date display format is invalid, the
Informatica Server uses the default date display format.
The default date display format is DY MON DD HH
24:MI:SS YYYY.
LoadManagerAllowDebugging Optional If set to Yes, you can run the Debugger.
This option is set to Yes by default.
CreateIndicatorFiles Optional If set to Yes, the Informatica Server creates indicator files
when you run a workflow with a flat file target.
Option
Required/
Optional
Description
3. Save your changes and close the file.
XMLWarnDupRows Optional If set to Yes, the Informatica Server writes duplicate row
warnings and duplicate rows for XML targets to the
session log.
By default, this option is set to Yes.
MaxLookupSPDBConnections Optional Allows you to specify a maximum number of connections
to a lookup or stored procedure database when you start
a session. If the number of connections needed exceeds
this value, session threads must share connections. This
can result in a performance loss. If you do not specify a
value, the Informatica Server allows an unlimited number
of connections to the lookup or stored procedure
database.
If the Informatica Server allows an unlimited number of
connections, but the database user does not have
permission for the number of connections required by the
session, the session fails.
MaxSybaseConnections Optional Allows you to specify a maximum number of connections
to a Sybase database when you start a session. If the
number of connections required by the session is greater
than this value, the session fails.
This value is set to 100 by default.
MaxMSSQLConnections Optional Allows you to specify a maximum number of connections
to a Microsoft SQL Server database when you start a
session. If the number of connections required by the
session is greater than this value, the session fails.
SybaseIQLocalToPmServer Optional Set this option to Yes if your Sybase IQ server is local to
the Informatica Server. When you enable this option, the
Informatica Server loads target data to Sybase IQ directly
from the named pipe, rather than writing data to a flat file
and loading the file contents to the Sybase IQ server.
Enabling this option can increase session performance,
since no disk activity is required.
NumOfDeadlockRetries Optional Allows you to specify the number of times the Informatica
Server retries a target write on a database deadlock.
DeadlockSleep Optional Allows you to specify the number of seconds before the
Informatica Server retries a target write on database
deadlock. If you set this value to zero seconds, the
Informatica server retries the target write immediately.
This value is set to 0 seconds by default.
Option
Required/
Optional
Description
To communicate with databases, the Informatica Server uses either native database
connectivity software or ODBC.
Informatica recommends using native database drivers to connect to the source and target
databases. To connect through native drivers, you must install and configure native database
client connectivity software on the machine hosting the Informatica Server. In order to ensure
compatibility between the Informatica Server and your source and target databases, use 32-bit
database client libraries only.
You need to configure the Informatica Server to communicate with each source and target
database. This section outlines specific steps for each database. However, the following steps
provide a brief overview of the tasks you need to complete to configure the Informatica
Server:
1. Install the native drivers on the machine hosting Informatica Server.
2. Set the database environment variable to the database installation directory.
3. Set the PATH variable to include the directory where PowerCenter or PowerMart is
installed.
Follow these guidelines when you use a UNIX shell:
For example, if you have an Oracle source and Informix target and the Informatica Server
is installed on Solaris, you could set the shared library variables as follows:
Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmserver_dir:$ORACLE_HOME/
lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql; export LD_LIBRARY_PATH
Table 9-3. Library Path for Informatica Server on UNIX
Operating System
Shared Library
Environment Variable
AIX LIBPATH
HP SHLIB_PATH
Shell To Modify Environment Variable
C-shell setenv PATH ${PATH}:/usr/mypath
Bourne Shell PATH=${PATH}:/usr/mypath; export PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
pmserver_dir:$ORACLE_HOME/lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql
5. Verify the system path includes the database installation directory.
6. Test connectivity through the native tool, such as ISQL.
For information on supported datatypes for each database see Datatype Reference in the
Designer Guide.
You need to connect each Informatica Server to each Oracle source and target database. You
must install the same version of the Oracle Client on each machine hosting the Oracle
To connect to an Oracle database through Oracle Net Services or Net8:
Install the same version of Oracle Net Services or Net8 on the machine hosting the
Oracle database and Informatica Server. If you have different versions installed, you may
experience difficulties reading from and writing to the database.
2. Set the ORACLE_HOME environment variable to the Oracle installation directory. For
example:
$ ORACLE_HOME=/HOME2/ORACLE; export ORACLE_HOME
Using a C-shell:
$ setenv ORACLE_HOME=/HOME2/ORACLE
The shared library path must include the database library path as well as the
PowerCenter/PowerMart library path.
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Informatica Server
installation directory. If you installed the Informatica Server in the $HOME/pmserver
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmserver_dir:$ORACLE_HOME/lib;
export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/pmserver_dir
:$ORACLE_HOME/lib
4. Set the TNS_ADMIN environment variable to the path for TNSNAMES. For example:
$ TNS_ADMIN=/HOME2/NETWORK/ADMIN; export TNS_ADMIN
Using a C-shell:
$ setenv TNS_ADMIN=/HOME2/NETWORK/ADMIN
Note: This step is optional, and might vary depending on your configuration.
5. Ensure that the system path includes an entry for Oracle.
$ PATH ${PATH}:$ORACLE_HOME/BIN; export PATH
Using a C-shell:
$ setenv $PATH ${PATH}:ORACLE_HOME/BIN
6. Configure the Oracle client. Use the SQL*Net Easy Configuration Utility or copy an
existing TNSNAMES.ORA file and modify it as needed.
TNSNAMES.ORA is stored in the <oracle_home>/NETWORK/ADMIN directory.
Enter the correct syntax for the Oracle connect string, that is databasename.world.
Here is a sample TNSNAMES.ORA. You need to enter the information for your
database.
mydatabase.world =
(DESCRIPTION
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
7. Launch SQL*Plus and try to connect to the database. If you fail to connect to the
Use the correct connect string (as defined in TNSNAMES.ORA) and username.
8. Configure the Informatica Server. Include the Oracle database key in the Informatica
Server configuration utility (pmconfig).
For details on configuring the Informatica Server, see Step 2. Configuring the
Informatica Server on UNIX on page 162.
Install the same version of the Open Client client on the machines hosting the database
and the Informatica Server. You may encounter problems reading from and writing to the
database if you use different versions of Open Client.
For example, if you install Open Client on a UNIX system, you might use the following
entry:
$ PATH=${PATH}:/usr/sybase/bin; export PATH
Using a C-shell:
$ setenv PATH ${PATH}:/usr/sybase/bin
For example, on Solaris, set the LD_LIBRARY_PATH variable to the Informatica Server
installation directory. For example, if you installed the Informatica Server in the
$HOME/pmserver directory, you could type:
$ LD_LIBRARY_PATH=$HOME/pmserver_dir:$SYBASE/lib; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmserver_dir:$SYBASE/lib
Note: $SYBASE is the directory where Sybase is installed.
4. Verify the Sybase server name in the Sybase interfaces file (stored in the $SYBASE/
interfaces).
5. Launch ISQL, enter the connectivity information, and connect to the database.
If you fail to connect to the database, verify that you correctly entered all of the
6. Configure the Informatica Server. Include the Sybase database key in the Informatica
Server configuration (pmconfig).
1. Install the ESQL/C client software.
Install compatible versions of ESQL/C on the machines hosting the Informatica Server
and Informix databases.
2. Set the environment variables:
INFORMIXDIR (where Informix is installed, for example /databases/informix)
INFORMIXSERVER (the name of the Informix server, for example, INFSERVER)
3. Make sure INFORMIXSERVER matches one of the servers defined in
$INFORMIXDIR/etc/sqlhosts file.
4. Make sure the Service (last column entry for the server named in the sqlhosts file) is
defined in the services file (usually /etc/services). If not, define the Informix Services
name in the Services file.
Enter the Services name and port number. The default port number is 1525, which
should work in most cases.
See your Informix and UNIX documentation for details.
5. Verify that the system path includes the $INFORMIXDIR/bin directory.
$ PATH=${PATH}=$INFORMIXDIR/bin; export PATH
Using a C-shell:
$ setenv PATH ${PATH}:$INFORMIXDIR/bin
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Informatica Server
installation directory. If you installed the Informatica Server in the $HOME/pmserver
$ LD_LIBRARY_PATH=$HOME/pmserver_dir:$INFORMIXDIR/lib:$INFORMIXDIR/lib/
esql; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmserver_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql
7. Optional. Set the $ONCONFIG environment variable to the Informix configuration file
name.
8. If you plan to call Informix stored procedures in mappings, set all of the date parameters
to the Informix datatype Datetime year to fraction(5).
9. On UNIX platforms only, make sure the DBDATE environment variable is not set.
For example, to check if DBDATE is set, you might type the following at a UNIX
prompt:
$ env | grep -i DBDATE
If DBDATE=MDY2/ appears, unset DBDATE by typing:
$ unsetenv DBDATE
10. Launch dbaccess, enter the necessary information, and connect to the Informix database.
11. Configure the Informatica Server. Include the Informix database key in the Informatica
Server configuration utility (pmconfig).
If a DB2 database server is running, or the DB2 Connect option is installed, database
connections may already be available. If not, complete the following steps. These
examples use the C-shell and assume you are logged in as the user where you intend to
run the Informatica Server (pmserver).
2. Install or verify that the UNIX IBM DB2 software, including the Client Application
Enabler (CAE), is installed at different locations, depending on the operating system
platform. The DB2DIR environment variable should always be set to point at this base
installation directory. The IBM DB2 Version 6.1 defaults are as follows:
For Solaris:
For HP-UX:
For AIX:
$ setenv DB2DIR /usr/lpp/db2_06_01
3. The UNIX IBM DB2 software always has an associated user login, often db2admin,
which serves as a holder for database configurations. This user holds the instance for
DB2. Set the following environment variables to enable access to the instance:
$ setenv DB2INSTANCE db2admin [The name of the instance holder]
$ setenv INSTHOME ~db2admin [db2admin's home directory path]
4. The UNIX IBM DB2 software comprises a number of shared library components that are
loaded dynamically by the Informatica Server. To locate the shared libraries at run-time,
the shared library environment variable requires alteration, depending on operating
system platform:
$ setenv LD_LIBRARY_PATH $DB2DIR/lib:${LD_LIBRARY_PATH}
5. To run IBM DB2 command line programs, the PATH environment variable should be
edited as follows:
$ setenv PATH $DB2DIR/bin:${PATH}
system platform. Either log out and in again, or issue the command:
$ source .cshrc
7. If you are configuring a new DB2 installation, you need to set up a remote database. Run
the DB2 Command Line Processor (db2) and issue the CATALOG <protocol> NODE
and CATALOG DATABASE commands to set up a remote database.
Consult the DB2 installation guide for details.
8. Verify the name of your remote database. Run the DB2 Command Line Processor (db2)
and issue the LIST DATABASE DIRECTORY command for a list of available databases.
It is recommended that database entries for use with Informatica Server exactly match
those in the client tools.
9. Verify you can connect to the DB2 database. Run the DB2 Command Line Processor
('db2') and issue the command:
CONNECT TO <databasename> USER <username> USING <password>
If connection is successful, disconnect and cleanup with the TERMINATE command.
10. In the Informatica Server configuration process, using the pmconfig utility, you must
provide an Informatica license key for DB2. Sessions requiring DB2 access do not run
without this key.
Step 4. Starti ng and Stopping the Informat ica Server on UNIX 175
Step 4. Starting and Stopping the Informatica Server on
UNIX
The procedure for starting and stopping the Informatica Server is the same for all UNIX
platforms. You start the Informatica Server from the UNIX command line and stop it from
the Workflow Manager. You can also use the pmcmd program to stop the Informatica Server.
Note: Before starting the Informatica Server, use the Workflow Manager to register the
Informatica Server in the repository.
When you start a PowerMart Server, it verifies that it is the only Informatica Server registered
in the repository. It does not start if there are other Informatica Servers registered in the
repository.
When you send a request to stop the Informatica Server, the Informatica Server first removes
all workflows scheduled to run in the future. It then attempts to stop all running workflows.
If any workflow fails to respond within a certain period of time, the Informatica Server aborts
it. Allow 1 to 2 minutes for the Informatica Server to complete all processes. When you
restart the Informatica Server, you must reschedule all workflows.
UNIX Command Line
Follow these instructions to start the Informatica Server from the UNIX command.
To start the Informatica Server:
1. Verify that the repository database and Repository Server are running.
2. Connect to the UNIX machine on which the Informatica Server is running.
Log on as a user who has rights to start the Informatica Server.
3. Type the following command:
pmserver [pmserver.cfg]
The Informatica Server displays a message indicating that it has started.
To verify that the Informatica Server started, check the Informatica Server event log file.
The following event displays if the Informatica Server successfully starts:
SF_34003 Server initialization completed.
Workflow Manager
With the Workflow Manager, you can stop the Informatica Server. However, you must first
configure the Workflow Manager to communicate with the Informatica Server.
workflows.
You must have the following privileges to shutdown:
Super User
Administer Server
To stop the Informatica Server from the Workflow Manager:
1. Launch the Workflow Manager and connect to the repository.
2. In the Navigator window, right-click on the Informatica Server and choose Shutdown
Server-Complete, Shutdown Server-Stop, or Shutdown Server-Abort from the menu.
The Workflow Manager executes the command. In the Output window, you should see
the following text:
{server_name} Shutdown Server: Request acknowledged
{server_name} Shutdown Server: Completed
pmcmd Program
The shutdownserver command stops the Informatica Server. You must have one of the
following privileges to use this command:
Administer Server
Super User
workflows.
Use the following syntax to stop the Informatica Server:
pmcmd shutdownserver <-serveraddr|-s>[host:]portno <<-user|-u>
username|<-uservar|-uv> userEnvVar> <<-password|-p> password|<-
passwordvar|-pv> passwordEnvVar> <-complete|-stop|-abort>
For more details on using pmcmd, see Using pmcmd in the Workflow Administration Guide.
Instal l ing and Conf iguri ng ODBC for UNIX 177
Installing and Configuring ODBC for UNIX
For information on installing and configuring ODBC for UNIX and Linux see, Installing
The Informatica installation CD provides a Merant 3.7 UNIX ODBC closed driver to
connect to ODBC data sources.
PowerCenter and PowerMart provide native drivers to connect to Informix, Sybase, Oracle,
and DB2 databases. If, however, you want to connect to another database, you can use the
Merant UNIX ODBC driver.
To install ODBC drivers for UNIX servers:
1. Insert the Informatica installation CD into the CD-ROM drive. On the Solaris platform,
this causes auto-mounting on the /cdrom path. On other platforms, use the appropriate
System Administration commands to mount the CD onto directory path
/cdrom (or similar).
Verify that you can locate ODBC for UNIX files on the CD. These are files named
unixodbc.tar in the following directories:
/cdrom/odbc/aix
/hpux
/solaris
2. Log on with root privileges.
3. Create the directory in which you want to install the drivers. On UNIX, ODBC driver
packages are installed under a directory path similar to /opt/odbc (or usr/lpp/odbc on
AIX). Change the path to this directory.
4. Extract the contents of the ODBC for UNIX installation file into the directory. You must
extract from the file specific to you operating system platform (that is, from the
appropriate subdirectory on the CD). For example, on Solaris you should use a
command:
tar xvf /cdrom/unixodbc/solaris/unixodbc.tar
5. Run the extracted installation script. This extracts all of the necessary driver files and
directories. To do this, issue a command:
ksh unixpi.ksh
6. To conserve space in the ODBC package directory, delete the unixodbc.tar file and the
.tar file that corresponds to your platform (solaris.tar, aix36.tar, or hp.tar).
7. Exit from root privileges.
8. Log on as the user where you run Informatica PowerCenter/PowerMart Server. Copy the
sample ODBC sources initialization file from the ODBC installation. For example:
cp /opt/odbc/odbc.ini ~/.odbc.ini
Copy and/or modify entries in .odbc.ini to create data sources based on the installed
ODBC drivers.
9. You might want to retrieve a copy of the appropriate shared-library path helper. For
example:
cp /opt/odbc/odbc.csh ~/.odbc.csh
Configure the user .cshrc file to invoke this script at logon. The purpose is to modify the
appropriate OS-specific shared library path environment variable so that ODBC drivers
can be accessed. The path to these drivers (for example: /opt/odbc/lib) is added to:
LD_LIBRARY_PATH (on Solaris)
SHLIB_PATH (on HP-UX)
LIBPATH (on AIX)
Note: These changes are not visible to Informatica Server until the Informatica Server is
stopped and re-started with the changed environment variables in effect.
You are now ready to use ODBC sources.
Connecting to ODBC Data Sources
To connect to each ODBC data source (source or target), follow these steps to configure the
Informatica Server on UNIX.
To connect to an ODBC data source:
1. Install the Merant ODBC for UNIX package (Solaris, HP-UX, or AIX) provided on the
2. Configure your environment as follows (examples use C-shell and assume you are logged
in as the user where you intend to run the Informatica Server):
The Merant ODBC for UNIX software is installed at different locations, depending on
your operating system platform. The ODBCHOME environment variable should always
be set to point at this base installation directory. The defaults are as follows:
For Solaris:
$ setenv ODBCHOME /opt/odbc
For HP-UX:
$ setenv ODBCHOME /opt/odbc
For AIX:
$ setenv ODBCHOME /usr/lpp/odbc
3. The Merant ODBC for UNIX software comprises a number of shared library
components that are loaded dynamically by the Informatica Server. To locate the shared
libraries at run-time, the shared library variable needs to be set:
$ setenv LD_LIBRARY_PATH $ODBCHOME/lib:${LD_LIBRARY_PATH}
4. To run the ivtestlib utility, the PATH environment variable should be altered as follows:
$ setenv PATH ${ODBCHOME}/bin:${PATH}
system platform. Either logout and in again, or issue the command:
$ source .cshrc
6. If you have already configured one or more ODBC data sources, you may have a file
named .odbc.ini in the current user's home directory ($HOME). If not, make a copy of
the file found in the ODBC for UNIX installation directory at $ODBCHOME/odbc.ini.
Use a command like:
$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
The ODBC.ini file looks similar to the following:
[ODBC Data Sources]
dBase=Merant 3.7 dBase Driver
Sybase11=Merant 3.7 Sybase 11 Driver
Oracle8=Merant 3.7 Oracle 8 Driver
Informix9=Merant 3.7 Informix 9 Driver
OpenIngres=Merant 3.7 OpenIngres 1.2 Driver
OpenIngres20=Merant 3.7 OpenIngres 2.0 Driver
DB2=Merant 3.7 DB2 Driver
Text=Merant 3.7 Text Driver
[dBase]
Driver=/usr/lpp/odbc/lib/DWdbf13.so
Description=dBase
Database=/usr/lpp/odbc/demo
[Sybase11]
Driver=/usr/lpp/odbc/lib/DWsyb1113.so
Description=Sybase11
Database=odbc
ServerName=SYBASE
WorkstationID=id
LogonID=odbc01
Password=odbc01
OptimizePrepare=2
SelectMethod=1
[Oracle8]
Driver=/usr/lpp/odbc/lib/DWor813.so
Description=Oracle8
ServerName=oraclehost
LogonID=odbc01
Password=odbc01
[Informix9]
Driver=/usr/lpp/odbc/lib/DWinf913.so
Description=Informix9
Database=odbc
HostName=informixhost
LogonID=odbc01
Password=odbc01
[DB2]
Driver=/usr/lpp/odbc/lib/DWdb213.so
Description=DB2
Database=ODBC
[OpenIngres]
Driver=/usr/lpp/odbc/lib/DWoing13.so
Description=OpenIngres1
ServerName=ingreshost
Database=odbc
LogonID=odbc01
Password=odbc01
Workarounds=1
[OpenIngres20]
Driver=/usr/lpp/odbc/lib/DWoi213.so
Description=OpenIngres2.0
ServerName=ingreshost
Database=odbc
LogonID=odbc01
Password=odbc01
Workarounds=1
[Text]
Driver=/usr/lpp/odbc/lib/DWtxt13.so
Description=Text driver
Database=/usr/lpp/odbc/demo
[ODBC]
Trace=0
TraceFile=odbctrace.out
TraceDll=/usr/lpp/odbc/lib/odbctrac.so
InstallDir=/usr/lpp/odbc
7. In the [ODBC Data Sources] section, add entries for any new data sources to be defined.
The unaltered .odbc.ini from $ODBCHOME contains default entries for all available
drivers.
8. Add an extra line under [ODBC Data Sources]. For example:
MY_ORACLE_ODBC_SOURCE=Driver or Data Source Description Text
9. Add a complete entry for the data source. For example:
[MY_ORACLE_ODBC_SOURCE]
Driver=/opt/odbc/lib/DWor813.so
Description=Merant 3.7 Oracle 8 Driver
ServerName=My Oracle Host
LogonID=My User
Password=My Password
10. For details on parameters in Data Source entries, see the example entries listed in the
unaltered .odbc.ini from $ODBCHOME. For more information, consult the Merant
ODBC for UNIX documentation.
11. For each data source you use, make a note of the file named under the Driver= parameter
in the Data Source entry in.odbc.ini. Use the ivtestlib utility to verify that each driver file
can be loaded by the Merant ODBC for UNIX manager. For example, if you have an
entry Driver=/opt/odbc/lib/DWxxxx.so, issue the following command:
ivtestlib /opt/odbc/lib/DWxxxx.so
12. Install and configure any underlying client access software needed by the ODBC driver.
Note: While some ODBC drivers are self-contained and have all information inside the
.odbc.ini file, most are not. An ODBC driver that, for example, accesses Oracle would
also need the Oracle SQL*NET software installed and appropriate environment variables
set. Such additional software configuration must be verified separately before using
ODBC.
13. When you configure the Informatica Server, using the pmconfig utility, you must provide
an Informatica license key for ODBC. Sessions requiring ODBC access do not run
without this key.
183
C h a p t e r 1 0
Registering the
Informatica Server
Overview, 184
Registering the Informatica Server, 185
184 Chapter 10: Registering the Informati ca Server
Overview
After you install and configure the Informatica Client and the Informatica Server, you can
register the Informatica Server with the repository that you indicated in the Informatica
Server Configuration. You must register the Informatica Server before you can start it.
Register Informatica Servers in the Workflow Manager. The Workflow Manager is the
Informatica Client tool that you use to create and run workflows that extract, transform, and
load data.
You can register and run multiple PowerCenter Servers against a local or global repository.
You can register and run only one PowerMart Server in a local repository. You cannot register
a PowerMart Server in a global repository. When you start a PowerMart Server, it verifies that
it is the only Informatica Server registered in the repository. It does not start if there are other
Informatica Servers registered in the repository. For details on local and global repositories,
see Managing the Repository in the Repository Guide.
You can perform the following registration tasks for an Informatica Server:
Register an Informatica Server. When you register an Informatica Server, you specify
information such as the code page and directories for workflow and session output. This
information is stored in the repository.
Register multiple Informatica Servers. When you register multiple Informatica Servers,
choose the Informatica Server for a workflow in the workflow properties.
Edit an Informatica Server. When you edit an Informatica Server, all workflows using that
Informatica Server use the updated server connection information, including the updated
code page settings. You do not need to restart the Workflow Manager to use the updated
information.
Delete an Informatica Server. When you delete an Informatica Server, assign another
Informatica Server for the workflows using the deleted server. To assign an Informatica
Server to a workflow, choose Connections-Assign Server in the Workflow Manager.
To register an Informatica Server, you must have one of the following privileges:
Administer Server
Super User
You can also configure the following information in the Workflow Manager to run workflows:
Create database connections for source, target, lookup transformations, and stored
procedures. For details on database connections, see Configuring the Workflow Manager
in the Workflow Administration Guide.
Define the FTP connections if you plan to use FTP to access source or target machines.
For details on FTP connections, see Using FTP in the Workflow Administration Guide.
Configure External Loader connections if you plan to use an external loader to load the
target database. For details on External Loader connections, see External Loading in the
Workflow Administration Guide.
Regi st eri ng the Informat ica Server 185
Registering the Informatica Server
Before you use the Workflow Manager to communicate with the Informatica Server, you need
to register it in the repository. You need the following information to register the Informatica
Server:
A unique Informatica Server name.
TCP/IP address used to access the Informatica Server.
Use the IP address and hostname of the machine on which the Informatica Server runs,
and the port number the Informatica Server uses on that machine.
Code page identifying the character set associated with the Informatica Server.
Directories and parameters you want the Informatica Server to use for workflow files and
caches.
When you register an Informatica Server, you must select a code page. This code page must be
identical to the code page of the operating system on which the Informatica Server resides and
it must be compatible with the repository code page.
When you create or upgrade a repository, you must select a code page for the repository.
When you register an Informatica Server, the Workflow Manager displays valid code pages
based on the repository code page.
The Workflow Manager allows you to change the Informatica Server code page to a
compatible code page. This ensures workflows associated with the Informatica Server remain
valid.
For example, the Informatica Server operating system code page is Shift-JIS. The repository
code page is JapanEUC. These code pages are compatible. Because the Informatica Server
code page is Shift-JIS, you enter Shift-JIS when you register the Informatica Server in the
Workflow Manager. After creating sessions, you change the Informatica Server code page to
JapanEUC and then update the Informatica Server information in the Workflow Manager.
Because these code pages are compatible, all sessions remain valid.
Server Variables
You can define server variables for each Informatica Server you register. Server variables define
the path and directories for session and workflow output files and caches. You can also use
server variables to define workflow properties, such as the number of workflow logs to
archive.
The installation process creates default directories in the location where you install the
Informatica Server. By default, the Informatica Server writes output files in these directories
when you run a workflow. To use these directories as the default location for the session and
workflow output files, you must configure the server variable $PMRootDir to define the path
to the directories.
Sessions and workflows are configured to use server directories by default. You can override
the default by entering different directories session or workflow properties.
For example, you might have an Informatica Server running all workflows in a repository. If
you define the server variable for workflow logs directory as c:\pmserver\workflowlog, the
Informatica Server saves the workflow log for each workflow in c:\pmserver\workflowlog by
default.
If you change the default server directories, make sure the designated directories exist before
running a workflow. If the Informatica Server cannot resolve a directory during the workflow,
it cannot run the workflow.
By using server variables instead of hard-coding directories and parameters, you simplify the
process of changing the Informatica Server that runs a workflow. If each workflow in a
development folder uses server variables, then when you copy the folder to a production
repository, the production server can run the workflow as configured. When the production
server runs the workflow, it uses the directories configured for its server variables. If, instead,
you changed workflow to use hard-coded directories, workflows fail if those directories do not
exist on the production server.
Table 7-1 lists the server variables you configure when you register an Informatica Server:
Table 7-1. Server Variables
Server Variable
Required/
Optional
Description
$PMRootDir Required A root directory to be used by any or all other server variables.
Informatica recommends you use the Server installation directory
as the root directory.
$PMSessionLogDir Required Default directory for session logs. Defaults to $PMRootDir/
SessLogs.
$PMBadFileDir Required Default directory for reject files. Defaults to $PMRootDir/BadFiles.
$PMCacheDir Required Default directory for the lookup cache, index and data caches, and
index and data files. To avoid performance problems, always use a
drive local to the Informatica Server for the cache directory. Do not
use a mapped or mounted drive for cache files. Defaults to
$PMRootDir/Cache.
$PMTargetFileDir Required Default directory for target files. Defaults to $PMRootDir/TgtFiles.
$PMSourceFileDir Required Default directory for source files. Defaults to $PMRootDir/SrcFiles.
$PMExtProcDir Required Default directory for external procedures. Defaults to $PMRootDir/
ExtProc.
$PMTempDir Required Default directory for temporary files. Defaults to $PMRootDir/Temp.
$PMSuccessEmailUser Optional Email address to receive post-session email when the session
completes successfully. Use to address post-session email.
Entering a Root Directory
When you register an Informatica Server, you must define the $PMRootDir server variable.
This is the root directory for other server directories.
The syntax for $PMRootDir is different for Windows and UNIX:
Windows. Enter a path beginning with a drive letter, colon, backslash, as follows:
C:\InformaticaServer\bin
UNIX. Enter an absolute path beginning with a slash, as follows:
/InformaticaServer/bin
For example, if you define $PMRootDir on Windows to be c:\InformaticaServer\bin, the
variable $PMSessionLogDir becomes c:\InformaticaServer\bin\SessLogs by default.
The Informatica Server installation directory is the recommended root directory. If you enter
a different root directory, make sure all directories specified for server variables exist before
running a workflow.
Entering Other Directories
By default, the Workflow Manager uses $PMRootDir as the basis for other server directories.
However, you can enter directories unrelated to the root directory. For example, if you want
to place caches and cache files in a different drive local to the Informatica Server, you can
change the default directory, $PMRootDir/Cache to:
D:\Cache
Note: If you enter a delimiter inappropriate to the Informatica Server platform (for example,
using a backslash for a UNIX server), the Workflow Manager corrects the delimiter.
$PMFailureEmailUser Optional Email address to receive post-session email when the session
fails. Use to address post-session email. The default value is an
empty string. For details, see Sending Emails in the Workflow
$PMSessionLogCount Optional Number of session logs the Informatica Server archives for the
session. Defaults to 0. Use to archive session logs. For details, see
Session Log File in the Workflow Administration Guide.
$PMSessionErrorThreshold Optional Number of errors the Informatica Server allows before failing the
session. Use to configure the Stop On option in the session
properties. Defaults to 0. The Informatica Server fails the session
on the first error if $PMSessionErrorThreshold is 0.
$PMWorkflowLogDir Required Default directory for workflow logs.
Defaults to $PMRootDir/WorkflowLogs.
$PMWorkflowLogCount Optional Number of workflow logs the Informatica Server archives for the
workflow. Use to archive workflow logs. Defaults to 0.
Table 7-1. Server Variables
Server Variable
Required/
Optional
Description
Changing Servers
If you change Informatica Servers, the new Informatica Server can run workflows using its
server variables. To ensure a workflow successfully completes, relocate any necessary file
sources, targets, or incremental aggregation files to the default directories of the new
Informatica Server.
If you do not use server variables in an individual session or workflow, you may need to
manually edit the session or workflow properties when you change the Informatica Server. If
the new Informatica Server cannot locate the override directory, it cannot execute the session.
For example, you might override the workflow log directory in the workflow properties, by
entering d:\data\workflowlog. You then copy the folder containing the workflow to a
production repository. The workflow log directory of the new Informatica Server is
c:\pmserver\workflowlog. When the new Informatica Server tries to run the copied workflow,
it cannot find the directory listed in the workflow properties, so it fails to initialize the
workflow. To correct the problem, you must either edit the workflow properties or create the
specified directory on the new Informatica Server.
Steps for Registering an Informatica Server
Use the following procedure to register an Informatica Server.
To register the Informatica Server:
1. In the Workflow Manager, connect to the repository.
2. Choose Connections-Server.
The Server Object Browser dialog box appears.
3. Click Add to register a new server.
The Server Editor dialog box appears.
4. Enter a new Server Name.
5. Configure the TCP/IP connectivity settings.
6. If you do not know the IP address, enter the host name and use the Resolve Server button
to resolve your IP address. You can also enter the IP address in the Host Name/IP Address
field and use the Resolve SErver button to resolve the hostname.
The Workflow Manager also resolves the host name and IP address when you click OK.
Table 10-1 describes the settings required to register an Informatica Server using TCP/IP:
Table 10-1. TCP/IP Settings to Register a Server
TCP/IP Option
Required/
Optional
Description
Server Name Required The name of Informatica Server. Use to select the Informatica
Server to run a workflow. This name must be unique to the
repository.
The Workflow Manager allows special characters such as a
colon (:) and ampersand (&) in server names.
Host Name or IP
address
Required Server host name or IP address of the Informatica Server
machine.
Resolved IP Address n/a (read-only) The IP address resolved by the Workflow Manager. This is a
read-only field.
Port Number Required Port number the Informatica Server uses. Must be the same port
listed in the Informatica Server configuration parameters.
7. For $PMRootDir, enter a valid root directory for the Informatica Server platform.
Informatica recommends using the Informatica Server installation directory as the
recommended root directory because the Informatica Server installation creates the
default server directories in the Server installation directory. If you enter a different root
directory, make sure to create the necessary directories.
8. Enter the server variables, as desired.
Do not use trailing delimiters. A trailing delimiter might invalidate the directory used by
the Informatica Server. For example, enter c:\data\sessionlog, not c:\data\sessionlog\.
See Table 7-1 on page 186 for a list of server variables.
9. Click OK.
The new Informatica Server appears in the Navigator below the repository.
Timeout Required Number of seconds the Workflow Manager waits for a response
from the Informatica Server.
Code Page Required Character set associated with the Informatica Server. Select the
code page identical to the Informatica Server operating system
code page. Must be identical to or compatible with the
repository code page.
Table 10-1. TCP/IP Settings to Register a Server
TCP/IP Option
Required/
Optional
Description
191
C h a p t e r 1 1
Upgrading a Repository
192 Chapter 11: Upgrading a Reposi tory
Overview
Please see Upgrading a Repository in the Supplemental Guide for information on the
following topics:
Upgrading a repository
The upgrade process
Preparing to upgrade
Troubleshooting for upgrading the repository.
For information on upgrading repository metadata, see Upgrading Repository Metadata in
the Supplemental Guide.
193
C h a p t e r 1 2
Using ODBC
Overview, 194
ODBC Data Sources, 195
ODBC and the Informatica Client and Server, 196
ODBC Calls, 198
Creating an ODBC Data Source, 201
Configuring an ODBC Data Source, 204
Deleting an ODBC Data Source, 205
Troubleshooting, 206
194 Chapter 12: Using ODBC
Overview
Open Database Connectivity (ODBC) provides a common way to communicate with several
different database platforms.
ODBC consists of three distinct components:
1. ODBC drivers. Process ODBC calls, submit SQL requests to data sources, and return
results. The drivers must connect to the client libraries to access the databases. They
communicate with data sources.
2. ODBC Driver Manager. Loads and calls one or more ODBC drivers to open and close
communications to databases.
3. ODBC Administrator. The visible part of the ODBC Driver Manager, launched from
the Control Panel in Windows 98 and Windows. Use the ODBC Administrator to create,
modify, and delete ODBC data sources.
Figure 12-1 illustrates connectivity between PowerCenter or PowerMart, the ODBC
components, and databases:
Figure 12-1. ODBC Connectivity Overview
PowerMart and PowerCenter
Driver Manager
ODBC Driver
for Sybase
ODBC Driver
for Oracle
Sybase Client Library Oracle Client Library
Sybase
Database
Oracle
Database
ODBC components
ODBC Data Sources 195
ODBC Data Sources
A data source consists of a set of data that has a supporting ODBC driver and associated
environments, such as the operating system and database. An ODBC data source refers to the
location of the data and the information required to access the data. This information
includes the driver name and network address.
Each ODBC data source has a unique data source name (DSN). For example, if you have an
ODBC data source named My Oracle connection on the system, you cannot give another data
source the same name.
You can create two types of data source: System and User. A System DSN is available to all
users on a machine, including users accessing the machine from a network connection. A User
DSN is available to a specific user and can only be used on the local machine. If you have a
System DSN and a User DSN with the same name, the ODBC data source uses the User
DSN information. When you set up the network connectivity to a system data source, you
use the System DSN. The Informatica Server uses the System DSN. The Informatica Client
uses either the User or System DSN.
Most ODBC connections require a data source name to connect to a database, but some data
sources, such as text files, do not require a data source name since they are not registered to
any particular user or workstation. However, you might set other options, such as designating
all sessions started through the ODBC connection as read-only.
Every ODBC driver presents its own configuration dialog box with customized options.
Different ODBC driver vendors might have their own drivers for connecting to the same
RDBMS. Therefore, each vendor driver may have different options for connections opened to
the same database.
ODBC and the Informatica Client and Server
The Informatica Client uses ODBC drivers to connect to databases. You can configure the
Informatica Server to use native drivers or ODBC drivers to connect to databases. However,
Informatica strongly recommends using native drivers when possible.
PowerCenter and PowerMart support ODBC drivers, such as ISG Navigator, that do not need
usernames and passwords to connect. To avoid using empty strings or nulls, use the reserved
words PmNullUser and PmNullPasswd for the username and password to connect to the
databases. The Informatica Server treats PmNullUser and PmNullPasswd as no user and no
password.
Before using ODBC data sources, make sure all the information provided in the ODBC DSN
is correct and the underlying connectivity software is already installed.
Table 12-1 shows the information that the Informatica Client and Server require to connect
the source, target, and repository databases:
The Designer accesses the ODBC Administrator settings to connect to data sources.
The Informatica Server on Windows or UNIX can connect to ODBC data sources to access
source and target data. On Windows, you connect to databases using the data sources
configured in the ODBC Administrator. On UNIX, you set ODBC environment variables for
data sources. The connect string is the database data source name in square brackets in the
odbc.ini file. For an example of an odbc.ini file and connect string information, see
Installing and Configuring ODBC for UNIX on page 177.
Table 12-1. ODBC Connection Requirements
Informatica Client and Server Connects to Required Information
Designer Source or Target ODBC data source name
- Username
- Password
Informatica Server Source or Target Data source name
- Username
- Password
- Connect string
- Database type
Note: Passwords must be in US-ASCII only.
ODBC and the Informati ca Cl i ent and Server 197
Database ODBC Drivers
The Informatica Client tools use ODBC drivers to connect to source and target databases.
Table 12-2 shows the ODBC drivers to use with each database:
If you have problems connecting to a database other than one of the supported source or
target databases, contact the ODBC driver vendor regarding function calls supported by the
driver. For a list of function calls, see ODBC Calls on page 198.
PowerCenter 6.0 and PowerMart 6.0 support the Merant 3.7 32-bit closed ODBC drivers
supplied with the installation CD. You can have only one version of the Merant drivers on the
system. Therefore, you need to install the drivers included on the Informatica installation CD
to ensure that you have the most recent version of these drivers. The Merant 3.7 32-bit
ODBC closed drivers are fully backward compatible. If you have any questions, contact
Merant.
Table 12-2. Database ODBC Drivers
Database ODBC Driver
IBM DB2 IBM ODBC driver
Informix Merant 3.7 32-bit closed ODBC driver
Microsoft Access97 Microsoft Access driver
Microsoft Excel Microsoft Excel driver
Microsoft SQL Server Microsoft SQL Server ODBC driver
Oracle Merant 3.7 32-bit closed ODBC driver
Sybase Merant 3.7 32-bit closed ODBC driver
Teradata Teradata ODBC driver
ODBC Calls
The Informatica Client and Server make the following function calls to connect to supported
ODBC drivers.
Client ODBC Calls
The Informatica Client makes function calls when communicating with databases.
Table 12-3 describes the core function calls the Informatica Client makes to connect to
ODBC drivers:
Table 12-3. Informatica Client ODBC Function Calls
Function Description
SQLAllocConnect Allocates resources for a connection.
SQLAllocStmt Allocates resources for a statement.
SQLBindCol Binds a result column.
SQLBindParam Binds a parameter.
SQLBindParameter Binds a parameter.
SQLCancel Cancels a query.
SQLColumns Called with the table name and the owner name. NULL is never passed
for the owner name or table name. The owner name is obtained from the
results of SQLTables.
SQLConnect Connects.
SQLDescribe Retrieves column information for a prepared query.
SQLDisconnect Disconnects.
SQLError Errors.
SQLExecDirect Executes a statement.
SQLExecute Executes a statement.
SQLFetch Fetches row by row.
SQLForeignKeys Called with the table name and the owner name. NULL is never passed
results of SQLTables above. This is called twice:
- With the FROM table as NULL
- With the TO table as NULL
SQLFreeConnect Frees the resources allocated by connect.
SQLFreeStmt Frees resources allocated by a statement.
ODBC Cal ls 199
Server ODBC Calls
The Informatica Server on UNIX and Windows can access databases through ODBC drivers.
Note: When you use Stored Procedure and Lookup transformations in a mapping, these
transformations also use ODBC calls to communicate with databases.
Table 12-4 describes the core function calls the Informatica Server makes to connect to
ODBC drivers:
SQLGetFunctions Called to see if the driver supports SQLForeignKeys before calling it.
SQLForeignKeys is called only if the driver supports it. The Intersolv 2.x
Informix driver does not support SQLForeignKeys.
SQLNumResultsCols Retrieves specified number of result columns from a query.
SQLPrepare Parses a SQL statement.
SQLPrimaryKeys Called with the table name and the owner name. NULL is never passed
results of SQLTables.
SQLProcedureColumns Called with the procedure name and the owner name. NULL is never
passed for the owner name or procedure name. The owner name is
obtained from the results of SQLProcedures.
SQLProcedures Called with the supplied owner name or NULL if all owners are
requested.
SQLRowCount Retrieves the number of rows affected by a query.
SQLSetConnectOption Sets connection options.
SQLSetParam Sets a parameter.
SQLTables Called with the supplied owner name or NULL if all owners are
requested.
This is called a total of five times, once for each of the following:
- TABLE
- SYSTEM TABLE
- VIEW
- ALIAS
- SYNONYM
The Import dialog box displays the union of all returned rows.
SQLTransact Turns on/off the auto commit feature.
Table 12-4. Informatica Server ODBC Function Calls
SQLAllocConnect Allocates resources for a connection.
SQLAllocStmt Allocates resources for a statement.
Table 12-3. Informatica Client ODBC Function Calls
SQLBindCol Binds a result column.
SQLBindParam Binds a parameter.
SQLConnect Connects.
SQLDisconnect Disconnects.
SQLError Errors.
SQLExecute Executes a statement.
SQLFetch Fetches row by row.
SQLFreeConnect Frees the resources allocated by connect.
SQLFreeStmt Frees resources allocated by a statement.
SQLPrepare Parses a SQL statement.
SQLSetConnectOption Sets connection options.
SQLSetParam Sets a parameter.
SQLTransact Turns on/off the auto commit feature.
SQLSetStmtOption Sets the options for a statement to control how to read and how many rows to read.
SQLExtendedFetch Fetches arrays.
SQLGetInfo Gets information about the ODBC driver.
SQLGetFunctions Gets supported ODBC driver functions.
SQLGetStmtOptions Gets attributes from the statement in the connection.
SQLRowCount Returns the number of rows affected by the SQLExecute command.
Table 12-4. Informatica Server ODBC Function Calls
Creat ing an ODBC Dat a Source 201
Creating an ODBC Data Source
Before you can use ODBC to connect to a database, you must perform the following tasks:
Install ODBC on the system. Informatica uses the 32-bit ODBC drivers. 16-bit versions
of the ODBC Driver Manager are not compatible with 32-bit drivers. Use the installation
utility provided with the ODBC drivers to include entries for these drivers in the system
registry.
Create an ODBC data source for each database connection.
Use the ODBC Data Source Administrator to create and configure ODBC data sources.
To create an ODBC data source:
1. Launch the ODBC 32-bit Administrator.
2. Choose the System DSN tab.
3. Click Add.
A dialog box displays all the installed ODBC drivers on the system.
4. Select the ODBC driver you want to use and click Finish.
The configuration dialog box for that ODBC driver appears.
5. Enter the name for the new ODBC data source.
Every ODBC data source name (DSN) must be unique on the system.
6. If necessary, enter the username and password used to open a connection to the database.
You can use the reserved words PmNullUser and PmNullPasswd as the username and
password to connect to databases, such as ISG Navigator, that do not allow usernames
and passwords.
7. Enter any other configuration options.
Each ODBC driver configuration dialog box has a different set of options.
Configuring ODBC for Microsoft Excel
To access the Microsoft Excel file, first select the version of the application. Then click Select
Workbook and browse for the file that contains the source data. You must create an ODBC
data source for each source file.
Figure 12-2 shows the ODBC Microsoft Excel Setup dialog box:
For more information on Microsoft Excel sources, refer to the article in the Informatica
Webzine. You can access the webzine at http://my.Informatica.com.
Configuring ODBC for Sybase
To ensure consistent data in the repository, optimize performance, and reduce overhead on
tempdb, select the Performance tab. Change Prepare Method to 2-Full.
Figure 12-2. ODBC Microsoft Excel Setup
Choose the Microsoft Excel version.
Creat ing an ODBC Dat a Source 203
Figure 12-3 shows the ODBC Sybase Driver Setup dialog box:
Configuring ODBC for Microsoft SQL Server
To ensure consistent data in Microsoft SQL Server repositories, clear Create temporary stored
procedures for prepared SQL statements option in the Create a New Data Source to SQL
Server dialog box.
Figure 12-4 shows the dialog box for the Microsoft SQL Server ODBC setup:
If you have difficulty clearing the temporary stored procedures for prepared SQL statements
options, see the Informatica Webzine for more information about configuring Microsoft SQL
Server. You can access the webzine at http://my.Informatica.com.
Figure 12-3. ODBC Sybase Driver Setup
Figure 12-4. ODBC Microsoft SQL Server Setup
Set Prepare Method to 2-Full.
Clear Create temporary stored
procedures for prepared SQL
statements and drop the stored
procedures.
Configuring an ODBC Data Source
Once you create an ODBC data source, you can modify the settings. For example, you can
change the data source, its data source name (DSN), the database to which it connects, and
the default username and password. However, you cannot change the type of database to
which it connects.
To configure an ODBC data source:
You can either open the Control Panel and double-click the icon for 32-bit ODBC, or
run the ODBC Administrator.
2. Double-click the name of the data source.
The configuration dialog box for the ODBC driver used by that data source appears.
Each ODBC driver has its own configuration dialog box, which may open other dialog
boxes displaying advanced configuration options.
3. Make the modifications to the ODBC data source.
4. Click OK to close the ODBC driver configuration dialog box, then click Close to close
the ODBC Administrator.
Delet ing an ODBC Dat a Source 205
Deleting an ODBC Data Source
If you no longer need an ODBC data source, delete the DSN from the ODBC Administrator.
To delete an ODBC data source:
You can either open the Control Panel and double-click the icon for 32-bit ODBC or
you can run the ODBC Administrator.
2. Select the ODBC DSN to delete, and click Remove.
A prompt appears to make sure you want to delete the data source. Click Yes.
3. Click Close to close the ODBC Administrator.
Troubleshooting
I get one or both of the following errors when I try to create an ODBC DSN in the ODBC
Data Source Administrator.
The setup routines for <driver name> ODBC driver could not be loaded due
to System error code 126.
Could not load the setup or translator library.
Check that you have installed the client, such as Oracle Client for Oracle database. Then
configure the ODBC DSN. You need to set up the client environment before creating an
ODBC DSN.
I get the following error when I attempt to run a workflow using an Informix ODBC DSN
as my source and target.
CMN_1046 ODBC Error
CMN_1046 [Merant][ODBC Informix driver][Informix]Attempt to connect to
database server (INFOOnline) failed.]
You have created an ODBC DSN, but no longer have the underlying native connectivity
software or environment. You need to reconfigure the native connectivity environment and
then run the workflow.
207
A p p e n d i x A
Code Pages
This appendix documents code pages and their compatibility in PowerCenter and PowerMart.
Topics include:
Code Pages, 208
Code Page Reference, 210
Informatica Code Page Relationships, 214
Code Page Compatibility, 216
208 Appendi x A: Code Pages
Code Pages
PowerCenter and PowerMart support code pages for internationalization.
Table A-1 displays available code pages, including the code page name, description, and code
page ID:
Table A-1. Code Page Descriptions
Name Description ID
EuroShift-JIS Test code page, Shift-JIS with European characters 9999
IBM037 IBM EBCDIC US English 2028
IBM273 IBM EBCDIC German 2030
IBM280 IBM EBCDIC Italian 2035
IBM285 IBM EBCDIC UK English 2038
IBM297 IBM EBCDIC French 2040
IBM500 IBM EBCDIC International Latin-1 2044
IBM930 IBM EBCDIC Japanese 930
IBM935 IBM EBCDIC Simplified Chinese 935
IBM937 IBM EBCDIC Traditional Chinese 937
ISO-8859-10 ISO 8859-10 Latin 6 (Nordic) 13
ISO-8859-15 ISO 8859-15 Latin 9 (Western European) 201
ISO-8859-2 ISO 8859-2 Eastern European 5
ISO-8859-3 ISO 8859-3 Southeast European 6
ISO-8859-4 ISO 8859-4 Baltic 7
ISO-8859-5 ISO 8859-5 Cyrillic 8
ISO-8859-6 ISO 8859-6 Arabic 9
ISO-8859-7 ISO 8859-7 Greek 10
ISO-8859-8 ISO 8859-8 Hebrew 11
ISO-8859-9 ISO 8859-9 Latin 5 (Turkish) 12
JapanEUC* Japanese Extended UNIX Code (including JIS X 0212) 18
Latin1* ISO 8859-1 Western European 4
MS1250 MS Windows Latin 2 (Central Europe) 2250
MS1251 MS Windows Cyrillic (Slavic) 2251
MS1252* MS Windows Latin1 (ANSI), superset of Latin1 2252
MS1253 MS Windows Greek 2253
Code Pages 209
Note: Select IBM EBCDIC as your source database connection code page only if you access
When you enable data code page validation, PowerCenter and PowerMart support UTF-8 for
target code pages only.
MS1254 MS Windows Latin 5 (Turkish), superset of ISO 8859-9 2254
MS1255 MS Windows Hebrew 2255
MS1256 MS Windows Arabic 2256
MS1257 MS Windows Baltic Rim 2257
MS1258 MS Windows Vietnamese 2258
MS1361 MS Windows Korean (Johab) 1361
MS874 MS-DOS Thai, superset of TIS 620 874
MS932* MS Windows Japanese, Shift-JIS 2024
MS936 MS Windows Simplified Chinese, superset of GB 2312-
80, EUC encoding
936
MS949 MS Windows Korean, superset of KS C 5601-1992 949
MS950 MS Windows Traditional Chinese, superset of Big 5 950
US-ASCII* 7-bit ASCII 1
UTF-8 UTF-8 encoding of Unicode 106
* PowerCenter and PowerMart use these code pages.
Table A-1. Code Page Descriptions
Name Description ID
Code Page Reference
Each language might have can have multiple associated code pages.
Note: The code pages listed are the most appropriate for English. However, all code pages
include the US-ASCII characters.
Table A-2 lists the territories, code pages, and sorts most appropriate for each language:
Table A-2. Code Pages by Language
Language Territory Code Page Sort Order
Albanian Albania ISO-8859-2
MS1250
Latin1
MS1252
ISO-8859-9
UTF-8
Default
Binary
Arabic Saudi Arabia ISO-8859-6
MS1256
UTF-8
Default
Binary
Belorussian Belarus ISO-8859-5
MS1251
UTF-8
Default
Binary
Bulgarian Bulgaria ISO-8859-5
MS1251
UTF-8
Default
Binary
Canadian French French-Canada Latin1
MS1252
ISO-8859-9
UTF-8
IBM297
Default
Binary
Catalan Catalonia Latin1
MS1252
ISO-8859-9
UTF-8
Default
Binary
Croatian Croatia ISO-8859-2
MS1250
UTF-8
Croatian
Binary
Cyrillic Serbian Yugoslavia ISO-8859-5
MS1251
UTF-8
Default
Binary
Czech Czech Republic ISO-8859-2
MS1250
UTF-8
Czech
Binary
Code Page Ref erence 211
Danish Denmark Latin1
MS1252
ISO-8859-9
UTF-8
Danish
Binary
Dutch Netherlands
Dutch-Belgium
Latin1
MS1252
ISO-8859-9
UTF-8
IBM037
Default
Binary
English United States
Australia
Canada
New Zealand
South Africa
United Kingdom
US-ASCII
Latin1
MS1252
UTF-8
IBM037
IBM285
Binary
Default
Estonian Estonia ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Estonian
Binary
Farsi Iran ISO-8859-6
UTF-8
Default
Binary
Finnish Finland Latin1
MS1252
ISO-8859-9
UTF-8
Finnish
Binary
French France
French-Belgium
French-Canada
French-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM297
Default
Binary
German Germany
Austria
German-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM273
Default
Binary
Greek Greece ISO-8859-7
MS1253
UTF-8
Default
Binary
Hebrew Israel ISO-8859-8
MS1255
UTF-8
Default
Binary
Hungarian Hungary ISO-8859-2
MS1250
UTF-8
Hungarian
Binary
Italian Italy
Italian-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM280
Default
Binary
Japanese Japan JapanEUC
MS932
UTF-8
IBM930
Binary
Korean Korea MS949
MS1361
UTF-8
Binary
Latvian Latvia ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Latvian
Binary
Lithuanian Lithuania ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Lithuanian
Binary
Macedonian Macedonia ISO-8859-5
MS1251
UTF-8
Default
Binary
Norwegian Norway Latin1
MS1252
ISO-8859-9
UTF-8
Danish
Binary
Portuguese Portugal
Brazil
Latin1
MS1252
ISO-8859-9
UTF-8
IBM037
Default
Binary
Romanian Romania ISO-8859-2
MS1250
UTF-8
Romanian
Binary
Russian Russia ISO-8859-5
MS1251
UTF-8
Default
Binary
Serbian Yugoslavia ISO-8859-2
MS1250
UTF-8
Default
Binary
Simplified Chinese China MS936
UTF-8
IBM935
Binary
Code Page Ref erence 213
Slovak Slovakia ISO-8859-2
MS1250
UTF-8
Slovak
Slovenian Slovenia ISO-8859-2
MS1250
UTF-8
Slovenian
Binary
Spanish Spain
Argentina
Chile
Mexico
Latin1
MS1252
ISO-8859-9
UTF-8
Spanish
Traditional Spanish
Binary
Swedish Sweden Latin1
MS1252
ISO-8859-9
UTF-8
Swedish
Binary
Thai Thailand MS874
UTF-8
Thai
Binary
Turkish Turkey ISO-8859-9
ISO-8859-3
MS1254
UTF-8
Turkish
Binary
Ukrainian Ukraine ISO-8859-5
MS1251
UTF-8
Ukrainian
Binary
Vietnamese Vietnam MS1258
UTF-8
Vietnamese
Binary
Informatica Code Page Relationships
For accurate data movement and transformation, make sure the code pages of each
PowerCenter and PowerMart component have the correct relationships with each other.
One code page can be a subset or superset of another. For accurate data movement, the target
code page must be a superset of both the source code page and Informatica Server code page.
In addition, the Informatica Server code page must be a superset of the source code page. If
the source database code page is a superset of the target code page, the Informatica Server
cannot process characters in the source because they are not encoded in the target code page.
The target then results in incorrect or missing data.
For example, Latin1 is a superset of US-ASCII. It contains all US-ASCII character encoding
in addition to its own character set encoding. If you select US-ASCII for the source code
page, Latin1 for the target code page, and the Informatica Server code page is Latin 1, the
Informatica Server writes accurate data to the target. However, if you select US-ASCII for the
target code page while the Informatica Server uses the Latin1 code page, the Informatica
Server might write incorrect or incomplete data to the target.
When two code pages are compatible, the characters encoded in the two code pages are
identical. For example, the IBM EBCDIC US English and Latin1 code pages contain
identical character sets and are compatible with each other. The repository and Informatica
Server can each use one these code pages and can pass data back and forth without data loss.
Note: When you create or upgrade a repository, do not select IBM EBCDIC for the code page.
Table A-3 summarizes code page compatibility between PowerCenter and PowerMart
components:
Table A-3. Code Page Compatibility
Source (including relational, flat file, and
Application)
Subset of target.
Subset of Informatica Server.
Target (including relational and flat file) Superset of source.
Superset of Informatica Server.
External Loader data and control files are created using the target flat file
code page.
Informatica Server Superset of source.
Subset of target.
Identical to Informatica Server operating system and machine hosting
pmcmd.
Compatible with repository, Informatica Client, Lookup, and Stored
Procedure transformation.
Global Repository Compatible with local repository. Can also be a subset of local repository.
Local Repository Compatible with global repository. Can also be a superset of global
repository.
Informat ica Code Page Rel at ionshi ps 215
For details on code page compatibility between components, see Globalization Overview on
page 29.
Standalone Repository Compatible with Informatica Client and Server.
Informatica Client Compatible with Informatica Server and repository.
pmcmd Identical to Informatica Server.
Table A-3. Code Page Compatibility
Code Page Compatibility
To allow greater flexibility in using code pages, Informatica considers some code pages
compatible, though they do not contain identical character sets.
Table A-4 describes the code pages Informatica considers compatible with each other:
Supported Code Pages and Related Code Pages
Table A-5 lists all supported code pages. Each supported code page has a corresponding
column for each of the following code pages:
Code pages compatible with the specified code page
Code pages that are supersets of the specified code page
Code pages that are subsets of the specified code page
Because a code page that is compatible with another code page can also act as superset or
subset of that code page, each compatible code page appears at the top of the list of supersets
and subsets. All other superset and subset code pages appear alphabetically below compatible
code pages.
For example, the first row of the table lists related code pages for the IBM037 (IBM EBCDIC
US English) code page.
IBM037 has three compatible code pages:
IBM037 (itself )
Latin1 (ISO 8859-1 Western European)
MS Latin1 (MS1252)
Table A-4. Compatible Code Pages
Code Page Compatible with
IBM037 IBM EBCDIC US English* Latin1 (ISO-8859-1)*
MS1252 MS Latin1
Latin1 (ISO-8859-1)* IBM037 IBM EBCDIC US English*
MS1252 MS Latin1
MS1252 MS Latin1 Latin1 (ISO-8859-1)
IBM037 IBM EBCDIC US English
JapanEUC IBM 930 IBM EBCDIC Japanese
MS932 MS Shift JIS
MS932 MS Shift JIS IBM930 IBM EBCDIC Japanese
JapanEUC
IBM930 IBM EBCDIC Japanese Japan EUC
MS932 MS Shift JIS
*No character loss occurs during code page conversion.
Code Page Compati bi l i ty 217
All three code pages are also supersets and subsets of IBM037 and appear at the top of those
columns. In addition, the Supersets column contains UTF-8, indicating it contains all critical
characters in the IBM037 code page. The Subsets column contains US-ASCII, indicating
IBM037 contains all critical US-ASCII characters.
Note: Although the IBM EBCDIC code page is compatible with Latin1 and MS Latin1, you
cannot install the Informatica Client, Server, or repository on a machine using the IBM
EBCDIC code page.
Table A-5 describes supported and compatible code pages:
Table A-5. Supported Code Pages and Related Code Pages
Supported Code Page Compatible Code Page Subsets Supersets
IBM037 (IBM EBCDIC US
English)
IBM037 IBM EBCDIC US
English)
Latin1(ISO 8859-1
Western European)
MS 1252 (MS Windows
Latin1 (ANSI), superset of
Latin1)
English)
Latin1 (ISO 8859-1
Western European)
English)
Latin1 (ISO 8859-1
Western European)
MS 1252 (MS Windows
Latin1 (ANSI), superset of
Latin1)
UTF-8 (UTF-8 encoding of
Unicode)
IBM273 (IBM EBCDIC
German)
IBM273 (IBM EBCDIC
German)
IBM273 (IBM EBCDIC
German
IBM273 (IBM EBCDIC
German
Unicode)
IBM280 (IBM EBCDIC
Italian)
IBM280 (IBM EBCDIC
Italian)
IBM280 (IBM EBCDIC
Italian)
IBM280 (IBM EBCDIC
Italian)
Unicode)
IBM285 (IBM EBCDIC UK
English)
English)
English)
English)
Unicode)
IBM297 (IBM EBCDIC
French)
IBM297 (IBM EBCDIC
French)
IBM297 (IBM EBCDIC
French)
IBM297 (IBM EBCDIC
French)
Unicode)
IBM500 (IBM EBCDIC
International Latin-1)
IBM500 (IBM EBCDIC
IBM500 (IBM EBCDIC
IBM500 (IBM EBCDIC
Unicode)
IBM930 (IBM EBCDIC
Japanese)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
MS932 (MS Windows
Shift-JIS)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
MS932 (MS Windows
Shift-JIS)
Unicode)
IBM935 (IBM EBCDIC
Simplified Chinese)
IBM935 (IBM EBCDIC
Simplified Chinese)
IBM935 (IBM EBCDIC
Simplified Chinese)
IBM935 (IBM EBCDIC
Simplified Chinese)
Unicode)
IBM937 (IBM EBCDIC
Traditional Chinese)
IBM937 (IBM EBCDIC
IBM937 (IBM EBCDIC
IBM937 (IBM EBCDIC
Unicode)
ISO-8859-2 (ISO 8859-2
Eastern European)
ISO-8859-2 (ISO 8859-2
Eastern European)
ISO-8859-2 (ISO 8859-2
Eastern European)
ISO-8859-2 (ISO 8859-2
Eastern European)
Unicode)
ISO-8859-3 (ISO 8859-3
Southeast European)
ISO-8859-3 (ISO 8859-3
Southeast European)
ISO-8859-3 (ISO 8859-3
Southeast European)
ISO-8859-3 (ISO 8859-3
Southeast European)
Unicode)
ISO-8859-4 (ISO 8859-4
Baltic)
ISO-8859-4 (ISO 8859-4
Baltic)
ISO-8859-4 (ISO 8859-4
Baltic)
ISO-8859-4 (ISO 8859-4
Baltic)
Unicode)
ISO-8859-5 (ISO 8859-5
Cyrillic)
ISO-8859-5 (ISO 8859-5
Cyrillic)
ISO-8859-5 (ISO 8859-5
Cyrillic)
ISO-8859-5 (ISO 8859-5
Cyrillic)
Unicode)
ISO-8859-6 (ISO 8859-6
Arabic)
ISO-8859-6 (ISO 8859-6
Arabic)
ISO-8859-6 (ISO 8859-6
Arabic)
ISO-8859-6 (ISO 8859-6
Arabic)
Unicode)
ISO-8859-7 (ISO 8859-7
Greek)
ISO-8859-7 (ISO 8859-7
Greek)
ISO-8859-7 (ISO 8859-7
Greek)
Unicode)
ISO-8859-7 (ISO 8859-7
Greek)
Unicode)
ISO-8859-8 (ISO 8859-8
Hebrew)
ISO-8859-8 (ISO 8859-8
Hebrew)
ISO-8859-8 (ISO 8859-8
Hebrew)
ISO-8859-8 (ISO 8859-8
Hebrew)
Unicode)
ISO-8859-9 (ISO 8859-9
Latin 5 (Turkish))
ISO-8859-9 (ISO 8859-9
Latin 5 (Turkish))
ISO-8859-9 (ISO 8859-9
Latin 5 (Turkish))
ISO-8859-9 (ISO 8859-9
Latin 5 (Turkish))
Unicode)
ISO-8859-10 (ISO 8859-
10 Latin 6 (Nordic))
ISO-8859-10 (ISO 8859-
ISO-8859-10 (ISO 8859-
ISO-8859-10 (ISO 8859-
Unicode)
ISO-8859-15 (ISO 8859-
15 Latin 9 (Western
European))
ISO-8859-15 (ISO 8859-
15 Latin 9 (Western
European))
ISO-8859-15 (ISO 8859-
15 Latin 9 (Western
European))
ISO-8859-15 (ISO 8859-
15 Latin 9 (Western
European))
Unicode)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
JapanEUC (Japanese
Extended UNIX Code
IBM930 (IBM EBCDIC
Japanese)
JEF (Japanese EBCDIC
Fujitsu)
JIPSE (NEC ACOS JIPSE
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
IBM930 (IBM EBCDIC
Japanese)
Fujitsu)
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
IBM930 (IBM EBCDIC
Japanese)
Fujitsu)
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Shift-JIS)
UNISYS (UNISYS
Japanese)
Unicode)
Fujitsu)
Fujitsu)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Fujitsu)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Fujitsu)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Japanese)
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
KEIS (HITACHI KEIS
Japanese)
KEIS (HITACHI KEIS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
KEIS (HITACHI KEIS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
KEIS (HITACHI KEIS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
Latin1 (ISO 8859-1
Western European)
Latin1 (ISO 8859-1
Western European)
English)
MS1252 (MS Windows
Latin 1 (ANSI), superset of
Latin1)
Latin1 (ISO 8859-1
Western European)
English)
MS1252 (MS Windows
Latin1)
Latin1 (ISO 8859-1
Western European)
English)
MS1252 (MS Windows
Latin1)
Unicode)
MELCOM (MITSUBISHI
MELCOM Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
MS874 (MS-DOS Thai,
superset of TIS 620)
MS874 (MS-DOS Thai,
MS874 (MS-DOS Thai,
MS874 (MS-DOS Thai,
Unicode)
MS932 (MS Windows
Shift-JIS)
MS932 (MS Windows
Shift-JIS)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
Fujitsu)
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
UNISYS (UNISYS
Japanese)
MS932 (MS Windows
Shift-JIS)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
Fujitsu)
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
UNISYS (UNISYS
Japanese)
MS932 (MS Windows
Shift-JIS)
IBM930 (IBM EBCDIC
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(incl. JIS X 0212))
Fujitsu)
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
UNISYS (UNISYS
Japanese)
Unicode)
MS936 (MS Windows
Simplified Chinese,
superset of GB 2312-80,
EUC encoding)
MS936 (MS Windows
Simplified Chinese,
EUC encoding)
MS936 (MS Windows
Simplified Chinese,
EUC encoding)
MS936 (MS Windows
Simplified Chinese,
EUC encoding)
Unicode)
MS949 (MS Windows
Korean, superset of KS C
5601-1992)
MS949 (MS Windows
5601-1992)
MS949 (MS Windows
5601-1992)
MS949 (MS Windows
5601-1992)
Unicode)
MS950 (MS Windows
Traditional Chinese,
superset of Big 5)
MS950 (MS Windows
superset of Big 5)
MS950 (MS Windows
superset of Big 5)
MS950 (MS Windows
superset of Big 5)
Unicode)
MS1250 (MS Windows
Latin 2 (Central Europe))
MS1250 (MS Windows
MS1250 (MS Windows
MS1250 (MS Windows
Unicode)
MS1251 (MS Windows
Cyrillic (Slavic))
MS1251 (MS Windows
Cyrillic (Slavic))
MS1251 (MS Windows
Cyrillic (Slavic))
MS1251 (MS Windows
Cyrillic (Slavic))
Unicode)
MS1252 (MS Windows
Latin1)
MS1252 (MS Windows
Latin1)
English)
Latin1 (ISO 8859-1
Western European)
MS1252 (MS Windows
Latin1)
English)
Latin1 (ISO 8859-1
Western European)
MS1252 (MS Windows
Latin1)
English)
Latin1 (ISO 8859-1
Western European)
Unicode)
MS1253 (MS Windows
Greek)
MS1253 (MS Windows
Greek)
MS1253 (MS Windows
Greek)
MS1253 (MS Windows
Greek)
Unicode)
MS1254 (MS Windows
Latin 5 (Turkish), superset
of ISO 8859-9)
MS1254 (MS Windows
of ISO 8859-9)
MS1254 (MS Windows
of ISO 8859-9)
MS1254 (MS Windows
of ISO 8859-9)
Unicode)
MS1255 (MS Windows
Hebrew)
MS1255 (MS Windows
Hebrew)
MS1255 (MS Windows
Hebrew)
MS1255 (MS Windows
Hebrew)
Unicode)
MS1256 (MS Windows
Arabic)
MS1256 (MS Windows
Arabic)
MS1256 (MS Windows
Arabic)
MS1256 (MS Windows
Arabic)
Unicode)
MS1257 (MS Windows
Baltic Rim)
MS1257 (MS Windows
Baltic Rim)
MS1257 (MS Windows
Baltic Rim)
MS1257 (MS Windows
Baltic Rim)
Unicode)
MS1258 (MS Windows
Vietnamese)
MS1258 (MS Windows
Vietnamese)
MS1258 (MS Windows
Vietnamese)
MS1258 (MS Windows
Vietnamese)
Unicode)
MS1361 (MS Windows
Korean (Johab))
MS1361 (MS Windows
Korean (Johab))
MS1361 (MS Windows
Korean (Johab))
MS1361 (MS Windows
Korean (Johab))
Unicode)
UNISYS (UNISYS
Japanese)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
MS932 (MS Windows
Shift-JIS)
US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII)
English)
IBM273 (IBM EBCDIC
German)
IBM280 (IBM EBCDIC
Italian)
English)
IBM297 (IBM EBCDIC
French)
IBM500 (IBM EBCDIC
IBM930 (IBM EBCDIC
Japanese)
IBM935 (IBM EBCDIC
Simplified Chinese)
IBM937 (IBM EBCDIC
ISO-8859-2 (ISO 8859-2
Eastern European)
ISO-8859-3 (ISO 8859-3
Southeast European)
ISO-8859-4 (ISO 8859-4
Baltic)
ISO-8859-5 (ISO 8859-5
Cyrillic)
ISO-8859-6 (ISO 8859-6
Arabic)
ISO-8859-7 (ISO 8859-7
Greek)
ISO-8859-8 (ISO 8859-8
Hebrew)
ISO-8859-9 (ISO 8859-9
Latin 5 (Turkish))
ISO-8859-15 (ISO 8859-
15 Latin 9 (Western
European))
JapanEUC (Japanese
Extended UNIX Code
(incl.
Fujitsu)
Japanese)
JIS X 0212))
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
Latin1 (ISO 8859-1
Western European)
When you select code pages that Informatica considers compatible, keep in mind that some
characters do not convert from one code page to another. These characters are unlikely to be
in your source data. For a complete list of characters you might lose during code page
conversions, see the following sections.
US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) MS874 (MS-DOS Thai,
MS932 (MS Windows
Shift-JIS)
MS936 (MS Windows
Simplified Chinese,
EUC encoding)
MS949 (MS Windows
5601-1992)
Korean (Johab))
MS950 (MS Windows
superset of Big 5)
MS1250 (MS Windows
MS1251 (MS Windows
Cyrillic (Slavic))
MS1252 (MS Windows
Latin1)
MS1253 (MS Windows
Greek)
MS1254 (MS Windows
of ISO 8859-9)
MS1255 (MS Windows
Hebrew)
MS1256 (MS Windows
Arabic)
MS1257 (MS Windows
Baltic Rim)
MS1361 (MS Windows
Korean (Johab))
UNISYS (UNISYS
Japanese)
Unicode)
Converting from MS Latin1 to Latin1
Table A-6 lists all characters by character ID and description that do not convert from MS
Latin1 to Latin1:
Converting from Latin1 to MS Latin1
Table A-7 lists all characters by character ID and description that do not convert from Latin1
to MS Latin1:
Table A-6. MS Latin1 to Latin1 Character Conversion
Characters lost when converting from MS1252 MS Latin1 to Latin1 (ISO-8859-1)
338 (LATIN CAPITAL LIGATURE OE) 8218 (SINGLE LOW-9 QUOTATION MARK)
339 (LATIN SMALL LIGATURE OE) 8220 (LEFT DOUBLE QUOTATION MARK)
352 (LATIN CAPITAL LETTER S WITH CARON) 8221 (RIGHT DOUBLE QUOTATION MARK)
353 (LATIN SMALL LETTER S WITH CARON) 8222 (DOUBLE LOW-9 QUOTATION MARK)
376 (LATIN CAPITAL LETTER Y WITH DIAERESIS) 8224 (DAGGER)
381 (LATIN CAPITAL LETTER Z WITH CARON) 8225 (DOUBLE DAGGER)
382 (LATIN SMALL LETTER Z WITH CARON) 8226 (BULLET)
402 (LATIN SMALL LETTER F WITH HOOK) 8230 (HORIZONTAL ELLIPSIS)
710 (MODIFIER LETTER CIRCUMFLEX ACCENT) 8240 (PER MILLE SIGN)
732 (SMALL TILDE) 8249 (SINGLE LEFT-POINTING ANGLE QUOTATION MARK)
8211 (EN DASH) 8250 (SINGLE RIGHT-POINTING ANGLE QUOTATION
MARK)
8212 (EM DASH) 8364 (EURO SIGN)
8216 (LEFT SINGLE QUOTATION MARK) 8482 (TRADE MARK SIGN)
8217 (RIGHT SINGLE QUOTATION MARK)
Table A-7. Latin1 to MS Latin1 Character Conversion
Characters lost when converting from Latin1 (ISO-8859-1) to MS1252 MS Latin1
128 (<control character>) 144 (<control character>)
Converting from IBM EBCDIC US English to Latin1
Table A-8 lists all characters by character ID and description that do not convert from IBM
EBCDIC US English to Latin1:
Table A-8. IBM EBCDIC US English to Latin1 Character Conversion
Characters lost when converting from IBM037 (IBM EBCDIC US English) to Latin1 (ISO-8859-1)
338 (LATIN CAPITAL LIGATURE OE) 8218 (SINGLE LOW-9 QUOTATION MARK)
339 (LATIN SMALL LIGATURE OE) 8220 (LEFT DOUBLE QUOTATION MARK)
352 (LATIN CAPITAL LETTER S WITH CARON) 8221 (RIGHT DOUBLE QUOTATION MARK)
353 (LATIN SMALL LETTER S WITH CARON) 8222 (DOUBLE LOW-9 QUOTATION MARK)
376 (LATIN CAPITAL LETTER Y WITH DIAERESIS) 8224 (DAGGER)
381 (LATIN CAPITAL LETTER Z WITH CARON) 8225 (DOUBLE DAGGER)
382 (LATIN SMALL LETTER Z WITH CARON) 8226 (BULLET)
402 (LATIN SMALL LETTER F WITH HOOK) 8230 (HORIZONTAL ELLIPSIS)
710 (MODIFIER LETTER CIRCUMFLEX ACCENT) 8240 (PER MILLE SIGN)
732 (SMALL TILDE) 8249 (SINGLE LEFT-POINTING ANGLE QUOTATION
MARK)
8211 (EN DASH) 8250 (SINGLE RIGHT-POINTING ANGLE QUOTATION
MARK)
8212 (EM DASH) 8364 (EURO SIGN)
8216 (LEFT SINGLE QUOTATION MARK) 8482 (TRADE MARK SIGN)
8217 (RIGHT SINGLE QUOTATION MARK)
Table A-7. Latin1 to MS Latin1 Character Conversion
Characters lost when converting from Latin1 (ISO-8859-1) to MS1252 MS Latin1
Converting from Latin1 to IBM EBCDIC US English
Table A-9 lists all characters by character ID and description that do not convert from Latin1
to IBM EBCDIC US English:
Converting from MS Shift JIS to JapanEUC
Shift JIS to JapanEUC:
Table A-9. Latin1 to IBM EBCDIC US English Character Conversion
Characters lost when converting from Latin1 (ISO-8859-1) to IBM037 (IBM EBCDIC US English)
Table A-10. MS Shift JIS to JapanEUC Character Conversion
Characters lost when converting from MS932 (MS Shift JIS) to JapanEUC
8481 (TELEPHONE SIGN) 13095 (SQUARE TON)
8544 (ROMAN NUMERAL ONE) 13099 (SQUARE PAASENTO)
8545 (ROMAN NUMERAL TWO) 13110 (SQUARE HEKUTAARU)
8546 (ROMAN NUMERAL THREE) 13115 (SQUARE PEEZI)
8547 (ROMAN NUMERAL FOUR) 13129 (SQUARE MIRI)
8548 (ROMAN NUMERAL FIVE) 13130 (SQUARE MIRIBAARU)
8549 (ROMAN NUMERAL SIX) 13133 (SQUARE MEETORU)
8550 (ROMAN NUMERAL SEVEN) 13137 (SQUARE RITTORU)
8551 (ROMAN NUMERAL EIGHT) 13143 (SQUARE WATTO)
8552 (ROMAN NUMERAL NINE) 13179 (SQUARE ERA NAME HEISEI)
8553 (ROMAN NUMERAL TEN) 13180 (SQUARE ERA NAME SYOUWA)
8560 (SMALL ROMAN NUMERAL ONE) 13181 (SQUARE ERA NAME TAISYOU)
8561 (SMALL ROMAN NUMERAL TWO) 13182 (SQUARE ERA NAME MEIZI)
8562 (SMALL ROMAN NUMERAL THREE) 13198 (SQUARE MG)
8563 (SMALL ROMAN NUMERAL FOUR) 13199 (SQUARE KG)
8564 (SMALL ROMAN NUMERAL FIVE) 13212 (SQUARE MM)
8565 (SMALL ROMAN NUMERAL SIX) 13213 (SQUARE CM)
8566 (SMALL ROMAN NUMERAL SEVEN) 13214 (SQUARE KM)
8567 (SMALL ROMAN NUMERAL EIGHT) 13217 (SQUARE M SQUARED)
8568 (SMALL ROMAN NUMERAL NINE) 13252 (SQUARE CC)
8569 (SMALL ROMAN NUMERAL TEN) 13261 (SQUARE KK)
8721 (N-ARY SUMMATION) 63785 (CJK COMPATIBILITY IDEOGRAPH-F929)
8735 (RIGHT ANGLE) 63964 (CJK COMPATIBILITY IDEOGRAPH-F9DC)
8741 (PARALLEL TO) 64014 (CJK COMPATIBILITY IDEOGRAPH-FA0E)
8750 (CONTOUR INTEGRAL) 64015 (CJK COMPATIBILITY IDEOGRAPH-FA0F)
8895 (RIGHT TRIANGLE) 64016 (CJK COMPATIBILITY IDEOGRAPH-FA10)
9312 (CIRCLED DIGIT ONE) 64017 (CJK COMPATIBILITY IDEOGRAPH-FA11)
9313 (CIRCLED DIGIT TWO) 64018 (CJK COMPATIBILITY IDEOGRAPH-FA12)
9314 (CIRCLED DIGIT THREE) 64019 (CJK COMPATIBILITY IDEOGRAPH-FA13)
9315 (CIRCLED DIGIT FOUR) 64020 (CJK COMPATIBILITY IDEOGRAPH-FA14)
9316 (CIRCLED DIGIT FIVE) 64021 (CJK COMPATIBILITY IDEOGRAPH-FA15)
9317 (CIRCLED DIGIT SIX) 64022 (CJK COMPATIBILITY IDEOGRAPH-FA16)
9318 (CIRCLED DIGIT SEVEN) 64023 (CJK COMPATIBILITY IDEOGRAPH-FA17)
9319 (CIRCLED DIGIT EIGHT) 64024 (CJK COMPATIBILITY IDEOGRAPH-FA18)
9320 (CIRCLED DIGIT NINE) 64025 (CJK COMPATIBILITY IDEOGRAPH-FA19)
9321 (CIRCLED NUMBER TEN) 64026 (CJK COMPATIBILITY IDEOGRAPH-FA1A)
9322 (CIRCLED NUMBER ELEVEN) 64027 (CJK COMPATIBILITY IDEOGRAPH-FA1B)
9323 (CIRCLED NUMBER TWELVE) 64028 (CJK COMPATIBILITY IDEOGRAPH-FA1C)
9324 (CIRCLED NUMBER THIRTEEN) 64029 (CJK COMPATIBILITY IDEOGRAPH-FA1D)
9325 (CIRCLED NUMBER FOURTEEN) 64030 (CJK COMPATIBILITY IDEOGRAPH-FA1E)
9326 (CIRCLED NUMBER FIFTEEN) 64031 (CJK COMPATIBILITY IDEOGRAPH-FA1F)
9327 (CIRCLED NUMBER SIXTEEN) 64032 (CJK COMPATIBILITY IDEOGRAPH-FA20)
9328 (CIRCLED NUMBER SEVENTEEN) 64033 (CJK COMPATIBILITY IDEOGRAPH-FA21)
9329 (CIRCLED NUMBER EIGHTEEN) 64034 (CJK COMPATIBILITY IDEOGRAPH-FA22)
9330 (CIRCLED NUMBER NINETEEN) 64035 (CJK COMPATIBILITY IDEOGRAPH-FA23)
9331 (CIRCLED NUMBER TWENTY) 64036 (CJK COMPATIBILITY IDEOGRAPH-FA24)
12317 (REVERSED DOUBLE PRIME QUOTATION MARK) 64037 (CJK COMPATIBILITY IDEOGRAPH-FA25)
12319 (LOW DOUBLE PRIME QUOTATION MARK) 64038 (CJK COMPATIBILITY IDEOGRAPH-FA26)
12849 (PARENTHESIZED IDEOGRAPH STOCK) 64039 (CJK COMPATIBILITY IDEOGRAPH-FA27)
12850 (PARENTHESIZED IDEOGRAPH HAVE) 64040 (CJK COMPATIBILITY IDEOGRAPH-FA28)
12857 (PARENTHESIZED IDEOGRAPH REPRESENT) 64041 (CJK COMPATIBILITY IDEOGRAPH-FA29)
12964 (CIRCLED IDEOGRAPH HIGH) 64042 (CJK COMPATIBILITY IDEOGRAPH-FA2A)
12965 (CIRCLED IDEOGRAPH CENTRE) 64043 (CJK COMPATIBILITY IDEOGRAPH-FA2B)
12966 (CIRCLED IDEOGRAPH LOW) 64044 (CJK COMPATIBILITY IDEOGRAPH-FA2C)
12967 (CIRCLED IDEOGRAPH LEFT) 64045 (CJK COMPATIBILITY IDEOGRAPH-FA2D)
12968 (CIRCLED IDEOGRAPH RIGHT) 65282 (FULLWIDTH QUOTATION MARK)
13059 (SQUARE AARU) 65287 (FULLWIDTH APOSTROPHE)
13069 (SQUARE KARORII) 65293 (FULLWIDTH HYPHEN-MINUS)
13076 (SQUARE KIRO) 65504 (FULLWIDTH CENT SIGN)
13080 (SQUARE GURAMU) 65505 (FULLWIDTH POUND SIGN)
13090 (SQUARE SENTI) 65506 (FULLWIDTH NOT SIGN)
13091 (SQUARE SENTO) 65508 (FULLWIDTH BROKEN BAR)
13094 (SQUARE DORU)
Converting from JapanEUC to MS Shift JIS
Table A-11 lists all characters by character ID and description that do not convert from
JapanEUC to MS Shift JIS:
Table A-11. JapanEUC to MS Shift JIS Character Conversion
Characters lost when converting from JapanEUC to MS932 (MS Shift JIS)
161 (INVERTED EXCLAMATION MARK) 323 (LATIN CAPITAL LETTER N WITH ACUTE)
162 (CENT SIGN) 324 (LATIN SMALL LETTER N WITH ACUTE)
163 (POUND SIGN) 325 (LATIN CAPITAL LETTER N WITH CEDILLA)
164 (CURRENCY SIGN) 326 (LATIN SMALL LETTER N WITH CEDILLA)
166 (BROKEN BAR) 327 (LATIN CAPITAL LETTER N WITH CARON)
169 (COPYRIGHT SIGN) 328 (LATIN SMALL LETTER N WITH CARON)
170 (FEMININE ORDINAL INDICATOR) 329 (LATIN SMALL LETTER N PRECEDED BY
APOSTROPHE)
172 (NOT SIGN) 330 (LATIN CAPITAL LETTER ENG)
174 (REGISTERED SIGN) 331 (LATIN SMALL LETTER ENG)
175 (MACRON) 332 (LATIN CAPITAL LETTER O WITH MACRON)
184 (CEDILLA) 333 (LATIN SMALL LETTER O WITH MACRON)
186 (MASCULINE ORDINAL INDICATOR) 336 (LATIN CAPITAL LETTER O WITH DOUBLE ACUTE)
191 (INVERTED QUESTION MARK) 337 (LATIN SMALL LETTER O WITH DOUBLE ACUTE)
192 (LATIN CAPITAL LETTER A WITH GRAVE) 338 (LATIN CAPITAL LIGATURE OE)
193 (LATIN CAPITAL LETTER A WITH ACUTE) 339 (LATIN SMALL LIGATURE OE)
194 (LATIN CAPITAL LETTER A WITH CIRCUMFLEX) 340 (LATIN CAPITAL LETTER R WITH ACUTE)
195 (LATIN CAPITAL LETTER A WITH TILDE) 341 (LATIN SMALL LETTER R WITH ACUTE)
196 (LATIN CAPITAL LETTER A WITH DIAERESIS) 342 (LATIN CAPITAL LETTER R WITH CEDILLA)
197 (LATIN CAPITAL LETTER A WITH RING ABOVE) 343 (LATIN SMALL LETTER R WITH CEDILLA)
198 (LATIN CAPITAL LETTER AE) 344 (LATIN CAPITAL LETTER R WITH CARON)
199 (LATIN CAPITAL LETTER C WITH CEDILLA) 345 (LATIN SMALL LETTER R WITH CARON)
200 (LATIN CAPITAL LETTER E WITH GRAVE) 346 (LATIN CAPITAL LETTER S WITH ACUTE)
201 (LATIN CAPITAL LETTER E WITH ACUTE) 347 (LATIN SMALL LETTER S WITH ACUTE)
202 (LATIN CAPITAL LETTER E WITH CIRCUMFLEX) 348 (LATIN CAPITAL LETTER S WITH CIRCUMFLEX)
203 (LATIN CAPITAL LETTER E WITH DIAERESIS) 349 (LATIN SMALL LETTER S WITH CIRCUMFLEX)
204 (LATIN CAPITAL LETTER I WITH GRAVE) 350 (LATIN CAPITAL LETTER S WITH CEDILLA)
205 (LATIN CAPITAL LETTER I WITH ACUTE) 351 (LATIN SMALL LETTER S WITH CEDILLA)
206 (LATIN CAPITAL LETTER I WITH CIRCUMFLEX) 352 (LATIN CAPITAL LETTER S WITH CARON)
207 (LATIN CAPITAL LETTER I WITH DIAERESIS) 353 (LATIN SMALL LETTER S WITH CARON)
209 (LATIN CAPITAL LETTER N WITH TILDE) 354 (LATIN CAPITAL LETTER T WITH CEDILLA)
210 (LATIN CAPITAL LETTER O WITH GRAVE) 355 (LATIN SMALL LETTER T WITH CEDILLA)
211 (LATIN CAPITAL LETTER O WITH ACUTE) 356 (LATIN CAPITAL LETTER T WITH CARON)
212 (LATIN CAPITAL LETTER O WITH CIRCUMFLEX) 357 (LATIN SMALL LETTER T WITH CARON)
213 (LATIN CAPITAL LETTER O WITH TILDE) 358 (LATIN CAPITAL LETTER T WITH STROKE)
214 (LATIN CAPITAL LETTER O WITH DIAERESIS) 359 (LATIN SMALL LETTER T WITH STROKE)
216 (LATIN CAPITAL LETTER O WITH STROKE) 360 (LATIN CAPITAL LETTER U WITH TILDE)
217 (LATIN CAPITAL LETTER U WITH GRAVE) 361 (LATIN SMALL LETTER U WITH TILDE)
218 (LATIN CAPITAL LETTER U WITH ACUTE) 362 (LATIN CAPITAL LETTER U WITH MACRON)
219 (LATIN CAPITAL LETTER U WITH CIRCUMFLEX) 363 (LATIN SMALL LETTER U WITH MACRON)
220 (LATIN CAPITAL LETTER U WITH DIAERESIS) 364 (LATIN CAPITAL LETTER U WITH BREVE)
221 (LATIN CAPITAL LETTER Y WITH ACUTE) 365 (LATIN SMALL LETTER U WITH BREVE)
222 (LATIN CAPITAL LETTER THORN) 366 (LATIN CAPITAL LETTER U WITH RING ABOVE)
223 (LATIN SMALL LETTER SHARP S) 367 (LATIN SMALL LETTER U WITH RING ABOVE)
224 (LATIN SMALL LETTER A WITH GRAVE) 368 (LATIN CAPITAL LETTER U WITH DOUBLE ACUTE)
225 (LATIN SMALL LETTER A WITH ACUTE) 369 (LATIN SMALL LETTER U WITH DOUBLE ACUTE)
226 (LATIN SMALL LETTER A WITH CIRCUMFLEX) 370 (LATIN CAPITAL LETTER U WITH OGONEK)
227 (LATIN SMALL LETTER A WITH TILDE) 371 (LATIN SMALL LETTER U WITH OGONEK)
228 (LATIN SMALL LETTER A WITH DIAERESIS) 372 (LATIN CAPITAL LETTER W WITH CIRCUMFLEX)
229 (LATIN SMALL LETTER A WITH RING ABOVE) 373 (LATIN SMALL LETTER W WITH CIRCUMFLEX)
230 (LATIN SMALL LETTER AE) 374 (LATIN CAPITAL LETTER Y WITH CIRCUMFLEX)
231 (LATIN SMALL LETTER C WITH CEDILLA) 375 (LATIN SMALL LETTER Y WITH CIRCUMFLEX)
232 (LATIN SMALL LETTER E WITH GRAVE) 376 (LATIN CAPITAL LETTER Y WITH DIAERESIS)
233 (LATIN SMALL LETTER E WITH ACUTE) 377 (LATIN CAPITAL LETTER Z WITH ACUTE)
234 (LATIN SMALL LETTER E WITH CIRCUMFLEX) 378 (LATIN SMALL LETTER Z WITH ACUTE)
235 (LATIN SMALL LETTER E WITH DIAERESIS) 379 (LATIN CAPITAL LETTER Z WITH DOT ABOVE)
236 (LATIN SMALL LETTER I WITH GRAVE) 380 (LATIN SMALL LETTER Z WITH DOT ABOVE)
237 (LATIN SMALL LETTER I WITH ACUTE) 381 (LATIN CAPITAL LETTER Z WITH CARON)
238 (LATIN SMALL LETTER I WITH CIRCUMFLEX) 382 (LATIN SMALL LETTER Z WITH CARON)
239 (LATIN SMALL LETTER I WITH DIAERESIS) 461 (LATIN CAPITAL LETTER A WITH CARON)
240 (LATIN SMALL LETTER ETH) 462 (LATIN SMALL LETTER A WITH CARON)
241 (LATIN SMALL LETTER N WITH TILDE) 463 (LATIN CAPITAL LETTER I WITH CARON)
242 (LATIN SMALL LETTER O WITH GRAVE) 464 (LATIN SMALL LETTER I WITH CARON)
243 (LATIN SMALL LETTER O WITH ACUTE) 465 (LATIN CAPITAL LETTER O WITH CARON)
244 (LATIN SMALL LETTER O WITH CIRCUMFLEX) 466 (LATIN SMALL LETTER O WITH CARON)
245 (LATIN SMALL LETTER O WITH TILDE) 467 (LATIN CAPITAL LETTER U WITH CARON)
246 (LATIN SMALL LETTER O WITH DIAERESIS) 468 (LATIN SMALL LETTER U WITH CARON)
248 (LATIN SMALL LETTER O WITH STROKE) 469 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
MACRON)
249 (LATIN SMALL LETTER U WITH GRAVE) 470 (LATIN SMALL LETTER U WITH DIAERESIS AND
MACRON)
250 (LATIN SMALL LETTER U WITH ACUTE) 471 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
ACUTE)
251 (LATIN SMALL LETTER U WITH CIRCUMFLEX) 472 (LATIN SMALL LETTER U WITH DIAERESIS AND
ACUTE)
252 (LATIN SMALL LETTER U WITH DIAERESIS) 473 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
CARON)
253 (LATIN SMALL LETTER Y WITH ACUTE) 474 (LATIN SMALL LETTER U WITH DIAERESIS AND
CARON)
254 (LATIN SMALL LETTER THORN) 475 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
GRAVE)
255 (LATIN SMALL LETTER Y WITH DIAERESIS) 476 (LATIN SMALL LETTER U WITH DIAERESIS AND
GRAVE)
256 (LATIN CAPITAL LETTER A WITH MACRON) 501 (LATIN SMALL LETTER G WITH ACUTE)
257 (LATIN SMALL LETTER A WITH MACRON) 711 (CARON)
258 (LATIN CAPITAL LETTER A WITH BREVE) 728 (BREVE)
259 (LATIN SMALL LETTER A WITH BREVE) 729 (DOT ABOVE)
260 (LATIN CAPITAL LETTER A WITH OGONEK) 730 (RING ABOVE)
261 (LATIN SMALL LETTER A WITH OGONEK) 731 (OGONEK)
262 (LATIN CAPITAL LETTER C WITH ACUTE) 733 (DOUBLE ACUTE ACCENT)
263 (LATIN SMALL LETTER C WITH ACUTE) 900 (GREEK TONOS)
264 (LATIN CAPITAL LETTER C WITH CIRCUMFLEX) 901 (GREEK DIALYTIKA TONOS)
265 (LATIN SMALL LETTER C WITH CIRCUMFLEX) 902 (GREEK CAPITAL LETTER ALPHA WITH TONOS)
266 (LATIN CAPITAL LETTER C WITH DOT ABOVE) 904 (GREEK CAPITAL LETTER EPSILON WITH TONOS)
267 (LATIN SMALL LETTER C WITH DOT ABOVE) 905 (GREEK CAPITAL LETTER ETA WITH TONOS)
268 (LATIN CAPITAL LETTER C WITH CARON) 906 (GREEK CAPITAL LETTER IOTA WITH TONOS)
269 (LATIN SMALL LETTER C WITH CARON) 908 (GREEK CAPITAL LETTER OMICRON WITH TONOS)
270 (LATIN CAPITAL LETTER D WITH CARON) 910 (GREEK CAPITAL LETTER UPSILON WITH TONOS)
271 (LATIN SMALL LETTER D WITH CARON) 911 (GREEK CAPITAL LETTER OMEGA WITH TONOS)
272 (LATIN CAPITAL LETTER D WITH STROKE) 912 (GREEK SMALL LETTER IOTA WITH DIALYTIKA AND
TONOS)
273 (LATIN SMALL LETTER D WITH STROKE) 938 (GREEK CAPITAL LETTER IOTA WITH DIALYTIKA)
274 (LATIN CAPITAL LETTER E WITH MACRON) 939 (GREEK CAPITAL LETTER UPSILON WITH
DIALYTIKA)
275 (LATIN SMALL LETTER E WITH MACRON) 940 (GREEK SMALL LETTER ALPHA WITH TONOS)
278 (LATIN CAPITAL LETTER E WITH DOT ABOVE) 941 (GREEK SMALL LETTER EPSILON WITH TONOS)
279 (LATIN SMALL LETTER E WITH DOT ABOVE) 942 (GREEK SMALL LETTER ETA WITH TONOS)
280 (LATIN CAPITAL LETTER E WITH OGONEK) 943 (GREEK SMALL LETTER IOTA WITH TONOS)
281 (LATIN SMALL LETTER E WITH OGONEK) 944 (GREEK SMALL LETTER UPSILON WITH DIALYTIKA
AND TONOS)
282 (LATIN CAPITAL LETTER E WITH CARON) 962 (GREEK SMALL LETTER FINAL SIGMA)
283 (LATIN SMALL LETTER E WITH CARON) 970 (GREEK SMALL LETTER IOTA WITH DIALYTIKA)
284 (LATIN CAPITAL LETTER G WITH CIRCUMFLEX) 971 (GREEK SMALL LETTER UPSILON WITH DIALYTIKA)
285 (LATIN SMALL LETTER G WITH CIRCUMFLEX) 972 (GREEK SMALL LETTER OMICRON WITH TONOS)
286 (LATIN CAPITAL LETTER G WITH BREVE) 973 (GREEK SMALL LETTER UPSILON WITH TONOS)
287 (LATIN SMALL LETTER G WITH BREVE) 974 (GREEK SMALL LETTER OMEGA WITH TONOS)
288 (LATIN CAPITAL LETTER G WITH DOT ABOVE) 1026 (CYRILLIC CAPITAL LETTER DJE)
289 (LATIN SMALL LETTER G WITH DOT ABOVE) 1027 (CYRILLIC CAPITAL LETTER GJE)
290 (LATIN CAPITAL LETTER G WITH CEDILLA) 1028 (CYRILLIC CAPITAL LETTER UKRAINIAN IE)
292 (LATIN CAPITAL LETTER H WITH CIRCUMFLEX) 1029 (CYRILLIC CAPITAL LETTER DZE)
293 (LATIN SMALL LETTER H WITH CIRCUMFLEX) 1030 (CYRILLIC CAPITAL LETTER BYELORUSSIAN-
UKRAINIAN I)
294 (LATIN CAPITAL LETTER H WITH STROKE) 1031 (CYRILLIC CAPITAL LETTER YI)
295 (LATIN SMALL LETTER H WITH STROKE) 1032 (CYRILLIC CAPITAL LETTER JE)
296 (LATIN CAPITAL LETTER I WITH TILDE) 1033 (CYRILLIC CAPITAL LETTER LJE)
297 (LATIN SMALL LETTER I WITH TILDE) 1034 (CYRILLIC CAPITAL LETTER NJE)
298 (LATIN CAPITAL LETTER I WITH MACRON) 1035 (CYRILLIC CAPITAL LETTER TSHE)
299 (LATIN SMALL LETTER I WITH MACRON) 1036 (CYRILLIC CAPITAL LETTER KJE)
302 (LATIN CAPITAL LETTER I WITH OGONEK) 1038 (CYRILLIC CAPITAL LETTER SHORT U)
303 (LATIN SMALL LETTER I WITH OGONEK) 1039 (CYRILLIC CAPITAL LETTER DZHE)
304 (LATIN CAPITAL LETTER I WITH DOT ABOVE) 1106 (CYRILLIC SMALL LETTER DJE)
305 (LATIN SMALL LETTER DOTLESS I) 1107 (CYRILLIC SMALL LETTER GJE)
306 (LATIN CAPITAL LIGATURE IJ) 1108 (CYRILLIC SMALL LETTER UKRAINIAN IE)
307 (LATIN SMALL LIGATURE IJ) 1109 (CYRILLIC SMALL LETTER DZE)
308 (LATIN CAPITAL LETTER J WITH CIRCUMFLEX) 1110 (CYRILLIC SMALL LETTER BYELORUSSIAN-
UKRAINIAN I)
309 (LATIN SMALL LETTER J WITH CIRCUMFLEX) 1111 (CYRILLIC SMALL LETTER YI)
310 (LATIN CAPITAL LETTER K WITH CEDILLA) 1112 (CYRILLIC SMALL LETTER JE)
311 (LATIN SMALL LETTER K WITH CEDILLA) 1113 (CYRILLIC SMALL LETTER LJE)
312 (LATIN SMALL LETTER KRA) 1114 (CYRILLIC SMALL LETTER NJE)
313 (LATIN CAPITAL LETTER L WITH ACUTE) 1115 (CYRILLIC SMALL LETTER TSHE)
314 (LATIN SMALL LETTER L WITH ACUTE) 1116 (CYRILLIC SMALL LETTER KJE)
315 (LATIN CAPITAL LETTER L WITH CEDILLA) 1118 (CYRILLIC SMALL LETTER SHORT U)
316 (LATIN SMALL LETTER L WITH CEDILLA) 1119 (CYRILLIC SMALL LETTER DZHE)
317 (LATIN CAPITAL LETTER L WITH CARON) 8214 (DOUBLE VERTICAL LINE)
318 (LATIN SMALL LETTER L WITH CARON) 8482 (TRADE MARK SIGN)
319 (LATIN CAPITAL LETTER L WITH MIDDLE DOT) 8722 (MINUS SIGN)
320 (LATIN SMALL LETTER L WITH MIDDLE DOT) 12316 (WAVE DASH)
321 (LATIN CAPITAL LETTER L WITH STROKE) 40869 (<CJK Ideograph Last>)
322 (LATIN SMALL LETTER L WITH STROKE)
Converting from IBM EBCDIC Japanese to JapanEUC
EBCDIC Japanese to JapanEUC:
Table A-12. IBM EBCDIC Japanese to JapanEUC Character Conversion
Characters lost when converting from IBM930 (IBM EBCDIC Japanese) to JapanEUC
128 (<control character>) 8562 (SMALL ROMAN NUMERAL THREE)
129 (<control character>) 8563 (SMALL ROMAN NUMERAL FOUR)
130 (<control character>) 8564 (SMALL ROMAN NUMERAL FIVE)
131 (<control character>) 8565 (SMALL ROMAN NUMERAL SIX)
132 (<control character>) 8566 (SMALL ROMAN NUMERAL SEVEN)
133 (<control character>) 8567 (SMALL ROMAN NUMERAL EIGHT)
134 (<control character>) 8568 (SMALL ROMAN NUMERAL NINE)
135 (<control character>) 8569 (SMALL ROMAN NUMERAL TEN)
136 (<control character>) 12849 (PARENTHESIZED IDEOGRAPH STOCK)
137 (<control character>) 57344 (<Private Use First>)
138 (<control character>) 63785 (CJK COMPATIBILITY IDEOGRAPH-F929)
139 (<control character>) 63964 (CJK COMPATIBILITY IDEOGRAPH-F9DC)
140 (<control character>) 64015 (CJK COMPATIBILITY IDEOGRAPH-FA0F)
141 (<control character>) 64016 (CJK COMPATIBILITY IDEOGRAPH-FA10)
150 (<control character>) 64026 (CJK COMPATIBILITY IDEOGRAPH-FA1A)
151 (<control character>) 64027 (CJK COMPATIBILITY IDEOGRAPH-FA1B)
152 (<control character>) 64028 (CJK COMPATIBILITY IDEOGRAPH-FA1C)
153 (<control character>) 64029 (CJK COMPATIBILITY IDEOGRAPH-FA1D)
154 (<control character>) 64030 (CJK COMPATIBILITY IDEOGRAPH-FA1E)
155 (<control character>) 64031 (CJK COMPATIBILITY IDEOGRAPH-FA1F)
Converting from JapanEUC to IBM EBCDIC Japanese
Table A-13 lists all characters by character ID and description that do not convert from
JapanEUC to IBM EBCDIC Japanese:
165 (YEN SIGN) 64036 (CJK COMPATIBILITY IDEOGRAPH-FA24)
8212 (EM DASH) 64037 (CJK COMPATIBILITY IDEOGRAPH-FA25)
8254 (OVERLINE) 64038 (CJK COMPATIBILITY IDEOGRAPH-FA26)
8481 (TELEPHONE SIGN) 64039 (CJK COMPATIBILITY IDEOGRAPH-FA27)
8544 (ROMAN NUMERAL ONE) 64040 (CJK COMPATIBILITY IDEOGRAPH-FA28)
8545 (ROMAN NUMERAL TWO) 64041 (CJK COMPATIBILITY IDEOGRAPH-FA29)
8546 (ROMAN NUMERAL THREE) 64042 (CJK COMPATIBILITY IDEOGRAPH-FA2A)
8547 (ROMAN NUMERAL FOUR) 64043 (CJK COMPATIBILITY IDEOGRAPH-FA2B)
8548 (ROMAN NUMERAL FIVE) 64044 (CJK COMPATIBILITY IDEOGRAPH-FA2C)
8549 (ROMAN NUMERAL SIX) 64045 (CJK COMPATIBILITY IDEOGRAPH-FA2D)
8550 (ROMAN NUMERAL SEVEN) 65282 (FULLWIDTH QUOTATION MARK)
8551 (ROMAN NUMERAL EIGHT) 65287 (FULLWIDTH APOSTROPHE)
8552 (ROMAN NUMERAL NINE) 65504 (FULLWIDTH CENT SIGN)
8553 (ROMAN NUMERAL TEN) 65505 (FULLWIDTH POUND SIGN)
8560 (SMALL ROMAN NUMERAL ONE) 65506 (FULLWIDTH NOT SIGN)
8561 (SMALL ROMAN NUMERAL TWO)
Table A-13. JapanEUC to IBM EBCDIC Japanese Character Conversion
Characters lost when converting from JapanEUC to IBM930 (IBM EBCDIC Japanese)
161 (INVERTED EXCLAMATION MARK) 325 (LATIN CAPITAL LETTER N WITH CEDILLA)
164 (CURRENCY SIGN) 326 (LATIN SMALL LETTER N WITH CEDILLA)
169 (COPYRIGHT SIGN) 327 (LATIN CAPITAL LETTER N WITH CARON)
170 (FEMININE ORDINAL INDICATOR) 328 (LATIN SMALL LETTER N WITH CARON)
Table A-12. IBM EBCDIC Japanese to JapanEUC Character Conversion
Characters lost when converting from IBM930 (IBM EBCDIC Japanese) to JapanEUC
174 (REGISTERED SIGN) 329 (LATIN SMALL LETTER N PRECEDED BY
APOSTROPHE)
175 (MACRON) 330 (LATIN CAPITAL LETTER ENG)
184 (CEDILLA) 331 (LATIN SMALL LETTER ENG)
186 (MASCULINE ORDINAL INDICATOR) 332 (LATIN CAPITAL LETTER O WITH MACRON)
191 (INVERTED QUESTION MARK) 333 (LATIN SMALL LETTER O WITH MACRON)
192 (LATIN CAPITAL LETTER A WITH GRAVE) 336 (LATIN CAPITAL LETTER O WITH DOUBLE ACUTE)
193 (LATIN CAPITAL LETTER A WITH ACUTE) 337 (LATIN SMALL LETTER O WITH DOUBLE ACUTE)
194 (LATIN CAPITAL LETTER A WITH CIRCUMFLEX) 338 (LATIN CAPITAL LIGATURE OE)
195 (LATIN CAPITAL LETTER A WITH TILDE) 339 (LATIN SMALL LIGATURE OE)
196 (LATIN CAPITAL LETTER A WITH DIAERESIS) 340 (LATIN CAPITAL LETTER R WITH ACUTE)
197 (LATIN CAPITAL LETTER A WITH RING ABOVE) 341 (LATIN SMALL LETTER R WITH ACUTE)
198 (LATIN CAPITAL LETTER AE) 342 (LATIN CAPITAL LETTER R WITH CEDILLA)
199 (LATIN CAPITAL LETTER C WITH CEDILLA) 343 (LATIN SMALL LETTER R WITH CEDILLA)
200 (LATIN CAPITAL LETTER E WITH GRAVE) 344 (LATIN CAPITAL LETTER R WITH CARON)
201 (LATIN CAPITAL LETTER E WITH ACUTE) 345 (LATIN SMALL LETTER R WITH CARON)
202 (LATIN CAPITAL LETTER E WITH CIRCUMFLEX) 346 (LATIN CAPITAL LETTER S WITH ACUTE)
203 (LATIN CAPITAL LETTER E WITH DIAERESIS) 347 (LATIN SMALL LETTER S WITH ACUTE)
204 (LATIN CAPITAL LETTER I WITH GRAVE) 348 (LATIN CAPITAL LETTER S WITH CIRCUMFLEX)
205 (LATIN CAPITAL LETTER I WITH ACUTE) 349 (LATIN SMALL LETTER S WITH CIRCUMFLEX)
206 (LATIN CAPITAL LETTER I WITH CIRCUMFLEX) 350 (LATIN CAPITAL LETTER S WITH CEDILLA)
207 (LATIN CAPITAL LETTER I WITH DIAERESIS) 351 (LATIN SMALL LETTER S WITH CEDILLA)
209 (LATIN CAPITAL LETTER N WITH TILDE) 352 (LATIN CAPITAL LETTER S WITH CARON)
210 (LATIN CAPITAL LETTER O WITH GRAVE) 353 (LATIN SMALL LETTER S WITH CARON)
211 (LATIN CAPITAL LETTER O WITH ACUTE) 354 (LATIN CAPITAL LETTER T WITH CEDILLA)
212 (LATIN CAPITAL LETTER O WITH CIRCUMFLEX) 355 (LATIN SMALL LETTER T WITH CEDILLA)
213 (LATIN CAPITAL LETTER O WITH TILDE) 356 (LATIN CAPITAL LETTER T WITH CARON)
214 (LATIN CAPITAL LETTER O WITH DIAERESIS) 357 (LATIN SMALL LETTER T WITH CARON)
216 (LATIN CAPITAL LETTER O WITH STROKE) 358 (LATIN CAPITAL LETTER T WITH STROKE)
217 (LATIN CAPITAL LETTER U WITH GRAVE) 359 (LATIN SMALL LETTER T WITH STROKE)
218 (LATIN CAPITAL LETTER U WITH ACUTE) 360 (LATIN CAPITAL LETTER U WITH TILDE)
219 (LATIN CAPITAL LETTER U WITH CIRCUMFLEX) 361 (LATIN SMALL LETTER U WITH TILDE)
220 (LATIN CAPITAL LETTER U WITH DIAERESIS) 362 (LATIN CAPITAL LETTER U WITH MACRON)
221 (LATIN CAPITAL LETTER Y WITH ACUTE) 363 (LATIN SMALL LETTER U WITH MACRON)
222 (LATIN CAPITAL LETTER THORN) 364 (LATIN CAPITAL LETTER U WITH BREVE)
223 (LATIN SMALL LETTER SHARP S) 365 (LATIN SMALL LETTER U WITH BREVE)
224 (LATIN SMALL LETTER A WITH GRAVE) 366 (LATIN CAPITAL LETTER U WITH RING ABOVE)
225 (LATIN SMALL LETTER A WITH ACUTE) 367 (LATIN SMALL LETTER U WITH RING ABOVE)
226 (LATIN SMALL LETTER A WITH CIRCUMFLEX) 368 (LATIN CAPITAL LETTER U WITH DOUBLE ACUTE)
227 (LATIN SMALL LETTER A WITH TILDE) 369 (LATIN SMALL LETTER U WITH DOUBLE ACUTE)
228 (LATIN SMALL LETTER A WITH DIAERESIS) 370 (LATIN CAPITAL LETTER U WITH OGONEK)
229 (LATIN SMALL LETTER A WITH RING ABOVE) 371 (LATIN SMALL LETTER U WITH OGONEK)
230 (LATIN SMALL LETTER AE) 372 (LATIN CAPITAL LETTER W WITH CIRCUMFLEX)
231 (LATIN SMALL LETTER C WITH CEDILLA) 373 (LATIN SMALL LETTER W WITH CIRCUMFLEX)
232 (LATIN SMALL LETTER E WITH GRAVE) 374 (LATIN CAPITAL LETTER Y WITH CIRCUMFLEX)
233 (LATIN SMALL LETTER E WITH ACUTE) 375 (LATIN SMALL LETTER Y WITH CIRCUMFLEX)
234 (LATIN SMALL LETTER E WITH CIRCUMFLEX) 376 (LATIN CAPITAL LETTER Y WITH DIAERESIS)
235 (LATIN SMALL LETTER E WITH DIAERESIS) 377 (LATIN CAPITAL LETTER Z WITH ACUTE)
236 (LATIN SMALL LETTER I WITH GRAVE) 378 (LATIN SMALL LETTER Z WITH ACUTE)
237 (LATIN SMALL LETTER I WITH ACUTE) 379 (LATIN CAPITAL LETTER Z WITH DOT ABOVE)
238 (LATIN SMALL LETTER I WITH CIRCUMFLEX) 380 (LATIN SMALL LETTER Z WITH DOT ABOVE)
239 (LATIN SMALL LETTER I WITH DIAERESIS) 381 (LATIN CAPITAL LETTER Z WITH CARON)
240 (LATIN SMALL LETTER ETH) 382 (LATIN SMALL LETTER Z WITH CARON)
241 (LATIN SMALL LETTER N WITH TILDE) 461 (LATIN CAPITAL LETTER A WITH CARON)
242 (LATIN SMALL LETTER O WITH GRAVE) 462 (LATIN SMALL LETTER A WITH CARON)
243 (LATIN SMALL LETTER O WITH ACUTE) 463 (LATIN CAPITAL LETTER I WITH CARON)
244 (LATIN SMALL LETTER O WITH CIRCUMFLEX) 464 (LATIN SMALL LETTER I WITH CARON)
245 (LATIN SMALL LETTER O WITH TILDE) 465 (LATIN CAPITAL LETTER O WITH CARON)
246 (LATIN SMALL LETTER O WITH DIAERESIS) 466 (LATIN SMALL LETTER O WITH CARON)
248 (LATIN SMALL LETTER O WITH STROKE) 467 (LATIN CAPITAL LETTER U WITH CARON)
249 (LATIN SMALL LETTER U WITH GRAVE) 468 (LATIN SMALL LETTER U WITH CARON)
250 (LATIN SMALL LETTER U WITH ACUTE) 469 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
MACRON)
251 (LATIN SMALL LETTER U WITH CIRCUMFLEX) 470 (LATIN SMALL LETTER U WITH DIAERESIS AND
MACRON)
252 (LATIN SMALL LETTER U WITH DIAERESIS) 471 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
ACUTE)
253 (LATIN SMALL LETTER Y WITH ACUTE) 472 (LATIN SMALL LETTER U WITH DIAERESIS AND
ACUTE)
254 (LATIN SMALL LETTER THORN) 473 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
CARON)
255 (LATIN SMALL LETTER Y WITH DIAERESIS) 474 (LATIN SMALL LETTER U WITH DIAERESIS AND
CARON)
256 (LATIN CAPITAL LETTER A WITH MACRON) 475 (LATIN CAPITAL LETTER U WITH DIAERESIS AND
GRAVE)
257 (LATIN SMALL LETTER A WITH MACRON) 476 (LATIN SMALL LETTER U WITH DIAERESIS AND
GRAVE)
258 (LATIN CAPITAL LETTER A WITH BREVE) 501 (LATIN SMALL LETTER G WITH ACUTE)
259 (LATIN SMALL LETTER A WITH BREVE) 711 (CARON)
260 (LATIN CAPITAL LETTER A WITH OGONEK) 728 (BREVE)
261 (LATIN SMALL LETTER A WITH OGONEK) 729 (DOT ABOVE)
262 (LATIN CAPITAL LETTER C WITH ACUTE) 730 (RING ABOVE)
263 (LATIN SMALL LETTER C WITH ACUTE) 731 (OGONEK)
264 (LATIN CAPITAL LETTER C WITH CIRCUMFLEX) 733 (DOUBLE ACUTE ACCENT)
265 (LATIN SMALL LETTER C WITH CIRCUMFLEX) 900 (GREEK TONOS)
266 (LATIN CAPITAL LETTER C WITH DOT ABOVE) 901 (GREEK DIALYTIKA TONOS)
267 (LATIN SMALL LETTER C WITH DOT ABOVE) 902 (GREEK CAPITAL LETTER ALPHA WITH TONOS)
268 (LATIN CAPITAL LETTER C WITH CARON) 904 (GREEK CAPITAL LETTER EPSILON WITH TONOS)
269 (LATIN SMALL LETTER C WITH CARON) 905 (GREEK CAPITAL LETTER ETA WITH TONOS)
270 (LATIN CAPITAL LETTER D WITH CARON) 906 (GREEK CAPITAL LETTER IOTA WITH TONOS)
271 (LATIN SMALL LETTER D WITH CARON) 908 (GREEK CAPITAL LETTER OMICRON WITH TONOS)
272 (LATIN CAPITAL LETTER D WITH STROKE) 910 (GREEK CAPITAL LETTER UPSILON WITH TONOS)
273 (LATIN SMALL LETTER D WITH STROKE) 911 (GREEK CAPITAL LETTER OMEGA WITH TONOS)
274 (LATIN CAPITAL LETTER E WITH MACRON) 912 (GREEK SMALL LETTER IOTA WITH DIALYTIKA AND
TONOS)
275 (LATIN SMALL LETTER E WITH MACRON) 938 (GREEK CAPITAL LETTER IOTA WITH DIALYTIKA)
278 (LATIN CAPITAL LETTER E WITH DOT ABOVE) 939 (GREEK CAPITAL LETTER UPSILON WITH
DIALYTIKA)
279 (LATIN SMALL LETTER E WITH DOT ABOVE) 940 (GREEK SMALL LETTER ALPHA WITH TONOS)
280 (LATIN CAPITAL LETTER E WITH OGONEK) 941 (GREEK SMALL LETTER EPSILON WITH TONOS)
281 (LATIN SMALL LETTER E WITH OGONEK) 942 (GREEK SMALL LETTER ETA WITH TONOS)
282 (LATIN CAPITAL LETTER E WITH CARON) 943 (GREEK SMALL LETTER IOTA WITH TONOS)
283 (LATIN SMALL LETTER E WITH CARON) 944 (GREEK SMALL LETTER UPSILON WITH DIALYTIKA
AND TONOS)
284 (LATIN CAPITAL LETTER G WITH CIRCUMFLEX) 962 (GREEK SMALL LETTER FINAL SIGMA)
285 (LATIN SMALL LETTER G WITH CIRCUMFLEX) 970 (GREEK SMALL LETTER IOTA WITH DIALYTIKA)
286 (LATIN CAPITAL LETTER G WITH BREVE) 971 (GREEK SMALL LETTER UPSILON WITH DIALYTIKA)
287 (LATIN SMALL LETTER G WITH BREVE) 972 (GREEK SMALL LETTER OMICRON WITH TONOS)
288 (LATIN CAPITAL LETTER G WITH DOT ABOVE) 973 (GREEK SMALL LETTER UPSILON WITH TONOS)
289 (LATIN SMALL LETTER G WITH DOT ABOVE) 974 (GREEK SMALL LETTER OMEGA WITH TONOS)
290 (LATIN CAPITAL LETTER G WITH CEDILLA) 1026 (CYRILLIC CAPITAL LETTER DJE)
292 (LATIN CAPITAL LETTER H WITH CIRCUMFLEX) 1027 (CYRILLIC CAPITAL LETTER GJE)
293 (LATIN SMALL LETTER H WITH CIRCUMFLEX) 1028 (CYRILLIC CAPITAL LETTER UKRAINIAN IE)
294 (LATIN CAPITAL LETTER H WITH STROKE) 1029 (CYRILLIC CAPITAL LETTER DZE)
295 (LATIN SMALL LETTER H WITH STROKE) 1030 (CYRILLIC CAPITAL LETTER BYELORUSSIAN-
UKRAINIAN I)
296 (LATIN CAPITAL LETTER I WITH TILDE) 1031 (CYRILLIC CAPITAL LETTER YI)
297 (LATIN SMALL LETTER I WITH TILDE) 1032 (CYRILLIC CAPITAL LETTER JE)
298 (LATIN CAPITAL LETTER I WITH MACRON) 1033 (CYRILLIC CAPITAL LETTER LJE)
299 (LATIN SMALL LETTER I WITH MACRON) 1034 (CYRILLIC CAPITAL LETTER NJE)
302 (LATIN CAPITAL LETTER I WITH OGONEK) 1035 (CYRILLIC CAPITAL LETTER TSHE)
303 (LATIN SMALL LETTER I WITH OGONEK) 1036 (CYRILLIC CAPITAL LETTER KJE)
304 (LATIN CAPITAL LETTER I WITH DOT ABOVE) 1038 (CYRILLIC CAPITAL LETTER SHORT U)
305 (LATIN SMALL LETTER DOTLESS I) 1039 (CYRILLIC CAPITAL LETTER DZHE)
306 (LATIN CAPITAL LIGATURE IJ) 1106 (CYRILLIC SMALL LETTER DJE)
307 (LATIN SMALL LIGATURE IJ) 1107 (CYRILLIC SMALL LETTER GJE)
308 (LATIN CAPITAL LETTER J WITH CIRCUMFLEX) 1108 (CYRILLIC SMALL LETTER UKRAINIAN IE)
309 (LATIN SMALL LETTER J WITH CIRCUMFLEX) 1109 (CYRILLIC SMALL LETTER DZE)
Converting from IBM EBCDIC Japanese to MS Shift JIS
EBCDIC Japanese to MS Shift JIS:
310 (LATIN CAPITAL LETTER K WITH CEDILLA) 1110 (CYRILLIC SMALL LETTER BYELORUSSIAN-
UKRAINIAN I)
311 (LATIN SMALL LETTER K WITH CEDILLA) 1111 (CYRILLIC SMALL LETTER YI)
312 (LATIN SMALL LETTER KRA) 1112 (CYRILLIC SMALL LETTER JE)
313 (LATIN CAPITAL LETTER L WITH ACUTE) 1113 (CYRILLIC SMALL LETTER LJE)
314 (LATIN SMALL LETTER L WITH ACUTE) 1114 (CYRILLIC SMALL LETTER NJE)
315 (LATIN CAPITAL LETTER L WITH CEDILLA) 1115 (CYRILLIC SMALL LETTER TSHE)
316 (LATIN SMALL LETTER L WITH CEDILLA) 1116 (CYRILLIC SMALL LETTER KJE)
317 (LATIN CAPITAL LETTER L WITH CARON) 1118 (CYRILLIC SMALL LETTER SHORT U)
318 (LATIN SMALL LETTER L WITH CARON) 1119 (CYRILLIC SMALL LETTER DZHE)
319 (LATIN CAPITAL LETTER L WITH MIDDLE DOT) 8213 (HORIZONTAL BAR)
320 (LATIN SMALL LETTER L WITH MIDDLE DOT) 8470 (NUMERO SIGN)
321 (LATIN CAPITAL LETTER L WITH STROKE) 8482 (TRADE MARK SIGN)
322 (LATIN SMALL LETTER L WITH STROKE) 40869 (<CJK Ideograph Last>)
323 (LATIN CAPITAL LETTER N WITH ACUTE) 65374 (FULLWIDTH TILDE)
324 (LATIN SMALL LETTER N WITH ACUTE)
Table A-14. IBM EBCDIC Japanese to MS Shift JIS Character Conversion
Characters lost when converting from IBM930 (IBM EBCDIC Japanese) to MS932 (MS Shift JIS)
Converting from MS Shift JIS to IBM EBCDIC Japanese
Shift JIS to IBM EBCDIC Japanese:
138 (<control character>) 162 (CENT SIGN)
139 (<control character>) 163 (POUND SIGN)
140 (<control character>) 165 (YEN SIGN)
141 (<control character>) 166 (BROKEN BAR)
142 (<control character>) 172 (NOT SIGN)
143 (<control character>) 8212 (EM DASH)
144 (<control character>) 8214 (DOUBLE VERTICAL LINE)
145 (<control character>) 8254 (OVERLINE)
146 (<control character>) 8722 (MINUS SIGN)
147 (<control character>) 12316 (WAVE DASH)
148 (<control character>) 57344 (<Private Use First>)
149 (<control character>)
Table A-15. MS Shift JIS to IBM EBCDIC Japanese Character Conversion
Characters lost when converting from MS932 (MS Shift JIS) to IBM930 (IBM EBCDIC Japanese)
8213 (HORIZONTAL BAR) 12968 (CIRCLED IDEOGRAPH RIGHT)
8470 (NUMERO SIGN) 13059 (SQUARE AARU)
8721 (N-ARY SUMMATION) 13069 (SQUARE KARORII)
8735 (RIGHT ANGLE) 13076 (SQUARE KIRO)
8741 (PARALLEL TO) 13080 (SQUARE GURAMU)
8750 (CONTOUR INTEGRAL) 13090 (SQUARE SENTI)
8895 (RIGHT TRIANGLE) 13091 (SQUARE SENTO)
9312 (CIRCLED DIGIT ONE) 13094 (SQUARE DORU)
9313 (CIRCLED DIGIT TWO) 13095 (SQUARE TON)
9314 (CIRCLED DIGIT THREE) 13099 (SQUARE PAASENTO)
9315 (CIRCLED DIGIT FOUR) 13110 (SQUARE HEKUTAARU)
9316 (CIRCLED DIGIT FIVE) 13115 (SQUARE PEEZI)
Table A-14. IBM EBCDIC Japanese to MS Shift JIS Character Conversion
Characters lost when converting from IBM930 (IBM EBCDIC Japanese) to MS932 (MS Shift JIS)
9317 (CIRCLED DIGIT SIX) 13129 (SQUARE MIRI)
9318 (CIRCLED DIGIT SEVEN) 13130 (SQUARE MIRIBAARU)
9319 (CIRCLED DIGIT EIGHT) 13133 (SQUARE MEETORU)
9320 (CIRCLED DIGIT NINE) 13137 (SQUARE RITTORU)
9321 (CIRCLED NUMBER TEN) 13143 (SQUARE WATTO)
9322 (CIRCLED NUMBER ELEVEN) 13179 (SQUARE ERA NAME HEISEI)
9323 (CIRCLED NUMBER TWELVE) 13180 (SQUARE ERA NAME SYOUWA)
9324 (CIRCLED NUMBER THIRTEEN) 13181 (SQUARE ERA NAME TAISYOU)
9325 (CIRCLED NUMBER FOURTEEN) 13182 (SQUARE ERA NAME MEIZI)
9326 (CIRCLED NUMBER FIFTEEN) 13198 (SQUARE MG)
9327 (CIRCLED NUMBER SIXTEEN) 13199 (SQUARE KG)
9328 (CIRCLED NUMBER SEVENTEEN) 13212 (SQUARE MM)
9329 (CIRCLED NUMBER EIGHTEEN) 13213 (SQUARE CM)
9330 (CIRCLED NUMBER NINETEEN) 13214 (SQUARE KM)
9331 (CIRCLED NUMBER TWENTY) 13217 (SQUARE M SQUARED)
12317 (REVERSED DOUBLE PRIME QUOTATION MARK) 13252 (SQUARE CC)
12319 (LOW DOUBLE PRIME QUOTATION MARK) 13261 (SQUARE KK)
12850 (PARENTHESIZED IDEOGRAPH HAVE) 64014 (CJK COMPATIBILITY IDEOGRAPH-FA0E)
12857 (PARENTHESIZED IDEOGRAPH REPRESENT) 64017 (CJK COMPATIBILITY IDEOGRAPH-FA11)
12964 (CIRCLED IDEOGRAPH HIGH) 65293 (FULLWIDTH HYPHEN-MINUS)
12965 (CIRCLED IDEOGRAPH CENTRE) 65374 (FULLWIDTH TILDE)
12966 (CIRCLED IDEOGRAPH LOW) 65508 (FULLWIDTH BROKEN BAR)
12967 (CIRCLED IDEOGRAPH LEFT)
Table A-15. MS Shift JIS to IBM EBCDIC Japanese Character Conversion
Characters lost when converting from MS932 (MS Shift JIS) to IBM930 (IBM EBCDIC Japanese)
245
I n d e x
A
Access97
See Microsoft Access97
Aggregate treat nulls as zero
setting on UNIX 165
setting on Windows 136
Aggregate treat rows as insert
setting on UNIX 165
Aggregator transformation
setting up for prior version compatibility 136, 165
treating nulls as zero 136, 165
treating rows as insert 136, 165
AIX
shared library environment variable 105, 167
ANSI code page (Windows)
definition 37
Application sources
code page 42
Application targets
code page 42
ASCII
8-bit ASCII 33
See also Unicode mode
overview 33
setting ASCII data movement mode on UNIX 163
setting ASCII data movement mode on Windows 138
B
backup domain controller
Informatica Server installation guidelines 127
C
Character data sets
See also Designer Guide
handling options for Microsoft SQL Server and
PeopleSoft on Oracle 137
character sizes
double byte 38
multibyte 38
single byte 38
client tools
See Informatica Client
COBOL
connectivity 24
code page relaxation
configuring the Informatica Server 48
Informatica Server validation 48
code pages
advanced external procedure 41
ANSI (Windows) 37
Application sources 42, 214
Application targets 42
character loss during conversions 224
246 Index
choosing 38
compatibility 216
compatibility between components 215
compatibility diagram 43
compatibility overview 38
configuring UNIX Server 158
configuring Windows Server 126
converting from IBM EBCDIC Japanese to JapanEUC
235
converting from IBM EBCDIC Japanese to MS Shift
JIS 241
converting from IBM EBCDIC US English to Latin1
226
converting from JapanEUC to IBM EBCDIC Japanese
236
converting from JapanEUC to MS Shift JIS 230
converting from Latin1 to IBM EBCDIC US English
227
converting from Latin1 to MS Latin1 225
converting from MS Latin1 to Latin1 225
converting from MS Shift JIS to IBM EBCDIC
Japanese 242
converting from MS Shift JIS to JapanEUC 227
external procedure 41
flat file sources 40, 42, 214
flat file targets 40, 42, 214
global repository 214
Informatica Client 40, 215
Informatica Server 40, 41, 185, 214
list of available code pages 208
local repository 214
lookup database 41
OEM code page (Windows) 37
overview 36
pmcmd 41, 215
reference 210
related languages 210
related sort orders 210
related territories 210
relational sources 40, 42, 214
relational targets 40, 42, 214
relaxed validation for sources and targets 48
repository 40, 42, 215
sort order overview 41
stored procedure database 41
subsets defined 214
supersets defined 214
supported code pages 208
UNIX 36
verifying compatibility 217
Windows 37
compatibility
between code pages 38, 216
configuring
Informatica Server (UNIX) 162
Informatica Server (Windows) 131
ODBC data sources 204
connect string
examples 23
syntax 23
connecting
Informatica Client to IBM DB2 74
Informatica Client to Informix 72, 76, 147
Informatica Client to Microsoft Access97 75
Informatica Client to Microsoft Excel 75
Informatica Client to Microsoft SQL Server 70
Informatica Client to Oracle 69
Informatica Client to Sybase SQL Server 71
Informatica Client to Teradata 76
Informatica Server to IBM DB2 (UNIX) 172
Informatica Server to IBM DB2 (Windows) 144
Informatica Server to Informix (UNIX) 171
Informatica Server to Informix (Windows) 143
Informatica Server to Microsoft Access97 145
Informatica Server to Microsoft Excel 146
Informatica Server to Microsoft SQL Server 141
Informatica Server to ODBC data sources (UNIX) 178
Informatica Server to Oracle (UNIX) 168
Informatica Server to Oracle (Windows) 140
Informatica Server to Sybase SQL Server (UNIX) 170
Informatica Server to Sybase SQL Server (Windows)
142
Informatica Server to Teradata 147
Repository Server to IBM DB2 (UNIX) 110
Repository Server to IBM DB2 (Windows) 89
Repository Server to Informix (UNIX) 109
Repository Server to Informix (Windows) 87
Repository Server to Microsoft SQL Server 86
Repository Server to Oracle (UNIX) 106
Repository Server to Oracle (Windows) 85
Repository Server to Sybase SQL Server (Windows) 87
to UNIX databases 167
to Windows databases 140
connections
TCP/IP 185
connectivity
COBOL 24
connect string examples 23
diagram of 21
Informatica Client 21
native drivers 23
overview 5, 21
Index 247
conversions
IBM EBCDIC Japanese to JapanEUC code pages 235
IBM EBCDIC Japanese to MS Shift JIS code pages
241
IBM EBCDIC US English to Latin1 code pages 226
JapanEUC to IBM EBCDIC Japanese code pages 236
JapanEUC to MS Shift JIS code pages 230
Latin1 to IBM EBCDIC US English code pages 227
Latin1 to MS Latin1 code pages 225
MS Latin1 to Latin1 code pages 225
MS Shift JIS to IBM EBCDIC Japanese code pages
242
MS Shift JIS to JapanEUC code pages 227
Create Indicator Files
setting on UNIX 165
creating
repositories 117
D
data movement mode
changing 34
setting on UNIX 163
databases
connecting to (UNIX) 167
connecting to (Windows) 140
connecting to IBM DB2 74, 89, 110, 144, 172
connecting to Informix 72, 87, 109, 143, 171
connecting to Microsoft Access97 75, 145
connecting to Microsoft Excel 75, 146
connecting to Microsoft SQL Server 70, 86, 141
connecting to Oracle 69, 85, 106, 140, 168
connecting to Sybase SQL Server 71, 87, 108, 142, 170
connecting to Teradata 76, 147
connectivity overview 184
source code page 40
target code page 40
Date Display Format
setting on UNIX 165
Date Handling 4.0 Compatibility
setting on UNIX 165
dates
setting up prior version compatibility (UNIX) 165
setting up prior version compatibility (Windows) 136
DB2
See IBM DB2
DB2 Key
See also IBM DB2
setting on UNIX 164
DB2CODEPAGE
configuring DB2 74
DB2INSTANCE
configuring DB2 74
deadlock retries
setting number of (UNIX) 166
setting number of (Windows) 137
Deadlock Sleep Before Retry
setting on UNIX 166
Debugger
Instance Data window 11
Target Data window 11
Designer
installing 67
Instance Data window 11
Mapping Designer 10
Mapplet Designer 10
Navigator 11
output window 11
overview window 11
Source Analyzer 10
status bar 11
Target Data window 11
Transformation Developer 10
Warehouse Designer 10
workspace 11
DHCP (Dynamic Host Configuration Protocol)
avoiding use with Informatica Server 126, 158
directories
data cache 187
indexes 187
Informatica Server 127, 158
root 187
server defaults 185
server variables 185
documentation
conventions xxiv
description xxi
online xxiii, 67
DSN (data source name)
ODBC data sources
248 Index
E
environment variables
DB2CODEPAGE 74
DB2INSTANCE 74
LANG_C 36
LC_ALL 36
LC_CTYPE 36
LD_LIBRARY_PATH 105, 167
LIBPATH 105, 167
NLS_LANG 59
PM_HOME 162
SHLIB_PATH 105, 160, 167
Error Severity Level
setting on UNIX 164
event logs
filename for 163
Excel
See Microsoft Excel
Export Session Log Lib Name
setting on UNIX 164
external procedures
directory for 127, 158
F
FailSessionIfMaxSessionsReached
setting on UNIX 164
flat files
connectivity 24
directory for targets 128, 159
source code page 40, 42, 214
target code page 40, 42, 214
G
global repositories
code page 214
creating 121
definition 3, 116
promoting 121
globalization
overview 30
H
HP/UX
shared library environment variable 105, 160, 167
I
IBM DB2
Client Configuration Assistant program 74, 89, 145
connect string example 23
connecting to Informatica Client 74
connecting to Informatica Server (UNIX) 172
connecting to Informatica Server (Windows) 144
connecting to Repository Server (UNIX) 110
connecting to Repository Server (Windows) 89
ODBC driver 65
ODBC issues 197
platform key 133, 164
setting DB2CODEPAGE 74, 89, 145
setting DB2INSTANCE 74, 89, 144
indicator files
configuring Informatica Server to create (Windows)
139
Informatica
documentation xxi
Webzine xxv
Informatica Client
See also Informatica Server
code page 40, 215
connecting to databases 69
connectivity requirements 21
installing 67
system requirements 20
Informatica repository
Informatica Server
See also Informatica Client
automatically starting (Windows) 150
changing servers 188
code page 40, 41, 185, 214
configuring (UNIX) 162
configuring (Windows) 131
configuring error severity level (UNIX) 164
configuring export session log lib name (UNIX) 164
configuring fail session if max sessions reached (UNIX)
164
configuring log file name (UNIX) 163
configuring Repository Server host name (UNIX) 163
configuring server name (UNIX) 162
configuring UNIX Server 158
Index 249
configuring Windows Server 126
connectivity overview 184
data movement mode (UNIX) 163
data movement mode (Windows) 138
date display format (UNIX) 165
date display format (Windows) 139
file directories 187
installation guidelines (Windows) 127
installing (Windows) 129
installing multiple (UNIX) 160
registering 185, 187, 188
root directory 187
selecting a code page 185
starting (UNIX) 175
starting from control panel (Windows) 148
stopping (Windows) 150
troubleshooting installation (Windows) 152
user types (Windows) 127
variable directories 127, 158
variables for 185
Informix
connect string syntax 23
connecting to Informatica Client 72, 76, 147
connecting to Repository Server (UNIX) 109
installing Merant ODBC drivers 65
ODBC driver 65
platform key 164
platform key (Windows) 132
SetNet 32 configuration 72, 88, 143
Informix Key
setting on UNIX 164
input locales
configuring 32
installation
minimum system requirements 20
overview 20
steps for upgrade 26
installing
ODBC drivers on Informatica Client 65
ODBC drivers on Informatica Server (UNIX) 177
troubleshooting (Windows) 152
Windows guidelines for 127
Instance Data
window 11
ISO 8859-1
definition 33
K
keys
required to run Informatica Server 132
L
LANG_C environment variable
setting locale in UNIX 36
language
code page reference 210
LC_ALL environment variable
LC_CTYPE environment variable
LD_LIBRARY_PATH
overview 105, 167
LIBPATH 105, 167
Load Manager
Load Manager Allow Debugging (UNIX) 163
Load Manager Shared Memory (UNIX) 163
local repositories
code page 214
definition 3, 116
promoting to global 121
registering multiple servers 184
locales
overview 32
LogFileName
setting on UNIX 163
Lookup databases
setting maximum number of connections (Windows)
137
M
mappings
description 9
process 10
mapplets
description 9
Max Lookup/SP DB Connections
setting on UNIX 166
250 Index
Max MSSQL Connections
setting on UNIX 166
Max Sessions
setting on UNIX 163
Max Sybase Connections
setting on UNIX 166
MBCS (Multibyte Character Set)
definition 33
Merant ODBC drivers
platform-specific drivers required 65, 197
uninstalling 66
metadata
description of Informatica 9
multi-dimensional 9
Metadata Reporter
See Metadata Reporter Guide
Microsoft Access97
connecting to Informatica Server 145
ODBC driver 65
ODBC issues 197
Microsoft Excel
ODBC driver 65
ODBC issues 76, 197
using PmNullPasswd 146
using PmNullUser 146
Microsoft SQL Server
connecting to Repository Server 86
determining code page and sort order 54
Generate Stored Procedure for Prepared Statement
option 71
ODBC driver 65
ODBC issues 71, 197
platform key 132
setting Char handling options 137
setting maximum number of connections (Windows )
137
Microsoft SQL Server Key
MS Exchange Profile
option for post-session email 139
N
native connect string
See connect string
Navigator
overview 11
NLS_LANG
setting locale 59
Number of Deadlock Retries
setting on UNIX 166
O
ODBC
connecting to databases in Informatica Server 196
ODBC (Open Database Connectivity)
See also ODBC calls
See also ODBC data sources
connecting to databases in Informatica Client 196
database-specific notes 197
definition 65
diagram of 194
drivers description 194
drivers for Microsoft Excel 146
installing drivers on Informatica Client 65
installing on Informatica Server (UNIX) 177
Merant driver issues 65, 197
overview 194
platform key 133, 164
requirement for Informatica Client 22
support for MS Excel-compatible drivers 75
uninstalling Merant drivers 66
ODBC Administrator
description 194
ODBC calls
Informatica Server 199
overview 198
ODBC data sources
configuring 204
connecting to (UNIX) 178
creating 201
deleting 205
overview 195
System 195
troubleshooting 206
User 195
ODBC Driver Manager
description 194
Index 251
ODBC Key
OEM code page (Windows)
definition 37
online help
Oracle
changing locale using NLS_LANG 70, 86, 108
displaying non-ASCII characters 70, 78, 86, 108
ODBC driver 65
platform key 164
setting locale with NLS_LANG 59
tips 123
Oracle Key
setting on UNIX 164
Oracle Net Services
using to connect Informatica Client to Oracle 69
using to connect Informatica Server to Oracle (NT)
140
using to connect Informatica Server to Oracle (UNIX)
168
using to connect Repository Server to Oracle (NT) 85
using to connect Repository Server to Oracle (UNIX)
106
P
password
entering repository (UNIX) 163
entering repository (Windows) 135
PeopleSoft on Oracle
setting Char handling options 137
Platform Key
setting on UNIX 164
PM Cache Directory
setting on Unix 163
PM Password
setting on UNIX 163
PM Server 3.X aggregate compatibility
setting on UNIX 165
PM User
setting on UNIX 162
PM_HOME
configuring on UNIX 162
pmcmd command line program
code page issues 41, 215
communicating with the Informatica Server 41
pmconfig program
using 162
PmNullPasswd
reserved word 196
PmNullUser
reserved word 196
pmrep
See Repository Guide
PMServer 4.0 date handling compatibility
setting on UNIX 165
pmserver command
starting server (UNIX) 175
pmserver.cfg
file 162
post-session
email option for Windows 139
PowerCenter
connectivity 21
installation steps 25
upgrading steps 26
PowerMart
connectivity 21
installation steps 25
upgrading steps 26
primary domain controller
Informatica Server installation guidelines 127
privileges
registering Informatica Server 184
R
registering
Informatica Server 185, 187, 188
multiple servers on local repository 184
release notes
installing 67
repositories
changing a code page 117
code page 40, 42, 215
connectivity 21
252 Index
creating 117
entering name for Informatica Server (UNIX) 162
entering name for Informatica Server (Windows) 135
global 116
local 116
open architecture 116
overview 116
restricted characters for repository name 117
size requirements 20, 26
standalone 116
tips 123
types of 116
Repository Manager
installing 67
Repository Name
setting on UNIX 162
repository objects
overview 9
Repository Password
setting on UNIX 163
Repository Server
configuration (UNIX) 103
configuration (Windows) 83
connecting to Oracle (UNIX) 106
installation (UNIX) 101
installation (Windows) 82
setting Administrative Password (Windows) 83
setting AdminPasswd (UNIX) 103
setting Backup Directory (Windows) 84
setting BackupDir (UNIX) 103
setting ConfigDir (UNIX) 103
setting Configuration Directory (Windows) 84
setting ErrorSeverityLevel (UNIX) 104
setting LogFileName (UNIX) 104
setting Maximum Port Number (Windows) 84
setting Minimum Port Number (Windows) 84
setting Output to Event Log (Windows) 84
setting Output to File (Windows) 84
setting RaMaxPort (UNIX) 103
setting RaMinPort (UNIX) 103
setting Server Port Number (Windows) 83
setting ServerPort (UNIX) 103
setting Severity Level (Windows) 84
starting (Windows) 91
starting on UNIX 112
stopping from Repository Manager 94
stopping from the Repository Manager 113
stopping from the UNIX command prompt 113
stopping from Windows command prompt 94
stopping from Windows Control Panel 94
user accounts (Windows) 80
Repository User
setting on UNIX 162
RepServerHostName
setting on UNIX 163
reusable transformations
description 9
root directory
entering 187
server variable 187
S
schemas
description 9
server
See Informatica Server
See also database-specific server
Server Name
setting on UNIX 162
server variables
description 185
directories on Windows 127, 158
list 186
session log 185
Session Log in UTF8
setting on UNIX 163
session logs
server variable for 185
sessions
description 9
setting maximum (UNIX) 163
sort order 41
SHLIB_PATH
overview 105, 167
Solaris
shared library environment variable 105, 160, 167
sort order
code page 41
Source Analyzer
Designer 10
Index 253
source databases
code page 40, 42, 214
connecting through ODBC (UNIX) 178
connectivity 21
source definitions
See Designer Guide
description 9
sources
supported 2
SQL scripts
installing 67
standalone repositories
description 116
starting
Informatica Server (UNIX) 175
Informatica Server automatically (Windows) 150
stopping
Stored Procedure databases
setting number of connections (Windows) 137
subset
defined for code page compatibility 39
superset
defined for code page compatibility 38
Sybase
ODBC driver 65
Sybase Key
setting on UNIX 164
Sybase SQL Server
connect string example 23
ODBC issues 72, 197
platform key (UNIX) 164
setting key on 132
setting maximum connections (Windows) 137
SybaseIQLocaltoPmServer
setting on UNIX 166
system locales
definition 32
system requirements
minimum installation requirements 20
T
Target Data
window 11
target databases
code page 40, 42, 214
connecting through ODBC (UNIX) 178
connectivity 21
target definitions
See Designer Guide
description 9
targets
supported 3
TCP/IP Host Address
TCP/IP network protocol
configuration restrictions 158
connection requirement 185
host address 133
requirement for Informatica Server 22
server settings 189
temporary files
Teradata
ODBC driver 65
territory
testing
date display formats 139
Time Stamp Workflow Log
Transformation Developer
Designer 10
Treat Char as Char on read (Microsoft SQL Server and
PeopleSoft on Oracle)
troubleshooting
installation (Windows) 152
tutorials
See also Getting Started
installing 67
U
Unicode mode
See also ASCII
overview 33
254 Index
setting data movement mode (UNIX) 163
uninstalling
Merant ODBC drivers 66
UNIX
configuring the Informatica Server 162
connecting Informatica Server to databases 167
connecting to ODBC data sources 178
installing the Informatica Server 160
platform key 164
pmconfig program 162
pmserver.cfg 162
starting Informatica Server 175
stopping Informatica Server 175
UNIX environment variables
LANG_C 36
LC_ALL 36
LC_CTYPE 36
upgrading
overview 26
user locales
definition 32
users
types for Informatica Server (Windows) 127
UTF-8
definition 33
V
Validate Data Code Pages
setting on UNIX 163
verifying Informatica Server starts (Windows)
procedure 149
versions
handling Aggregator transformation (UNIX) 165
handling Aggregator transformation (Windows) 136
W
Warehouse Designer
Designer 10
Warn about duplicate XML rows
webzine xxv
Windows
automatically starting Informatica Server 150
backup domain controller 127
configuring Informatica Server 131
connecting Informatica Server to databases 69
installing Informatica Client 67
installing Informatica Server 129
platform key 132
primary domain controller 127
required permissions for session log file directory 128
service start account (Windows 2000) 96
service start account (Windows NT) 95
starting Informatica Server 148, 152, 153
stopping Informatica Server 150
user accounts 127
verifying Informatica Server starts 149
windows
Workflow Manager default 14
Workflow Manager
installing 67
overview 184
registering the Informatica Server 185, 188
stopping server (Windows) 150, 175
troubleshooting 156
windows 14
workflows
description 9
workspace
Designer 11
X
XMLWarnDupRows
setting on UNIX 166

Informatic Installationguide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Informatic Installationguide

Încărcat de

Drepturi de autor:

Formate disponibile

Installation and

Metadata Exchange SDK User Guide. Provides information about the

User Guide. Provides information on how to transport

User and Administrator Guide. Provides

User and Administrator Guide. Provides information to

BW User and Administrator Guide. Provides information to

User and Administrator Guide. Provides information to

User and Administrator Guide. Provides information to

User and Administrator Guide. Provides information to

Software Development Kit Developer Guide. Provides information to

S-ar putea să vă placă și