Install

Installation and Configuration
Guide
INFORMATICA® POWERMART® 5
INFORMATICA® POWERCENTER® 5
(VERSION 5.1)
Informatica PowerMart/PowerCenter Installation and Configuration Guide
Version 5.1.0
June 2001
Copyright (c) 2001 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, PowerChannel, PowerConnect, PowerPlug, PowerBridge, 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) 1999-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.
Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
About PowerCenter and PowerMart . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Accessing the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . .xviii
Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Version 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Version 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
Chapter 1: Installation and Configuration Overview . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
PowerMart and PowerCenter Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Informatica Client Tools and Informatica Server Connections . . . . . . . . . 3
PowerMart and PowerCenter Installation Steps . . . . . . . . . . . . . . . . . . . . . . . 6
Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Upgrading from a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2: Globalization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
System Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
User Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Input Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
iii
Character Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Changing Data Movement Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Code Page Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operating System Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Choosing a Code Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Informatica Code Page Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Relaxed Data Code Page Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring the Informatica Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Relaxed Code Page Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Troubleshooting for Relaxed Code Page Validation . . . . . . . . . . . . . . . . . . . 32
Case Study: Processing 7-bit ASCII Data . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring the 7-bit ASCII Environment . . . . . . . . . . . . . . . . . . . . . . 34
ASCII Case Study: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Case Study: Processing ISO 8859-1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . 37
The ISO 8859-1 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring the ISO 8859-1 Environment . . . . . . . . . . . . . . . . . . . . . . 38
ISO 8859-1 Case Study: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 3: Installing and Configuring the Informatica Client . . . . . . 43

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Step 1. Installing ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Merant ODBC 3.6 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Uninstalling Merant ODBC 3.6 Drivers . . . . . . . . . . . . . . . . . . . . . . . . 46
Step 2. Installing the Informatica Client Tools . . . . . . . . . . . . . . . . . . . . . . . 47
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Connecting to a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . 52
Connecting to a Sybase SQL Server Database . . . . . . . . . . . . . . . . . . . . 54
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Connecting to an IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . 57
Connecting to Microsoft Access97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Connecting to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Connecting to a Teradata Source Database . . . . . . . . . . . . . . . . . . . . . . 60
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
iv Table of Contents
Chapter 4: Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 5: Installing and Configuring the Informatica NT Server . . . 69

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
DHCP (TCP/IP Connections Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating Informatica Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Informatica Server Variable Directories . . . . . . . . . . . . . . . . . . . . . . . . . 72
Step 1. Installing the Informatica NT Server . . . . . . . . . . . . . . . . . . . . . . . . 73
Step 2. Configuring the Informatica NT Server . . . . . . . . . . . . . . . . . . . . . 75
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting to Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting to Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Connecting to Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Connecting to Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Connecting to IBM DB2 Universal Database . . . . . . . . . . . . . . . . . . . . 91
Connecting to Microsoft Access97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Connecting to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Connecting to a Teradata Source Database . . . . . . . . . . . . . . . . . . . . . . 93
Step 4. Starting and Stopping the Informatica Server . . . . . . . . . . . . . . . . . . 95
Windows NT/2000 Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Command Line Program (pmcmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 6: Installing and Configuring the Informatica UNIX Server 105

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
DHCP (TCP/IP Connections Only) . . . . . . . . . . . . . . . . . . . . . . . . . 106
Step 1. Installing the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Step 2. Configuring the Informatica Server on UNIX . . . . . . . . . . . . . . . . 109
Step 3. Connecting to Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Connecting to an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Table of Contents v
Connecting to a Sybase SQL Server Database . . . . . . . . . . . . . . . . . . . 120
Connecting to an Informix Database . . . . . . . . . . . . . . . . . . . . . . . . . 121
Connecting to a DB2 Universal Database . . . . . . . . . . . . . . . . . . . . . . 122
Step 4. Starting and Stopping the Informatica Server on UNIX . . . . . . . . . 125
UNIX Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Command Line Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Installing and Configuring ODBC for UNIX . . . . . . . . . . . . . . . . . . . . . . 127
Connecting to ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Chapter 7: Registering the Informatica Server . . . . . . . . . . . . . . . . 133

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Registering the Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Informatica Server Code Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Server Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Steps for Registering an Informatica Server . . . . . . . . . . . . . . . . . . . . . 138
Chapter 8: Upgrading a Repository . . . . . . . . . . . . . . . . . . . . . . . . . 141

Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Upgrading a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Selecting a Code Page (PowerMart 4.6/PowerCenter 1.6 Only) . . . . . . . 145
Upgrading PowerMart 4.6/4.7 or PowerCenter 1.6/1.7 . . . . . . . . . . . . . . . 147
Upgrading Lookup Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Upgrading System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Upgrading Global Objects with Permissions . . . . . . . . . . . . . . . . . . . . 148
Upgrading Objects for Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Upgrading External Loader Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Upgrading Incremental Aggregation Files . . . . . . . . . . . . . . . . . . . . . . 150
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Upgrade Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 9: Using ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
ODBC and the Informatica Client and Server . . . . . . . . . . . . . . . . . . . . . . 156
Database ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
vi Table of Contents
Client ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Server ODBC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Creating an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Configuring ODBC for Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . 162
Configuring ODBC for Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Configuring ODBC for SQL Server 6.5 . . . . . . . . . . . . . . . . . . . . . . . 163
Configuring ODBC for SQL Server 7.0 . . . . . . . . . . . . . . . . . . . . . . . 164
Configuring an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Deleting an ODBC Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Appendix A: Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Code Page Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Informatica Code Page Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Supported Code Pages and Related Code Pages . . . . . . . . . . . . . . . . . . 178
Converting from MS Latin1 to Latin1 . . . . . . . . . . . . . . . . . . . . . . . . 187
Converting from Latin1 to MS Latin1 . . . . . . . . . . . . . . . . . . . . . . . . 187
Converting from IBM EBCDIC US English to Latin1 . . . . . . . . . . . . . 188
Converting from Latin1 to IBM EBCDIC US English . . . . . . . . . . . . . 189
Converting from MS Shift JIS to JapanEUC . . . . . . . . . . . . . . . . . . . . 189
Converting from JapanEUC to MS Shift JIS . . . . . . . . . . . . . . . . . . . . 192
Converting from IBM EBCDIC Japanese to JapanEUC . . . . . . . . . . . . 197
Converting from JapanEUC to IBM EBCDIC Japanese . . . . . . . . . . . . 198
Converting from IBM EBCDIC Japanese to MS Shift JIS . . . . . . . . . . 203
Converting from MS Shift JIS to IBM EBCDIC Japanese . . . . . . . . . . 204
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table of Contents vii

viii Table of Contents
List of Figures
Figure 1-1. PowerMart and PowerCenter Connectivity . . . . . . . . . . . . . . . . . . . . . . .. . .. . .. 3
Figure 2-1. Required Code Page Relationships for Unicode Data Movement Mode . . .. . .. . . 19
Figure 2-2. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 22
Figure 2-3. 7-bit ASCII Mode Case Study Environment . . . . . . . . . . . . . . . . . . . . . .. . .. . . 33
Figure 2-4. ASCII Case Study Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 36
Figure 2-5. ISO 8859-1 Case Study Environment . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 38
Figure 2-6. Summary of ISO 8859-1 Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 41
Figure 9-1. ODBC Connectivity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 154
Figure 9-2. ODBC Microsoft Excel Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 162
Figure 9-3. ODBC Sybase Driver Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 163
Figure 9-4. ODBC SQL Server 6.5 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 163
Figure 9-5. ODBC SQL Server 7.0 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . 164
List of Figures ix
x List of Figures
List of Tables
Table 1-1. Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. 2
Table 1-2. Informatica Client Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . .. . .. 4
Table 1-3. Informatica Server Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . .. . .. 4
Table 1-4. Native Connect String Syntax ................................ . .. . .. 5
Table 2-1. Session and File Cache Handling After Data Movement Mode Change . . . . . .. . . 14
Table 2-2. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 23
Table 3-1. ODBC Drivers for Source and Target Databases . . . . . . . . . . . . . . . . . . . . . . .. . . 45
Table 3-2. Informatica Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 48
Table 3-3. Informix SetNet32 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 56
Table 4-1. Create Repository Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 66
Table 5-1. Installation Parameters for Informatica Server on Windows NT/2000 . . . . . . .. . . 73
Table 5-2. Keys Configuration for Informatica Server on Windows NT/2000 . . . . . . . . . .. . . 76
Table 5-3. Network Configuration for Informatica Server on Windows NT/2000 . . . . . . .. . . 78
Table 5-4. Repository Configuration for Informatica Server on Windows NT/2000 . . . . .. . . 79
Table 5-5. Compatibility and Database Configuration for Informatica NT Server . . . . . . .. . . 80
Table 5-6. Miscellaneous Configuration for Informatica Server on Windows NT/2000 . . .. . . 83
Table 5-7. Informix SetNet32 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 90
Table 6-1. Library Path for Informatica Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . .. . 107
Table 6-2. Configuration Parameters for Informatica Server on UNIX . . . . . . . . . . . . . . .. . 109
Table 6-3. Library Path for Informatica Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . .. . 115
Table 7-1. TCP/IP Settings to Register a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 139
Table 7-2. IPX/SPX Settings to Register a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 140
Table 8-1. Upgrading Lookup Transformation Options . . . . . . . . . . . . . . . . . . . . . . . . . .. . 147
Table 9-1. ODBC Connection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 156
Table 9-2. Database ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 157
Table 9-3. Informatica Client ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 158
Table 9-4. Informatica Server ODBC Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 160
Table A-1. Code Page Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 170
Table A-2. Code Pages by Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 172
Table A-3. Code Page Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 176
Table A-4. Compatible Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 178
Table A-5. Supported Code Pages and Related Code Pages . . . . . . . . . . . . . . . . . . . . . . .. . 179
Table A-6. MS Latin1 to Latin1 Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . .. . 187
Table A-7. Latin1 to MS Latin1 Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . .. . 187
Table A-8. IBM EBCDIC US English to Latin1 Character Conversion . . . . . . . . . . . . . . .. . 188
Table A-9. Latin1 to IBM EBCDIC US English Character Conversion . . . . . . . . . . . . . . .. . 189
Table A-10. MS Shift JIS to JapanEUC Character Conversion . . . . . . . . . . . . . . . . . . . . .. . 189
Table A-11. JapanEUC to MS Shift JIS Character Conversion . . . . . . . . . . . . . . . . . . . .. . 192
Table A-12. IBM EBCDIC Japanese to JapanEUC Character Conversion . . . . . . . . . . . . .. . 197
Table A-13. JapanEUC to IBM EBCDIC Japanese Character Conversion . . . . . . . . . . . . .. . 198
List of Tables xi
Table A-14. IBM EBCDIC Japanese to MS Shift JIS Character Conversion . . . . . . . . . . . . . .203
Table A-15. MS Shift JIS to IBM EBCDIC Japanese Character Conversion . . . . . . . . . . . . . .204
xii List of Tables

Preface
Welcome to PowerMart and PowerCenter, Informatica’s integrated suite of software products

that deliver an open, scalable solution addressing the complete life cycle for data warehouse
and analytic application development. Both PowerMart and PowerCenter combine the latest
technology enhancements for reliably managing data repositories and delivering information
resources in a timely, usable manner.
The metadata repository coordinates and drives a variety of core functions including
extraction, transformation, loading, and management. The Informatica Server can extract
large volumes of data from multiple platforms, handle complex transformations, and support
high-speed loads. PowerMart and PowerCenter can simplify and accelerate the process of
moving data warehouses from development to test to full production.
xiii
About Informatica Documentation
The complete set of printed documentation for PowerMart and PowerCenter 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 Informatica 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 PowerMart and PowerCenter
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.
♦ Session and Server Guide. Provides information to help you create and run sessions in the
Server Manager, as well as administer the Informatica Server. Also contains information on
tuning sessions and the Informatica Server for better performance.
♦ Transformation Language Reference. Provides syntax descriptions and examples for each
transformation function provided with PowerMart and PowerCenter.
♦ Troubleshooting Guide. Provides error messages that you might encounter while using
PowerMart or PowerCenter. Each error message includes one or more possible causes and
actions that you can take to correct the condition.
Documentation available with our other products includes:
♦ Informatica® Metadata Exchange SDK User Guide. Provides information about the
second generation of Metadata Exchange interfaces for PowerMart and PowerCenter
repositories.
♦ Informatica® PowerChannel™ User Guide. Provides information on how to transport
compressed and encrypted data through a secure channel.
♦ PowerCenter™ Integration Server for BW Installation Guide. Provides information to
install and configure PCISBW for loading source data into a SAP Business Warehouse. It
also contains basic instructions for loading into BW.
♦ PowerConnect™ for IBM ® DB2® Installation Guide. Provides information on setting up
a mainframe environment to work with PowerCenter, including connectivity issues for
mainframe and DB2 databases.
xiv Preface
♦ 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.
♦ PowerConnect™ for PeopleSoft® User and Administrator Guide. Provides information to
install PowerConnect for PeopleSoft, extract data from PeopleSoft, build mappings, and
run sessions to load PeopleSoft source data into your data warehouse.
♦ PowerConnect™ for SAP ™ R/3® User and Administrator Guide. Provides information to
install PowerConnect for SAP R/3, extract data from SAP R/3, build mappings, and run
sessions to load SAP R/3 data into a data warehouse.
♦ PowerConnect™ for Siebel® User and Administrator Guide. Provides information to
install PowerConnect for Siebel, extract data from Siebel systems, build mappings, and run
sessions to load Siebel source data into a data warehouse.
♦ PowerPlug ™ User Guide. Provides information on how to use PowerPlug to extract
metadata from leading data modeling tools and import it into PowerMart/PowerCenter
repositories through Informatica Metadata Exchange SDK.
♦ PowerBridge™ for Hyperion® Essbase® Server User Guide. Provides information on how
to use PowerBridge to export multi-dimensional metadata from PowerMart/PowerCenter
repositories into the Hyperion Integration Server through Informatica Metadata Exchange
SDK.
About Informatica Documentation xv

About this Book
The Installation and Configuration Guide is written for the system administrators who are
responsible for installing and configuring the PowerMart or PowerCenter 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 online help and Adobe Acrobat versions of this book contain material for PowerMart 5.1/
PowerCenter 5.1. The printed version of this book contains material for PowerMart 5.0/
PowerCenter 5.0. To view printed material for the new features in PowerMart 5.1/PowerCenter
5.1, refer to the PowerMart/PowerCenter Supplemental Guide.
The material in this book is available for online use.
About PowerCenter and PowerMart

This guide contains information about both PowerMart and PowerCenter. The
documentation explicitly mentions software features that differ between the two products.
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 data.
A PowerCenter license lets you create a single repository that you can configure as a global
repository, the core component of a data warehouse.
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 data partitioning. Also, the various options available with PowerCenter
(such as PowerCenter Integration Server for BW, PowerConnect for IBM DB2,
PowerConnect for IBM MQSeries, PowerConnect for SAP R/3, PowerConnect for Siebel,
and PowerConnect for PeopleSoft) are not available with PowerMart.
When this guide mentions a PowerMart Server, it is referring to an Informatica Server with a
PowerMart license.
xvi 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.
About this Book xvii

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. You can access the webzine at:
http://www.informatica.com/webzine
The Informatica Webzine is a password-protected site. Informatica 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://www.informatica.com/support/webpaswdreq.html
If you have any questions, please email [email protected].
To better serve your needs, the Informatica Documentation Team welcomes all comments and
suggestions. You can send comments and suggestions to:
[email protected]
Visiting the Informatica Web Site

You can access Informatica’s 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 Informatica’s interoperability
interfaces.
xviii 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 [email protected] or call 650-687-6300.
North America / South America Africa / Asia / Australia / Europe
Informatica Corporation Informatica Software Ltd.

3350 W. Bayshore Rd. 6 Waltham Park
Palo Alto, CA 94303 Waltham Road, White Waltham
Phone: 650.687.6300 Maidenhead, Berkshire
Fax: 650.687.0040 SL6 3TN
Hours: 6 a.m. - 7 p.m./ p.s.t Phone:
email: [email protected] UK +44 870 606 1525
Germany +49 1805 702 702
Switzerland +41 800 81 80 70
Fax: +44 1628 511 411
Hours: 9 a.m. - 5 p.m./ g.m.t
email: [email protected]
Other Informatica Resources xix

New Features and Enhancements
This section describes new features and enhancements to PowerMart and PowerCenter.
Version 5.1
The following list describes new features and enhancements in PowerMart 5.1/PowerCenter
5.1.
Performance Enhancements
♦ High precision decimal arithmetic. The Informatica Server optimizes data throughput to
increase performance of sessions using the Enable Decimal Arithmetic option.
♦ To_Decimal and Aggregate functions. The Informatica Server uses improved algorithms
to increase performance of To_Decimal and all aggregate functions such as percentile,
median, and average.
♦ Cache management. The Informatica Server uses better cache management to increase
performance of Aggregator, Joiner, Lookup, and Rank transformations.
♦ Partition sessions with sorted aggregation. You can partition sessions with Aggregator
transformation that use sorted input. This improves memory usage and increases
performance of sessions that have sorted data.
Relaxed Data Code Page Validation

When enabled, the Informatica Client and Informatica Server lift code page selection and
validation restrictions. You can select any supported code page for source, target, lookup, and
stored procedure data.
Designer Features and Enhancements

♦ Debug mapplets. You can debug a mapplet within a mapping in the Mapping Designer.
You can set breakpoints in transformations in the mapplet.
♦ Support for slash character (/) in table and field names. You can use the Designer to
import source and target definitions with table and field names containing the slash
character (/). This allows you to import SAP BW source definitions by connecting directly
to the underlying database tables.
Server Manager Features and Enhancements

♦ Continuous sessions. You can schedule a session to run continuously. A continuous
session starts automatically when the Load Manager starts. When the session stops, it
restarts immediately without rescheduling. Use continuous sessions when reading real time
sources, such as IBM MQSeries.
xx Preface
♦ Partition sessions with sorted aggregators. You can partition sessions with sorted
aggregators in a mapping.
♦ Register multiple servers against a local repository. You can register multiple PowerCenter
Servers against a local repository.
Version 5.0
The following list describes new features and enhancements in PowerMart 5.0/PowerCenter
5.0.
Designer Features and Enhancements

♦ Debugger. You can debug a mapping from the Mapping Designer. Using the Debugger
Wizard, choose to run the Debugger against an existing session in debug mode or create a
debug session. Before you debug a mapping, set breakpoints in the mapping where you
want the Informatica Server to evaluate data and error conditions. The Debugger pauses
when a breakpoint evaluates to true, and you can change transformation output data.
♦ Double-click folder icon to open the folder and tool. When you double-click a folder
icon in the Navigator window, the Designer opens the folder and displays the last tool that
was active within that folder.
♦ Find in Workspace tool. You can search for text strings in tables, columns, or ports across
all open objects in the workspace.
♦ Full screen view. You can view the workspace over the entire screen. The Designer hides
the menu, the Navigator and Output windows, and the title bar to maximize the
workspace window.
♦ Invalid mapping icon. The Designer displays a new icon for invalid mappings in the
Navigator window.
♦ Lookup cache. You can use a dynamic lookup cache in a Lookup transformation. When
you use a dynamic lookup cache, the Informatica Server updates the lookup cache during
the session run. Also, you can share persistent lookup caches within and across mappings
by naming the cache files.
♦ Mapping parameters and variables. Create mapping parameters and variables in a mapplet
or mapping to make mappings more flexible. Mapping parameters and variables represent
values in mappings and mapplets. Use mapping parameters and variables to reduce the
overhead of creating multiple mappings when only certain attributes of a mapping need to
change.
♦ New Designer shortcut keys. New shortcut keys allow you to cut, copy, paste, and delete
rows when you edit a repository object.
♦ New workspace look. You can select two colors to create a color gradient for the title bars
of repository objects. Other components of the workspace, such as links, arrows, and tool
title, also have a sharper, three-dimensional look.
♦ Object import and export. You can export objects from a repository and import objects
into a repository. When you export a repository object, the Designer or Server Manager
New Features and Enhancements xxi

creates an XML file describing the repository metadata. Use the XML file to import
repository objects into a repository. You can export and import sources, targets,
transformations, mapplets, mappings, and sessions.
♦ Preview data. The Designer allows you to preview data for relational sources, flat file
sources, and relational targets.
♦ Retain relationships and source or target definition descriptions when re-importing a
source or target definition. When you re-import a source or target definition, you have
the option of retaining primary and foreign key relationships and source or target
descriptions.
♦ Resizable Expression Editor. You can resize the Expression Editor by dragging the corner
of the dialog box.
♦ Router transformation. The Designer allows you to use a Router transformation to test
data based on multiple conditions. The Router transformation allows you to route groups
of data to a transformation or a target.
♦ Save mappings and mapplets under a different name. The Designer allows you to save
mappings and mapplets under a different name within the same folder.
♦ XML sources and targets. You can use XML data as a source or target. You can create
source and target definitions from an XML, DTD, or XML schema file and use them in
mappings. When you run a session, you can read data from an XML source file and
validate it against a DTD. You can also write data from any type of source to an XML file.
Informatica Server Enhancements

♦ Expanded pmcmd capability. You can use the command line program pmcmd to specify a
parameter file when you start a session or batch. This allows you to change the values of
session parameters, and mapping parameters and variables at runtime.
♦ Parallel data processing. Available with PowerCenter only. If you run the Informatica
Server on a symmetric multi-processing system, you can use multiple CPUs to process a
session concurrently. You configure partitions in the session properties based on source
qualifiers. The Informatica Server reads, transforms, and writes partitions of data in
parallel for a single session.
♦ Process session data using threads. The Informatica Server runs on two processes: the
Load Manager process and the DTM process. The DTM process creates threads to
perform session tasks, such as reading, transforming, and writing data as well as
performing pre-and post-session operations.
Metadata Reporter
The Metadata Reporter is a web-based application that enables you to run reports against
repository metadata. With the Metadata Reporter, you can access information about your
repository without having knowledge of SQL, the transformation language, or the underlying
tables in the repository.
xxii Preface
Repository Manager Features and Enhancements
♦ Compare Folders. You can compare the contents of folders in the same repository or across
different repositories.
♦ Copy and Replace Folder Wizard. You can maintain shortcuts from local to global
repositories when you copy and replace folders. When copying folders, you can select the
shared folder to associate shortcuts.
♦ Display user privileges. The Manage Privileges dialog box displays all user and group
privileges so you can assign and revoke privileges by selecting the appropriate option.
♦ pmrep. A command line program for Windows NT/2000 that allows you to perform
repository tasks and change session-related parameters. Using pmrep, you can connect to,
back up, delete, and restore a repository. Additional pmrep commands allow you to update
database connectivity information for a repository, update email address information for
session notification email, and update server variables.
Server Manager Features and Enhancements

♦ Additional email variables. With new email variables, you can configure post-session
email to include information, such as the mapping used during the session.
♦ Additional server variables. You can configure several new server variables when
registering a server. Server variables such as $PMSuccessEmailUser allow you to configure
sessions without hard-coding information.
♦ Copy session. You can copy sessions across folders and repositories using the Copy Session
Wizard in the Server Manager.
♦ Enhanced user security. You can set read, write, and execute permissions for users and
groups to restrict access to database, FTP, and external loader connections.
♦ Global validation of sessions. You can validate a specified set of sessions in a folder or
validate all of the invalid sessions in a folder.
♦ Read-only privileges for sessions. You can set user and group permissions and privileges
that allow users to view, but not edit, session properties.
♦ Session parameters. Create session parameters to reuse sessions. You can create parameters
for database connections, reject files, and file sources and targets. You can also use a built-
in session parameter for the session log. Define session parameters in the session parameter
file.
♦ Sybase IQ 12 External Loader. You can use Sybase IQ 12 external loaders to load
multibyte data. Null characters and delimiters can be up to four bytes long.
♦ Teradata External Loader. You can use Teradata external loaders to load single-byte data.
The Teradata external loader uses ASCII-based single-byte code pages.
Transformation Language Enhancements

You can use two new built-in system variables with PowerMart and PowerCenter:
New Features and Enhancements xxiii

♦ SESSSTARTTIME. Returns the system date value on the machine hosting the
Informatica Server when the server initializes the session. You can use SESSSTARTTIME
within any function that accepts transformation date/time datatypes using the
transformation language.
♦ $$$SessStartTime. Returns the system date value on the machine hosting the Informatica
Server when the server initializes the session. You can use $$$SessStartTime at the
mapping level in the filter condition, user-defined join, or SQL override of a source
qualifier. You can also use $$$SessStartTime in session-level overrides for mapping
attributes.
You can also use four new variable functions with mapping variables:
♦ SetCountVariable. Counts the number of evaluated rows and increment or decrement a
mapping variable for each row.
♦ SetMaxVariable. Evaluates the value of a mapping variable to the higher of two values.
♦ SetMinVariable. Evaluates the value of a mapping variable to the lower of two values.
♦ SetVariable. Sets the value of a mapping variable to a specified value.
xxiv Preface
Chapter 1
Installation and
Configuration Overview
This chapter includes the following topics:
♦ Overview, 2
♦ PowerMart and PowerCenter Connectivity, 3
♦ PowerMart and PowerCenter Installation Steps, 6
1
Overview
Installing and configuring PowerMart and PowerCenter requires some understanding of the
different components of the product. Before you begin installation, read:
♦ “Product Overview” in Getting Started. This chapter provides an overview of the product
and guidelines for designing your data warehouse.
♦ This chapter. Before you install the product, review the installation steps and connectivity
requirements.
Minimum System Requirements

Before you install PowerMart or PowerCenter, verify system requirements.
Table 1-1 shows the minimum system requirements to run PowerMart or PowerCenter Client
and the Informatica Server:
Table 1-1. Minimum System Requirements
Informatica Client Informatica Repository Informatica Server
Operating system Windows 95/98, Windows 2000, Windows Windows 2000, Windows
Windows 2000, or NT 4.0, or UNIX (Solaris, NT 4.0, or UNIX (Solaris,
Windows NT 4.0 HP-UX, AIX) HP-UX, AIX)
Disk space 170 MB 70 MB of database space* 100 MB
RAM 128 MB 128 MB 256 MB
Database connectivity ODBC drivers Native drivers or ODBC Native drivers or ODBC
* Although you can create a repository with a minimum of 70 MB of database space, Informatica recommends allocating up to 130
MB for repositories.
2 Chapter 1: Installation and Configuration Overview

PowerMart and PowerCenter Connectivity
Since most data warehouses do not exist on a single computer, you must configure
connectivity between the different components and databases.
Figure 1-1 shows the PowerMart and PowerCenter components and connectivity:
Figure 1-1. PowerMart and PowerCenter Connectivity
This section covers the general connectivity information. For detailed information on
configuring connectivity for the Informatica Client tools and Informatica Server, see the
appropriate installation chapters in this guide.
Informatica Client Tools and Informatica Server Connections

The following sections describe the necessary connections that need to exist between the
Informatica Client tools and Informatica Server.
Informatica Client Connections

The Informatica Client uses two software layers to communicate with each source, target, and
repository database:
♦ ODBC drivers
♦ Native database client connectivity software
Informatica Client tools pass all 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
PowerMart and PowerCenter Connectivity 3

request and sends the information back to the Designer (passing through the native software
layer and ODBC software), which displays the source definition.
For each database, make note of the native connect string that you define through the
database connectivity software, such as Net8. Reference these connect strings in the
Informatica Server configuration utility, Repository Manager, and Server Manager.
The Server Manager communicates directly with the Informatica Server each time you
schedule or edit a session, display session details, and request session logs. Unlike connecting
to a database, the Server Manager communicates with the Informatica Server through a TCP/
IP or IPX/SPX port. You create the connection by defining the port number in the Server
Manager and in the Informatica Server configuration.
Table 1-2 summarizes the software you need to connect the Informatica Client to the
repository, source, target databases, and the Informatica Server:
Table 1-2. Informatica Client Connectivity Requirements
To connect the Informatica Client to the... You need...
Repository database ODBC connection for the database containing the repository
Source databases ODBC connection for each source database
Target databases ODBC connection for each target database
Informatica Server TCP/IP or IPX/SPX
Informatica Server Connections

The Informatica Server needs a connection to the repository database. You cannot start the
Informatica Server without first configuring it to connect to the repository database. You also
need to use the Server Manager to register the Informatica Server in the repository.
Table 1-3 summarizes the software you need to connect the Informatica Server to the
repository, source, and target databases:
Table 1-3. Informatica Server Connectivity Requirements
To connect the Informatica Server to the... You need...
Repository Native database drivers or ODBC
Source databases Native database drivers or ODBC
Target databases Native database drivers or ODBC
Informatica Client TCP/IP or IPX/SPX

Note: Both the Windows NT/2000 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.
The Informatica Server requires a connect string to communicate with the repository. You
define the native connect string in the native database client connectivity software, such as
Net8, on the machine hosting the repository database.

Table 1-4 lists the native connect string syntax for each supported RDBMS:
Table 1-4. 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
Oracle dbname.world (same as TNSNAMES entry) oracle.world
Sybase servername@dbname sambrown@mydatabase
For Windows NT/2000, the Informatica Server includes ODBC libraries that you can use to
connect to other ODBC source databases, such as FoxPro and Paradox.
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.
PowerMart and PowerCenter Connectivity 5

PowerMart and PowerCenter Installation Steps
This section outlines the steps for installing PowerMart and PowerCenter. 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 PowerMart and PowerCenter for the first time, complete each of the
following tasks in the specified order:
1. Install the Informatica Client tools.
For more information, see “Installing and Configuring the Informatica Client” on
page 43.
2. Configure the Informatica Client tools to connect to each database your data warehouse
needs to access.
page 43.
3. Create an ODBC connection for each source, target, and repository database.
For more information, see “Using ODBC” on page 153.
4. Create a repository.
Before you can start the Informatica Server, create a repository. The Informatica Server
needs a connection to the repository. For more information, see “Creating a Repository”
on page 63.
5. Configure the machine on which you plan to install the Informatica Server to connect to
each database and the Informatica Client tools.
See the appropriate installation chapter for your platform. The chapters are “Installing
and Configuring the Informatica UNIX Server” on page 105 and “Installing and
Configuring the Informatica NT Server” on page 69.
6. Install the Informatica Server.

7. Use the Server Manager to register the Informatica Server with the repository.
For more information, see “Registering the Informatica Server” on page 133.
8. Start the Informatica Server.
Upgrading from a Previous Version

You can upgrade to PowerMart 5.1 and PowerCenter 5.1 from PowerMart 4.6/4.7/5.0 or
from PowerCenter 1.6/1.7/5.0. Follow these steps to upgrade to PowerMart 5.1 or
PowerCenter 5.1:
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 PowerMart 5.1 or
PowerCenter 5.1.
See your database documentation for details.
Note: The PowerMart 5.1 and PowerCenter 5.1 repository is approximately 15 percent
larger than a PowerMart 4.7 and PowerCenter 1.7 repository and approximately 45
percent larger than a PowerMart 4.6 or PowerCenter 1.6 repository. Before you upgrade
the repository, check the repository database size and available disk space. If you are
upgrading a PowerMart 4.6 or PowerCenter 1.6 repository, you need to increase the size
of the database or add more disk space because during the upgrade, the table columns
widen to allocate space for multibyte character data. Informatica recommends that you
allocate approximately 60 percent additional space in the database. The PowerMart 5.1
and PowerCenter 5.1 repository is not significantly larger than the PowerMart 5.0 and
PowerCenter 5.0 database. If you are upgrading a PowerMart 5.0 or PowerCenter 5.0
repository, you do not need to allocate additional space in the database.
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 PowerMart 5.1 or
PowerCenter 5.1. Upgrade the copy of your existing repository to PowerMart 5.1/
PowerCenter 5.1 to evaluate it without altering your existing repository. For more
information, see “Upgrading a Repository” on page 141.
4. Upgrade the Informatica Client tools.
page 43.
5. Configure the Informatica Client tools to connect to each database your data warehouse
needs to access.
page 43.
6. Create an ODBC connection for each source, target, and repository database.
PowerMart and PowerCenter Installation Steps 7

Note: The Merant 3.6 32-bit ODBC closed drivers are designed for use with PowerMart
and PowerCenter only. If you use them with other software, these drivers generate
warning messages about violating licensing agreements. For details, see “Using ODBC”
on page 153.
7. Upgrade each repository.
For more information, see “Upgrading a Repository” on page 141.
8. Configure the machine on which you plan to install the Informatica Server to connect to
each database and the Informatica Client tools.
9. Install and configure the Informatica Server.
10. In the Server Manager, register the Informatica Server in the repository.
For details, see “Registering the Informatica Server” on page 133.

Chapter 2
Globalization Overview

♦ Overview, 10
♦ Locales, 12
♦ Data Movement Modes, 13
♦ Code Page Overview, 16
♦ Relaxed Data Code Page Validation, 27
♦ Case Study: Processing 7-bit ASCII Data, 33
♦ Case Study: Processing ISO 8859-1 Data, 37
9
Overview
The Informatica Server can process single-byte data or multibyte data. PowerMart and
PowerCenter 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 PowerMart or PowerCenter, you must decide if you want the Informatica
Server to process single-byte data or multi-byte 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 PowerMart and PowerCenter, 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
♦ Source and target database code pages
PowerMart and PowerCenter also allow you to configure the Informatica Client and
Informatica Server for relaxed data code page validation. Relaxed validation lifts restrictions
on source and target data code page selection.
10 Chapter 2: Globalization Overview

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.
Overview 11
Locales
Every machine has a locale, a set of preferences related to the user environment. PowerMart
and PowerCenter 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 and Server on Windows NT/
2000 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
PowerMart and PowerCenter.
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 NT/2000 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.

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 and 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 18.
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 one code
page, such as ISO 8859-1 (8-bit ASCII) or Shift-JIS, only.
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 23.
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. 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.
Data Movement Modes 13

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 2-1 describes how the Informatica Server handles session files and caches after you
change the data movement mode:
Table 2-1. Session and File Cache Handling After Data Movement Mode Change
Session File or Time of Creation or Informatica Server Behavior After Data Movement
Cache Use Mode Change
Session Log File Each session. No change in behavior. Creates a new session log for each
(*.log) session 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 No change in behavior for delimited flat files. Creates a new
file. output file for each session using the target code page.
Indicator File (*.in) Sessions writing to flat No change in behavior. Creates a new indicator file for each
file. session.
Incremental Sessions with When files are removed or deleted, the Informatica Server
Aggregation Files Incremental creates new files.
(*.idx, *.dat) Aggregation enabled.
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 Sessions with a Rebuilds the persistent lookup cache.

Persistent Lookup Lookup transformation
Files (*.idx, *.dat) configured for a
persistent lookup
cache.
Named Persistent Sessions with a Fails the session.

Lookup Files (*.idx, Lookup transformation
*.dat) configured for a
persistent lookup
cache.

If you are not sure how you want to run the Informatica Server, install and configure
PowerMart and PowerCenter 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.
Data Movement Modes 15

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 PowerMart or PowerCenter 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
a 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 95, 98, NT, and 2000 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 95 and 98 as fully-localized products with default code pages.
Windows NT/2000 has two code pages:
♦ ANSI Code Page. Windows NT/2000 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 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 95/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 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 NT/2000 in the United States and
Code Page Overview 17

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 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 2-1 illustrates the necessary relationship between source and target database code pages
when you run the Informatica Server in Unicode data movement mode:
Figure 2-1. Required Code Page Relationships for Unicode Data Movement Mode
Target Code Page
Informatica Server Code Page
Source Code Page
When you install or upgrade to run the Informatica Server in Unicode mode, you need to
ensure code page compatibility between the Informatica Client, Server, and repository
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 involved in 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.
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 176.

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 Server Manager, select the same code page as the
operating system code page.
♦ 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 Server Manager, you enter the
identical code page. The Server 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
♦ Compatible with the repository code page
Each code page has associated sort orders. When you configure a session, the Server 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 NT/2000, 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 Code Page

The repository code page is the code page of the data in the repository. The repository code
page must be:
♦ Compatible with the Informatica Client code page
♦ Compatible with the Informatica 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 2-2 illustrates code page compatibility between sources, targets, the repository, and the
Informatica Client and Server:
Figure 2-2. Code Page Compatibility

Table 2-2 summarizes code page compatibility between sources, targets, the repository, and
the Informatica Client and Server:
Table 2-2. Code Page Compatibility
Component Code Page Code Page Compatibility
Source (including relational, flat file, Subset of target.

and XML file) Subset of Informatica Server.
Target (including relational, XML files, Superset of source.

and flat files) 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.
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.
Informatica Code Page Validation

For PowerMart and PowerCenter, the machines hosting the Informatica Client, Server, and
repository 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:
♦ Informatica Client restricts the use of EBCDIC-based code pages. Since you cannot
install the Informatica Client, Server, or repository on mainframe systems, the Informatica
Client does not allow you to select EBCDIC-based code pages, like IBM EBCDIC, as the
repository code page or the Informatica Server code page.
♦ Informatica Client restricts repository code page choices to those compatible with the
Informatica Client. The Informatica Client code page must be compatible with the
repository code page to prevent data loss or inconsistencies. After you install the
Informatica Client, it uses the operating system code page as the Informatica Client code
page. When you create a new repository or upgrade an existing repository, you select a

code page for the repository. The Repository Manager restricts code page choices to those
compatible with the Informatica Client 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.
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 NT/2000 Event Viewer or the UNIX server log or server error
log:
LM_2473 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 Server Manager. To ensure accurate session validation, the Informatica
Server code page must be registered correctly in the Server Manager. After you install or
upgrade the Informatica Client and repository, the Server 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 Server 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 NT/2000 Event Viewer or UNIX server or
server error log:
LM_2474 Error: codepage mismatch. Server is running in codepage
<Informatica Server code page> whereas the server is configured in the
Server 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 Server Manager restricts code page choices to those compatible
with the Informatica Client code page.
♦ When in Unicode data movement mode, the Informatica Server starts sessions with the
appropriate source and target code page relationships. 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 session. For details on code
page relationships, subsets, and supersets, see “ Supported Code Pages and Related Code
Pages” on page 178.
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:
LM_2457 Error: Code page incompatible in session <session name>.
<Additional details>.
♦ Server Manager validates source and target code page relationships for each session.
Source and target code page relationships are critical when the Informatica runs in
Unicode mode. As a result, the Server Manager always checks code page relationships when
you save a session, regardless of the Informatica Server data movement mode. The Server
Manager alerts you to inappropriate code page relationships in case you change the
Informatica Server to Unicode mode or run the session on a different Informatica Server.
If you configure a session with invalid source or target code page relationships, the Server
Manager issues a warning similar to the following when you save the session:
If you want to run the session on an Informatica Server in ASCII mode, you can save the
session as configured. If you want to run the session 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
property sheet. The Server Manager restricts source file code page choices to those that
are subsets of the Informatica Server code page. The Server Manager also restricts target
file code page choices to those that are subsets of the Informatica Server code page. The
Server 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 session database connections. Edit the code
page for relational sources and targets in the Server Manager database connection dialog
box. Because you can use the same database connection as a source or target, the Server
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.
♦ Server 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 Server
Manager always checks these code page relationships.

When you configure the session with invalid lookup or stored procedure code page
relationships, the Server 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 session on an Informatica Server in ASCII mode, you can save the
session as configured. If you want to run the session 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 property sheet.
− Correct the code page for the database connection. You can configure the database code
page in the Server Manager.
− Correct the configured code page for the registered server.

Relaxed Data Code Page Validation
Your data warehouse 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
Client and 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.
PowerMart and PowerCenter 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 selection. You can select any code
page supported by PowerMart and PowerCenter for your source and target data.
♦ Lifted restrictions for session sort order selection. You can select any sort order supported
by PowerMart and PowerCenter 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.
You must configure both the Informatica Server and the Informatica Client to use relaxed
data code page validation. The Informatica Server and Informatica Client must be configured
the same way to ensure safe data processing and avoid errors when selecting code pages or
running sessions.
Configuring the Informatica Server

To configure the Informatica Server on Windows NT/2000 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 NT/2000 for data code page relaxation
in the Informatica Server setup program. On the Miscellaneous tab of the Informatica Server
setup program, clear the Validate Data Code Pages check box, select UNICODE as the data
movement mode, and select the Session Log in UTF-8 check box.
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 Data Code Page Validation 27

Configuring the Informatica Client
When you install the Informatica Client tools, the final step of the installation program
allows you to enable or disable data code page validation. If you want to configure the
Informatica Client for relaxed data code page validation, select the Disable Code Page
Validation check box in the final step of the Informatica Client installation program.
If you want to reconfigure the code page validation features of the Informatica Client at a
later time, you must edit the powrmart.ini file. You can find powrmart.ini in the root
directory of your client installation. Open the file and edit the ValidateDataCodePages entry
under the Code Pages section:
♦ Configure this entry to Yes if you want to enforce restrictions for data code page selection
and session sort order selection in the Designer and Server Manager
♦ Configure this entry to No if you want to lift restrictions for data code page selection and
session sort order selection in the Designer and Server Manager.
Relaxed Code Page Validation

Configuring the Informatica Client and Informatica Server for relaxed data code page
validation lifts restrictions on source and target data code pages. However, the Informatica
Server and Informatica Client continue to prevent data inconsistencies between PowerMart
and PowerCenter components by enforcing code page compatibility between the Informatica
Server, Informatica Client, and the repository.
Informatica Client Relaxed Code Page Validation

When you configure code page relaxation, it provides the following relaxation for code page
selection:
♦ You can select any supported code page for source, target, lookup and stored procedure
database connections.
♦ You can select any supported code page when you create or edit a flat file source definition.
♦ You can select any supported sort order when you configure a session.
Note: The Flat File Wizard restricts some code pages when you import a flat file source
definition. You cannot select EBCDIC code pages for flat file source definitions. If you select
UTF-8 or a code page containing a shift-in character set, the Designer does not allow you
choose a fixed-width flat file type.
The Informatica Client code page must be two-way compatible with the repository database
code page.
When you configure a session, the Informatica Client allows you to select any supported
session sort order. The sort order does not have to be compatible with the Informatica Server
code page. When you specify a sort order in a specific language, the Informatica Server
processes all data within that specific language range according to the specified sort order. The
Informatica Server sorts all data that falls outside the specified language range according to
standard Unicode sort ordering.

For example, suppose your source data is encoded in the UTF-8 code page and you configure
the session to use a Spanish sort order. The Informatica Server processes all characters in your
source data that fall within the Spanish language range according to the Spanish sort order.
The Informatica Server sorts characters that fall into other language ranges, such as Japanese,
Hebrew, or Greek, according to standard Unicode sort ordering.
Informatica Server Relaxed Code Page Validation

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 using the
Informatica Client code page relaxation features. 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
database code page.
♦ The Informatica Server code page must be the same code page as operating system the
Informatica Server is installed on.
When you run a session with relaxed data code page validation, the Informatica Server writes
the following message to the session log:
LM_2517 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 session, Informatica Server converts source, target, and lookup queries from
the Informatica 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 session 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 Client and Informatica Server allow you to select any supported
code pages, 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 sessions 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 warehouse without inconsistencies. However, if your data contains any characters 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, 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 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
I cannot exit or change the session properties sheet without selecting a compatible sort
order.
Cause: Your Informatica Client is configured to validate data code pages, and only
allows you to select a sort order compatible with the Informatica Server code
page, even though your Informatica Server is configured for relaxed data code
page validation.
Action: Edit the powrmart.ini file to disable data code page validation. For details on
configuring the Informatica Client, “ Configuring the Informatica Client” on
page 28.
The Informatica Server failed a session and wrote the following message to the session log:
TM_6194 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. This can occur if the Informatica Client is configured for relaxed data
code page validation and the Informatica Server is configured to validate data
code pages.
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 27.
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 Miscellaneous tab of the
Informatica Server setup program.

Case Study: Processing 7-bit ASCII Data
This case study describes how you can configure a data warehouse 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 PowerMart/PowerCenter Clients running on Windows 2000 machines
♦ The Informatica Server running on a Windows NT machine
♦ The Informatica repository 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 2-3 illustrates the 7-bit ASCII data environment:
Figure 2-3. 7-bit ASCII Mode Case Study Environment
Lookup Database External Procedures

(7-bit ASCII Data) (7-bit ASCII Data)
Sources Informatica Server Targets

(7-bit ASCII Data) (Windows NT) (7-bit ASCII Data)
Informatica Repository
(Microsoft SQL Server on
Windows NT)
Informatica Clients
(Windows 2000)
Case Study: Processing 7-bit ASCII Data 33

Configuring the 7-bit ASCII Environment
When you configure the globalization properties for this environment, you must follow these
guidelines:
1. Verify Informatica Client and Server code page compatibility.
2. Verify repository database client and 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 Informatica Client and Server Code Page Compatibility

Informatica Client and Server code pages must be compatible. In this case, because the
Informatica Client and 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 and Server use the same code page as the operating system each
is installed on, the Informatica Client and 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 database client and server hosting the Informatica repository 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.

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 Server
Manager always validates session code page relationships when you save a session.
When the Server 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 Server Manager lists all sort orders associated with
the Informatica Server code page. You can select a sort order for the session.
Case Study: Processing 7-bit ASCII Data 35

ASCII Case Study: Summary
Figure 2-4 summarizes the required code page settings for processing 7-bit ASCII data in the
sample data environment:
Figure 2-4. ASCII Case Study Summary
Informatica Server
(Windows NT: MS Windows
Sources Latin1 default) Targets
Set code page in Server
Manager to MS Windows
(Microsoft SQL Server on
Windows NT)
Set the repository code page when
Informatica Clients creating or upgrading repository.
(Windows 2000)

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 Informatica repository installed on a 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.
Case Study: Processing ISO 8859-1 Data 37

The ISO 8859-1 Environment
The data environment must process English and German character data.
Figure 2-5 illustrates the ISO 8859-1 data environment:
Figure 2-5. ISO 8859-1 Case Study Environment

(English Data) (English Data)
Sources
(English Data)
Targets
Informatica Server
(English and
(UNIX)
German Data)
Sources
(German and
English Data)
(Oracle on UNIX)
Informatica Clients
(Windows NT)
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 and 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.

Step 1. Verify Informatica Client and Server Code Page Compatibility
The Informatica Client and Informatica Server code pages must be compatible. Because the
Informatica Client and 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 169. For details on changing the UNIX system code page, see “ UNIX Code
Pages” on page 16.
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 21.
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 13.
The ISO 8859-1 Environment 39

Step 4. Verify Session Code Page Compatibility
When you run a session in Unicode data movement mode, the Informatica Server enforces
source and target code page relationships. For details on code page validation when running
sessions, see “ Informatica Code Page Validation” on page 23.
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 Server 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
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 2-6 summarizes the guidelines set forth in this case study to configure a data warehouse
environment to process ISO 8859-1 data:
Figure 2-6. Summary of ISO 8859-1 Case Study

(English Data) (English Data)
Sources
(English Data) Informatica Server
(UNIX: ASCII default) Targets
Set code page to ISO 8859-1. (English and
Change Data Movement Mode German Data)
to Unicode.
Sources Set code page in Server Manager to
(German and ISO 8859-1.
English Data)
(Oracle on UNIX)
Informatica Clients
(Windows NT)
The ISO 8859-1 Environment 41

Chapter 3
Installing and Configuring

the Informatica Client
♦ Before You Begin, 44
♦ Step 1. Installing ODBC Drivers, 45
♦ Step 2. Installing the Informatica Client Tools, 47
♦ Step 3. Connecting to Databases, 49
♦ Troubleshooting, 61
43
Before You Begin
You need to complete the following steps to install and configure the Informatica Client tools:
1. Install the ODBC drivers.
2. Install 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 NT/2000 or Windows 95/98 boot drive. The Informatica Platform
Setup requires this space for temporary files.
Note: Please read the release notes for any last minute changes to the Informatica Client
installation and connectivity issues.
44 Chapter 3: Installing and Configuring the Informatica Client

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, target, and repository database.
Table 3-1 shows the ODBC drivers to use with each database:
Table 3-1. ODBC Drivers for Source and Target Databases
Database ODBC driver
IBM DB2 IBM ODBC driver
Informix Merant 3.6 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.6 32-bit closed ODBC driver
Sybase Merant 3.6 32-bit closed ODBC driver
Teradata Teradata ODBC driver
Note: The Merant 3.6 32-bit ODBC closed drivers are designed for use with PowerMart and
PowerCenter only. If you use them with other software, they generate warning messages about
violating licensing agreements.
To connect to IBM DB2 on mainframe, use PowerConnect for IBM DB2. Contact your
Informatica sales representative for details.
For a complete description of supported databases and ODBC drivers, see “Using ODBC” on
page 153.
Merant ODBC 3.6 Installation

The Merant 3.6 32-bit ODBC installation is compatible with Informix, Oracle, and Sybase
databases. It includes:
♦ ODBC Administrator
♦ Merant 3.6 32-bit ODBC closed drivers
♦ Uninstall program
If the installation program finds an older version of the driver installed on your system, it
replaces the old driver with the Merant 3.6 32-bit ODBC closed driver. Likewise, if it finds
Step 1. Installing ODBC Drivers 45

an older version of the ODBC Administrator, it automatically overwrites it with the version
included on the Informatica installation CD.
To install Merant 3.6 32-bit ODBC closed drivers:
1. Close all open applications.

2. From Windows NT/2000, or Windows 95/98, run setup.exe, located on the Informatica
installation CD.
The Welcome screen displays.
3. Click Next.
4. Select ODBC and click Next.
The program launches the ODBC installation.
5. Click Next.
6. Select the type of installation.
7. Click Next.
The program installs the ODBC 3.6 drivers.
8. Click Finish when the installation completes.
After you install the Merant 3.6 32-bit ODBC closed drivers, you need to create an ODBC
data source for each database accessed by the client tools. Refer to the appropriate section in
this chapter for details on connecting to databases.
Uninstalling Merant ODBC 3.6 Drivers

The Merant uninstall program deletes only the Merant 3.6 32-bit ODBC closed drivers
installed from the Informatica installation CD.
To uninstall the Merant 3.6 32-bit ODBC closed drivers:
1. Open the Windows Control Panel.

2. Select Add/Remove programs.
3. Select ODBC 3.6 and click Add/Remove.
A message prompts you to remove these ODBC drivers.
4. Click OK to uninstall the Merant 3.6 32-bit ODBC closed drivers.

Step 2. Installing the Informatica Client Tools
You can install the Informatica Client tools on either a Windows 95/98 or Windows NT/
2000 system.
The installation program provides a complete installation and a custom installation. The
complete installation installs the following:
♦ All the program files you need to run the Designer, Repository Manager, and Server
Manager, the sample repository, and the SQL scripts for the hands-on tutorials included in
Getting Started
♦ pmrep, the repository command line program
♦ Release notes
♦ Online help file for the Designer, Repository Manager, and Server Manager
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 PowerMart 5.1 or PowerCenter 5.1. You should upgrade the copy of your
existing repository so you can evaluate it without altering your existing repository.
Note: For Windows NT/2000, 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 NT, Windows 2000, or Windows 95/98, run setup.exe, located on the
Informatica installation CD.
The Welcome screen displays.
Note: If installing from your network, the Windows NT/2000 system must be mapped to
the root directory of the CD to run the setup program.
3. Click Next.
4. Select Client.
5. Click Next to launch the client installation.
6. Select the type of setup you want to perform. If you have a client tools already installed
on your machine, you can choose to uninstall or reinstall the client tools.
7. Choose the directory where you want to install the Informatica Client tools.
8. Click Next.
9. Specify the program folder in which the client icons will appear.
10. Click Next.
11. Select the components you want to install. By default, all components are selected.
Step 2. Installing the Informatica Client Tools 47

Table 3-2 describes the components you can install:
Table 3-2. Informatica Client Components
Component Description
Program and Configuration Files The files required to run and configure the Informatica Client.
Documentation Files Informatica product manuals in PDF format.
Tutorial Files Sample SQL scripts you can use to create the source and target tables
used in the tutorial lessons in Getting Started.
Sample Repository A sample repository file, stored in an .rep backup file.
12. Click Next.

13. The PowerMart/PowerCenter Client Tools Setup copies the selected components to your
installation directory.
14. When the installation completes, select Disable Data Code Page Validation if you want to
relax data code page validation restrictions.
15. Select View Readme if you want to read the PowerMart/PowerCenter release notes.
16. Click Finish to exit the Client Tools Setup.
17. If you installed the client tools only, click Finish to exit the Informatica Platform Setup
and return to Windows.

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, target, and repository
database.
Note: These steps are provided as a guideline. For specific connectivity instructions, refer to
your database documentation.
Net8 and SQL*Net 2.3.4

If your data warehouse includes a mix of Oracle 7 and Oracle 8, and Oracle 8i databases, you
can use SQL*Net 2.3.4, Net8, or Net8i. You must install the same version of the Oracle
Client on each machine hosting the Oracle database server and Informatica Server.
If your data warehouse includes Oracle 8i and Oracle 8 databases, install Net8 or Net8i on
each machine hosting the Oracle database server and Informatica Server.
Also, when you configure the Informatica Server, you must choose between SQL*Net 2.3.4
and Net8 or Net8i. If you install SQL*Net 2.3.4, set the Oracle Version parameter in the
Informatica Server configuration to Oracle 7. If you install Net8 or Net 8i, set the Oracle
Version parameter to Oracle 8.
Using SQL*Net 2.3.4

Use the following steps as a guideline to connect to an Oracle database through SQL*Net
2.3.4. For specific connectivity instructions, refer to your database documentation.
Note: The Informatica Server on HP-UX does not support SQL*Net 2.3.4.
To connect to an Oracle database with SQL*Net 2.3.4:
1. Install the SQL*Net 2.3.4 software.

Install the same version of SQL*Net on the machine hosting the Informatica Client,
Oracle database, and Informatica Server. If you have different versions of SQL*Net
installed, you may experience difficulties reading from and writing to the database.
2. Configure the Oracle client. You can use the SQL*Net Easy Configuration 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.
Step 3. Connecting to Databases 49

Use TCP/IP as the network protocol. PowerMart and PowerCenter 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 server instance ID defined on the Oracle
server.
3. Verify that the system path includes the Oracle bin directory.
For example, if you install SQL*Net on a Windows 95/98 system, your path might
include the following entry:
C:\ORAWIN95\BIN
4. Launch SQL*Plus and 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.6 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 Server Manager, create a database connection for each source and target database.
See “Configuring the Server Manager” in the Session and Server Guide.

Using Net8
Use the following steps as a guideline to connect to an Oracle database through Net8. For
specific connectivity instructions, refer to your database documentation.
To connect to an Oracle database with Net8:
1. Install the Net8 software.

2. Configure the Oracle client. You can use the Net8 Utility or copy an existing
TNSNAMES.ORA and SQLNET.ORA file and modify it as needed.
Enter the correct syntax for the Oracle connect string, typically: databasename.world.
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(Host =mymachine)
(Port = 1521)
)
(CONNECT_DATA =
(SID = MYORA7)
Make sure the SID entered here matches the database server instance ID defined on the
Oracle server.
For example, if you install Net8 on a Windows 95/98 system, your path might include
the following entry:
C:\ORAWIN95\BIN
4. Launch SQL*Plus and try to connect to the database.


5. Create an ODBC connection for each Oracle database.
Use the Merant 3.6 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.
See “Configuring the Server Manager in the Session and Server Guide.
7. On Oracle 8 and 8i databases, if the database character set is not the default, configure
the database to use the U.S. English character set:
On Windows NT/2000 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.
On Windows 95/98, add the following entry to the autoexec.bat file:
SET NLS_LANG=american_america.UTF8
Connecting to a Microsoft SQL Server Database

Use the following steps as a guideline to connect each Microsoft SQL Server database (source,
target, or repository) to the Informatica Client tools, complete the following steps. For
For Microsoft SQL Server 6.5, install the SQL Client version 6.5x. Do not use the Merant
driver included on the Informatica installation CD.
For Microsoft SQL Server 7.0, install the SQL Client version 7.x and the SQL Server Service
Pack 1 on each client, server, and repository machine. Do not use the Merant driver included
on the Informatica installation CD.
Microsoft SQL Server version 7.0 is backward-compatible with Microsoft SQL Server 6.5. If
your data warehouse includes both Microsoft SQL Server 6.5 and 7.0 database, use the SQL
Client version 7.0. Do not use the Microsoft SQL Server 6.5 client with a Microsoft SQL
Server 7.0 database, as it can cause inconsistent data in the repository.
To connect to a Microsoft SQL Server database:
1. Install the SQL Client software.

Be sure to install DB Library.
2. Verify that the system path includes the Microsoft SQL Server directory.
For example, if you install SQL Client on a Windows 95/98 system, your path might
include the following entry:
PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
If your path does not include the Microsoft SQL Server directory, edit your
AUTOEXEC.BAT file.

3. Open the SQL Client Configuration Utility. In the Net-Library window, verify that the
Default Network matches the default network for your Microsoft SQL Server database
(usually TCP/IP sockets).
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 database.

Use the Microsoft SQL Server 32-bit ODBC driver supplied with your database. See
“Using ODBC” on page 153.
For Microsoft SQL Server 6.5 repositories, clear the Generate Stored Procedure for
Prepared Statement option in the SQL Server ODBC driver configuration Advanced
Option dialog box.
For Microsoft SQL

Server 6.5
repositories, clear
Generate
Stored Procedure
for Prepared
Statement.

For Microsoft SQL Server 7.0 repositories, clear the Create temporary stored procedures for
prepared SQL statements option in the Create a New Data Source to SQL Server dialog
box.
For Microsoft SQL

Server 7.0
repositories, clear
Create temporary
stored procedures
for prepared SQL
statements and
drop the stored
procedures.
If you have difficulty clearing the temporary stored procedures for prepared SQL
statements options, see the Informatica Webzine for more information about configuring
SQL Server 7.0. You can access the webzine at http://www.informatica.com/webzine.
For more information, see “Configuring the Server Manager” in the Session and Server
Guide.
Connecting to a Sybase SQL Server Database

Use the following steps as a guideline to connect each Sybase SQL Server database (source,
target, or repository) to the Informatica Client tools. For specific connectivity instructions,
refer to your database documentation.
To connect to a Sybase SQL Server database:
1. Install the Open Client 11.1.1 software.

Install the same version of Open Client on the machine hosting the Informatica Client,
Sybase database, and 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 95/98 system, your path might
have the following entry:
PATH=C:\SYBASE\BIN;C:\SYBASE\DLL
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. Be sure you use the correct connect
string. The syntax is servername@dbname (for example, myserver@sybasedb).
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 153.
For Sybase repositories using the Merant 3.6 Sybase driver, set the Prepare Method
option to 2-Full as shown below:
Set Prepare Method to 2-Full
Note: This setting is required for Sybase repositories.
For details on creating source and target database connections, see “Configuring the
Server Manager” in the Session and Server Guide.

Connecting to an Informix Database
Use the following steps as a guideline to connect each Informix database (source, target, or
repository) 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 3-3 describes the options available in the Server Information tab:
Table 3-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.
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 95/98: %WINDIR%\Services
Windows NT/2000: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr 1525/tcp
In the Host tab, enter the following information for each Informix server:
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.
4. Verify that the system path includes the %INFORMIXDIR%\bin directory.

For example:
PATH=%INFORMIXDIR%\bin;%PATH%
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 NT/2000, 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
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 database.
Install the Merant 3.6 32-bit ODBC closed driver included on the Informatica
installation CD. For details, see “Using ODBC” on page 153.
Once you complete this step, you can use Repository Manager to create a repository.
Guide.
Connecting to an IBM DB2 Universal Database

Use the following steps as a guideline to connect each DB2 database on Windows NT/2000
or UNIX to the Informatica Client tools, complete the following steps. For specific

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. Check
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.
Guide.

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.
Guide.
Connecting to Microsoft Excel

PowerMart and PowerCenter 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.
Choose the
Microsoft Excel
version
Click Select Workbook to browse
for the Microsoft Excel source
9. Click OK to exit the ODBC Administrator.

Guide.
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. Add the following entry to the powrmart.ini file under the [ODBCDLL] heading in each
Informatica Client machine:
TERADATA=PMODBC.DLL
2. Install WinDDI, Teradata Client, Teradata ODBC driver, and any other Teradata
software you might need.
3. Launch the ODBC 32-bit Data Source Administrator by selecting ODBC Data Sources
from the Control Panel.
4. From the ODBC Data Source Administrator, create and configure ODBC data sources.
5. To create a data source name (DSN), click the System DSN tab, and click Add.
6. Select the Teradata ODBC driver, and click Finish.
7. 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.
8. 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 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.
On Windows 95/98, add the following entry to the autoexec.bat file:
SET NLS_LANG=american_america.UTF8
Troubleshooting 61
Chapter 4
Creating a Repository

♦ Overview, 64
♦ Creating a Repository, 65
♦ Tips, 67
63
Overview
After you install and configure the Informatica Client, you can create a repository. A
repository contains metadata the Informatica Server uses to move and transform data from
sources to targets.
Use the Repository Manager client application to create and administer the repository. The
Repository Manager uses ODBC to connect to databases, so you must configure the necessary
data sources (DSN) 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 corrupted data that is caused by customer alteration
of the repository tables or data within those tables.
64 Chapter 4: Creating a Repository

Creating a Repository
Before you can create a repository, you must first create and configure the database to contain
the repository. 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, Windows 2000, or UNIX operating system
♦ 70 MB disk space (70-130 MB is recommended)
When you create a repository, you must have the following information available:
♦ Data source to connect to the database.
♦ 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.
Since IBM EBCDIC US English code page is compatible with Latin1, it appears as a code
page selection. However, you cannot install the Informatica Client, Server, or repository
on mainframe systems, so do not select IBM EBCDIC as a code page for a repository.
For more information on code pages, see “Globalization Overview” on page 9.
Do not use the following characters when creating a repository name:
\ / : * ? < > " | .
To create a repository:
1. Launch the Repository Manager and choose Repository-Create Repository.
Creating a Repository 65
2. Enter the repository parameters.
Table 4-1 describes the options available in the Create Repository dialog box:
Table 4-1. Create Repository Parameters
Create Repository Required/

Description
Parameter Optional
Repository Name Required Name for the new repository. Each repository name must be
unique within the domain and easily distinguished from all other
repositories.
Database Username Required Username required to connect to the database. This login must
have the appropriate database permissions to create the
repository.
Database Password Required Password associated with the database username. Must be in
US-ASCII.
ODBC Data Source Required Data source used to connect to the database.
Native Connect String Required Connect string identifying the location of the database. For a list
of native connect strings, see Table 1-4 on page 5.
Code Page Required Character set associated with the repository. Must be
compatible with the Informatica Client and Server. The
Repository Manager displays only code pages that are
compatible with the Informatica Client.
After creating the repository, you cannot change the repository
code page.
3. Click OK.
4. The Repository Manager begins building the repository. You can see the progress in the
Output window.
5. 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 if you want to create a global repository, click No. You can promote an existing local
repository to a global repository later.

Tips
The following tip helps 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 warehouse
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.
Tips 67
Chapter 5
Installing and Configuring

the Informatica NT Server
♦ Step 1. Installing the Informatica NT Server, 73
♦ Step 2. Configuring the Informatica NT Server, 75
♦ Step 4. Starting and Stopping the Informatica Server, 95
69
Before You Begin
Complete the following steps to install and configure the Informatica Server on Windows
NT/2000:
1. Install the Informatica Server.
2. Configure the Informatica Server.
3. Configure database connectivity for the repository, source, and target databases.
4. Register the Informatica Server in the Server Manager.
See the release notes for last minute changes to the installation.
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select in each component of PowerMart and PowerCenter are compatible with each other. For
more information, see “Globalization Overview” on page 9.
DHCP (TCP/IP Connections Only)

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 Server Manager 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 Server Manager. If,
in the TCP/IP Setup dialog box, the Host Name field contains an IP address, enter the new
IP address the DHCP Informatica Server assigned to the Informatica Server. If the Host
Name field contains a name, click OK to save the existing information and configure the
Server Manager to update the new IP address.
If the Informatica Server machine has multiple network cards, after starting the Informatica
Server, re-register the Informatica Server with the Server Manager, entering the desired IP
address for the Informatica Server.
70 Chapter 5: Installing and Configuring the Informatica NT Server

Installation Guidelines
Use the following guidelines before you install the Informatica Server on a Windows NT/
2000 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 sessions and batches run when you expect. The
Server 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 NT/2000. To
verify this, select Start-Settings-Control Panel, double-click the Regional Settings icon,
and click the Date tab.
3. Make sure you have 30 MB of disk space available on the Windows NT/2000 or
Windows 95/98 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 NT/2000 system, you need four
different user accounts:
1. Windows NT/2000 user with administrator rights. To install the Informatica Server, log
on to the Windows NT/2000 system as a member of the Administrators group in the
local domain.
2. Windows NT/2000 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 post-session email or access
a repository on a Microsoft SQL Server database that uses Windows NT/2000 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 NT/2000 account.
4. Database user. When you configure the Informatica Server, 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
Before You Begin 71

repository database. This user is not a Windows NT/2000 or repository account. The
password must be in US-ASCII only.
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
All sessions and batches configured to run on the registered Informatica Server use these
directories by default. For details, see “Registering the Informatica Server” on page 133.
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. Installing the Informatica NT Server
After you create a repository database and an ODBC data source, install the client tools, and
create a repository, you can install the Informatica Server.
You can install only one Informatica Server on a Windows NT/2000 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 NT/2000 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 NT/2000 system to the
root directory of the CD to run the setup program.
3. Click Next.
4. Select Server.
5. Click Next.
The Server setup application starts.
6. Click Next.
7. When the Edit Service Account dialog box appears, enter the Service Start Account
information for the Informatica service.
Table 5-1 describes the options available in the Edit Service Account dialog box:
Table 5-1. Installation Parameters for Informatica Server on Windows NT/2000
Required/
Option Description
Optional
Domain Optional The domain for the Windows NT/2000 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 NT/2000 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 Required The password for the Service Start Account.

Password
Step 1. Installing the Informatica NT Server 73

8. If you are upgrading, the installation program prompts you to update the installed
version. Click Yes to update or No to cancel the installation.
The update removes the current installation, but preserves existing configuration settings.
9. When prompted, select the directory where you want to install the Informatica Server.
Click Next.
You can either select an existing directory or have the installation program create a new
directory.
10. When the setup application finishes copying files, select View Readme if you want to
read the readme file. Select Configure Informatica Service if you want to configure the
Informatica Server.
For details on configuring the Informatica NT Server, see “Step 2. Configuring the
Informatica NT Server” on page 75.
11. Click Finish to exit the PowerMart/PowerCenter Server Setup.
12. If the Informatica Server is the only platform component you wish to install, click Finish
to exit the Informatica Platform setup and return to Windows.

Step 2. Configuring the Informatica NT 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
Server 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 session, you need to complete the following tasks in the Server Manager:
♦ Register the Informatica Server in the repository.
♦ Configure the source and target database connections.
For details, see “Registering the Informatica Server” on page 133.
Note: ODBC databases, such as Microsoft Access97 and Excel, are compatible with the
Informatica Server on a Windows NT/2000 system. However, they are not compatible with
the Informatica Server installed on a UNIX system.
To configure the Informatica Server on Windows NT/2000:
1. If the configuration screen is not displayed from the installation, choose Programs-
Informatica Server-Informatica Server Setup from the Windows NT/2000 Start Menu.
2. Select the Configure Informatica Service option and click Continue.
Step 2. Configuring the Informatica NT Server 75

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.
Table 5-2 describes the options available in the Keys Tab:
Table 5-2. Keys Configuration for Informatica Server on Windows NT/2000
Required/
Option Description
Optional
Platform Key Required The Windows NT/2000 platform key. Required when you
install the Informatica Server on a Windows NT/2000
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.

Table 5-2. Keys Configuration for Informatica Server on Windows NT/2000
Required/
Option Description
Optional
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.
4. Click the Network tab.
Select the network protocol (TCP/IP or IPX/SPX) the Server Manager uses to access the
Informatica Server across a network, as well as the address of the machine on which it is
running.

Table 5-3 describes the options available on the Network tab:
Table 5-3. Network Configuration for Informatica Server on Windows NT/2000
Required/
TCP/IP Option Description
Optional
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.
TCP/IP Port Number Required If you select TCP/IP, enter the port the Informatica Server
uses. Only the Informatica Server can use this port. Make
sure no other services on the system use this port.
Required/
IPX/SPX Option Description
Optional
IPX/SPX Address Required The IPX/SPX address for the host. This is a dotted, three-
part hexadecimal string, such as
12345678.00A0420AE743.4001. The first 8 digits are the net
number, the next 12 digits are the node number, and the last
4 digits are the socket number.
5. Click the Repository tab.

Table 5-4 describes the options available on the Repository tab:
Table 5-4. Repository Configuration for Informatica Server on Windows NT/2000
Required/
Option Description
Optional
Repository Name Required The name of the repository when it is created in the Repository
Manager.
Database Type Required The type of database containing the repository. All supported
databases appear in the list, but the Informatica Server only
accesses databases that have a valid license entered in the Keys
tab.
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.
Database User Required The account for the database containing the repository. This
account is set up using the appropriate database client tools.
Database Password Required The repository database password corresponding to the database
user. Must be in US-ASCII only.
Connect String Required The native connect string that the Informatica 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 ODBC sources, such as Microsoft
Access and Microsoft Excel, the connect string must match the
ODBC data source name on the Informatica Server machine. For a
list of native connect string syntax for supported RDBMS sources,
see Table 1-4 on page 5.
Domain Optional/ The Windows NT domain of the user specified in the Database
Microsoft User field. Enter the domain for the user specified in the Database
SQL Server User field only if the repository is stored in a Microsoft SQL Server
repository database that uses Windows NT integrated security.
only
Use Trusted Connection Optional/ If selected, the repository uses Windows NT integrated security. If
Microsoft you select this option, verify the following:
SQL Server - The database user must be a Windows NT/2000 user.
repository - The database password is the correct Windows NT/2000
only password for the user.
- The domain entered in the Domain field is the user Windows NT/
2000 domain.
The Informatica Server uses this information to log on to the
Microsoft SQL Server. Note that if you select this option, you must
run the SQL Client Configuration utility and specify Multi-Protocol
as the Default Network on the Net Library property page.

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 5-5 describes the options available on the Compatibility and Database Tab:
Table 5-5. Compatibility and Database Configuration for Informatica NT Server
Required/
Setting Description
Optional
PMServer 3.X Optional If selected, the Informatica Server handles Aggregator

aggregate transformations as it did in PowerMart 3.x. This overrides both
compatibility 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 Optional If selected, the Informatica Server treat nulls as zero in Aggregator
as zero transformations. If you do not select this option, the Informatica
Server treats nulls as nulls in aggregate calculations.

Required/
Setting Description
Optional
Aggregate treat rows Optional If selected, the Informatica Server performs aggregate calculations
as insert 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 Optional If selected, the Informatica Server handles dates as in PowerMart 4.0/
handling compatibility PowerCenter 1.0. If not selected, the Informatica Server handles
dates as defined in PowerMart 5.1/PowerCenter 5.1.
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 Optional Valid for Microsoft SQL Server sources. If selected, the Informatica
on read Server does not trim trailing spaces from the end of Char source
fields. Do not select this option if you want to retain extra spacing in
Char fields. This option is selected by default.
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.*
Oracle Version Optional Select Oracle 7 to use the SQL*Net 2.3.4 driver. Select Oracle 8 to
use Net8 driver. See “Connecting to Oracle” on page 85 for more
details on Oracle driver configuration.
Max LKP/SP DB Optional Allows you to specify a maximum number of connections to a lookup
Connections 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.
By default, this value is not specified.
Max Sybase Optional Allows you to specify a maximum number of connections to a Sybase
Connections 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 Optional Allows you to specify a maximum number of connections to a

Connections 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. By default, this value is set to 100.
Number of Deadlock Optional Allows you to specify the number of times the Informatica Server
Retries retries a target write on a database deadlock. By default, this value is
set to 10.

Required/
Setting Description
Optional
Deadlock Sleep Optional Allows you to specify the number of seconds before the Informatica
Before Retry Server retries a target write on database deadlock. By default, this
(seconds) 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 People Soft User and Administrator Guide.
7. Click the Miscellaneous tab.
Enter additional miscellaneous Informatica Server configuration settings.

Table 5-6 describes the options available on the Miscellaneous tab:
Table 5-6. Miscellaneous Configuration for Informatica Server on Windows NT/2000
Required/
Setting Description
Optional
Max Sessions Required The maximum number of sessions stored in shared memory. This also
sets the maximum number of sessions that you can view in the Server
Manager Monitor mode. Increase this value only if you have sufficient
shared memory. Default is 10.
Load Manager Required The amount of shared memory available for use by the Informatica
Shared Memory 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.
MS Exchange Optional MS Exchange profile used by the Service Start Account to send post-
Profile session email. The Service Start Account must be set up as a Domain
account to use this feature.
Shared Memory Optional If this parameter is set to the default value of 0x00000000, the Load
Base Address Manager allows Windows NT/2000 to set the base address of shared
memory. When the DTM starts, Windows NT/2000 sometimes maps
executable code to this same base address. When the DTM
subsequently tries to map shared memory to this same address, it fails
because the address is already occupied by the executable code. In
these situations, you can set the address to another value. Valid values
are strings representing 32-bit hexadecimal numbers, such as
0xABCD0010. Windows NT/2000 then sets the base address of shared
memory to the specified value, rounded down to the next memory
granulation boundary.
Stay Connected for Required The Load Manager holds the connection to the repository for the value
(secs) set in the Informatica Server configuration, Stay Connected for (secs).
By default, this time is 300 seconds, or 5 minutes. Each time the Load
Manager communicates with the repository, the Load Manager verifies if
the connection duration is expired. If the duration is expired, the Load
Manager disconnects and reconnects to the repository. If the duration is
not expired, the Load Manager uses the same connection and resets the
connection time to the full duration.
Date Display Required If specified, the Informatica Server validates the date display format and
Format 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.
Data Movement Required Choose ASCII or Unicode. The default data movement mode is ASCII,
Mode which passes US-ASCII character data. To pass 8-bit ASCII and
multibyte character data from sources to targets, use Unicode mode.
Perform Event Optional Select to include detailed event logging in the system event log. If this is
Logging not selected, standard logging is still performed and logged to the event
log.

Table 5-6. Miscellaneous Configuration for Informatica Server on Windows NT/2000
Required/
Setting Description
Optional
Override Exec Optional If selected, the Informatica Server ignores any session or batch execute
Locking locks. If you run a session that is already running or has a lock from a
previously failed session, the Informatica Server ignores the lock and
runs the session anyway. This option should only be selected in
development, since problems can arise running simultaneous sessions.
Disable Recovery Optional If selected, the Informatica Server does not create the recovery table
(OPB_SRVR_RECOVERY) in the target database. Also, the Informatica
Server does not record recovery information from the session it is
running, even if the OPB_SRVR_RECOVERY exists in the target
database. If selected, Perform Recovery in the Server Manager has no
effect.
If not selected, the Informatica Server enables recovery.
This option is enabled by default.
Keep Repeating Optional The Keep Repeating Sessions option determines the action the Load
Sessions In LM Manager takes when there are no available slots when a session start
Shared Memory time arrives. By default, this option is disabled. When this option is
disabled, the Load Manager moves repeating sessions out of session
slots to run new session requests. If all session slots are occupied with
active sessions, the Load Manager places new session requests in a
waiting state until a session slot becomes available. If you enable this
option, the Load Manager retains repeating sessions in shared memory,
and fails to run new session requests.
Load Manager Optional If selected, you can run the debugger. This option is enabled by default.
Allow Debugging
Create indicator Optional If enabled, the Informatica Server creates indicator files when you run a
files for target flat session with a flat file target.
file output
Warn about Optional If enabled, the Informatica Server writes duplicate row warnings and
duplicate XML rows duplicate rows for XML targets to the session log. By default, this option
is enabled.
Validate Data Code Required If you enable this option, the Informatica Server enforces data code page
Pages 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. By default, this option is enabled.
Session Log In Required If you enable this option, the Informatica Server writes to the session log
UTF8 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.
By default, this option is disabled.
8. Click OK to save the configuration options. Click Exit to close the Server Setup dialog
box.

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 repository, 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, target, and repository
databases, use 32-bit database client libraries only.
Informatica Servers running on a Windows NT/2000 machine can use ODBC to connect to
databases. For more information on ODBC connections, see “Using ODBC” on page 153.
Connecting to Oracle
You need to connect each Informatica Server to each Oracle source, target, and repository
database.
SQL*Net 2.3.4 and Net8

If your data warehouse includes a mix of Oracle 7, Oracle 8, and Oracle 8i databases, you can
use SQL*Net 2.3.4, Net8, or Net8i. You must install the same version of the Oracle Client on
each machine hosting the Oracle database server and the Informatica Client and Server.
Using SQL*Net 2.3.4

Use the following steps as a guideline to connect to an Oracle database through SQL*Net
2.3.4. For specific connectivity instructions, refer to your database documentation.
To connect to an Oracle database with SQL*Net 2.3.4:

You must install the same version of SQL*Net on the machine hosting the Informatica
Client, Oracle database, and Informatica Server. If you have different versions of
SQL*Net installed, you may experience difficulties reading from and writing to the
database.

2. Configure the Oracle client. You can use the SQL*Net Easy Configuration Utility or
copy 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.
Here is a sample TNSNAMES.ORA:
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
(CONNECT_DATA =
(SID = MYORA7)
server.
For example, if you install SQL*Net, your path might include the following entry:
C:\ORAWIN95\BIN

You must use the correct connect string (as defined in TNSNAMES.ORA) and
username. Make sure SQL*Plus connects correctly before continuing.
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 NT Server” on page 75.

Using Net8
Follow these steps to connect to an Oracle database through Net8. These steps are provided as
a guideline. For specific connectivity instructions, refer to your database documentation.
To connect to an Oracle database with Net8:

2. Configure the Oracle client. You can use the Net8 Utility or copy an existing
TNSNAMES.ORA and SQLNET.ORA files and modify them as needed.
<oracle_home>\NET80\ADMIN directory.
Enter the correct syntax for the Oracle connect string, typically databasename.world.
You must use TCP/IP as the network protocol. PowerMart and PowerCenter 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)
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.
Connecting to Microsoft SQL Server

Use the following steps as a guideline to connect each Microsoft SQL Server database (source,
target, or repository) to the Informatica Client tools. For specific connectivity instructions,
refer to your database documentation.
For Microsoft SQL Server 6.5, install the SQL Client version 6.5x. Do not use the Merant
driver included on the Informatica installation CD.
For Microsoft SQL Server 7.0, install the SQL Client version 7.x and the SQL Server Service
Pack 1 on each client, server, and repository machine. Do not use the Merant driver included
on the Informatica installation CD.
Microsoft SQL Server version 7.0 is backward-compatible with Microsoft SQL Server 6.5. If
your data warehouse includes both Microsoft SQL Server 6.5 and 7.0 database, use the SQL
Server Client version 7.0. Do not use the Microsoft SQL Server 6.5 client with a Microsoft
SQL Server 7.0 database, as it can cause inconsistent data in the repository.
To connect to a Microsoft SQL Server database:
1. Install the SQL Client software and the DB Library.

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%
3. Open the SQL Client Configuration Utility. In the Net-Library window, verify that the
Default Network matches the default network for your Microsoft SQL Server database,
usually TCP/IP sockets.
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 may be case-sensitive.
Connecting to Sybase
Use the following steps as a guideline to connect to a Sybase database. For specific

To connect to a Sybase database:
1. Install the Open Client software.

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
name and port number, check with your system administrator.
3. Verify that the SYBASE environment variable refers to the Sybase directory.
For example:
SYBASE=C:\SYBASE

For example, if you install Open Client on a Windows NT/2000 system, your path might
have the following entry:
PATH=C:\SYBASE\BIN;C:\SYBASE\DLL
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.
Usernames and database names may be case-sensitive. Use the correct connect string. The
syntax is servername@dbname.
Connecting to Informix
Use the following steps as a guideline to connect to an Informix database. For specific
On Windows NT/2000, 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).
1. Install the ESQL for C, Informix Client SDK, or any other Informix client software.

Install compatible versions of ESQL/runtime or iconnect on machines hosting the
Informatica Client and 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, enter the server connectivity information for
each server.
Table 5-7 describes the options available on the Server Information tab:
Table 5-7. 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.
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 95/98: %WINDIR%\Services
Windows NT/2000: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr 1525/tcp
On the Host tab, enter the host connectivity information for the Informix Server:
Setting Description
Current Host Name of the host where Informix server is running.
User Name User name for the Informix server.
Password Option Password.
Password Password for the Informix server.
4. Verify that the system path includes the %INFORMIXDIR%\bin directory.

For example:
PATH=%INFORMIXDIR%\bin;%PATH%
If your path does not include the Informix directory, edit your AUTOEXEC.BAT file.

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 NT/2000, 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
information about connecting to an Informix database, refer to your Informix
documentation.
Usernames and database names are case-sensitive. Enter the correct connect string. The
syntax is dbname@servername (for example, informixdb@myserver).
Connecting to IBM DB2 Universal Database

Use the following steps as a guideline to connect to an IBM DB2 Universal Database. For
To connect to an IBM DB2 database:
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 (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 NT/2000. 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.
♦ 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.
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

PowerMart and PowerCenter 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 Server 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.
Choose the
Microsoft Excel
version
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.
Connecting to a Teradata Source Database

The Informatica Server on Windows NT/2000 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 NT/2000 as the
advanced NT/2000 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 NT/2000 Control Panel (start and stop the Informatica Server)
♦ Server Manager (stop the Informatica Server)
♦ Command line program pmcmd (stop the Informatica Server)
Before you can start the Informatica Server, you must register it in the Server Manager. If you
are running the Informatica Server for the first time, edit the temp_server temporary server.
For more information, see “Registering the Informatica Server” on page 133.
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 sessions and batches scheduled to run in the future. It then attempts to stop all running
sessions and batches. If any sessions or batches fail to respond within a certain period of time,
the Informatica Server aborts the remaining sessions and batches. Allow 1 to 2 minutes for the
Informatica Server to complete all processes. When you restart the Informatica Server, you
must reschedule all sessions and batches.
Windows NT/2000 Control Panel

You can start the Informatica Server from the Windows NT/2000 control panel.
To start the Informatica Server:
1. Verify that the repository database is running.

2. In the Server Manager, verify the Informatica Server is registered in the repository.
If the Informatica Server is not registered in the repository, use the Server Manager to
register it.
3. Log on to the Windows NT/2000 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 NT/2000 machine, select
Informatica.
7. Click Start.
The Informatica Server might take a moment to start.
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 are
available at boot time from the host.
Step 4. Starting and Stopping the Informatica Server 95

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:
Event LM 2003
displays if the
Informatica
Server
successfully
starts
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 99 for possible solutions. Also see the
Troubleshooting Guide for more information.
To stop the Informatica Ser ver:
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 Ser ver:
1. From Windows NT/2000, 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 opens the repository. If this 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.
Server Manager
With the Server Manager, you can stop the Informatica Server. However, you must first
configure the Server Manager to communicate with the Informatica Server.
You must also have the following privileges:
♦ Super User or Administer Server
♦ Create Session and Batches
If the Informatica Server is listed in Server Manager, choose Server Requests-Stop Server. In
the Output window, you should see the following text:
Request to stop server PRODUCTION.
Server acknowledged the request to stop itself.
Command Line Program (pmcmd)

When you send a request to stop the Informatica Server, the Informatica Server first
unschedules all sessions and batches scheduled to run in the future. It then attempts to stop
all running sessions and batches. If any sessions or batches fail to respond within a certain
period of time, the Informatica Server aborts the remaining sessions and batches. Allow up to
Step 4. Starting and Stopping the Informatica Server 97

two minutes for the Informatica Server to complete all processes. When you restart the
Informatica Server, you must reschedule all sessions and batches removed from the schedule.
You can use the command line program pmcmd to stop the Informatica Server. The basic
syntax is as follows:
pmcmd stopserver {user_name | %user_env_var}
{password | %password_env_var}
{[TCP/IP:][hostname:]portno | IPX/SPX:ipx/spx_address}
For more details on using pmcmd, see “Using pmcmd” in the Session and Server Guide.

Troubleshooting
This section contains information on troubleshooting the Informatica Server on Windows
NT/2000.
I installed the Informatica Server on a Windows NT 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 NT 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 NT system. Follow these steps to verify that the account with proper rights also
starts the Informatica Server.
1. In the Windows NT Control Panel, double-click the Services icon.
2. In the Services dialog box, double-click Informatica.
The following dialog box appears:
3. Select This Account, and enter the account name and password assigned to the
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.
Troubleshooting 99
In addition, verify the connectivity settings you specify in the Informatica Server Setup and
the Server dialog box in the Server 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, database
username and password for the repository database, and repository username and
password to start.
2. Make sure you registered the Informatica Server in the Server Manager. If you are
installing and starting the Informatica Server for the first time, edit the temp_server
temporary server automatically created in the Server Manager.
3. Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Server Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
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:
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.
Troubleshooting 101
Use the following steps to verify that the account with the right to log on as a service also
starts the Informatica service:
1. In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2. Double-click the Services icon.
3. In the Services dialog box, double-click Informatica.
The Informatica Properties dialog box appears.
4. Open the Log On tab.
5. Select This Account, and enter the account name and password assigned to the
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 Server 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, database
username and password for the repository database, and repository username and
password to start.
2. Make sure you registered the Informatica Server in the Server Manager. If you are
installing and starting the Informatica Server for the first time, edit the temp_server
temporary server automatically created in the Server Manager.

3. Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Server Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
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 access the repository. See “Step 3. Connecting to Databases” on
page 85 for details.
The Server 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 Server 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.
Troubleshooting 103
Chapter 6
Installing and Configuring the

Informatica UNIX Server
♦ Step 1. Installing the Informatica Server, 107
♦ Step 2. Configuring the Informatica Server on UNIX, 109
♦ Step 4. Starting and Stopping the Informatica Server on UNIX, 125
♦ Installing and Configuring ODBC for UNIX, 127
105
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, target, and
repository database.
4. Register the Informatica Server in the Server Manager.
Please read the chapter “Installation and Configuration Overview” on page 1 before installing
the Informatica Server.
See the release notes for last minute changes to the installation.
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select in each component of PowerMart and PowerCenter are compatible with each other. For
more information, see “Globalization Overview” on page 9.
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 Server Manager so the client can communicate
with the Informatica Server at its 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 Server Manager. If,
in the TCP/IP Setup dialog, the Host Name field contains an IP address, enter the new IP
address the DHCP Informatica Server assigned to the Informatica Server. If the Host Name
field contains a name, click OK to save the existing information and configure the Server
Manager to update the new IP address.
If the machine hosting the Informatica Server has multiple network cards, after starting the
Informatica Server, reregister the Informatica Server with the Server Manager, entering the
desired IP address for the Informatica Server.
106 Chapter 6: Installing and Configuring the Informatica UNIX Server

Step 1. Installing the Informatica Server
After you create a repository database and an ODBC data source, install the client tools, 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.
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 6-1 describes the library paths for different UNIX operating systems:
Table 6-1. Library Path for Informatica Server on UNIX
Operating System Library Path
Solaris LD_LIBRARY_PATH
AIX LIBPATH
HP SHLIB_PATH
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. Select PowerCenter Server from the list of components available to install.
7. Enter the absolute target directory path where you want to install the Informatica Server.
8. The installation program now extracts and installs the files. The upgrade preserves your
configuration settings.
Step 1. Installing the Informatica Server 107

9. When the installation completes, type Y to configure the Informatica Server, or N to
configure it later.
10. Type Y if you want to view the readme file, or N if you wish to read it later.
11. 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 as pmserver. 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 133.
Note: ODBC databases, such as Microsoft Access97 and Excel, are not compatible with the
Informatica Server installed on a UNIX system.
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.
Table 6-2 describes the setting required to configure the Informatica Server on UNIX:
Table 6-2. Configuration Parameters for Informatica Server on UNIX
Required/
Option Description
Optional
ServerPort Required The TCP/IP port the Informatica Server uses. Default is
4001.
RepositoryName Required The exact repository name, the repository name entered
when creating or upgrading a repository.
DBUser Required The user name for the database containing the
repository. The Informatica Server uses this to connect to
the repository.
DBPassword Required The user password for the database containing the
repository. The Informatica Server uses this to connect to
the repository. Must be in US-ASCII only.
Step 2. Configuring the Informatica Server on UNIX 109

Required/
Option Description
Optional
PMUser Required The repository username specific to the Informatica

Client and Informatica Server tools to connect to the
repository.
PMPassword Required The password corresponding to the repository user

(PMUser). Must be in US-ASCII only.
DatabaseType Required The type of database containing the repository

(for example, Oracle, Sybase, DB2, or Informix).
ConnectString Required The native connect string that the Informatica 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, Oracle72.world for
Oracle). For ODBC sources, such as Microsoft Access
and Microsoft Excel, the connect string must match the
ODBC data source name on the server machine. For a
list of native connect strings, see Table 1-4 on page 5.
ErrorLogFile Required The filename of the Informatica Server error log file.
Default is pmserver.err.
EventLogFile Optional The filename of the Informatica Server event log file. If
you set PerformEventLogging to Yes, you must enter a
filename for EventLogFile. Default is pmserver.log.
PerformEventLogging Optional A flag (Yes or No) indicating whether the Informatica

Server performs event logging. If you set this flag to Yes,
the Informatica Server writes all events, including errors,
to the event log file. Default is No.
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.
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.

Required/
Option Description
Optional
KeepRepeatSessionInShM Optional The Keep Repeating Sessions option determines the

action the Load Manager takes when there are no
available slots when a session start time arrives. When
this option is set to No, the Load Manager moves
repeating sessions out of session slots to run new
session requests. If all session slots are occupied with
active sessions, the Load Manager places new session
requests in a waiting state until a session slot becomes
available. If set to Yes, the Load Manager retains
repeating sessions in shared memory, and fails to run
new session requests.
This option is set to No by default.
LMStayConnectToRepositDuration Required The Load Manager holds the connection to the repository
for the value set in the Informatica Server configuration,
LMStayConnectToRepositDuration. By default, this time
is 300 seconds, or 5 minutes. Each time the Load
Manager communicates with the repository, the Load
Manager verifies the connection duration. If the duration
is expired, the Load Manager disconnects and
reconnects to the repository. If the duration is not expired,
the Load Manager uses the same connection and resets
the connection time to the full duration. Default is 300
seconds.
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
PowerMart and PowerCenter, use the server variable
$PMCacheDir. Configure $PMCacheDir when you
configure the Informatica Server in the Server Manager.
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.

Required/
Option Description
Optional
DisableRecovery Optional If set to Yes, the Informatica Server does not create the
recovery table (OPB_SRVR_RECOVERY) in the target
database. Also, the Informatica Server does not record
recovery information from the session it is running, even
if the OPB_SRVR_RECOVERY exists in the target
database. If set to Yes, Perform Recovery in the Server
Manager has no effect.
If set to No, or if DisableRecovery is not included in the
configuration file, the Informatica Server enables
recovery.
This option is set to Yes by default.
OverrideExecLocking Optional Set to 1 to have the Informatica Server ignore any

session or batch locks. If you run a session that is already
running or has been left behind from a previously failed
session, the Informatica Server ignores the lock and runs
the session anyway. This option should only be selected
in development, since problems can arise running
simultaneous sessions.
This option is set to 0 by default.
DateHandling40Compatibility Optional Set to Yes, the Informatica Server handles dates as in

PowerMart 4.0/PowerCenter 1.0. Set to No, the
Informatica Server handles dates as defined in
PowerMart 5.1/PowerCenter 5.1.
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.
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.
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.

Required/
Option Description
Optional
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 Designer Guide.
OracleVersion Optional Set to 7 to use SQL*Net 2.3.4 to connect to all Oracle

databases. If set to 7, set the ORACLE_HOME
environment variable to point to the Oracle 7 installation
directory. Set to 8 to use Net8 to connect to all Oracle
databases. If set to 8, set the ORACLE_HOME
environment variable to point to the Oracle 8 installation
directory.
The Informatica Server on HP-UX does not support
SQL*Net 2.3.4.
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 session with a flat file target.
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.
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. 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.
By default, this option is set to No.

Required/
Option Description
Optional
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 0seconds by default.
3. Save your changes and close the file.

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 repository, 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, target, and
repository databases, use 32-bit database client libraries only.
You need to configure the Informatica Server to communicate to each source target, and
repository database in your data warehouse. 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 PowerMart or PowerCenter is
installed.
4. Set the shared library environment variable:
Table 6-3. Library Path for Informatica Server on UNIX
Shared Library
Operating System
Environment Variable
Solaris LD_LIBRARY_PATH
AIX LIBPATH
HP SHLIB_PATH
Follow these guidelines when you use a UNIX shell:
Shell To Modify Environment Variable
C-shell setenv PATH ${PATH}:/usr/mypath
Bourne Shell PATH=${PATH}:/usr/mypath; export PATH
For example, if you have an Oracle source, Sybase repository, 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:$SYBASE/lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql; export
LD_LIBRARY_PATH

Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
pmserver_dir:$ORACLE_HOME/lib:$SYBASE/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.
Connecting to an Oracle Database

You need to connect each Informatica Server to each Oracle source, target, and repository
database.
SQL*Net 2.3.4 and Net8

If your data warehouse includes a mix of Oracle 7 and Oracle 8, and Oracle 8i databases, you
can use SQL*Net 2.3.4, Net8, or Net8i. You must install the same version of the Oracle
Client on each machine hosting the Oracle database server and Informatica Server.
Using SQL*Net 2.3.4

Follow these steps to connect to an Oracle database through SQL*Net 2.3.4. These steps are
provided as a guideline. For specific connectivity instructions, refer to your database
documentation.
To connect to an Oracle database through SQL*Net 2.3.4:

Install the same version of SQL*Net on the machines hosting the Oracle database and
Informatica Server. If you have different versions of SQL*Net 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, on Solaris, set the LD_LIBRARY_PATH variable to the Informatica Server
installation directory. If you installed the Informatica Server in the $HOME/pmserver
directory, you could type:
$ 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
Note: $ORACLE_HOME is the directory where Oracle is installed.
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 may vary depending on your configuration.
5. Ensure that the system path includes an entry for Oracle.

For example, if you install SQL*Net on a UNIX system, your path might include the
following entry:
$ PATH=${PATH}:$ORACLE_HOME/BIN
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.
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 109.
Using Net8
Follow these steps to connect to an Oracle database through Net8. These steps are provided as
a guideline. For specific connectivity instructions, refer to your database documentation.
To connect to an Oracle database through Net8:

Install the same version of Net8 on the machine hosting the Oracle database and
Informatica Server. If you have different versions of Net8 installed, you may experience
difficulties reading from and writing to the database.
2. Set the ORACLE_HOME environment variable to the Oracle 8 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
$ 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.

For example, your path might include the following entry:
$ 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.
8. Configure the Informatica Server. Include the Oracle database key in the Informatica
Connecting to a Sybase SQL Server Database

database documentation.
To connect to a Sybase database:
1. Install the Open Client software.

Install the same version of Open 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
connectivity information.
Usernames and database names may be case-sensitive. You use the correct connect string.
The syntax is servername@dbname (for example, myserver@sybasedb).
6. Configure the Informatica Server. Include the Sybase database key in the Informatica
Server configuration (pmconfig).
Connecting to an Informix Database

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
$ 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.
If you connect to the database, continue with the next step. If you fail to connect to the
11. Configure the Informatica Server. Include the Informix database key in the Informatica
Connecting to a DB2 Universal Database


To connect to a DB2 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 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:
$ setenv DB2DIR /opt/IBMdb2/v6.1
For HP-UX:
$ setenv DB2DIR /opt/IBMdb2/v6.1
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:
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 logout 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. 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 Server Manager. You can also use the command line program pmcmd to stop the
Informatica Server.
Note: Before starting the Informatica Server, use the Server 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 sessions and batches scheduled to run in the future. It then attempts to stop all running
sessions and batches. If any sessions or batches fail to respond within a certain period of time,
the Informatica Server aborts the remaining sessions and batches. Allow 1 to 2 minutes for the
Informatica Server to complete all processes. When you restart the Informatica Server, you
must reschedule all sessions and batches.
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 is 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:
Event LM_2003 for PowerMart: "Server initialization completed
successfully."
If the Informatica Server does not start, check the error log for the Informatica Server.
Step 4. Starting and Stopping the Informatica Server on UNIX 125

Command Line Program
You can use the command line program pmcmd to stop the Informatica Server. For details, see
“Using pmcmd “ in the Session and Server Guide.

Installing and Configuring ODBC for UNIX
The Informatica installation CD provides a Merant 3.6 UNIX ODBC closed driver to
connect to ODBC data sources.
PowerMart and PowerCenter 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 PowerMart/PowerCenter 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.
Installing and Configuring ODBC for UNIX 127

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
Informatica installation CD.
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:
For example, on Solaris:
$ 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}

5. Edit into your (.cshrc) the complete set of shell commands appropriate to your operating
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.6 dBase Driver
Sybase11=Merant 3.6 Sybase 11 Driver
Oracle7=Merant 3.6 Oracle 7 Driver

Oracle8=Merant 3.6 Oracle 8 Driver
Informix9=Merant 3.6 Informix 9 Driver
OpenIngres=Merant 3.6 OpenIngres 1.2 Driver

OpenIngres20=Merant 3.6 OpenIngres 2.0 Driver
DB2=Merant 3.6 DB2 Driver
Text=Merant 3.6 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
[Oracle7]
Driver=/usr/lpp/odbc/lib/DWor713.so
Description=Oracle7

ServerName=oraclehost
LogonID=odbc01
Password=odbc01
[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/DWor713.so
Description=Merant 3.6 Oracle 7 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.
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.

Chapter 7
Registering the
Informatica Server
♦ Overview, 134
♦ Registering the Informatica Server, 135
133
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 Server Manager. The Server Manager is the Informatica
Client tool that you use to create and run sessions 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 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 session in the session properties sheet.
♦ Edit an Informatica Server. When you edit an Informatica Server, all sessions using that
Informatica Server use the updated connection, including the updated code page
information.
♦ Delete an Informatica Server. When you delete an Informatica Server, the Server Manager
prompts you to choose another Informatica Server for the sessions using that Server.
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 Server Manager to run sessions:
♦ Create source and target database connections.
♦ Define the FTP connections if you plan to use FTP to access source or target machines.
♦ Configure External Loader connections if you plan to use an external loader to load the
target database.
For more information, see “Configuring the Server Manager” in the Session and Server Guide.
134 Chapter 7: Registering the Informatica Server

Registering the Informatica Server
Before you use the Server 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.
− The Server Manager performs a case-insensitive comparison of all server names to
prevent duplicate server names.
♦ Type of network protocol used to access the Informatica Server: TCP/IP or IPX/SPX.
− TCP/IP. Use the IP address or hostname of the machine on which the Informatica
Server runs, and the port number the Informatica Server uses on that machine.
− IPX/SPX. Use the address of the machine on which the Informatica Server runs.
♦ Code page identifying the character set associated with the Informatica Server.
♦ Directories and parameters you want the Informatica Server to use for session 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 Server Manager displays valid code pages based
on the repository code page.
The Server Manager allows you to change the Informatica Server code page to a compatible
code page. This ensures sessions 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
Server Manager. After creating sessions, you change the Informatica Server code page to
JapanEUC and then update the Informatica Server information in the Server 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 output files and caches. They can also define session
properties, such as the number of session logs to archive or the session error threshold.
The installation process creates directories in the location where you install the Informatica
Server. By default, the Informatica Server writes output files in these directories when you run
Registering the Informatica Server 135

a session. To use these directories as the default location for the session output files, you must
configure the server variable $PMRootDir to define the path to the directories.
Sessions and batches are configured to use server variable directories by default. You can enter
different directories on a session-by-session basis in the session property sheet.
For example, you might have an Informatica Server running all sessions in a repository. If you
define the server variable for session logs as c:\pmserver\sesslog, the Informatica Server saves
the session log for each session in c:\pmserver\sesslog by default.
If you change the default server variable directories, make sure the designated directories exist
before running a session or batch. If the Informatica Server cannot resolve a server variable
during the session, it cannot run the session.
By using server variables instead of hard-coding directories and parameters, you simplify the
process of changing the Informatica Server that runs a session or batch. If each session and
batch in a development folder uses server variables, then when you copy the folder to a
production repository, the production server can run the sessions and batches as configured.
When the production server runs the sessions and batches, it uses the directories configured
for its server variables. If, instead, you changed sessions to use hard-coded directories, sessions
fail if those directories do not exist on the production server.
Similarly, if you use a server variable to send post-session email to the administrator of the
Informatica Server, when you change the Informatica Server running the session, the
administrator of the new Informatica Server receives the email.
Table 7-1 lists the server variables you configure when you register an Informatica Server:
Table 7-1. Server Variables
Required/
Server Variable Description
Optional
$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. Defaults to $PMRootDir/Cache. 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.
$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.

Table 7-1. Server Variables
Required/
Server Variable Description
Optional
$PMSuccessEmailUser Optional Email address to receive post-session email when the session
completes successfully. Use to address post-session email. The
default value is an empty string. For details, see “Sending Post-
Session Email” in the Session and Server Guide.
$PMFailureEmailUser Optional Email address to receive post-session email when the session fails
to complete. Use to address post-session email. The default value
is an empty string. For details, see “Sending Post-Session Email”
in the Session and Server Guide.
$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 Files” in the Session and Server Guide.
$PMSessionErrorThreshhold Optional Number of errors the Informatica Server allows before failing the
session. Defaults to 0. Use to configure the Stop On option in the
session property sheet.
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 variable directories.
The syntax for $PMRootDir is different for Windows NT/2000 and UNIX:
♦ Windows NT/2000. Enter a path on Windows NT beginning with a drive letter, colon,
backslash, as follows:
C:\InformaticaServer\bin
♦ UNIX. Enter an absolute path on UNIX beginning with a slash, as follows:

/InformaticaServer/bin
For example, if you define $PMRootDir on Windows NT/2000 to be

c:\InformaticaServer\bin, the variable $PMSessionLogDir becomes
c:\InformaticaServer\bin\SessLogs.
The Informatica Server installation directory is the recommended root directory. If you enter
a different root directory, make sure all server variable directories exist before running a
session.
Entering Other Directories

By default, the Server Manager uses $PMRootDir as the basis for other server variable
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,
one with plenty of memory and disk space for index and data caches, 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 Server Manager corrects the delimiter.
Changing Servers
If you change Informatica Servers, the new Informatica Server can run sessions and batches
using the server variables. To ensure a session successfully completes, relocate any necessary
file sources, targets, or incremental aggregation files to the default directories of the new
Informatica Server.
If you override a server variable in an individual session, you may need to manually edit the
session if you change the Informatica Server. If the new Informatica Server cannot locate the
override directory, it cannot run the session.
For example, you might override the session log variable in the session property sheet, by
entering d:\data\sesslog. You then copy the folder containing the session to a production
repository. The log file variable of the new Informatica Server is c:\pmserver\sesslog. When
the new Informatica Server tries to run the copied session, it cannot find the directory listed
in the session property sheet, so it fails to initialize the session. To correct the problem, you
must either edit the session property sheet, or create the specified directory on the 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 Server Manager, connect to the repository.

If you are connecting to a repository for the first time, the Server Manager creates a
temporary server called temp_server.You must edit this server to register it in the
repository.

2. To edit the temporary server, select it and choose Server Configuration-Edit Server.
3. Select the network protocol (TCP/IP or IPX/SPX) and enter the appropriate settings for
that protocol.
If you select TCP/IP, configure the TCP/IP connectivity settings.
Table 7-1 describes the settings required to register an Informatica Server using TCP/IP:
Table 7-1. TCP/IP Settings to Register a Server
Required/
TCP/IP Option Description
Optional
Server Name Required for MS The name of Informatica Server. Use to select the Informatica
SQL Server and Server to run a session or batch. This name must be unique to
Sybase only the repository.
Host Name or IP Required Server hostname or IP address of the Informatica Server

address machine.
Port Number Required Port number the Informatica Server uses. Must be the same port
listed in the Informatica Server configuration parameters.
Timeout Required Number of seconds the Server 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
If you select IPX/SPX (NT/2000 only), configure the IPX/SPX connectivity settings.

Table 7-2 describes the settings required to register an Informatica Server using IPX/SPX:
Table 7-2. IPX/SPX Settings to Register a Server
Required/
IPX/SPX Option Description
Optional
Server Name Required for MS Name of Informatica Server. Used to configure

SQL Server and sessions and batches.
Sybase only
Dotted IPX/SPX Required IPX/SPX address of the machine hosting the

Address Informatica Server.
Timeout Required Number of seconds the Server Manager waits for a

response from the Informatica Server.
4. 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 variable directories in the Server installation directory. If you enter a
different root directory, make sure to create the necessary server variable directories.
5. 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 136 for a list of server variables.
6. Click OK.
The new Informatica Server appears in the Navigator below the repository.

Chapter 8
Upgrading a Repository

♦ Upgrade Process, 142
♦ Preparing to Upgrade, 143
♦ Upgrading a Repository, 144
♦ Upgrading PowerMart 4.6/4.7 or PowerCenter 1.6/1.7, 147
141
Upgrade Process
PowerMart 5.1 and PowerCenter 5.1 include a new repository version, 102. Because the
repository is versioned, you need to upgrade the existing repository to incorporate the new
features included in PowerMart 5.1 and PowerCenter 5.1. When you upgrade a repository,
the upgrade process modifies repository tables to accommodate new types of metadata.
PowerMart 5.1 and PowerCenter 5.1 support upgrading from PowerMart 4.6/4.7/5.0 and
PowerCenter 1.6/1.7/5.0.
If you have several repositories in a data mart domain, you must upgrade all global
repositories before the local repositories. The upgrade process checks if the global repositories
have been upgraded before the local repositories. For more information on data mart
domains, see “PowerCenter Repositories” in the Repository Guide.
The upgrade process proceeds incrementally, one repository version at a time, incorporating
new features with each version. A repository version is an indicator that the client tools use to
identify which features are supported in the current repository configuration. For example,
you cannot use the PowerMart 5.1 Designer to connect to a PowerMart 4.7 repository.
Likewise, you cannot use the PowerMart 4.7 Designer to connect to a PowerMart 5.1
repository.
During the upgrade, existing data is copied from the original tables into temporary tables.
Because these temporary tables are created in the same database as the repository, the upgrade
process requires additional space. The PowerMart 5.1 and PowerCenter 5.1 repository is
approximately 15 percent larger than a PowerMart 4.7 and PowerCenter 1.7 repository and
approximately 45 percent larger than a PowerMart 4.6 or PowerCenter 1.6 repository. You
may need to increase the size of the database or add more disk space. Informatica recommends
that you allocate approximately 60 percent more available disk space and temporary storage
space in the database. The PowerMart 5.1 and PowerCenter 5.1 repository is not significantly
larger than the PowerMart 5.0 and PowerCenter 5.0 database. If you are upgrading a PowerMart
5.0 or PowerCenter 5.0 repository, you do not need to allocate additional space in the database.
The repository upgrade process stops if it encounters problems during the upgrade such as
lack of disk space. Once you identify and fix the problem, you can run the upgrade again.
When you upgrade the repository, the upgrade process begins again at the last successful
version number. For example, if the upgrade fails between version 85 and 86, the upgrade
process starts at version 85 when you run upgrade for the second time.
Note: If you are upgrading from PowerMart 4.0/4.5 or PowerCenter 1.0/1.5, you must first
upgrade to PowerMart 4.6/PowerCenter 1.6. Please contact Informatica Technical Support.
142 Chapter 8: Upgrading a Repository

Preparing to Upgrade
IMPORTANT: Unlock all folders and objects in the existing version Repository Manager before
upgrading. Informatica recommends that you upgrade a copy of the existing 4.6/4.7/5.0 or
PowerCenter 1.6/1.7/5.0 repository.
PowerMart 5.1 and PowerCenter 5.1 can restore PowerMart 5.1 or PowerCenter 5.1
repositories only. If you have any PowerMart 4.6/4.7/5.0 or PowerCenter 1.6/1.7/5.0
repositories in backup files only, you must use that previous version to restore the backup file
before you upgrade the client tools. After you upgrade the client tools, you can upgrade the
repositories and create new backup files.
Make a copy of all incremental aggregation files (PMAGG*.dat and PMAGG*.idx files), log
files, and cache files. If you have any difficulties upgrading or if the upgrade fails, see
“Troubleshooting” on page 151 for a list of error messages and solutions.
Complete the following tasks before you perform the repository upgrade:
1. Read the release notes for additional upgrade information.
2. Have all users close all Informatica Client tools connected to the repository.
3. Stop the Informatica Server.
4. In the PowerMart 4.6/4.7/5.0 or PowerCenter 1.6/1.7/5.0 Repository Manager, unlock
all folders.
5. Back up the PowerMart 4.6/4.7/5.0 or PowerCenter 1.6/1.7/5.0 repository.
6. Create a new database for each repository you want to upgrade.
Review system requirements and supported client, repository, and Informatica Server
platforms. See “Minimum System Requirements” on page 2 for details.
7. Use the PowerMart 4.6/4.7/5.0 or PowerCenter 1.6/1.7/5.0 Repository Manager to copy
each repository to the new database.
Warning: If you copy the repository to a database with an existing repository, the
Repository Manager overwrites the existing repository. If you want to preserve the
existing repository, back it up before copying the new repository into the database.
8. Install the PowerMart 5.1/PowerCenter 5.1 client tools.
9. Install the Merant 3.6 32-bit closed ODBC drivers.
10. Create data sources for each new repository database.
You are ready to upgrade the repository.
Preparing to Upgrade 143

Upgrading a Repository
Before you upgrade a repository, make sure you complete the tasks in “Preparing to Upgrade”
on page 143.
Note: You must upgrade global repositories before you upgrade local repositories.
To upgrade a repository:
1. Launch the PowerMart 5.1 or PowerCenter 5.1 Repository Manager.

2. Choose a repository from the list of repositories.
If you are upgrading global and local repositories, choose the global repository first.
If the repository does not display in the list, add the repository using Repository-Add
Repository.
3. Choose Repository-Upgrade Repository.
4. Enter a repository username and password. Passwords must be in US-ASCII.
You need to be a Super User or a Repository Administrator with Administer Repository
privileges to perform the upgrade. Make sure you enter a repository username/password,
not a database username/password.
5. Click Connect.
The Repository Manager warns you that the changes are not reversible.
6. Click OK. The Repository Manager warns you that users are connected to the repository.
If any users are connected to the repository, have them close all client tools.
If you are certain no users are connected to the repository, click OK to start the upgrade.
The upgrade process begins. You can see the progression of incremental changes to the
repository in the Output window.
7. Click OK.
The Output window displays the progression of changes in the repository and informs
you when the upgrade completes.

8. The following dialog box displays only when upgrading from PowerMart 4.6/
PowerCenter 1.6:
The Repository Manager prompts you to select a code page. Choose a code page from the
list and click OK. For more information, see “Selecting a Code Page (PowerMart 4.6/
PowerCenter 1.6 Only)” on page 145.
9. When the Repository Manager notifies you that the upgrade is finished, click OK.
To see if the upgrade completes without errors, review the text in the Output window after
you run the upgrade. Errors appear in blue text. Warnings appear in red text.
After you upgrade the repository, install and configure the PowerMart 5.1 or PowerCenter 5.1
Server. If you perform a new install, register the Informatica Server in the Server Manager and
select a code page for the Informatica Server. The Informatica Server code page must be
compatible with the repository code page. For more information, see “Registering the
Informatica Server” on page 133.
Selecting a Code Page (PowerMart 4.6/PowerCenter 1.6 Only)

If you are upgrading from PowerMart 4.6/PowerCenter 1.6, you must select a code page for
each repository. The repository code page is the encoding scheme for the character set of the
repository data. When you create or upgrade a repository, you must select a code page. Once
selected, the code page cannot be changed and must be compatible with the Informatica
Client and Server code pages. For more information on code pages and compatibility, see
“Globalization Overview” on page 9.
You must upgrade global repositories before you upgrade local repositories. The code page
you select for the global repository must be compatible with the code page of the local
repository. If you select an incompatible code page, a warning appears in the Repository
Manager output window.
Once you select a code page for a repository, you cannot change it. However, if you must
change the repository code page, you can back up the repository before the upgrade, and then
restore it. When you restore the repository, you are prompted to select a code page. This code
page must be compatible with the code page of the backed up repository and with the
Informatica Client and Server code pages.
For example, you want to connect to a repository from an English workstation and run the
Informatica Server using a Japanese code page, such as Japan-EUC, select a compatible
Japanese code page for the repository. However, you cannot choose a Japanese code page on
the English workstation. You must then upgrade the repository on a Japanese client
Upgrading a Repository 145

workstation instead of an English workstation, then select a Japanese code page as the
For a list of compatible code pages, see “Code Pages” on page 169.

Upgrading PowerMart 4.6/4.7 or PowerCenter 1.6/1.7
The upgrade from PowerMart 4.6/4.7 or PowerCenter 1.6/1.7 to PowerMart 5.1/
PowerCenter 5.1 affects the following objects:
♦ Lookup transformations. Lookup caching properties upgrade.
♦ System variables. SYSDATE upgrades to SESSSTARTIME.
♦ Global objects with permissions. Database, external loader, and FTP connections upgrade
to global objects.
♦ Objects for partitioning. Mappings upgrade for partitioning.
♦ External loader objects. Oracle and Sybase IQ external loader objects upgrade.
♦ Incremental aggregation files. Incremental aggregation files upgrade when you run a
session.
If you are upgrading from PowerMart 5.0/PowerCenter 5.0, these objects have already been
upgraded.
Upgrading Lookup Transformations

In repository versions prior to PowerCenter 5.0 and PowerMart 5.0, the Lookup
transformation had two different transformation options that instructed the Informatica
Server to rebuild the lookup cache under certain conditions. The old transformation options
were Lookup Cache Initialize and Recache If Stale. In this version, there is only one
transformation option, Recache from Database.
When you upgrade a repository that contains Lookup transformations, the upgrade process
enables the Recache From Database option under certain conditions.
Table 8-1 shows how the upgrade process maps the old transformation options to the new
Recache From Database transformation option:
Table 8-1. Upgrading Lookup Transformation Options
Lookup Cache Recache if

Recache From Database
Initialize Stale
Enabled Enabled Always maps to enabled.
Enabled Not enabled Always maps to enabled.
Not enabled Enabled Always maps to enabled.
Not enabled Not enabled Always maps to not enabled.
When you run a session with a persistent lookup cache, the Informatica Server rebuilds the
PowerMart and PowerCenter lookup cache files even if Recache From Database is not
enabled. For more information on the Recache from Database option, see “Lookup
Transformation” in the Designer Guide.
Upgrading PowerMart 4.6/4.7 or PowerCenter 1.6/1.7 147

Upgrading System Variables
When you upgrade a repository to PowerMart 5.1/PowerCenter 5.1, the upgrade process
replaces the system variable SYSDATE with the system variable SESSSTARTTIME in
expressions and default values for ports.
The repository upgrade process upgrades SYSDATE to SESSSTARTTIME when SYSDATE is
used in the following expressions:
♦ Aggregator transformation port expressions
♦ Expression transformation port expressions
♦ Filter transformation filter condition expression
♦ Rank transformation port expressions
♦ Update strategy expression
SESSSTARTTIME returns the current system date on the machine hosting the Informatica
Server at the time the session runs. For details on SESSSTARTTIME, see “Variables” in the
Transformation Language Reference.
Upgrading Global Objects with Permissions

You create global objects in the repository when you define database, FTP, and external loader
connections in the Server Manager. PowerMart 5.1 and PowerCenter 5.1 allow you to enable
enhanced security to assign stricter permissions for global objects.
The repository upgrade automatically assigns permissions to existing database, FTP, and
external loader connections. By default, the repository upgrade assigns read, write, and
execute permissions to all existing database, FTP, and external loader connections for the
World group in the Permissions dialog box for global objects.
All users can access the existing global objects after the repository upgrade. You must edit the
permissions on global objects to restrict the assigned permissions. For more details on
enabling enhanced security and assigning global object permissions, see “Configuring the
Server Manager” in the Session and Server Guide.
Upgrading Objects for Partitioning

When you upgrade the repository, the upgrade process evaluates each mapping to determine if
each mapping meets partitioning criteria. The upgrade marks each mapping as partitionable
or non-partitionable.
Some sources marked as non-partitionable during the upgrade process might be partitionable
according to partitioning rules. To use these objects in a partitioned session, you must open
and resave them.
The upgrade process marks the following partitionable objects as non-partitionable:
♦ Sources that pass data into a Joiner transformation. According to partitioning rules, you
cannot partition the master source for a Joiner transformation. When you upgrade the

repository, the upgrade process marks both sources as non-partitionable because it cannot
detect which source is the master source. If you want to partition the detail source, you
must resave the mapping.
♦ Sources in a mapplet. If the objects in the mapplet are partitionable, you can resave the
mapplet and then partition the session.
♦ Sources that pass data into a mapplet. If the objects in the mapplet and source pipeline
are partitionable, you can resave the mapping and then partition the session.
♦ Sources that pass data into an Advanced External Procedure or External Procedure
transformation. Select the IsPartitionable option in the transformation before you can
partition the source. You muse use an external procedure or advanced external procedure
with a thread-safe library to run a partitioned session.
♦ All external loader connections. To use the Oracle SQL external loader connection in a
partitioned session, you must open and save the connection after the repository upgrade.
You can only use Oracle SQL Loader to load partitioned data.
Note: To resave a mapping or mapplet, you must open, edit, and save it using Repository-Save.
For a complete listing of partitioning restrictions, see “Partitioning Data” in the Session and
Server Guide.
Upgrading External Loader Objects

When you upgrade a repository, the upgrade process upgrades external loader objects. The
upgrade process upgrades Oracle external loaders to allow parallel loading, and upgrades
Sybase IQ 11 external loader objects to Sybase IQ 12.
Upgrading Oracle External Loaders for Partitioned Sessions

You can load data from a partitioned session to an Oracle database using the Oracle external
loader. However, the upgrade process marks all external loader objects as non-partitionable.
Before you run upgraded sessions that use the Oracle external loader, open and save the
Oracle external loader connection.
For details on using Oracle external loaders with partitioned sessions, see “External Loading”
in the Session and Server Guide.
Sybase IQ 12 External Loader Upgrade

PowerMart 5.1 and PowerCenter 5.1 use Sybase IQ 12 external loader connections. The
upgrade process replaces all existing Sybase IQ 11 objects with Sybase IQ 12 objects:
♦ Copied Attributes. The upgrade process retains some similar attributes of Sybase IQ 11
and Sybase IQ 12 objects and copies the Sybase IQ 11 attributes to the new Sybase IQ 12
object. The upgrade process copies these values from the existing Sybase IQ 11 object to
the new Sybase IQ 12 object :
− Block Factor
− Blocksize
Upgrading PowerMart 4.6/4.7 or PowerCenter 1.6/1.7 149

− Notify Interval
− The upgrade process discards these attributes during the upgrade process:
− Indexspace Name
− Indexset Type
− Sort Memory (MB)
♦ Server Datafile Directory. Sybase IQ 12 objects have a new attribute, Server Datafile
Directory. When the upgrade process upgrades the repository, it leaves this attribute
unspecified. The upgrade process does not mark sessions with an unspecified Server
Datafile Directory as invalid, but if the attribute is left unspecified, the session fails when
you run it. You must edit upgraded Sybase IQ 12 objects and specify the Server Datafile
Directory before running sessions with Sybase IQ 12 connections.
♦ Connection String. Sybase IQ 12 uses a single connection string to connect to a Sybase IQ
database. The repository upgrade process copies the host name and database name
parameters from Sybase IQ 11 objects into the new Sybase IQ 12 connection string
format. The repository upgrade process does not copy the password parameter. Each
parameter is separated by a semi-colon:
host_name; db_name
Upgrading Incremental Aggregation Files

When you run an upgraded session using incremental aggregation for the first time, the
Informatica Server automatically upgrades the index and data cache files. If you want to
partition a mapping in a session using incremental aggregation, the Informatica Server re-
aligns the index and data cache files. For more information, see “Upgrading Objects for
Partitioning” on page 148.

Troubleshooting
This section provides information to help solve any problems you might encounter during an
upgrade. If you need further assistance, contact Informatica Technical Support.
Upgrade Fails
The repository upgrade process stops if it encounters problems during the upgrade such as
lack of disk space. The most common reasons an upgrade might fail are:
♦ The upgrade process has trouble reading or writing to the repository database.
♦ The repository database has insufficient disk space or temporary storage space.
♦ The client system has insufficient memory.
♦ The repository has inconsistent data.
Once you identify and fix the problem, you can restart the upgrade. When you upgrade the
repository the second time, the upgrade process starts the upgrade process at the last
successful version number. For example, if the upgrade fails between version 85 and 86, the
upgrade process starts at version 85 when you run upgrade the second time. However, you
should always maintain a copy of the original repository, in case you need to start the upgrade
from the beginning.
Troubleshooting 151
Chapter 9
Using ODBC

♦ Overview, 154
♦ ODBC Data Sources, 155
♦ ODBC and the Informatica Client and Server, 156
♦ ODBC Calls, 158
♦ Creating an ODBC Data Source, 161
♦ Configuring an ODBC Data Source, 165
♦ Deleting an ODBC Data Source, 166
153
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 95/98 and Windows NT/2000. Use the ODBC
Administrator to create, modify, and delete ODBC data sources.
Figure 9-1 illustrates connectivity between PowerMart or PowerCenter, the ODBC
components, and databases:
Figure 9-1. ODBC Connectivity Overview
PowerMart and PowerCenter
ODBC components
Driver Manager
ODBC Driver ODBC Driver

for Sybase for Oracle
Sybase Client Library Oracle Client Library
Sybase Oracle
Database Database
154 Chapter 9: Using ODBC

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 Data Sources 155

ODBC and the Informatica Client and Server
The Informatica Client uses ODBC drivers to connect to repositories and databases as well as
secondary connections. Secondary connections occur when you connect to a local repository
and then to a global repository or connect to a global repository and then to a local repository.
You might also connect to a local repository and retrieve a shortcut from a global repository.
You can configure the Informatica Server to use the ODBC driver to connect to databases.
However, Informatica strongly recommends using native drivers when possible. The
Informatica Server uses native and ODBC drivers to connect to databases. If you register
multiple servers, you must use the same System DSN for each server to connect to a global
repository.
PowerMart and PowerCenter 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. You enter usernames and passwords in the Server Manager, Server Configuration-
Database Connections-Edit dialog box. 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 9-1 shows the information that the Informatica Client and Server require to connect
the source, target, and repository databases:
Table 9-1. ODBC Connection Requirements
Informatica Client and Server Connects to Required Information
Designer Source or Target ODBC data source name

- Username
- Password
Repository Manager Repository ODBC data source name

- Username
- Password
- Native connect string
Server Manager Repository 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.
The Repository Manager and Designer access the ODBC Administrator settings to connect to
data sources.

The Server Manager communicates with the Informatica Server on Windows NT/2000 and
UNIX platforms. On Windows NT/2000, 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 127.
Tip: The Repository Manager saves repository connection information in the client registry.
To simplify the process of setting up client systems, you can use the Export/Import Registry
feature in the Repository Manager to export the repository connection information. Then
import it to a different client system. This process ensures that each client uses the same
connection information. However, you need to configure ODBC DSNs for each connection.
For details, see “Managing the Repository” in the Repository Manager Guide.
Database ODBC Drivers

The Informatica Client tools use ODBC drivers to connect to source and target databases.
Table 9-2 shows the ODBC drivers to use with each database:
Table 9-2. Database ODBC Drivers
Database ODBC Driver
IBM DB2 IBM ODBC driver
Informix Merant 3.6 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.6 32-bit closed ODBC driver
Sybase Merant 3.6 32-bit closed ODBC driver
Teradata Teradata ODBC driver
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 158.
PowerMart 5.1 and PowerCenter 5.1 support the Merant 3.6 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.6 32-bit
ODBC closed drivers are fully backward compatible. If you have any questions, contact
Merant.
ODBC and the Informatica Client and Server 157

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 9-3 describes the core function calls the Informatica Client makes to connect to ODBC
drivers:
Table 9-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.

Table 9-3. Informatica Client ODBC Function Calls
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.
ODBC Calls 159

Server ODBC Calls
The Informatica Server on UNIX and Windows NT/2000 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 9-4 describes the core function calls the Informatica Server makes to connect to ODBC
drivers:
Table 9-4. Informatica Server ODBC Function Calls
SQLAllocConnect Allocates resources for a connection.
SQLAllocStmt Allocates resources for a statement.
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.

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.
Tip: When setting up the ODBC connection to the repository, use the repository database
name for the ODBC connection. This practice makes it easier to configure the same ODBC
settings for other user client settings. See “Managing the Repository” in the Repository Guide
for information on copying client tool ODBC registry entries to other computers.
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.
Note: For a global repository, make sure that you create a system DSN, not a user DSN.
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.
Creating an ODBC Data Source 161

5. Enter the name for the new ODBC data source.
Every ODBC data source name (DSN) must be unique on the system. If you create an
ODBC data source to connect to a global repository or secondary connections, make sure
that the DSN is the same as the repository name. This step ensures that every client
accessing the global repository uses the same DSN for the connection.
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 9-2 shows the ODBC Microsoft Excel Setup dialog box:
Figure 9-2. ODBC Microsoft Excel Setup
Choose the Microsoft Excel version

For more information on Microsoft Excel sources, refer to the article in the Informatica
Webzine. You can access the webzine at http://www.informatica.com/webzine.
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 9-3 shows the ODBC Sybase Driver Setup dialog box:
Figure 9-3. ODBC Sybase Driver Setup
Set Prepare Method to 2-Full
Configuring ODBC for SQL Server 6.5

Clear Generate Stored Procedure for Prepared Statement in the ODBC SQL Server Setup
dialog box.
Figure 9-4 shows the dialog box for the SQL Server 6.5 ODBC setup:
Figure 9-4. ODBC SQL Server 6.5 Setup
Clear Generate Stored Procedure

for Prepared Statement
Creating an ODBC Data Source 163

Configuring ODBC for SQL Server 7.0
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 9-5 shows the dialog box for the SQL Server 7.0 ODBC setup:
Figure 9-5. ODBC SQL Server 7.0 Setup
For Microsoft SQL Server 7.0

repositories, clear Create
temporary stored procedures
for prepared SQL statements
and drop the stored
procedures.
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 7.0. You can access the webzine at http://www.informatica.com/webzine.

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. If you need to change the database type, create a new DSN and choose the
correct database.
To configure an ODBC data source:

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.
Configuring an ODBC Data Source 165

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 session 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 session.
Troubleshooting 167
Appendix A
Code Pages
This appendix documents code pages and their compatibility in PowerMart and PowerCenter.
Topics include:
♦ Code Pages, 170
♦ Code Page Reference, 172
♦ Informatica Code Page Relationships, 176
♦ Code Page Compatibility, 178
169
Code Pages
PowerMart and PowerCenter 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
170 Appendix A: Code Pages

Table A-1. Code Page Descriptions
Name Description ID
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- 936

80, EUC encoding
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

* PowerMart and PowerCenter use these code pages.
Note: Select IBM EBCDIC as your source database connection code page only if you access
When you enable data code page validation, PowerMart and PowerCenter support UTF-8 for
target code pages only.
Code Pages 171

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 Default

MS1250 Binary
Latin1
MS1252
ISO-8859-9
UTF-8
Arabic Saudi Arabia ISO-8859-6 Default

MS1256 Binary
UTF-8
Belorussian Belarus ISO-8859-5 Default

MS1251 Binary
UTF-8
Bulgarian Bulgaria ISO-8859-5 Default

MS1251 Binary
UTF-8
Canadian French French-Canada Latin1 Default

MS1252 Binary
ISO-8859-9
UTF-8
IBM297
Catalan Catalonia Latin1 Default

MS1252 Binary
ISO-8859-9
UTF-8
Croatian Croatia ISO-8859-2 Croatian

MS1250 Binary
UTF-8
Cyrillic Serbian Yugoslavia ISO-8859-5 Default

MS1251 Binary
UTF-8
Czech Czech Republic ISO-8859-2 Czech

MS1250 Binary
UTF-8

Danish Denmark Latin1 Danish

MS1252 Binary
ISO-8859-9
UTF-8
Dutch Netherlands Latin1 Default

Dutch-Belgium MS1252 Binary
ISO-8859-9
UTF-8
IBM037
English United States US-ASCII Binary

Australia Latin1 Default
Canada MS1252
South Africa UTF-8
United Kingdom IBM037
IBM285
Estonian Estonia ISO-8859-4 Estonian

ISO-8859-10 Binary
MS1257
UTF-8
Farsi Iran ISO-8859-6 Default

UTF-8 Binary
Finnish Finland Latin1 Finnish

MS1252 Binary
ISO-8859-9
UTF-8
French France Latin1 Default

French-Belgium MS1252 Binary
French-Canada ISO-8859-9
French-Switzerland UTF-8
IBM297
German Germany Latin1 Default

Austria MS1252 Binary
German-Switzerland ISO-8859-9
UTF-8
IBM273
Greek Greece ISO-8859-7 Default

MS1253 Binary
UTF-8
Hebrew Israel ISO-8859-8 Default

MS1255 Binary
UTF-8
Hungarian Hungary ISO-8859-2 Hungarian

MS1250 Binary
UTF-8
Code Page Reference 173

Italian Italy Latin1 Default

Italian-Switzerland MS1252 Binary
ISO-8859-9
UTF-8
IBM280
Japanese Japan JapanEUC Binary

MS932
UTF-8
IBM930
Korean Korea MS949 Binary

MS1361
UTF-8
Latvian Latvia ISO-8859-4 Latvian

ISO-8859-10 Binary
MS1257
UTF-8
Lithuanian Lithuania ISO-8859-4 Lithuanian

ISO-8859-10 Binary
MS1257
UTF-8
Macedonian Macedonia ISO-8859-5 Default

MS1251 Binary
UTF-8
Norwegian Norway Latin1 Danish

MS1252 Binary
ISO-8859-9
UTF-8
Portuguese Portugal Latin1 Default

Brazil MS1252 Binary
ISO-8859-9
UTF-8
IBM037
Romanian Romania ISO-8859-2 Romanian

MS1250 Binary
UTF-8
Russian Russia ISO-8859-5 Default

MS1251 Binary
UTF-8
Serbian Yugoslavia ISO-8859-2 Default

MS1250 Binary
UTF-8
Simplified Chinese China MS936 Binary

UTF-8
IBM935

Slovak Slovakia ISO-8859-2 Slovak

MS1250
UTF-8
Slovenian Slovenia ISO-8859-2 Slovenian

MS1250 Binary
UTF-8
Spanish Spain Latin1 Spanish

Argentina MS1252 Traditional Spanish
Chile ISO-8859-9 Binary
Mexico UTF-8
Swedish Sweden Latin1 Swedish

MS1252 Binary
ISO-8859-9
UTF-8
Thai Thailand MS874 Thai

UTF-8 Binary
Turkish Turkey ISO-8859-9 Turkish

ISO-8859-3 Binary
MS1254
UTF-8
Ukrainian Ukraine ISO-8859-5 Ukrainian

MS1251 Binary
UTF-8
Vietnamese Vietnam MS1258 Vietnamese

UTF-8 Binary
Code Page Reference 175

Informatica Code Page Relationships
For accurate data movement and transformation, make sure the code pages of each
PowerMart and PowerCenter 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 PowerMart and PowerCenter
components:
Table A-3. Code Page Compatibility
Source (including relational, flat file, and Subset of target.

ERP) 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.

Table A-3. Code Page Compatibility
Standalone Repository Compatible with Informatica Client and Server.
Informatica Client Compatible with Informatica Server and repository.
pmcmd Identical to Informatica Server.
For details on code page compatibility between components, see “Globalization Overview” on
page 9.
Informatica Code Page Relationships 177

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:
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.
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)

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 IBM037 IBM EBCDIC US IBM037 (IBM EBCDIC US IBM037 (IBM EBCDIC US
English) English) English) English)
Latin1(ISO 8859-1 Latin1 (ISO 8859-1 Latin1 (ISO 8859-1
Western European) Western European) Western European)
MS 1252 (MS Windows US-ASCII (7-bit ASCII) MS 1252 (MS Windows
Latin1 (ANSI), superset of Latin1 (ANSI), superset of
Latin1) Latin1)
UTF-8 (UTF-8 encoding of
Unicode)
IBM273 (IBM EBCDIC IBM273 (IBM EBCDIC IBM273 (IBM EBCDIC IBM273 (IBM EBCDIC
German) German) German German
US-ASCII (7-bit ASCII) UTF-8 (UTF-8 encoding of
Unicode)
Italian) Italian) Italian) Italian)
Unicode)
IBM285 (IBM EBCDIC UK IBM285 (IBM EBCDIC UK IBM285 (IBM EBCDIC UK IBM285 (IBM EBCDIC UK
English) English) English) English)
Unicode)
French) French) French) French)
Unicode)
International Latin-1) International Latin-1) International Latin-1) International Latin-1)
Unicode)
Code Page Compatibility 179

Japanese) Japanese) Japanese) Japanese)
JapanEUC (Japanese JapanEUC (Japanese JapanEUC (Japanese
Extended UNIX Code Extended UNIX Code Extended UNIX Code
(incl. JIS X 0212)) (incl. JIS X 0212)) (incl. JIS X 0212))
MS932 (MS Windows MS932 (MS Windows MS932 (MS Windows
Japanese, superset of Japanese, superset of Japanese, superset of
Shift-JIS) Shift-JIS) Shift-JIS)
Unicode)
Simplified Chinese) Simplified Chinese) Simplified Chinese) Simplified Chinese)
Unicode)
Traditional Chinese) Traditional Chinese) Traditional Chinese) Traditional Chinese)
Unicode)
ISO-8859-2 (ISO 8859-2 ISO-8859-2 (ISO 8859-2 ISO-8859-2 (ISO 8859-2 ISO-8859-2 (ISO 8859-2
Eastern European) Eastern European) Eastern European) Eastern European)
Unicode)
Southeast European) Southeast European) Southeast European) Southeast European)
Unicode)
Baltic) Baltic) Baltic) Baltic)
Unicode)
Cyrillic) Cyrillic) Cyrillic) Cyrillic)
Unicode)
Arabic) Arabic) Arabic) Arabic)
Unicode)
Greek) Greek) Greek) Greek)
UTF-8 (UTF-8 encoding of UTF-8 (UTF-8 encoding of
Unicode) Unicode)
Hebrew) Hebrew) Hebrew) Hebrew)
Unicode)

Latin 5 (Turkish)) Latin 5 (Turkish)) Latin 5 (Turkish)) Latin 5 (Turkish))
Unicode)
ISO-8859-10 (ISO 8859- ISO-8859-10 (ISO 8859- ISO-8859-10 (ISO 8859- ISO-8859-10 (ISO 8859-
10 Latin 6 (Nordic)) 10 Latin 6 (Nordic)) 10 Latin 6 (Nordic)) 10 Latin 6 (Nordic))
Unicode)
ISO-8859-15 (ISO 8859- ISO-8859-15 (ISO 8859- ISO-8859-15 (ISO 8859- ISO-8859-15 (ISO 8859-
15 Latin 9 (Western 15 Latin 9 (Western 15 Latin 9 (Western 15 Latin 9 (Western
European)) European)) European)) European))
Unicode)
JapanEUC (Japanese JapanEUC (Japanese JapanEUC (Japanese JapanEUC (Japanese

Extended UNIX Code Extended UNIX Code Extended UNIX Code Extended UNIX Code
(including JIS X 0212)) (including JIS X 0212)) (including JIS X 0212)) (including JIS X 0212))
IBM930 (IBM EBCDIC IBM930 (IBM EBCDIC IBM930 (IBM EBCDIC
Japanese) Japanese) Japanese)
JEF (Japanese EBCDIC JEF (Japanese EBCDIC JEF (Japanese EBCDIC
Fujitsu) Fujitsu) Fujitsu)
JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE
KEIS (HITACHI KEIS KEIS (HITACHI KEIS KEIS (HITACHI KEIS
MELCOM (MITSUBISHI MELCOM (MITSUBISHI MELCOM (MITSUBISHI
MELCOM Japanese) MELCOM Japanese) MELCOM Japanese)
UNISYS (UNISYS UNISYS (UNISYS UNISYS (UNISYS
Unicode)
JEF (Japanese EBCDIC JEF (Japanese EBCDIC JEF (Japanese EBCDIC JEF (Japanese EBCDIC
Fujitsu) Fujitsu) Fujitsu) Fujitsu)
(including JIS X 0212)) (including JIS X 0212)) (including JIS X 0212))
US-ASCII (7-bit ASCII)

JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE
KEIS (HITACHI KEIS KEIS (HITACHI KEIS KEIS (HITACHI KEIS KEIS (HITACHI KEIS
Latin1 (ISO 8859-1 Latin1 (ISO 8859-1 Latin1 (ISO 8859-1 Latin1 (ISO 8859-1
Western European) Western European) Western European) Western European)
IBM037 (IBM EBCDIC US IBM037 (IBM EBCDIC US IBM037 (IBM EBCDIC US
English) English) English)
Latin 1 (ANSI), superset of Latin 1 (ANSI), superset of Latin 1 (ANSI), superset of
Latin1) Latin1) Latin1)
Unicode)
MELCOM (MITSUBISHI MELCOM (MITSUBISHI MELCOM (MITSUBISHI MELCOM (MITSUBISHI

MELCOM Japanese) MELCOM Japanese) MELCOM Japanese) MELCOM Japanese)
MS874 (MS-DOS Thai, MS874 (MS-DOS Thai, MS874 (MS-DOS Thai, MS874 (MS-DOS Thai,
superset of TIS 620) superset of TIS 620) superset of TIS 620) superset of TIS 620)
Unicode)

MS932 (MS Windows MS932 (MS Windows MS932 (MS Windows MS932 (MS Windows
Japanese, superset of Japanese, superset of Japanese, superset of Japanese, superset of
Shift-JIS) Shift-JIS) Shift-JIS) Shift-JIS)
IBM930 (IBM EBCDIC IBM930 (IBM EBCDIC IBM930 (IBM EBCDIC
(incl. JIS X 0212)) (incl. JIS X 0212)) (incl. JIS X 0212))
JEF (Japanese EBCDIC JEF (Japanese EBCDIC JEF (Japanese EBCDIC
Fujitsu) Fujitsu) Fujitsu)
JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE JIPSE (NEC ACOS JIPSE
KEIS (HITACHI KEIS KEIS (HITACHI KEIS KEIS (HITACHI KEIS
MELCOM (MITSUBISHI MELCOM (MITSUBISHI MELCOM (MITSUBISHI
MELCOM Japanese) MELCOM Japanese) MELCOM Japanese)
UNISYS (UNISYS UNISYS (UNISYS UNISYS (UNISYS
Unicode)
Simplified Chinese, Simplified Chinese, Simplified Chinese, Simplified Chinese,
superset of GB 2312-80, superset of GB 2312-80, superset of GB 2312-80, superset of GB 2312-80,
EUC encoding) EUC encoding) EUC encoding) EUC encoding)
Unicode)
Korean, superset of KS C Korean, superset of KS C Korean, superset of KS C Korean, superset of KS C
5601-1992) 5601-1992) 5601-1992) 5601-1992)
Unicode)
Traditional Chinese, Traditional Chinese, Traditional Chinese, Traditional Chinese,
superset of Big 5) superset of Big 5) superset of Big 5) superset of Big 5)
Unicode)
Latin 2 (Central Europe)) Latin 2 (Central Europe)) Latin 2 (Central Europe)) Latin 2 (Central Europe))
Unicode)
Cyrillic (Slavic)) Cyrillic (Slavic)) Cyrillic (Slavic)) Cyrillic (Slavic))
Unicode)

Latin 1 (ANSI), superset of Latin 1 (ANSI), superset of Latin 1 (ANSI), superset of Latin 1 (ANSI), superset of
Latin1) Latin1) Latin1) Latin1)
IBM037 (IBM EBCDIC US IBM037 (IBM EBCDIC US IBM037 (IBM EBCDIC US
English) English) English)
Latin1 (ISO 8859-1 Latin1 (ISO 8859-1 Latin1 (ISO 8859-1
Western European) Western European) Western European)
Unicode)
Greek) Greek) Greek) Greek)
Unicode)
Latin 5 (Turkish), superset Latin 5 (Turkish), superset Latin 5 (Turkish), superset Latin 5 (Turkish), superset
of ISO 8859-9) of ISO 8859-9) of ISO 8859-9) of ISO 8859-9)
Unicode)
Hebrew) Hebrew) Hebrew) Hebrew)
Unicode)
Arabic) Arabic) Arabic) Arabic)
Unicode)
Baltic Rim) Baltic Rim) Baltic Rim) Baltic Rim)
Unicode)
Vietnamese) Vietnamese) Vietnamese) Vietnamese)
Unicode)
Korean (Johab)) Korean (Johab)) Korean (Johab)) Korean (Johab))
Unicode)
UNISYS (UNISYS UNISYS (UNISYS UNISYS (UNISYS UNISYS (UNISYS


US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII)
IBM037 (IBM EBCDIC US
English)
IBM273 (IBM EBCDIC
German)
IBM280 (IBM EBCDIC
Italian)
IBM285 (IBM EBCDIC UK
English)
IBM297 (IBM EBCDIC
French)
IBM500 (IBM EBCDIC
International Latin-1)
IBM930 (IBM EBCDIC
Japanese)
IBM935 (IBM EBCDIC
Simplified Chinese)
IBM937 (IBM EBCDIC
Traditional Chinese)
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.
JEF (Japanese EBCDIC
Fujitsu)
JIPSE (NEC ACOS JIPSE
Japanese)
JIS X 0212))
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
Latin1 (ISO 8859-1
Western European)

US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) US-ASCII (7-bit ASCII) MS874 (MS-DOS Thai,
superset of TIS 620)
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
MS936 (MS Windows
Simplified Chinese,
superset of GB 2312-80,
EUC encoding)
MS949 (MS Windows
Korean, superset of KS C
5601-1992)
Korean (Johab))
MS950 (MS Windows
Traditional Chinese,
superset of Big 5)
MS1250 (MS Windows
Latin 2 (Central Europe))
MS1251 (MS Windows
Cyrillic (Slavic))
MS1252 (MS Windows
Latin 1 (ANSI), superset of
Latin1)
MS1253 (MS Windows
Greek)
MS1254 (MS Windows
Latin 5 (Turkish), superset
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)
UTF-8 (UTF-8 encoding of
Unicode)
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.

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:
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)
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-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>)

Table A-7. Latin1 to MS Latin1 Character Conversion
Characters lost when converting from Latin1 (ISO-8859-1) to MS1252 MS Latin1
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)

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:
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)
Converting from MS Shift JIS to JapanEUC

Shift JIS to JapanEUC:
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)

Table A-12. IBM EBCDIC Japanese to JapanEUC Character Conversion
Characters lost when converting from IBM930 (IBM EBCDIC Japanese) to JapanEUC
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)
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:
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)

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)

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)
Converting from IBM EBCDIC Japanese to MS Shift JIS

EBCDIC Japanese to MS Shift JIS:
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)

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)
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>)
Converting from MS Shift JIS to IBM EBCDIC Japanese

Shift JIS to IBM EBCDIC Japanese:
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-15. MS Shift JIS to IBM EBCDIC Japanese Character Conversion
Characters lost when converting from MS932 (MS Shift JIS) to IBM930 (IBM EBCDIC Japanese)
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)

Index
A Informatica Server installation guidelines 71
Access97
See Microsoft Access97 C
Aggregate treat nulls as zero
setting on UNIX 112 Character data sets
setting on Windows NT/2000 80 See also Designer Guide
Aggregate treat rows as insert handling options for Microsoft SQL Server and
setting on UNIX 113 PeopleSoft on Oracle 81
setting on Windows NT/2000 81 character sizes
Aggregator transformation double byte 18
setting up for prior version compatibility 80, 112 multibyte 18
treating nulls as zero 80, 112 single byte 18
treating rows as insert 81, 113 client tools
AIX See Informatica Client
shared library environment variable 115 COBOL
ANSI code page (Windows NT/2000) connectivity 5
definition 17 code page relaxation
ASCII configuring the Informatica Client 28
8-bit ASCII 13 configuring the Informatica Server 27
See also Unicode mode Informatica Client validation 28
overview 13 Informatica Server validation 29
setting ASCII data movement mode on NT/2000 83 code pages
setting ASCII data movement mode on UNIX 110 advanced external procedure 21
ANSI (Windows NT/2000) 17
character loss during conversions 186
B choosing 18
compatibility 178
backup domain controller compatibility between components 177
207
compatibility diagram 22 between code pages 18, 178
compatibility overview 18 configuring
configuring NT/2000 Server 70 Informatica Server (UNIX) 109
configuring UNIX Server 106 Informatica Server (Windows NT/2000) 75
converting from IBM EBCDIC Japanese to JapanEUC ODBC data sources 165
197 connect string
converting from IBM EBCDIC Japanese to MS Shift examples 5
JIS 203 setting on UNIX 110
converting from IBM EBCDIC US English to Latin1 setting on Windows NT/2000 79
188 syntax 5
converting from JapanEUC to IBM EBCDIC Japanese connecting
198 Informatica Client to IBM DB2 57
converting from JapanEUC to MS Shift JIS 192 Informatica Client to Informix 56, 60, 93
converting from Latin1 to IBM EBCDIC US English Informatica Client to Microsoft Access97 59
189 Informatica Client to Microsoft Excel 59
converting from Latin1 to MS Latin1 187 Informatica Client to Microsoft SQL Server 52
converting from MS Latin1 to Latin1 187 Informatica Client to Oracle 49, 51
converting from MS Shift JIS to IBM EBCDIC Informatica Client to Sybase SQL Server 54
Japanese 204 Informatica Client to Teradata 60
converting from MS Shift JIS to JapanEUC 189 Informatica Server to IBM DB2 (UNIX) 122
ERP sources 21, 176 Informatica Server to IBM DB2 (Windows NT/2000)
ERP targets 22 91
external procedure 21 Informatica Server to Informix (UNIX) 121
flat file sources 20, 21, 176 Informatica Server to Informix (Windows NT/2000)
flat file targets 20, 22, 176 89
global repository 176 Informatica Server to Microsoft Access97 92
Informatica Client 20, 177 Informatica Server to Microsoft Excel 92
Informatica Server 20, 135, 176 Informatica Server to Microsoft SQL Server 88
list of available code pages 170 Informatica Server to ODBC data sources (UNIX) 128
local repository 176 Informatica Server to Oracle (UNIX) 116
lookup database 21 Informatica Server to Oracle (Windows NT/2000) 85
OEM code page (Windows NT/2000) 17 Informatica Server to Sybase SQL Server (UNIX) 120
overview 16 Informatica Server to Sybase SQL Server (Windows
pmcmd 21, 177 NT/2000) 88
reference 172 Informatica Server to Teradata 93
related languages 172 to UNIX databases 115
related sort orders 172 to Windows NT/2000 databases 85
related territories 172 connections
relational sources 20, 21, 176 IPX/SPX 135
relational targets 20, 22, 176 TCP/IP 135
relaxed validation for sources and targets 27 connectivity
repository 20, 21, 177 COBOL 5
sort order overview 21 connect string examples 5
stored procedure database 21 diagram of 3
subsets defined 176 Informatica Client 3
supersets defined 176 native drivers 4
supported code pages 170 overview 3
UNIX 16 conversions
verifying compatibility 179 IBM EBCDIC Japanese to JapanEUC code pages 197
Windows 17 IBM EBCDIC Japanese to MS Shift JIS code pages
compatibility 203
208 Index
IBM EBCDIC US English to Latin1 code pages 188 setting on Windows NT/2000 83
JapanEUC to IBM EBCDIC Japanese code pages 198 Date Handling 4.0 Compatibility
JapanEUC to MS Shift JIS code pages 192 setting on UNIX 112
Latin1 to IBM EBCDIC US English code pages 189 setting on Windows NT/2000 81
Latin1 to MS Latin1 code pages 187 dates
MS Latin1 to Latin1 code pages 187 setting up prior version compatibility (UNIX) 112
MS Shift JIS to IBM EBCDIC Japanese code pages setting up prior version compatibility (Windows NT/
204 2000) 80
MS Shift JIS to JapanEUC code pages 189 DB2
Create Indicator Files See IBM DB2
setting on UNIX 113 DB2 Key
setting on Windows NT/2000 84 See also IBM DB2
creating setting on UNIX 111
ODBC data sources 161 setting on Windows NT/2000 77
repositories 65 DB2CODEPAGE
configuring DB2 58
DB2INSTANCE
D configuring DB2 58
deadlock retries
data movement mode setting number of (UNIX) 114
changing 14 setting number of (Windows NT/2000) 81
setting on UNIX 110 Deadlock Sleep Before Retry
setting on Windows NT/2000 83 setting on UNIX 114
Database Name setting on Windows NT/2000 82
entering (UNIX) 109 Designer
entering (Windows NT/2000) 79 installing 47
Database Password DHCP (Dynamic Host Configuration Protocol)
setting on UNIX 109 avoiding use with Informatica Server 70, 106
setting on Windows NT/2000 79 directories
Database Type data cache 137
setting on UNIX 110 indexes 137
setting on Windows NT/2000 79 Informatica Server 72
Database User root 137
setting on UNIX 109 server defaults 135
setting on Windows NT/2000 79 server variables 135
databases Disable Recovery
connecting to (UNIX) 115 setting on UNIX 112
connecting to (Windows NT/2000) 85 setting on Windows NT/2000 84
connecting to IBM DB2 57, 91, 122 documentation
connecting to Informix 56, 89, 121 conventions xvii
connecting to Microsoft Access97 59, 92 description xiv
connecting to Microsoft Excel 59, 92 online xvi, 47
connecting to Microsoft SQL Server 52, 88 Domain
connecting to Oracle 49, 85, 116 setting on Windows NT/2000 79
connecting to Sybase SQL Server 54, 88, 120 DSN (data source name)
connecting to Teradata 60, 93 See also ODBC data sources
connectivity overview 134
source code page 20
target code page 20
Date Display Format
E
setting on UNIX 113 editing
Index 209
temp_server 138 definition 64
8-bit ASCII promoting 66
definition 13 globalization
environment variables overview 10
DB2CODEPAGE 58
DB2INSTANCE 58
LANG_C 16 H
LC_ALL 16
LC_CTYPE 16 HP/UX
LD_LIBRARY_PATH 115 shared library environment variable 107, 115
LIBPATH 115
NLS_LANG 39
PM_HOME 109 I
SHLIB_PATH 107, 115
ERP sources IBM DB2
code page 21 Client Configuration Assistant program 58, 91
ERP targets connect string example 5
code page 22 connecting to Informatica Client 57
Error Log File connecting to Informatica Server (UNIX) 122
setting on UNIX 110 connecting to Informatica Server (Windows NT/
error logs 2000) 91
entering filename on UNIX 110 ODBC driver 45
Event Log File ODBC issues 157
setting on UNIX 110 platform key 77, 111
event logs setting DB2CODEPAGE 58, 91
enabling 83, 110 setting DB2INSTANCE 58, 91
filename for 110 incremental aggregation
Excel upgrading cache files 150
See Microsoft Excel indicator files
external procedures configuring Informatica Server to create (Windows
See also Designer Guide NT/2000) 84
directory for 72 Informatica
documentation xiv
Webzine xviii
F Informatica Client
See also Informatica Server
flat files code page 20, 177
connectivity 5 connecting to databases 49
directory for targets 72 connectivity requirements 3
source code page 20, 21, 176 installing 47
target code page 20, 22, 176 system requirements 2
Informatica Server
See also Informatica Client
G automatically starting (Windows NT/2000) 97
changing servers 138
Generate Stored Procedure for Prepared Statement option code page 20, 135, 176
uncheck for Microsoft SQL Server repositories 53 configuring (UNIX) 109
global objects configuring (Windows NT/2000) 75
upgrading 148 configuring NT/2000 Server 70
global repositories configuring UNIX Server 106
code page 176 connection duration option (UNIX) 111
creating 66 connection duration option (Windows NT/2000) 83
210 Index
connectivity overview 134 IPX/SPX network protocol
connectivity requirements 4 address 78
data movement mode (UNIX) 110 connection requirement 135
data movement mode (Windows NT/2000) 83 requirement for Informatica Server 4
date display format (UNIX) 113 server settings 140
date display format (Windows NT/2000) 83
file directories 137
installation guidelines (Windows NT/2000) 71 K
installing (Windows NT/2000) 73
installing multiple (UNIX) 107 Keep Repeating Sessions in LM Shared Memory
overriding locks option 84, 112 setting on UNIX 111
registering 135, 137, 138, 140 setting on Windows NT/2000 84
root directory 137 keys
selecting a code page 135 required to run Informatica Server 76
setting TCP/IP port (UNIX) 109
starting (UNIX) 125
starting from control panel (Windows NT/2000) 95 L
stopping (UNIX) 126
stopping (Windows NT/2000) 97 LANG_C environment variable
system requirements 2 setting locale in UNIX 16
troubleshooting installation (Windows NT/2000) 99 language
user types (Windows NT) 71 code page reference 172
variable directories 72 LC_ALL environment variable
variables for 135 setting locale in UNIX 16
Informix LC_CTYPE environment variable
connect string syntax 5 setting locale in UNIX 16
connecting to Informatica Client 56, 60, 93 LD_LIBRARY_PATH 115
connecting to Informatica Server (UNIX) 121 LIBPATH 115
connecting to Informatica Server (Windows NT/ Load Manager
2000) 89 connection duration option (UNIX) 111
installing Merant ODBC drivers 45 connection duration option (Windows NT/2000) 83
ODBC driver 45 setting on UNIX 110
platform key 111 Load Manager Allow Debugging
platform key (Windows NT/2000) 76 setting on UNIX 113
SetNet 32 configuration 56, 90 setting on Windows NT/2000 84
Informix Key Load Manager Shared Memory
setting on UNIX 111 setting on UNIX 110
setting on Windows NT/2000 76 setting on Windows NT/2000 83
input locales 12 Load Manager Stay Connected to Repository Duration
installation setting on UNIX 111
minimum system requirements 2 local repositories
steps for upgrade 7 code page 176
installing definition 64
Informatica Client 47 promoting to global 66
Informatica Server (Windows NT/2000) 73 registering multiple servers 134
ODBC drivers on Informatica Client 45 locales
ODBC drivers on Informatica Server (UNIX) 127 overview 12
troubleshooting (Windows NT/2000) 99 locks
Windows NT/2000 guidelines for 71 overriding option 84, 112
IPX/SPX Address logging
setting on Windows NT/2000 78 events, option for 83, 110
Lookup Cache Initialize 147
Index 211
Lookup databases setting maximum number of connections (Windows
setting maximum number of connections in Windows NT/2000) 81
NT/2000 81 Microsoft SQL Server Key
Lookup transformations setting on Windows NT 76
upgrading files 147 MS Access97
ODBC driver 45
MS Excel
M ODBC driver 45
MS Exchange Profile
mapping partitions option for post-session email 83
upgrading 148 setting on Windows NT/2000 83
Max Lookup/SP DB Connections
setting on UNIX 114
setting on Windows NT/2000 81
Max MSSQL Connections
N
setting on UNIX 114 native connect string
setting on Windows NT/2000 81 See connect string
Max Sessions Net8
setting on UNIX 110 using to connect Informatica Client to Oracle 51
setting on Windows NT/2000 83 using to connect Informatica Server to Oracle (UNIX)
Max Sybase Connections 118
setting on UNIX 114 using to connect Informatica Server to Oracle
setting on Windows NT/2000 81 (Windows NT) 87
MBCS (Multibyte Character Set) NLS_LANG
definition 13 setting locale 39
Merant ODBC drivers Number of Deadlock Retries
platform-specific drivers required 45, 157 setting on UNIX 114
uninstalling 46 setting on Windows NT/2000 81
Microsoft Access97
connecting to Informatica Client 59
connecting to Informatica Server 92 O
ODBC issues 157
Microsoft Excel ODBC
connecting to Informatica Client 59 connecting to databases in Informatica Server 156
connecting to Informatica Server 92 ODBC (Open Database Connectivity)
ODBC issues 60, 157 See also ODBC calls
using PmNullPasswd 92 See also ODBC data sources
using PmNullUser 92 connecting to databases in Informatica Client 156
Microsoft SQL Server database-specific notes 157
connect string syntax 5 definition 45
connecting to Informatica Client 52 diagram of 154
connecting to Informatica Server 88 drivers description 154
Create temporary stored procedures for prepared SQL drivers for Microsoft Excel 92
statements 54 installing drivers on Informatica Client 45
determining code page and sort order 34 installing on Informatica Server (UNIX) 127
Generate Stored Procedure for Prepared Statement Merant driver issues 45, 157
option 53 overview 154
ODBC driver 45 platform key 77, 111
ODBC issues 53, 157 requirement for Informatica Client 4
platform key 76 support for MS Excel-compatible drivers 59
setting Char handling options 81 uninstalling Merant drivers 46
ODBC Administrator
212 Index
description 154
ODBC calls
P
Informatica Client 158 password
Informatica Server 160 entering database (UNIX) 109
overview 158 entering database (Windows NT/2000) 79
ODBC data sources entering repository (UNIX) 110
configuring 165 entering repository (Windows NT/2000) 79
connecting to (UNIX) 128 PeopleSoft on Oracle
creating 161 setting Char handling options 81
deleting 166 Perform Event Logging
overview 155 setting on UNIX 110
System 155 setting on Windows NT/2000 83
troubleshooting 167 Platform Key
User 155 setting on UNIX 111
ODBC Driver Manager setting on Windows NT/2000 76
description 154 PM Cache Directory
ODBC Key setting on Unix 111
setting on Windows NT/2000 77 PM Password
OEM code page (Windows NT/2000) setting on UNIX 110
definition 17 PM Server 3.X aggregate compatibility
online help setting on UNIX 112
Informatica Client 47 setting on Windows NT/2000 80
Oracle PM User
changing locale using NLS_LANG 52 setting on UNIX 110
connect string syntax 5 PM_HOME 109
connecting to Informatica Client 49, 51 pmcmd command line program
connecting to Informatica Server (UNIX) 116 code page issues 21, 177
connecting to Informatica Server (Windows NT/ communicating with the Informatica Server 21
2000) 85 starting/stopping Informatica Server (Windows NT/
displaying non-ASCII characters 52, 61 2000) 98
installing Merant ODBC drivers 45 stopping Informatica Server (UNIX) 126
ODBC driver 45 pmconfig program
platform key 111 using 109
platform key (Windows NT/2000) 76 PmNullPasswd
setting locale with NLS_LANG 39 reserved word 156
tips 67 PmNullUser
version handling options (UNIX) 113 reserved word 156
version handling options (Windows NT/2000) 81 pmrep
Oracle Key See Repository Guide
setting on UNIX 111 PMServer 4.0 date handling compatibility
setting on Windows NT 76 setting on UNIX 112
Oracle Version setting on Windows NT/2000 81
setting on UNIX 113 pmserver command
setting on Windows NT/2000 81 starting server (UNIX) 125
Override Exec Locking pmserver.cfg
setting on UNIX 112 file 109
setting on Windows NT/2000 84 post-session
email option for Windows NT/2000 83
PowerCenter
installation steps 6
minimum system requirements 2
Index 213
repository version number 142 types of 64
upgrading steps 7 upgrading, preliminary steps 143
PowerMart version number 142
installation steps 6 Repository Manager
minimum system requirements 2 installing 47
repository version number 142 Repository Name
upgrading steps 7 setting on UNIX 109
powrmart.ini setting on Windows NT/2000 79
adding entry for relaxed code page validation 28 Repository Password
adding entry for Teradata 60 setting on UNIX 110
primary domain controller 71 setting on Windows NT/2000 79
privileges Repository User
registering Informatica Server 134 setting on UNIX 110
root directory
R entering 137
server variable 137
Recache from Database
upgrading Lookup transformations 147
Recache if Stale
upgrading Lookup transformations 147
S
recovery process SAP BW
disabling 112 See Designer Guide
registering server
Informatica Server 135, 137, 138, 140 See Informatica Server
multiple servers on local repository 134 See also database-specific server
release notes Server Manager
installing 47 installing 47
repositories overview 134
changing a code page 65 registering the Informatica Server 135, 138
code page 20, 21, 66, 177 stopping server (Windows NT) 97
connectivity 3 troubleshooting 103
creating 65 server variables
database password 66 description 135
database user name 66 directories on Windows NT/2000 72
entering name for Informatica Server (UNIX) 109 list 136
entering name for Informatica Server (Windows NT/ session log 135
2000) 79 ServerPort
global 64 setting on UNIX 109
local 64 Session Log in UTF8
naming 66 setting on UNIX 113
native connect string 66 setting on Windows NT/2000 84
ODBC data source 66 session logs
open architecture 64 directory for 72
overview 64 server variable for 135
restricted characters for repository name 65 sessions
size requirements 2, 7 handling limited slots option (UNIX) 111
standalone 64 handling limited slots option (Windows NT/2000) 84
system requirements 2 setting maximum (UNIX) 110
tips 67 setting maximum (Windows NT/2000) 83
troubleshooting, upgrading 151 sort order 21
214 Index
shared memory Sybase SQL Server
base address setting 83 connect string example 5
options for repeating sessions (UNIX) 111 connecting to Informatica Client 54
options for repeating sessions (Windows NT/2000) 84 connecting to Informatica Server (UNIX) 120
setting for Load Manager 83 connecting to Informatica Server (Windows NT) 88
Shared Memory Base Address installing Merant ODBC drivers 45
setting on Windows NT/2000 83 ODBC issues 55, 157
SHLIB_PATH 115 platform key (UNIX) 111
Solaris platform key (Windows NT/2000) 76
shared library environment variable 107, 115 set prepare method to 2-Full 55
sort order setting key on Windows NT/2000 76
code page 21 setting maximum connections (Windows NT/2000)
code page reference 172 81
source databases SybaseIQLocaltoPmServer
code page 20, 21, 176 setting on UNIX 114
connecting through ODBC (UNIX) 128 system locales
connectivity 3 definition 12
source definitions system requirements
See Designer Guide minimum installation requirements 2
SQL scripts
installing 47
SQL*Net
using to connect Informatica Client to Oracle 49
T
using to connect Informatica Server to Oracle (UNIX) target databases
116 code page 20, 22, 176
using to connect to Informatica Server to Oracle connecting through ODBC (UNIX) 128
(Windows NT/2000) 85 connectivity 3
standalone repositories target definitions
description 64 See Designer Guide
starting TCP/IP Host Address
Informatica Server (UNIX) 125 setting on Windows NT/2000 78
Informatica Server (Windows NT/2000) 95 TCP/IP network protocol
Informatica Server automatically (Windows NT/2000) configuration restrictions 70, 106
97 connection requirement 135
Stay Connected for (secs) host address 78
setting on Windows NT/2000 83 port number 78
stopping requirement for Informatica Server 4
Informatica Server (UNIX) 126 server settings 139
Informatica Server (Windows NT/2000) 97 setting server port 109
Stored Procedure databases TCP/IP Port Number
setting number of connections (Windows NT/2000) setting on Windows NT 78
81 temp_server
subset editing 138
defined for code page compatibility 18 temporary files
superset directory for 72
defined for code page compatibility 18 Teradata
Sybase adding entry in powrmart.ini 60
ODBC driver 45 connecting to Informatica Client 60
Sybase Key connecting to Informatica Server 93
setting on UNIX 111 ODBC driver 45
setting on Windows NT/2000 76 territory
Index 215
code page reference 172 User Trusted Connection
testing specifying for NT integrated security 79
date display formats 83 users
Treat Char as Char on read (Microsoft SQL Server and types for Informatica Server (Windows NT) 71
PeopleSoft on Oracle) UTF-8
setting on Windows NT/2000 81 definition 13
troubleshooting
installation (Windows NT/2000) 99
ODBC data sources 167
upgrading repositories 151
V
tutorials Validate Data Code Pages
See also Getting Started setting on UNIX 113
installing 47 setting on Windows NT/2000 84
verifying Informatica Server starts (Windows NT/2000)
procedure 96
U versions
handling Aggregator transformation (UNIX) 112
Unicode mode handling Aggregator transformation (Windows NT/
See also ASCII 2000) 80
overview 13 handling Oracle (UNIX) 113
setting data movement mode (UNIX) 110 handling Oracle (Windows NT/2000) 81
uninstalling
Merant ODBC drivers 46 W
UNIX
configuring the Informatica Server 109 Warn about duplicate XML rows
connecting Informatica Server to databases 115 setting on Windows NT/2000 84
connecting to ODBC data sources 128 webzine
installing the Informatica Server 107 Informatica URL xviii
platform key 111 Windows 2000
pmconfig program 109 required permissions for session log file directory 72
pmserver.cfg 109 Windows NT
starting Informatica Server 125 configuring Informatica Server 75
stopping Informatica Server 125, 126 Windows NT/2000
UNIX environment variables automatically starting Informatica Server 97
LANG_C 16 backup domain controller 71
LC_ALL 16 connecting Informatica Server to databases 49
LC_CTYPE 16 installing Informatica Client 47
upgrading installing Informatica Server 73
external loader objects 149 platform key 76
global objects 148 primary domain controller 71
Lookup transformations 147 shared memory base address 83
mapping partitions 148 starting Informatica Server 95, 99, 100
overview 7 stopping Informatica Server 97
preliminary steps 143 user accounts 71
repositories 143 verifying Informatica Server starts 96
troubleshooting repository 151
Use Trusted Connection
setting on Windows NT 79 X
user locales
definition 12 XMLWarnDupRows
setting on UNIX 113
216 Index

Install

Uploaded by

Copyright:

Available Formats

Install

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Install

Uploaded by

Copyright:

Available Formats

Installation and Configuration

Copyright (c) 2001 Informatica Corporation.

Chapter 1: Installation and Configuration Overview . . . . . . . . . . . . . . 1

Chapter 2: Globalization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3: Installing and Configuring the Informatica Client . . . . . . 43

Chapter 5: Installing and Configuring the Informatica NT Server . . . 69

Chapter 6: Installing and Configuring the Informatica UNIX Server 105

Chapter 7: Registering the Informatica Server . . . . . . . . . . . . . . . . 133

Chapter 8: Upgrading a Repository . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 9: Using ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Appendix A: Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table of Contents vii

xii List of Tables

Welcome to PowerMart and PowerCenter, Informatica’s integrated suite of software products

About Informatica Documentation xv

About PowerCenter and PowerMart

If You Are Using PowerCenter

If You Are Using PowerMart

If you see… It means…

italicized text The word or set of words are especially emphasized.

boldfaced text Emphasized subjects.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

monospaced text This is a code example.

About this Book xvii

Accessing the Informatica Webzine

Visiting the Informatica Web Site

Visiting the Informatica Developer Network

North America / South America Africa / Asia / Australia / Europe

Informatica Corporation Informatica Software Ltd.

Other Informatica Resources xix

Relaxed Data Code Page Validation

Designer Features and Enhancements

Server Manager Features and Enhancements

Designer Features and Enhancements

New Features and Enhancements xxi

Informatica Server Enhancements

Server Manager Features and Enhancements

Transformation Language Enhancements

New Features and Enhancements xxiii

Minimum System Requirements

Table 1-1. Minimum System Requirements

Informatica Client Informatica Repository Informatica Server

Disk space 170 MB 70 MB of database space* 100 MB

RAM 128 MB 128 MB 256 MB

2 Chapter 1: Installation and Configuration Overview

Figure 1-1. PowerMart and PowerCenter Connectivity

Informatica Client Tools and Informatica Server Connections

Informatica Client Connections

PowerMart and PowerCenter Connectivity 3

Table 1-2. Informatica Client Connectivity Requirements

To connect the Informatica Client to the... You need...

Source databases ODBC connection for each source database

Target databases ODBC connection for each target database

Informatica Server TCP/IP or IPX/SPX

Informatica Server Connections

Table 1-3. Informatica Server Connectivity Requirements

To connect the Informatica Server to the... You need...

Repository Native database drivers or ODBC

Source databases Native database drivers or ODBC