Escolar Documentos
Profissional Documentos
Cultura Documentos
Configuration Guide
INFORMATICA POWERCENTER 6
INFORMATICA POWERMART 6
(VERSION 6.0)
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii
Transformation Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii
About PowerCenter and PowerMart . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Accessing the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xxv
Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
iii
iv
Table of Contents
Table of Contents
Table of Contents
Table of Contents
vii
Table of Contents
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Table of Contents
ix
Table of Contents
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.. 2
.. 6
.. 8
.. 9
. 10
. 11
. 12
. 13
. 15
. 16
. 21
. 39
. 43
. 53
. 56
. 58
. 61
194
202
203
203
List of Figures
xi
xii
List of Figures
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20
. 22
. 23
. 23
. 23
. 34
. 43
. 65
. 68
. 72
. 83
. 88
101
103
105
119
120
121
129
132
133
135
136
138
143
160
162
167
189
196
197
198
199
208
210
214
216
217
225
225
List of Tables
xiii
Table
Table
Table
Table
Table
Table
Table
Table
xiv
List of Tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.226
.227
.227
.230
.235
.236
.241
.242
Preface
Welcome to PowerCenterRT, PowerCenter, and PowerMart, Informaticas integrated suite of
software products that delivers an open, scalable data integration solution addressing the
complete life cycle for data warehouse and analytic application development. PowerCenter
and PowerMart combine the latest technology enhancements for reliably managing data
repositories and delivering information resources in a timely, usable, and efficient manner.
The PowerCenter/PowerMart metadata repository coordinates and drives a variety of core
functions including extracting, transforming, loading, and managing. The Informatica Server
can extract large volumes of data from multiple platforms, handle complex transformations
on the data, and support high-speed loads. PowerCenter and PowerMart can simplify and
accelerate the process of moving data warehouses from development to test to production.
Note: Unless otherwise indicated, when this guide mentions PowerCenter, it refers to both
xv
Designer
xvi
Preface
Compare objects. The Designer allows you to compare two repository objects of the same
type to identify differences between them. You can compare sources, targets,
transformations, mapplets, mappings, instances, or mapping/mapplet dependencies in
detail. You can compare objects across open folders and repositories.
Copying objects. In each Designer tool, you can use the copy and paste functions to copy
objects from one workspace to another. For example, you can select a group of transformations
in a mapping and copy them to a new mapping.
Custom tools. The Designer allows you to add custom tools to the Tools menu. This
allows you to start programs you use frequently from within the Designer.
Flat file targets. You can create flat file target definitions in the Designer to output data to
flat files. You can create both fixed-width and delimited flat file target definitions.
Heterogeneous targets. You can create a mapping that outputs data to multiple database
types and target types. When you run a session with heterogeneous targets, you can specify
a database connection for each relational target. You can also specify a file name for each
flat file or XML target.
Link paths. When working with mappings and mapplets, you can view link paths. Link paths
display the flow of data from a column in a source, through ports in transformations, to a
column in the target.
Linking ports. You can now specify a prefix or suffix when automatically linking ports between
transformations based on port names.
Lookup cache. You can use a dynamic lookup cache in a Lookup transformation to insert
and update data in the cache and target when you run a session.
Mapping parameter and variable support in lookup SQL override. You can use mapping
parameters and variables when you enter a lookup SQL override.
Mapplet enhancements. Several mapplet restrictions are removed. You can now include
multiple Source Qualifier transformations in a mapplet, as well as Joiner transformations
and Application Source Qualifier transformations for IBM MQSeries. You can also include
both source definitions and Input transformations in one mapplet. When you work with a
mapplet in a mapping, you can expand the mapplet to view all transformations in the
mapplet.
Metadata extensions. You can extend the metadata stored in the repository by creating
metadata extensions for repository objects. The Designer allows you to create metadata
extensions for source definitions, target definitions, transformations, mappings, and
mapplets.
Numeric and datetime formats. You can define formats for numeric and datetime values
in flat file sources and targets. When you define a format for a numeric or datetime value,
the Informatica Server uses the format to read from the file source or to write to the file
target.
Pre- and post-session SQL. You can specify pre- and post-session SQL in a Source Qualifier
transformation and in a mapping target instance when you create a mapping in the Designer.
The Informatica Server issues pre-SQL commands to the database once before it runs the
session. Use pre-session SQL to issue commands to the database such as dropping indexes
before extracting data. The Informatica Server issues post-session SQL commands to the
database once after it runs the session. Use post-session SQL to issue commands to a database
such as re-creating indexes.
Renaming ports. If you rename a port in a connected transformation, the Designer propagates
the name change to expressions in the transformation.
Tips. When you start the Designer, it displays a tip of the day. These tips help you use the
Designer more efficiently. You can display or hide the tips by choosing Help-Tip of the
Day.
Tool tips for port names. Tool tips now display for port names. To view the full contents
of the column, position the mouse over the cell until the tool tip appears.
View dependencies. In each Designer tool, you can view a list of objects that depend on a
source, source qualifier, transformation, or target. Right-click an object and select the View
Dependencies option.
Working with multiple ports or columns. In each Designer tool, you can move multiple ports
or columns at the same time.
Informatica Server
Add timestamp to workflow logs. You can configure the Informatica Server to add a
timestamp to messages written to the workflow log.
Expanded pmcmd capability. You can use pmcmd to issue a number of commands to the
Informatica Server. You can use pmcmd in either an interactive or command line mode.
The interactive mode prompts you to enter information when you omit parameters or
enter invalid commands. In both modes, you can enter a command followed by its
command options in any order. In addition to commands for starting and stopping
workflows and tasks, pmcmd now has new commands for working in the interactive mode
and getting details on servers, sessions, and workflows.
Error handling. The Informatica Server handles the abort command like the stop
command, except it has a timeout period. You can specify when and how you want the
Informatica Server to stop or abort a workflow by using the Control task in the workflow.
After you start a workflow, you can stop or abort it through the Workflow Monitor or
pmcmd.
New Features and Enhancements
xvii
Export session log to external library. You can configure the Informatica Server to write
the session log to an external library.
Flat files. You can specify the precision and field length for columns when the Informatica
Server writes to a flat file based on a flat file target definition, and when it reads from a flat
file source. You can also specify the format for datetime columns that the Informatica
Server reads from flat file sources and writes to flat file targets.
Write Informatica Windows Server log to a file. You can now configure the Informatica
Server on Windows to write the Informatica Server log to a file.
Metadata Reporter
List reports for jobs, sessions, workflows, and worklets. You can run a list report that lists
all jobs, sessions, workflows, or worklets in a selected repository.
Details reports for sessions, workflows, and worklets. You can run a details report to view
details about each session, workflow, or worklet in a selected repository.
Completed session, workflow, or worklet detail reports. You can run a completion details
report, which displays details about how and when a session, workflow, or worklet ran, and
whether it ran successfully.
Installation on WebLogic. You can now install the Metadata Reporter on WebLogic and
run it as a web application.
Repository Manager
Metadata extensions. You can extend the metadata stored in the repository by creating
metadata extensions for repository objects. The Repository Manager allows you to create
metadata extensions for source definitions, target definitions, transformations, mappings,
mapplets, sessions, workflows, and worklets.
pmrep security commands. You can use pmrep to create or delete repository users and
groups. You can also use pmrep to modify repository privileges assigned to users and
groups.
Tips. When you start the Repository Manager, it displays a tip of the day. These tips help
you use the Repository Manager more efficiently. You can display or hide the tips by
choosing Help-Tip of the Day.
Repository Server
The Informatica Client tools and the Informatica Server now connect to the repository
database over the network through the Repository Server.
xviii
Preface
Repository Server. The Repository Server manages the metadata in the repository
database. It accepts and manages all repository client connections and ensures repository
consistency by employing object locking. The Repository Server can manage multiple
repositories on different machines on the network.
Repository connectivity changes. When you connect to the repository, you must specify
the host name of the machine hosting the Repository Server and the port number the
Repository Server uses to listen for connections. You no longer have to create an ODBC
data source to connect a repository client application to the repository.
Transformation Language
New functions. The transformation language includes two new functions, ReplaceChr and
ReplaceStr. You can use these functions to replace or remove characters or strings in text
data.
SETVARIABLE. The SETVARIABLE function now executes for rows marked as insert or
update.
Workflow Manager
The Workflow Manager and Workflow Monitor replace the Server Manager. Instead of
creating a session, you now create a process called a workflow in the Workflow Manager. A
workflow is a set of instructions on how to execute tasks such as sessions, emails, and shell
commands. A session is now one of the many tasks you can execute in the Workflow Manager.
The Workflow Manager provides other tasks such as Assignment, Decision, and Event-Wait
tasks. You can also create branches with conditional links. In addition, you can batch
workflows by creating worklets in the Workflow Manager.
DB2 external loader. You can use the DB2 EE external loader to load data to a DB2 EE
database. You can use the DB2 EEE external loader to load data to a DB2 EEE database.
The DB2 external loaders can insert data, replace data, restart load operations, or
terminate load operations.
Environment SQL. For relational databases, you may need to execute some SQL
commands in the database environment when you connect to the database. For example,
you might want to set isolation levels on the source and target systems to avoid deadlocks.
You configure environment SQL in the database connection. You can use environment
SQL for source, target, lookup, and stored procedure connections.
Email. You can create email tasks in the Workflow Manager to send emails when you run a
workflow. You can configure a workflow to send an email anywhere in the workflow logic,
including after a session completes or after a session fails. You can also configure a
workflow to send an email when the workflow suspends on error.
Flat file targets. In the Workflow Manager, you can output data to a flat file from either a
flat file target definition or a relational target definition.
Heterogeneous targets. You can output data to different database types and target types in
the same session. When you run a session with heterogeneous targets, you can specify a
database connection for each relational target. You can also specify a file name for each flat
file or XML target.
xix
xx
Preface
Metadata extensions. You can extend the metadata stored in the repository by creating
metadata extensions for repository objects. The Workflow Manager allows you to create
metadata extensions for sessions, workflows, and worklets.
Oracle 8 direct path load support. You can load data directly to Oracle 8i in bulk mode
without using an external loader. You can load data directly to an Oracle client database
version 8.1.7.2 or higher.
Partitioning enhancements. To improve session performance, you can set partition points
at multiple transformations in a pipeline. You can also specify different partition types at
each partition point.
Server variables. You can use new server variables to define the workflow log directory and
workflow log count.
Teradata TPump external loader. You can use the Teradata TPump external loader to load
data to a Teradata database. You can use TPump in sessions that contain multiple
partitions.
Tips. When you start the Workflow Manager, it displays a tip of the day. These tips help
you use the Workflow Manager more efficiently. You can display or hide the tips by
choosing Help-Tip of the Day.
Workflow log. In addition to session logs, you can configure the Informatica Server to
create a workflow log to record details about workflow runs.
Workflow Monitor. You use a tool called the Workflow Monitor to monitor workflows,
worklets, and tasks. The Workflow Monitor displays information about workflow runs in
two views: Gantt Chart view or Task view. You can run, stop, abort, and resume workflows
from the Workflow Monitor.
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.
Metadata Reporter Guide. Provides information on how to install and use the web-based
Metadata Reporter to generate reports on the metadata in PowerCenter and PowerMart
repositories.
Repository Guide. Provides information needed to administer the repository using the
Repository Manager or the pmrep command line program. Includes details on
functionality available in the Repository Manager, such as creating and maintaining
repositories, folders, users, groups, and permissions and privileges.
Transformation Language Reference. Provides syntax descriptions and examples for each
transformation function provided with PowerCenter and PowerMart.
Transformation Guide. Provides information on how to create and configure each type of
transformation in the Designer.
Troubleshooting Guide. Lists error messages that you might encounter while using
PowerCenter or PowerMart. Each error message includes one or more possible causes and
actions that you can take to correct the condition.
Workflow Administration Guide. Provides information to help you create and run
workflows in the Workflow Manager, as well as monitor workflows in the Workflow
Monitor. Also contains information on administering the Informatica Server and
performance tuning.
Informatica Metadata Exchange SDK User Guide. Provides information about the
second generation of Metadata Exchange interfaces for PowerCenter and PowerMart
repositories.
xxi
xxii
Preface
PowerConnect for SAP R/3 User and Administrator Guide. Provides information to
install PowerConnect for SAP R/3, build mappings, and run workflows to extract data
from SAP R/3 and load data into SAP R/3.
Metadata Exchange for Data Models User Guide. Provides information on how to extract
metadata from leading data modeling tools and import it into PowerCenter/PowerMart
repositories through Informatica Metadata Exchange SDK.
Metadata Exchange for OLAP User Guide. Provides information on how to use export
multi-dimensional metadata from PowerCenter/PowerMart repositories into the Hyperion
Integration Server through Informatica Metadata Exchange SDK.
xxiii
Document Conventions
This guide uses the following formatting conventions:
xxiv
Preface
If you see
It means
italicized text
boldfaced text
Emphasized subjects.
Note:
Tip:
Warning:
monospaced text
Informatica Webzine
xxv
Informatica Corporation
2100 Seaport Blvd.
Redwood City, CA 94063
Phone: 866.563.6332 or 650.385.5800
Fax: 650.213.9489
Hours: 6 a.m. - 6 p.m. (PST/PDT)
email: support@informatica.com
xxvi
Preface
Chapter 1
Product Overview
This chapter covers the following topics:
Introduction, 2
Loading Data, 14
Getting Started, 17
Introduction
PowerCenter and PowerMart provide an environment that allows you to load data into a
centralized location, such as a datamart, data warehouse, or operational data store (ODS).
You can extract data from multiple sources, transform the data according to business logic you
build in the client application, and load the transformed data into file and relational targets.
Informatica provides the following integrated components:
Informatica Client. Use the Informatica Client to manage users, define sources and
targets, build mappings and mapplets with the transformation logic, and create workflows
to run the mapping logic. The Informatica Client has four client applications: Repository
Manager, Designer, Workflow Manager, and Workflow Monitor.
Informatica Server. The Informatica Server extracts the source data, performs the data
transformation, and loads the transformed data into the targets.
Source
Server
Source
data
Target
Transformed
data
Instructions
from
metadata
Repository
Sources
PowerCenter and PowerMart access the following sources:
Relational. Oracle, Sybase, Informix, IBM DB2, Microsoft SQL Server, and Teradata.
File. Fixed and delimited flat file, COBOL file, and XML.
Application. If you use PowerCenter, you can purchase additional PowerConnect products
to access business sources such as PeopleSoft, SAP R/3, Siebel, IBM MQSeries, and Tibco.
Mainframe. If you use PowerCenter, you can purchase PowerConnect for Mainframe for
faster access to IBM DB2 on MVS.
Note: The Designer imports relational sources, such as Microsoft Excel, Microsoft Access, and
Targets
PowerCenter and PowerMart can load data into the following targets:
Relational. Oracle, Sybase, Sybase IQ, Informix, IBM DB2, Microsoft SQL Server, and
Teradata.
Application. If you use PowerCenter, you can purchase additional PowerConnect products
to load data into SAP BW. You can also load data into IBM MQSeries message queues and
Tibco.
You can load data into targets using ODBC or native drivers, FTP, or external loaders.
For more information about targets, see Working with Targets in the Designer Guide.
Repository
The Informatica repository resides on a relational database. The repository database tables
contain the instructions required to extract, transform, and load data. Informatica client
applications access the repository database tables through the Repository Server.
You add metadata to the repository tables when you perform tasks in the Informatica Client
application such as creating users, analyzing sources, developing mappings or mapplets, or
creating workflows. The Informatica Server reads metadata created in the Client application
when you run a workflow. The Informatica Server also creates metadata such as start and
finish times of a session or session status.
When you use PowerCenter, you can develop global and local repository to share metadata:
Global repository. The global repository is the hub of the domain. Use the global
repository to store common objects that multiple developers can use through shortcuts.
These objects may include operational or Application source definitions, reusable
transformations, mapplets, and mappings.
Local repositories. A local repository is within a domain that is not the global repository.
Use local repositories for development. From a local repository, you can create shortcuts to
Introduction
objects in shared folders in the global repository. These objects typically include source
definitions, common dimensions and lookups, and enterprise standard transformations.
You can also create copies of objects in non-shared folders.
You can connect to a repository, back up, delete, or restore repositories using pmrep, a
command line program. For more information on pmrep, see Using pmrep in the Repository
Guide.
For more information about global repositories, see Understanding the Repository in the
Repository Guide.
You can view much of the metadata in the Repository Manager. You can also through the
Metadata Reporter. For more information about the Metadata Reporter, see the Metadata
Reporter Guide.
Repository Server
The Repository Server manages repository connection requests from client applications. For
each repository database registered with the Repository Server, it configures and manages a
Repository Agent process. The Repository Server also monitors the status of running
Repository Agents, and sends repository object notification messages to client applications.
The Repository Agent is a separate, multi-threaded process that accepts performs the action
needed to retrieve, insert, and update metadata in the repository database tables. The
Repository Agent ensures the consistency of metadata in the repository by employing object
locking.
For more information about the Repository Server, see Understanding the Repository in the
Repository Guide.
Informatica Client
The Informatica Client is comprised of three applications that you use to manage the
repository, design mappings, mapplets, and create sessions to load the data.
Repository Manager. Use the Repository Manager to create and administer the metadata
repository. You can create repository users and groups, assign privileges and permissions,
and manage folders and locks.
Designer. Use the Designer to create mappings that contain transformation instructions
for the Informatica Server. Before you can create mappings, you must add source and
target definitions to the repository. The Designer has five tools that you use to analyze
sources, design target schemas, and build source-to-target mappings:
Mapping Designer. Create mappings that the Informatica Server uses to extract,
transform, and load data.
Workflow Manager. Use the Workflow Manager to create, schedule, and run workflows. A
workflow is a set of instructions that describes how and when to run tasks related to
extracting, transforming, and loading data. The Informatica Server runs workflow tasks
(such as the Session task) according to the links connecting the tasks. You can run a task by
placing it in a workflow.
Workflow Monitor. Use the Workflow Monitor to monitor scheduled and running
workflows for each Informatica Server. You can choose a Gantt Chart or Task view. You
can also access details about those workflow runs.
Install the client tools on a Microsoft Windows machine. For more information about
installation requirements, see Installation and Configuration Overview in the Installation
and Configuration Guide.
Informatica Server
The Informatica Server reads mapping and session information from the repository. It extracts
data from the mapping sources and stores the data in memory while it applies the
transformation rules that you configure in the mapping. The Informatica Server loads the
transformed data into the mapping targets.
The Informatica Server can achieve high performance using symmetric multi-processing
systems. The Informatica Server can start and run multiple workflows concurrently. It can
also concurrently process partitions within a single session. When you create multiple
partitions within a session, the Informatica Server creates multiple database connections to a
single source and extracts a separate range of data for each connection, according to the
properties you configure.
The Informatica Server manages the scheduling and execution of workflows. It moves data
from sources to targets based on mapping and session information stored in the repository.
You can install the Informatica Server on a Windows or UNIX server machine. For more
information about installation requirements, see Installation and Configuration Overview
in the Installation and Configuration Guide.
You can communicate with the Informatica Server using the pmcmd program. For more
information, see Using pmcmd in the Workflow Administration Guide.
Connectivity
PowerCenter and PowerMart use the following types of connectivity:
Network protocol
Native drivers
ODBC
The Informatica Client uses ODBC and native drivers to connect to source and target
databases. It uses TCP/IP to connect to the Repository Server. The Repository Server uses
Introduction
native drivers to connect to the repository database. The Workflow Manager and the
Informatica Server use TCP/IP to communicate with each other.
The Informatica Server uses native drivers to connect to the databases to move data. You can
optionally use ODBC to connect the Informatica Server to the source and target databases. It
uses TCP/IP to connect to the Informatica Client.
Figure 1-2 shows the connectivity used within the PowerCenter/PowerMart architecture:
Figure 1-2. Connectivity Overview
Metadata Reporter
PowerCenter and PowerMart provide the Metadata Reporter, a web-based application that
allows you to run reports against repository metadata. It gives you insight into your repository
that enhances your ability to analyze and manage your repository efficiently.
The Metadata Reporter provides a number of reports, including reports on executed sessions,
lookup table dependencies, mappings, and source or target schemas.
You can install the Metadata Reporter on a server with any type of operating system running a
compatible web server. You can run the Metadata Reporter from a browser on any
workstation, even without the Informatica tools installed on the workstation. For more
information, see the Metadata Reporter Guide.
Manage the repository. You can perform repository management functions such as
copying, creating, starting, and shutting down repositories. You connect to the Repository
Server to perform these functions.
Implement repository security. You can create, edit, and delete repository users and user
groups. You can assign and revoke repository privileges and folder permissions.
Perform folder functions. You can create, edit, copy, and delete folders. All the work you
perform in the Designer is stored in folders. If you want to share metadata, you can
configure a folder to be shared.
View metadata. You can analyze sources, targets, mappings, and shortcut dependencies,
search by keyword, and view the properties of repository objects.
Customize the Repository Manager. You can add, edit, and remove repositories in the
Navigator, view or hide windows.
For more information about the repository and the Repository Manager, see the Repository
Guide.
Navigator. Displays all objects that you create in the Repository Manager, the Designer,
and the Workflow Manager. It is organized first by repository, then by folder and folder
version. Viewable objects include sources, targets, dimensions, cubes, mappings, mapplets,
transformations, sessions, and workflows. You can also view folder versions and business
components.
Main. Provides properties of the object selected in the Navigator window. The columns in
this window change depending on the object selected in the Navigator window.
Dependency. Shows dependencies on sources, targets, mappings, and shortcuts for objects
selected in either the Navigator or Main window.
Output. Provides the output of tasks executed within the Repository Manager, such as
creating a repository.
Navigator
Main
Dependency
Output
Status Bar
Folders
Sessions
Worklets
Workflows
Version
Nodes
Mappings
Repository Objects
You create repository objects using the Repository Manager, Designer, and Workflow
Manager client tools. You can view the following objects in the Navigator window of the
Repository Manager:
Source definitions. Definitions of database objects (tables, views, synonyms) or files that
provide source data.
Target definitions. Definitions of database objects or files that contain the target data.
Mappings. A set of source and target definitions along with transformations containing
business logic that you build into the transformation. These are the instructions that the
Informatica Server uses to transform and move data.
Sessions and workflows. Sessions and workflows store information about how and when
the Informatica Server moves data. A workflow is a set of instructions that describes how
and when to run tasks related to extracting, transforming, and loading data. A session is a
type of task that you can put in a workflow. Each session corresponds to a single mapping.
Import source definitions. Use the Source Analyzer to connect to the sources and import
the source definitions.
2.
Create or import target definitions. Use the Warehouse Designer to define relational,
flat file, or XML targets to receive data from sources. You can import target definitions
from a relational database or a flat file, or you can manually create a target definition.
3.
Create the target tables. If you add a target definition to the repository that does not
exist in a relational database, you need to create target tables in your target database. You
do this by generating and executing the necessary SQL code within the Warehouse
Designer.
4.
Design mappings. Once you have source and target definitions in the repository, you can
create mappings in the Mapping Designer. A mapping is a set of source and target
definitions linked by transformation objects that define the rules for data transformation.
A transformation is an object that performs a specific function in a mapping, such as
looking up data or performing aggregation.
5.
Create mapping objects. Optionally, you can create reusable objects for use in multiple
mappings. Use the Transformation Developer to create reusable transformations. Use the
Mapplet Designer to create mapplets. A mapplet is a set of transformations that may
contain sources and transformations.
6.
Debug mappings. Use the Mapping Designer to debug a valid mapping to gain
troubleshooting information about data and error conditions.
7.
Import and export repository objects. You can import and export repository objects,
such as sources, targets, transformations, mapplets, and mappings to archive or share
metadata.
Figure 1-5 shows a sample mapping with source and target definitions and transformations:
Figure 1-5. Sample Mapping
Source Definition
Transformations
Target Definition
For more information about the Designer, see the Designer Guide.
10
Designer Windows
You can display the following windows in the Designer:
Navigator. Connect to repositories, and open folders within the Navigator. You can also
copy objects and create shortcuts within the Navigator.
Workspace. Open different tools in this window to create and edit repository objects such
as sources, targets, mapplets, transformations, and mappings.
Output. View details about tasks you perform, such as saving your work or validating a
mapping.
Instance data. View transformation data while you run the Debugger to debug a mapping.
Target data. View target data while you run the Debugger to debug a mapping.
Navigator
Workspace
Output
Status Bar
11
Overview Window
12
13
Loading Data
In the Workflow Manager, you define a set of instructions to execute tasks such as sessions,
emails and shell commands. This set of instructions is called a workflow.
After you create a new workflow in the Workflow Designer, the next step is to add tasks to the
workflow. The Workflow Manager includes tasks such as the Session task, the Command task,
and the Email task so you can design your workflow. The Session task is based on a mapping
you build in the Designer.
You then connect tasks with links to specify the order of execution for the tasks you created.
Use conditional links and workflow variables to create branches in the workflow.
When the workflow start time arrives, the Informatica Server retrieves the metadata from the
repository to execute the tasks in the workflow.
You can monitor the workflow status in the Workflow Monitor.
Workflow Manager
The Workflow Manager consists of three tools to help you develop a workflow:
Task Developer. Create tasks you want to accomplish in the workflow in the Task
Developer.
Workflow Designer. Create a workflow by connecting tasks with links in the Workflow
Designer. You can also create tasks in the Workflow Designer as you develop the workflow.
Worklet Designer. Create a worklet in the Worklet Designer. A worklet is an object that
groups a set of tasks. A worklet is similar to a workflow, but without scheduling
information. You can execute a batch of worklets inside a workflow.
Before you create a workflow, you must configure the following connection information:
Informatica Server connection. Register the Informatica Server with the repository before
you can start it or create a session to run against it.
Other connections. If you want to use external loaders or FTP, you configure these
connections in the Workflow Manager.
For more information about configuring the Workflow Manager, see Configuring the
Workflow Manager in the Workflow Administration Guide.
14
Navigator. Allows you to connect to and work in multiple repositories and folders.
Workspace. Allows you to create, edit, and view tasks, workflows, and worklets.
Output. Displays messages from the Informatica Server and the Repository Server. The
Output window also displays messages when you save or validate task and workflows.
Overview. An optional window that makes it easier to view workbooks containing large
workflows. Outlines the visible area in the workspace and highlights selected objects in
color. Choose View-Overview Window to display this window.
The Workflow Manager also displays a status bar that shows the status of the operation you
perform.
Figure 1-9 shows the Workflow Manager windows:
Figure 1-9. Workflow Manager Windows
Navigator
Workspace
Overview
Output
Status Bar
Workflow Monitor
After you create a workflow, you run the workflow in the Workflow Manager and monitor it
in the Workflow Monitor. The Workflow Monitor is a tool that displays details about
workflow runs in two views: Gantt chart view and Task view. You can monitor workflows in
online and offline modes.
The Workflow Monitor consists of the following windows:
Loading Data
15
Gantt chart view. Displays details about workflow runs in chronological (Gantt chart)
format.
Time
Window
Navigator
window
Gantt
Chart
View
Task View
16
Output Window
Getting Started
Before you can begin using PowerCenter or PowerMart, you must create the environment and
perform the following administration tasks to allow access to the repository and the
Informatica Server:
1.
Configure the sources. If you extract from relational sources, ask the database
administrator to create user profiles with read access. This allows you to import source
definitions into the repository and access the sources at runtime.
If you extract from file sources, the files must be accessible to the Informatica Server and
Client machines.
2.
Configure the targets. Ask the database administrator to create user profiles with read
and write access. This allows you to import target definitions into the repository and
write to the targets at runtime.
If the target database does not exist, create it using the database administration tools
included with your RDBMS. After you create the target database, you can use the
Designer to design and create target tables.
For flat file targets, you need a target directory large enough to process the resulting files.
3.
Choose globalization settings and data movement modes. The data movement mode
you use depends on whether you want the Informatica Server to process single-byte data
or multibyte character data. You select code pages for the repository, Informatica Client
and Informatica Server.
4.
Create repository database. Create a database for the repository. Users accessing the
repository database need full rights in that database. If you upgrade the repository to a
new version, you need database rights to drop or modify these tables.
5.
Install the Informatica Client. Install the client software on a machine that accesses the
sources, targets, and repository databases, as well as the Informatica Server.
6.
Install and configure the Repository Server. Install and configure the Repository Server
on a machine that accesses the repository database, the Informatica Client, and the
Informatica Server.
7.
Install and configure the Informatica Server. Install the Informatica Server on a
Windows or UNIX system that accesses the sources, targets, and the repository database.
8.
9.
Create the repository. After you configure connectivity between source, target, and
repository databases, you can create the metadata repository. Connect to the Repository
Server from within the Repository manager to create the metadata repository. The
Repository Server connects to the repository database and runs the SQL needed to create
the repository tables. All the objects you create with PowerCenter or PowerMart are
stored as metadata in the repository.
Getting Started
17
10. Create repository users and groups. Create groups and user profiles, then assign
privileges and permissions that determine tasks that users can perform.
11. Register the Informatica Server. Before you can start the Informatica Server you must
register the Informatica Server so the Workflow Manager can direct the Informatica
Server to the repository.
18
Chapter 2
Installation and
Configuration Overview
This chapter includes the following topics:
19
Product Overview on page 1. This chapter provides an overview of the product and
product tools.
This chapter. Before you install the product, review the installation steps and connectivity
requirements.
Repository Server
Informatica
Repository Database
Informatica Server
Operating
system
Windows 98,
Windows 2000,
Windows XP, or
Windows NT 4.0
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
(Solaris, HP-UX, AIX)
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
(Solaris, HP-UX, AIX)
Windows 2000,
Windows NT 4.0,
Windows XP, or UNIX
(Solaris, HP-UX, AIX)
Disk space
70 MB
40 MB
100 MB of database
space*
40 MB
RAM
256 MB
32 MB
plus
16 MB per managed
repository
128 MB
256 MB
Database
connectivity
ODBC drivers
Native drivers
Native drivers
Native drivers or
ODBC
* Although you can create a repository with a minimum of 100 MB of database space, Informatica recommends allocating up to 150 MB
for repositories.
Informatica recommends a screen resolution of 1024 x 768 or higher for all machines running
the Informatica Client.
20
For detailed information on configuring connectivity for the Informatica Client tools and
Informatica Server, see the appropriate installation chapters in this guide.
ODBC drivers
Informatica Client tools pass all source and target database calls to the ODBC driver, which
interprets the information and sends it to the native database client connectivity software.
From there the information passes to the database, which processes the command and sends
the desired information back to the Informatica Client tool.
For example, when you import a source definition in the Designer, the Designer issues a call
to the ODBC driver. The ODBC driver translates the call and passes it to the native database
connectivity software, which in turn passes it to the database. The database processes the
request and sends the information back to the Designer (passing through the native software
layer and ODBC software), which displays the source definition.
21
Informatica Client tools communicate with the repository through the Repository Server. The
Informatica Client tools connect to the Repository Server over TCP/IP.
For each database, make note of the native connect string that you define through the
database connectivity software. Reference these connect strings in the Informatica Server
configuration utility, Repository Manager, and Workflow Manager.
The Workflow Manager communicates directly with the Informatica Server each time you
schedule or edit a session, display session details, and request session logs. The Workflow
Manager communicates with the Informatica Server through TCP/IP. You create the
connection by defining the port number in the Workflow Manager and in the Informatica
Server configuration.
Table 2-2 summarizes the software you need to connect the Informatica Client to the
repository, source, target databases, and the Informatica Server:
Table 2-2. Informatica Client Connectivity Requirements
To connect the Informatica Client to the...
You need...
Repository Server
TCP/IP
Source databases
Target databases
Informatica Server
TCP/IP
22
Database
Example
IBM DB2
dbname
mydatabase
Informix
dbname@servername
mydatabase@informix
servername@dbname
sqlserver@mydatabase
Example
Oracle
oracle.world
Sybase
servername@dbname
sambrown@mydatabase
You need...
Repository Database
Informatica Client
TCP/IP
Informatica Server
TCP/IP
You need...
Repository Server
TCP/IP
Source databases
Target databases
Informatica Client
TCP/IP
Note: Both the Windows and UNIX versions of the Informatica Server can also use ODBC drivers to connect to
databases. However, Informatica recommends using native drivers when possible to improve performance.
For Windows, the Informatica Server includes ODBC libraries that you can use to connect to
other ODBC source databases.
23
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.
24
These steps refer to additional chapters in this guide where you can obtain details for each
installation task.
Metadata Reporter installation is tightly integrated with the installation of a suitable web
server. See the Metadata Reporter Guide for details.
Follow these steps to install PowerCenter or PowerMart:
1.
2.
Configure the Informatica Client tools to connect to each database you need to access.
For more information, see Installing and Configuring the Informatica Client on
page 63.
3.
4.
5.
6.
Create a repository.
Before you can start the Informatica Server, you must create a repository. The
Informatica Server needs a connection to the repository. For more information, see
Creating a Repository on page 115.
25
7.
Configure the machine on which you plan to install the Informatica Server to connect to
each source and target database, the Repository Server, and the Informatica Client tools.
See the appropriate installation chapter for your platform. The chapters are Installing
and Configuring the Informatica UNIX Server on page 157 and Installing and
Configuring the Informatica Windows Server on page 125.
8.
9.
Use the Workflow Manager to register the Informatica Server with the repository.
For more information, see Registering the Informatica Server on page 183.
Use your existing version of the Repository Manager to back up each repository you want
to upgrade.
2.
Create a new database for each repository you want to upgrade to PowerCenter 6.0 or
PowerMart 6.0.
See your database documentation for details.
Note: The PowerCenter 6.0 and PowerMart 6.0 repository is approximately 30 percent
larger than a PowerCenter 5.1 and PowerMart 5.1 repository and approximately 60
percent larger than a PowerCenter 4.7 and PowerMart 1.7 repository. Before you upgrade
the repository, check the repository database size and available disk space.
3.
Use your existing version of the Repository Manager to make a copy of each existing
repository.
Important: We recommend that you make a copy of all existing repositories in your
existing version of the Repository Manager before upgrading to PowerCenter 6.0 or
PowerMart 6.0. Upgrade the copy of your existing repository to PowerCenter 6.0/
PowerMart 6.0 to evaluate it without altering your existing repository. For more
information, see Upgrading a Repository on page 191.
4.
26
For more information, see Installing and Configuring the Informatica Client on
page 63.
5.
Configure the Informatica Client tools to connect to each source or target database you
need to access.
For more information, see Installing and Configuring the Informatica Client on
page 63.
6.
7.
8.
9.
In the Repository Manager, create a repository configuration for each repository database
managed by the Repository Server.
For more information, see Managing the Repository in the Repository Guide.
10. Upgrade each repository. If you are upgrading multiple repositories in a domain, upgrade
and start the global repository first.
For more information, see Upgrading a Repository on page 191.
11. Configure the machine on which you plan to install the Informatica Server to connect to
each database, the Repository Server, and the Informatica Client tools.
See the appropriate installation chapter for your platform. The chapters are Installing
and Configuring the Informatica UNIX Server on page 157 and Installing and
Configuring the Informatica Windows Server on page 125.
12. Install and configure the Informatica Server.
See the appropriate installation chapter for your platform. The chapters are Installing
and Configuring the Informatica UNIX Server on page 157 and Installing and
Configuring the Informatica Windows Server on page 125.
13. Use the Workflow Manager to register the Informatica Server with the repository.
For details, see Registering the Informatica Server on page 183.
14. Start the Informatica Server.
27
28
Chapter 3
Globalization Overview
This chapter includes the following topics:
Overview, 30
Locales, 32
29
Overview
The Informatica Server can process single-byte data or multibyte data. PowerCenter and
PowerMart support multibyte character data movement, which means you can write multiple
language source data to targets. The Informatica Client user interface allows you to enter
multibyte character data in mappings.
When you install PowerCenter or PowerMart, you must decide if you want the Informatica
Server to process single-byte data or multibyte data. To help you decide, this chapter describes
how the system locale affects data movement and code page settings, summarizes the
differences between the Informatica Server data movement modes and describes what happens
when you change data movement modes. It also includes background information about code
pages and details on code page validation and code page compatibility. You can easily change
the Informatica Server data movement mode at a later time.
When you install PowerCenter or PowerMart, use the operating system locale, which specifies
the language, code pages, territory, and collation order. Code pages distinguish between 7-bit
ASCII, ISO 8859-1 (8-bit ASCII), and multibyte characters in the Informatica Client and
Server, repository, source, and target databases.
The Informatica Server can transform character data in two modes: ASCII and Unicode. The
default data movement mode is ASCII, which passes US-ASCII character data. To pass 8-bit
or multibyte character data from sources to targets, use the Unicode data movement mode.
When you run the Informatica Server in Unicode mode, it uses two bytes for each character
to move data and performs additional checks at the session level to ensure data integrity.
Code pages contain the encoding to specify characters in a set of one or more languages. You
select a code page based on the type of character data in the mappings. Character data can
vary from one to eight bytes in size. Compatibility between code pages is essential for accurate
data movement.
To ensure data passes accurately through your data warehouse environment, the following
components must work together:
PowerCenter and PowerMart also allow you to configure the Informatica Server for relaxed
data code page validation. Relaxed validation lifts restrictions on source and target data code
pages.
30
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 (8bit ASCII) data using the Unicode data movement mode.
Overview
31
Locales
Every machine has a locale, a set of preferences related to the user environment. PowerCenter
and PowerMart use locale settings on each machine to run in the local environment. You can
set three locale settings in the Windows operating system Control Panel Regional Settings and
System Properties dialog boxes:
System locale. Determines the language, code pages, and associated bitmap font files that
are used as defaults for the system.
User locale. Determines the default formats to display date, time, currency, and number
formats.
Input locale. Describes the input method, such as using the keyboard, of the system
language.
Locales allow you flexibility in setting up the Informatica Client, Informatica Server, and
Repository Server on Windows machines.
System Locale
The system locale is also referred to as the system default locale. It determines which ANSI
and OEM code pages, as well as bitmap font files, are used as defaults for the system. The
system locale is already set on your system and you do not need to change settings to run
PowerCenter and PowerMart.
The system locale also contains the language setting that displays in the user interface,
including in dialog boxes and error messages. A message catalog file defines the language in
which messages display.
User Locale
The user locale is a setting that displays date, time, currency, and number formats for each
user. You can specify different user locales on a single machine. Create a user locale if you are
working with data on a machine that is in a different language than the operating system. For
example, you might be an English user working in Japan on a Japanese operating system. You
can set English as the user locale to use English standards in your work in Japan.
When you create a new user account, the machine uses a default user locale. You can change
this default setting once the account is created.
Input Locale
An input locale specifies the keyboard layout of a particular language. You can set an input
locale in the Regional Settings on a Windows machine to type characters of a specific
language. For example, if you are working on a Japanese operating system and need to type
text in English, you can set an English input locale for the keyboard setting. The keyboard
allows you to type English text on the Japanese operating system.
32
Unicode. The universal character-encoding standard that supports all major languages.
When the Informatica Server runs in Unicode data movement mode, it allots two bytes for
each character. The Informatica Server uses the additional byte for non-ASCII characters,
such as Japanese characters. Run the Informatica Server in Unicode mode when source
data contains multibyte or ISO 8859-1 (8-bit ASCII) data.
ASCII. (American Standard Code for Information Interchange) 7-bit ASCII contains a set
of 128 characters is the one common denominator contained in all other character sets.
When the Informatica Server runs in the ASCII data movement mode, it holds all data in
a single byte.
When you select a data movement mode, code pages used for sessions must have appropriate
relationships. For details on code page compatibility, see Code Page Compatibility on
page 38.
In ASCII mode, the Informatica Server processes single byte characters and does not perform
code page conversions. In Unicode mode, the Informatica Server recognizes multibyte
character data and allocates 2 bytes to every character. The Informatica Server performs code
page conversions from sources to targets. When you set the Informatica Server to Unicode
data movement mode, it uses the Unicode character set to process characters in a specified
code page, such as ISO 8859-1 (8-bit ASCII) or Shift-JIS.
When you run the Informatica Server in ASCII mode, it does not enforce session code page
relationships. When you run the Informatica Server in Unicode mode, it enforces session code
page relationships. For details on how the Informatica Server enforces session code page
relationships in Unicode data movement mode, see Informatica Code Page Validation on
page 44.
Other character modes are defined as follows:
MBCS. (Multibyte Character Set) A mixed-width character set that contains characters of
more than one byte.
UTF-8. Characters range from one to three bytes in size. If you enable code page
validation, you can use UTF-8 for target database code pages only.
ISO 8859-1 (8-bit ASCII). Most European languages use this mode for accented Roman
characters.
33
Time of Creation or
Use
Each session.
Workflow Log
Each workflow.
Each session.
Incremental
Aggregation Files
(*.idx, *.dat)
Sessions with
Incremental
Aggregation enabled.
34
Unnamed
Persistent Lookup
Files (*.idx, *.dat)
Sessions with a
Lookup transformation
configured for a
named persistent
lookup cache.
Named Persistent
Lookup Files (*.idx,
*.dat)
Sessions with a
Lookup transformation
configured for a
persistent lookup
cache.
If you are not sure how you want to run the Informatica Server, install and configure
PowerCenter and PowerMart for Unicode data movement mode. This allows you the
flexibility to change the Informatica Server data movement mode from Unicode to ASCII,
and from ASCII to Unicode.
35
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.
36
an HP-UX machine. You use the following command in the C-shell to view your
environment:
locale
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.
ANSI Code Page. Windows NT/2000/XP uses the ANSI code page for Win32
applications that interact with the operating system through the Windows GUI.
Applications such as Microsoft SQL Server are considered ANSI servers if they use code
pages MS1252-MS1259. The Informatica Client and Informatica Server use the ANSI
code page of the machine they are installed on.
OEM Code Page. Windows NT/2000/XP uses the OEM code page for Win32
applications that interact with the operating system through the Windows console.
Applications such as Microsoft SQL Server are considered OEM servers if they use any
code page other than MS1252-MS1259.
If you purchase English Windows 98 in the United States, your operating system uses the MS
Latin1 (MS1252) ANSI code page and the MS437 US English code page by default.
37
However, if you add other display or input languages and use those languages, the operating
system might use a different code page.
Windows NT/2000/XP operating systems are based on Unicode, but use only one local code
page at a time as the ANSI code page. If you purchase Windows in the United States and use
English as an input and display language, your operating system ANSI and OEM code pages
use MS Latin1 (MS1252) by default. However, if you install additional display or input
languages from the Windows NT/2000/XP installation CD and use those languages, the
operating system might use a different code page.
For details on the default code page for your Windows system, contact Microsoft.
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.
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.
38
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 USASCII. It contains all US-ASCII character encoding in addition to its own character set
encoding. You can select US-ASCII for the source code page and Latin1 for the target code
page. However, if you select Latin1 as the source code page and US-ASCII as the target code
page, you might lose character data.
Figure 3-1 illustrates the necessary relationship between source and target database code pages
when you run the Informatica Server in Unicode data movement mode:
Figure 3-1. Required Code Page Relationships for Unicode Data Movement Mode
Target 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, Informatica Server,
Repository Server, and repository database machines. In Unicode mode, the Informatica
Server enforces code page compatibility between the Informatica Client, Server, and
repository. In addition, when you run the Informatica Server in Unicode mode, code pages
associated with sessions must have the appropriate relationships:
For each source in the session, the source code page must be a subset of the Informatica
Server code page.
The target code page must be a superset of the Informatica Server code page.
If the session contains a Lookup transformation, the lookup database must use a code page
that is compatible with the Informatica Server.
If the session contains a Stored Procedure transformation, the stored procedure database
must use a code page that is compatible with the Informatica Server.
39
If you have existing source and target database connections registered in the repository and
you want to run the Informatica Server in Unicode mode, you might need to reconfigure the
Informatica Server machine or choose a different machine for the Informatica Server to
ensure the appropriate session code page relationships.
For a list of compatible code pages, see Informatica Code Page Relationships on page 214.
Set code pages for the following components:
Informatica Client. The code page of the Informatica Client operating system. Clients
connected to different repositories might have different code pages.
Informatica Server. The code page of the Informatica Server operating system. When you
register the Informatica Server in the Workflow Manager, select the same code page as the
operating system code page.
Informatica Repository Server. The code page of the Repository Server operating system.
The Repository Server uses this code page automatically when you configure the Windows
or UNIX locale.
Informatica repository. The code page of data in the repository. When you create or
upgrade a repository, you select a code page.
Source and target files. The code page of the operating system on which source or target
files reside. Different operating systems can have different code pages.
XML source and target files. XML files contain an encoding declaration that indicates the
code page used in the file. XML source definitions use the repository code page. XML
target definitions use the code page declared in the XML file.
Source and target databases. The code page of the database for relational sources or
targets. Different databases can have different code pages.
Most database servers use two code pages, a client code page to receive data from client
applications and a server code page to store the data. When the database server is running, it
converts data between the two code pages, if they are different. In this type of database
configuration, the Informatica Server interacts with the database client code page only. Thus,
code pages used by the Informatica Server, such as the repository, source, or target code pages,
must be identical to the database client code page. The database client code page is usually
identical to the operating system code page on which the Informatica Server is running.
For details on specific database client and server code pages, consult your database
documentation.
40
Each code page has associated sort orders. When you configure a session, the Workflow
Manager allows you to select one of the sort orders associated with the Informatica Server
code page. When you run the Informatica Server in Unicode mode, it uses the selected session
sort order to sort character data. When you run the Informatica Server in ASCII mode, it
sorts all character data using a binary sort order.
If you run the Informatica Server in Unicode mode, you must enter the session code page
information in the session configuration. If a session contains a Lookup or Stored Procedure
transformation, the databases on which the lookup table or stored procedure reside must be
compatible with the Informatica Server code page. If a session contains an External Procedure
or Advanced External Procedure transformation, the external or advanced external procedure
must pass data in the Informatica Server code page.
If you run the Informatica Server in the United States on Windows, Informatica recommends
using MS Windows Latin1 (ANSI) as the Informatica Server code page.
If you run the Informatica Server in the United States on UNIX, Informatica recommends
using ISO 8859-1 as the Informatica Server code page.
If you use pmcmd to communicate with the Informatica Server, the code page of the operating
system hosting pmcmd must be identical to the Informatica Server code page.
The Informatica Server generates session log files, reject files, caches and cache files, and
performance detail files based on the Informatica Server code page.
41
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.
Note: Select IBM EBCDIC as your source database connection code page only if you access
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
42
Table 3-2 summarizes code page compatibility between sources, targets, the repository, the
Repository Server, the Informatica Client and the Informatica Server:
Table 3-2. Code Page Compatibility
Component Code Page
Subset of target.
Subset of Informatica Server.
Superset of source.
Superset of Informatica Server.
External loader data and control files are created using the target flat file code
page.
Informatica Server
Superset of source.
Subset of target.
Identical to Informatica Server operating system and machine hosting pmcmd.
Compatible with repository and Informatica Client.
Compatible with database connection code page used by Lookup and Stored
Procedure transformations.
Repository Server
43
Global Repository
Local Repository
Standalone Repository
Informatica Client
Repository Server restricts the use of EBCDIC-based code pages for repositories. Since
you cannot install the Informatica Client, Informatica Server, Repository Server, or
repository database on mainframe systems, the Repository Server does not allow you to
select EBCDIC-based code pages, like IBM EBCDIC, as the repository code page.
Informatica Client restricts use of EBCDIC-based code pages for the Informatica Server.
The Workflow Manager does not allow you to select EBCDIC-based code pages for the
Informatica Server code page.
Repository Server restricts repository code page choices to those compatible with the
Repository Server. The Repository Server code page must be compatible with the
repository code page to prevent data loss or inconsistencies. After you install the
Repository Server, it uses the operating system code page as the Repository Server code
page. When you create a new repository or upgrade an existing repository, you select a
code page for the repository. The Repository Server restricts code page choices to those
compatible with the Repository Server code page.
Informatica Client connects to the repository only when its code page is compatible
with the repository code page. If the Informatica Client code page is not compatible with
the repository code page, the Informatica Client fails to connect to the repository code
page with the following error:
REP_12782 The repository <repository name>s code page <code page name>
and <Informatica Client>s code page <code page name> are incompatible.
44
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 Event Viewer or the UNIX server log or server error log:
Error: Server can only obtain a read-only connection with the repository.
Please make sure the code page where the server is running is two way
compatible with the repository code page.
The Informatica Server starts only when the Informatica Server code page is registered
correctly in the Workflow Manager. To ensure accurate session validation, the Informatica
Server code page must be registered correctly in the Workflow Manager. After you install
or upgrade the Informatica Client and repository, the Workflow Manager sets the code
page for each registered server to the repository code page. The Informatica Server starts
only when the code page registered in the Workflow Manager matches the Informatica
Server code page.
If the code page does not match the Informatica Server code page, the Informatica Server
writes the following message in the Windows Event Viewer or UNIX server or server error
log:
LM_36011 Error: codepage mismatch. Server is running in codepage
<Informatica Server code page> whereas the server is configured in the
Workflow Manager to run in codepage <user-configured code page>.
Informatica Client restricts Informatica Server code page choices to those compatible
with the Informatica Client. The Informatica Server code page must be compatible with
the Informatica Client code page to prevent data loss or inconsistencies. When you register
an Informatica Server, the Workflow Manager restricts code page choices to those
compatible with the Informatica Client code page.
When in Unicode data movement mode, the Informatica Server starts workflows with
the appropriate source and target code page relationships for each session. When the
Informatica Server runs in Unicode mode, the code page for every session source must be a
subset of the Informatica Server code page, and the code page for each target must be a
superset of the Informatica Server code page. This prevents data loss during a workflow.
For details on code page relationships, subsets, and supersets, see Supported Code Pages
and Related Code Pages on page 216.
If the source and target code pages do not have the appropriate relationships to the
Informatica Server code page, the Informatica Server fails the session and writes the
following message to the session log:
TM_6227 Error: Code page incompatible in session <session name>.
<Additional details>.
45
Workflow Manager validates source and target code page relationships for each session.
Source and target code page relationships are critical when the Informatica Server runs in
Unicode mode. As a result, the Workflow Manager always checks code page relationships
when you save a session, regardless of the Informatica Server data movement mode. The
Workflow Manager alerts you to inappropriate code page relationships in case you change
the Informatica Server to Unicode mode or run the workflow containing the session on a
different Informatica Server.
If you configure a session with invalid source or target code page relationships, the
Workflow Manager issues a warning similar to the following when you save the session:
If you want to run the workflow containing the session on an Informatica Server in ASCII
mode, you can save the session as configured. If you want to run the workflow on an
Informatica Server in Unicode mode, perform the most appropriate of the following
actions:
Change the relational source or target database connections to those with appropriate
code pages, or change the file source or target code page and location. You can set the
code page for file sources and targets in the file properties dialog boxes in the session
properties. The Workflow Manager restricts source file code page choices to those that
are subsets of the Informatica Server code page. The Workflow Manager also restricts
target file code page choices to those that are subsets of the Informatica Server code
page. The Workflow Manager also restricts target file code page choices to those that are
supersets of the Informatica Server code page.
Correct the configured code pages in the database connections. Edit the code page for
relational sources and targets in the Workflow Manager database connection dialog box.
Because you can use the same database connection as a source or target, the Workflow
Manager restricts code page choices to those that are either subsets or supersets of the
Informatica Server code page.
Workflow Manager validates code pages for lookup and/or stored procedure databases in
a session. When the Informatica Server runs in Unicode mode, the database hosting a
lookup table or stored procedure for a session must use a code page that is compatible with
the Informatica Server code page. As with source and target code pages, the Workflow
Manager always checks these code page relationships.
When you configure the session with invalid lookup or stored procedure code page
relationships, the Workflow Manager issues the following warning:
The database <lookup or stored procedure database name> and server <server
name> do not have compatible code pages. Do you want to save the session?
If you want to run the workflow containing this session on an Informatica Server in ASCII
mode, you can save the session as configured. If you want to run the workflow on an
46
Informatica Server in Unicode mode, perform the most appropriate of the following
actions:
Change the lookup or stored procedure database connections to those with appropriate
code pages. You can configure the database used for the Lookup and Stored Procedure
transformation in the transformation property sheet or enter a session override on the
Transformations tab of the session properties.
Correct the code page for the database connection. You can configure the database code
page in the Workflow Manager.
47
Lifted restrictions for source and target data code page. You can use any code page
supported by PowerCenter and PowerMart for your source and target data.
Lifted restrictions for session sort order. You can use any sort order supported by
PowerCenter and PowerMart when you configure a session.
Informatica Server writes multibyte characters to the session log. You can configure the
Informatica Server to write to the session log using the UTF-8 character set. This ensures
that multibyte characters display properly when you view the session log.
Configure the Informatica Server to write to the session log using the UTF-8 character set.
You can configure the Informatica Server on Windows for data code page relaxation in the
Informatica Server setup program. On the Configuration tab of the Informatica Server setup
program, select UNICODE as the data movement mode, clear the Validate Data Code Pages
check box, and select the Session Log in UTF-8.
To configure the Informatica Server on UNIX for data code page relaxation, run pmconfig
and set DataMovementMode to UNICODE, ValidateDataCodePages to No, and
SessionLogInUTF8 to Yes.
48
The Informatica Server code page must be two-way compatible with the repository and
Repository Server code pages.
The Informatica Server code page must be the same code page as operating system the
Informatica Server is installed on.
When you run a workflow with relaxed data code page validation, the Informatica Server
writes the following message to the session log:
TM_6185 WARNING! Data codepage validation is disabled in this session.
When you relax data code page validation, the Informatica Server writes descriptions of the
code pages selected for source and target files and database connections to the session log. The
Informatica Server also writes descriptions of code pages for lookup and stored procedure
databases to the session log. The following example shows these descriptions as they appear in
a session log:
TM_6186 Repository codepage: [MS Windows Latin 1 (ANSI), superset of Latin
1]
TM_6188 Target file [$PMTargetFileDir\passthru.out] codepage: [MS Windows
Traditional Chinese, superset of Big 5]
TM_6190 Target database connection [Japanese Oracle] codepage: [MS
Windows Japanese, superset of Shift-JIS]
TM_6189 Source database connection [Japanese Oracle] code page: [MS
Windows Japanese, superset of Shift-JIS]
TM_6191 Lookup [LKP_sjis_lookup] uses database connection [Japanese
Oracle] in codepage [MS Windows Japanese, superset of Shift-JIS]
TM_6192 Stored procedure [J_SP_INCREMENT] uses database connection
[Japanese Oracle] in codepage [MS Windows Japanese, superset of Shift-JIS]
The Informatica Server operates internally using UCS-2. The Informatica Server converts
source data encoded in other code pages to the UCS-2 character set before processing, and
converts the processed data from UCS-2 to the target warehouse code page before loading.
When you run a workflow that contains a session, Informatica Server converts source, target,
and lookup queries from the repository code page to the source, target, or lookup database
code page. The Informatica Server also converts the name and call text of stored procedures
from the repository code page to the stored procedure database code page. At runtime, the
Informatica Server performs checks on the following code page conversions:
49
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, presource 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.
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.
51
Session sort order [sort order name] is incompatible with the Informatica
Server's codepage [code page name].
Cause:
The specified sort order is incompatible with the Informatica Server code
page.
Action:
If you want to validate data code pages, select a sort order compatible with the
Informatica Server code page. If you want to relax data code page validation,
configure the Informatica Server to relax data code page validation in Unicode
data movement mode. For details on configuring the Informatica Server, see
Configuring the Informatica Server on page 48.
52
Cause:
Your Informatica Server is not configured to write to the session log using the
UTF-8 character set.
Action:
Enable the Session Log in UTF-8 option on the Configuration tab of the
Informatica Server setup program.
The repository tables residing on a Microsoft Windows SQL Server database on Windows
NT
A lookup database
All character data in the data warehouse environment is U.S. English, 7-bit ASCII data.
Figure 3-3 illustrates the 7-bit ASCII data environment:
Figure 3-3. 7-bit ASCII Mode Case Study Environment
Lookup Database
(7-bit ASCII Data)
Sources
(7-bit ASCII Data)
External Procedures
(7-bit ASCII Data)
Informatica Server
(Windows NT)
Targets
(7-bit ASCII Data)
Repository Server
Informatica Client Tools
(Windows 2000)
Repository Agent
(Windows NT)
Repository Database
(Microsoft SQL Server on
Windows NT)
53
Verify Informatica Client, Repository Server and Informatica Server code page
compatibility.
2.
3.
4.
5.
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 ToolsOptions, then open the Connection tab to enable or disable this setting.
55
Lookup Database
External Procedures
Informatica Server
-Configure ASCII Data Movement
Mode
-Set code page in Workflow
Manager to MS Windows Latin 1
Sources (7-bit
ASCII Data)
Targets (7-bit
ASCII Data)
Repository Server
Informatica Clients
(Windows 2000: MS Windows
Latin 1 default)
Repository Database
(Microsoft SQL Server on
Windows NT)
56
The Repository Server and Repository Agent process on a UNIX Solaris machine.
57
External Procedures
(English Data)
Sources
(English Data)
Informatica Server
(UNIX)
Targets
(English and
German Data)
Sources
(German and
English Data)
Repository Server
Informatica Client Tools
(Windows NT)
Repository Agent
(UNIX))
Repository Database
(Oracle on UNIX)
58
1.
Verify Informatica Client, Repository Server and Informatica Server code page
compatibility.
2.
3.
4.
5.
6.
7.
By default, Oracle configures NLS_LANG for U.S. English, U.S. date formats, and the U.S.
English code page:
NLS_LANG = AMERICAN_AMERICA.US7ASCII
Change the default configuration to write ISO 8859-1 data to the repository using the Oracle
WE8ISO8859P1 code page.
See your repository database documentation for details on verifying and changing the
repository database code page. For details on repository database code pages, see Repository
Code Page on page 42.
59
60
Sources
(English Data)
Sources
(German and
English Data)
External Procedures
(English Data)
Informatica Server
(UNIX: ASCII default)
Set UNIX code page to ISO 8859-1.
Change Data Movement Mode
to Unicode.
Set code page in Workflow Manager
to ISO 8859-1.
Targets
(English and
German Data)
Repository Server
Informatica Client Tools
(Windows NT: MS
Windows Latin 1 default)
Repository Database
(Oracle on UNIX)
61
62
Chapter 4
Troubleshooting, 78
63
2.
3.
If you are upgrading the Informatica Client tools, you need to complete the following steps:
1.
Replace existing Merant 32-bit closed ODBC drivers with Merant 3.7 32-bit closed
ODBC drivers.
2.
3.
Before you install the Informatica Client tools, make sure you have 30 MB of disk space
available on the Windows boot drive. The Informatica Platform Setup requires this space for
temporary files.
Before you begin, locate the PowerCenter/PowerMart product license key. Use the same
product license key to install the Informatica Server, Repository Server, Informatica Client
tools, and Metadata Reporter.
Note: Please read the release notes for last minute changes to the Informatica Client
64
ODBC driver
IBM DB2
Informix
Microsoft Access97
Microsoft Excel
Oracle
Sybase
Teradata
Note: The Merant 3.7 32-bit ODBC closed drivers are designed for use with PowerCenter and
PowerMart only. If you use them with other software, they generate warning messages about
violating licensing agreements.
For a complete description of supported databases and ODBC drivers, see Using ODBC on
page 193.
ODBC Administrator
Uninstall program
If the installation program finds an earlier version of the driver installed on your system, it
replaces the old driver with the Merant 3.7 32-bit ODBC closed driver. Likewise, if it finds
an earlier version of the ODBC Administrator, it automatically overwrites it with the version
included on the Informatica installation CD.
65
2.
3.
Click Next.
4.
5.
Click Next.
6.
7.
Click Next.
The program installs the ODBC 3.7 drivers.
8.
After you install the Merant 3.7 32-bit ODBC closed drivers, you need to create an ODBC
data source for each source and target database accessed by the client tools. Refer to the
appropriate section in this chapter for details on connecting to databases.
2.
3.
4.
66
All the program files you need to run the Designer, Repository Manager, Workflow
Manager, and Workflow Monitor
Sample repository
Release notes
Online help file for the Designer, Repository Manager, Workflow Manager, and Workflow
Monitor
The custom installation allows you to choose the components you want to install.
Informatica recommends that you make a backup and copy of all existing repositories before
upgrading to PowerCenter 6.0 or PowerMart 6.0. You should upgrade the copy of your
existing repository so you can evaluate it without altering your existing repository.
You can install multiple versions of the Informatica Client tools on the same machine. To
determine which version starts when you launch the Designer, Repository Manager,
Workflow Manager, or Workflow Monitor, edit the following entry in the system win.ini file:
[Informatica PowerMart]
home=<Informatica_Client_installation_directory>
Edit the entry with the name of the installation directory of the Informatica Client version
you want to use.
Note: You must be the Administrator on the local machine to install the Informatica Client
tools.
To install the Informatica Client tools:
1.
2.
Click Next.
4.
5.
Click Next.
67
6.
Select Client.
7.
8.
9.
Click Next.
10.
Choose the directory where you want to install the Informatica Client tools.
If you have an existing version of the Informatica Client tools installed on the machine,
the existing version installation directory displays as the default installation directory.
The installation program overwrites any existing Informatica Client tools files in the
installation directory.
11.
Click Next.
12.
Specify the program folder in which the client icons will appear.
13.
Click Next.
14.
Select the components you want to install. By default, all components are selected.
Table 4-2 describes the components you can install:
Table 4-2. Informatica Client Components
68
Component
Description
The files required to run and configure the Informatica Client, including
the readme file and online help.
Documentation Files
Tutorial Files
Sample SQL scripts you can use to create the source tables and stored
procedures used in the tutorial lessons in Getting Started.
Sample Repository
15.
Click Next.
16.
The PowerCenter/PowerMart Client Tools Setup copies the selected components to your
installation directory.
17.
When the installation completes, select View Readme if you want to read the
PowerCenter/PowerMart release notes.
18.
19.
Click Finish to exit the Informatica Platform Setup and return to Windows.
2.
Configure the Oracle client. You can use the Oracle Net Services or Net8 utility or copy
an existing TNSNAMES.ORA and SQLNET.ORA file and modify it as needed.
TNSNAMES.ORA and SQLNET.ORA are stored in the
<oracle_home>\NETWORK\ADMIN directory.
Enter the correct syntax for the Oracle connect string, typically, databasename.world.
Use TCP/IP as the network protocol. PowerCenter and PowerMart support only the
TCP/IP protocol for Oracle databases.
Here is a sample TNSNAMES.ORA:
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world)
(PROTOCOL = TCP)
(Host =mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = MYORA7)
(GLOBAL_NAMES = mydatabase.world)
69
Make sure the SID entered here matches the database server instance ID defined on the
Oracle server.
3.
Verify that the system path includes the Oracle bin directory.
For example, if you install Net8 on a Windows system, your path might include the
following entry:
C:\ORACLE\ORA8\BIN
4.
5.
6.
7.
On Oracle databases, if the database character set is not the default, configure the
database to use the U.S. English character set:
On Windows 98, add the following entry to the autoexec.bat file:
SET NLS_LANG=american_america.UTF8
70
1.
Install the SQL Client software, including the Microsoft OLE DB Provider for SQL
Server.
2.
Verify that the system path includes the Microsoft SQL Server directory.
For Windows 98, if your path does not include the Microsoft SQL Server directory, edit
your AUTOEXEC.BAT file.
3.
Open the Client Network Utility. On the General tab, verify that the Default Network
Library matches the default network for your Microsoft SQL Server database.
4.
Launch ISQL_w, enter the necessary information, and connect to the Microsoft SQL
Server database.
If you connect to the database, continue with the next step. If you fail to connect to the
database, verify that you correctly entered all of the connectivity information.
Tip: Usernames and database names are case-sensitive.
5.
Create an ODBC connection for each Microsoft SQL Server source and target database.
6.
In the Workflow Manager, create a database connection for each source and target
database. The Informatica Server uses database connections to connect to the source and
target databases.
For more information, see Configuring the Workflow Manager in the Workflow
Administration Guide.
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.
71
On Windows 98, if your path does not include the Sybase directory, edit your
AUTOEXEC.BAT file.
4.
Verify that the SYBASE environment variable refers to the Sybase installation directory,
for example:
SYBASE=C:\SYBASE
5.
Launch SYBPING, enter the connectivity information, and connect to the database. If
you connect to the database, continue to step 6. If you fail to connect to the database,
verify that you correctly entered all of the connectivity information.
Usernames and database names may be case-sensitive.
6.
7.
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.
3.
In SetNet32, on the Server Information tab, configure the Informix server connectivity
information.
Table 4-3 describes the options available in the Server Information tab:
Table 4-3. Informix SetNet32 Configuration
72
Setting
Description
Informix Server
Host Name
Description
Protocol Name
Protocol the server uses, usually onsoctcp. Ask your Informix Administrator.
Service Name
Service name the Informix server uses. Ask your Informix Administrator. The
Informix server must also be defined in the services file for the following operating
systems:
Windows 98: %WINDIR%\Services
Windows NT/2000/XP: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr
1525/tcp
In the Host tab, enter the following information for each Informix server:
4.
Setting
Description
Current Host
User Name
Password Option
Password
On Windows 98, if your path does not include the Informix directory, edit your
AUTOEXEC.BAT file.
5.
Enable transaction logging for each repository database. Perform a level-0 archive using
ontape. The syntax is:
ontape -s -B <dbname>
This command performs the archive and turns buffered logging on at the same time.
You can also create the database with logging turned on. You can set logging to buffered
or unbuffered.
6.
Launch ILogin Demo or SQLEditor, enter the necessary information, and connect to the
Informix database.
This step assumes you created the demonstration database on the machine where the
Informix database is installed. To create the demonstration database on a UNIX machine,
run dbaccessdemo7. This creates a small database called stores7, which you can use to run a
variety of tests. To create a demonstration database on Windows, run dbaccessdemo7.bat
in %INFORMIXDIR%\bin.
Note: If you connect to the database, continue with the next step. If you fail to connect to
the database, verify that you correctly entered all of the connectivity information. You
need to connect to the database before you can create an ODBC data source. For more
73
Create an ODBC data source for each Informix source and target database.
Install the Merant 3.7 32-bit ODBC closed driver included on the Informatica
installation CD. For details, see Using ODBC on page 193.
8.
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.
74
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-ProgramsDB2 for Windows NT. A list of databases appears.
If the required database is not listed, click the Add button and follow instructions in
the DB2 Add Database SmartGuide. Remember to check Register this Database for
ODBC.
If the required database is listed, but states [Not registered] in the ODBC Name
column, you must register it. Select the database name and click Properties. Select
Register this database for ODBC and click OK.
Verify you can connect to the required database by selecting the database name and
clicking Test. Then supply a valid username and password and click OK. The
following message displays: The connection test was successful, followed by some
database details. If you cannot connect to the database, consult the DB2
documentation and/or your system administrator.
3.
From the Informatica Client tools, use the data source name as registered by the DB2
client configuration tool for ODBC. Use the entry with the name labeled IBM DB2
ODBC driver. Use only this driver, and not any DB2 driver from the Merant ODBC
package supplied on the Informatica installation CD.
4.
In the Workflow Manager, create a database connection for each source and target
database.
For more information, see Configuring the Workflow Manager in the Workflow
Administration Guide.
2.
3.
In the Workflow Manager, create a database connection for each source and target
database.
For more information, see Configuring the Workflow Manager in the Workflow
Administration Guide.
2.
Install the Microsoft Excel ODBC driver provided with Microsoft Excel.
Step 3. Connecting to Databases
75
3.
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.
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.
10.
In the Workflow Manager, create a database connection for each source and target
database.
For more information, see Configuring the Workflow Manager in the Workflow
Administration Guide.
76
1.
Install WinDDI, Teradata Client, Teradata ODBC driver, and any other Teradata
software you might need.
2.
Launch the ODBC 32-bit Data Source Administrator by selecting ODBC Data Sources
from the Control Panel.
3.
From the ODBC Data Source Administrator, create and configure ODBC data sources.
4.
To create a data source name (DSN), click the System DSN tab, and click Add.
5.
6.
Enter the name for the new ODBC data source and the name of the Teradata server or its
IP address.
If necessary, enter the username and password to open a connection to the default
database.
7.
Click OK twice to close the ODBC Data Source Administrator dialog box.
77
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.
78
Chapter 5
Troubleshooting, 95
79
2.
3.
4.
You can install one Repository Server on a Windows machine. Before you begin, locate the
PowerCenter/PowerMart product license key. Use the same product license key to install the
Repository Server, the Informatica Server, and the Informatica Client tools.
Note: Please read the release notes for last minute changes to the Repository Server installation
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select for each PowerCenter/PowerMart component are compatible with each other. For more
information, see Globalization Overview on page 29.
Installation Guidelines
Use the following guidelines before you install the Repository Server on a Windows system:
1.
2.
Make sure you have 30 MB of disk space available on the Windows boot drive. The
Informatica Platform Setup requires this space for temporary files.
3.
Verify you have the appropriate Windows user accounts to install the Repository Server,
run the Repository Server service, and access the managed repository databases.
80
1.
Windows user with administrator rights. To install the Repository Server, log on to the
Windows system as a member of the Administrators group in the local domain.
2.
Windows user that runs the Repository Server service. Before you install the Repository
Server, create a user account with the right to run services, known as the Service Start
Account. Verify this account has the Logon as a service right. Create this account
specifically to run the Repository Server. Do not run the Repository Server as the System
account.
For details on creating a user account to run the Repository Server service, see
Troubleshooting on page 95.
Note: You can create either a local or domain account. To manage repositories on a
Microsoft SQL Server database that uses Windows integrated security, you must create a
domain account.
3.
Database user for each managed repository. When you configure the repository, you
enter a username and password to access the database containing the repository. This is
the owner name defined by the database. The Informatica Server uses this name to
connect to the repository database. This user is not a Windows or repository account.
The password must be in US-ASCII only.
81
Log on to the Windows machine as a user who is a member of the local Administrators
group.
2.
Enter your name, your company name, and platform license key in the User Informatica
dialog box. Click Next.
4.
In the Select Components dialog box, select Informatica Repository Server. Click Next.
5.
6.
In the Edit Service Account dialog box, enter the domain, username, and password for
the user account that will run the Informatica Repository Server service. The user
account must have the Logon as a service right. Click Next.
7.
In the Destination Location dialog box, select the directory where you want to install the
Repository Server. Click Next.
8.
In the Select Program Folder dialog box, select the program folder in the Start Menu
where you want to install the Repository Server shortcuts. Click Next.
The setup application copies files to the destination directory and installs the Repository
Server service.
9.
When setup application finishes installing the Repository Server service, it starts the
Repository Server setup program. Enter the Repository Server configuration parameters
and click OK, or click Cancel to configure the Repository Server later.
For more information on configuring the Repository Server, see Step 2. Configuring the
Repository Server on Windows on page 83.
82
10.
Select View Readme if you want to read the PowerCenter/PowerMart release notes.
11.
12.
If the Repository Server is the only platform component you wish to install, click Finish
to exit the Informatica Platform setup and return to Windows.
If you want to configure the Repository Server after the installation program finishes
choose Informatica Repository Server-Repository Server Setup from the Windows Start
Menu.
2.
3.
Required/
Optional
Required
Administrative Password
Required
Description
83
84
Option
Required/
Optional
Required
Required
Configuration Directory
Required
Backup Directory
Required
Plugin Directory
Required
Severity Level
Required
Optional
Output to File
Optional
Description
2.
Configure the Oracle client. You can use the Oracle Net Services or Net8 utility or copy
an existing TNSNAMES.ORA and SQLNET.ORA files and modify them 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.
You must use TCP/IP as the network protocol. PowerCenter and PowerMart support
only the TCP/IP protocol for Oracle databases.
Here is a sample TNSNAMES.ORA:
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world)
(PROTOCOL = TCP)
(Host = mymachine)
(Port = 1521)
)
)
(CONNECT_DATA =
85
(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 Net8, your path might include the following entry:
C:\ORANT8\BIN
4.
5.
6.
On Oracle databases, if the database character set is not the default, configure the
database to use the U.S. English character set. In the Windows Control Panel, doubleclick System. In the Environment tab, set the System Variable to NLS_LANG and the
value to american_america.UTF8.
Install the SQL Client software, including the Microsoft OLE DB Provider for SQL
Server.
2.
Verify that the system path includes the Microsoft SQL Server directory.
For example, your path might include the following entry:
PATH=C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
86
3.
Open the Client Network Utility. On the General tab, verify that the Default Network
Library matches the default network for your Microsoft SQL Server database.
4.
Launch ISQL_w, and enter a database name, username, and password. Try to connect to
the Microsoft SQL Server database. If you fail to connect to the database, verify that you
correctly entered all of the connectivity information. Usernames and database names are
case-sensitive.
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
4.
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.
87
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.
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 machines hosting the
Repository Server.
2.
3.
In SetNet32, on the Server Information tab, enter the server connectivity information for
each server.
Table 5-2 describes the options available on the Server Information tab:
Table 5-2. Informix SetNet32 Configuration
Setting
Description
Informix Server
Host Name
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 98: %WINDIR%\Services
Windows NT/2000/XP: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr
1525/tcp
On the Host tab, enter the host connectivity information for the Informix Server:
4.
88
Setting
Description
Current Host
User Name
Password Option
Password.
Password
For example:
PATH=%INFORMIXDIR%\bin;%PATH%
If your path does not include the Informix directory, edit your AUTOEXEC.BAT file.
5.
Launch ILogin Demo or SQLEditor, enter the necessary information, and connect to the
Informix database.
This step assumes you created the demonstration database on the machine where the
Informix database is installed. To create the demonstration database on a UNIX machine,
run dbaccessdemo7. This creates a small database called stores7, which you can use to run a
variety of tests. To create a demonstration database on Windows, run dbaccessdemo7.bat
in %INFORMIXDIR%\bin.
Note: If you connect to the database, continue with the next step. If you fail to connect to
the database, verify that you correctly entered all of the connectivity information. You
need to connect to the database before you can create an ODBC data source. For more
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).
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 (directory where the client is installed)
Verify that the PATH environment variable includes the \BIN subdirectories of your
DB2 Client Application Enabler (CAE) installation directory (default C:\SQLLIB). For
example:
PATH=C:\WINNT\SYSTEM32;C:\SQLLIB\BIN;...
2.
Configure or verify the configuration of the DB2 Client Application Enabler (CAE).
Open the DB2 Client Configuration Assistant utility. For example, Start-ProgramsDB2 for Windows. A list of databases appears.
If the required database is not listed, click the Add button and follow the instructions
in the DB2 Add Database SmartGuide.
Step 3. Connecting to Databases
89
90
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.
2.
3.
4.
5.
From the scrolling list of services installed on the Windows machine, select Informatica
Repository Server.
6.
Click Start.
The Repository Server might take a moment to start.
7.
If you would like the Repository Server service to run every time the computer starts,
choose Automatic as the Startup Type.
8.
91
If you configured the Repository Server to write messages to the Windows event log, use the
Windows Event Viewer to verify the Repository Server started.
To verify the Repository Server started in the Windows Event Viewer:
1.
2.
Event
PmRepServer
34003 displays
if the Repository
Server
successfully
starts.
92
You should see several events in the Application log for PmRepServer. Select the latest
event. It should indicate it completed initialization:
2.
3.
Switch to the Repository Server installation directory and enter the following command:
pmrepserver -p -h <hostname>:<port_number>
Specify the host name of the machine running the Repository Server you want to ping,
and the port number it uses for connections.
The Repository Server returns the following message when it pings a running Repository
Server:
Informatica Repository Server running at <hostname>:<port number>
93
2.
2.
In the Configure Servers dialog box, choose the Repository Server you want to stop from
the Hostname list.
3.
4.
Click Connect.
5.
Confirm that all repositories managed by the Repository Server are shut down. For details
on shutting down the repository, see Managing the Repository in the Repository Guide.
6.
7.
Use the following steps to shut down the Repository Server from the Windows command
prompt:
To stop the Repository Server from the Windows command prompt:
1.
Log on to the Windows machine as the user who has rights to start and stop the
Repository Server service.
2.
3.
Switch to the Repository Server installation directory and enter the following command.
pmrepserver -s -h <host_name>:<port_number>
Specify the Repository Server administrative password, the host name of the machine
running the Repository Server, and the port number it uses for connections.
4.
To verify that the Repository Server stopped, check the Repository Server log file. The
Repository Server writes the following message to the log file if it successfully stops:
INFO : SF_34014 Server shut down.
94
Troubleshooting
This section contains information on troubleshooting the Repository Server on Windows.
I installed the Repository Server on a Windows NT system, but I cannot start the
Repository Server.
If you cannot start the Repository Server, you may receive the following message:
Error 1069 (The service did not start due to a logon failure)
Use the Windows Event Viewer to check the Application log. If possible, correct any errors
described in the application log. Also, verify the service start information.
The Service Start Account needs the advanced NT user right Log on as a service on the
Windows system. Follow these steps to verify that the account with proper rights also starts
the Repository Server:
1.
2.
3.
Select This Account, and enter the account name and password assigned to the
Repository Server service.
If the correct account user is displayed, reenter the account user to have NT verify the
rights assigned to this user.
4.
Click OK.
If the user has the necessary rights to run the Repository Server, the dialog box closes.
Troubleshooting
95
If the user does not have the correct rights, a message appears asking if you want this user
to have the Log on as a service right. Select OK to assign the Log on as a service right to this
user.
Try to start the Repository Server again. If it does not start, call Informatica Technical
Support.
I installed the Repository Server on a Windows 2000 system, but I cannot start it.
If you cannot start the Repository Server, you may receive the following message:
Error 1069 (The service did not start due to a logon failure)
Use the Windows 2000 Event Viewer to check the Application log. If possible, correct any
errors described in the application log. Also, verify the service start information.
The Service Start Account needs the Windows 2000 user right Log on as a service on the
Windows 2000 system. Follow these steps to verify that the account has the correct rights to
start the Informatica Server:
96
1.
In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2.
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.
6.
Click OK when finished and close the Local Security Settings dialog box.
Use the following steps to verify that the account with the right to log on as a service also
starts the Informatica Repository Server service:
1.
In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2.
3.
Troubleshooting
97
4.
5.
Select This Account, and enter the account name and password assigned to the
Informatica Repository Server service. You can also click Browse to search for an account
name.
If the correct account user is displayed, reenter the account user to have Windows 2000
verify the rights assigned to this user.
6.
Click OK.
7.
Close the Informatica Repository Server Properties dialog box and start the Informatica
Repository Server service again.
If the Repository Server does not start, call Informatica Technical Support.
98
Chapter 6
99
2.
3.
4.
Before you begin, locate the PowerCenter/PowerMart product license key. Use the same
product license key to install the Repository Server, Informatica Server, and Informatica
Client tools.
Please read the release notes for last minute changes to the Repository Server installation and
connectivity issues.
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select in each component of PowerCenter and PowerMart are compatible with each other. For
more information, see Globalization Overview on page 29.
100
2.
Set the library path to the absolute directory path where the Repository Server is to be
installed for the following operating systems:
Table 6-1 describes the library paths for different UNIX operating systems:
Table 6-1. Library Path for Repository Server on UNIX
3.
Operating System
Library Path
Solaris
LD_LIBRARY_PATH
AIX
LIBPATH
HP
SHLIB_PATH
On the Informatica installation CD, locate the directory specific to the product.
For example, if you are installing the Repository Server on a Solaris system, switch to the
unixserv/pc/solaris directory.
4.
Run install.
Using a Bourne shell, type ./install.
Using a C-shell, type sh install.
5.
English
Japanese
If you are running one or more Repository Server processes, a message displays warning
you that the install may cause problems.
Step 1. Installing the Repository Server
101
6.
7.
8.
Enter the absolute target directory path where you want to install the Repository Server.
9.
10.
Type Y if you want to view the readme file, or N if you wish to read it later.
11.
The installation program starts the pmrsconfig configuration utility. Configure the
Repository Server.
For details on configuring the Repository Server on UNIX, see Step 2. Configuring the
Repository Server on UNIX on page 103.
12.
102
2.
Required/
Optional
ServerPort
Required
The port number the Repository Server uses for repository client
connections. By default, this value is set to 5001.
AdminPasswd
Required
RaMinPort
Required
The minimum port number the Repository Server can assign to the
Repository Agent process. By default, this value is set to 5002.
RaMaxPort
Required
The maximum port number the Repository Server can assign to the
Repository Agent process. By default, this value is set to 65535.
ConfigDir
Required
BackupDir
Required
PluginDir
Required
Description
103
3.
104
Option
Required/
Optional
ErrorSeverityLevel
Required
LogFileName
Required
The name of the Repository Server log file. The default Repository
Server log file name is pmrepserver.log.
Description
Install the native client software on the machine hosting Repository Server.
2.
3.
Set the PATH variable to include the directory where the Repository Server is installed.
4.
Shared Library
Environment Variable
Solaris
LD_LIBRARY_PATH
AIX
LIBPATH
HP
SHLIB_PATH
C-shell
Bourne Shell
For example, if you have an Oracle repository and the Repository Server is installed on
Solaris, you could set the shared library variables as follows:
Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmrepserver_dir:$ORACLE_HOME/
lib; export LD_LIBRARY_PATH
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
pmrepserver_dir:$ORACLE_HOME/lib
5.
6.
105
For information on supported datatypes for each database see Datatype Reference in the
Designer Guide.
For information on connecting to a Teradata database, see the Supplemental Guide.
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.
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/pmrepserver_dir
:$ORACLE_HOME/lib
4.
Set the TNS_ADMIN environment variable to the path for TNSNAMES. For example:
Using a Bourne Shell:
$ TNS_ADMIN=/HOME2/NETWORK/ADMIN; export TNS_ADMIN
106
Using a C-shell:
$ setenv TNS_ADMIN=/HOME2/NETWORK/ADMIN
Note: This step is optional, and might vary depending on your configuration.
5.
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)
(GLOBAL_NAMES = mydatabase.world)
7.
Launch SQL*Plus and try to connect to the database. If you fail to connect to the
database, verify that you correctly entered all of the connectivity information.
Use the correct connect string (as defined in TNSNAMES.ORA) and username.
Usernames and database names are case-sensitive.
107
8.
On Oracle databases, if the database character set is not the default, configure the
database to use the U.S. English character set:
On Windows 98, add the following entry to the autoexec.bat file:
SET NLS_LANG=american_america.UTF8
2.
Using a C-shell:
$ setenv PATH ${PATH}:/usr/sybase/bin
3.
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmrepserver_dir:$SYBASE/lib
108
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.
2.
3.
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.
Using a C-shell:
$ setenv PATH ${PATH}:$INFORMIXDIR/bin
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Repository Server
installation directory. If you installed the Repository Server in the $HOME/pmrepserver
directory, you could type:
Using a Bourne Shell:
$ LD_LIBRARY_PATH=$HOME/pmrepserver_dir:$INFORMIXDIR/lib:$INFORMIXDIR/
lib/esql; export LD_LIBRARY_PATH
109
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmrepserver_dir:$INFORMIXDIR/
lib:$INFORMIXDIR/lib/esql
6.
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.
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
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
database, verify that you correctly entered all of the connectivity information.
Install or verify that you have already installed IBM DB2 Client Application Enabler
(CAE), Version 6.1 or above.
If a DB2 database server is running, or the DB2 Connect option is installed, database
connections may already be available. If not, complete the following steps. These
examples use the C-shell and assume you are logged in as the user where you intend to
run the Repository Server (pmrepserver).
2.
Install or verify that the UNIX IBM DB2 software, including the Client Application
Enabler (CAE), is installed at different locations, depending on the operating system
platform. The DB2DIR environment variable should always be set to point at this base
installation directory. The IBM DB2 Version 6.1 defaults are as follows:
For Solaris:
$ setenv DB2DIR
110
/opt/IBMdb2/v6.1
For HP-UX:
$ setenv DB2DIR
/opt/IBMdb2/v6.1
For AIX:
$ setenv DB2DIR
3.
/usr/lpp/db2_06_01
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
$ setenv INSTHOME
4.
db2admin
~db2admin
The UNIX IBM DB2 software uses a number of shared library components that are
loaded dynamically by the Repository Server. To locate the shared libraries at run-time,
the shared library environment variable requires alteration, depending on operating
system platform:
For example, on Solaris:
$ setenv LD_LIBRARY_PATH
5.
To run IBM DB2 command line programs, the PATH environment variable should be
edited as follows:
$ setenv PATH
6.
$DB2DIR/lib:${LD_LIBRARY_PATH}
$DB2DIR/bin:${PATH}
Edit into your (.cshrc) the complete set of shell commands appropriate to your operating
system platform. Either log out and in again, or issue the command:
$ source .cshrc
7.
If you are configuring a new DB2 installation, you need to set up a remote database. Run
the DB2 Command Line Processor (db2) and issue the CATALOG <protocol> NODE
and CATALOG DATABASE commands to set up a remote database.
Consult the DB2 installation guide for details.
8.
Verify the name of your remote database. Run the DB2 Command Line Processor (db2)
and issue the LIST DATABASE DIRECTORY command for a list of available databases.
It is recommended that database entries for use with Repository Server exactly match
those in the client tools.
9.
Verify you can connect to the DB2 database. Run the DB2 Command Line Processor
(db2) and issue the command:
CONNECT TO <databasename> USER <username> USING <password>
111
2.
2.
Switch to the Repository Server installation directory and enter the following command:
pmrepserver -p -h <hostname>:<port_number>
Specify the host name of the machine running the Repository Server you want to ping,
and the port number it uses for connections.
The Repository Server returns the following message when it pings a running Repository
Server:
Informatica Repository Server running at <hostname>:<port number>
112
2.
Switch to the Repository Server installation directory and enter the following command.
pmrepserver -s -h <host_name>:<port_number>
Specify the Repository Server administrative password, the host name of the machine
running the Repository Server, and the port number it uses for connections.
3.
To verify that the Repository Server stopped, check the Repository Server log file. The
Repository Server writes the following message to the log file if it successfully stops:
INFO : SF_34014 Server shut down.
Use the following steps to stop the Repository Server from the Repository Manager.
To stop the Repository Server from the Repository Manager:
1.
2.
In the Configure Servers dialog box, choose the Repository Server you want to stop from
the Hostname list.
3.
4.
Click Connect.
5.
Confirm that all repositories managed by the Repository are shut down.
6.
7.
113
114
Chapter 7
Creating a Repository
This chapter includes the following topics:
Overview, 116
Tips, 123
115
Overview
After you install and configure the Informatica Client and Repository Server, you can create a
repository. A repository contains metadata you create using the Informatica Client tools and
the Informatica Server uses to move and transform data from sources to targets.
Use the Repository Manager to create and administer the repository. The Repository Manager
connects to the repository database through the Repository Server, so you must install and
configure the Repository Server before working with repositories. There are three different
types of repository:
Local repository. (PowerCenter only.) A repository within a domain that is not the global
repository. Each local repository in the domain can connect to the global repository and
use objects in its shared folders.
Once you create a global repository, you cannot change it to a local repository. However, you
can promote an existing local repository to a global repository.
Warning: The Informatica repository tables have an open architecture. Although you can view
the repository tables, Informatica strongly advises against altering the tables or data within the
tables. Informatica is not responsible for corrupt data that is caused by customer alteration of
the repository tables or data within those tables.
116
Creating a Repository
Before you can create a repository, you must first create and configure the database to contain
the repository and install and configure the Repository Server and Informatica Client tools.
You can locate the repository on the source or target database systems. However, to protect
your repository, consider keeping the repository separate from overloaded machines. Verify
the following requirements for the repository database:
You can locate the Repository Server on the source or target database systems. To improve
repository performance, consider installing the Repository Server on a machine with a fast
network connection. The Repository Server can manage repositories on different machines on
the network. Verify the following requirements for the Repository Server machine:
40 MB disk space
32 MB RAM, plus 16 MB RAM for each repository the Repository Server manages
For more information on installing and configuring the Repository Server, see Installing and
Configuring the UNIX Repository Server on page 99, and Installing and Configuring the
Windows Repository Server on page 79.
Note: If you want to create, restore, or upgrade a Sybase repository, set allow nulls by default to
TRUE at the database level. Setting this option changes the default null type of the column to
null in compliance with the SQL standard.
When you create a repository, you must have the following information available:
Database username and password. This login must have the appropriate database
permissions to create the repository. In the new repository, this login becomes a default
user with full privileges in the repository. The username may be in other languages, but the
password must be in US-ASCII only.
Code page. When you create a repository, you must specify a code page from a list of code
pages that are compatible with the Informatica Client. The code page contains the
character set of the data in the repository. Once specified, you cannot change the code
page. The Informatica Client and Server code pages must be compatible with the
repository code page.
For more information on code pages, see Globalization Overview on page 29.
Creating a Repository
117
To create a repository:
118
1.
2.
Enter the host name and port number of the machine running the Repository Server, and
enter the Repository Server administration password.
3.
4.
5.
Click OK. The Repository Configuration dialog box appears, displaying the Repository
tab.
6.
Table 7-1 describes the repository connectivity options available on the Repository tab:
Table 7-1. Repository Database Connectivity Configuration
Option
Required/
Optional
Description
DatabaseType
Required
CodePage
Required
RepositoryName
Required
ConnectString
Required
The native connect string the Repository Server uses to access the
database containing the repository. Note that this is not an ODBC
data source name, but a native connect string (for example,
servername@dbname for Microsoft SQL Server, or dbname.world
for Oracle). For a list of native connect string syntax for supported
repository databases, see Table 2-3 on page 23.
DBUser
Required
The account for the database containing the repository. Set up this
account using the appropriate database client tools.
DBPassword
Required
7.
8.
Creating a Repository
119
Table 7-2 describes the repository Server network settings available on the Network tab:
Table 7-2. Repository Network Configuration
120
Option
Required/
Optional
MessageReceiveTimeout
Required
MessageSendTimeout
Required
Description
9.
10.
Table 7-3 describes the repository configuration options available on the Configuration
tab:
Table 7-3. Repository Configuration
Option
Required/
Optional
MaximumConnections
Required
ErrorSeverityLevel
Required
The level of error messages written to the repository log file. Specify
one of the following:
- Error. Writes ERROR code messages to the log file.
- Warning. Writes WARNING and ERROR code messages to the log
file.
- Information. Writes INFO, WARNING, and ERROR code messages
to the log file.
- Trace. Writes TRACE, INFO, WARNING, and ERROR code
messages to the log file.
Informatica recommends using the Trace and Information logging
levels for troubleshooting purposes only. Default is Warning.
DateDisplayFormat
Required
DynamicConfig
RefreshInterval
Required
The number of seconds the repository waits to poll for updates to its
configuration. By default, this value is set to 10 seconds.
ThreadWaitTimeout
Required
MaximumLocks
Required
LogFileName
Required
The path and name of the Repository Agent process log file. If you do
not specify a unique log file name, the Repository Agent process
automatically writes messages to pmrepagent.log. By default, this
option specifies pmrepagent.log.
Description
11.
Click OK. The Repository Server begins building the repository. You can see the progress
in the Repository Manager Output window.
12.
If you use PowerCenter, the Repository Manager prompts you to create a global
repository. To create a global repository, click Yes. To create a local repository, click No.
Once created, you cannot change a global repository to a local repository. If you are not
sure you want to create a global repository, click No. You can promote an existing local
repository to a global repository later.
Creating a Repository
121
122
13.
In the Manage Repositories dialog box, select the repository and click Start. The
Repository Server starts the repository.
14.
Tips
The following tips help you create a repository:
Set Oracle storage parameters to prevent the repository from using excessive amounts of
disk space.
When creating a repository in an Oracle database, make sure the storage parameters specified
for the tablespace that contains the repository are not set too large. Since many target
tablespaces are initially set for very large INITIAL and NEXT values, large storage parameters
cause the repository to use excessive amounts of space. Also verify that the default tablespace
for the user that owns the repository tables is set correctly.
The following example shows how to set the recommended storage parameters, assuming the
repository is stored in the REPOSITORY tablespace:
ALTER TABLESPACE REPOSITORY DEFAULT STORAGE ( INITIAL 10K NEXT 10K
MAXEXTENTS UNLIMITED PCTINCREASE 50 );
Tips
123
124
Chapter 8
Troubleshooting, 152
125
2.
3.
4.
5.
Before you begin, locate the PowerCenter/PowerMart product license key. Use the same
product license key to install the Informatica Server and Informatica Client tools.
Note: Please read the release notes for any last minute changes to the Informatica Server
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select in each component of PowerCenter and PowerMart are compatible with each other. For
more information, see Globalization Overview on page 29.
DHCP
When configuring the Informatica Server, avoid using the Dynamic Host Configuration
Protocol (DHCP) for machine hosting the Informatica Server.
DHCP dynamically assigns a new IP address each time you start a machine on the network. If
you use DHCP on the Informatica Server machine, each time you start the Informatica
Server, you must re-register the Informatica Server with the repository so the Informatica
Client can communicate with the Informatica Server at the new address.
If the Informatica Server machine has only one network card, after starting the Informatica
Server, edit the existing Informatica Server connection information in the Workflow Manager.
You may need to resolve the Informatica Server IP address in the Server Editor dialog box in
the Workflow Manager.
If the Informatica Server machine has multiple network cards, configure the Informatica
Server with the desired IP address in the Informatica Server setup program. After you
configure the Informatica Server with the correct IP address, you can start it. You may also
need to resolve the Informatica Server IP address in the Server Editor dialog box in the
Workflow Manager.
126
Installation Guidelines
Use the following guidelines before you install the Informatica Server on a Windows system:
1.
2.
Verify that the date and time are correct on the host computer task bar. Make sure the
time zone is correct to ensure that your workflows run when you expect. The Workflow
Manager displays the date and time based on the machine hosting the Informatica Server.
Note: You must set the short date format to MM/DD/YYYY on Windows.
3.
Make sure you have 30 MB of disk space available on the Windows boot drive. The
Informatica Platform Setup requires this space for temporary files.
4.
If you are upgrading your version of the Informatica Server, stop the Informatica service
before running the installation program.
Windows user with administrator rights. To install the Informatica Server, log on to the
Windows system as a member of the Administrators group in the local domain.
2.
Windows user that runs the Informatica Server service. Before you install the
Informatica Server, create a user account with the right to run services, known as the
Service Start Account. To see if this account has the correct rights, run User Manager for
Domains and select the user. Select User Rights from the Policies menu. The user must
have the Logon as a service right. Create this account specifically to run the Informatica
Server. Do not run the Informatica Server as the System account.
Note: You can create either a local or domain account. To send email when you run a
workflow or access a repository on a Microsoft SQL Server database that uses Windows
integrated security, you must create a domain account.
3.
Repository user. When you configure the Informatica Server, you enter a repository
username and password specific to the Informatica Client and Informatica Server tools.
This is created using Repository Manager and is not a Windows account.
BadFiles
Cache
ExtProc
SessLogs
Before You Begin
127
SrcFiles
Temp
TgtFiles
WorkflowLogs
All workflows configured to run on the registered Informatica Server use these directories by
default. For details, see Registering the Informatica Server on page 183.
If you are running the Informatica Server on Windows 2000, you must have write, full
control, and modify permissions on the session log file directory to start the Informatica
Server.
128
Log on to the Windows machine as a user who is a member of the local Administrators
group.
2.
Enter your name, company name, and product license key. Click Next.
4.
5.
When the Edit Service Account dialog box appears, enter the Service Start Account
information for the Informatica service.
Table 8-1 describes the options available in the Edit Service Account dialog box:
Table 8-1. Installation Parameters for Informatica Server on Windows
6.
Option
Required/
Optional
Domain
Optional
The domain for the Windows system where you want to install the
Informatica Server. If the user account for the Informatica service is
a local user account, you can leave this field blank, enter a .
(single period, no quotes), or enter the name of the machine on
which you are running the installation program.
User
Required
Password
Required
Confirm
Password
Required
Description
Click Next.
129
7.
When prompted, select the directory where you want to install the Informatica Server.
You can either select an existing directory or have the installation program create a new
directory.
8.
Click Next.
The setup application copies files to the destination directory and installs the Informatica
Server service. When the setup application finishes installing the Informatica Server
service, it starts the Informatica Server setup program.
9.
Click Continue to configure the Informatica Server, or click Exit to configure the
Informatica Server later.
For more information on configuring the Informatica Server, see Step 2. Configuring
the Informatica Windows Server on page 131.
130
10.
11.
On Windows NT, the installation program prompts you to restart Windows. You must
restart Windows before you can start the Informatica Server service.
12.
If the Informatica Server is the only platform component you wish to install, click Finish
to exit the Informatica Platform setup.
Informatica Server on a Windows system. However, they are not compatible with the
Informatica Server installed on a UNIX system.
For information on additional Informatica Server configuration parameters, see Installing
and Configuring PowerCenter and PowerMart in the Supplemental Guide.
To configure the Informatica Server on Windows:
1.
If the configuration screen is not displayed from the installation, choose ProgramsInformatica Server-Informatica Server Setup from the Windows Start Menu.
2.
131
The Configure Informatica Service dialog box appears, displaying the Keys tab.
3.
Enter the keys needed to run the Informatica Server against your particular database
platforms.
For information about entering the license key for Teradata, see the Supplemental Guide.
Table 8-2 describes the options available in the Keys Tab:
Table 8-2. Keys Configuration for Informatica Server on Windows
132
Option
Required/
Optional
Platform Key
Required
Oracle Key
Optional
Sybase Key
Optional
Informix Key
Optional
Optional
Description
4.
Option
Required/
Optional
DB2 Key
Optional
ODBC Key
Optional
Description
Required/
Optional
Server Name
Required
Optional
Description
133
134
Required/
Optional
Description
Required
Shared Memory
Required
Required
Optional
Allow mapping/session
debugging
Optional
Optional
Optional
Output to File
Optional
5.
Required/
Optional
Repository Name
Required
Repository User
Required
Repository Password
Required
Required
Required
Description
135
6.
Enter the optional information needed to maintain compatibility with previous versions
of the Informatica Server and databases.
Table 8-5 describes the options available on the Compatibility and Database Tab:
Table 8-5. Compatibility and Database Configuration for Informatica NT Server
Setting
136
Required/
Optional
Description
PMServer 3.X
aggregate
compatibility
Optional
Optional
Optional
Required/
Optional
Description
Optional
Optional
If you have PowerConnect for PeopleSoft, you can use this option for
PeopleSoft sources on Oracle. You cannot, however, use it for
PeopleSoft lookup tables on Oracle or PeopleSoft sources on
Microsoft SQL Server.*
Max LKP/SP DB
Connections
Optional
Max Sybase
Connections
Optional
Max MSSQL
Connections
Optional
Number of Deadlock
Retries
Optional
Deadlock Sleep
Before Retry
(seconds)
Optional
*PowerConnect for PeopleSoft is a separate Informatica product. For more information on this product, see the
PowerConnect for PeopleSoft User and Administrator Guide.
137
7.
138
Required/
Optional
Description
Data Movement
Mode
Required
Optional
If you enable this option, the Informatica Server enforces data code page
compatibility. If you disable this option, the Informatica Server lifts
restrictions for source and target data code page selection, stored
procedure and lookup database code page selection, and session sort
order selection. This option is only available when the Informatica Server
runs in Unicode data movement mode.
By default, this option is enabled.
Output Session
Log In UTF8
Optional
If you enable this option, the Informatica Server writes to the session log
using the UTF-8 character set. If you disable this option, the Informatica
Server writes to the session log using the Informatica Server code page.
This option is available when the Informatica Server runs in Unicode
data movement mode. By default, this option is disabled.
Warn About
Duplicate XML
Rows
Optional
If you enable this option, the Informatica Server writes duplicate row
warnings and duplicate rows for XML targets to the session log. By
default, this option is enabled.
8.
Required/
Optional
Description
Create Indicator
Files for Target Flat
File Output
Optional
If you enable this option, the Informatica Server creates indicator files
when you run a session with a flat file target.
Optional
Microsoft
Exchange Profile
Optional
Date Display
Format
Required
If specified, the Informatica Server validates the date display format and
uses it in session log and server log entries. If the date display format is
invalid, the Informatica Server uses the default date display format. The
default date display format is DY MON DD HH 24:MI:SS YYYY. When
you specify a date display format, it displays in the test window. An
invalid date display format is marked invalid.
Click OK to save the configuration options. Click Exit to close the Server Setup dialog
box.
139
2.
Configure the Oracle client. You can use the Oracle Net Services or Net8 utility or copy
an existing TNSNAMES.ORA and SQLNET.ORA files and modify them 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.
You must use TCP/IP as the network protocol. PowerCenter and PowerMart support
only the TCP/IP protocol for Oracle databases.
Here is a sample TNSNAMES.ORA:
mydatabase.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = mycompany.world)
(PROTOCOL = TCP)
(Host = mymachine)
140
(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 Net8, your path might include the following entry:
C:\ORANT8\BIN
4.
5.
In the Informatica Client tools, configure each source and target database. Enter all the
necessary information to connect to each Oracle database.
6.
If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
Install the SQL Client software, including the Microsoft OLE DB Provider for SQL
Server.
2.
Verify that the system path includes the Microsoft SQL Server directory.
For example, your path might include the following entry:
C:\MSSQL\BIN;C:\MSSQL\BINN;%PATH%
3.
Open the Client Network Utility. On the General tab, verify that the Default Network
Library matches the default network for your Microsoft SQL Server database.
141
4.
Launch ISQL_w, and enter a database name, username, and password. Try to connect to
the Microsoft SQL Server database. If you fail to connect to the database, verify that you
correctly entered all of the connectivity information.
Usernames and database names are case-sensitive.
5.
If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
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
4.
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.
6.
142
If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
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.
3.
In SetNet32, on the Server Information tab, enter the server connectivity information for
each server.
Table 8-7 describes the options available on the Server Information tab:
Table 8-7. Informix SetNet32 Configuration
Setting
Description
Informix Server
Host Name
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 98: %WINDIR%\Services
Windows: %WINDIR%\System32\Drivers\etc\Services
For example, a sample entry in the services file looks like the following:
inflsnr
1525/tcp
143
On the Host tab, enter the host connectivity information for the Informix Server:
4.
Setting
Description
Current Host
User Name
Password Option
Password.
Password
5.
Launch ILogin Demo or SQLEditor, enter the necessary information, and connect to the
Informix database.
This step assumes you created the demonstration database on the machine where the
Informix database is installed. To create the demonstration database on a UNIX machine,
run dbaccessdemo7. This creates a small database called stores7, which you can use to run a
variety of tests. To create a demonstration database on Windows, run dbaccessdemo7.bat
in %INFORMIXDIR%\bin.
Note: If you connect to the database, continue with the next step. If you fail to connect to
the database, verify that you correctly entered all of the connectivity information. You
need to connect to the database before you can create an ODBC data source. For more
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).
6.
If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
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
144
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.
3.
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-ProgramsDB2 for Windows. A list of databases appears.
If the required database is not listed, click the Add button and follow the instructions
in the DB2 Add Database SmartGuide. Remember to check Register this Database for
ODBC.
If the required database is listed, but states [Not registered] in the ODBC Name
column, you must register it. Select the database name and click Properties. Check
Register this database for ODBC and click OK.
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.
If you did not enter the database-specific key in the Informatica Server configuration, see
Step 2. Configuring the Informatica Windows Server on page 131.
2.
3.
If you did not enter the ODBC key in the Informatica Server configuration, see Step 2.
Configuring the Informatica Windows Server on page 131.
145
2.
Install the Microsoft Excel ODBC driver provided with Microsoft Excel.
3.
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.
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.
146
9.
10.
If you did not enter the ODBC key in the Informatica Server configuration, see Step 2.
Configuring the Informatica Windows Server on page 131.
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.
6.
7.
8.
Click OK twice to close the ODBC Data Source Administrator dialog box.
9.
Before you run a session, test the ODBC connection using an ODBC query tool, such as
WinDDI. Before you test the ODBC connection, log into Windows as the advanced user
with the Log on as a service right.
147
Before you can start the Informatica Server, you must register it in the Workflow Manager.
You must also install, configure, and start the Repository Server. For more information, see
Registering the Informatica Server on page 183, Installing and Configuring the Windows
Repository Server on page 79, and Installing and Configuring the UNIX Repository Server
on page 99.
When you start a PowerMart Server, it verifies that it is the only Informatica Server registered
in the repository. It does not start if there are other Informatica Servers registered in the
repository.
When you send a request to stop the Informatica Server, the Informatica Server first removes
all workflows scheduled to run in the future. It then attempts to stop all running workflows.
If any workflow fails to respond within a certain period of time, the Informatica Server aborts
the remaining workflows. Allow 1 to 2 minutes for the Informatica Server to complete all
processes. When you restart the Informatica Server, you must reschedule all workflows.
Verify that the repository database and Repository Server managing the repository are
running.
2.
In the Workflow Manager, verify the Informatica Server is registered in the repository.
If the Informatica Server is not registered in the repository, use the Workflow Manager to
register it.
3.
4.
5.
6.
From the scrolling list of services installed on the Windows machine, select Informatica.
7.
Click Start.
The Informatica Server might take a moment to start.
148
8.
If you would like the Informatica service to run every time the computer starts, choose
Automatic as the Startup Type. Be sure that access to all necessary database services and
the Repository Server are available at boot time from the host.
9.
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 34003
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 152 for possible solutions. Also see the
Troubleshooting Guide for more information.
149
2.
2.
3.
4.
5.
Click OK.
Once the Informatica Server starts it connects to the Repository Server. If the Repository
Server is installed on the same machine, the Informatica Server might start before the
Repository Server and consequently fail to connect to the Repository Server.
If the repository is stored in a database on a local database server and the database server also
runs as a service, the Informatica Server might start before the database server and
consequently fail to connect to the database server.
Workflow Manager
With the Workflow Manager, you can stop the Informatica Server. However, you must first
configure the Workflow Manager to communicate with the Informatica Server.
You can shut down the Informatica Server in the complete, stop, or abort mode. In the
complete mode, the Informatica Server allows currently running workflows to complete
before shutting down the Informatica Server. In the stop mode, the Informatica Server stops
the running workflows. In the abort mode, the Informatica Server aborts the running
workflows.
You must have one of the following privileges to shutdown:
Administer Server
Super User
150
1.
2.
In the Navigator window, right-click on the Informatica Server and choose Shutdown
Server-Complete, Shutdown Server-Stop, or Shutdown Server-Abort from the menu.
The Workflow Manager executes the command. In the Output window, you should see
the following text:
{server_name} Shutdown Server: Request acknowledged
{server_name} Shutdown Server: Completed
pmcmd Program
The shutdownserver command stops the Informatica Server. You must have one of the
following privileges to use this command:
Administer Server
Super User
You can shut down the Informatica Server in the complete, stop, or abort mode. In the
complete mode, the Informatica Server allows currently running workflows to complete
before shutting down the Informatica Server. In the stop mode, the Informatica Server stops
the running workflows. In the abort mode, the Informatica Server aborts the running
workflows.
Use the following syntax to stop the Informatica Server:
pmcmd shutdownserver <-serveraddr|-s>[host:]portno <<-user|-u>
username|<-uservar|-uv> userEnvVar > <<-password|-p> password|<passwordvar|-pv> passwordEnvVar> <-complete|-stop|-abort>
For more details on using pmcmd, see Using pmcmd in the Workflow Administration Guide.
151
Troubleshooting
This section contains information on troubleshooting the Informatica Server on Windows.
I installed and registered the Informatica Server, but I get an internal error when I try to
start the service.
Verify that the Repository Server is running. You must start the Repository Server before you
can start the Informatica Server.
I installed the Informatica Server on a Windows system, but I cannot start the Informatica
Server.
If you cannot start the Informatica Server, or you receive the message Error 1069 (The
service did not start due to a logon failure), use the Windows Event Viewer to check the
Application log. If possible, correct any errors described in the application log. Also, verify the
service start information.
The Service Start Account needs the advanced NT user right Log on as a service on the
Windows system. Follow these steps to verify that the account with proper rights also starts
the Informatica Server.
1.
2.
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.
152
Click OK.
If the user has the necessary rights to run the Informatica Server, the dialog box closes.
If the user does not have the correct rights, a message appears asking if you want this user
to have the Log on as a service right. Select OK to assign the Log on as a service right to this
user.
In addition, verify the connectivity settings you specify in the Informatica Server Setup and
the Server dialog box in the Workflow Manager are correct:
1.
Make sure you entered the correct information on the Repository tab of the Informatica
Server Setup program. The Informatica Server needs the exact repository name,
Repository Server hostname and port number, and repository username and password to
start.
2.
Make sure you registered the Informatica Server in the Workflow Manager.
3.
Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Workflow Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
Informatica Technical Support.
I installed the Informatica Server on a Windows 2000 system, but I cannot start the
Informatica Server.
If you cannot start the Informatica Server, or you receive the message Error 1069 (The
service did not start due to a logon failure), use the Windows 2000 Event Viewer to check
the Application log. If possible, correct any errors described in the application log. Also, verify
the service start information.
The Service Start Account needs the Windows 2000 user right Log on as a service on the
Windows 2000 system. Follow these steps to verify that the account has the correct rights to
start the Informatica Server:
1.
In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2.
Troubleshooting
153
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.
154
6.
Click OK when finished and close the Local Security Settings dialog box.
Use the following steps to verify that the account with the right to log on as a service also
starts the Informatica service:
1.
In the Windows 2000 Control Panel, double-click the Administrative Tools icon.
2.
3.
4.
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 Workflow Manager are correct:
1.
Make sure you entered the correct information on the Repository tab of the Informatica
Server Setup program. The Informatica Server needs the exact repository name,
Repository Server hostname and port number, and repository username and password to
start.
2.
Make sure you registered the Informatica Server in the Workflow Manager.
Troubleshooting
155
3.
Make sure the settings specified in the Informatica Server Setup program match those
specified for the Informatica Server registered in the Workflow Manager.
Try to start the Informatica Server again. If the Informatica Server does not start, call
Informatica Technical Support.
I started the Informatica Server, but it does not connect to the repository.
Verify that the Informatica Server and the system on which you installed the Informatica
Server are configured to connect to the Repository Server. Also verify that the Repository
Server is running.
The Workflow Manager cannot connect to the Informatica Server.
Verify that the Informatica Server is running. Make sure you have the correct connectivity
settings specified in the Server dialog box in the Workflow Manager.
The Informatica Server does not start after rebooting the machine.
In the Services configuration, make sure the Startup Type is set to automatic.
The Services dialog box shows that the Informatica Server started, but it does not seem to
be running.
After you start the Informatica Server, the Services dialog box displays the status as Started.
This does not necessarily indicate the Informatica Server is running. If the Informatica Server
stops because of an error, the status does not change automatically in this dialog box.
To determine if the Informatica Server started, either:
156
Chapter 9
157
2.
3.
Configure the Informatica Server machine to connect to each source and target database.
4.
5.
Before you begin, locate the PowerCenter/PowerMart product license key. Use the same
product license key to install the Informatica Server and Informatica Client tools.
Please read the release notes for any last minute changes to the Informatica Server installation
and connectivity issues.
Code Pages
For accurate data movement and transformation, you must make sure the code pages you
select in each component of PowerCenter and PowerMart are compatible with each other. For
more information, see Globalization Overview on page 29.
158
BadFiles
Cache
ExtProc
SessLogs
SrcFiles
Temp
TgtFiles
WorkflowLogs
All workflows configured to run on the registered Informatica Server use these directories by
default. For details, see Registering the Informatica Server on page 183.
159
2.
Set the library path to the absolute directory path where the Informatica Server is to be
installed for the following operating systems.
Table 9-1 describes the library paths for different UNIX operating systems:
Table 9-1. Library Path for Informatica Server on UNIX
3.
Operating System
Library Path
Solaris
LD_LIBRARY_PATH
AIX
LIBPATH
HP
SHLIB_PATH
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.
English
Japanese
If you are running one or more server processes, a message displays warning you that the
install or upgrade may cause problems.
160
6.
7.
8.
Enter the absolute target directory path where you want to install the Informatica Server.
9.
The installation program now extracts and installs the files. The upgrade preserves your
configuration settings.
10.
Type Y if you want to view the readme file, or N if you wish to read it later.
11.
12.
161
same name. The PM_HOME environment variable must point to the PowerMart
directory.
2.
162
Option
Required/
Optional
ServerName
Required
RepositoryName
Required
PMUser
Required
Description
Required/
Optional
PMPassword
Required
RepServerHostName
Required
RepServerPortNumber
Required
LogFileName
Optional
DataMovementMode
Required
ValidateDataCodePages
Required
SessionLogInUTF8
Required
MaxSessions
Required
LMSharedMem
Required
PMCacheDir
Optional
The default directory for caches and cache files. Use for
backward compatibility for mappings created in
PowerMart 3.5. For mappings created in later versions of
PowerCenter and PowerMart, use the server variable
$PMCacheDir. Configure $PMCacheDir when you
configure the Informatica Server in the Workflow
Manager.
Description
163
164
Option
Required/
Optional
PlatformKey
Required
OracleKey
Optional
SybaseKey
Optional
InformixKey
Optional
DB2Key
Optional
ODBCKey
Optional
TimeStampWorkflowLogMessages
Optional
FailSessionIfMaxSessionsReached
Optional
ExportSessionLogLibName
Optional
ErrorSeverityLevel
Optional
Description
Required/
Optional
DateHandling40Compatibility
Optional
PMServer3XCompatibility
Optional
AggregateTreatNullAsZero
Optional
AggregateTreatRowAsInsert
Optional
DateDisplayFormat
Required
LoadManagerAllowDebugging
Optional
CreateIndicatorFiles
Optional
Description
165
3.
166
Option
Required/
Optional
XMLWarnDupRows
Optional
MaxLookupSPDBConnections
Optional
MaxSybaseConnections
Optional
MaxMSSQLConnections
Optional
SybaseIQLocalToPmServer
Optional
NumOfDeadlockRetries
Optional
DeadlockSleep
Optional
Description
2.
3.
Set the PATH variable to include the directory where PowerCenter or PowerMart is
installed.
4.
Shared Library
Environment Variable
Solaris
LD_LIBRARY_PATH
AIX
LIBPATH
HP
SHLIB_PATH
C-shell
Bourne Shell
For example, if you have an Oracle source and Informix target and the Informatica Server
is installed on Solaris, you could set the shared library variables as follows:
Using a Bourne shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/pmserver_dir:$ORACLE_HOME/
lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql; export LD_LIBRARY_PATH
167
Using a C-shell:
$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
pmserver_dir:$ORACLE_HOME/lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql
5.
6.
For information on supported datatypes for each database see Datatype Reference in the
Designer Guide.
For information on connecting to a Teradata database, see the Supplemental Guide.
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.
Using a C-shell:
168
Set the TNS_ADMIN environment variable to the path for TNSNAMES. For example:
Using a Bourne Shell:
$ 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.
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)
(GLOBAL_NAMES = mydatabase.world)
7.
Launch SQL*Plus and try to connect to the database. If you fail to connect to the
database, verify that you correctly entered all of the connectivity information.
169
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 162.
2.
Using a C-shell:
$ setenv PATH ${PATH}:/usr/sybase/bin
3.
Using a C-shell:
$ setenv LD_LIBRARY_PATH $HOME/pmserver_dir:$SYBASE/lib
170
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.
6.
Configure the Informatica Server. Include the Sybase database key in the Informatica
Server configuration (pmconfig).
For details on configuring the Informatica Server, see Step 2. Configuring the
Informatica Server on UNIX on page 162.
2.
3.
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.
Using a C-shell:
$ setenv PATH ${PATH}:$INFORMIXDIR/bin
For example, for Solaris, set the LD_LIBRARY_PATH variable to the Informatica Server
installation directory. If you installed the Informatica Server in the $HOME/pmserver
directory, you could type:
Using a Bourne Shell:
171
$ 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
6.
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.
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
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
database, verify that you correctly entered all of the connectivity information.
11.
Configure the Informatica Server. Include the Informix database key in the Informatica
Server configuration utility (pmconfig).
For details on configuring the Informatica Server, see Step 2. Configuring the
Informatica Server on UNIX on page 162.
Install or verify that you have already installed IBM DB2 Client Application Enabler
(CAE), Version 6.1 or above.
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).
172
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
3.
/usr/lpp/db2_06_01
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
$ setenv INSTHOME
4.
db2admin
~db2admin
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
5.
To run IBM DB2 command line programs, the PATH environment variable should be
edited as follows:
$ setenv PATH
6.
$DB2DIR/lib:${LD_LIBRARY_PATH}
$DB2DIR/bin:${PATH}
Edit into your (.cshrc) the complete set of shell commands appropriate to your operating
system platform. Either log out and in again, or issue the command:
$ source .cshrc
7.
If you are configuring a new DB2 installation, you need to set up a remote database. Run
the DB2 Command Line Processor (db2) and issue the CATALOG <protocol> NODE
and CATALOG DATABASE commands to set up a remote database.
Consult the DB2 installation guide for details.
8.
Verify the name of your remote database. Run the DB2 Command Line Processor (db2)
and issue the LIST DATABASE DIRECTORY command for a list of available databases.
It is recommended that database entries for use with 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>
173
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.
For details on configuring the Informatica Server, see Step 2. Configuring the
Informatica Server on UNIX on page 162.
174
Verify that the repository database and Repository Server are running.
2.
3.
Workflow Manager
With the Workflow Manager, you can stop the Informatica Server. However, you must first
configure the Workflow Manager to communicate with the Informatica Server.
You can shut down the Informatica Server in the complete, stop, or abort mode. In the
complete mode, the Informatica Server allows currently running workflows to complete
before shutting down the Informatica Server. In the stop mode, the Informatica Server stops
Step 4. Starting and Stopping the Informatica Server on UNIX
175
the running workflows. In the abort mode, the Informatica Server aborts the running
workflows.
You must have the following privileges to shutdown:
Super User
Administer Server
2.
In the Navigator window, right-click on the Informatica Server and choose Shutdown
Server-Complete, Shutdown Server-Stop, or Shutdown Server-Abort from the menu.
The Workflow Manager executes the command. In the Output window, you should see
the following text:
{server_name} Shutdown Server: Request acknowledged
{server_name} Shutdown Server: Completed
pmcmd Program
The shutdownserver command stops the Informatica Server. You must have one of the
following privileges to use this command:
Administer Server
Super User
You can shut down the Informatica Server in the complete, stop, or abort mode. In the
complete mode, the Informatica Server allows currently running workflows to complete
before shutting down the Informatica Server. In the stop mode, the Informatica Server stops
the running workflows. In the abort mode, the Informatica Server aborts the running
workflows.
Use the following syntax to stop the Informatica Server:
pmcmd shutdownserver <-serveraddr|-s>[host:]portno <<-user|-u>
username|<-uservar|-uv> userEnvVar > <<-password|-p> password|<passwordvar|-pv> passwordEnvVar> <-complete|-stop|-abort>
For more details on using pmcmd, see Using pmcmd in the Workflow Administration Guide.
176
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.
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.
8.
Log on as the user where you run Informatica PowerCenter/PowerMart Server. Copy the
sample ODBC sources initialization file from the ODBC installation. For example:
cp /opt/odbc/odbc.ini
~/.odbc.ini
177
Copy and/or modify entries in .odbc.ini to create data sources based on the installed
ODBC drivers.
9.
You might want to retrieve a copy of the appropriate shared-library path helper. For
example:
cp /opt/odbc/odbc.csh ~/.odbc.csh
Configure the user .cshrc file to invoke this script at logon. The purpose is to modify the
appropriate OS-specific shared library path environment variable so that ODBC drivers
can be accessed. The path to these drivers (for example: /opt/odbc/lib) is added to:
LD_LIBRARY_PATH
(on Solaris)
SHLIB_PATH
(on HP-UX)
LIBPATH
(on AIX)
Note: These changes are not visible to Informatica Server until the Informatica Server is
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
3.
/usr/lpp/odbc
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
178
$ODBCHOME/lib:${LD_LIBRARY_PATH}
4.
To run the ivtestlib utility, the PATH environment variable should be altered as follows:
$ setenv PATH
5.
${ODBCHOME}/bin:${PATH}
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
179
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
180
[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.
9.
10.
For details on parameters in Data Source entries, see the example entries listed in the
unaltered .odbc.ini from $ODBCHOME. For more information, consult the Merant
ODBC for UNIX documentation.
11.
For each data source you use, make a note of the file named under the Driver= parameter
in the Data Source entry in.odbc.ini. Use the ivtestlib utility to verify that each driver file
can be loaded by the Merant ODBC for UNIX manager. For example, if you have an
entry Driver=/opt/odbc/lib/DWxxxx.so, issue the following command:
ivtestlib /opt/odbc/lib/DWxxxx.so
12.
Install and configure any underlying client access software needed by the ODBC driver.
Note: While some ODBC drivers are self-contained and have all information inside the
.odbc.ini file, most are not. An ODBC driver that, for example, accesses Oracle would
also need the Oracle SQL*NET software installed and appropriate environment variables
set. Such additional software configuration must be verified separately before using
ODBC.
13.
When you configure the Informatica Server, using the pmconfig utility, you must provide
an Informatica license key for ODBC. Sessions requiring ODBC access do not run
without this key.
For details on configuring the Informatica Server, see Step 2. Configuring the
Informatica Server on UNIX on page 162.
181
182
Chapter 10
Registering the
Informatica Server
This chapter includes the following topics:
Overview, 184
183
Overview
After you install and configure the Informatica Client and the Informatica Server, you can
register the Informatica Server with the repository that you indicated in the Informatica
Server Configuration. You must register the Informatica Server before you can start it.
Register Informatica Servers in the Workflow Manager. The Workflow Manager is the
Informatica Client tool that you use to create and run workflows that extract, transform, and
load data.
You can register and run multiple PowerCenter Servers against a local or global repository.
You can register and run only one PowerMart Server in a local repository. You cannot register
a PowerMart Server in a global repository. When you start a PowerMart Server, it verifies that
it is the only Informatica Server registered in the repository. It does not start if there are other
Informatica Servers registered in the repository. For details on local and global repositories,
see Managing the Repository in the Repository Guide.
You can perform the following registration tasks for an Informatica Server:
Register an Informatica Server. When you register an Informatica Server, you specify
information such as the code page and directories for workflow and session output. This
information is stored in the repository.
Register multiple Informatica Servers. When you register multiple Informatica Servers,
choose the Informatica Server for a workflow in the workflow properties.
Edit an Informatica Server. When you edit an Informatica Server, all workflows using that
Informatica Server use the updated server connection information, including the updated
code page settings. You do not need to restart the Workflow Manager to use the updated
information.
Delete an Informatica Server. When you delete an Informatica Server, assign another
Informatica Server for the workflows using the deleted server. To assign an Informatica
Server to a workflow, choose Connections-Assign Server in the Workflow Manager.
To register an Informatica Server, you must have one of the following privileges:
Administer Server
Super User
You can also configure the following information in the Workflow Manager to run workflows:
184
Create database connections for source, target, lookup transformations, and stored
procedures. For details on database connections, see Configuring the Workflow Manager
in the Workflow Administration Guide.
Define the FTP connections if you plan to use FTP to access source or target machines.
For details on FTP connections, see Using FTP in the Workflow Administration Guide.
Configure External Loader connections if you plan to use an external loader to load the
target database. For details on External Loader connections, see External Loading in the
Workflow Administration Guide.
Code page identifying the character set associated with the Informatica Server.
Directories and parameters you want the Informatica Server to use for workflow files and
caches.
Server Variables
You can define server variables for each Informatica Server you register. Server variables define
the path and directories for session and workflow output files and caches. You can also use
server variables to define workflow properties, such as the number of workflow logs to
archive.
The installation process creates default directories in the location where you install the
Informatica Server. By default, the Informatica Server writes output files in these directories
when you run a workflow. To use these directories as the default location for the session and
185
workflow output files, you must configure the server variable $PMRootDir to define the path
to the directories.
Sessions and workflows are configured to use server directories by default. You can override
the default by entering different directories session or workflow properties.
For example, you might have an Informatica Server running all workflows in a repository. If
you define the server variable for workflow logs directory as c:\pmserver\workflowlog, the
Informatica Server saves the workflow log for each workflow in c:\pmserver\workflowlog by
default.
If you change the default server directories, make sure the designated directories exist before
running a workflow. If the Informatica Server cannot resolve a directory during the workflow,
it cannot run the workflow.
By using server variables instead of hard-coding directories and parameters, you simplify the
process of changing the Informatica Server that runs a workflow. If each workflow in a
development folder uses server variables, then when you copy the folder to a production
repository, the production server can run the workflow as configured. When the production
server runs the workflow, it uses the directories configured for its server variables. If, instead,
you changed workflow to use hard-coded directories, workflows fail if those directories do not
exist on the production server.
Table 7-1 lists the server variables you configure when you register an Informatica Server:
Table 7-1. Server Variables
186
Server Variable
Required/
Optional
$PMRootDir
Required
$PMSessionLogDir
Required
$PMBadFileDir
Required
$PMCacheDir
Required
Default directory for the lookup cache, index and data caches, and
index and data files. To avoid performance problems, always use a
drive local to the Informatica Server for the cache directory. Do not
use a mapped or mounted drive for cache files. Defaults to
$PMRootDir/Cache.
$PMTargetFileDir
Required
$PMSourceFileDir
Required
$PMExtProcDir
Required
$PMTempDir
Required
$PMSuccessEmailUser
Optional
Description
Required/
Optional
$PMFailureEmailUser
Optional
$PMSessionLogCount
Optional
$PMSessionErrorThreshold
Optional
$PMWorkflowLogDir
Required
$PMWorkflowLogCount
Optional
Description
Windows. Enter a path beginning with a drive letter, colon, backslash, as follows:
C:\InformaticaServer\bin
Note: If you enter a delimiter inappropriate to the Informatica Server platform (for example,
using a backslash for a UNIX server), the Workflow Manager corrects the delimiter.
Registering the Informatica Server
187
Changing Servers
If you change Informatica Servers, the new Informatica Server can run workflows using its
server variables. To ensure a workflow successfully completes, relocate any necessary file
sources, targets, or incremental aggregation files to the default directories of the new
Informatica Server.
If you do not use server variables in an individual session or workflow, you may need to
manually edit the session or workflow properties when you change the Informatica Server. If
the new Informatica Server cannot locate the override directory, it cannot execute the session.
For example, you might override the workflow log directory in the workflow properties, by
entering d:\data\workflowlog. You then copy the folder containing the workflow to a
production repository. The workflow log directory of the new Informatica Server is
c:\pmserver\workflowlog. When the new Informatica Server tries to run the copied workflow,
it cannot find the directory listed in the workflow properties, so it fails to initialize the
workflow. To correct the problem, you must either edit the workflow properties or create the
specified directory on the new Informatica Server.
2.
Choose Connections-Server.
The Server Object Browser dialog box appears.
3.
188
4.
5.
6.
If you do not know the IP address, enter the host name and use the Resolve Server button
to resolve your IP address. You can also enter the IP address in the Host Name/IP Address
field and use the Resolve SErver button to resolve the hostname.
The Workflow Manager also resolves the host name and IP address when you click OK.
Table 10-1 describes the settings required to register an Informatica Server using TCP/IP:
Table 10-1. TCP/IP Settings to Register a Server
TCP/IP Option
Required/
Optional
Server Name
Required
Host Name or IP
address
Required
Resolved IP Address
n/a (read-only)
Port Number
Required
Port number the Informatica Server uses. Must be the same port
listed in the Informatica Server configuration parameters.
Description
189
7.
TCP/IP Option
Required/
Optional
Timeout
Required
Code Page
Required
Description
For $PMRootDir, enter a valid root directory for the Informatica Server platform.
Informatica recommends using the Informatica Server installation directory as the
recommended root directory because the Informatica Server installation creates the
default server directories in the Server installation directory. If you enter a different root
directory, make sure to create the necessary directories.
8.
9.
Click OK.
The new Informatica Server appears in the Navigator below the repository.
190
Chapter 11
Upgrading a Repository
191
Overview
Please see Upgrading a Repository in the Supplemental Guide for information on the
following topics:
Upgrading a repository
Preparing to upgrade
192
Chapter 12
Using ODBC
This chapter includes the following topics:
Overview, 194
Troubleshooting, 206
193
Overview
Open Database Connectivity (ODBC) provides a common way to communicate with several
different database platforms.
ODBC consists of three distinct components:
1.
ODBC drivers. Process ODBC calls, submit SQL requests to data sources, and return
results. The drivers must connect to the client libraries to access the databases. They
communicate with data sources.
2.
ODBC Driver Manager. Loads and calls one or more ODBC drivers to open and close
communications to databases.
3.
ODBC Administrator. The visible part of the ODBC Driver Manager, launched from
the Control Panel in Windows 98 and Windows. Use the ODBC Administrator to create,
modify, and delete ODBC data sources.
ODBC components
Driver Manager
ODBC Driver
for Sybase
194
ODBC Driver
for Oracle
Sybase
Database
Oracle
Database
195
Connects to
Required Information
Designer
Source or Target
Informatica Server
Source or Target
The Designer accesses the ODBC Administrator settings to connect to data sources.
The Informatica Server on Windows or UNIX can connect to ODBC data sources to access
source and target data. On Windows, you connect to databases using the data sources
configured in the ODBC Administrator. On UNIX, you set ODBC environment variables for
data sources. The connect string is the database data source name in square brackets in the
odbc.ini file. For an example of an odbc.ini file and connect string information, see
Installing and Configuring ODBC for UNIX on page 177.
196
ODBC Driver
IBM DB2
Informix
Microsoft Access97
Microsoft Excel
Oracle
Sybase
Teradata
If you have problems connecting to a database other than one of the supported source or
target databases, contact the ODBC driver vendor regarding function calls supported by the
driver. For a list of function calls, see ODBC Calls on page 198.
PowerCenter 6.0 and PowerMart 6.0 support the Merant 3.7 32-bit closed ODBC drivers
supplied with the installation CD. You can have only one version of the Merant drivers on the
system. Therefore, you need to install the drivers included on the Informatica installation CD
to ensure that you have the most recent version of these drivers. The Merant 3.7 32-bit
ODBC closed drivers are fully backward compatible. If you have any questions, contact
Merant.
197
ODBC Calls
The Informatica Client and Server make the following function calls to connect to supported
ODBC drivers.
198
Function
Description
SQLAllocConnect
SQLAllocStmt
SQLBindCol
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
SQLDisconnect
Disconnects.
SQLError
Errors.
SQLExecDirect
Executes a statement.
SQLExecute
Executes a statement.
SQLFetch
SQLForeignKeys
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 above. This is called twice:
- With the FROM table as NULL
- With the TO table as NULL
SQLFreeConnect
SQLFreeStmt
Description
SQLGetFunctions
SQLNumResultsCols
SQLPrepare
SQLPrimaryKeys
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.
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
SQLSetConnectOption
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
Description
SQLAllocConnect
SQLAllocStmt
ODBC Calls
199
200
Function
Description
SQLBindCol
SQLBindParam
Binds a parameter.
SQLConnect
Connects.
SQLDisconnect
Disconnects.
SQLError
Errors.
SQLExecute
Executes a statement.
SQLFetch
SQLFreeConnect
SQLFreeStmt
SQLPrepare
SQLSetConnectOption
SQLSetParam
Sets a parameter.
SQLTransact
SQLSetStmtOption
Sets the options for a statement to control how to read and how many rows to read.
SQLExtendedFetch
Fetches arrays.
SQLGetInfo
SQLGetFunctions
SQLGetStmtOptions
SQLRowCount
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.
Use the ODBC Data Source Administrator to create and configure ODBC data sources.
To create an ODBC data source:
1.
2.
3.
Click Add.
A dialog box displays all the installed ODBC drivers on the system.
4.
Select the ODBC driver you want to use and click Finish.
The configuration dialog box for that ODBC driver appears.
5.
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.
201
7.
For more information on Microsoft Excel sources, refer to the article in the Informatica
Webzine. You can access the webzine at http://my.Informatica.com.
202
Figure 12-3 shows the ODBC Sybase Driver Setup dialog box:
Figure 12-3. ODBC Sybase Driver Setup
If you have difficulty clearing the temporary stored procedures for prepared SQL statements
options, see the Informatica Webzine for more information about configuring Microsoft SQL
Server. You can access the webzine at http://my.Informatica.com.
Creating an ODBC Data Source
203
2.
204
3.
4.
Click OK to close the ODBC driver configuration dialog box, then click Close to close
the ODBC Administrator.
2.
3.
205
Troubleshooting
I get one or both of the following errors when I try to create an ODBC DSN in the ODBC
Data Source Administrator.
The setup routines for <driver name> ODBC driver could not be loaded due
to System error code 126.
Could not load the setup or translator library.
Check that you have installed the client, such as Oracle Client for Oracle database. Then
configure the ODBC DSN. You need to set up the client environment before creating an
ODBC DSN.
I get the following error when I attempt to run a workflow using an Informix ODBC DSN
as my source and target.
CMN_1046 ODBC Error
CMN_1046 [Merant][ODBC Informix driver][Informix]Attempt to connect to
database server (INFOOnline) failed.]
You have created an ODBC DSN, but no longer have the underlying native connectivity
software or environment. You need to reconfigure the native connectivity environment and
then run the workflow.
206
Appendix A
Code Pages
This appendix documents code pages and their compatibility in PowerCenter and PowerMart.
Topics include:
207
Code Pages
PowerCenter and PowerMart support code pages for internationalization.
Table A-1 displays available code pages, including the code page name, description, and code
page ID:
Table A-1. Code Page Descriptions
208
Name
Description
ID
EuroShift-JIS
9999
IBM037
2028
IBM273
2030
IBM280
2035
IBM285
2038
IBM297
2040
IBM500
2044
IBM930
930
IBM935
935
IBM937
937
ISO-8859-10
13
ISO-8859-15
201
ISO-8859-2
ISO-8859-3
ISO-8859-4
ISO-8859-5
ISO-8859-6
ISO-8859-7
10
ISO-8859-8
11
ISO-8859-9
12
JapanEUC*
18
Latin1*
MS1250
2250
MS1251
2251
MS1252*
2252
MS1253
MS Windows Greek
2253
Description
ID
MS1254
2254
MS1255
MS Windows Hebrew
2255
MS1256
MS Windows Arabic
2256
MS1257
2257
MS1258
MS Windows Vietnamese
2258
MS1361
1361
MS874
874
MS932*
2024
MS936
936
MS949
949
MS950
950
US-ASCII*
7-bit ASCII
UTF-8
106
Note: Select IBM EBCDIC as your source database connection code page only if you access
Code Pages
209
210
Language
Territory
Code Page
Sort Order
Albanian
Albania
ISO-8859-2
MS1250
Latin1
MS1252
ISO-8859-9
UTF-8
Default
Binary
Arabic
Saudi Arabia
ISO-8859-6
MS1256
UTF-8
Default
Binary
Belorussian
Belarus
ISO-8859-5
MS1251
UTF-8
Default
Binary
Bulgarian
Bulgaria
ISO-8859-5
MS1251
UTF-8
Default
Binary
Canadian French
French-Canada
Latin1
MS1252
ISO-8859-9
UTF-8
IBM297
Default
Binary
Catalan
Catalonia
Latin1
MS1252
ISO-8859-9
UTF-8
Default
Binary
Croatian
Croatia
ISO-8859-2
MS1250
UTF-8
Croatian
Binary
Cyrillic Serbian
Yugoslavia
ISO-8859-5
MS1251
UTF-8
Default
Binary
Czech
Czech Republic
ISO-8859-2
MS1250
UTF-8
Czech
Binary
Territory
Code Page
Sort Order
Danish
Denmark
Latin1
MS1252
ISO-8859-9
UTF-8
Danish
Binary
Dutch
Netherlands
Dutch-Belgium
Latin1
MS1252
ISO-8859-9
UTF-8
IBM037
Default
Binary
English
United States
Australia
Canada
New Zealand
South Africa
United Kingdom
US-ASCII
Latin1
MS1252
UTF-8
IBM037
IBM285
Binary
Default
Estonian
Estonia
ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Estonian
Binary
Farsi
Iran
ISO-8859-6
UTF-8
Default
Binary
Finnish
Finland
Latin1
MS1252
ISO-8859-9
UTF-8
Finnish
Binary
French
France
French-Belgium
French-Canada
French-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM297
Default
Binary
German
Germany
Austria
German-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM273
Default
Binary
Greek
Greece
ISO-8859-7
MS1253
UTF-8
Default
Binary
Hebrew
Israel
ISO-8859-8
MS1255
UTF-8
Default
Binary
Hungarian
Hungary
ISO-8859-2
MS1250
UTF-8
Hungarian
Binary
211
212
Language
Territory
Code Page
Sort Order
Italian
Italy
Italian-Switzerland
Latin1
MS1252
ISO-8859-9
UTF-8
IBM280
Default
Binary
Japanese
Japan
JapanEUC
MS932
UTF-8
IBM930
Binary
Korean
Korea
MS949
MS1361
UTF-8
Binary
Latvian
Latvia
ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Latvian
Binary
Lithuanian
Lithuania
ISO-8859-4
ISO-8859-10
MS1257
UTF-8
Lithuanian
Binary
Macedonian
Macedonia
ISO-8859-5
MS1251
UTF-8
Default
Binary
Norwegian
Norway
Latin1
MS1252
ISO-8859-9
UTF-8
Danish
Binary
Portuguese
Portugal
Brazil
Latin1
MS1252
ISO-8859-9
UTF-8
IBM037
Default
Binary
Romanian
Romania
ISO-8859-2
MS1250
UTF-8
Romanian
Binary
Russian
Russia
ISO-8859-5
MS1251
UTF-8
Default
Binary
Serbian
Yugoslavia
ISO-8859-2
MS1250
UTF-8
Default
Binary
Simplified Chinese
China
MS936
UTF-8
IBM935
Binary
Territory
Code Page
Sort Order
Slovak
Slovakia
ISO-8859-2
MS1250
UTF-8
Slovak
Slovenian
Slovenia
ISO-8859-2
MS1250
UTF-8
Slovenian
Binary
Spanish
Spain
Argentina
Chile
Mexico
Latin1
MS1252
ISO-8859-9
UTF-8
Spanish
Traditional Spanish
Binary
Swedish
Sweden
Latin1
MS1252
ISO-8859-9
UTF-8
Swedish
Binary
Thai
Thailand
MS874
UTF-8
Thai
Binary
Turkish
Turkey
ISO-8859-9
ISO-8859-3
MS1254
UTF-8
Turkish
Binary
Ukrainian
Ukraine
ISO-8859-5
MS1251
UTF-8
Ukrainian
Binary
Vietnamese
Vietnam
MS1258
UTF-8
Vietnamese
Binary
213
Table A-3 summarizes code page compatibility between PowerCenter and PowerMart
components:
Table A-3. Code Page Compatibility
214
Subset of target.
Subset of Informatica Server.
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
Local Repository
Standalone Repository
Informatica Client
pmcmd
For details on code page compatibility between components, see Globalization Overview on
page 29.
215
Compatible with
Latin1 (ISO-8859-1)*
MS1252 MS Latin1
Latin1 (ISO-8859-1)*
MS1252 MS Latin1
Latin1 (ISO-8859-1)
IBM037 IBM EBCDIC US English
JapanEUC
Japan EUC
MS932 MS Shift JIS
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:
216
IBM037 (itself )
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
Subsets
Supersets
217
218
Subsets
Supersets
Subsets
Supersets
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
IBM930 (IBM EBCDIC
Japanese)
JEF (Japanese EBCDIC
Fujitsu)
JIPSE (NEC ACOS JIPSE
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
IBM930 (IBM EBCDIC
Japanese)
JEF (Japanese EBCDIC
Fujitsu)
JIPSE (NEC ACOS JIPSE
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
UNISYS (UNISYS
Japanese)
US-ASCII (7-bit ASCII)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
IBM930 (IBM EBCDIC
Japanese)
JEF (Japanese EBCDIC
Fujitsu)
JIPSE (NEC ACOS JIPSE
Japanese)
KEIS (HITACHI KEIS
Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
UNISYS (UNISYS
Japanese)
UTF-8 (UTF-8 encoding of
Unicode)
219
220
Subsets
Supersets
MELCOM (MITSUBISHI
MELCOM Japanese)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
US-ASCII (7-bit ASCII)
MELCOM (MITSUBISHI
MELCOM Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
Subsets
Supersets
221
222
Subsets
Supersets
UNISYS (UNISYS
Japanese)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
US-ASCII (7-bit ASCII)
UNISYS (UNISYS
Japanese)
JapanEUC (Japanese
Extended UNIX Code
(including JIS X 0212))
MS932 (MS Windows
Japanese, superset of
Shift-JIS)
Subsets
Supersets
223
Subsets
Supersets
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.
224
8224 (DAGGER)
8226 (BULLET)
225
8224 (DAGGER)
8226 (BULLET)
226
227
228
229
230
175 (MACRON)
184 (CEDILLA)
231
232
711 (CARON)
728 (BREVE)
731 (OGONEK)
233
234
235
8254 (OVERLINE)
236
175 (MACRON)
184 (CEDILLA)
237
238
711 (CARON)
728 (BREVE)
731 (OGONEK)
239
240
241
8254 (OVERLINE)
242
243
244
Index
Access97
See Microsoft Access97
Aggregate treat nulls as zero
setting on UNIX 165
setting on Windows 136
Aggregate treat rows as insert
setting on UNIX 165
setting on Windows 136
Aggregator transformation
setting up for prior version compatibility 136, 165
treating nulls as zero 136, 165
treating rows as insert 136, 165
AIX
shared library environment variable 105, 167
ANSI code page (Windows)
definition 37
Application sources
code page 42
Application targets
code page 42
ASCII
8-bit ASCII 33
See also Unicode mode
overview 33
setting ASCII data movement mode on UNIX 163
setting ASCII data movement mode on Windows 138
C
Character data sets
See also Designer Guide
handling options for Microsoft SQL Server and
PeopleSoft on Oracle 137
character sizes
double byte 38
multibyte 38
single byte 38
client tools
See Informatica Client
COBOL
connectivity 24
code page relaxation
configuring the Informatica Server 48
Informatica Server validation 48
code pages
advanced external procedure 41
ANSI (Windows) 37
Application sources 42, 214
Application targets 42
character loss during conversions 224
245
choosing 38
compatibility 216
compatibility between components 215
compatibility diagram 43
compatibility overview 38
configuring UNIX Server 158
configuring Windows Server 126
converting from IBM EBCDIC Japanese to JapanEUC
235
converting from IBM EBCDIC Japanese to MS Shift
JIS 241
converting from IBM EBCDIC US English to Latin1
226
converting from JapanEUC to IBM EBCDIC Japanese
236
converting from JapanEUC to MS Shift JIS 230
converting from Latin1 to IBM EBCDIC US English
227
converting from Latin1 to MS Latin1 225
converting from MS Latin1 to Latin1 225
converting from MS Shift JIS to IBM EBCDIC
Japanese 242
converting from MS Shift JIS to JapanEUC 227
external procedure 41
flat file sources 40, 42, 214
flat file targets 40, 42, 214
global repository 214
Informatica Client 40, 215
Informatica Server 40, 41, 185, 214
list of available code pages 208
local repository 214
lookup database 41
OEM code page (Windows) 37
overview 36
pmcmd 41, 215
reference 210
related languages 210
related sort orders 210
related territories 210
relational sources 40, 42, 214
relational targets 40, 42, 214
relaxed validation for sources and targets 48
repository 40, 42, 215
sort order overview 41
stored procedure database 41
subsets defined 214
supersets defined 214
supported code pages 208
UNIX 36
verifying compatibility 217
Windows 37
246
Index
compatibility
between code pages 38, 216
configuring
Informatica Server (UNIX) 162
Informatica Server (Windows) 131
ODBC data sources 204
connect string
examples 23
syntax 23
connecting
Informatica Client to IBM DB2 74
Informatica Client to Informix 72, 76, 147
Informatica Client to Microsoft Access97 75
Informatica Client to Microsoft Excel 75
Informatica Client to Microsoft SQL Server 70
Informatica Client to Oracle 69
Informatica Client to Sybase SQL Server 71
Informatica Client to Teradata 76
Informatica Server to IBM DB2 (UNIX) 172
Informatica Server to IBM DB2 (Windows) 144
Informatica Server to Informix (UNIX) 171
Informatica Server to Informix (Windows) 143
Informatica Server to Microsoft Access97 145
Informatica Server to Microsoft Excel 146
Informatica Server to Microsoft SQL Server 141
Informatica Server to ODBC data sources (UNIX) 178
Informatica Server to Oracle (UNIX) 168
Informatica Server to Oracle (Windows) 140
Informatica Server to Sybase SQL Server (UNIX) 170
Informatica Server to Sybase SQL Server (Windows)
142
Informatica Server to Teradata 147
Repository Server to IBM DB2 (UNIX) 110
Repository Server to IBM DB2 (Windows) 89
Repository Server to Informix (UNIX) 109
Repository Server to Informix (Windows) 87
Repository Server to Microsoft SQL Server 86
Repository Server to Oracle (UNIX) 106
Repository Server to Oracle (Windows) 85
Repository Server to Sybase SQL Server (Windows) 87
to UNIX databases 167
to Windows databases 140
connections
TCP/IP 185
connectivity
COBOL 24
connect string examples 23
diagram of 21
Informatica Client 21
native drivers 23
overview 5, 21
conversions
IBM EBCDIC Japanese to JapanEUC code pages 235
IBM EBCDIC Japanese to MS Shift JIS code pages
241
IBM EBCDIC US English to Latin1 code pages 226
JapanEUC to IBM EBCDIC Japanese code pages 236
JapanEUC to MS Shift JIS code pages 230
Latin1 to IBM EBCDIC US English code pages 227
Latin1 to MS Latin1 code pages 225
MS Latin1 to Latin1 code pages 225
MS Shift JIS to IBM EBCDIC Japanese code pages
242
MS Shift JIS to JapanEUC code pages 227
Create Indicator Files
setting on UNIX 165
setting on Windows 139
creating
ODBC data sources 201
repositories 117
D
data movement mode
changing 34
setting on UNIX 163
setting on Windows 138
databases
connecting to (UNIX) 167
connecting to (Windows) 140
connecting to IBM DB2 74, 89, 110, 144, 172
connecting to Informix 72, 87, 109, 143, 171
connecting to Microsoft Access97 75, 145
connecting to Microsoft Excel 75, 146
connecting to Microsoft SQL Server 70, 86, 141
connecting to Oracle 69, 85, 106, 140, 168
connecting to Sybase SQL Server 71, 87, 108, 142, 170
connecting to Teradata 76, 147
connectivity overview 184
source code page 40
target code page 40
Date Display Format
setting on UNIX 165
setting on Windows 139
Date Handling 4.0 Compatibility
setting on UNIX 165
setting on Windows 137
dates
setting up prior version compatibility (UNIX) 165
setting up prior version compatibility (Windows) 136
DB2
See IBM DB2
DB2 Key
See also IBM DB2
setting on UNIX 164
setting on Windows 133
DB2CODEPAGE
configuring DB2 74
DB2INSTANCE
configuring DB2 74
deadlock retries
setting number of (UNIX) 166
setting number of (Windows) 137
Deadlock Sleep Before Retry
setting on UNIX 166
setting on Windows 137
Debugger
Instance Data window 11
Target Data window 11
Designer
installing 67
Instance Data window 11
Mapping Designer 10
Mapplet Designer 10
Navigator 11
output window 11
overview window 11
Source Analyzer 10
status bar 11
Target Data window 11
Transformation Developer 10
Warehouse Designer 10
workspace 11
DHCP (Dynamic Host Configuration Protocol)
avoiding use with Informatica Server 126, 158
directories
data cache 187
indexes 187
Informatica Server 127, 158
root 187
server defaults 185
server variables 185
documentation
conventions xxiv
description xxi
online xxiii, 67
DSN (data source name)
ODBC data sources
Index
247
environment variables
DB2CODEPAGE 74
DB2INSTANCE 74
LANG_C 36
LC_ALL 36
LC_CTYPE 36
LD_LIBRARY_PATH 105, 167
LIBPATH 105, 167
NLS_LANG 59
PM_HOME 162
SHLIB_PATH 105, 160, 167
Error Severity Level
setting on UNIX 164
event logs
filename for 163
Excel
See Microsoft Excel
Export Session Log Lib Name
setting on UNIX 164
setting on Windows 139
external procedures
See also Designer Guide
directory for 127, 158
HP/UX
shared library environment variable 105, 160, 167
F
FailSessionIfMaxSessionsReached
setting on UNIX 164
setting on Windows 134
flat files
connectivity 24
directory for targets 128, 159
source code page 40, 42, 214
target code page 40, 42, 214
G
global repositories
code page 214
creating 121
definition 3, 116
promoting 121
globalization
overview 30
248
Index
I
IBM DB2
Client Configuration Assistant program 74, 89, 145
connect string example 23
connecting to Informatica Client 74
connecting to Informatica Server (UNIX) 172
connecting to Informatica Server (Windows) 144
connecting to Repository Server (UNIX) 110
connecting to Repository Server (Windows) 89
ODBC driver 65
ODBC issues 197
platform key 133, 164
setting DB2CODEPAGE 74, 89, 145
setting DB2INSTANCE 74, 89, 144
indicator files
configuring Informatica Server to create (Windows)
139
Informatica
documentation xxi
Webzine xxv
Informatica Client
See also Informatica Server
code page 40, 215
connecting to databases 69
connectivity requirements 21
installing 67
system requirements 20
Informatica repository
connectivity requirements 22
Informatica Server
See also Informatica Client
automatically starting (Windows) 150
changing servers 188
code page 40, 41, 185, 214
configuring (UNIX) 162
configuring (Windows) 131
configuring error severity level (UNIX) 164
configuring export session log lib name (UNIX) 164
configuring fail session if max sessions reached (UNIX)
164
configuring log file name (UNIX) 163
configuring Repository Server host name (UNIX) 163
configuring server name (UNIX) 162
configuring UNIX Server 158
Instance Data
window 11
ISO 8859-1
definition 33
K
keys
required to run Informatica Server 132
L
LANG_C environment variable
setting locale in UNIX 36
language
code page reference 210
LC_ALL environment variable
setting locale in UNIX 36
LC_CTYPE environment variable
setting locale in UNIX 36
LD_LIBRARY_PATH
overview 105, 167
LIBPATH 105, 167
Load Manager
Load Manager Allow Debugging (UNIX) 163
Load Manager Shared Memory (UNIX) 163
local repositories
code page 214
definition 3, 116
promoting to global 121
registering multiple servers 184
locales
overview 32
LogFileName
setting on UNIX 163
Lookup databases
setting maximum number of connections (Windows)
137
M
mappings
See also Designer Guide
description 9
process 10
mapplets
description 9
Max Lookup/SP DB Connections
setting on UNIX 166
Index
249
250
Index
N
native connect string
See connect string
Navigator
overview 11
NLS_LANG
setting locale 59
Number of Deadlock Retries
setting on UNIX 166
setting on Windows 137
O
ODBC
connecting to databases in Informatica Server 196
ODBC (Open Database Connectivity)
See also ODBC calls
See also ODBC data sources
connecting to databases in Informatica Client 196
database-specific notes 197
definition 65
diagram of 194
drivers description 194
drivers for Microsoft Excel 146
installing drivers on Informatica Client 65
installing on Informatica Server (UNIX) 177
Merant driver issues 65, 197
overview 194
platform key 133, 164
requirement for Informatica Client 22
support for MS Excel-compatible drivers 75
uninstalling Merant drivers 66
ODBC Administrator
description 194
ODBC calls
Informatica Client 198
Informatica Server 199
overview 198
ODBC data sources
configuring 204
connecting to (UNIX) 178
creating 201
deleting 205
overview 195
System 195
troubleshooting 206
User 195
ODBC Driver Manager
description 194
ODBC Key
setting on Windows 133
OEM code page (Windows)
definition 37
online help
Informatica Client 67
Oracle
changing locale using NLS_LANG 70, 86, 108
connect string syntax 23
connecting to Informatica Client 69
connecting to Informatica Server (UNIX) 168
connecting to Informatica Server (Windows) 140
connecting to Repository Server (Windows) 85
displaying non-ASCII characters 70, 78, 86, 108
installing Merant ODBC drivers 65
ODBC driver 65
platform key 164
platform key (Windows) 132
setting locale with NLS_LANG 59
tips 123
Oracle Key
setting on UNIX 164
setting on Windows 132
Oracle Net Services
using to connect Informatica Client to Oracle 69
using to connect Informatica Server to Oracle (NT)
140
using to connect Informatica Server to Oracle (UNIX)
168
using to connect Repository Server to Oracle (NT) 85
using to connect Repository Server to Oracle (UNIX)
106
P
password
entering repository (UNIX) 163
entering repository (Windows) 135
PeopleSoft on Oracle
setting Char handling options 137
Platform Key
setting on UNIX 164
setting on Windows 132
PM Cache Directory
setting on Unix 163
PM Password
setting on UNIX 163
PM Server 3.X aggregate compatibility
setting on UNIX 165
setting on Windows 136
PM User
setting on UNIX 162
PM_HOME
configuring on UNIX 162
pmcmd command line program
code page issues 41, 215
communicating with the Informatica Server 41
pmconfig program
using 162
PmNullPasswd
reserved word 196
PmNullUser
reserved word 196
pmrep
See Repository Guide
PMServer 4.0 date handling compatibility
setting on UNIX 165
setting on Windows 137
pmserver command
starting server (UNIX) 175
pmserver.cfg
file 162
post-session
email option for Windows 139
PowerCenter
connectivity 21
installation steps 25
minimum system requirements 20
upgrading steps 26
PowerMart
connectivity 21
installation steps 25
minimum system requirements 20
upgrading steps 26
primary domain controller
Informatica Server installation guidelines 127
privileges
registering Informatica Server 184
R
registering
Informatica Server 185, 187, 188
multiple servers on local repository 184
release notes
installing 67
repositories
changing a code page 117
code page 40, 42, 215
connectivity 21
Index
251
creating 117
entering name for Informatica Server (UNIX) 162
entering name for Informatica Server (Windows) 135
global 116
local 116
open architecture 116
overview 116
restricted characters for repository name 117
size requirements 20, 26
standalone 116
system requirements 20
tips 123
types of 116
Repository Manager
installing 67
Repository Name
setting on UNIX 162
setting on Windows 135
repository objects
overview 9
Repository Password
setting on UNIX 163
setting on Windows 135
Repository Server
configuration (UNIX) 103
configuration (Windows) 83
connecting to Oracle (UNIX) 106
connectivity requirements 22
installation (UNIX) 101
installation (Windows) 82
setting Administrative Password (Windows) 83
setting AdminPasswd (UNIX) 103
setting Backup Directory (Windows) 84
setting BackupDir (UNIX) 103
setting ConfigDir (UNIX) 103
setting Configuration Directory (Windows) 84
setting ErrorSeverityLevel (UNIX) 104
setting LogFileName (UNIX) 104
setting Maximum Port Number (Windows) 84
setting Minimum Port Number (Windows) 84
setting Output to Event Log (Windows) 84
setting Output to File (Windows) 84
setting RaMaxPort (UNIX) 103
setting RaMinPort (UNIX) 103
setting Server Port Number (Windows) 83
setting ServerPort (UNIX) 103
setting Severity Level (Windows) 84
starting (Windows) 91
starting on UNIX 112
stopping from Repository Manager 94
stopping from the Repository Manager 113
252
Index
S
schemas
description 9
server
See Informatica Server
See also database-specific server
Server Name
setting on UNIX 162
setting on Windows 133
server variables
description 185
directories on Windows 127, 158
list 186
session log 185
Session Log in UTF8
setting on UNIX 163
setting on Windows 138
session logs
directory for 127, 158
server variable for 185
sessions
description 9
setting maximum (UNIX) 163
sort order 41
SHLIB_PATH
overview 105, 167
Solaris
shared library environment variable 105, 160, 167
sort order
code page 41
code page reference 210
Source Analyzer
Designer 10
source databases
code page 40, 42, 214
connecting through ODBC (UNIX) 178
connectivity 21
source definitions
See Designer Guide
description 9
sources
supported 2
SQL scripts
installing 67
standalone repositories
description 116
starting
Informatica Server (UNIX) 175
Informatica Server (Windows) 148
Informatica Server automatically (Windows) 150
stopping
Informatica Server (Windows) 150
Stored Procedure databases
setting number of connections (Windows) 137
subset
defined for code page compatibility 39
superset
defined for code page compatibility 38
Sybase
ODBC driver 65
Sybase Key
setting on UNIX 164
setting on Windows 132
Sybase SQL Server
connect string example 23
connecting to Informatica Client 71
connecting to Informatica Server (UNIX) 170
connecting to Informatica Server (Windows) 142
connecting to Repository Server (Windows) 87
installing Merant ODBC drivers 65
ODBC issues 72, 197
platform key (UNIX) 164
platform key (Windows) 132
setting key on 132
setting maximum connections (Windows) 137
SybaseIQLocaltoPmServer
setting on UNIX 166
system locales
definition 32
system requirements
minimum installation requirements 20
T
Target Data
window 11
target databases
code page 40, 42, 214
connecting through ODBC (UNIX) 178
connectivity 21
target definitions
See Designer Guide
description 9
targets
supported 3
TCP/IP Host Address
setting on Windows 133
TCP/IP network protocol
configuration restrictions 158
connection requirement 185
host address 133
requirement for Informatica Server 22
server settings 189
temporary files
directory for 128, 159
Teradata
connecting to Informatica Client 76
connecting to Informatica Server 147
ODBC driver 65
territory
code page reference 210
testing
date display formats 139
Time Stamp Workflow Log
setting on Windows 134
Transformation Developer
Designer 10
Treat Char as Char on read (Microsoft SQL Server and
PeopleSoft on Oracle)
setting on Windows 137
troubleshooting
installation (Windows) 152
ODBC data sources 206
tutorials
See also Getting Started
installing 67
U
Unicode mode
See also ASCII
overview 33
Index
253
XMLWarnDupRows
setting on UNIX 166
W
Warehouse Designer
Designer 10
Warn about duplicate XML rows
setting on Windows 138
webzine xxv
Windows
automatically starting Informatica Server 150
backup domain controller 127
configuring Informatica Server 131
connecting Informatica Server to databases 69
254
Index