Troubleshooting Guide - dbmanagement.infodbmanagement.info/Books/MIX/ts_Informatica.pdf · Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug,

Troubleshooting Guide

INFORMATICA POWERCENTER 6INFORMATICA POWERMART 6(VERSION 6.0)

Informatica PowerCenter/PowerMart Troubleshooting GuideVersion 6.0 June 2002

Copyright (c) 2002 Informatica Corporation.All rights reserved. Printed in the USA.

This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free.Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug, PowerBridge, ZL Engine, and MX are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Portions of this software are copyrighted by MERANT, 1991-2000.

Apache SoftwareThis product includes software developed by the Apache Software Foundation (http://www.apache.org/).The Apache Software is Copyright (c) 2000 The Apache Software Foundation. All rights reserved.Redistribution and use in source and binary forms of the Apache Software, with or without modification, are permitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation (http://www.apache.org/).Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names Xerces and Apache Software Foundation must not be used to endorse or promote products without prior written permission of the Apache Software Foundation.5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation.THE APACHE SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.The Apache Software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc.,http://www.ibm.com. For more information on the Apache Software foundation, please see http://www.apache.org/.

DISCLAIMER: Informatica Corporation provides this documentation as is without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiNew Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Informatica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Transformation Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About PowerCenter and PowerMart . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvi

Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Accessing the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xvii

Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviii

Chapter 1: Client Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Business Components Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Mapping Variable Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Metadata Extension Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Repository Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Validation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

XML Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2: pmcmd Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17pmcmd Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3: Exporting and Importing Objects Messages . . . . . . . . . . 19Exporting and Importing Objects Messages . . . . . . . . . . . . . . . . . . . . . . . . . 20

i i i

Chapter 4: SDK Client Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45SDK Client Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 5: Log File Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Message Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Log Files and Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Session Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Workflow Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Informatica Server Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Repository Server Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Repository Agent Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 6: BLKR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57BLKR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 7: CMN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61CMN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 8: DBG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83DBG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 9: DBGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85DBGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Chapter 10: EP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91EP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 11: ES Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103ES Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 12: FR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107FR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

iv Table of Contents

Chapter 13: FTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115FTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 14: HIER Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119HIER Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Chapter 15: LM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123LM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 16: NTSERV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129NTSERV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 17: OBJM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137OBJM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Chapter 18: ODL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141ODL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 19: PMF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145PMF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 20: REP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149REP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Chapter 21: RR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169RR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Chapter 22: SDKC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SDKC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Chapter 23: SDKS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175SDKS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Table of Contents v

Chapter 24: SF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177SF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Chapter 25: SORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181SORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Chapter 26: TE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185TE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Chapter 27: TM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191TM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Chapter 28: VAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201VAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Chapter 29: WID Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211WID Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Chapter 30: WRT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217WRT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Chapter 31: XMLW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233XMLW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

vi Table of Contents

Preface

Welcome to PowerCenterRT, PowerCenter, and PowerMart, Informaticas integrated suite of software products that delivers an open, scalable data integration solution addressing the complete life cycle for data warehouse and analytic application development. PowerCenter and PowerMart combine the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely, usable, and efficient manner.

The PowerCenter/PowerMart metadata repository coordinates and drives a variety of core functions including extracting, transforming, loading, and managing. The Informatica Server can extract large volumes of data from multiple platforms, handle complex transformations on the data, and support high-speed loads. PowerCenter and PowerMart can simplify and accelerate the process of moving data warehouses from development to test to production.

Note: Unless otherwise indicated, when this guide mentions PowerCenter, it refers to both PowerCenter and PowerCenterRT.

vii

New Features and Enhancements

This section describes new features and enhancements to PowerCenter 6.0 and PowerMart 6.0.

Designer Compare objects. The Designer allows you to compare two repository objects of the same

type to identify differences between them. You can compare sources, targets, transformations, mapplets, mappings, instances, or mapping/mapplet dependencies in detail. You can compare objects across open folders and repositories.

Copying objects. In each Designer tool, you can use the copy and paste functions to copy objects from one workspace to another. For example, you can select a group of transformations in a mapping and copy them to a new mapping.

Custom tools. The Designer allows you to add custom tools to the Tools menu. This allows you to start programs you use frequently from within the Designer.

Flat file targets. You can create flat file target definitions in the Designer to output data to flat files. You can create both fixed-width and delimited flat file target definitions.

Heterogeneous targets. You can create a mapping that outputs data to multiple database types and target types. When you run a session with heterogeneous targets, you can specify a database connection for each relational target. You can also specify a file name for each flat file or XML target.

Link paths. When working with mappings and mapplets, you can view link paths. Link paths display the flow of data from a column in a source, through ports in transformations, to a column in the target.

Linking ports. You can now specify a prefix or suffix when automatically linking ports between transformations based on port names.

Lookup cache. You can use a dynamic lookup cache in a Lookup transformation to insert and update data in the cache and target when you run a session.

Mapping parameter and variable support in lookup SQL override. You can use mapping parameters and variables when you enter a lookup SQL override.

Mapplet enhancements. Several mapplet restrictions are removed. You can now include multiple Source Qualifier transformations in a mapplet, as well as Joiner transformations and Application Source Qualifier transformations for IBM MQSeries. You can also include both source definitions and Input transformations in one mapplet. When you work with a mapplet in a mapping, you can expand the mapplet to view all transformations in the mapplet.

Metadata extensions. You can extend the metadata stored in the repository by creating metadata extensions for repository objects. The Designer allows you to create metadata extensions for source definitions, target definitions, transformations, mappings, and mapplets.

viii Preface

Numeric and datetime formats. You can define formats for numeric and datetime values in flat file sources and targets. When you define a format for a numeric or datetime value, the Informatica Server uses the format to read from the file source or to write to the file target.

Pre- and post-session SQL. You can specify pre- and post-session SQL in a Source Qualifier transformation and in a mapping target instance when you create a mapping in the Designer. The Informatica Server issues pre-SQL commands to the database once before it runs the session. Use pre-session SQL to issue commands to the database such as dropping indexes before extracting data. The Informatica Server issues post-session SQL commands to the database once after it runs the session. Use post-session SQL to issue commands to a database such as re-creating indexes.

Renaming ports. If you rename a port in a connected transformation, the Designer propagates the name change to expressions in the transformation.

Sorter transformation. The Sorter transformation is an active transformation that allows you to sort data from relational or file sources in ascending or descending order according to a sort key. You can increase session performance when you use the Sorter transformation to pass data to an Aggregator transformation configured for sorted input in a mapping.

Tips. When you start the Designer, it displays a tip of the day. These tips help you use the Designer more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.

Tool tips for port names. Tool tips now display for port names. To view the full contents of the column, position the mouse over the cell until the tool tip appears.

View dependencies. In each Designer tool, you can view a list of objects that depend on a source, source qualifier, transformation, or target. Right-click an object and select the View Dependencies option.

Working with multiple ports or columns. In each Designer tool, you can move multiple ports or columns at the same time.

Informatica Server Add timestamp to workflow logs. You can configure the Informatica Server to add a

timestamp to messages written to the workflow log.

Expanded pmcmd capability. You can use pmcmd to issue a number of commands to the Informatica Server. You can use pmcmd in either an interactive or command line mode. The interactive mode prompts you to enter information when you omit parameters or enter invalid commands. In both modes, you can enter a command followed by its command options in any order. In addition to commands for starting and stopping workflows and tasks, pmcmd now has new commands for working in the interactive mode and getting details on servers, sessions, and workflows.

Error handling. The Informatica Server handles the abort command like the stop command, except it has a timeout period. You can specify when and how you want the Informatica Server to stop or abort a workflow by using the Control task in the workflow. After you start a workflow, you can stop or abort it through the Workflow Monitor or pmcmd.

New Features and Enhancements ix

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 ServerThe Informatica Client tools and the Informatica Server now connect to the repository database over the network through the Repository Server.

Repository Server. The Repository Server manages the metadata in the repository database. It accepts and manages all repository client connections and ensures repository consistency by employing object locking. The Repository Server can manage multiple repositories on different machines on the network.

x Preface

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 ManagerThe 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.

New Features and Enhancements xi

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.

xii Preface

About Informatica Documentation

The complete set of printed documentation for PowerCenterRT, PowerCenter, and PowerMart includes the following books:

Designer Guide. Provides information needed to use the Designer. Includes information to help you create mappings, mapplets, and transformations. Also includes a description of the transformation datatypes used to process and transform source data.

Getting Started. Provides basic tutorials for getting started. Also contains documentation about the sample repository.

Installation and Configuration Guide. Provides information needed to install and configure the PowerCenter and PowerMart tools, including details on environment variables and database connections.

Metadata Reporter Guide. Provides information on how to install and use the web-based Metadata Reporter to generate reports on the metadata in PowerCenter and PowerMart repositories.

Repository Guide. Provides information needed to administer the repository using the Repository Manager or the pmrep command line program. Includes details on functionality available in the Repository Manager, such as creating and maintaining repositories, folders, users, groups, and permissions and privileges.

Transformation Language Reference. Provides syntax descriptions and examples for each transformation function provided with PowerCenter and PowerMart.

Transformation Guide. Provides information on how to create and configure each type of transformation in the Designer.

Troubleshooting Guide. Lists error messages that you might encounter while using PowerCenter or PowerMart. Each error message includes one or more possible causes and actions that you can take to correct the condition.

Workflow Administration Guide. Provides information to help you create and run workflows in the Workflow Manager, as well as monitor workflows in the Workflow Monitor. Also contains information on administering the Informatica Server and performance tuning.

Documentation available with our other products includes:

Informatica Metadata Exchange SDK User Guide. Provides information about the second generation of Metadata Exchange interfaces for PowerCenter and PowerMart repositories.

Informatica PowerChannel User Guide. Provides information on how to transport compressed and encrypted data through a secure channel.

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

About Informatica Documentation xiii

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

PowerConnect for SAP BW User and Administration Guide. Provides information to install and configure PowerConnect for SAP BW to load source data into an SAP Business Information Warehouse.

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

PowerConnect for SAP R/3 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.

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

PowerConnect for TIBCO User and Administrator Guide. Provides information to install PowerConnect for TIBCO, build mappings, extract data from TIBCO messages, and load data into TIBCO messages.

PowerConnect Software Development Kit Developer Guide. Provides information to install PowerConnect SDK and build plug-ins to extract data from third-party applications and load data into third-party applications.

Metadata Exchange for Data Models User Guide. Provides information on how to extract metadata from leading data modeling tools and import it into PowerCenter/PowerMart repositories through Informatica Metadata Exchange SDK.

Metadata Exchange for OLAP User Guide. Provides information on how to use export multi-dimensional metadata from PowerCenter/PowerMart repositories into the Hyperion Integration Server through Informatica Metadata Exchange SDK.

xiv Preface

About this Book

The Troubleshooting Guide is written for all PowerCenter and PowerMart users. It contains troubleshooting information for all aspects of data warehouse development, including source analysis, transformation development, mapping development, and running sessions. This guide assumes you have knowledge about your operating systems, relational database concepts, and the interface requirements for your supporting applications.

The material in this book is available for online use.

About PowerCenter and PowerMartThis guide contains information about PowerCenterRT, PowerCenter, and PowerMart. The documentation explicitly mentions software features that differ between the products.

If You Are Using PowerCenterRTWith PowerCenterRT, you receive all product functionality, including the ability to register multiple servers, share metadata across repositories, and partition pipelines. PowerCenterRT includes the Zero Latency engine, which enables real-time, high performance, data integration for business analytics and operational data stores.

A PowerCenterRT license lets you create a single repository that you can configure as a global repository, the core component of a PowerCenterRT domain.

When this guide mentions a PowerCenterRT Server, it is referring to an Informatica Server with a PowerCenterRT license.

If You Are Using PowerCenterWith PowerCenter, you receive all product functionality, including the ability to register multiple servers, share metadata across repositories, and partition pipelines.

A PowerCenter license lets you create a single repository that you can configure as a global repository, the core component of a PowerCenter domain.

When this guide mentions a PowerCenter Server, it is referring to an Informatica Server with a PowerCenter license.

If You Are Using PowerMartThis version of PowerMart includes all features except distributed metadata, multiple registered servers, and pipeline partitioning. Also, the various PowerConnect products available with PowerCenter or PowerCenterRT are not available with PowerMart.

When this guide mentions a PowerMart Server, it is referring to an Informatica Server with a PowerMart license.

About this Book xv

Document ConventionsThis guide uses the following formatting conventions:

If you see It means

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

boldfaced text Emphasized subjects.

italicized monospaced text This is the variable name for a value you enter as part of an operating system command. This is generic text that should be replaced with user-supplied values.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

Warning: The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure.

monospaced text This is a code example.

bold monospaced text This is an operating system command you enter from a prompt to execute a task.

xvi Preface

Other Informatica Resources

In addition to the product manuals, Informatica provides these other resources:

Informatica Webzine

Informatica web site

Informatica Developer Network

Informatica Technical Support

Accessing the Informatica WebzineThe Informatica Documentation Team delivers an online journal, the Informatica Webzine. This journal provides solutions to common tasks, conceptual overviews of industry-standard technology, detailed descriptions of specific features, and tips and tricks to help you develop data warehouses.

The Informatica Webzine is a password-protected site that you can access through the Customer Portal. The Customer Portal has an online registration form for login accounts to its webzine and web support. To register for an account, go to the following URL:

http://my.Informatica.com/

If you have any questions, please email [email protected]

To better serve your needs, the Informatica Documentation Team welcomes all comments and suggestions. You can send comments and suggestions to:

[email protected]

Visiting the Informatica Web SiteYou can access Informaticas corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and locating your closest sales office. You will also find product information, as well as literature and partner information. The services area of the site includes important information on technical support, training and education, and implementation services.

Visiting the Informatica Developer Network The Informatica Developer Network is a web-based forum for third-party software developers. You can access the Informatica Developer Network at http://devnet.informatica.com. The site contains information on how to create, market, and support customer-oriented add-on solutions based on Informaticas interoperability interfaces.

Other Informatica Resources xvii

Obtaining Technical SupportThere are many ways to access Informatica technical support. You can call or email your nearest Technical Support Center listed below or you can use our WebSupport Service.

Both WebSupport and our Customer Site require a user name and password. To receive a user name and password, please contact us at [email protected] or call 866-563-6332 or 650-385-5800.

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

Informatica Corporation2100 Seaport Blvd.Redwood City, CA 94063Phone: 866.563.6332 or 650.385.5800Fax: 650.213.9489Hours: 6 a.m. - 6 p.m. (PST/PDT)email: [email protected]

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNPhone: 44 870 606 1525Fax: +44 1628 511 411Hours: 9 a.m. - 5:30 p.m. (GMT)email: [email protected]

BelgiumPhone: +32 15 281 702Hours: 9 a.m. - 5:30 p.m. (local time)

FrancePhone: +33 1 41 38 92 26Hours: 9 a.m. - 5:30 p.m. (local time)

GermanyPhone: +49 1805 702 702Hours: 9 a.m. - 5:30 p.m. (local time)

NetherlandsPhone: +31 306 082 089Hours: 9 a.m. - 5:30 p.m. (local time)

SingaporePhone: +65 322 8589Hours: 9 a.m. - 5 p.m. (local time)

SwitzerlandPhone: +41 800 81 80 70Hours: 8 a.m. - 5 p.m. (local time)

xviii Preface

C h a p t e r 1

Client Error Messages

This chapter covers the following error message topics:

Overview, 2

Business Components Messages, 3

Mapping Variable Messages, 5

Metadata Extension Messages, 6

Repository Upgrade, 7

Validation Messages, 11

XML Messages, 13

1

Overview

The Informatica Client tools display messages in the status bar as you perform tasks, such as opening or copying objects. The Designer displays error messages when you perform tasks that are not permitted, such as importing an invalid XML file.

This chapter contains messages that may display in the Informatica Client applications. Messages are listed alphabetically by category, such as validation or mapping variables. You can use this chapter to help determine what causes error messages to appear and what measures you can take to correct the problems.

If you follow the suggested instructions, but the problem persists, please contact Informatica Technical Support for additional help.

This chapter contains messages for the following topics:

Business component

Mapping variables

Metadata extensions

Repository upgrade

Validation

XML

For more error messages, see the Supplemental Guide.

For information on error messages the Informatica Client might display when you export or import an object, see Exporting and Importing Objects Messages on page 20.

2 Chapter 1: Client Error Messages

Business Components Messages


The following business component messages may appear in the Designer Output window, status bar, or a message box of the Informatica Client:

Cannot copy/move directory: The destination directory is a subdirectory of the source directory.

Cause: You tried to move a directory into a subdirectory.

Action: Check the directory structure before moving directories.

Cannot copy to an inactive version. Use Repository-Change Version to switch to that version first.

Cause: You tried to copy a directory from an active version node to an inactive version.

Action: Change the inactive version to active, and then copy the directory. Choose Repository-Change Version and select the active version. Click OK. The active version displays below the business components node. You can then copy the directory into the active version.

Cannot create a business component at the root level: please select a directory to use.

Cause: You tried to put an object directly in a business components node.

Action: You can put an object in a directory in the business components node, but not directly in the business components node.

Only Sources and Mapplets can be placed in Business Components.

Cause: You tried to place a transformation, cube, mapping, or target in a business components directory.

Action: Business component directories support sources and mapplets only.

already exists in .

Cause: You tried to have two sources or mapplets with identical names in the same directory.

Action: Sources or mapplets must have unique names in the same directory. Rename one of the sources or mapplets.

Select a directory under Business Components.

Cause: You tried to move an object into the business components node.

Action: You can put an object in a directory in the business components node, but not directly in the business components node.

The source folder is not open. Use Repository - Open to open it.

Cause: You dragged an object from one folder into a closed folder.

Business Components Messages 3

Action: Open the source folder in the Navigator before you drag an object into the destination folder.

This is not a valid move/copy.

Cause: You tried to copy, move, drag, or drop an object that cannot be copied, moved, dragged, or dropped into a directory.

Action: Check the directory structure before moving an object into it.


Mapping Variable Messages


The following mapping variable messages might appear in the Output window, status bar, or a message box of the Informatica Client:

Syntax error: bad variable name .

Cause: You altered the XML file or created an invalid mapping variable name. The imported mapping variable has an invalid name. The name has to start with $$, has to be longer than two characters, and can only have alphanumeric characters and underscores.

Action: Make sure mapping variable names follow the correct format.

A variable with this name, , already exists in the mapping.

Cause: You altered the XML file or created an invalid mapping variable name. The imported mapping variable name is not unique within the imported mapping.

Action: Make sure mapping variable names are unique within any mapping.

Mapping Variable Messages 5

Metadata Extension Messages


The following mapping variable messages might appear in a message box of the Informatica Client:

is not a valid integer value. Please enter an integer value between and .

Cause: You entered a value for an integer metadata extension that is either too large or too small.

Action: Enter a value that is between the minimum and maximum values.

Invalid name: You must specify a name.

Cause: You tried to create a metadata extension, but left the metadata extension name blank.

Action: Specify a valid name for the metadata extension.

The maximum length is too large. Please specify a value smaller than or equal to .

Cause: You tried to enter a precision for a string metadata extension that is too long.

Action: Specify a precision that is less than or equal to the maximum length.

A metadata extension named already exists in the current domain.

Cause: You tried to create or rename a metadata extension. However, another metadata extension with the name you specified already exists for the same type of object in the domain.

Action: Specify a unique name for the metadata extension.

The value's length of is higher than the maximum length of . Please enter a value with a length smaller or equal to that maximum.

Cause: You tried to change the precision for a string metadata extension, but the existing string is longer than the precision you specified.

Action: Either shorten the length of the existing metadata extension and then change the precision, or specify a precision that is greater than or equal to the length of the existing metadata extension.


Repository Upgrade

The repository upgrade process generates messages when it performs the upgrade. Many of these messages are informational, but some are error messages. Use this section to help determine what causes the error message to appear and what measures you can take to correct the problem.

The following error messages might appear when you upgrade the repository. The messages appear in the Output window in the Repository Manager. To save the messages, select and copy the text from the Output window into a text file.

For more information about upgrading a repository, see Upgrading a Repository in the Installation and Configuration Guide.


Database error while connecting to the GDR.

Cause: A database error occurred when the upgrade process connected to the global repository.

Action: Verify that the global repository database is running.

Failed creating temporary tables.

Cause: A database error occurred. The upgrade process failed to generate temporary tables used during the upgrade.

Action: Verify the repository database error. Fix the database error and restart the upgrade.

Failed clearing new session tables.

Cause: A database error occurred. The repository upgrade failed to clear tables in the repository database.


Failed initializing temporary tables.

Cause: A database error occurred. The upgrade process failed to initialize the temporary tables used during the upgrade.


Failed to update GDR connectivity information.

Cause: The upgrade process could not update the connectivity information for the global repository.

Action: Use your existing version of PowerCenter/PowerMart to register the local repository to the global repository before you perform the upgrade. Upgrade and start the global repository before you upgrade the local repository.

Repository Upgrade 7

Failed to upgrade batch to workflow: name = [batch_name], old ID = [ID_number], folder ID = [folder_ID_number].

Cause: The upgrade process failed to upgrade a batch to a workflow.

Action: Check for repository database errors. Fix any errors and restart the upgrade. If the error persists, please contact Informatica Technical Support.

Failed to upgrade file: name = [name], old ID = [ID_number], file type = [file_type].

Cause: The upgrade process failed to upgrade a file.


Failed to upgrade [object_name]: name = [object_name], old ID = [ID_number].

Cause: The upgrade process failed to upgrade an object.


Failed to upgrade session: name = [session_name], old ID = [ID_number], folder ID = [folder_ID_number].

Cause: The upgrade process failed to upgrade a session.


Failed to upgrade session persistence values.

Cause: The upgrade process could not upgrade persisted values for the session.

Action: Run the session again to generate the persisted values and restart the upgrade.

Failed to upgrade stand-alone session to workflow: name = [session_name], old ID = [ID_number], folder ID = [folder_ID_number].

Cause: The repository upgrade process failed to upgrade a session to a workflow.


Failed upgrading batch objects.

Cause: The upgrade process failed to upgrade a batch object.

Action: Contact Informatica Technical Support.

Failed upgrading database connection objects.

Cause: The upgrade process failed to upgrade a database connection object.


Failed upgrading file objects.

Cause: The upgrade process failed to upgrade a file object.



Failed upgrading session objects.

Cause: The upgrade process failed to upgrade a session object.


GDR connectivity is lost. Please restore the GDR connection before restarting the upgrade.

Cause: The upgrade process lost the connection to the global repository.

Action: Verify that the global repository is running. Restart the upgrade.


GDR connectivity failed.

Cause: The upgrade process cannot upgrade the local repository because it cannot connect to the global repository.


Repository connectivity information is incorrect.

Cause: The connectivity information required to connect to and log in to the repository is incorrect.

Action: Verify that the repository configuration information and login information is correct. Correct any errors and restart the upgrade.

Repository login failed while connecting to the GDR.

Cause: The upgrade process could not access the global repository.

Action: The username and password you use to access the local repository when you start the upgrade must match the username and password you use to access the global repository. Restart the upgrade process using the correct username and password.

Session [session_name] with ID = [ID_number] cannot be upgraded. The mapping may have been deleted or is invalid. Mapping ID = [ID_number].

Cause: The upgrade process failed to fetch a mapping from the repository because the mapping was deleted or is invalid.

Action: Verify if the mapping exists in the repository or if it is invalid. If the mapping is invalid, validate it and restart the upgrade.

Unable to connect to the GDR.

Cause: The upgrade process could not connect to the global repository because the connectivity information for the global repository may be incorrect, or the global repository database may not be available.

Repository Upgrade 9


or

Action: Verify that the global repository database is running.

Unable to set the state during the session upgrade.

Cause: A database error occurred.

Action: Verify the repository database error. Fix the database error, and restart the upgrade.

Unknown upgrade state. Fatal error occurred.

Cause: A fatal error occurred during the upgrade.


Upgrade failed due to a fatal error in fetching mapping; MappingID = [mapping ID number].

Cause: The upgrade process failed to fetch a mapping from the repository.



Validation Messages


The following validation messages might appear in the Output window, status bar, or message boxes of the Informatica Client:

Cannot get group fields for group .

Cause: Internal error.


Failed to validate transformation field .

Cause: Internal error. The field ID or the table ID that the field belongs to is zero.


The server and target database do not have compatible code pages (one way compatibility is required). Do you want to save the session?

Cause: Validation error. The code page of the target database connection used in the session is not a superset of the Informatica Server code page. When the Informatica Server runs in the Unicode data movement mode, this causes the session to fail.

Action: If the Informatica Server to execute the session runs in ASCII mode, you can ignore this warning. If the Informatica Server runs in Unicode mode, choose the most appropriate of the following actions:

Choose a different target database connection.

Choose a different Informatica Server to run the session.

Correct the code page configured for the target database connection.

Correct the code page registered for the Informatica Server.

The server and target file do not have compatible code pages. (One way compatibility is required.)

Cause: Validation error. The code page of the target file used in the session is not a superset of the Informatica Server code page. When the Informatica Server runs in the Unicode data movement mode, this causes the session to fail.

Action: If the Informatica Server to execute the session runs in ASCII mode, you can ignore this warning. If the Informatica Server runs in Unicode mode, choose the most appropriate of the following actions:

Choose a different target file and code page.

Choose a different Informatica Server to run the workflow.


Validation Messages 11

The source database and server do not have compatible code pages (one way compatibility is required). Do you want to save the session?

Cause: Validation error. The code page of the source database connection used in the session is not a subset of the Informatica Server code page. When the Informatica Server runs in the Unicode data movement mode, this causes the session to fail.

Action: If the Informatica Server runs in ASCII mode, you can ignore this warning. If the Informatica Server runs in Unicode mode, choose the most appropriate of the following actions:

Choose a different source database connection.

Choose a different Informatica Server to run the workflow.

Correct the code page configured for the source database connection.



XML Messages


The following XML messages might appear in the Output window, status bar, or a message box in the Designer:

Cannot change cardinality! The selected cardinality will cause groups to be invalid.

Cause: You tried to change the cardinality of an element that invalidates the group.

Action: You cannot change the cardinality of an element if it violates the structure defined in the associated DTD or XML schema.

cannot be pivoted since it is a key column.

Cause: You tried to pivot a column designated as a primary key.

Action: Select another column to pivot. You cannot pivot a column that is designated as a primary key.

Column cannot be added since it will make the group invalid. If you add this element/attribute, the multiple occurring parent for this group will move down to . Remove the primary key before adding this element/attribute.

Cause: You tried to add a column to the group that can turn the primary key in the group into a multiple-occurring column and invalidate the group.

Action: Remove the primary key before adding the column. When you have completed modifying your group, set an appropriate column as a key.

Column cannot be pivoted. All columns under the same multiple occurring parent should be either pivoted or unpivoted. Column is pivoted while column is not.

Cause: You have a pivoted and an unpivoted column under the same multiple occurring parent.

Action: This is a warning. If you pivot an element, you must also pivot all its sibling elements included in the group. You may get this warning if you are pivoting several elements or attributes in a group. You can proceed with the action if you are sure you want to pivot the element or attribute.

Column cannot be unpivoted. All columns under the same multiple occurring parent should be either pivoted or unpivoted. Column and column are pivoted.

Cause: You have a pivoted and an unpivoted column under the same multiple occurring parent.

Action: This is a warning. You may get this warning if you are pivoting several elements or attributes in a group. You can proceed with the action if you are sure you want to pivot the element or attribute.

XML Messages 13

Denormalized group cannot be created since XML Element/Attribute has a many to many relationship with XML Element/Attribute .

Cause: You have at least two multiple-occurring elements in the group with a many-to-many relationship.

Action: You cannot put more than one multiple-occurring elements with a many-to-many relationship in the same group. The multiple-occurring elements in a denormalized group must have a one-to-many relationship.

Element/Attribute occurs only once and cannot be pivoted.

Cause: You tried to pivot an element that occurs only once.

Action: This is a warning. It is not necessary to pivot a column that occurs only once. You can proceed with the action if you are sure you want to pivot the column.

Group cannot be related to group . Related groups should be under the same XML tree branch.

Cause: You tried to set a foreign key to relate to the primary key of a group that is lower on the parent chain than the current group.

Action: Relate to another primary key. You can only set a foreign key to relate to the primary key of a group that is higher in the parent chain than the current group.

A key already exists at this level. has a one-one correspondence with .

Cause: You tried to add a key to a hierarchy level that already has a key.

Action: You cannot have more than one key for one hierarchy level.

Only leaf elements can be pivoted. refers to a non-leaf element and cannot be pivoted.

Cause: You tried to pivot a column that points to an element that is not a leaf element.

Action: Select another column to pivot. You can pivot only attributes and leaf elements.

Source file name has to be less than 80 characters long for DBD .

Cause: You changed the XML file so that the DBD FILENAME attribute is greater or equal to 80 characters.

Action: Make sure the FILENAME attribute is less than 80 characters.

The XML file has fewer elements than the pivot value specified. Element appears only times in the XML file.

Cause: The pivot value you set is larger than the number of times the element appears in the XML file you are importing from.


Action: This is a warning. You can proceed with the action if you know that the pivot value will match the number of times the element appears in the source XML file when you run the session.

You cannot have a pivoted column and an unpivoted column referring to the same element. Column is pivoted while column is not.

Cause: You have a pivoted and an unpivoted column in one group pointing to the same element.

Action: This is a warning. You may get this warning if you are pivoting the same element into several columns in a group. You can proceed with the action if you are sure you want to pivot the column.

You cannot have two multiple occurring elements in the same group. XML Element/Attribute has a many to many relationship with XML Element/Attribute .

Cause: You have at least two multiple-occurring elements in the group with a many-to-many relationship.

Action: You cannot put more than one multiple-occurring elements with a many-to-many relationship in the same group. The multiple-occurring elements in a denormalized group must have a one-to-many relationship.

XML Messages 15

C h a p t e r 2

pmcmd Messages

This chapter covers the following topics:

pmcmd Messages, 18

Error messages listed alphabetically.

17

pmcmd Messages

pmcmd is a program that you can use to communicate with the Informatica Server. You can perform some of the tasks that you can also perform in the Workflow Manager such as starting and stopping workflows and tasks.

You issue pmcmd commands from the command line, and pmcmd returns informational or error messages to the command line. This chapter lists error messages alphabetically.


For more information about pmcmd, see Using pmcmd in the Workflow Administration Guide.

Invalid code page name specified in environment variable PM_CODEPAGENAME.

Cause: You set an invalid Informatica Server code page.

Action: Change the Informatica Server code page to a valid code page.

Code page name specified in environment variable PM_CODEPAGENAME is not ASCII based.

Cause: Your environment requires an ASCII-based Informatica Server code page. The code page you set in PM_CODEPAGENAME is not derived from an ASCII-based code page.

Action: Select an ASCII-based code page for the Informatica Server code page.

Product started with code page named . This code page is unavailable in the product's installation.

Cause: You started the Informatica Server with an invalid code page.

Action: Select a valid code page.

Invalid language specified in environment variable PM_LANGUAGE.

Cause: You set an invalid language in PM_LANGUAGE.

Action: Select a valid language.

Failed to expand server variables or session parameters.

Cause: While resolving mapping references, the Informatica Server did not have the initial values for the session parameters in the parameter file, such as $input or $output.

Action: Look at the Informatica Server log and identify the missing or incorrect parameters.

18 Chapter 2: pmcmd Messages

C h a p t e r 3

Exporting and Importing Objects Messages

This chapter covers the following topics:

Exporting and Importing Objects Messages, 20

Error messages listed alphabetically.

19

Exporting and Importing Objects Messages


The following object export/import messages may appear in the Output window, status bar, or a message box of the Informatica Client:

Code page in file: not compatible with repository code page: .

Cause: The repository code page specified in the XML file is not compatible with the target repository code page.

Action: Cannot import the XML file. Edit the XML file and make sure the code pages are compatible.

Database Error: while Assigning Ids for Source: .



Database Error: while Assigning Ids for Target: .



Database Error: while Assigning Ids for Transformation: .



The DTD file name is not specified.

Cause: The XML file does not contain the DTD file name.

Action: Edit the XML file header with the DTD file name, powrmart.dtd.

Error: a partition name is given for a non-partitionable connection reference for session transformation instance .

Cause: In the XML file, you included a PARTITIONNAME attribute in a CONNECTIONREFERENCE element that is not partitionable.

Action: Edit the XML file, and remove the PARTITIONNAME attribute from the CONNECTIONREFERENCE element. Or, re-export the object and then import it.

Error: An Unknown target field attribute: has been detected for Field: .

Cause: Internal Error.


20 Chapter 3: Exporting and Importing Objects Messages

Error: building session .

Cause: The SESSION element or some of its sub-elements are invalid.

Action: View the Output window for more information. Re-export the object and then import it.

Error: Cannot determine ODBC Data type for field .

Cause: You defined an invalid ODBC type for a table field in the XML file.

Action: Edit the XML file for the ODBC data type for that particular field.

Error: Cannot import tables of type .

Cause: You entered an invalid value for the TABLETYPE attribute in the TARGET element in the XML file.

Action: Edit the XML file and enter NONE for the TABLETYPE attribute. Or, re-export the object and then import it.

Error: connection reference s type and subtype is not valid for the extension.

Cause: In the XML file, you specified CONNECTIONTYPE and CONNECTIONSUBTYPE attributes in the specified CONNECTIONREFERENCE element that are not valid for the TYPE and SUBTYPE attributes of the SESSIONEXTENSION element.

Action: Edit the XML file, and verify the type and subtypes of the CONNECTIONREFERENCE and SESSIONEXTENSION elements are compatible. Or, re-export the object and then import it.

Error: connection reference with connection number is not found for element due to the following error:

Cause: In the SESSIONEXTENSION element, the referenced CONNECTIONREFERENCE element does not exist.

Action: Edit the XML file, and specify a valid CONNECTIONREFERENCE. Or, re-export the object and then import it.

Error: could not add group .

Cause: Unable to add group information.

Action: Check that the group exists in the XML file. Or, re-export the object and then import it.

Error: Could not find associated source field: for .

Cause: In the XML file, the specified REF_SOURCEFIELD attribute in the TRANSFORMFIELD element in the specified Normalizer transformation does not match the name of a SOURCEFIELD element.

Exporting and Import ing Objects Messages 21

Action: Edit the XML field and verify the REF_SOURCEFIELD attribute matches the name of a SOURCEFIELD element in the XML file. Or, re-export the object and then import it.

Error: Could not find DSQ instance for .

Cause: The source qualifier associated with the source is missing in the XML file.

Action: Edit the XML file and verify that it has a valid entry for the source qualifier. Or, re-export the object and then import it.

Error: Could not find field: in Instance: .

Cause: You specified a Foreign Key field name does not exist in the referenced source.

Action: Edit the referenced field name in the XML file. Or, re-export the object and then import it.

Error: Could not find Transformation definition for: .

Cause: The TRANSFORMATION_NAME attribute in the INSTANCE element does not match a TRANSFORMATION element name in the XML file.

Action: Edit the XML file and verify the TRANSFORMATION_NAME attribute matches a TRANSFORMATION element name. Or, re-export the object and then import it.

Error: Could not get datatype description for field: .



Error: Could not get group for source field: .



Error: Could not Resolve Foreign key dependency For Field: in Source: .

Cause: The DBD or source for a specified foreign key field name is missing in the XML file.

Action: Edit the XML file. Or, re-export the object and then import it.

Error: Duplicate instances of type: name: .

Cause: In the XML file, you defined two instances of the same type with the same instance name.

Action: Edit the XML file and rename one of the transformation instance names. Also, rename any references to it in the mapping or mapplet. Import the object again.

Error: duplicate object of type .

Cause: The XML file contains two objects with the same name and type.


Action: Edit the XML file, and rename the duplicate object. Or, re-export the object and then import it.

Error encountered while Parsing file.

Cause: The XML file from which you tried to import is invalid or does not follow the powrmart.dtd file.

Action: Edit the XML file and make sure it is valid against the powrmart.dtd file.

Error: expected a timer for task .

Cause: In the XML file, you did not specify a TIMER element for the Timer TASK.

Action: Re-export the object and then import it.

Error: Expected unsigned value for attribute: , found value: .

Cause: You provided a negative or invalid value for an unsigned number in the XML file.

Action: Correct the value in the XML file. Or, re-export the object and then import it.

Error: extension subType for extension type is invalid for element .

Cause: In the XML file, you specified an invalid SUBTYPE attribute for the SESSIONEXTENSION element with the specified TYPE attribute. The SUBTYPE attribute must be compatible with the TYPE attribute.

Action: Edit the XML file, and specify a valid SUBTYPE. Or, re-export the object and then import it.

Error: Failed to Fetch Version under folder .

Cause: You defined a version name of the mapping in the XML file that does not exist in the target folder.

Action: Edit the version node under the session in the XML file.

Error: Field order does not match group order.

Cause: The field order does not match the group order in the XML file.

Action: Edit the XML file and make sure the field order matches the group order. Or, re-export the object and then import it.

Error: Illegal Folder Version: for Shortcut: .

Cause: The folder version information in the shortcut node for an object is invalid.

Action: Edit the XML file for the VERSION node under the SHORTCUT node. Or, re-export the object and then import it.

Error: Internal Error encountered in initializing Parser.




Error: Invalid aggregate type for mapping variable .

Cause: In the XML file, you specified NO for the ISPARAM attribute, and you entered an invalid value for the AGGFUNCTION attribute for the specified MAPPINGVARIABLE element.

Action: Edit the XML file and enter COUNT, MIN, or MAX for the AGGFUNCTION attribute for the MAPPINGVARIABLE element. Or, re-export the object and then import it.

Error: Invalid Codepage: for Flat File.

Cause: You defined a code page for the flat file object in the XML file that is not compatible with the repository code page information.

Action: Cannot import the source.

Error: invalid Component Type for element .

Cause: In the XML file, you specified an invalid TYPE attribute for the SESSIONCOMPONENT element.

Action: Edit the XML file, and specify a valid TYPE attribute for the SESSIONCOMPONENT element. Or, re-export the object and then import it.

Error: invalid connection type for connection reference .

Cause: In the XML file, you specified an invalid CONNECTIONTYPE attribute for the CONNECTIONREFERENCE element.

Action: Edit the XML file, and specify a valid CONNECTIONTYPE attribute. Or, re-export the object and then import it.

Error: Invalid Database Type: .

Cause: The database name in the XML file for that object is not supported or invalid.

Action: Edit the XML file and verify the database type. Or, re-export the object and then import it.

Error: Invalid Database Type: for source: .

Cause: You entered an invalid database type in the DATABASETYPE attribute in the SOURCE element for the specified source.

Action: Edit the XML file and correct the DATABASETYPE attribute in the SOURCE element. Or, re-export the object and then import it.


Error: Invalid database type for target ....A plugin required to handle this is missing....This target will not be available for import.

Cause: In the XML file, you defined a plug-in database type for the target, but you did not register the plug-in in the Informatica Client.

Action: Register the plug-in the Informatica Client before importing the file. Or, edit the XML file and specify an existing database type.

Error: Invalid Database Type: for target: , or the Database Type is not installed in this repository

Cause: In the XML file, you defined a plug-in database type for the target, but you did not install the plug-in in the repository.

Action: Install the plug-in in the repository before importing the file. Or, edit the XML file and specify an existing database type.

Error: Invalid Datatype: for field: .

Cause: You entered an invalid datatype for the field in the XML file.

Action: Edit the XML file to specify a supported datatype. Or, re-export the object and then import it.

Error: Invalid datatype for aggregate COUNT for mapping variable .

Cause: In the XML file, you specified COUNT for the AGGFUNCTION attribute, and you entered an invalid value for the DATATYPE attribute for the specified MAPPINGVARIABLE element.

Action: Edit the XML file and enter either LONG or SHORT for the DATATYPE attribute for the MAPPINGVARIABLE element. Or, re-export the object and then import it.

Error: Invalid datatype for mapping variable .

Cause: You entered an invalid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element in the XML file.

Action: Edit the XML file and define a valid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element. Or, re-export the object and then import it.

Error: invalid datatype for workflow variable .

Cause: In the XML file, you specified an invalid DATATYPE attribute for the WORKFLOWVARIABLE element.

Action: Edit the XML file, and specify a valid DATATYPE attribute for the WORKFLOWVARIABLE element. Or, re-export the object and then import it.


Error: invalid DSQ instance name for session transformation instance .

Cause: In the XML file, you specified a DSQINSTNAME attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element.

Action: Edit the XML file, and verify the DSQINSTNAME attribute matches the SESSTRANSFORMATIONINST element name. Or, re-export the object and then import it.

Error: invalid DSQ of type for the extension in session transformation instance .

Cause: In the XML file, you specified a DSQINSTNAME and DSQINSTTYPE attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element or a SESSTRANSFORMATIONINST element that does not match the name and type specified in the SESSIONEXTENSION element.

Action: Edit the XML file, and verify the DSQINSTNAME and DSQINSTTYPE attributes match the SESSTRANSFORMATIONINST element name and type. Or, re-export the object and then import it.

Error: invalid DSQ type for element .

Cause: In the XML file, you specified an invalid DSQINSTTYPE attribute for the SESSIONEXTENSION element.

Action: Edit the XML file, and specify a valid DSQINSTTYPE attribute. Or, re-export the object and then import it.

Error: Invalid Extension type: for element .

Cause: In the XML file, you specified an invalid TYPE attribute for the SESSIONEXTENSION element.

Action: Edit the XML file, and specify a valid TYPE for the SESSIONEXTENSION. Or, re-export the object and then import it.

Error: Invalid Field Attribute: found for field: .

Cause: You defined an invalid field attribute for a table field in the XML file.

Action: Edit the XML file for that particular attribute. Or, re-export the object and then import it.

Error: Invalid FTP Name .

Cause: Unable to retrieve the connection object defined in the XML file for that session.

Action: Create a new connection object or select an existing one using the Workflow Manager.


Error: Invalid Group for field .

Cause: You defined a group in the XML file that does not exist for that table field.

Action: Edit the group name in the XML file. Or, re-export the object and then import it.

Error: Invalid Initialization Property: .

Cause: You entered NO for the USERDEFINED attribute and entered an invalid value for the NAME attribute for the INITPROP element in the XML file.

Action: If the INITPROP element represents a user-defined initialization property in the transformation, edit the XML file and enter YES for the USERDEFINED attribute. Otherwise, re-export the object and then import it.

Error: Invalid Instance Type: .

Cause: You specified an invalid entry for the TYPE attribute in the INSTANCE element for a transformation.

Action: Edit the XML file and enter a valid instance type for the TYPE attribute. Or, re-export the object and then import it.

Error: Invalid Key Type: .

Cause: You defined a key type for a source object in the XML file that is not supported.

Action: Edit the key type node in the XML file. Or, re-export the object and then import it.

Error: Invalid Mapping Name for the session .

Cause: You defined an invalid mapping name associated with the session in the XML file.

Action: Edit the XML file for the mapping name attribute in the session. Or, re-export the object and then import it.

Error: Invalid Mapplet Group for Field: Transformation: .

Cause: In the XML file, the MAPPLETGROUP attribute value does not match the name of the GROUP element for the mapplet.

Action: Edit the XML file and verify the MAPPLETGROUP attribute matches the GROUP name for the mapplet. Or, re-export the object and then import it.

Error: Invalid number of fields for transformation: .

Cause: In the XML file, you included more than two TRANSFORMFIELD elements in the specified TRANSFORMATION element for a Sequence Generator transformation.


Action: Edit the XML file and make sure the Sequence Generator transformation has exactly two TRANSFORMFIELD elements. Or, re-export the object and then import it.

Error: invalid partition name for element .

Cause: In the XML file, you specified an invalid PARTITIONNAME attribute for the specified element.

Action: Edit the XML file, and specify a valid PARTITIONNAME attribute. Or, re-export the object and then import it.

Error: invalid partition type for session transformation .

Cause: In the XML file, you specified an invalid PARTITIONTYPE attribute for the SESSTRANSFORMATIONINST element.

Action: Edit the XML file, and specify a valid PARTITIONTYPE. Or, re-export the object and then import it.

Error: Invalid precision: specified for field: . The maximum precision is 65535.

Cause: You defined the field precision in the XML file greater than the maximum of 65,535.

Action: Edit the XML file and make sure the precision is less than or equal to the maximum precision, which is 65,535.

Error: Invalid reference field: for Lookup Field: Transformation: .

Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file.

Action: Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, re-export the object and then import it.

or

Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name.

Action: Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, re-export the object and then import it.


Error: Invalid reference field: for Field: Transformation: .

Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file.

Action: Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, re-export the object and then import it.

or

Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name.

Action: Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, re-export the object and then import it.

Error: Invalid reference field for Transformation field: .

Cause: In the XML file, a TRANSFORMFIELD element contains a value for the REF_FIELD attribute that does not match a SOURCEFIELD element.

Action: Edit the XML file and verify the REF_FIELD attribute matches the name of the SOURCEFIELD element. Or, re-export the object and then import it.

Error: Invalid scale: specified for field: . The scale cannot be greater than the precision or the maximum scale which is 65535.

Cause: You defined the scale for a field in the XML file with an invalid number. The scale is either greater than the corresponding precision or greater than the maximum scale allowed, which is 65,535.

Action: Edit the XML file and make sure the scale for the field is less than or equal to the precision for the field.

Error: invalid suspension email for workflow .

Cause: In the XML file, you specified a SUSPENSION_EMAIL attribute for the WORKFLOW element that references a non-existent Email task.

Action: Edit the XML file, and verify the SUSPENSION_EMAIL matches a reusable Email task. Or, re-export the object and then import it.

Error: Invalid table attribute: .

Cause: You defined a table attribute type in the XML that is not supported.

Action: Edit the XML file for that attribute. Or, re-export the object and then import it.


Error: Invalid target database type: for target: .

Cause: You defined an invalid database type in the XML file, or the database type is not valid for a target.

Action: Edit the XML file and define the correct database type for the DATABASETYPE attribute in the TARGET element. Or, re-export the object and then import it.

Error: invalid task type for element .

Cause: In the XML file, you specified an invalid TYPE attribute in the TASK element.

Action: Edit the XML file, and enter a valid TYPE for the TASK. Or, re-export the object and then import it.

Error: Invalid Task type for task .

Cause: In the XML file, you specified an invalid TYPE attribute for the TASK element.

Action: Edit the XML file, and specify a valid TYPE for the TASK. Or, re-export the object and then import it.

Error: Invalid Transformation type for transformation .

Cause: In the XML file, you defined the TYPE Attribute in the TRANSFORMATION element as an incorrect value.

Action: Edit the XML file and enter a legal transformation type for the attribute TYPE. Or, re-export the object and then import it.

Error: Invalid Usage Flags: .

Cause: You specified an invalid usage flag in the XML file.

Action: Edit the XML file. Or, re-export the object and then import it.

Error: Invalid value: , expecting unsigned value for attribute: , for : .

Cause: You provided a negative or invalid value for an unsigned number in the XML file.

Action: Edit the XML file and define a valid value for the attribute OCCURS. Or, re-export the object and then import it.

Error: invalid value for in Scheduler.

Cause: In the XML file, you specified a invalid value for the specified attribute in the SCHEDULER element.

Action: Edit the XML file, and enter a valid value. Or, re-export the object and then import it.


Error: invalid VALUEPAIR for object type for element .

Cause: In the specified element, you referenced a VALUEPAIR element that is invalid for the TASKTYPE of the specified element.

Action: Edit the XML file, and specify a valid VALUEPAIR, or remove the VALUEPAIR if it is not needed.

Error: Invalid version name in the XML file for the mapping associated with the session: .

Cause: You defined an invalid version name for the mapping in the XML file.

Action: Edit the XML file for the version node in the session. Or, re-export the object and then import it.

Error: invalid Widget Type (transformation type) for element .

Cause: In the XML file, you specified an invalid TRANSFORMATIONTYPE attribute for the SESSTRANSFORMATIONINST or SESSIONEXTENSION element.

Action: Edit the XML file, and specify a valid TRANSFORMATIONTYPE. Or, re-export the object and then import it.

Error: Lookup should be done before importing.



Error: Missing ATTRIBUTE for field: .

Cause: The specif

Troubleshooting Guide - dbmanagement.infodbmanagement.info/Books/MIX/ts_Informatica.pdf · Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug,

Text of Troubleshooting Guide - dbmanagement.infodbmanagement.info/Books/MIX/ts_Informatica.pdf ·...

Mini-Hydropower: Introduction and Overvie · Mini-Hydropower: Introduction and Overview Peter Schragl Lima, 13 noviembre 2012. Content ... Powerchannel and penstock Long penstock

Informatica PowerExchange for HDFS - 10.0 - User Guide - (English) Documentation... · 2016-07-24 · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT,

PowerCenter/PowerMart Metadata Reporter Guidedbmanagement.info/Books/MIX/MetaRpt_Informatica.pdf · Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect,

Informatica PowerCenter (Version 9.5.1) · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer,

Novelties plugs Seed 2015 Novelties GAZANIA LAVANDULA ...Powerplug-team Novelties Powerplugs Seed 2015Powerplugs2015 SEED Novelties Powerplug-team Powerplug-team Production and Sales

Informatica PowerCenter - 10.0 - Getting Started - (English)...Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter

UserGuideof HostofRemote Controller · 2016. 8. 29. · Nameandpositionofeachpartsof QN-H618 1. USBoutlet 10.Remotecontrolinductionzone 2. Remote 11.Returnbutton 3. Powerplug 12.Checkfunctionbutton

Action PowerChannel

ExtractingandUsingPowerChannelDatafor ... · ExtractingandUsingPowerChannelDatafor AutomatonInferenceUsingSparseAlphabets June 27, 2016 supervised by: S. Schupp A. Wichmann ... powerchannel

ENGLISH DEUTSCH FRANÇAIS NEDERLANDS …...not cut off the powerplug to replace it with another plug,as this will cause a hazardous situation. Do not use a damaged powerplug. If the

Informatica PowerCenter (Version 9.0.1) - Gerardnico...Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data

Informatica AddressDoctor Cloud (Version 2)€¦ · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data

HQ7865optics-production.s3.amazonaws.com/product_media_files/...Warning Please read these instructions before using the appliance. Only use the HQ8000 powerplug supplied to charge

Informatica MDM Multidomain Edition - 9.7.1 HotFix 6 ... Documentation/5/MDM… · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter

PowerCenter Command Reference - …docshare01.docshare.tips/files/9396/93966627.pdf · Informatica PowerCenter Command Reference Version 8.6.1 February 2009 ... PowerCenterRT, PowerCenter

Informatica PowerChannel 9.0 User Guide

1.0 Introduction - futuretech.blinkenlights.nlfuturetech.blinkenlights.nl/onyx/IR_techreport.pdf · system through the POWERchannel-2 board and is responsible for the preliminary

Unit 2: Mobile Communication Systems Performance ... · Performance Improvement Techniques in Cellular RFMNRFMN--20092009 Umrani A. Waheed ... To reduce CCI powerchannel interference

Workflow Basics Guide - datacadamia.com · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer,

Transformation Language Reference - Gerardnico€¦ · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data

Web Services Provider Guide - Informatica · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer,

Informatica Ultra Messaging - 6.0.0 - Concepts Guide ... Documentation/2/UMQ… · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter

Informatica Data Integration Hub - 10.0.0 - Developer ... Documentation/4/DIH_1000... · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT,

HQ663,HQ662 - p4c.philips.com fileImportant Read these instructions for use carefully before using the appliance and save them for future reference. Only use the powerplug supplied

Informatica (Version 9.6.1) · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,

Informatica Cloud - 2 - Migration Guide - (English) Documentation...Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter

Informatica PowerCenter (Version 9.0.1) - Gerardnico · Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter

Static Analysis of Security Properties by Abstract ...mehdi.bouaziz.org/p/Bouaziz-ENS12-slides.pdf · I PowerChannel Mehdi Bouaziz, École normale supérieure Introduction to Security

HQ6894,6893,6890 - Philips · 2001-01-15 · HQ6894,6893,6890 3. Important Only use the HQ6000 powerplug supplied to charge the appliance. The powerplug transforms 110-240 volts to

HQ6889,HQ6888,HQ6885optics-production.s3.amazonaws.com/product_media_files/... · 2015-08-17 · Every week:shaving unit 1 Switch the shaver off,remove the powerplug from the wall

Documents

Troubleshooting Guide - dbmanagement.infodbmanagement.info/Books/MIX/ts_Informatica.pdf · Informatica, PowerMart, PowerCenter, PowerCenterRT, PowerChannel, PowerConnect, PowerPlug,

Text of Troubleshooting Guide - dbmanagement.infodbmanagement.info/Books/MIX/ts_Informatica.pdf ·...