0% found this document useful (0 votes)

310 views

Informatica 951 MessageReference

Error message descriptions for Informatica 951

Uploaded by

nivedith

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

310 views

Informatica 951 MessageReference

Error message descriptions for Informatica 951

Uploaded by

nivedith

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 481

Informatica (Version 9.5.

Message Reference

Informatica Message Reference

Version 9.5.1
December 2012
Copyright (c) 1998-2012 . All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and
disclosure and are 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. This Software may be protected by U.S. and/or international
Patents and other Patents Pending.
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 and as provided in
DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(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 product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in
writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On
Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica
Master Data Management 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 and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights
reserved.Copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta
Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All
rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved.
Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright
Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information
Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights
reserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright Jaspersoft
Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yWorks GmbH. All rights reserved. Copyright
Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc.
Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved.
Copyright LogiXML, Inc. All rights reserved. Copyright 2003-2010 Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board
of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,
Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under the License.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright
1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://
www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not
limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,
and Vanderbilt University, Copyright () 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of
this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without
fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 () MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available
at http://www.dom4j.org/ license.html.
The product includes software copyright 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software copyright 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://
www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject
to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://
www.pcre.org/license.txt.
This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// www.eclipse.org/org/documents/epl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/
doc/ license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/
license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,
http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- licenseagreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://
www.jcraft.com/jsch/LICENSE.txt. http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/
license.html; http://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://
www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/

software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/

iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.netsnmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html;
http://www.jmock.org/license.html; http://xsom.java.net; and http://benalman.com/about/license/.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution
License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License
Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mitlicense.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).
This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software
are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further
information please visit http://www.extreme.indiana.edu/.
This product includes software developed by Andrew Kachites McCallum. "MALLET: A Machine Learning for Language Toolkit." http://mallet.cs.umass.edu (2002).
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7676516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.
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 noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is
subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF
THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH
OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Part Number: IN-MR-951-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1: Client Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PowerExchange for JMS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
PowerExchange for Netezza Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
PowerExchange for PeopleSoft Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
PowerExchange for Salesforce.com Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
PowerExchange for SAP NetWeaver Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Importing Source Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Validating the Filter Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Validating the Join Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Validating SAP Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating ABAP Program Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Cleaning ABAP Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Generating and Installing ABAP Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Validating SAP Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Importing and Exporting SAP Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Working with IDocs Using ALE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Data Migration Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Business Content Integration Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
PowerExchange for SAP NetWeaver BI Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
PowerExchange for TIBCO Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PowerExchange for webMethods Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
PowerExchange for Web Services Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
PowerExchange for WebSphere MQ Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
XML Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2: Informatica Administrator Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Informatica Administrator Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table of Contents

Chapter 3: A Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

ADV Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ALERT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ATHR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
AUTH Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
AUTHEN Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4: B Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

BAPI Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
BR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
BTree Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
BW Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 5: C Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

CFG Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
CMD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
CMN Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
CNX Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
CONF Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
CSE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
CTSDK Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 6: D Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

DBGR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
DMI Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
DOM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
DP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
DSP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 7: E Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

EB Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
EP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
EB Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
EXP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
EXPFN Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Chapter 8: F Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

FEXP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
FR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
FTP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Table of Contents

Chapter 9: H Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

HIER Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 10: I Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

IDM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
IDOC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 11: J Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

JDE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
JMS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
JSDK Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
JTX Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 12: L Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

LB Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
LDAP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
LDBG Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
LGS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
LIC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
LM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
LMTGT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Lotus Notes Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 13: M Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

MBC_EXCL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
MMS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
MPSVCCMN Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
MQ Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
MSRdr Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Chapter 14: N Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

NODE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
NTSERV Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
NZRDR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
NZWRT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 15: O Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

OBJM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
ODL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
OHS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
OPT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Table of Contents

iii

Chapter 16: P Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

PCCL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
PCSF Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
PETL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
PMF Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
PMJVM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
PR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
PWX Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
PWXPC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Chapter 17: R Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

REGEX Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
REP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
REP_CORE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
RFC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
RR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
RS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Chapter 18: S Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

SAPUTIL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
SDKC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
SDKS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
SDKXML Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
SF Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
SFDC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
SM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
SORT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
SPC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
SQL Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
SR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Chapter 19: T Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

TE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
TIB Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
TM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
TPTRD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
TPTWR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
TT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Chapter 20: U Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

UDT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
UM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Table of Contents

Chapter 21: V Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

VAR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Chapter 22: W Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

WEBM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426
WRT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
WSC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
WSH Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
WSP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Chapter 23: X Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

XMLR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
XMLW Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

Table of Contents

Preface
The Informatica Message Reference is written for all Informatica users. This guide 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.

Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at
http://mysupport.informatica.com. The site contains product information, user group information, newsletters,
access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,
the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product
Documentation, and access to the Informatica user community.

Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have
questions, comments, or ideas about this documentation, contact the Informatica Documentation team through
email at [email protected]. We will use your feedback to improve our documentation. Let us
know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your product,
navigate to Product Documentation from http://mysupport.informatica.com.

Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The site contains information
about Informatica, its background, upcoming events, and sales offices. You will also find product and partner
information. The services area of the site includes important information about technical support, training and
education, and implementation services.

Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.
The How-To Library is a collection of resources to help you learn more about Informatica products and features. It
includes articles and interactive demonstrations that provide solutions to common problems, compare features and
behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com.
Use the Knowledge Base to search for documented solutions to known technical issues about Informatica
products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If
you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base
team through email at [email protected].

Informatica Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at
http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files
that help you learn about common concepts and guide you through performing specific tasks. If you have
questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base
team through email at [email protected].

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires
a user name and password. You can request a user name and password at http://mysupport.informatica.com.
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America

Europe / Middle East / Africa

Asia / Australia

Toll Free

Brazil: 0800 891 0202

France: 0805 804632

Australia: 1 800 151 830

Mexico: 001 888 209 8853

Germany: 0800 5891281

New Zealand: 09 9 128 901

North America: +1 877 463 2435

Italy: 800 915 985

Netherlands: 0800 2300001
Portugal: 800 208 360

Standard Rate

Spain: 900 813 166

Explanation:

You wanted to import a repository object that represents a JMS source or target definition
from an XML file. However, the XML file contains an invalid header field. The XML file may
have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

Chapter 1: Client Messages

The object has an invalid header field map value.

Explanation:

You wanted to import a repository object that represents a JMS source or target definition
from an XML file. However, the XML file contains an invalid map value for a header field. The
XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Bytes Message, but the body field name is invalid.
Explanation:

You wanted to import a repository object that represents a JMS source or target definition in
Bytes message format from an XML file. However, the body field name in the XML file is
invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Bytes Message, but the datatype for the body field is invalid.
Explanation:

You wanted to import a repository object that represents a JMS source or target definition in
Bytes message format from an XML file. However, the datatype for the body field in the XML
file is invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Text Message, but the body field name is invalid.
Explanation:

You wanted to import a repository object that represents a JMS source or target definition in
Text message format from an XML file. However, the body field name in the XML file is
invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Text Message, but the datatype for the body field is invalid.
Explanation:

You wanted to import a repository object that represents a JMS source or target definition in
Text message format from an XML file. However, the datatype for the body field in the XML
file is invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The precision is invalid.

Explanation:

You wanted to import a repository object that represents a JMS source or target definition
from an XML file. However, the precision for a field is invalid. The XML file may have been
modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

Unknown error happened.

Explanation:

The Designer encountered an unknown error. The Repository Service might not be running.

User Response:

Make sure the Repository Service is running. If necessary, start the Repository Service.

Explanation:

The repository may contain inconsistencies.

Invalid user name, password, or DSN entry.

User Response:

Provide a valid user name and password, and verify that the DSN entry is valid.

No output links found or no input link found for the output link.
Explanation:

The mapping is not valid.

User Response:

Provide at least one output link for the Source Qualifier or provide input links for all the output
links.

PowerExchange for PeopleSoft Messages

Application source qualifier <application source qualifier name>: Error in preparing the query for effective date
data extraction.
Explanation:

You have defined this application source qualifier to extract current rows from an effective
dated record that has no primary keys or PeopleSoft keys defined.

User Response:

Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in
the Source Analyzer.

Explanation:

You have specified an effective date join order in this application source qualifier, and at least
one of the effective dated records has no primary keys or PeopleSoft keys defined.

User Response:

Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in
the Source Analyzer.

Application source qualifier <application source qualifier name> has Effective Date Extract Join Order with invalid
source names.
Explanation:

Chapter 1: Client Messages

In the Effective Date Join Order field, you typed a PeopleSoft record name that is not
connected to the application source qualifier.

User Response:

Edit the Effective Date Join Order field so that each PeopleSoft record name is spelled
correctly. The record names you enter in the Effective Date Join Order field must match the
records associated with the application source qualifier. Separate each record name with a
comma.

Application source qualifier <application source qualifier name> has invalid Extract Date.
Explanation:

You entered the Extract Date in the wrong date format.

User Response:

Enter the Extract Date in the following format: MM/DD/YYYY HH24:MI:SS.

Application source qualifier <application source qualifier name> has more than one tree attached.
Explanation:

The listed application source qualifier is associated or connected to more than one imported
PeopleSoft tree source definition. You can associate or connect only one imported tree
source definition to a single application source qualifier.

User Response:

Disconnect one of the tree source definitions from the application source qualifier. Or,
remove one of the associated tree source definitions. To use more than one tree in a single
mapping, create an application source qualifier for each tree you want to use. Use a Joiner
transformation to join two related trees.

Application source qualifier <application source qualifier name> has projected port with no inbound link.
Explanation:

The listed application source qualifier has a connected output port, and the corresponding
input port is not connected.

User Response:

Connect the necessary input port or disconnect the connected output port.

Application Source Qualifier <application source qualifier name> has tree and Extract Override.
Explanation:

The listed application source qualifier uses a user-defined extract override for a PeopleSoft
tree source definition. You cannot use extract overrides for tree sources.

User Response:

Edit the application source qualifier to remove the extract override and save the mapping.

Application source qualifier <application source qualifier name> has winter tree and other sources.
Explanation:

The listed application source qualifier is connected to an imported winter tree source
definition and other source definitions. You cannot join a winter tree with other PeopleSoft
sources.

User Response:

Explanation:

You tried to import a non-PeopleSoft object in the Import from PeopleSoft dialog box.

User Response:

Import only PeopleSoft sources with the Import from PeopleSoft dialog box.

Explanation:

In the Import from PeopleSoft dialog box, you entered a database user name that does not
have SELECT permission on PeopleSoft metadata tables.

User Response:

Use a different user name or have the PeopleSoft administrator grant the user name the
necessary permissions.

Error! Cannot find PeopleSoft metadata from source <source name>!

Explanation:

In the Import from PeopleSoft dialog box, you entered a database user name that does not
have SELECT permission on PeopleSoft metadata tables.

User Response:

Use a different user name or have the PeopleSoft administrator grant the user the
appropriate permissions.

Explanation:

The user name entered in the Import from PeopleSoft dialog box does not have permission to
log in to the database.

User Response:

Use a different user name or have the database administrator grant the user the appropriate
permissions.

Error! This version of PeopleSoft source <source name> is not supported!

Explanation:

You tried to import a PeopleSoft source definition from a version of PeopleSoft that is not
supported by this version of PowerExchange for PeopleSoft.

User Response:

Only import source definitions or extract source data from supported versions of PeopleSoft.

Failed to log on to PeopleSoft database server.

Explanation:

The Designer was unable to access the PeopleSoft system database server. The network or
the database server might not be running properly.

User Response:

Make sure the network and database are running before trying again.

The language code <language code> specified is either invalid or not configured on the current PeopleSoft system.
Explanation:

Chapter 1: Client Messages

When importing a PeopleSoft source definition, you entered an invalid PeopleSoft language
code. The code is either not a valid PeopleSoft language code or not configured on the
PeopleSoft system you accessed.

User Response:

Enter a PeopleSoft language code that is configured for the PeopleSoft system you want to
access.

The specified Language Code <language code> is either invalid or not configured on the current PeopleSoft
System!
Explanation:

Failed to add menu item for import from Salesforce.com.

Explanation:

The Import from Salesforce.com menu item was not added to the Source Analyzer or the
Target Designer tool in the Designer.

User Response:

Shut down and restart the machine running the Designer. If the problem persists, contact
Informatica Global Customer Support.

Failed to create table. Reason: <error message>.

Explanation:

The Designer could not create a source or target definition based on an object imported from
Salesforce.com.

User Response:

See the additional error message for more information.

Login failed. Error code: <error code> Reason: <error message>.

Explanation:

The Designer could not connect to Salesforce.com.

User Response:

See the additional error message for more information.

The Source <source name> is associated with more than one Source Qualifier.
Explanation:

A source in the mapping is associated with multiple Application Source Qualifier

transformations. Each Salesforce source definition must be associated with exactly one
Application Source Qualifier transformation.

User Response:

If a source definition is associated with multiple Application Source Qualifier transformations,

remove the extra transformations and associate the source definition with a single Application
Source Qualifier.

PowerExchange for Salesforce.com Messages

The Source Qualifier <Application Source Qualifier name> has more than one PowerCenter Connect for
Salesforce.com source definition associated with it.
Explanation:

An Application Source Qualifier transformation in the mapping is associated with multiple

source definitions. To extract data from multiple Salesforce sources, you must have an
Application Source Qualifier for each source definition in the mapping.

User Response:

Associate each source definition in the mapping with a single Application Source Qualifier
transformation.

PowerExchange for SAP NetWeaver Messages

This section lists messages alphabetically for the following tasks:
Importing source definitions
Validating a filter condition
Validating a join condition
Validating SAP functions
Creating ABAP program variables
Cleaning ABAP programs
Generating and installing ABAP programs
Validating SAP mappings
Importing and exporting SAP mappings
Working with IDocs Using ALE
Data migration messages
Business content integration messages

Importing Source Definitions

A data source name must be selected or specified.
Explanation:

You tried to connect to the SAP system without entering a connect string.

User Response:

Select a connect string. Also verify that you have correctly configured the saprfc.ini file and
set the RFC_INI environment variable.

Cannot import selected object(s).

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

Error! Not all the selected items have been imported. <quantity> item(s) have been selected. However, only
<quantity> item(s) were added to the import list.

Explanation:

You tried to import a hierarchy definition that is empty. The hierarchy has no nodes.

User Response:

Import a hierarchy definition that contains nodes.

Explanation:

You selected to import some SAP functions that you have already imported in the repository.

Chapter 1: Client Messages

User Response:

Select SAP functions that you have not already imported in the repository.

Validating the Filter Condition

<Filter condition>: <operator> is not a legal relational operator.
Explanation:

The Designer does not recognize the relational operator used in the condition.

User Response:

Use a valid operator and verify spacing around the operator.

In the Application Source Qualifier <Application Source Qualifier name>, as Exec SQL option is selected Outer
Joins are not allowed.
Explanation:

You joined sources with an outer join and selected to generate the ABAP program using exec
SQL.

User Response:

Choose inner join to generate the ABAP program with exec SQL. When you generate the
ABAP program with exec SQL, the ABAP program joins sources using inner join.

In filter expression for <Application Source Qualifier name>: <filter condition>; <token>: constant or literal has to
follow an operator.
Explanation:

You cannot have a space in an operator, such as < =.

User Response:

Edit the filter expression and remove the space from the operator.

In filter expression for <Application Source Qualifier name>: <filter condition>; <table-field> is a reference to a field
not part of this source for which this filter expression is specified.
Explanation:

The source table specified to the left of the condition is not part of the condition.

User Response:

Edit the condition so that the source table specified to the left of the condition is also
specified in the condition.

Explanation:

User Response:

Remove the hierarchy from the filter condition.

Warning: Join Override for the first source <source> will be ignored. No syntax error detected.
Explanation:

The qualifying table is not the outer most table of the join order.

User Response:

Use the outer most table as the qualifying table in the join condition. For example, if the join
order is S1, S2, the override must be S2 = S2 = S1.

Validating SAP Functions

In the function <SAP function name> the parameter <parameter name> is specified as source field type with value
<source name-field name> but the source <source name> must precede this function call.
Explanation:

When you assigned a source field to a function parameter, you selected a source field from a
source table that the ABAP program has not selected.

User Response:

Select a source field from source tables above the SAP function in the ABAP program flow.

In the function <SAP function name> the value of the variable <variable name> does not match with the function
parameter <parameter name>.

Explanation:

After you assigned a variable to the function parameter, you modified the variable value. The
value of the variable no longer matches the function parameter.

User Response:

Click the Variables button in the ABAP program flow and modify the variable value to match
the function parameter.

Chapter 1: Client Messages

In the function <SAP function name> the parameter <parameter name> is specified as variable type but the
assigned variable <variable name> is not defined.
Explanation:

You removed the variable that you assigned to the function parameter.

User Response:

Click the Variable button in the ABAP program flow and define the variable again.

Creating ABAP Program Variables

Reserved keyword <key word> cannot be used.
Explanation:

You specified a variable name that contains a reserved key word. Variable names cannot
contain SAP datatype names, table, structure, or structure field names, or any ABAP key
word.

User Response:

Have the SAP administrator truncate YPMPRGSEQ and repopulate it using a different prefix.

Error obtaining program name from destination <connect string> for mapping <mapping name>.
Explanation:

RFC error.

User Response:

Contact the SAP administrator.

Error opening selected ABAP file with associated file viewer or Notepad.exe.
Explanation:

You do not have the file type associated with a viewer.

User Response:

Associate the file type.ab4 with the Wordpad or Notepad viewer.

PowerExchange for SAP NetWeaver Messages

In Application Source Qualifier <Application Source Qualifier name>, for ABAP join syntax, source <source name>
cannot be outer joined multiple sources.
Explanation:

Contact Informatica Global Customer Support.

Output Window Messages

You tried to install an ABAP program from an invalid file or a file that was generated from
another repository.

User Response:

Verify that you are installing a valid ABAP file and that you are connected to the repository
from which the ABAP program was generated.

You cannot have more than one Info Hierarchy coming into an Application SQ. Code generation for mapping
<mapping name> failed.
Explanation:

You tried to generate an ABAP program for a mapping that contains more than one hierarchy
definition in a single Application Source Qualifier.

User Response:

Edit the mapping to connect each hierarchy to an individual Application Source Qualifier.

You can have one and only one IDoc coming into an Application SQ. Join with other IDoc is not supported. Code
generation for mapping <mapping name> failed.
Explanation:

You tried to join two IDocs in one Application Source Qualifier.

You edited the XML file and deleted a name for the imported SAP table parameter.

User Response:

Check that there are no empty object names in the XML file. Or, re-export the SAP mapping
and import it again.

Error: No name for the imported SAP function instance parameter field.
Explanation:

You edited the XML file and deleted a function name or other function information.

User Response:

Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping
and import it again.

Error: No name for the import SAP function instance parameter.

Explanation:

BEGIN_CONTROL_RECORD not found. Need to get metadata for the control record.
Explanation:

The Designer cannot retrieve the IDoc metadata from the SAP system. The metadata for the
IDoc is not consistent.

User Response:

Validate the IDoc metadata.

Explanation:

SAP fetch error.

Create a request file in the currently specified directory.

No hierarchy catalog in the source system.

Explanation:

While creating a processing mapping, you clicked Send Request before selecting a hierarchy
DataSource in the Generate Mapping for BCI Wizard.

User Response:

Select a hierarchy DataSource before clicking Send Request to send the request to the SAP
system.

Registration is not complete. Please complete the registration before continuing.

Explanation:

There is no logical system in SAP for business content integration.

User Response:

Create a logical system for business content integration in SAP.

Change the GWSERV entry in the saprfc.ini file to point to the server on which the SAP
NetWeaver BI system is running.

PowerExchange for SAP NetWeaver BI Messages

When editing a TIBCO target definition, you wanted to add a group from the TIBCO metadata
tree as a column in the target definition. You also wanted to add fields from the group as
columns in the target definition. This is not allowed.

User Response:

If you want to add a group to a target definition, do not add any fields from the group to the
target definition.

Libraries related to TIBCO SDK metadata retrieval weren't appropriately installed.

Explanation:

TIB/Adapter SDK might not be properly installed.

User Response:

Verify that TIB/Adapter SDK is properly installed.

Chapter 1: Client Messages

Metadata for the TIBCO source/target is corrupt.

You wanted to import a TIBCO target definition from an XML object. However, the XML file is
corrupt. You might have attempted to change the XML file.

User Response:

Import the TIBCO source or target definition from a new XML object.

Unexpected error happened when trying to retrieve metadata from TIBCO Repository.
Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

Sequence header field is not applicable for target.

Explanation:

You wanted to import a TIBCO target definition from an XML object. However, the XML file is
corrupt. You might have attempted to change the XML file.

User Response:

Import the TIBCO source or target definition from a new XML object.

PowerExchange for TIBCO Messages

PowerExchange for webMethods Messages

Conversion from the source to target failed.
Explanation:

The Designer could not convert the source definition to a target definition.

User Response:

See the additional error message for more information.

Document type <document type name> contains field <field name>, which is of an unsupported datatype.
Explanation:

You tried to import a document type as a webMethods source or target definition. However,
the document type contains a field, which uses an unsupported datatype. As a result, the
Designer could not import the source or target definition.

User Response:

Make sure that any document types you want to import as webMethods source or target
definitions contain fields that use datatypes that PowerCenter supports.

Envelope field <field name> is invalid or uses the datatype <datatype>, which does not match the data for the field.
Explanation:

You wanted to import a repository object that represents a webMethods source or target
definition from an XML file. However, the datatype for an envelope field is invalid in the XML
file. The XML file may have been modified.
The envelope field is invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

Error from the webMethods Broker: <error message>.

Explanation:

The Designer encountered an error from the webMethods Broker.

User Response:

See the additional error message for more information.

Failed to add a menu item.

Explanation:

Internal error.

The Designer could not import the source or target definition, because PowerExchange for
webMethods is not properly installed.

User Response:

Reinstall PowerExchange for webMethods.

Chapter 1: Client Messages

The Map attribute value for field <field name> is empty.

Explanation:

You wanted to import a repository object that represents a webMethods source or target
definition from an XML file. However, the Map attribute value for a field in the XML file is
invalid. The XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

The Map attribute value <map value> for field <field name> already exists.
Explanation:

You wanted to import a repository object that represents a webMethods source or target
definition from an XML file. However, the Map attribute value for a field is duplicated. The
XML file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

There should be exactly one group.

Explanation:

You wanted to import a repository object that represents a webMethods source or target
definition from an XML file. However, there is more than one group in the XML file. The XML
file may have been modified.

User Response:

Import the repository object from a new XML file. Avoid editing the XML file before importing.

Explanation:

The SOAP request contains elements that the SOAP server does not recognize.

User Response:

PowerExchange for Web Services Messages

Invalid SOAP Request. Element <element name> does not exist.

Explanation:

The SOAP request is missing an element.

User Response:

Reimport the web service operation and run the session again.
Use a SOAP development tool to generate a SOAP request from the WSDL file. You can
replace the current SOAP request with the one that you generate.

Invalid SOAP Request. Failed to process at <element name>.

Explanation:

The SOAP request contains an invalid element.

User Response:

Invalid SOAP Request. Operation cannot be found.

Explanation:

The SOAP request does not specify a web service operation.

User Response:

Invalid SOAP Request. The SOAP Operation parameters in the request are inconsistent with the WSDL file.
Explanation:

User Response:

None.

Unable to delete links from an MQ Source Qualifier transformation to an associated source qualifier transformation.
Explanation:

You tried to delete the link between MQ Source Qualifier and the associated source qualifier.

User Response:

To delete the link, remove the association between the MQ Source Qualifier and the
associated source qualifier in the Edit Transformation dialog box of the MQ Source Qualifier.

VSAM, XML, MQ sources connect to exactly one source qualifier transformation.

User Response:

Remove the duplicate reference ports.

A reference port can be created only in the XML root group.

Explanation:

A non-root group in an XML Generator transformation contains a reference port.

User Response:

Remove the invalid reference port.

Source: <source> is not part of the Source Join Order.

Explanation:

The Designer does not recognize the sources for the source join order.

User Response:

The XML file has fewer elements than the pivot value specified. Element <element name> appears only <number>
times in the XML file.
Explanation:

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

User Response:

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.

The XML metadata is invalid.

Explanation:

The XML definition contains inconsistencies.

User Response:

The XML definition is unusable. You must recreate it.

You cannot have a pivoted column and an unpivoted column referring to the same element. Column <column
name> is pivoted while column <column name> is not.
Explanation:

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

User Response:

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.

XML Messages

CHAPTER 2

Informatica Administrator Messages

This chapter includes the following topic:
Informatica Administrator Messages, 28

Informatica Administrator Messages

Correct the validation errors in <field name> and try the update again. <error message>.
Explanation:

A validation error occurs when data cannot be validated for some reason. For example, if you
enter text into a field that requires an integer, the data cannot be validated because it is the
wrong type of data.

User Response:

Read the error description and make any necessary changes. For example, if the error
description indicates that an integer value is required in the field, enter an integer value
instead of a text value. For more information, look up the cause and action for the error code.

The Domain Service could not disable the process due to the following error: <error message>.
Explanation:

The Service Manager encountered a problem while disabling the service process. The
service process may have been starting up when you attempted to enable it.

User Response:

Read the error description and make any necessary changes. For more information, look up
the cause and action for the error code.

The Domain Service could not disable the service due to the following error: <error message>.
Explanation:

The Service Manager encountered a problem while disabling the service. The service may
have already been disabled, or it may have been in the process of starting up.

User Response:

Read the error description and make any necessary changes. For example, if the service was
in the process of being enabled when you attempted to disable it, wait for the service to
become enabled before trying to disable it. For more information, look up the cause and
action for the error code.

The Domain Service could not enable the process due to the following error: <error message>.

Explanation:

The Service Manager encountered a problem while enabling the service process. The service
process may have been shutting down when you attempted to enable it, or the node where
the service process runs may not be available.

User Response:

Read the error description and make any necessary changes. For more information, look up
the cause and action for the error code.

The Domain Service could not enable the service due to the following error: <error message>.
Explanation:

The Service Manager could not enable the service when you clicked the Enable button. This
error may appear, for example, if the service was shutting down when you attempted to
enable it.

User Response:

Read the error description and make any necessary changes. For example, if the shutdown
operation was incomplete when you attempted to enable the service, wait until the service is
completely shut down before clicking the Enable button. For more information, look up the
cause and action for the error code.

Enter a valid location for the shared configuration on the node <node name>.
Explanation:

No location was supplied for the shared configuration file.

The Service Manager could not enable the service when you attempted to create it. This error
may appear, for example, if the node you specified to run the service is unavailable.

User Response:

Read the error description and make any necessary changes. For example, if the error
description indicates that the node is unavailable, either restart the node or configure the
service to run on a different node. For more information, look up the cause and action for the
error code.

Informatica Administrator Messages

This key was already used to update the license. Please use another key for the update.
Explanation:

The same key cannot be used more than once to update a license.

User Response:

Verify that you are using the correct key to update the license.

The location of the shared configuration files for some of the nodes could not be determined. Verify that all nodes
are running.
Explanation:

The Service Manager could not determine the location of shared configuration files. This
problem can occur if node is not running or if the connection to the node fails.

User Response:

Verify that all the nodes in the domain are running.

Logs for specified query could not be exported because of the following error. Error - <error message>.
Explanation:

The Service Manager could not export logs for a query.

User Response:

Read the error description and make any necessary changes. For more information, look up
the cause and action for the error code.

Logs for specified query could not be fetched because of the following error. Error - <error message>.
Explanation:

The Service Manager could not fetch logs for the query.

User Response:

Read the error description and make any necessary changes. For more information, look up
the cause and action for the error code.

Logs for specified query could not be purged because of the following error. Error - <error message>.
Explanation:

The Service Manager could not purge logs for a query.

User Response:

Read the error description and make any necessary changes. For more information, look up
the cause and action for the error code.

More than one group is being mapped to group <name>. Only one group can be merged with a group in the
domain. Correct group <name> and try again.
Explanation:

When you upgrade groups in the repository, you are trying to map multiple groups in the
selected domain to a single group in the PowerCenter domain. For example, you cannot map
groups Sales and sales in the selected domain to group Sales in the PowerCenter
domain. In the PowerCenter domain, group names are not case sensitive.

User Response:

Rename the group in the selected domain or merge one of the groups in the selected domain
with a different group in the PowerCenter domain.

More than one user is being mapped to user <name>. Only one user can be merged with a user in the domain.
Correct user <name> and try again.
Explanation:

When you upgrade users in the repository, you are trying to map multiple users in the
selected domain to a single user in the PowerCenter domain. For example, you cannot map
users RSmith and rsmith in the selected domain to user RSmith in the PowerCenter
domain. In the PowerCenter domain, user names are not case sensitive.

User Response:

Rename the user in the selected domain or merge one of the users in the selected domain
with a different user in the PowerCenter domain.

None of selected nodes are running. Select at least one node that can be connected to run the Gateway Service.
Explanation:

The nodes you designated as gateway nodes have been shut down.

Chapter 2: Informatica Administrator Messages

User Response:

Start up one of the designated gateway nodes. Alternatively, configure a node that is running
to serve as a gateway.

You cannot remove node <node name> because it is the only gateway in the domain.
Explanation:

All domains require at least one gateway node. You cannot remove a gateway node if it is the
only gateway in the domain.

User Response:

If you have the high availability option, create another gateway node for the domain before
removing this gateway.

Informatica Administrator Messages

CHAPTER 3

A Message Codes
This chapter includes the following topics:
ADV Messages, 32
ALERT Messages, 32
ATHR Messages, 33
AUTH Messages, 35
AUTHEN Messages, 39

ADV Messages
ADV_13226

Could not open the following dll: <dynamic link library name>.The reason is: <error message>.

Explanation:

The Integration Service cannot load an external Custom transformation library that is
dependent on other libraries.

User Response:

See the additional error message for more information.

Verify that the master gateway node is running on the domain.

ATHR Messages
ATHR_10000

The Service Manager is not initialized yet.

Explanation:

The Tomcat servlet container has not initialized the Service Manager.

User Response:

The Service Manager is still initializing. If the Service Manager is not initialized within five
minutes, contact Informatica Global Customer Support.

Chapter 3: A Message Codes

User Response:

Users can only access objects with reference to the repository they logged in to.

ATHR_10022

The Service Manager denied authorization access for user <user name> as service\folder is
wrongly specified: <service and folder>.

Explanation:

A user was trying to access a service and folder that was not specified correctly.

User Response:

The user should ask the domain administrator to perform desired request.

AUTH Messages
AUTH_10000

The Service Manager could not enable Authentication because authentication state is invalid.

Explanation:

The network shared disk that stores the domain configuration data is not accessible.

User Response:

Ensure access to the shared disk that stores the domain configuration database.

Explanation:

Node configuration is not synchronized with the domain configuration.

User Response:

Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix
the node configuration with infacmd.

Explanation:

Explanation:

Cannot create a user with the same name as an existing user.

User Response:

Use a different user name to create a user.

AUTH_10009

Cannot remove the Administrator user.

Authentication data is invalid as it contains no users.

Explanation:

The authentication data is invalid within the domain configuration database.

User Response:

Chapter 3: A Message Codes

AUTH_10015

A request for operation <operation name> required input that was not supplied.

Explanation:

The input required by the operation was not provided.

User Response:

Contact Informatica Global Customer Support.

AUTH_10016

A request cannot be performed as user <user name> cannot be found.

Explanation:

An attempt was made to update user data, but the Service Manager could not authenticate
the user specified in the request.

User Response:

If the error displays because of a user request, resubmit the request with a valid user name.
You might need to recreate the user.

AUTH_10018

A request for operation <operation name> expected input of type <expected input type>, but
was supplied with <actual input type>.

Explanation:

The authentication data is invalid within the domain configuration database.

User Response:

AUTH_10024

Message request failed because the message contained invalid credentials that were not
recognized by the system.

Explanation:

The message request contained invalid credentials.

User Response:

If error displays because of a user request, the user must log in again and resubmit the
request to get a valid credential. Otherwise, contact Informatica Global Customer Support.

AUTH_10026

The thread was interrupted while associating node <node name> with the domain.

Explanation:

A problem occurred with threads while associating a node.

User Response:

Try again. If the problem persists, then contact Informatica Global Customer Support.

AUTH_10027

The user <user name> associated with node <node name> was not found in the domain.

Explanation:

The user specified in the node was not found in the domain.

User Response:

Either add the user in the domain or redefine node with a user.

AUTH Messages

AUTH_10028

The password associated with node <node name> is invalid.

Explanation:

The user password provided with the node did not match the password in the domain
configuration database.

User Response:

Redefine the node with the correct password.

AUTH_10029

The node <node name> is not associated in the domain.

Explanation:

The node is not associated.

User Response:

Redefine the node.

AUTH_10030

User <user name> was not associated with node <node name>.

Explanation:

The user specified in the node configuration does not match the domain configuration.

User Response:

Either modify the user in the domain node or redefine node with the same user as the domain
node.

AUTH_10031

The host name for node <node name> is inconsistent between node configuration and
domain configuration.

AUTH_10033

The gateway setting for node <node name> is inconsistent between node configuration and
domain configuration.

Explanation:

You configure a gateway node in the domain properties and in the node properties. The node
is configured as a gateway node in one location and as a worker node in the other location.

User Response:

Update the domain or node properties so that the node is configured as a gateway node or a
worker node in both locations.

AUTH_10036

User <user name> does not have permission on any object within the domain.

Explanation:

The user trying to log in does not have any permission within the domain.

User Response:

The user should ask the domain administrator to add permissions for the user or remove the
user.

AUTH_10037

Domain <domain name> for Repository Service <Repository Service name> is not linked
within this domain.

Explanation:

The user trying to log in through this domain for service not used within this domain.

Chapter 3: A Message Codes

User Response:

The user should log directly in to the Repository Service domain or define the link.

Explanation:

The ABAP datatype in the status or text field for the RETURN parameter in the BAPI/RFC
transformation is not CHAR or NUMC.

User Response:

Set the ABAP datatype to CHAR or NUMC in the status or text field for the RETURN
parameter in the BAPI/RFC transformation.

BAPI_99106

Could not find the STATUS field [{0}] in the RETURN structure.

Explanation:

A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC
transformation.

User Response:

Specify a valid value in the status field for the RETURN structure in the BAPI/RFC
transformation.

BAPI_99107

Could not find the TEXT field [{0}] in the RETURN structure.

Explanation:

A valid value in the text field for the return structure is not specified in the BAPI/RFC
transformation.

User Response:

Specify a valid value in the text field or the return structure in the BAPI/RFC transformation.

BAPI_99109

Could not read the internal table for the function table parameter.

Explanation:

A BAPI/RFC transformation imported from another repository or folder that was modified
before it was imported. As a result, the Integration Service could not read the internal table
for the function table parameter.

User Response:

Export and import the BAPI/RFC transformation again.

BAPI_99113

Exception <exception> has been raised from the RFC function call with IntegrationID
<integration_ID>.

Explanation:

The RFC call to the SAP system from the SAP application server failed.

User Response:

Enter valid input data for the SAP system. Verify that the SAP application server is running.

BAPI_99116

The Integration Service could not create an SAP internal table for function table parameter
[{0}].

Explanation:

The Integration Service could not create an SAP internal table. The node where the
Integration Service process runs might be out of memory.

User Response:

Verify that the machine on which the node resides has enough memory.

BAPI_99118

The Integration Service could not find field [{0}] in the RETURN structure.

Explanation:

A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC
transformation.

User Response:

Specify a valid value in the status field for the RETURN structure in the BAPI/RFC
transformation.

BAPI_99129

Commit call to SAP failed.

Explanation:

The Integration Service could not make a commit function call to SAP.

User Response:

See the error messages in the session log for more information.

BAPI_99133

The Integration Service could not connect to SAP.

Explanation:

Connection information in the BAPI/RFC application connection is invalid.

User Response:

Verify the connection parameters.

Explanation:

An SAP system error occurred.

User Response:

See the additional error message for more information.

BAPI Messages

BAPI_99135

Data overflow occurred when the Integration Service applied default value <value> to function
parameter <function parameter name> for Integration ID <ID number>.

Explanation:

The Integration Service could not copy the default values of the parameter. The parameter
value does not comply with the parameter metadata. For example, it might not have the
correct length, scale, or precision.

User Response:

Verify that the value complies with the metadata of the parameter.

BAPI_99136

Data <data> overflow at port <port number> for Integration ID <ID number>.

Explanation:

The Integration Service could not copy the input data for the parameter. The parameter value
does not comply with the parameter metadata. For example, it might not have the correct
length, scale, or precision.

User Response:

Verify that the value complies with the metadata of the parameter.

BAPI_99137

Data overflow occurred when the Integration Service applied the default value <value> to the
field <field name> for the Legacy Key <legacy key value>.

Explanation:

The Integration Service could not copy the default values of the field. The field value does not
comply with the field metadata. For example, it might not have the correct length, scale, or
precision.

User Response:

Verify that the field value complies with the metadata of the field.

BAPI_99138

Data conversion error for port <port number> with data <data>.

Explanation:

The SAP system might have sent data with a precision or scale that does not comply with the
parameter metadata.

Explanation:

The Integration Service failed to initialize the reader.

User Response:

Check the session log for related error messages. If no other messages appear, contact
Informatica Global Customer Support.

BR_16004

ERROR: Prepare failed.

Explanation:

The Integration Service failed to prepare the SQL query for the Source Qualifier
transformation.

User Response:

Validate the mapping in the Designer.

Explanation:

Either you terminated the session during the reader process, or the Integration Service
terminated the reader process because of internal errors.

User Response:

Validate the mapping in the Designer and run the session again. If the session fails, contact
Informatica Global Customer Support.

BR Messages

BR_16045

Reader run terminating. Error threshold <maximum number of errors> reached reading data
from <file name>.

Explanation:

The Integration Service reached the error threshold reading data from a source file.

User Response:

See the previous error in the session log.

BR_16046

User defined query <query name> has references to mapping parameters or variable that
cannot be resolved correctly.

Explanation:

The Integration Service encountered an error while expanding referenced parameters and
variables in the specified query.

User Response:

Make sure you declare the parameters and variables in the specified query and have valid
start values.

BR_16047

User defined join condition and/or source filter <condition name> has references to mapping
parameters or variable that cannot be resolved correctly.

Explanation:

The Integration Service encountered an error while expanding referenced parameters and
variables in the specified join or filter condition.

User Response:

Make sure you declare the parameters and variables in the specified join or filter condition
and have valid start values.

BR_16048

User defined source filter condition <condition name> has references to mapping parameters
or variables that cannot be resolved correctly.

Explanation:

The Integration Service encountered an error while expanding parameters and variables in
the specified filter condition.

User Response:

Make sure you declare the parameters and variables in the specified string and that they
have valid start values.

BR_16050

User provided string <string value> has references to mapping parameters or variables that
cannot be resolved correctly.

Explanation:

The Integration Service encountered an error while expanding parameters and variables in
the specified string.

User Response:

Make sure you declare the parameters and variables in the specified string and that they
have valid start values.

BR_16056

FTP Information in the repository is corrupt.

Explanation:

The repository contains inconsistent FTP information.

User Response:

Contact Informatica Global Customer Support.

BTree Messages

BTree_90002

Error: Specified cache size is too small. It must be larger than <size>.

Explanation:

The session failed because the cache size specified for the transformation is insufficient.

User Response:

In the session properties, increase the cache size.

The cache directory has inadequate disk space.

User Response:

Check the disk for free space.

BTree_90011

Error inserting a row into the foreign key index for group <group>.

Explanation:

The Integration Service does not have write permission on the cache directory.

User Response:

Verify that the user configured to start Informatica services has write permission on the cache
directory.

Explanation:

The cache directory has inadequate disk space.

User Response:

Check the disk for free space.

BTree_90012

Error inserting a row into the primary key index for group <group>.

Explanation:

The Integration Service does not have write permission on the cache directory.

BTree Messages

User Response:

Verify that the user configured to start Informatica services has write permission on the cache
directory.

Explanation:

The cache directory has inadequate disk space.

User Response:

Check the disk for free space.

BTree_90013

Error: Cannot remove duplicate row.

Explanation:

The Integration Service does not have write permission on the cache directory.

User Response:

Verify that the user configured to start Informatica services has write permission on the cache
directory.

Explanation:

The cache directory has inadequate disk space.

Cannot connect to Integration Service <Integration Service name> in domain <domain name>.

Explanation:

The connection setting for the Integration Service is incorrect.

User Response:

Verify that the Integration Service is running. Check the user name, password, hostname,
and port number settings for the Integration Service.

BW_41014

The BW Server sent a request to the SAP BW Service that did not include a PowerCenter
workflow name.

Explanation:

The 3rd Party Selection tab of the InfoPackage does not include a PowerCenter workflow
name.

User Response:

Specify a PowerCenter workflow name in the 3rd Party Selection tab of the InfoPackage.

BW_41020

Connect to SAP gateway failed.

Explanation:

The RFC destination or the destination entry in saprfc.ini is incorrect.

User Response:

Change the RFC destination or the destination entry in saprfc.ini.

Chapter 4: B Message Codes

BW_41027

The Integration Service could not prepare the data in row number <row number> for the BW
target <target name>.

Explanation:

The source data contains invalid data for the row.

User Response:

Correct the source data so that it matches the datatype, scale, and precision for the fields in
the target definition.

BW_41031

The SAP BW Service could not open the parameter file <parameter file> for data selection:
<data selection>.

Explanation:

The Parameter File Directory property for the SAP BW Service contains a directory that does
not exist or that does not have read and write permissions enabled.

User Response:

In the Administrator tool, verify that the Parameter File Directory property contains a valid
directory on the node where the SAP BW Service process runs. Also verify that the directory
has read and write permissions enabled.

BW_41044

Data selection was specified in the SAP BW InfoPackage but input value in 3rd party selection
is not of the form Folder:Workflow:Session. The workflow name will be used as the session
name in the parameter file header.

Explanation:

The SAP NetWeaver BI server sent a request to the SAP BW Service that contains a data
selection entry, but does not specify the workflow name on the 3rd Party Selection tab in the
correct format.

User Response:

Enter the workflow name in the 3rd Party Selections tab in the InfoPackage using the format
<PowerCenter folder name>:<PowerCenter workflow name>:<PowerCenter session name>.

BW_41052

The SAP BW Service could not connect to the Integration Service.

Explanation:

The Integration Service may not be running. Or the SAP BW Service contains incorrect
connection information for the associated Integration Service.

User Response:

Verify that the Integration Service is running. Or in the Administrator tool, verify that the SAP
BW Service contains correct connection information for the Integration Service.

BW_41058

The SAP BW Service reached the maximum number of errors trying to connect to the BW
system. The SAP BW Service will be shut down.

Explanation:

The SAP BW Service tried to connect to the SAP NetWeaver BI system five times without
succeeding.

User Response:

Verify that the saprfc.ini file is configured correctly.

BW_41065

Workflow Start request failed with message <error message>.

Explanation:

The Integration Service could not start the SAP NetWeaver BI workflow for the reason
specified in the message.

User Response:

Correct the problem specified in the message and restart the workflow.

BW_41073

The SAP BW Service received a call to the unsupported function <function>.

Explanation:

The SAP BW Service received an RFC call from the SAP NetWeaver BI system for a function
that is not registered to the SAP BW Service.

User Response:

Use the RFC Destination created for the SAP BW Service in the SAP NetWeaver BI system
for data loading purposes only.

BW Messages

BW_41076

Error fetching the SAP BW Service configuration properties: <properties>.

Explanation:

The SAP BW Service could not be started because the service contains properties with
invalid values.

User Response:

In the Administrator tool, verify that the SAP BW Service properties are configured correctly.

BW_41077

Error initializing service.

Explanation:

The SAP BW Service could not initialize the LMAPI service because it could not connect to
the Integration Service.

User Response:

Verify that the Integration Service is running. Or in the Administrator tool, verify that the SAP
BW Service contains correct connection information for the Integration Service.

BW_41082

The SAP BW Service could not find the Integration Service <Integration Service name> in
domain <domain name>.

Explanation:

The SAP BW Service could not find the Integration Service in the domain specified in the 3rd
Party Selection tab of the InfoPackage. The values for the domain and Integration Service
name properties might be invalid.

User Response:

In the SAP NetWeaver BI system, verify that the domain and Integration Service name
entered in the 3rd Party Selection tab are valid.

Explanation:

The Integration Service might not be enabled.

User Response:

Verify that the Integration Service is enabled.

Chapter 4: B Message Codes

CHAPTER 5

C Message Codes
This chapter includes the following topics:
CFG Messages, 49
CMD Messages, 56
CMN Messages, 57
CNX Messages, 88
CONF Messages, 88
CSE Messages, 89
CTSDK Messages, 90

CFG Messages
CFG_10000

The Service Manager could not enable Domain Configuration because the domain state is
invalid.

Explanation:

The network shared disk that stores the domain configuration database is not accessible.

CFG_10029

Linked domain <linked domain name> cannot be found in the domain.

Explanation:

A request was received to access a linked domain that could not be found.

CFG Messages

User Response:

Contact Informatica Global Customer Support to extend the license.

Either assign permission to that user to access the node or choose a user who has node
permission.

CFG_10049

Cannot associate a gateway node <node name> without specifying the log directory.

Explanation:

A request was received to associate a gateway node without the log directory being specified.

User Response:

Verify that the log directory is specified.

CFG_10050

Cannot switch to or from a gateway node with the update operation.

Explanation:

A request was received to switch gateway status for a node.

User Response:

Use the switchToGatewayNode or the switchToWorkerNode commands, or change the

gateway status in the Administrator tool.

CFG_10051

User <user name> cannot be found.

Explanation:

A request was received to update a node with a login user that is not defined in the domain.

User Response:

Choose a user who has node permission.

CFG_10052

Cannot unassociate node <node name> while it is running.

Explanation:

An attempt was made to unassociate a running node.

User Response:

Shutdown the node first.

CFG_10055

The domain configuration database is invalid because: <validation message>.

Explanation:

The domain configuration database is invalid.

CFG Messages

User Response:

CFG_10057

Unable to connect to the linked domain <domain name> because: <error message>.

Explanation:

The domain cannot communicate with the linked domain specified.

User Response:

Verify that the Service Manager on the linked domain is running and that its gateway
host:port address is correct.

CFG_10059

Cannot associate node <node name> without redefining the node.

Explanation:

A request was received to associate a node that was probably unassociated and has not
been redefined.

User Response:

Use infacmd defineGatewayNode or defineWorkerNode command to redefine the node.

CFG_10060

The administrator permissions on the root folder cannot be removed.

Explanation:

The operating mode cannot be changed to safe while the service is enabled.

User Response:

Disable the service first.

CFG_10084

Cannot move the root folder.

Explanation:

A request was received to move the root folder.

User Response:

None. You cannot perform this protected operation.

Chapter 5: C Message Codes

CFG_10085

Cannot move a folder to one of its subfolders.

Explanation:

A request was received to move folder to one of its subfolders.

User Response:

Select a different target location.

CFG_10086

Cannot perform operation on an unassociated node <node name>.

Explanation:

An attempt was made to perform an operation on an unassociated node.

User Response:

Verify that the database connectivity information specified for the domain is correct.

Explanation:

The domain configuration database has invalid data.

User Response:

Contact Informatica Global Customer Support. Before restoring the domain configuration
database from the last known good backup file, first back up the invalid domain configuration
database to another file to help Informatica Global Customer Support troubleshoot the
problem.

CFG_10103

Cannot enable service <service name> with the same name as the domain. Rename your
service.

Explanation:

An application service cannot have the same name as the PowerCenter domain. You
upgraded a Repository Service, Integration Service, SAP BW Service, or Web Services Hub
from a previous version that had the same name as the PowerCenter domain.

CFG Messages

User Response:

Create the Integration Service, SAP BW Service, or Web Services Hub with a different name.
Remove the application service with the invalid name.
In the previous version, back up and restore the repository to a Repository Service with a
different name. Remove the Repository Service with the invalid name.

CFG_10104

Cannot add service <service name> with the same name as the domain. Rename your service.

Explanation:

An application service cannot have the same name as the PowerCenter domain.

User Response:

Enter a different name for the application service.

CFG_10105

The code page of an existing Repository Service <Repository Service name> cannot be
changed.

Explanation:

After a Repository Service is created, the code page cannot be changed in the Repository
Service properties.

User Response:

To change the repository code page, back up the repository and restore it to a new
Repository Service. When you create the new Repository Service, you can specify a
compatible code page.

CFG_10106

Cannot create an OS profile with the system user name set to root because this may result in
a security breach.

User Response:

Assign a different operating system user to the OS profile.

CFG_10107

Cannot start the service upgrade process as the following services have already been
upgraded to version <service version>: <list of service>

User Response:

Verify that the service requires an upgrade or contact Informatica Global Customer Support.

CFG_10110

Cannot upgrade the services because the list of services received by the domain contains
one or more services that do not depend on the Repository Service.

User Response:

Contact Informatica Global Customer Support.

CFG_10111

Cannot upgrade services as the list of services received by the domain does not contain one
or more dependent services.

User Response:

Contact Informatica Global Customer Support.

CFG_10116

The version of the domain <domain name> is different from the version of the current domain.
Upgrade the domain to version <domain version>.

User Response:

Upgrade the domain to the current domain version before you add it to the current domain.

CMD Messages

CMD_35197

The Value <value> for INFA_CLIENT_RESILIENCE_TIMEOUT is invalid. Using default value

<value> instead.

Explanation:

The environment variable INFA_CLIENT_RESILIENCE_TIMEOUT is set to an invalid value.

User Response:

Change the value to 0 or any positive integer.

Chapter 5: C Message Codes

CMD_35198

Error: Cannot connect to Integration Service.

Explanation:

You can use the environment variable INFA_DOMAINS_FILE to store the domains.infa path.
You will receive an error if the environment variable INFA_DOMAINS_FILE is not set.

User Response:

Add the environment variable, INFA_DOMAINS_FILE, and set the path to the domains.infa
file. By default, the domains.infa file resides in the PowerCenter directory.

CMN_1011

Error allocating system shared memory of <number> bytes for [DTM Buffer Pool]. Error is
<system error code>: <system error message>.

Database driver event.

Explanation:

A database driver event occurred.

Response:

Contact Informatica Global Customer Support.

CMN_1035

Sybase event.

Explanation:

A Sybase event has occurred.

User Response:

User Response:

Check the session log for a related Oracle error message. If necessary, see the Oracle
documentation for appropriate action.

CMN_1040

SQL Server Error.

Explanation:

A Microsoft SQL Server error has occurred.

User Response:

Check the session log for a related Microsoft SQL Server error message. If necessary, see
the Microsoft SQL Server documentation for appropriate action.

CMN_1044

DB2 Error.

Explanation:

A DB2 error has occurred.

User Response:

Check the session log for a related DB2 error message. If necessary, see the DB2
documentation for appropriate action.

CMN_1046

ODBC Error.

Explanation:

You created an ODBC data source, but no longer have the underlying native connectivity
software or environment.

User Response:

Reconfigure the native connectivity environment and then run the session.

Explanation:

A session with DB2 UDB EEE sources or targets failed when the Integration Service ran on
AIX and used both the DataDirect ODBC driver manager and the DB2 UDB EEE CAE ODBC
driver. This problem occurred because the DataDirect ODBC driver manager and the DB2
UDB EEE CAE ODBC driver are not compatible.

User Response:

Do not use an ODBC connection. Be sure to only use a native DB2 CAE connection to a DB2
database.

This message varies depending on the error. Check the session log for more specific
messages.

CMN_1054

Memory allocation error.

Explanation:

Error in memory allocation. The system resources may be low.

User Response:

Close any unnecessary applications and restart the system. If the problem persists, you may
need to add RAM to the system.

This message should be followed by information naming the port or table. Correct the port
name or datatype in the Lookup transformation, and save the mapping.

Explanation:

The Integration Service failed to connect to the database containing the lookup table. You
may have logged in incorrectly.

User Response:

Explanation:

The Integration Service failed to connect to the database containing the lookup table. The
database containing the lookup table may be down.

User Response:

Make sure the database is up before running the session again.

CMN_1065

Error in lookup SQL statement execute.

Explanation:

A port name or datatype specified in a Lookup transformation does not match the lookup
table in the database. Both port names and datatypes must match exactly.

User Response:

This message should be followed by information naming the port or table. Correct the port
name or datatype in the Lookup transformation, and save the mapping.

Explanation:

The Integration Service failed to connect to the database containing the lookup table. You
may have logged in incorrectly.

User Response:

Explanation:

The Integration Service failed to connect to the database containing the lookup table. The
database containing the lookup table may be down.

User Response:

Make sure the database is up before running the session again.

CMN_1066

Error in lookup SQL statement fetch.

Explanation:

A port name or datatype specified in a Lookup transformation does not match the lookup
table in the database. Both port names and datatypes must match exactly.

User Response:

This message should be followed by information naming the port or table. Correct the port
name or datatype in the Lookup transformation, and save the mapping.

CMN Messages

Explanation:

The Integration Service failed to connect to the database containing the lookup table. You
may have logged in incorrectly.

User Response:

User Response:

Contact Informatica Global Customer Support.

CMN_1079

WARNING: Lookup table contains no data.

Explanation:

The lookup table specified in the mapping contains no data because you specified an invalid
lookup table.

User Response:

Make sure the mapping contains the correct name of the lookup table.

Explanation:

The lookup table specified in the mapping is empty.

User Response:

Import or enter the correct data for the lookup table.

CMN_1082

ERROR: Invalid lookup condition.

Explanation:

In a Lookup transformation, the lookup condition is invalid or blank.

User Response:

Correct the invalid lookup condition.

CMN_1083

Error encountered encrypting password.

Explanation:

Explanation:

A Joiner transformation in the mapping specifies an invalid join condition.

User Response:

Make sure the condition for each Joiner transformation in the session contains at least one
valid join.

Explanation:

If each Joiner transformation uses valid conditions, you may have repository inconsistencies.

User Response:

Contact Informatica Global Customer Support.

CMN_1094

ERROR: No valid field from the master relation.

Explanation:

One of the Joiner transformations in the mapping has a master port that is not used in the
join condition or the output port.

Edit the join condition in the session properties, using an equal sign (=) as an operator.

CMN_1097

ERROR: No valid output field.

Explanation:

A Joiner transformation has no output links. Each Joiner transformation needs to have at
least one output link.

User Response:

Make sure each Joiner transformation has at least one linked output port.

CMN_1098

ERROR: Cache Directory may not exist or insufficient privilege/space in the supplied cache
directory.

Explanation:

The directory specified for the index and data caches has run out of memory.

User Response:

Free up disk space in the cache directory.

Explanation:

The Informatica services account or the operating system user in the operating system profile
does not have the appropriate privileges to access that directory.

User Response:

Grant write permission on the directory to the Informatica services account or the operating
system user in the operating system profile.

CMN_1099

ERROR: Master and detail relations are flipped from user specification.

Explanation:

In the mapping, one Source Qualifier transformation has been linked to two Joiner
transformations in the same target load order group, and has been specified as the master
source in one Joiner transformation and the detail source in the other.

User Response:

Edit the Joiner transformations so the same Source Qualifier transformation is the master
source in both Joiner transformations in the same target load order group.
If you need to keep the Source Qualifier transformation as the master source in one Joiner
transformation and the detail source in the other, create a separate target load order group
and place one of the Joiner transformations in that second group.

CMN_1100

ERROR: A target load order group has at least one Source Qualifier transformation that has
been used to provide master as well as detail data.

Explanation:

User Response:

User Response:

In the Designer, validate the mapping to locate the invalid conversion.

CMN_1105

ERROR populating index using the key value from the master relation row.

Explanation:

The index cache ran out of memory, causing the Integration Service to use the index file at a
local directory that ran out of disk space as well.

User Response:

This message is preceded by a file error. Correct the file error before running the session
again.

CMN Messages

CMN_1111

Error encountered decrypting PowerMart password.

Explanation:

The Integration Service encountered an invalid password in the Administrator tool.

The Integration Service on UNIX tried to load Microsoft SQL Server as a target database
using native drivers. The Integration Service on UNIX does not support Microsoft SQL Server
database type.

User Response:

Use the DataDirect ODBC SQL Server driver for UNIX to load Microsoft SQL Server.

CMN_1141

ERROR: Unexpected condition at file <file name> line <line number>. Application terminating.
Contact Informatica Global Customer Support for assistance.

Explanation:

An application error occurred.

Note the file name and line number and contact Informatica Global Customer Support.

CMN_1164

Database driver error. Bulk write initialization failed (blk_init returned failure).

Explanation:

The session failed because you loaded to Sybase 11 and configured the Table Name Prefix
option in the mapping target instance or in the session properties.

User Response:

If you load to multiple Sybase 11 tables with different owners, create views of all the target
tables in one database. Ensure that the owner of the views has all required permissions on
the target tables. Create the database connection in the Workflow Manager using the target
owner as the user in the connection. Or, if the target tables have the same owner, make sure
the user in the database connection is the owner of the targets.

CMN_1555

The mapping was changed after the saved disk cache file was created.

User Response:

Recache the lookup source.

CMN_1557

The precision is different from the saved disk cache.

Explanation:

The Lookup transformation uses a persistent named cache, and the high precision option for
the session was enabled or disabled between session runs. The precision setting for the
session differs from the precision setting for the lookup cache.

User Response:

Recache the lookup source, or change the high precision setting to the previous setting.

CMN Messages

CMN_1564

The Integration Service data movement mode is different from the saved disk cache.

Explanation:

The Lookup transformation uses a persistent named cache, and the Integration Service data
movement mode was changed between session runs.

User Response:

Recache the lookup source, or change the data movement mode to the previous mode.

CMN_1565

The Integration Service code page is different from the saved disk cache.

Explanation:

The Lookup transformation uses a persistent named cache, and the code page for the
Integration Service was changed between session runs. The Integration Service and cache
code pages are no longer compatible.

User Response:

Recache the lookup source, or change the code page to the previous code page.

CMN_1573

Error: Unknown code page <code page ID> for data source <source name>.

Explanation:

The system could not find a code page for the source. The pmlocale.bin file might be corrupt
or incomplete.

User Response:

Install a complete pmlocale.bin file from the installation DVD.

CMN_1574

Error: Failed to create locale from code page <code page ID> for data source <source name>.

Explanation:

The system could not locate locale information for the source. The pmlocale.bin file that
contains the locale information might be corrupt or incomplete.

User Response:

Install pmlocale.bin file from the installation DVD.

CMN_1575

The Integration Service sort order is different from the saved disk cache.

Explanation:

The Lookup transformation uses a persistent named cache, and the Unicode mode sort order
was changed between session runs.

User Response:

Recache the lookup source, or change the sort order to the previous sort order.

CMN_1576

Error: The current lookup index cache size of <number> bytes is too small. Increase the
lookup index cache to at least <number> bytes.

Explanation:

In the Designer or Workflow Manager, you entered a value for the lookup index cache that is
less than the recommended value.

User Response:

Increase the lookup index cache size to the value recommended in the error message.

CMN_1577

Error: The current lookup index cache size of <number> bytes is too small. Increase the
lookup index cache size to at least <number> bytes.

Explanation:

In the Designer or Workflow Manager, you entered a value for the lookup index cache that is
less than the recommended value.

User Response:

Increase the lookup index cache size to the value recommended in the error message.

CMN_1579

Input lookup precision is greater than the output lookup precision. Verify that the Lookup
transformation and linked transformations have the same port precision.

Explanation:

The precision for the lookup input port and the lookup output port do not match.

User Response:

In the lookup condition, verify that the ports in the Lookup Table Column and the
Transformation Port have the same precision.

Chapter 5: C Message Codes

CMN_1625

ERROR: Joiner <Joiner transformation> has <number> inputs for the master relation. There
should only be one master relation.

Explanation:

Unexpected error.

User Response:

Review error messages preceding this message. Otherwise, note the file name and line
number and contact Informatica Global Customer Support.

CMN_1636

Error occurred aborting row in joiner transformation <transformation name>.

Explanation:

An error occurred while aborting a row in the Joiner transformation instance.

User Response:

Check other error messages preceding this error message in the log.

CMN_1642

Error: Static Lookup Transformation <transformation name> has the same cache file name
prefix <cache file name> as a Dynamic Lookup Transformation <transformation name> in
same TLOG.

Explanation:

You cannot share static and dynamic lookups in the same target load order group.

User Response:

Remove the cache file name prefix. Or, use a unique prefix to share the cache with the
Lookup transformation in another target load order group.

CMN_1643

Error: Dynamic Lookup Transformation <transformation name> has the same cache file name
prefix <cache file name> as a Dynamic Lookup Transformation <transformation name> in
same TLOG.

Explanation:

You cannot share two dynamic lookups in the same target load order group.

User Response:

Remove the cache file name prefix. Or, use a unique prefix to share the cache with the
Lookup transformation in another target load order group.

CMN Messages

CMN_1644

Error: Dynamic Lookup Transformation <transformation name> has the same cache file name
prefix <cache file name> as a Static Lookup Transformation <transformation name> in same
TLOG.

Explanation:

You cannot share static and dynamic or two dynamic lookups in the same target load order
group.

User Response:

Remove the cache file name prefix. Or, use a unique prefix to share the cache with the
Lookup transformation in another target load order group.

CMN_1645

Error: Failed to get shared access to cache files <cache file name>. [dat/idx] for lookup
<Lookup transformation>.

Explanation:

One session is trying to read from a cache file while another session is still writing to it.

User Response:

Wait until the first session completes, then run the session.

CMN_1646

Error: Failed to get exclusive access to cache files <cache file name>. [dat/idx] for lookup
<Lookup transformation>.

Explanation:

One session is trying to write to a cache file while another session is reading from it.

User Response:

Wait until the first session completes, then run the session.

CMN_1647

Error: Failed to upgrade to exclusive access for cache files <cache file name> for lookup
<Lookup transformation>.

Explanation:

A session is trying to write to a cache file while another session is reading from the file.

User Response:

Wait until the first session completes, and then run the session.

CMN_1650

A duplicate row was attempted to be inserted into a dynamic lookup cache <Lookup
transformation name>. The dynamic lookup cache only supports unique condition keys.

Explanation:

You configured a Lookup transformation to use a dynamic lookup cache and the lookup table
contains duplicate rows.

User Response:

Eliminate duplicate rows in the lookup table, or use a static cache.

CMN_1655

Error: Lookup Transformations <transformation name> and <transformation name> have the
same cache file name prefix <cache file name> but have different connect strings <connect
string> vs. <connect string>.

Explanation:

Two Lookup transformations have different connect strings, but have the same cache file
name.

User Response:

Make sure the connect strings match.

CMN_1656

Error: Lookup Transformations <transformation name> and <transformation name> have the
same cache file name prefix <cache file name> but only the latter has a query override
<query>.

Explanation:

Two Lookup transformations have different query overrides, but have the same cache file
name.

User Response:

If you want to share the cache, use the same query override. If you do not want to share the
cache, change the cache file name for one of the Lookup transformations.

Chapter 5: C Message Codes

CMN_1657

Error: Lookup Transformations <transformation name> and <transformation name> have the
same cache file name prefix <cache file name> but have different override strings <override
string> vs. <override string>.

Explanation:

Two Lookup transformations have different query overrides, but have the same cache file
name.

User Response:

If you want to share the cache, use the same query override. If you do not want to share the
cache, change the cache file name for one of the Lookup transformations.

CMN_1658

Error: Lookup Transformations <transformation name> and <transformation name> have the
same cache file name prefix <cache file name> but correspond to different tables <table
name> vs. <table name>.

Explanation:

Two Lookup transformations use different lookup tables, but have the same cache file name.

User Response:

If you want to share the cache, the lookup table names must match. If you do not want to
share the cache, change the cache file name for one of the Lookup transformations.

CMN_1659

Error: Condition column <column name> of Lookup <transformation name> (with existing
cache) was not found in Lookup <transformation name> (that is trying to find one to share)
even though they have the same cache file name prefix <cache file name>.

Explanation:

When you have multiple Lookup transformations in a mapping, the first lookup creates a
cache file. The second lookup tries to use the same cache file, but cannot because the
condition does not match. Because both lookups use the same cache file name, the second
lookup cannot create a cache file.

User Response:

If you do not want to share the cache, change the cache file name for one of the lookups. If
you want to share the cache, make sure the shared transformations use the same ports in
the lookup conditions.

CMN_1660

Error: The number <number> of condition columns of Lookup <transformation name> is

different from <number> Lookup <transformation name> even though they have the same
cache file name prefix <prefix name> and <cache file name> needs to be refreshed / updated.

Explanation:

The second Lookup transformation uses a subset of condition columns of the first Lookup
transformation. However, the second Lookup transformation needs to refresh the cache. The
number of condition columns must be the same.

User Response:

If you do not want to share the cache, change the cache file name for one of the Lookup
transformations. If you want to share the cache, make sure the shared transformations use
the same ports in the lookup conditions.

CMN_1661

Error: Output column <column name> of Lookup <transformation name> (that is trying to find
one to share) was not found in Lookup <transformation name> (with existing cache) even
though they have the same cache file name prefix <cache file name> and <cache file name>
needs to be refreshed / updated.

Explanation:

User Response:

CMN Messages

CMN_1662

Error: Output column <column name> of Lookup <transformation name> (that is trying to find
one to share) was not found in condition or output columns of Lookup <transformation
name> (with existing cache) even though they have the same cache file name prefix <cache
file name>.

Explanation:

The second Lookup transformation uses a subset of output columns of the first Lookup
transformation. However, the second Lookup transformation needs to update the cache. The
number of output columns must be the same.

User Response:

CMN_1663

Error: The number <number> of output columns of Lookup <transformation name> is

different from <number> Lookup <transformation name> even though they have the same
cache file name prefix <cache file name> and <cache file name> needs to be refreshed /
updated.

Explanation:

The second Lookup transformation uses a subset of output columns of the first Lookup
transformation. However, the second Lookup transformation needs to refresh the cache. The
number of output columns must be the same.

User Response:

CMN_1664

Error: Out of sequence IDs to generate for port <port name> of Lookup <transformation
name> for insertion.

Explanation:

You reached the limit of unique sequence IDs that can be generated for inserting rows in the
dynamic lookup cache.

User Response:

Check the value of this port in the rows that are used to initialize the lookup cache. Try to
modify the value.

CMN_1665

Error: Failed to form key row for insertion in index cache file for Lookup <transformation
name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

CMN_1666

Error: Failed to form data row for insertion in data cache file for Lookup <transformation
name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

CMN_1667

Error: Failed to insert row for Lookup <transformation name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

CMN_1675

Cache for Lookup <Lookup transformation name> expects lookup override <SQL override>
but Cache file <file name> has <SQL override>.

Explanation:

The Lookup transformation uses a persistent named cache, and the lookup SQL override was
changed between session runs.

Chapter 5: C Message Codes

User Response:

Recache the lookup source, or change the lookup SQL override to the previous one.

CMN_1677

Error: Cache file <cache file name> needed by unnamed Lookup Transformation
<transformation name> in this mapping appears to be created by a named cache lookup
transformation.

Explanation:

Another session with a named lookup cache in the mapping may be running that is using this
cache file.

User Response:

Use unique cache file names for the named Lookup transformation.

CMN_1678

Error: Cache file <cache file name> needed by named Lookup Transformation
<transformation name> in this mapping appears to be created by an unnamed cache lookup
transformation.

Explanation:

Another session with an unnamed Lookup transformation in the mapping may be running that
is using this cache file.

User Response:

Use unique cache file names for the named Lookup transformation.

CMN_1679

Warning: A cache file name prefix <prefix> has been specified for the Lookup Transformation
<transformation name> but it is not marked as persistent. The cache file name prefix will be
ignored.

Explanation:

The Lookup transformation has been configured to use a cache file name prefix, but it has
not been configured for a persistent lookup cache. You can use a cache file name prefix only
with a persistent lookup cache.

User Response:

Change the Lookup properties to either remove the cache file name prefix or use a persistent
cache.

CMN_1683

Error: Static Lookup <lookup> needs to delete a cache file <cache file name> that was created
by a Dynamic Lookup <transformation name> in an earlier TLOG using different parameters.

Explanation:

In a previous target load order group in a mapping, a dynamic Lookup transformation created
a cache file. A static Lookup transformation uses the same cache file name and cannot
delete it.

User Response:

Use unique cache file names for the transformations.

CMN_1684

Error: Dynamic Lookup <transformation name> needs to delete a cache file <cache file name>
that was created by a Static Lookup <transformation name> in an earlier TLOG using different
parameters.

Explanation:

In a previous target load order group in a mapping, a static Lookup transformation created a
cache file. A dynamic Lookup transformation uses the same cache file name and cannot
delete it.

User Response:

Use unique cache file names for the transformations.

CMN_1686

Error allocating <number of bytes requested> in memory for cache transformation:

<transformation name>.

Explanation:

You specified a cache size larger than the system can allocate.

User Response:

Either reduce cache size for the transformation or increase virtual memory available in the
machine.

CMN Messages

CMN_1687

Error: Cache not enabled for Dynamic Lookup transformation <transformation name>.

Explanation:

In the session, you disabled caching for a Lookup transformation that you configured to use
as a dynamic cache.

User Response:

If you configure a Lookup transformation with a dynamic cache, you must enable caching in
the session.

CMN_1689

Failed to allocate <number> bytes from process memory for [DTM Buffer Pool].

Explanation:

There is insufficient process memory.

User Response:

Reduce the DTM buffer pool size, or free system resources.

CMN_1691

Cache expects port <port name> but cache file has it in a different data type and cannot be
used. A new cache file will be created.

Explanation:

Two Lookup transformations are configured to share a lookup cache, but the datatypes of the
cached columns in the Lookup transformations do not match.

User Response:

If you are using a named cache, verify that the caching structures match. If you are using an
unnamed cache, verify that the caching structures are compatible.

CMN_1694

Database Event Unable to set DBARITHABORT: Arithmetic exceptions from Microsoft SQL
Server will not cancel query execution.

Explanation:

The Integration Service failed to set database option DBARITHABORT for a database
connection to Microsoft SQL Server.

User Response:

Make sure Microsoft SQL Server is running and check Microsoft SQL Server network settings
so that the Integration Service can connect to the database and set the DBARITHABORT
option.

CMN_1695

Database Event Unable to set options: Options cannot be set in Microsoft SQL Server.

Explanation:

The Integration Service failed to set any database option for a database connection to
Microsoft SQL Server.

User Response:

Make sure Microsoft SQL Server is running and you can set the database connection and
database connection options.

CMN_1701

Error: Data for Lookup <transformation name> fetched from the database is not sorted on the
condition ports. Please check your Lookup SQL override.

Explanation:

You specified a SQL override for this Lookup transformation and specified the ORDER BY
clause incorrectly.

User Response:

When you override the lookup query ORDER BY clause, you must put the condition ports first.

CMN_1702

Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at
address <address>. System error is <error number> <error message>. (UNIX only)

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

CMN_1703

CMN_1715

The lookup query <Lookup transformation> contains character(s) that is(are) not valid in the
codepage of the database connection. The invalid character starts at position <character
position> of the query.

Explanation:

The lookup query contains one or more characters that are not encoded in character set of
the lookup database code page.

User Response:

Identify the invalid character referenced in the session log. Edit the lookup query so that it
contains characters encoded in the character sets of both the Integration Service code page
and the lookup database code page.
You can also configure the lookup database to use a code page that contains encoding for
the lookup data character set and is compatible with the Integration Service code page.

Explanation:

The lookup database uses a code page that is not supported by PowerCenter.

User Response:

Select a code page for the lookup database that is supported by PowerCenter and contains
encoding for the lookup data character set.

CMN_1720

The persistent lookup cache was created in a format that is incompatible with this release.

Explanation:

You upgraded a session using a persistent lookup cache and the Integration Service ran it for
the first time since the upgrade.

User Response:

None. The Integration Service rebuilds the cache from the lookup table.

CMN Messages

CMN_1767

Failed to ftell file <file name>: Error Msg <error message>.

Explanation:

Operating system error.

User Response:

Contact internal technical support.

CMN_1768

Failed to truncate file <file name>: Error Msg <error message>.

Explanation:

The Integration Service could not truncate the specified cache file.

User Response:

Check the additional error message for more information.

CMN_1769

Inconsistent recovery cache.

Explanation:

The Integration Service cannot run the session enabled for recovery because the recovery
cache file does not contain valid data.

User Response:

Delete all recovery cache files associated with the session and run the session with recovery
disabled to create a cache file. To determine which recovery cache file is associated with the
session, compare the time at which the file was last modified with the time the session failed.
If the times are the approximately the same, you can associate the cache file with the session.
You can also refer to the cache file names to determine which files are associated with the
session. Recovery cache file names use the following format:
pmgmd_metadata_<repository ID>_<workflow ID>_<folder ID>_
<session ID>_<transformation ID>_<partition ID>_<group ID>_
<checkpoint ID>_<sequence number>.dat

For example, in the following file name, the session ID is 102:

pmgmd_metadata_7661f424_379f_11d7_947e_f63b53abfef7_103_2_102_0_0_0_1_1.dat

Use the REP_LOAD_SESSIONS MX View on the repository database to determine the name
of the session associated with the session ID. You can use REP_LOAD_SESSIONS to view
information about reusable sessions.

CMN_1770

Recovery cache consumer is registered more than once.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

CMN_1771

The connection <database connection> specified is ambiguous. The connection name exists
in both relational and application connections.

Explanation:

In the Location Information session property for a Lookup transformation, or the Connection
Information session property for a Stored Procedure transformation, you specified a database
connection name that exists as both a Relational and Application database connection. When
the Integration Service runs the session, it cannot determine which connection to use.
This might occur when you specify the database connection name for the transformation in
the Designer and then create a session using the mapping. Or, this might occur when you
type the connection name in the session property.

User Response:

In the session properties, select the correct database connection name for the Lookup or
Stored Procedure transformation.

CMN_1772

Guaranteed Message Delivery cache directory <directory name> does not exist.

Explanation:

The Integration Service cannot find the cache file directory for message recovery.

Chapter 5: C Message Codes

User Response:

Verify that the cache file directory exists. Specify the correct path to the cache file directory in
the session properties. If the cache file directory does not exist, create a directory and specify
a directory path in the session properties.

CMN_1773

Error: Logical connection <database connection> in cache header file [lookup cache file.dat]
used by Lookup <Lookup transformation name> is either an invalid connection or it exists in
both Relational and Application type connections.

Explanation:

In a cached Lookup transformation in the Designer, you specified a database connection

name that exists as both a Relational and Application database connection in the Workflow
Manager. When the Integration Service runs the session, it cannot determine which
connection to use.

User Response:

In the session properties, select the correct database connection name for the Lookup
transformation. Or, you can enter Relational: before the connection name if it is a Relational
connection, or type Application: before the connection name if it is an Application
connection.

CMN_1774

Error: Logical connection <database connection> in Lookup <Lookup transformation name>

is either an invalid connection or it exists in both Relational and Application type connections.

Explanation:

In a cached Lookup transformation in the Designer, you specified a database connection

name that exists as both a Relational and Application database connection in the Workflow
Manager. When the Integration Service runs the session, it cannot determine which
connection to use.

User Response:

CMN_1775

Recovery cache directory <directory name> is invalid.

Explanation:

The name for the recovery cache folder is not valid.

User Response:

From the Properties settings on the sources tab in the session properties, specify a valid path
for the recovery cache folder.

CMN_1777

The connection <database connection name> specified can not run SQL query; hence can not
be used as a lookup or stored procedure connection.

Explanation:

For a Lookup or Stored Procedure transformation, you selected an Application database

connection type that is not a relational database.

User Response:

Select a Relational database connection, or select an Application database connection based

on a relational database, such as a PeopleSoft connection.

CMN_1778

Failed to read file <file>: Error Msg <error message>.

Explanation:

The Integration Service failed to read data from the specified cache file.

User Response:

Check the additional error message for more information.

CMN_1779

Failed to write file <file>: Error Msg <error message>.

Explanation:

The Integration Service failed to write data to the specified cache file.

User Response:

Check the additional error message for more information.

CMN Messages

CMN_1780

Guaranteed Message Delivery timestamp was changed, message cache will be cleaned and
session will continue running.

Explanation:

This is an informational message. The mapping or the session properties in the Task
Developer have changed since the last session run. The message recovery cache will be
deleted and the session will continue to run.

User Response:

None.

CMN_1781

Error: A connection must be specified for $Target when using 3.5 LOOKUP function.

Explanation:

An expression in the mapping uses the LOOKUP function and you did not specify a database
connection for the $Target Connection Value session property.

User Response:

On the General Options settings of the Properties tab in the session properties, enter a
database connection for the $Target Connection Value property. When you create a session
based on a mapping that uses the LOOKUP function, you must specify the database
connection for either the $Source Connection Value or $Target Connection Value in the
session properties.

CMN_1782

Error: A connection must be specified for $Source when using 3.5 LOOKUP function.

Explanation:

An expression in the mapping uses the LOOKUP function and you did not specify a database
connection for the $Source Connection Value session property.

User Response:

On the General Options settings of the Properties tab in the session properties, enter a
database connection for the $Source Connection Value property. When you create a session
based on a mapping that uses the LOOKUP function, you must specify the database
connection for either the $Source Connection Value or $Target Connection Value in the
session properties.

CMN_1784

Connect string <connection name in Location Information property> too long. Maximum
length allowed is <maximum length>.

Explanation:

In the Location Information session property for a Lookup transformation, you specified a
database connection name that is too long.

User Response:

Edit the database connection name in either the Relational or Application Connection
Browser.

CMN_1785

Lookup SQL override <Lookup transformation> has references to mapping parameters or

variables that cannot be resolved correctly.

Explanation:

You referenced a mapping parameter or variable in the lookup SQL override, but the
Integration Service could not resolve the parameter or variable to text.

User Response:

Edit the lookup SQL override and verify you spelled the mapping parameter or variable
correctly. Also, verify you declared the mapping parameter or variable in the mapping.

CMN_1786

Error: Failed to update row for Lookup <Lookup transformation>.

Explanation:

The Integration Service failed to update the row in the dynamic lookup cache.

User Response:

Check the session log for related error messages.

Chapter 5: C Message Codes

CMN_1796

An error was encountered while writing prior message(s) to this log file. Those messages may
be lost. Please check for available disk space.

Explanation:

The Integration Service encountered an error when writing to the server log file, most likely
because the machine that hosts the server log file ran out of disk space. Any messages
related to the task the Integration Service was performing at the time may have been lost.

User Response:

Check the available space on the machine that hosts the server log file.

CMN_1798

Cache for Lookup <Lookup transformation name> expects <number of> partitions but Cache
file <file name> has <number of> partitions.

Explanation:

The Lookup transformation uses a persistent named cache, and the number of partitions in
the pipeline that contains the Lookup transformation was changed between session runs.

User Response:

Recache the lookup source, or change the number of partitions to the previous number.

CMN_1800

Error: Lookup <Lookup transformation name> with cache file name prefix <prefix name> is
setup for <number of partitions> partitions but another Lookup <Lookup transformation
name> with the same cache file name prefix is setup for <number of partitions> partitions.

Explanation:

You configured two Lookup transformations in a mapping to share a named cache, but you
configured only one transformation for cache partitioning. The Integration Service cannot
share a partitioned cache with a non-partitioned cache.

User Response:

Edit the session properties and configure either both Lookup transformations with a hash
auto-keys partition point or neither with a hash auto-keys partition point.
Edit the mapping so that the Lookup transformations do not share a cache.

Explanation:

You configured two Lookup transformations in separate target load order groups to share a
named cache, but you configured a different number of partitions for the target load order
groups.

User Response:

Edit the session properties and configure the same number of partitions for each Lookup
transformation.
Edit the mapping so that the Lookup transformations do not share a cache.

CMN_1801

Error: Lookup <Lookup transformation name> and Lookup <Lookup transformation name>
with cache file name prefix <prefix name> are setup for partitioned cache but have condition
columns in different order.

Explanation:

You added hash auto-keys partition points to two Lookup transformations that are configured
to share a named cache, but the condition columns for the transformations do not match.
When you use cache partitioning with a named cache, the condition columns in the Lookup
transformations must be identical and in the same order.

User Response:

Remove the hash auto-keys partition points from the Lookup transformations.
Configure the Lookup transformations with identical condition columns. Verify that they are in
the same order.

CMN_1804

Cache cannot be empty when running in recovery mode.

Explanation:

You enabled recovery for a session. The session failed. Before you started the recovery
session, the cache was emptied. This is not allowed.

User Response:

When a session configured for recovery fails, make sure that the cache is not emptied before
starting the recovery session.

CMN Messages

CMN_1806

Failed to get information for file <cache file>. Error message: <error message>.

Explanation:

You enabled recovery for a session. The session failed. Before you started the recovery
session, the number of partitions for the session changed. This is not allowed.

User Response:

When a session configured for recovery fails, make sure that the number of partitions does
not change before starting the recovery session.

CMN_1813

ERROR: Some cache files with name prefix <name prefix> for Lookup <Lookup
transformation name> are missing or invalid.

Explanation:

You ran a session with multiple partitions that uses a named persistent lookup cache, but the
Integration Service cannot access some of the cache files.

User Response:

Verify the Integration Service can access all cache files for each partition. Or, remove all
existing persistent named cache files and run the session again. If all named persistent
cache files do not exist, the Integration Service rebuilds the persistent cache files.

CMN_1836

Error: Data for Lookup fetched from the file is not sorted on the condition ports.

Explanation:

You ran a flat file lookup session configured for sorted input, but the data for the condition
columns is not grouped.

User Response:

Clear the sorted input option in the Lookup transformation.

Ensure that data in the condition columns are grouped.

CMN_1919

External loader error. Error getting Teradata loader information.

Explanation:

The Integration Service could not fetch information from the repository to build the Teradata
control file.

User Response:

Verify the Integration Service machine can connect to the Repository Service machine and
that the Repository Service machine can connect to the repository. Verify the repository
machine is plugged in and connected to the network.

Chapter 5: C Message Codes

CMN_1920

External loader error. Error getting Flat-File information required for Loader.

Explanation:

The Integration Service could not fetch information from the repository to build the Teradata
control file.

User Response:

CMN_1921

External loader error. Control File will be generated for First Partition Only.

Explanation:

You tried to override the control file for a partition other than the first partition in the Teradata
target definition. The Integration Service only uses the control file specified in the first
partition when you create multiple partitions in a session that uses Multiload or FastLoad to
load to Teradata.

User Response:

Verify the control file in the first partition of the session uses the attributes you want for the
session.

CMN_1922

External loader error. Update is not valid for target instance <target definition name> since no
primary key(s) is mapped to the target.

Explanation:

The Teradata target table does not have a primary key, so the Integration Service cannot
generate a control file and update the target.

User Response:

Define a primary key on the target table and run the session again.

CMN_1923

External loader error. Update is not valid for target instance <target definition name> since no
non-key field(s) is mapped to the target.

Explanation:

The primary key column in the Teradata target definition is not connected to an upstream
transformation in the mapping. The Integration Service cannot generate a control file and
cannot update the target.

User Response:

Connect the primary key column in the Teradata target definition to an upstream port in the
mapping. Run the session again.

CMN_1924

External loader error. Delete is not valid for target instance <target definition name> since no
primary key(s) is mapped to the target.

Explanation:

User Response:

Connect the primary key column in the Teradata target definition to an upstream port in the
mapping. Run the session again.

CMN_1926

Error: Teradata external loader requires a primary key on table <target table name> when
using load mode <load mode>.

Explanation:

The Teradata external loader connection uses the specified load mode, such as update or
upsert, but the target table has no primary key. The target table must have a primary key for
the Integration Service to use this load mode.

User Response:

Define a primary key on the target table and run the session again.

CMN_1927

Error: Unable to set null character.

Explanation:

Internal error.

CMN Messages

User Response:

Contact Informatica Global Customer Support.

CMN_1928

External loader error. Upsert is not valid for target instance <target definition name> since
update is not valid for the target.

Explanation:

The Integration Service cannot perform upserts on the Teradata target table.

User Response:

Verify the target table has a primary key and that the primary key column in the target
definition is connected to an upstream transformation.

CMN_1929

External loader error <error message>.

Explanation:

The Integration Service cannot generate the Teradata control file because some control file
option values are missing, such as the TPDID value.

User Response:

Edit the external loader connection in the session and enter a value for all options.

CMN_1986

Service <service name> encountered an error while communicating with Licensing Service:
<error code and message>.

Explanation:

The service encountered an error while communicating with the Licensing Service.

User Response:

See the additional error message for more information.

CMN_1989

Service <service name> is not licensed to execute on node <node name>.

Explanation:

The service is not licensed to run on the operating system of the node.

User Response:

Get a license to run the service on the operating system.

Error: At Transformation <transformation name>. One of the concatenating pipelines contains

a Transaction Control Transformation. This mapping is no longer valid since TCT is an active
transformation. Please move the TCT before or after the concatenation.

Explanation:

The upgraded mapping contains a pipeline branch with a Transaction Control transformation
that concatenates with another branch in the same pipeline. This mapping is no longer valid
in PowerCenter.

User Response:

Edit the mapping and move the Transaction Control transformation either before or after the
concatenation.

CMN_17800

Property <property name> is missing.

Explanation:

A required property for a Custom transformation does not exist. You may have modified the
transformation.

User Response:

If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare
transformation, create the transformation again.

CMN_17802

<Input/output port> port for <port number> not found.

Explanation:

The Integration Service cannot find a column in a Custom transformation. You may have
modified the transformation.

User Response:

If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare
transformation, create the transformation again.

CMN_17804

Port <port number>: The transformation type <transformation datatype> is incompatible with
SAP type <SAP datatype>.

Explanation:

The transformation datatype and SAP datatype are not compatible for the specified
transformation. You may have modified the transformation.

User Response:

If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare
transformation, create the transformation again.

CMN_17807

Data conversion error for port <port number> with data <data>.

Explanation:

The Integration Service received data from the SAP system. The SAP system may have sent
data with a precision or scale that is too large.

User Response:

Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase
the precision or scale for the port.

Explanation:

The data contains inconsistencies.

User Response:

Contact Informatica Global Customer Support.

CMN Messages

CMN_17808

Data conversion error for port <port number>.

Explanation:

The Integration Service received data from the SAP system. The SAP system may have sent
data with a precision or scale that is too large.

User Response:

Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase
the precision or scale for the port.

Explanation:

The data contains inconsistencies.

User Response:

Contact Informatica Global Customer Support.

CMN_17825

The value for property <property> is not specified.

Explanation:

There is no value for the specified property.

User Response:

If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare
transformation, create the transformation again.
If you received this error for an SAP/ALE IDoc Prepare transformation, view the
transformation properties to see if it has the required value for the specified property. Or,
create the transformation again.

Chapter 5: C Message Codes

CMN_17829

Failed to connect to SAP system.

Explanation:

The Integration Service could not connect to the SAP system because the SAP RFC/BAPI
Interface or SAP_ALE_IDoc_Writer application connection contains invalid values for several
connection attributes.

User Response:

Verify that the application connection contains valid values for the User Name, Password,
and Connect String attributes.

CMN_17831

Incorrect source file name may have been specified in the session.

Explanation:

The source file name specified for the 6.x IDoc_Writer AEP transformation may be incorrect.

User Response:

Verify that the source file name is correct.

CMN_17833

Binary datatypes are not supported in RFC/BAPI function mappings. Disconnect port <port
name> in the mapping.

Explanation:

The binary datatypes PREC and LRAW are not supported in RFC/BAPI function mappings. If
a port uses these datatypes, you cannot connect it in the mapping.

User Response:

Disconnect the specified port.

CMN_17838

SAP code page <code page> is not compatible with the connection code page <code page>.

Explanation:

The code page specified in the SAP RFC/BAPI Interface application connection is not
compatible with the SAP server.

User Response:

Verify that the code page entered for the application connection is compatible with the SAP
server.

CMN_17839

SAP code page <code page> is not compatible with the Integration Service code page.

Explanation:

The code page specified for the Integration Service is not compatible with the SAP server.

User Response:

Verify that the Integration Service code page is compatible with the SAP server.

CMN_17840

Data <data> overflow at port <port number>. See below to find the row with error.

Explanation:

The Integration Service encountered a row error. As a result, the session failed.

User Response:

See the session error log to determine the row that contains the error and view more
information about the error.

Eliminate the errors in the data.

Increase the error threshold.

CMN_17856

Control field <control field> cannot have length greater than the precision <value>.

Explanation:

The length of the control field exceeds the precision set for it.

User Response:

Eliminate the errors in the data.

Increase the precision for the control field.

CMN_65011

Lookup instance <name> uses a dynamic cache. However, the workflow is configured to run
concurrently with the same instance name. This combination is not supported.

Explanation:

The Lookup transformation uses a dynamic cache and the workflow is configured to run
concurrently with same instance name.

User Response:

Configure the Lookup transformation to use a static cache or define unique names for each
workflow instance.

CMN_65017

The Integration Service could not use operating system profiles because pmimprocess was
not configured.

Explanation:

The pmimprocess was not configured.

User Response:

Set the user and groups to root and enable the setuid bit for pmimprocess before you use
operating system profiles.

CMN_65018

The workflow failed because the operating system user name specified in the operating
system profile is invalid.

Explanation:

The operating system profile contains an invalid operating system user name.

User Response:

Verify that the operating system user name is valid for nodes in the domain.

Chapter 5: C Message Codes

CMN_65019

Error using operating system profiles to run a workflow. Contact Informatica Global Customer
Support.

Explanation:

An internal error occurred when using an operating system profile to run a workflow.

Explanation:

The SMTP server may require a user name and password.

User Response:

Disable the login requirements on the SMTP server. For more information about configuring
the Integration Service to send SMTP email on Windows, see the PowerCenter Workflow
Basics Guide.

CMN_65051

The Integration Service could not send an email to the SMTP server.

Explanation:

The SMTP server machine may not be accessible.

User Response:

Verify that the Integration Service machine can access the SMTP server machine. For more
information about configuring the Integration Service to send SMTP email on Windows, see
the PowerCenter Workflow Basics Guide.

CMN_65052

The timeout period expired before the Integration Service could connect to the SMTP server.

Explanation:

The SMTP server custom properties for the Integration Service process may contain invalid
values.

User Response:

Verify the values of the custom properties. For more information about configuring the
Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics
Guide.

CMN_65057

The Integration Service could not locate the SMTP server because the server address is
invalid.

Explanation:

The SMTP server address custom property for the Integration Service process contains an
invalid server address.

User Response:

Verify the server address in the custom property. For more information about configuring the
Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics
Guide.

CMN Messages

CMN_65070

ERROR: Update dynamic cache condition is not valid for Lookup transformation.

Explanation:

The dynamic Lookup transformation does not have a conditional expression to update the
dynamic cache.

User Response:

Create an expression that returns a boolean or numeric value.

CMN_65071

Error: Lookup transformation[{0}] and Lookup transformation [{1}] with cache file name prefix
[{2}] share the same named cache but have but have incompatible match policies.

Explanation:

A Lookup transformation that returns multiple rows is sharing a lookup cache with a Lookup
transformation that returns one row for each input row.

User Response:

Verify that the Lookup transformations that share named cache have the same multiple
match properties.

CNX Messages
CNX_53117

Failed processing request ID <request ID>, req opcode <request operation ID>, reply opcode
<reply operation ID>. Return Status: <return status>.

Explanation:

Repository agent failed to complete the requested operation.

User Response:

If error persists, contact Informatica Global Customer Support.

CNX_53119

Thread received a notification to force the closing of client connection.

Explanation:

A repository connection ended because a repository or domain administrator terminated the

repository connection.

User Response:

Verify that the administrator does not need to have all users disconnected from the repository
for maintenance or other purposes. Then retry the operation in the PowerCenter Client.

CONF Messages

CONF_45006

Error: The Service Manager could not validate the Integration Service <Integration Service
Name> because the Integration Service does not have an associated repository.

Explanation:

The Integration Service validation failed because an associated repository was not configured
for the Integration Service.

User Response:

Configure an associated repository for the Integration Service.

Chapter 5: C Message Codes

CSE Messages
CSE_34005

The Integration Service could not set the encryption key for encryption.

Explanation:

The Integration Service could not set the encryption key for AES_ENCRYPT. An error
occurred in the Advanced Encryption Standard (AES) algorithm. The error may occur
because of low system resources or an out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to encrypt.

CSE_34010

The Integration Service could not set the encryption key for decryption.

Explanation:

The Integration Service could not set the encryption key for AES_DECRYPT. An error
occurred in the Advanced Encryption Standard (AES) algorithm. The error may occur
because of low system resources or an out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to decrypt.

CSE_34039

The Integration Service failed to decrypt data.

Explanation:

The Integration Service could not decrypt the data because of low system resources or an
out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to decrypt.

CSE_34040

The Integration Service failed to encrypt data.

Explanation:

The Integration Service could not encrypt the data because of low system resources or an
out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to encrypt.

CSE_34041

The Integration Service failed to compress data.

Explanation:

The Integration Service could not compress the data because of low system resources or an
out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to compress.

CSE_34042

The Integration Service failed to decompress data.

Explanation:

The Integration Service could not decompress the data because of low system resources or
an out of memory error.

User Response:

Run the session again. If the error persists, contact Informatica Global Customer Support and
provide the data you are trying to decompress.

CSE Messages

CTSDK Messages
CTSDK_43000

Couldn't load the library <library name> for plug-in <plug-in name>.

Explanation:

The plug-in has been installed incorrectly or is not compatible with the PowerCenter version.

User Response:

Reinstall the plug-in.

CTSDK_43001

Couldn't load the library <library name>.

Explanation:

PowerCenter could not load the specified library for the Custom transformation. The library or
dependent libraries may not be in the proper directory.

User Response:

Verify that the library and any dependent library is in the proper directory.

CTSDK_43002

Couldn't find address of function <function name> for plug-in <plug-in name>.

Explanation:

The function for the plug-in is not defined or is incorrectly defined.

User Response:

Reinstall the plug-in.

CTSDK_43003

Couldn't find address of function <function name>.

Explanation:

PowerCenter could not load the specified function for the Custom transformation.

User Response:

Verify that the library and any dependent library is in the proper directory.
Rebuild the library.

Chapter 5: C Message Codes

CHAPTER 6

D Message Codes
This chapter includes the following topics:
DBGR Messages, 91
DMI Messages, 95
DOM Messages, 98
DP Messages, 99
DS Messages, 105
DSP Messages, 105

DBGR_25025

Cannot modify data for transformations other than the current one.

Explanation:

Internal error. You tried to modify a port during an error breakpoint.

User Response:

Contact Informatica Global Customer Support.

DBGR_25026

Rowtype change not allowed for this transformation.

Explanation:

You tried to change the row type for this transformation to something other than Filter, Data
Driven, or Router.

User Response:

You can only change the row type for Filter, Router, and Update Strategy transformations.

DBGR_25027

Cannot modify port.

Error in breakpoint condition: Port <port name> and Port <port name> are from different
groups.

Explanation:

You used ports from different groups when setting a conditional breakpoint using two ports. A
Normalizer or an XML Source Qualifier transformation have ports organized in different
groups. The Integration Service reads data from these ports one group at a time.

User Response:

Do not use ports from different groups to set the conditional breakpoint.

DBGR_25049

Transformation has not received any data yet.

Explanation:

You tried to evaluate an expression before the Integration Service received data.

User Response:

Wait for a row of data to move into the transformation before evaluating an expression.

DBGR_25050

Port <port name> used in expression is unconnected and has no default value.

Explanation:

You tried to evaluate an expression using a port that is unconnected and has no default
value. An expression port never receives a value.

User Response:

Check to see if a port connection was deleted. Do not use this port in any expression
evaluation. Or, pass a value to the port through a valid connection.

DBGR_25059

Failed to create a socket to listen for connections from the client <PowerCenter Client
machine name>.

Explanation:

The Integration Service could not create a socket for Debugger connections. The
PowerCenter Client machine may have failed during the connection.

User Response:

Restart the Debugger session.

DBGR_25060

Failed to find an available port between <DebuggerMinPort> and <DebuggerMaxPort> to listen

for connections from the client <PowerCenter Client machine name>.

Explanation:

Explanation:

The data for the primary or foreign key is missing.

User Response:

Make sure the data contains primary and foreign key values.

DMI Messages

DMI_17507

NULL data obtained for all connected fields for the segment <segment name>.

Explanation:

The data for all connected fields is missing for the named segment.

User Response:

Make sure the data exists for all connected fields for the named segment.

DMI_17508

Error building the tree.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
process the IDoc data in the SAP DMI Prepare transformation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

DMI_17509

Unknown error traversing the tree.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
process the IDoc data in the SAP DMI Prepare transformation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

DMI_17515

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because mandatory segment is missing: <segment
name>.

Explanation:

You configured the session to validate DMI documents before writing them to the SAP
system. The Integration Service determined that a value for the mandatory segment in the
DMI document is missing.

User Response:

Verify that the SAP DMI Prepare transformation for the DMI document contains values for the
mandatory segment.

Chapter 6: D Message Codes

DMI_17516

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because maximum occurrence is higher than
maximum limit for: <segment name>.

Explanation:

You configured the session to validate DMI documents before writing them to the SAP
system. The Integration Service determined that the segment contains more than the
maximum number of records allowed.

User Response:

Correct the source data so that the number of records for the segment does not exceed the
maximum number of records allowed.

DMI_17517

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because minimum occurrence is less than the
minimum limit for: <value>.

Explanation:

You configured the session to validate DMI documents before writing them to the SAP
system. The Integration Service determined that the segment contains less than the minimum
number of records allowed.

User Response:

Correct the source data, so that the number of records for the segment meet at least the
minimum number of records allowed.

DMI_17518

Data <data> overflow at port <port number>. If the error threshold is not met, the row will be
sent through the ErrorDMIData port.

Explanation:

The SAP DMI Prepare transformation received data that is larger than the precision for the
row.

User Response:

Correct the source data so that the value matches the precision for the row.

DMI_17519

Error getting data for the field.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
process the IDoc data in the SAP DMI Prepare transformation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

DMI_17520

The SAP DMI Prepare transformation has an unconnected input group. All input groups must
be connected for the transformation.

Explanation:

An input group does not have any connected ports.

User Response:

Make sure that at least one port for each input group is connected.

DMI_17525

Cache folder specified for the SAP DMI Prepare transformation <transformation name> is
invalid.

Explanation:

The cache directory specified for the SAP DMI Prepare transformation does not exist.

User Response:

In the session properties, enter a valid directory for the Cache Directory property.

DMI_17526

The Integration Service could not access the cache block in group <group>. Increase the
cache size.

Explanation:

The cache size specified for the SAP DMI Prepare transformation is inadequate.

User Response:

In the session properties, increase the cache size.

DMI Messages

DMI_17527

The SAP DMI Prepare transformation did not receive data for the DMI object.

Explanation:

The source in the DMI mapping does not contain valid data for the DMI object.

User Response:

Verify that the source data is valid.

DOM Messages

DOM_10009

Cannot find the specified domain <linked domain name> from domain <current domain
name>.

Explanation:

The Service Manager cannot find the domain name that is specified in the lookup request.
The domain information may be out of date, or the requested domain may not be running.

Chapter 6: D Message Codes

User Response:

Shut down the domain, and then start Informatica services on the gateway nodes and worker
nodes.

DOM_10184

The Integration Service cannot use operating system profiles on Windows node <node name>
in <service name>.

Explanation:

Integration Services can use operating system profiles on UNIX nodes. The Integration
Service cannot use operating system profiles on Windows nodes.

User Response:

Enable operating system profiles for an Integration Service that runs on UNIX nodes.
Disable operating system profiles for the Integration Service.

DOM_10185

User <user name> in security domain <security domain name> does not have the
Administrator role required to shut down the domain.

Explanation:

To shut down a PowerCenter domain, a user must have the Administrator role for the domain.

User Response:

Ask the domain administrator to shut down the PowerCenter domain.

DOM_10188

Unable to start service <service name> of version <service version> on the node <node
name>. This node is not configured to run this service version.

User Response:

Start this service on a node that is configured to run this service version.

DOM_10189

Unable to start the service <service name> of service version <service version> as the
associated services <service names> belong to a different version.

User Response:

Verify that associated and dependent services are of the same service version as the service,
and then restart the service.

DP Messages
DP_90001

Invalid target type. Profile mapping targets should either be relational or null.

Explanation:

The profile mapping contains target definitions that are not relational or null. The targets in
the profile mapping might have been modified.

User Response:

Recreate the profile.

DP_90002

All the targets in a profiling mapping should use the same connection and have the same
connection attributes.

Explanation:

There are two or more relational database connections configured for targets in the profile
mapping.

User Response:

Make sure you use the same relational database connection for all targets in a profiling
mapping.

DP_90003

Create server database connection failed.

The Data Profiling warehouse tables are invalid.

User Response:

Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit
the SQL script after you run it.

DP_90012

SQL Fetch failed for statement <SQL statement> with error <database error>.

Explanation:

The Data Profiling warehouse tables are invalid.

User Response:

Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit
the SQL script after you run it.

Chapter 6: D Message Codes

DP_90013

Fetching the key for type <key number> failed.

Explanation:

A Data Profiling warehouse table is missing surrogate keys. The following surrogate keys
correspond to these key types in error messages:
0 - Profile run key
1 - Column key
2 - Source function key
3 - Column function key
4 - Referential Integrity Analysis function key
5 - Join Complexity Evaluation function key

User Response:

Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit
the SQL script after you run it.

Explanation:

You attempted to run an existing profile session in an upgraded PowerCenter repository

against a new Data Profiling warehouse.

User Response:

Regenerate the profile mapping and run the profile session again.

DP_90014

There must be one input group and one output group for this transformation.

Explanation:

The Custom transformation in the profile mapping has been modified and is invalid.

User Response:

Regenerate the profile mapping.

DP_90015

The output port <port name> datatype should be long.

Explanation:

The Custom transformation in the profile mapping has been modified and is invalid.

User Response:

Regenerate the profile mapping.

DP_90016

The target warehouse is already used for repository <repository name> with GUID <global
unique identifier>. Either drop the warehouse tables or use a different one.

Explanation:

You tried to use two repositories for the same Data Profiling warehouse.

User Response:

Create a second Data Profiling warehouse. Also, create a relational database connection to
the second Data Profiling warehouse in the Workflow Manager.

DP_90017

The profile warehouse tables are not present in the target database connection. Please check
the target connection information.

Explanation:

The Data Profiling warehouse tables are not in the target database.

User Response:

Run the Data Profiling warehouse script in the Data Profiling installation directory. Commit
the SQL script after you run it.

DP_90019

Failed to get the folder information from repository.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

DP_90020

Failed to get the metadata extension <metadata extension> for the mapping.

Explanation:

You copied a profile mapping without copying the metadata extensions.

User Response:

Copy the metadata extensions from the original profile mapping to the copied mapping and
run the session again.

DP Messages

101

102

Explanation:

You are running a session with an original profile mapping that corresponds to a data profile,
but the metadata extensions are deleted.

User Response:

Regenerate the profile mapping.

DP_90022

Profile has some invalid functions. Session run failed.

Explanation:

You tried to run a profile session for a data profile. The data profile contains invalid functions.

User Response:

Edit the data profile to modify or remove the invalid functions.

DP_90023

Warehouse table PMDP_WH_VERSION is missing. The target warehouse version is incorrect.

You may need to upgrade the warehouse.

Explanation:

The version of the Data Profiling warehouse does not match the version of PowerCenter.

User Response:

Upgrade the Data Profiling warehouse using the upgrade script for the database type.

DP_90024

The target warehouse uses schema version <version> and data version <version>. You may
need to upgrade the warehouse.

Explanation:

The version of the Data Profiling warehouse does not match the version of PowerCenter.

User Response:

Upgrade the Data Profiling warehouse using the upgrade script for the database type.

DP_90026

Warehouse table PMDP_WH_VERSION is missing or column SCHEMA_VERSION/

DATA_VERSION/DATABASE_TYPE is missing. You need to upgrade the warehouse.

Explanation:

The version of the Data Profiling warehouse does not match the version of PowerCenter.

User Response:

Upgrade the Data Profiling warehouse using the upgrade script for the database type.

DP_90411

Corrupt input received.

Explanation:

You tried to run a session with a copied or deployed profile mapping that contains reusable
domains.

User Response:

You must run a profile session with the original profile mapping if the mapping contains
reusable domains.

Explanation:

You copied a profile transformation to use in another mapping.

DATA_VERSION/DATABASE_TYPE is missing.

User Response:

Regenerate the profile mapping.

Chapter 6: D Message Codes

DS Messages
DS_10008

Cannot find node <name> specified in the service lookup request in domain <name>.

Explanation:

The node is not running or does not exist in the domain.

User Response:

Verify that the node is running. Verify that the node name was entered correctly.

DS_10009

Cannot find domain <name> specified in the service lookup request.

Explanation:

The command specified a domain gateway machine name and port number, as well as a
domain name. The command line program was unable to find the domain on the gateway
host machine.

User Response:

Verify the domain exists on the domain gateway host machine. Verify the domain name was
entered correctly.

DS_10012

The disable mode specified <mode> is invalid to disable service <service name>.

Explanation:

The DisableService command was used to disable the service shown. The mode specified is
invalid.

User Response:

Verify the mode is either complete, stop, or abort.

DSP Messages
DSP_20307

Error fetching node information from Configuration Service (domain name <domain>, node
name <node>). Error message: <message text>.

Explanation:

The Integration Service could not fetch node metadata from the Service Manager.

User Response:

Start Informatica services on the referenced node. Check the error message text for more
information about the cause of the failure.

DS Messages

105

CHAPTER 7

E Message Codes
This chapter includes the following topics:
EB Messages, 106
EP Messages, 110
EB Messages, 119
EXP Messages, 120
EXPFN Messages, 125

EB Messages

106

EBRDR_13003

The PowerCenter Integration Service could not connect to Oracle E-Business Suite.

Explanation:

Connection information is not correct.

User Response:

Enter a valid DSN, user name, and password.

EBRDR_13005

The PowerCenter Integration Service could not generate or parse the SQL query.

Explanation:

The SQL query in the session properties or Source Qualifier properties may be invalid.

User Response:

Verify that the query in SQL Query property of the Source Qualifier or session attribute is
valid.

Explanation:

You have provided invalid data.

User Response:

Provide valid data.

-or-

Explanation:

You may not have the necessary privileges to submit the concurrent program request.

User Response:

Contact the Oracle E-Business Suite administrator to get the necessary privileges.

EBWRT_32028

The Integration Service could not determine the application ID of <application name>.

Explanation:

You have provided an invalid application short name in the Interfacelist.xml.

User Response:

Provide a valid application short name in the Interfacelist.xml.

-or-

Explanation:

Oracle Application error.

User Response:

See the Oracle documentation for more information.

EBWRT_32069

-orSpecify the responsibility name in the Oracle E-Business Suite target definition.

EBWRT_33007

The PowerCenter Integration Service could not write data to the temporary file.

Explanation:

Explanation:

User name is incorrect.

Chapter 7: E Message Codes

User Response:

Provide a valid user name.

EBWRT_36011

The PowerCenter Integration Service could not determine Responsibility ID of

<Port name> port of group <group name> is not linked.

Explanation:

Dummy primary key of the specified group ID is not connected to the Source Qualifier.

User Response:

Connect the dummy primary key of group name.

EBWRT_36070

Incorrect language <language>.

Explanation:

The language is invalid.

User Response:

Specify a language that is installed on the Oracle E-Business Suite machine.

EBWRT_36072

The PowerCenter Integration Service could not write data for GPK__<port name> = <data>
and GFK__<port name> = <data>.

Explanation:

The PowerCenter Integration Service could not write data to the interface table.

User Response:

For more information, see the corresponding ODBC error message in the session log.
If the session is configured to skip the hierarchy validation and the data for the GPK and GFK
ports is blank in the error message, verify that the GPK and GFK ports are linked. Also, verify
that the data is specified for these ports.

EBWRT_40001

The PowerCenter Integration Service could not connect to Oracle E-Business Suite.

Explanation:

Connection information is not correct.

EP_13001

Invalid conversion.

Explanation:

In an external procedure, the Integration Service cannot convert the datatype of the port to
the datatype of the corresponding parameter, or vice versa. For example, the port may have
a Date/Time datatype, while the parameter has an Integer datatype. The Integration Service
cannot convert a Date/Time datatype to an Integer datatype.

User Response:

Either change the external procedure datatype or the port datatype before running the
session again.

EP_13002

Error freeing external module.

Explanation:

The Integration Service encountered an error while closing a DLL or shared object.

object in the Informatica external module.

Chapter 7: E Message Codes

User Response:

Examine the CreateExternalModuleObject function and the constructor for the external
module object called within it.

EP_13011

NULL external procedure name.

Explanation:

You did not enter the procedure name in the External Procedure transformation.

User Response:

Enter a valid name for the procedure.

EP_13012

Cannot get external procedure signature.

Explanation:

A call to the TINFExternal Module Impl::GetProcSignature function failed.

User Response:

Examine this function in the file infemimp.cpp. Also, make sure that the
INFEMProcSignatures and the p*ParamVector data structures in the module_nameEM.CPP
file have not been altered.

EP_13013

Number of ports in transform does not match number of formal arguments.

Explanation:

The Integration Service cannot match the number of ports in an External Procedure
transformation with the number of formal arguments in the external procedure.

User Response:

Correct either the number of arguments in the external procedure or the number of ports in
the External Procedure transformation before running the session again.

112

User Response:

Make sure the return value of the External Procedure transformation is the last port.

EP_13024

Port lookup failed.

Explanation:

An External Procedure transformation port name does not match the corresponding external
procedure argument.

User Response:

Change the external procedure argument or the External Procedure transformation port name
before running the session again.

EP_13025

Not all input params found.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

EP_13026

Multiple connections to input port.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

EP_13027

Decimal overflow error.

Explanation:

The Integration Service encountered an error converting decimal numbers on input to or

output from an external procedure.

User Response:

Evaluate the external procedure to see if the Decimal datatype is necessary. If possible,
change the Decimal datatype to Double.

EP_13028

Unknown error while converting datatype.

Explanation:

Internal error.

User Response:

Send the external procedure to Informatica Global Customer Support with a description of the
error.

EP_13030

Exception error was thrown from external procedure <external procedure name>.

Explanation:

The Integration Service encountered a serious exception while running the external
procedure.

User Response:

Debug the external procedure code before running the session again.

EP_13033

Cannot initialize COM-style external procedure.

Explanation:

The Integration Service encountered an error initializing a COM-style external procedure.

User Response:

This is a general error. Check the session log for related error messages.

EP_13034

Unknown COM error.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

EP_13035

Cannot initialize column/parameter mapping.

Explanation:

EP Messages

113

114

EP_13046

IDispatch::Invoke failed.

Explanation:

The Integration Service encountered a major exception in a COM-style external procedure.

User Response:

In the registry, make sure the type library is valid and in the correct location. For more
information, see the COM documentation.

EP_13053

Cannot get type library attributes.

Explanation:

The Integration Service encountered an error accessing a COM type library.

User Response:

Contact Informatica Global Customer Support.

EP_13054

Cannot open registry key HKEY_CLASSES_ROOT\\CLSID\\clsid\\server type.

Explanation:

The Integration Service could not open the named key because it is invalid or not at that
location.

User Response:

In the registry, make sure the named key exists at the right location and is a valid key. For
more information, see the COM documentation.

EP_13055

Cannot get registry value for HKEY_CLASSES_ROOT\\CLSID\\clsid\\<server type>.

Explanation:

EP Messages

115

116

EP_13066

Error converting COM datatype to Informatica internal datatype.

Explanation:

The Integration Service encountered an error converting between a COM and Informatica
datatype. Either the external procedure attempted an invalid conversion, or a data overflow
occurred.

User Response:

Check the session log for messages related to data overflow or invalid datatype conversions.
If data overflowed, change the external procedure or mapping to accommodate the data.
Otherwise, make sure the external procedure uses valid datatype conversions.

EP_13067

Error converting Informatica internal datatype to COM datatype.

Explanation:

The Integration Service encountered an error converting between a COM and Informatica
datatype. Either the external procedure attempted an invalid conversion, or a data overflow
occurred.

User Response:

User Response:

Check the code for the Init or InitParams method in the specified external procedure and
correct the fatal error. Read the session log for related messages logged by the external
procedure.

EP_13084

Data conversion error.

Explanation:

The Integration Service cannot convert a String port from the External Procedure
transformation to a Date/Time input port in the external procedure. The string is not in the
default date format (MM/DD/YYYY HH24:MI:SS).

User Response:

Use TO_DATE with the appropriate format string to convert a string to a date.

Explanation:

The Integration Service cannot convert data from an external procedure Date/Time output
port to a String port in the External Procedure transformation.

User Response:

Change the External Procedure transformation port to Date/Time.

EP_13089

Error converting initialization parameter to correct data type for constructor parameter.

Explanation:

In the initialization properties for the External Procedure transformation, you specified a
parameter that the Integration Service cannot convert to the COM datatype for the
constructor in the external procedure. Before the Integration Service calls the constructor in
the external procedure, it tries to convert the initialization parameters in the External
Procedure transformation to the required COM datatypes.

User Response:

Edit the parameters in the Initialization Properties tab of the External Procedure
transformation. Enter values that the Integration Service can convert to the required COM
datatypes for the constructor.

EP_13103

<External Procedure transformation>: Fatal error returned from external procedure <external
procedure>.

Explanation:

The specified external procedure returned a fatal error.

User Response:

Check the code for the specified external procedure and correct the fatal error. Read the
session log for related messages logged by the external procedure.

EP_13124

<External Procedure transformation>: Fatal error from initialization of external module

<module: external procedure>.

Explanation:

The Init or InitParams method in the specified external procedure returned a fatal error.

EP Messages

117

118

User Response:

Check the code for the Init or InitParams method in the specified external procedure and
correct the fatal error. Read the session log for related messages logged by the external
procedure.

EP_13261

Fatal Error: It is illegal to set pass thru port when the transformation scope is not ROW or
when the data access mode is ARRAY for active Custom Transformation.

Explanation:

The Custom transformation procedure code uses the INFA_CTSetPassThruPort() function

when the transformation scope is transaction or all input and the data access mode is rowbased.

User Response:

Change the transformation scope to row.

Explanation:

The procedure code for an active Custom transformation uses the

INFA_CTSetPassThruPort() function and the data access mode is array-based.

User Response:

Edit the procedure code and use the array-based mode data handling functions to set the
data for all output ports. Do not use the INFA_CTSetPassThruPort() function.

EP_13262

Fatal Error: It is illegal to set default row strategy to pass thru when the transformation scope
is not ROW or when the data access mode is ARRAY for active Custom Transformation.

Explanation:

The Custom transformation procedure code uses the INFA_CTSetRowStrategy() function to

define the default row strategy to pass through when the transformation scope is transaction
or all input and the data access mode is row-based.

User Response:

Change the transformation scope to row.

Explanation:

The procedure code for an active Custom transformation uses the INFA_CTSetRowStrategy()
function to define the default row strategy to pass through and the data access mode is arraybased.

User Response:

Edit the procedure code and use the INFA_CTASetRowStrategy() function to define the
default row strategy to pass through.

EP_13263

Fatal Error: It is illegal to call INFA_CTASetInputErrorRow when the data access mode is not
ARRAY.

Explanation:

The Custom transformation procedure code uses the INFA_CTASetInputErrorRowM() or

INFA_CTASetInputErrorRowU() function and the data access mode is row-based.

User Response:

Edit the procedure code and remove the INFA_CTASetInputErrorRowM() or

INFA_CTASetInputErrorRowU() function. Instead, you can return INFA_ROWERROR in the
input row notification function to notify the Integration Service that a particular input row has
an error.

EP_13264

Fatal Error: It is illegal to call INFA_CTGetRowStrategy outside inputRowNotification.

Explanation:

The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function

inside a function other than the p_<proc_name>_inputRowNotification() function.

User Response:

Edit the procedure code and only use the INFA_CTGetRowStrategy() function inside the
p_<proc_name>_inputRowNotification() function.

EP_13265

Fatal Error: It is illegal to call INFA_CTGetRowStrategy when the data access mode is ARRAY.

Explanation:

The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function

when the data access mode is array-based.

Chapter 7: E Message Codes

User Response:

Edit the procedure code and use the INFA_CTAGetRowStrategy() function to get the default
row strategy.

EP_13266

Fatal Error: It is illegal to call INFA_CTOutputNotification outside inputRowNotification when

the transformation scope is ROW.

Explanation:

An invalid argument was entered in a date function.

User Response:

Check the function syntax and enter a valid argument.

EXP_19108

The Integration Service failed to parse the date format <date format string>.

Explanation:

An invalid date format was entered in a date function.

User Response:

Check the function syntax and enter a valid date format string.

EXP_19138

The Integration Service failed to parse the date format <unit portion of date format>.

Explanation:

A date format was entered in a date function. Part of the date format string is invalid.

User Response:

Check the function syntax and enter a valid date format string.

EXP_19145

Invalid date value string: <date format string>.

Explanation:

The string argument provided to the TO_DATE function is invalid.

User Response:

Check the function syntax and enter a valid string argument.

EXP_19160

Failed to find version API <function name> in module <module name>.

Chapter 7: E Message Codes

User Response:

The custom function developer needs to implement the function in the implementation file.

EXP_19164

Module API <function name> in module <module name> failed.

Explanation:

The custom function developer configured the INFA_EXPR_GetPluginVersion function to

return INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19165

Module init for <function name> failed: <error message>.

Explanation:

The custom function developer configure module_init to return INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

Explanation:

The function failed for the reason specified in the additional error message.

INFA_EXPR_FunctionInstanceGetUserInterface.

User Response:

The custom function developer needs to implement the function in the implementation file.

EXP_19169

Module deinit for <function name> failed: <error message>.

Explanation:

The custom function developer configured module_deinit to return INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

Explanation:

The function failed for the reason specified in the additional error message.

User Response:

The custom function developer may need to correct the function syntax.

EXP_19170

Failed to get validation interface for <function name>.

Explanation:

The custom function developer configured INFA_EXPR_ValidateGetUserInterface to return

INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19171

Failed to get function interface for <function name>.

Explanation:

The custom function developer configured INFA_EXPR_FunctionGetUserInterface to return

INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP Messages

121

122

EXP_19172

Failed to get function instance interface for <function name>.

Explanation:

The custom function developer configured INFA_EXPR_FunctionInstanceGetUserInterface to

INFA_EXPR_FunctionInstanceGetUserInterface.

Explanation:

The custom function developer did not implement processRow.

User Response:

The custom function developer needs to implement the function in the implementation file.

EXP_19177

Failed to initialize function instance for <function name>: <error message>.

Explanation:

The custom function developer configured fnInstance_init to return INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

Explanation:

The function failed for the reason specified in the additional error message.

User Response:

The custom function developer may need to correct the function syntax.

EXP_19178

Failed to deinitialize function instance for <function name>: <error message>.

The custom function developer configured processRow to return INFA_FAILURE.

User Response:

The custom function developer needs to configure the function to return INFA_SUCCESS.

Explanation:

The function failed for the reason specified in the additional error message.

User Response:

The custom function developer may need to correct the function syntax.

EXP_19181

Failed to get validation functions for <function name>.

Explanation:

The custom function developer did not implement one ore more of the following functions:
validateFunction, getFunctionDescription, getFunctionPrototype, and DestroyString.

User Response:

The custom function developer needs to verify that these functions are implemented.

EXP_19182

User-defined function <user-defined function> has a cyclic dependency. Call stack is <call
stack>.

Explanation:

The specified user-defined function contains a reference to itself in the expression syntax. Or,
it contains another user-defined function which refers to it.

Explanation:

The Integration Service truncated an operand value because the precision is too low. The
error message may provide more information about this error.

User Response:

Increase the precision.

Explanation:

Data overflow occurred for an integer value.

User Response:

Check the data values for the overflow. The error message may provide more information
about this error.

EXP_19188

<<Expression Warning: user-defined function>> <token>: <error message>. <sub-expression>.

Explanation:

The Integration Service encountered an error converting between a COM and Informatica
datatype. Either the external procedure attempted an invalid conversion, or a data overflow
occurred.

User Response:

EXP_19189

Error in fetching metadata for the user-defined function <user-defined function>.

Explanation:

The Integration Service or PowerCenter Client cannot fetch metadata for the specified userdefined function.

User Response:

Close the repository connection and reconnect. Run the session again.
Verify that you are not trying to use a user-defined function that does not exist.

124

EXP_19190

Error: Argument mismatch for user-defined function <user-defined function>

Explanation:

The number of arguments in the user-defined function does not match the number of required
arguments. The user-defined function may contain too many or too few arguments.

User Response:

Edit the user-defined function syntax to include the correct number of arguments.

Chapter 7: E Message Codes

EXP_19194

Argument index <index number> exceeds the expected number of arguments, <number>, in
the expression.

Explanation:

The expression contains an argument having an index greater then the expected number of
arguments for the expression. For example, you created an expression that takes two
arguments, but used an argument name x3 inside the expression. Instead, the expression
should use x1 and x2.

User Response:

Use the correct number of arguments for the expression when you invoke the expression.

EXP_19195

Error: A non-callable user-defined function <user-defined function> is being called directly in

the expression.

Explanation:

An expression contains a non-callable user-defined function. You may have manually entered
the user-defined function in the expression syntax. Or, the expression contains a userdefined function which you modified to be non-callable.

User Response:

Edit the user-defined function to be callable. Or, remove the user-defined function from the
expression.

EXPFN Messages

125

CHAPTER 8

F Message Codes
This chapter includes the following topics:
FEXP Messages, 126
FR Messages, 127
FTP Messages, 135

FEXP Messages

126

FEXP_87001

The following system error occurred opening the file <file name>: <error number>: <error
message>.

Explanation:

The line number in the fexpcodepagemapfile.dat file does not use the correct format. Each
line must start with an exclamation point (!) to designate a comment or must assign a
PowerCenter code page to a Teradata character set by entering the names on a single line in
the following format: <PowerCenter_code_page>=<Teradata_character_set>.
A line cannot consist of blank spaces or tab characters only.

User Response:

Modify the file so that the specified line number uses the correct format.

FEXP_87026

The following system error occurred when the Integration Service tried to get the values of
session attributes: [{0}].

Explanation:

The Teradata FastExport process could not get the values of session attributes from the
Integration Service in a FastExport session because of the error shown.

User Response:

Fix the error and restart the session.

FR Messages
FR_3000

Error opening file <file name>. Operating system error message <error message>.

Explanation:

A file name specified in the session properties is incorrect. The operating system error
displays when the file does not exist.

User Response:

In the Workflow Manager, correct the file name in the session properties.
If you are loading a packaged resource in Metadata Manager, check the value of the
PowerCenter Integration Service Process property $PMSourceFileDir. Metadata Manager
stores transformed metadata for packaged resources in IME files in the $PMRootDir/SrcFiles
directory. If the $PMSourceFileDir property is not set to $PMRootDir/SrcFiles, Metadata
Manager cannot find the IME files.

FR Messages

127

128

FR_3002

Error reading file <file name>. Operating system error message <error message>.

Explanation:

This is an operating system error.

User Response:

An operating system error number appears with this message. If necessary, see the
operating system documentation for appropriate action.

FR_3013

Error setting field delimiter string.

Explanation:

The Integration Service failed to identify a field separator. You may have repository
inconsistencies.

User Response:

Contact Informatica Global Customer Support.

FR_3015

Warning! Row <row ID>, field <name>: Data was truncated.

Explanation:

Data is larger than field length (delimited files only), forcing the Integration Service to
truncate data.

User Response:

To avoid truncating data, increase the field length accordingly.

FR_3016

Record length <record ID> is longer than line sequential buffer length <number> for <string>.

Chapter 8: F Message Codes

User Response:

Specify a delimiter other than the escape character.

FR_3032

Delimited file attribute error: must specify at least one delimiter.

Explanation:

You have not specified a delimiter.

User Response:

Specify a delimiter.

FR_3033

Delimited file reader: Warning! Missing matching quote character in column <column name>
of file <file name>. Reading till the end of line for the column.

Explanation:

There is a missing closing quote in the specified column.

User Response:

Review the file and add a closing quote character where appropriate.

FR_3034

Delimited file reader: Warning! Skipped extra character(s) after the closing quote of column
<column name> in file <file name>.

Explanation:

There are additional characters after the closing quote delimiter in the specified column. The
Integration Service did not read the extra characters.

User Response:

Look in the source file to verify if the skipped characters are intended to be a part of the
column. If so, import the file into the Source Analyzer again.

FR_3035

Error opening file NULL. Operating system error message.

Explanation:

FR_3050

Error: Invalid code page <code page name> for fixed-width VSAM file.

Explanation:

The code page you selected is not valid for VSAM files.

User Response:

Select a code page that is valid for VSAM files.

FR_3051

Error: Invalid binary null character <null character value>. The decimal value is not between 0
and 255.

Explanation:

You entered an invalid null character value.

Chapter 8: F Message Codes

User Response:

Specify a null character value between 0 and 255.

FR_3053

Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width
boundary for <bytes to skip between records>. Next row/record will also be an error.

Explanation:

The number of bytes to skip between records is greater than 0. If the number of bytes to skip
between records is greater than 0, then there is an alignment error in these bytes. The record
data does not end at the fixed-width boundary for these skipped bytes.

User Response:

Fix the data and the number of bytes to skip between rows/records setting.

FR_3054

Error! Remaining data <string data> in non-repeating, binary null field, in fixed-width file <file
name> does not end at the fixed-width boundary for field <field name>.

Explanation:

Remaining data in a non-repeating, binary null field does not end at the fixed-width boundary
for that field.

User Response:

Fix the data and/or the fixed-width settings.

FR_3056

Error reading from file <file name>.

Explanation:

An error occurred reading the source file.

User Response:

Check other error messages logged for more details.

FR_3057

Error: Insufficient data for fixed-width flat file or fixed-width VSAM file. Row data is <row
data>.

Explanation:

The non line-sequential data is too small. The data displayed is the row, including the trailing
bytes between records.

User Response:

Make sure the data is the correct length and the bytes between rows match the source file
options.

FR_3058

Error processing COBOL file: cannot parse the input [numeric character in <data> at position
<position> has to be in the Latin1 code page].

Explanation:

The reader cannot read the input field because the input field contains characters that are not
in the Latin 1 code page.

User Response:

Change the input field to contain Latin 1 character data.

FR_3059

Error processing record <record name> in file <file name>: Record is invalid because at least
one set of redefines is invalid (redefine is not at a perfect character boundary or conversion
error for picnum field).

Explanation:

In a file source, at least one of the REDEFINES statements results in a character exceeding
the field boundary.

User Response:

Examine and correct the row where the error occurred.

Explanation:

The definition is incorrect.

User Response:

Edit the REDEFINES statement.

FR_3060

Error processing record <record name> in file <file name>: Conflicting shift states at position
<position number, referring to byte offset into the row> when interpreting multiple redefines.

Explanation:

In a file source, one of the REDEFINES statements leaves the row in the shift in state while
another REDEFINES statement leaves the row in the shift out state.

FR Messages

131

132

User Response:

Examine and correct the row where the error occurred or edit the REDEFINES statement.

FR_3061

Error opening WebSphere MQ queue. Operating system error message.

Explanation:

The Integration Service could not open the queue.

User Response:

Verify the source file contains different characters for the thousands separators and column
delimiters. Edit the source definition in the Source Analyzer, or import it again.

FR_3070

Error: The character <character> is used as a delimiter and a decimal separator for field
<column name>.

Explanation:

In the Designer, you specified the same character as both the file delimiter and as the
decimal separator for the specified numeric column.

Chapter 8: F Message Codes

User Response:

Verify the source file contains different characters for the decimal separator and column
delimiter. Edit the source definition in the Source Analyzer, or import it again.

FR_3072

Error: Flat file <file name> cannot be processed for reading.

Explanation:

The Integration Service cannot access the source file.

User Response:

Verify the Integration Service can access the machine hosting the file.
Grant read permission on the directory where the file is located to the Informatica Services
account or the operating system user in the operating system profile.

FR_3074

Error at row <row number>. A multibyte character spans over two fields or two lines. Record
will be skipped.

Explanation:

In the fixed-width file source, a multibyte character in a column spans over two columns. The
Integration Service skips the row.

User Response:

Verify that the row in the source file contains valid data. Also, verify that the data in the
source file matches the source definition.

FR_3075

Error: Source file type cannot be indirect for an MQ associated source qualifier.

Explanation:

You selected Indirect for the Source file type. When the mapping contains an associated
source qualifier, the source file type must be direct.

User Response:

Select Direct as the source file type.

FR_3077

Fatal Error: The column <column name> has corrupt formatting information. Resave the
information in the repository.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

FR_3078

Fatal error: Cannot flush an incomplete row in real time.

Explanation:

During a real-time session, the Integration Service issued a commit while processing a
record. As a result, the session failed.

User Response:

Make sure that all message fields in the change WebSphere MQ source are complete before
running the session.

FR_3085

ERROR: Row <row number>: <character>-th character is a null character, which is not
allowed in a text input file <file name>.

Explanation:

The Integration Service cannot read the input field because it contains a null character.

User Response:

Verify that the source does not have null values.

FR_3107

ERROR: The character <character> is used as both a column delimiter and a row delimiter.

Explanation:

The session failed because the line break character is the same character as the column
delimiter in the flat file.

User Response:

Configure different characters for the flat file line break character and column delimiter
character.

FR Messages

133

134

FR_3108

ERROR: DSQ <Source Qualifier name> UCS-2 code page UTF-16BE or UTF-16LE are not
supported with this type of file.

Explanation:

The session failed because the UTF-16BE or UTF-16LE code page is not supported for fixedwidth flat files.

User Response:

You can use these code pages with delimited flat files.

FR_3110

Error in opening SFTP connection.

Explanation:

The SFTP connection specified in the session has an error. Or, the SFTP server might be
down.

Disable one of the properties. For more information about custom properties, contact
Informatica Global Customer Support.

FR_3116

Error: Invalid NULL replacement character is specified for the delimited file source <source
name>.

Explanation:

When you enable the FileRdrTreatNullCharAs custom property, the Integration Service sets
null characters in a source file to the character you define. The character format is invalid.

User Response:

Define a valid octal character, such as \040. For more information about custom properties,
contact Informatica Global Customer Support.

FR_3117

The Integration service cannot use multibyte replacement character <character> specified for
the delimited file source <source name>. Please specify a replacement character with a single
character unit length.

Explanation:

When you enable the FileRdrTreatNullCharAs custom property, the Integration Service sets
null characters in a source file to the character you define. The character specified is a
multibyte character.

User Response:

Define a valid single-byte character. For more information about custom properties, contact
Informatica Global Customer Support.

Chapter 8: F Message Codes

FTP Messages
FTP_14002

Unable to transfer file using FTP because the TCP/IP address for the specified host could not
be obtained.

Explanation:

Could not obtain the TCP/IP address of the remote FTP remote host using the remote host
name specified in the FTP connection.

User Response:

Verify that the FTP host name provided in the FTP connection is correct.
Contact the FTP system administrator.

FTP_14003

Unable to transfer file using FTP because Integration Service could not create a socket.

Explanation:

The Integration Service could not create the socket due to insufficient resources such as file
descriptors, memory, or permissions on the FTP server.

User Response:

Contact the FTP system administrator.

FTP_14004

Unable to transfer the file using FTP because socket option could not be set.

Explanation:

Internal error.

User Response:

Contact the Informatica Global Customer Support.

FTP_14005

Unable to transfer the file using FTP because the Integration Service could not connect to the
FTP server.

Explanation:

The Integration Service could not connect to the FTP server, possibly because the network is
down.

User Response:

Contact the network administrator.

Explanation:

The FTP server is not properly configured on the remote machine.

User Response:

Contact the FTP system administrator.

FTP_14006

Unable to transfer the file using FTP because the Integration Service cannot read the remote
file.

Explanation:

The network connection went down after the Integration Service connected to the FTP server.

User Response:

Contact the network administrator, the FTP system administrator, and the Informatica system
administrator.

FTP_14007

Unable to transfer the file using FTP because the format of the FTP response is not expected.
The FTP server is not supported.

FTP_14012

Unable to transfer file using FTP. FTP command <command name> rejected by FTP server.

Explanation:

The FTP user in the FTP connection object does not have read permissions.

User Response:

For Windows, verify that the FTP user accessing the file has standard read permissions on
the directory of the staged file.
For UNIX, prepare the staging directory so that the FTP user who accesses the file also owns
the directory. Run the following UNIX command from the directory where you want to
generate the file:
% chmod g+s

136

Explanation:

This is an informational message. The Integration Service checks the existence of a file when
you run a file persist session. The first time you run a file persist session, the file does not
exist. When the Integration Service does not find the file, it writes this message to the
session log.

User Response:

None.

Chapter 8: F Message Codes

FTP_14024

FTP host name <host name> has incorrect format. Specify <hostname> or <hostname>:<port>
where 0 <port< 65536.

Explanation:

You entered an FTP host name in the wrong format in the Host Name field in the FTP
Connection Editor dialog box.

User Response:

Edit the FTP connection in the Workflow Manager. Specify the host name format as
<hostname> or <hostname:port>.

FTP_14040

FTP Socket <socket number> timeout. The FTP server has not responded in time. Verify the
FTP server is running, or increase the FTP timeout value.

Explanation:

The Integration Service tried to accessed a file source on an FTP server, but the FTP server
did not send any data before the Integration Service timed out. By default, the Integration
Service waits 600 seconds before timing out.

User Response:

Verify the FTP server is still running. If you need to increase the amount of time the
Integration Service waits before timing out, contact Informatica Global Customer Support.

FTP_14046

Cannot reconnect to FTP server at <FTP host>: <control port number> within retry period.

Explanation:

The connection to the FTP server failed. The Integration Service could not reconnect to the
FTP server within the retry period for the FTP connection object.

User Response:

Check the status of the FTP server and run the session again. If the session is enabled for
recovery, recover the session.

FTP_14047

The source file <file name> or its timestamp was changed after the previous read. Session
should now terminate.

Explanation:

The connection to the FTP server for the session failed and the Integration Service
reconnected to the FTP server. However, the source file for the session changed since the
last time the Integration Service read from the file, and the session failed.

User Response:

Run the session again. If the session is enabled for recovery, recover the session.

FTP_14048

FTP server does not support the FTP command <FTP command>. Resilience is disabled.

Explanation:

The connection to the FTP server failed. The Integration Service reconnected to the FTP
server and attempted to restart the file transfer. However, the FTP server does not support
the REST, MDTM, or SIZE FTP commands, which are necessary to restart the file transfer.
As a result, the session failed.

User Response:

For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP
commands.

FTP_14049

FTP server does not support the FTP command <FTP command>. Cannot restart file transfer
to FTP server.

Explanation:

User Response:

For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP
commands.

FTP Messages

137

FTP_14050

DTM buffer does not contain enough data to restart file transfer. Terminating session.

Explanation:

The Integration Service transferred some target data to the remote FTP server and the
connection failed. Some of the target data was not written to the remote file by the FTP
server, and target data no longer exists in the buffer for the DTM process. As a result, data
was lost and the Integration Service cannot restart file transfer after reconnecting to the FTP
server.

User Response:

Run the session again.

FTP_14055

A socket <socket number> failure is encountered: <error text>.

Explanation:

The Integration Service encountered an error for the socket. As a result, the session failed.

User Response:

Correct the error and run the session again.

FTP_14056

High availability license is absent. Retry period specified for Integration Service connection to
the FTP server is ignored.

Explanation:

The retry period is configured in the FTP connection object, but you do not have the high
availability option. The retry period is ignored.

User Response:

None.

FTP_14057

Unable to transfer files using SFTP because the Integration Service could not get the TCP/IP
address for the specified host.

Explanation:

Could not obtain the TCP/IP address of the remote SFTP remote host using the remote host
name specified in the SFTP connection.

User Response:

Verify that the SFTP host name provided in the SFTP connection is correct.
Contact the SFTP system administrator.

138

FTP_14058

Unable to transfer files using SFTP because the Integration Service could not create a socket.

Explanation:

The Integration Service could not create the socket due to insufficient resources such as file
descriptors, memory, or permissions on the SFTP server.

User Response:

Contact the SFTP system administrator.

FTP_14059

Unable to transfer file using SFTP because the Integration Service could not connect to SFTP
server.

Explanation:

The Integration Service could not connect to the SFTP server, possibly because the network
is down.

User Response:

Contact the network administrator.

Explanation:

The SFTP server is not properly configured on the remote machine.

User Response:

Contact the SFTP system administrator.

FTP_14060

SFTP host name <host name> has incorrect format. Specify <host name>; or <host
name>:<port> where 0<port<65536.

Explanation:

Explanation:

The SFTP user does not have permission to delete the staging file.

User Response:

Delete the file manually, and contact the administrator of the SFTP system to get permission
to delete SFTP files for future sessions.

FTP_14065

Failed to initialize SSH2 session (transport layer) with SFTP server: <system message>.

Explanation:

The SSH library that the Integration Service uses is not compatible with the library files on
the SFTP server.

User Response:

Verify that the SFTP server supports the SSH version that the Integration Service uses.

Explanation:

The public key and private key file names were not provided in the FTP connection.

User Response:

Specify the public key and private key file name in the FTP connection.

FTP Messages

139

140

FTP_14081

Remote SFTP server is not responding.

Explanation:

The Integration Service could not connect to the SFTP server, possibly because the network
is down.

FTP_14084

Unable to access the private key or public key file. Verify that the correct file path was
specified.

Explanation:

The public key or private key file was not specified correctly.

User Response:

Verify that the correct file name and file path is specified in the FTP connection object.

Chapter 8: F Message Codes

CHAPTER 9

H Message Codes
This chapter includes the following topic:
HIER Messages, 141

HIER Messages
HIER_28004

XML Reader Error: <error text>.

Explanation:

This is a generic error.

User Response:

Check the session log for related error messages.

HIER_28020

DTM buffer block is filled, and we can't send the block yet. Need to use heap memory to hold
data.

Explanation:

In the XML file, leaf elements appear after multiple-occurring enclosure elements of a parent
element. The memory block for the multiple-occurring enclosure elements is filled.

User Response:

Restructure the file so that all of the leaf elements of a parent element appear before the
multiple-occurring enclosure elements.

HIER_28028

Fatal Error: Could not allocate memory from heap.

Explanation:

In the XML file, leaf elements appear after multiple-occurring enclosure elements of a parent
element. The Integration Service has now run out of heap memory.

User Response:

Restructure the file so that all of the leaf elements of a parent element appear before the
multiple-occurring enclosure elements.

HIER_28031

There are two fields pointing to the same XML node, but the datatypes and lengths do not
match.

Explanation:

The Source Qualifier transformation contains different ports based on the same XML
element. The datatypes or lengths for these ports are different.

User Response:

Check the Source Qualifier transformation and make sure the datatypes and lengths for all
occurrences of the element match.

HIER_28032

Error: There are no fields in any of the groups defined that have a reference to a node in the
XML tree.

HIER_28043

Reader failure: The node <element name> occurs multiple times. This node was marked in the
schema as occurring one or less times.

Explanation:

You imported a source in the Designer based on an XML file. In the source qualifier, the
Designer marked one of the elements as a single-occurring element. When you used this
source in a mapping, the imported XML file contained the element multiple times.

User Response:

Recreate the XML Source Qualifier transformation using a more accurate XML file.

HIER_28044

Reader failure: The root node for the given XML does not match the root node in the
repository.

Explanation:

You imported a source in the Designer based on an XML file. The Designer determined the
root element based on this file and stored it in the repository. When you used this source in a
mapping, the imported XML file contained a different root element.

User Response:

Check the XML file and then import it again.

IDM_24045

The Data Masking transformation failed to read the data masking rules.

User Response:

Run the session again. If the problem persists, contact Informatica Global Customer Support.

IDM_24051

The Data Masking transformation failed to create a masking rule.

User Response:

Run the session again. If the problem persists, contact Informatica Global Customer Support.

IDM_24055

Seed is not between 1 and 1000. Using default value for seed.

Explanation:

A column is configured for key masking in the Data Masking transformation. The seed value
is configured in a mapping parameter. The mapping parameter has an incorrect value. The
Integration Service used the seed value from the defaultValue.xml file. The defaultValue.xml
file contains default mask values.

User Response:

Configure the mapping parameter value to be a number between 1 and 1000.

IDM_24056

Seed defined in the Data Masking default file is not between 1 and 1000. Using 725 as value
for seed.

Explanation:

A column is configured for key masking in the Data Masking transformation. The seed value
in a mapping parameter file is invalid. The seed value in the Data Masking default file also is
invalid. The Integration Service uses 725 as the default seed value.

User Response:

Update default_seed in the default mask values file, defaultValue.xml. Verify the seed value
is between 1 and 1000. The default mask values file is in the following location:
<PowerCenter Installation Directory>\infa_shared\SrcFiles\defaultValue.xml.

IDM_24057

Failed to mask SSN: <number>. The SSN is invalid.

Explanation:

The source Social Security number is invalid because the area is not in the highgroup.txt file
from the Social Security Administration. The area is the first three digits of the Social Security
number. The Data Masking transformation does not mask the Social Security number if the
source number is invalid.

User Response:

Verify the Social Security number.

IDM_24058

Transformation failed to evaluate expression <expression>.

Explanation:

The session failed when the Data Masking transformation attempted to evaluate an
expression. The expression returned invalid results.

User Response:

Check the session reject file or error log to find the row that caused the error. If this is a
recurring error, change the expression.

Chapter 10: I Message Codes

IDM_24059

Expression parse fatal error; Failed to parse expression <expression>. Should be: Fatal error
while parsing Data Masking transformation expression.

Explanation:

The session failed when the Data Masking transformation attempted to evaluate an
expression.

User Response:

Check the session reject file or error log to find the row that caused the error. If this is a
recurring error, change the expression that references the port.

IDM_24060

Datatype of the evaluated expression, <expression>, and the port datatype are not the same.
Using default value of the port datatype as output. Change to: Expression datatype is not the
same as the port datatype. Using a default port value to mask data.

Explanation:

The Integration Service could not apply a mask to a port configured for expression masking.
The expression returns a result that is not the same datatype as the port in the Data Masking
transformation. The Data Masking transformation returns a default masked value.

User Response:

When you create an expression for a Data Masking transformation port, verify that the
expression returns a value that matches the port datatype. The Expression Editor does not
validate if the expression returns a datatype that is valid for the port.

IDM_24061

No connection information for the relational dictionary has been specified.

Explanation:

The Data Masking transformation is configured to use a relational dictionary, but there is no
connection information for the dictionary.

User Response:

Configure a connection object for the IDM_Dictionary connection on the Mapping tab of the
session properties.

IDM_24062

No connection information for storage has been specified.

Explanation:

The Data Masking transformation is configured to use a storage table for repeatable masking,
but there is no connection information for the database table.

User Response:

Configure a connection object for the IDM_Storage connection on the Mapping tab of the
session properties.

IDM_24063

Storage table does not exist. Create the storage table before running a session.

Explanation:

The Data Masking transformation is configured for repeatable substitution or expression

masking. The storage table that maintains source data and masked value pairs does not exist.

User Response:

Informatica provides SQL scripts to create a storage table for a Sybase, Microsoft SQL
Server, IBM DB2, or Oracle database. The scripts are located in the <PowerCenter
installation directory>\client\bin\Extensions\DataMasking directory. Create a storage table
and configure a connection to the table before you run the session.

IDM_24064

Size of the dictionary is zero. Unable to select a masked value.

Explanation:

The Data Masking transformation is configured for substitution masking. The dictionary that
provides the substitute data is empty.

User Response:

Verify that the correct dictionary file or table is configured in the Masking Properties tab of the
Data Masking transformation. Verify that the dictionary contains data.

IDM_24065

Unable to select a unique masked value from the dictionary.

Explanation:

The Data Masking transformation is configured for repeatable masking. The Data Masking
transformation cannot return unique masked values because the dictionary does not have
enough data.

IDM Messages

145

146

User Response:

Verify that the dictionary has more unique values than the source data.

IDM_24066

Unable to select a masked value from the dictionary.

Explanation:

The Integration Service was unable to retrieve a substitute masked value from the dictionary
for data masking.

User Response:

Verify the structure of the dictionary is correct. Each row in the dictionary must have a serial
number. The serial numbers are integers that start at one. The rows are numbered
sequentially with no gaps in the numbers. Configure the serial number column name in the
Data Masking transformation.

IDM_24067

The dictionary <dictionary name> is unavailable in the connection provided.

Explanation:

The Data Masking transformation is configured for substitution masking. The relational
dictionary that provides the substitute data is unavailable for the connection.

User Response:

When you configure a relational dictionary, configure a relational connection for the dictionary
on the Mappings tab of session properties. Select a relational connection object for the
IDM_Dictionary connection.

IDM_24068

The dictionary <dictionary name> is unavailable in the $PMLookupFileDir.

Explanation:

The Data Masking transformation is configured for substitution masking. The flat file
dictionary that provides the substitute data is unavailable in the lookup file directory.

Explanation:

The Data Masking transformation could not apply a mask to a source date because the date
format is invalid.

Chapter 10: I Message Codes

User Response:

Verify that the date is in a format that is defined by the session configuration object. Check
the DateTime Format String attribute on the Config Object tab for a session or session
configuration object. By default, the date format is MM/DD/YYYY HH24:MI:SS.US.

Property <property> is invalid. Error parsing IDocs list.

Explanation:

The 6.x IDoc_Writer AEP transformation contains a list of values for the IDocTypeList
property that are not separated with the correct delimiter.

User Response:

Edit the transformation and use a semicolon (;) to separate the list of IDoc types.

IDOC_17608

The number of IDoc types in the property <property> does not match the number specified in
<property>.

Explanation:

The number of IDoc types listed in the IDocTypeList property does not match the number
specified in the NumberOfIDocTypes property for the 6.x IDoc_Writer AEP transformation.

User Response:

Edit the transformation so that the value for the NumberOfIDocTypes property matches the
number of IDoc types listed in the IDocTypeList property.

IDOC_17610

Error getting metadata for some of the IDocs in the list: <list>.

Explanation:

The Integration Service failed to retrieve the metadata for the IDoc_Writer AEP
transformation in a 6.x inbound IDoc mapping.

User Response:

Verify that the Informatica transports were correctly installed or upgraded.

Verify that the saprfc.ini file is configured. Also, verify that the RFC Destination created in the
SAP system for the Integration Service is valid.

148

IDOC_17613

Unexpected IDoc type <IDoc type> received.

Explanation:

The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in
the IDocTypeList property.

User Response:

Edit the transformation so that the IDocTypeList property includes all IDoc types the
transformation will receive.

IDOC_17614

Input is expected only for IDoc types: <IDoc type>.

Explanation:

The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in
the IDocTypeList property.

User Response:

Edit the transformation so that the IDocTypeList property includes all IDoc types the
transformation will receive.

Chapter 10: I Message Codes

IDOC_17615

Error parsing control data. Check the control data for IDoc type <IDoc type>.

Explanation:

The Integration Service failed to parse the IDoc control record data received by the 6.x
IDoc_Writer AEP transformation.

User Response:

Correct the source data so that it contains valid control record data.

IDOC_17617

The segment <IDoc segment> is not allowed in the current IDoc type <type>.

Explanation:

The 6.x IDoc_Writer AEP transformation received data for an invalid segment for the IDoc
type.

User Response:

Correct the source data so that it contains only valid segment data as defined by the
metadata for the IDoc type.

IDOC_17618

Control record data cannot be NULL for IDoc <IDoc>.

Explanation:

The 6.x IDoc_Writer AEP transformation received a null value for the control record.

User Response:

Correct the source data so that the IDoc control record data does not contain null values.

IDOC_17619

Segment data cannot be NULL for segment <segment>.

Explanation:

The 6.x IDoc_Writer AEP transformation received a null value for the segment record.

User Response:

Correct the source data so that the IDoc segment record data does not contain null values.

IDOC_17620

Error creating control table <control table>.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
perform the desired operation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17621

Error creating data table <data table>.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
perform the desired operation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17622

Error appending control record <control record>. Failed to allocate enough memory.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
perform the desired operation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17623

Error appending data record <data record>. Failed to allocate enough memory.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
perform the desired operation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC Messages

149

150

IDOC_17624

The SAPALEIDoc target definition did not receive a control record segment for IDoc type:
<IDoc type>.

Explanation:

The SAPALEIDoc target definition received several data segments but no control record
segment (EDIDC) for the specified IDoc type. Each IDoc must contain one control record
segment followed by one or more data segments. This error might occur if the transformation
preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation
and if it passes invalid IDoc data.

User Response:

Verify that valid IDoc data is passed to the SAPALEIDoc target definition.

IDOC_17625

The SAPALEIDoc target definition did not receive a control record segment. Error
encountered in IDoc processing.

Explanation:

The SAPALEIDoc target definition received several data segments but no control record
segment (EDIDC) for an IDoc type. Each IDoc must contain one control record segment
followed by one or more data segments. This error might occur if the transformation
preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation
and if it passes invalid data.

User Response:

Verify that valid IDoc data is passed to the SAPALEIDoc target definition.

IDOC_17626

The SAPALEIDoc target definition received an incorrect number of control record segments.
Error encountered in IDoc processing.

Explanation:

The number of control record segments that the SAPALEIDoc target definition received does
not match the total number of IDocs received. Each IDoc must contain one control record
segment followed by one or more data segments. This error might occur if the transformation
preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation
and if it passes invalid data.

User Response:

Verify that valid IDoc data is passed to the SAPALEIDoc target definition.

IDOC_17627

The SAPALEIDoc target definition did not receive any data segments for IDoc type <IDoc
type>. Error encountered in IDoc processing.

Explanation:

The SAPALEIDoc target definition received a control record segment but no data segments
for the specified IDoc type. Each IDoc must contain one control record segment followed by
one or more data segments. This error might occur if the transformation preceding the
SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes
invalid data.

User Response:

Verify that valid IDoc data is passed to the SAPALEIDoc target definition.

IDOC_17633

Error creating control table <table name>.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
perform the desired operation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17642

Idle Time <time> must be greater than or equal to -1.

Explanation:

Explanation:

The Reader Time Limit session property specified for the SAPALEIDoc source definition
contains an invalid value.

User Response:

In the session properties, edit the Reader Time Limit value so that it is greater than or equal
to 0.

IDOC_17646

Failed to get connection reference for source qualifier instance <Source Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

IDOC_17647

Failed to get connection for source qualifier instance <Source Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

IDOC_17648

Failed to initialize reader properties for source qualifier instance <Source Qualifier name>.

Explanation:

The Integration Service cannot initialize the session. The session properties for the Source
Qualifier instance might be invalid.

User Response:

Check the additional error message for more information.

IDOC_17649

Incorrect connection type specified for SAPALEIDoc source.

Explanation:

In the session properties, an invalid application connection type was selected for the
SAPALEIDoc source definition. An SAPALEIDoc source definition must use an
SAP_ALE_IDoc_Reader application connection.

User Response:

In the session properties, select an SAP_ALE_IDoc_Reader application connection for the

SAPALEIDoc source definition.

IDOC_17652

The value for the property <TypeOfEP> should be <IDocInterpreter>.

Explanation:

In the 6.x IDoc_Interpreter EP transformation, the TypeOfEP property is not set to

The input IDoc type <IDoc type> is different from the expected IDoc type <IDoc type>. Check
the source data or the configuration to ensure data consistency.

Explanation:

The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in
the IDocTypeList property.

User Response:

Edit the transformation so that the IDocTypeList property includes all IDoc types the
transformation will receive.

Contact Informatica Global Customer Support.

IDOC_17670

IDoc writer cannot get connection information for the target instance <target>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

IDOC_17671

Writer partition <partition> failed to register for recovery.

Explanation:

The Integration Service could not configure recovery for the session.

User Response:

Check the additional error message for more information.

Chapter 10: I Message Codes

IDOC_17672

Data <data> truncated by writer.

Explanation:

This is a warning message. The data for the segment exceeds the maximum length. The data
was truncated.

User Response:

Check the data for the segment specified in the message. Correct the length of the data for
the next session run.

IDOC_17675

IDoc reader failed to support recovery for the Source Qualifier instance <Source Qualifier
name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

IDOC_17676

Cache folder specified for reader partition <partition> is invalid.

Explanation:

The recovery cache folder in the session properties is invalid.

User Response:

In the session properties, specify a recovery cache folder.

IDOC Messages

153

154

IDOC_17684

Reader partition <partition> failed to flush the cache: <error message>.

Explanation:

The Integration Service could not flush the cache.

Chapter 10: I Message Codes

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17699

Error building the tree.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
process the IDoc data in the SAP/ALE IDoc Interpreter transformation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17700

Error getting data for the field.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
process the IDoc data in the SAP/ALE IDoc Interpreter transformation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

IDOC_17704

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because mandatory segment is missing: <segment
name>.

Explanation:

You configured the session to validate inbound IDocs before writing them to the SAP system.
The Integration Service determined that a value for the mandatory segment in the IDoc is
missing.

User Response:

Verify that the SAP/ALE IDoc Prepare transformation for the inbound IDoc contains values for
the mandatory segment.

IDOC_17705

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because maximum occurrence is higher than
maximum limit for: <segment name>.

Explanation:

You configured the session to validate inbound IDocs before writing them to the SAP system.
The Integration Service determined that the segment contains more than the allowed number
of records.

User Response:

Correct the source data so that the number of records for the segment do not exceed the
maximum number allowed.

IDOC_17706

Syntax validation failed for primary key <primary key> and corresponding generated
document number <document number> because minimum occurrence is less than the
minimum limit for: <segment name>.

Explanation:

You configured the session to validate inbound IDocs before writing them to the SAP system.
The Integration Service determined that the segment contains less than the minimum number
of records allowed.

User Response:

Correct the source data so that the number of records for the segment meet the minimum
number of records allowed.

IDOC_17707

NULL data obtained for primary/foreign key fields.

Explanation:

Data for the primary or foreign key fields is missing.

User Response:

Make sure the data contains primary and foreign keys.

IDOC Messages

155

156

IDOC_17708

NULL data obtained for all connected fields for the segment <segment name>.

Explanation:

Data for the connected fields in the named segment is missing.

User Response:

Make sure the data exists for the connected fields in the named segment.

IDOC_17709

Data <data> overflow at port <port number>. If the error threshold is not met, the row will be
sent through the ErrorIDocData port.

Explanation:

The SAP/ALE IDoc Prepare transformation received data that is larger than the precision for
the row.

User Response:

Correct the source data so that the value matches the precision for the row.

IDOC_17710

<Value> orphan rows were received by the SAP/ALE IDoc Prepare transformation.

Explanation:

The SAP/ALE IDoc Prepare transformation received orphan rows. The session fails if the
Orphan Row Handling session property is set to Error and the error count has exceeded the
error threshold.

User Response:

Eliminate the duplicate rows in the data.

IDOC_17714

The following IDoc data is not of proper length: <value>.

Explanation:

The SAP/ALE IDoc Interpreter transformation received IDoc data that is less than the fixed
length of 1,063 characters for each segment.

User Response:

Correct the source data so that it equals 1,063 characters for each segment.

IDOC_17720

The SAP/ALE IDoc Prepare transformation has an unconnected input group. Connect all input
groups for the transformation.

Explanation:

One or more input groups in the SAP/ALE IDoc Prepare transformation are not connected.

User Response:

Make sure that all input groups are connected.

IDOC_17721

Error encountered while setting data for group: <group>.

Explanation:

There is not enough disk space to perform the desired operation.

User Response:

Check the disk for free space.

Chapter 10: I Message Codes

IDOC_17722

Syntax validation failed for document number <document number> because mandatory
segment is missing: <segment name>.

Explanation:

The session is configured to validate outbound IDocs and write invalid IDocs to a relational or
flat file target. The Integration Service determined that a value for the mandatory segment in
the IDoc is missing.

User Response:

Correct the source data so that the mandatory segment contains values.

IDOC_17723

Syntax validation failed for document number <document number> because maximum
occurrence is higher than maximum limit for: <segment name>.

Explanation:

The session is configured to validate outbound IDocs and write invalid IDocs to a relational or
flat file target. The Integration Service determined that the segment contains more than the
allowed number of records.

User Response:

Correct the source data so that the number of records for the segment do not exceed the
maximum number allowed.

IDOC_17724

Syntax validation failed for document number <document number> because minimum
occurrence is less than the minimum limit for: <segment name>.

Explanation:

The session is configured to validate outbound IDocs and write invalid IDocs to a relational or
flat file target. The Integration Service determined that the segment contains less than the
minimum number of records allowed.

User Response:

Correct the source data so that the number of records for the segment meet the minimum
number of records allowed.

IDOC_17725

Extended Syntax Check skipped because Error Output port is missing. Recreate the SAP/ALE
IDoc Interpreter transformation.

Explanation:

The outbound IDoc session contains an SAP/ALE IDoc Interpreter transformation created in
version 7.x. The Extended Syntax Check session property is selected. However, the
Integration Service cannot validate outbound IDocs for an SAP/ALE IDoc Interpreter
transformation created in earlier versions because the transformation does not contain an
Error Output port.

User Response:

Recreate the SAP/ALE IDoc Interpreter transformation.

IDOC_17742

Cache folder specified for the SAP/ALE IDoc Prepare transformation <transformation name>
is invalid.

Explanation:

The cache directory specified for the SAP/ALE IDoc Prepare transformation does not exist.

User Response:

In the session properties, enter a valid directory for the Cache Directory property.

IDOC_17743

The Integration Service could not access the cache block in group <group>. Increase the
cache size.

Explanation:

The cache size specified for the SAP/ALE IDoc Prepare transformation is inadequate.

User Response:

In the session properties, increase the cache size.

IDOC_17744

The SAP/ALE IDoc Prepare transformation did not receive control record data for the IDoc
type <IDoc type>.

Explanation:

The source in the inbound IDoc mapping does not contain valid data for the IDoc control
record.

IDOC Messages

157

158

User Response:

Verify that the source data contains valid control record data.

IDOC_17747

<Value> orphan rows were received by the SAP/ALE IDoc Interpreter transformation.

Explanation:

The SAP/ALE IDoc Interpreter transformation received orphan rows. The session fails if the
Orphan Row Handling session property is set to Error and the error count has exceeded the
error threshold.

User Response:

Verify that all child rows have parent rows.

IDOC_17748

The SAP/ALE IDoc Interpreter transformation received orphan row <index of the row> in
group <group> with primary key <primary key>.

Explanation:

The SAP/ALE IDoc Interpreter transformation received an orphan row. The session fails if the
Orphan Row Handling session property is set to Error and the error count has exceeded the
error threshold.

User Response:

Verify that all child rows have parent rows.

IDOC_17749

<Value> duplicate rows were received by the SAP/ALE IDoc Interpreter transformation.

Explanation:

The SAP/ALE IDoc Interpreter transformation received duplicate rows. The transformation
uses the segment number as the primary key to detect duplicate rows. The segment number
is part of the header data for each segment data row that the transformation receives for the
IDoc message.

User Response:

Verify that each segment in the IDoc message has a unique segment number.

IDOC_17750

Reader buffer flush failed.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

IDOC_17755

The type A connection to the SAP system failed.

Explanation:

The SAP_ALE_IDoc_Writer application connection object contains invalid values for one or
more connection parameters.

User Response:

Enter correct values for the connection parameters in the SAP_ALE_IDoc_Writer application
connection object.

Chapter 10: I Message Codes

CHAPTER 11

J Message Codes
This chapter includes the following topics:
JDE Messages, 159
JMS Messages, 164
JSDK Messages, 173
JTX Messages, 173

JDE Messages
JDEWRDR_50004

The PowerCenter Integration Service failed to fetch connection information from the
repository.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JDEWRDR_50005

The PowerCenter Integration Service failed to fetch the database type from the repository.

Explanation:

The PowerCenter Repository Service is not running.

User Response:

Verify that the PowerCenter Repository Service is running.

The PowerCenter Integration Service failed to fetch the field attribute from the repository.

Explanation:

Explanation:

The PWX_JDEWORLDPATH environment variable is not set.

User Response:

Set the PWX_JDEWORLDPATH environment variable.

JDEWRDR_50031

PowerExchange for JD Edwards World is not enabled on PowerCenter or the license has
expired.

Explanation:

The license for PowerExchange for JD Edwards World does not exist in the repository.
-orThe license for PowerExchange for JD Edwards World is expired.

160

User Response:

Add a valid license key using the Administrator tool. If the problem persists, contact
Informatica Global Customer Support.

JDEWRDR_50037

Mismatch in datatype or precision or both for a field.

Explanation:

The datatype or precision or both for a field at the mapping level is not compatible with the
field in the target.

User Response:

Verify that the datatype and precision for a field at the mapping level match with the field in
the target.

JDEWRDR_50040

The libraries specified in the JDE Library List do not contain the table <table name>.

Explanation:

The specified libraries do not contain the required table.

Chapter 11: J Message Codes

User Response:

Verify that the library containing the table is part of the JDE Library List field.

JDEWRDR_50042

Invalid value specified for the Number of Sorted Ports property at the session level.

Explanation:

A negative value is specified for the Number of Sorted Ports property.

User Response:

Start the PowerExchange Listener on the AS/400 machine.

-or-

Explanation:

The PowerExchange license is invalid.

User Response:

Provide a valid license key.

-or-

JDE Messages

161

Explanation:

The network is down.

User Response:

Contact Informatica Global Customer Support.

Verify that the CFG file is configured for the PowerExchange Listener on the AS/400 machine.
-or-

Explanation:

The PowerExchange license key specified is not valid.

User Response:

Provide a valid license key.

-or-

Internal error.

User Response:

Contact Informatica Global Customer Support.

JDE Messages

163

JDEWRDR_51026

PowerExchange failed to bind a column.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JMS Messages
JMS_1001

Failed to connect to a JNDI provider: <error message>.

Explanation:

The Integration Service could not connect to a JNDI provider.

User Response:

Check the additional error message for more information.

JMS_1002

The object <object name> looked up from JNDI is not a Destination object.

Explanation:

The value for JMS Destination in the JMS application connection is not valid.

User Response:

Enter a valid value for JMS Destination. Use a value that exists in the JNDI configuration.

JMS_1003

Failed to set JMS exception listener: <error message>.

Explanation:

The Integration Service cannot set a listener for JMS exceptions.

User Response:

Verify that the JNDI server is running. If necessary, start the server.

JMS Messages

165

166

Explanation:

JMS could not create the message consumer.

User Response:

Check the additional error message for more information.

JMS_1021

Failed to create the message consumer because of conflicting JMS session and JMS
connection objects.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JMS_1022

Failed to get the JMS destination <destination>. Reason: <error message>.

Explanation:

The specified value for the JMS Destination attribute in the JMS application connection does
not exist in the JNDI configuration.

User Response:

Configure JNDI to include the value. Or, use a value that exists in the JNDI configuration.

JMS_1023

Failed to get the Queue Connection Factory <queue connection factory>. Reason: <error
message>.

Explanation:

The Integration Service cannot retrieve the queue connection factory from JNDI to connect to
JMS. The value for the JMS Connection Factory Name attribute may not be valid.

User Response:

Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure
the value exists in the JNDI configuration.

Explanation:

The JNDI server may not be running.

User Response:

Verify that the JNDI server is running. If necessary, start the JNDI server.

JMS_1024

Failed to get the Topic Connection Factory <topic connection factory>. Reason: <error
message>.

Explanation:

The Integration Service cannot retrieve the topic connection factory from JNDI to connect to
JMS. The value for the JMS Connection Factory Name attribute may not be valid.

User Response:

Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure
the value exists in the JNDI configuration.

Explanation:

The JNDI server may not be running.

User Response:

Verify that the JNDI server is running. If necessary, start the JNDI server.

Chapter 11: J Message Codes

JMS_1026

The file jndi.properties is not found. No additional SSL related properties are used at runtime.

Explanation:

The Integration Service could not run the session with SSL, because it could not find the
JNDI.properties file.

User Response:

To run the session with SSL, add the JNDI.properties file with the necessary SSL
configuration to the <INFA_HOME>/server/infa_shared/SrcFiles directory.

JMS_2002

Error in getting the session extension information for Source Qualifier <Source Qualifier
name>.

Explanation:

The Integration Service cannot read the session properties. The repository may contain
inconsistencies.

The partition #<number> of Source Qualifier <Source Qualifier name> failed to get cache
coordinator for recovery.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JMS_2036

File cache folder is not provided. Please enter a file cache folder.

Explanation:

You enabled message recovery for the session, but did not specify a file cache folder.

User Response:

In the session properties, enter a file cache folder.

JMS_2037

Failed to create storage information object for Guaranteed Message Delivery. Reason: <error
message>.

Explanation:

The Integration Service encountered an error acknowledging a source message.

User Response:

Check the additional error message for more information.

JMS_2046

A data conversion error happened while processing the message for field <field name> in the
Source Qualifier <Source Qualifier name>.

Explanation:

The Integration Service could not process the specified field because of a data conversion
error. The datatype for the field is not compatible with the datatype for the corresponding field
in the source definition.

Chapter 11: J Message Codes

User Response:

Make sure that the datatype for the field in the JMS source messages is compatible with the
datatype in the source definition.

JMS_2047

Message listener cannot be set: <error message>.

Explanation:

The Integration Service cannot set the JMS message listener.

User Response:

Verify that the JMS settings are correct. Check the additional error message for more
information.

JMS_2052

The jms.jar library could not be loaded.

Explanation:

The Integration Service could not start the session because it could not load the jms.jar file.

User Response:

Verify that the jms.jar file is in the Integration Service /bin/javlib directory.

JMS_2063

The Integration Service fails a JMS real-time session that is enabled for recovery and contains
multiple partitions.

Explanation:

A JMS real-time session that contains multiple partitions cannot be enabled for recovery.

User Response:

Delete the partitions or do not enable the session for recovery.

JMS_2064

Source Qualifier <Source Qualifier name> received <number of recovery messages received>
out of <number of possible recovery messages> possible recovery messages. The Integration
Service processed the messages in the previous session and will delete them through
partition <partition ID>.

User Response:

Restart the session. If the problem persists, contact Informatica Global Customer Support.

JMS_2065

Source Qualifier <Source Qualifier name> received <number of recovery messages received>
out of <number of possible recovery messages> possible recovery messages. The Integration
Service did not process the messages in the previous session and will write the messages
through partition <partition ID>.

Cannot create message writer: <error message>.

Explanation:

Internal error.
Out of memory error.

User Response:

Check the additional error message for more information.

Contact Informatica Global Customer Support.

170

JMS_3013

Cannot create a message object because an invalid message type is given.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JMS_3014

The field <field name> is not a valid JMS target field.

Explanation:

The repository may contain inconsistencies.

User Response:

Contact Informatica Global Customer Support.

JMS_3015

An invalid row type was encountered. JMS writer will publish a message if the row type is
INSERT, UPDATE, and DELETE.

Explanation:

The row type for the source rows is Data Driven, but must be Insert, Update, or Delete.

Chapter 11: J Message Codes

User Response:

From the Properties tab in the session properties, set the value for the Treat Source Rows As
property to Insert, Update, or Delete.

JMS_3016

JMS writer encountered an unknown row type error.

Explanation:

The Integration Service could not convert the data for the specified field when writing
messages to the JMS target. The field contains incompatible datatypes. The Integration
Service rejected the field.

User Response:

Check the additional error message for more information.

JMS_3024

Invalid datatype ID: <error message>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

JMS_3025

JMS writer received NULL for the field <field name>, which is set to Not Null. The message
will be rejected.

Explanation:

The specified field is set to Not Null in the target definition for the mapping.

JMS Messages

171

172

User Response:

Edit the target definition in the Designer, and clear the Not Null option for the field to prevent
messages with a NULL value from being rejected.

JMS_3026

JMS writer encounters a JMS exception: <error message>.

Explanation:

The Integration Service encountered a JMS error when writing messages to the target.

User Response:

Check the additional error message for more information. If the additional error message is
an MQSeries JMS message regarding an invalid value for the JMSTimeToLive field in the
target, it prints the value for field multiplied by 1,000. For example, if the JMSTimeToLive
value in the target is -1, the MQSeries JMS message prints -1,000.

JMS_3027

JMS writer encountered an out of memory error.

Explanation:

JVM is out of memory. As a result, the PowerCenter session failed.

User Response:

Increase the memory for JVM. Then restart the session.

JMS_3028

JMS writer encountered an error in getting the default JMSReplyTo object <object name>
from JNDI. Reason: <error message>.

Explanation:

The Integration Service could not obtain a value for JMSReplyTo from JNDI.

User Response:

Check the additional error message for more information.

JMS_3029

JMS writer encountered an error in processing the data for the field <field name> in the target
<target name>. Reason: <error message>.

Explanation:

The Integration Service could not process data for the specified field in the target.

User Response:

Check the additional error message for more information.

JMS_3030

The jms.jar library could not be loaded.

Explanation:

The file jms.jar is not available in the <PowerCenter Installation Directory>/server/bin/javalib

directory.

User Response:

Copy jms.jar to the <PowerCenter Installation Directory>/server/bin/javalib directory.

JMS_3031

The Integration Service cannot guarantee that it will process messages only once. Some
messages may be lost or duplicated.

Explanation:

Integration Service did not register the JMS writer with the cache coordinator.

User Response:

For relational targets, verify that the recovery table exists and the table creation privilege to
the database user name is configured in the target database connection. For queue targets,
verify that the recovery queue exists.

JMS_3033

The Integration Service failed to write the recovery state to the recovery <recovery destination
type>, recovery destination <recovery destination name>, connection factory <connection
factory name>. Reason: <reason for error>.

User Response:

Review the reason for error and make any appropriate changes.

JMS_3034

Field <field name> for target <target name> can be projected if IsDestinationNameDynamic is
set to true in session properties.

Explanation:

The JMS target is configured to have a static destination name. When the destination name
is static, the Integration Service uses the destination name from the application connection.
You cannot project the destination name in the JMS target.

Chapter 11: J Message Codes

User Response:

Enable IsDestinationNameDynamic in session properties, or remove the link to the

destination in the JMS target.

JSDK Messages
JSDK_42021

Failed to load the library: <library name>.

Explanation:

You attempted to run a session to read messages from a JMS source or write messages to a
JMS target. Or, you attempted run a session to read documents form a webMethods source
or write documents to a webMethods target. However, the JVM library is not properly set on
the machine hosting the Integration Service.

User Response:

If the Integration Service runs on Windows, verify that the path to the jvm.dll file is properly
set. You can do this from the Environment tab in the Systems settings on the Control Panel.
If the Integration Service runs on UNIX or Linux, make sure the library path for the JVM
library is properly set.

JSDK_42075

The Integration Service is trying to reset the session but the resetNotification API has not
been implemented in the Java transformation <transformation>."

Explanation:

If you run the Data Transformation Manager (DTM) in restart mode and a mapping contains a
Java transformation that does not implement the resetNotification method, this error occurs.

User Response:

Implement the resetNotification method in the Java transformation.

JTX Messages
JTX_1001

Failed to create partition driver. An exception occurred while loading partition driver class
from byte code: <exception text>.

Explanation:

The Integration Service failed to create the partition driver for the Java transformation class.
This error can occur due to inconsistent byte code in the repository.

User Response:

Use the Designer to recompile the byte code for the Java transformation, and run the session
again.

JTX_1002

Failed to find metadata extension <metadata extension name>.

Explanation:

The repository stores the code for the Java transformation in metadata extensions for the
Java transformation. The Integration Service could not find the metadata extensions that
correspond to the code for the Java transformation in the repository. This error can occur due
to inconsistent metadata in the repository.

User Response:

Use the Designer to save the Java transformation to the repository, and run the session
again. Otherwise, contact Informatica Global Customer Support.

JSDK Messages

173

174

JTX_1003

Failed to retrieve metadata for input/output ports: <port names>.

Explanation:

The Integration Service could not retrieve the metadata for the input and output ports in the
Java transformation from the repository. This error can occur due to inconsistent metadata in
the repository.

User Response:

Use the Designer to save the Java transformation to the repository, and run the session
again. Otherwise, you need to re-create the repository.

JTX_1005

Column name <name> is not valid.

Explanation:

The Integration Service could not retrieve the metadata for the Java transformation because
the column name is not valid.

User Response:

None.

JTX_1006

The number of groups is not valid. The Java transformation must have exactly one input
group and one output group.

Explanation:

The Java transformation contains more than one input group or output group.

User Response:

Edit the Java transformation in the Designer and remove the extra group or groups.

JTX_1008

The row type <row type> is not valid. Valid row types for the setOutRowType API are INSERT,
DELETE, and UPDATE.

Explanation:

You used the setOutRowType API to set the output row type for the Java transformation.
However, the specified row type is not valid. Valid row types are INSERT, DELETE, and
UPDATE.

User Response:

Change the row type for the setOutRowType API to a valid type.

JTX_1009

Failed to create partition driver. The byte code for the Java transformation is not valid.

Explanation:

The Integration Service failed to create the partition driver for the Java transformation class.
This error can occur due to inconsistent byte code in the repository.

User Response:

Use the Designer to recompile the byte code for the Java transformation, and run the session
again.

JTX_1010

Transformation name cannot be null. Failed to create class loader.

Explanation:

Because the Integration Service could not retrieve the transformation name from the
repository, the Integration Service failed to create the class loader for a Java transformation.

User Response:

None.

JTX_1011

Error thrown by Java transformation failSession API: <error text>.

Explanation:

You used the failSession method to throw a fatal error in the Java transformation.

User Response:

None.

JTX_1013

Error message: <message text>.

Explanation:

Explanation:

In the Java code for the transformation, the call to defineJExpression failed.

User Response:

In the Designer, verify that the expression is valid and run the session again.

JTX_1102

The specified row type <row type> is not valid. Valid row types are: INSERT, DELETE, and
UPDATE.

Explanation:

You used a row type that is not valid in a Java expression. Valid row types are INSERT,
DELETE, and UPDATE.

User Response:

Use a valid row type.

JTX_1103

NULL result.

Explanation:

In a Java transformation, you used an expression that returned a NULL value. You cannot
return NULL values from a Java expression.

User Response:

Modify the expression in the Designer so it returns a non-NULL value.

JTX Messages

175

176

JTX_1104

Result data type is <type>. This API call is not valid.

Explanation:

You passed a datatype that is not valid to an API method in a Java expression.

User Response:

Modify the call to the API method to pass a valid datatype, or use the correct API method.

JTX_1108

The expression string parameter of callable API <method name> cannot be null.

Explanation:

You passed a NULL value for the String parameter of a Java expression API method. The
String parameter cannot take a NULL value.

User Response:

Modify the call the Java expression API method to pass a non-NULL value to the String
parameter.

JTX_1109

Too few parameters were passed to the expression <expression name>. Expected: <number>
parameters. Passed: <number> parameters.

Explanation:

In a Java transformation, you did not pass the required number of parameters to an
expression.

User Response:

Edit the Java code for the transformation and pass the correct number of parameters to the
expression.

JTX_1110

Too many parameters were passed to the expression <expression name>. The extra
parameters are ignored.

Explanation:

In an expression in a Java transformation, you passed more parameters than the expression
requires. The Integration Service ignored the extra parameters.

User Response:

None. If you do not want the Integration Service to ignore the extra parameters, redefine the
Java expression.

JTX_1111

The JExpression API <method name> parameter cannot be null.

Explanation:

In a Java expression API method, you passed a NULL value to a parameter. You cannot
pass NULL values for Java expression API method parameters.

User Response:

Pass a non-NULL value to the parameter in the Java expression API method.

Chapter 11: J Message Codes

JTX_1114

Failed to load class <class name>: <error text>.

Explanation:

The Integration Service could not load the Java transformation class or an inner class in a
Java transformation. This error can occur if the repository contains inconsistent data for the
byte code or the repository does not contain the updated byte code for the transformation.

User Response:

Correct the error indicated in the error text in the message and run the session again. You
might need to recompile the Java code for the transformation in the Designer.

JTX_1115

An exception occurred during the initialization of JExpression object: <name>.

Explanation:

The initialization of a JExpression object failed.

User Response:

Verify that the defined expression is valid and run the session again.

JTX_1117

Data was truncated for field <port name>.

Explanation:

The precision of the data assigned to a binary or string output port in a Java transformation is
greater than the configured precision for the port. As a result, the Java transformation
truncated the data for the port. This warning can occur for data assigned to an output port.

User Response:

Make sure the precision of the port is equal to or greater than the precision of the data
assigned to the port.

JTX_60000

Cannot validate Java transformation. Unable to retrieve metadata extensions from repository.

Explanation:

The Designer or Integration Service encountered an internal error when retrieving the
metadata extensions for the Java transformation.

User Response:

Contact Informatica Global Customer Support.

JTX_60001

Cannot validate Java transformation. Unable to retrieve Java code snippets from the
repository.

Explanation:

The Designer or Integration Service encountered an internal error when retrieving the Java
code snippets for the transformation from the repository.

User Response:

Contact Informatica Global Customer Support.

JTX_60002

Cannot validate Java transformation. Unable to retrieve byte code from the repository.

Explanation:

The Designer or Integration Service encountered an internal error when retrieving the byte
code for the transformation from the repository.

User Response:

Contact Informatica Global Customer Support.

JTX_60003

Cannot validate Java transformation. Unable to retrieve CRC value from the repository.

Explanation:

The Designer or Integration Service encountered an internal error when retrieving the CRC
value for the transformation from the repository. The Designer or Integration Service
compares the current CRC value for the byte code to the CRC value stored in the repository
to verify the byte code for the transformation.

User Response:

Contact Informatica Global Customer Support.

JTX_60004

Byte code for the transformation is not in the repository. Java transformation is invalid.

Explanation:

The byte code for the transformation is not in the repository.

User Response:

Compile the Java code for the transformation, and validate the transformation or mapping.

JTX Messages

177

178

JTX_60005

Byte code in the repository is invalid. Java transformation is invalid.

Explanation:

The CRC value for the byte code retrieved from the repository does not match the CRC value
stored in the repository. As a result, the transformation is not valid.

User Response:

Compile the Java code for the transformation, and validate the transformation or mapping.

Chapter 11: J Message Codes

JTX_60014

Cannot validate Java transformation. Unable to retrieve precision mode from the repository.

Explanation:

The Designer or Integration Service could not retrieve the value of the precision mode for the
Java transformation from the repository. This error can occur due to inconsistent data in the
repository.

User Response:

Contact Informatica Global Customer Support.

JTX Messages

179

CHAPTER 12

L Message Codes
This chapter includes the following topics:
LB Messages, 180
LDAP Messages, 181
LDBG Messages, 185
LGS Messages, 186
LIC Messages, 188
LM Messages, 192
LMTGT Messages, 205
Lotus Notes Messages, 207

LB Messages

180

LB_47007

Submitted task <task name> was canceled by a user.

Explanation:

The Session or Command task failed because it was stopped.

User Response:

Restart the task.

LB_47008

Submitted task <task name> was canceled because no available node has the resources
required by the task.

Explanation:

The Session or Command task failed because no available node has the resources required
by the task.

User Response:

Verify that at least one node has the resources required to run the task. Verify the nodes that
have the required resources are running and available.

LB_47010

The Integration Service failed to load the external resource manager library due to error <error
text>.

Explanation:

The PowerCenter administrator configured PowerCenter to work with a third-party resource

manager. The Integration Service is unable to load the resource manager library.

User Response:

Verify the following:

The third-party resource manager library exists in the location specified in the PATH.
The user account authorized to start Informatica Services has read and execute

permissions on the library file.

The library file is not corrupt.

LB_47011

The Integration Service failed to retrieve the external resource manager interface due to error
<error text>.

Explanation:

The PowerCenter administrator configured PowerCenter to work with a third-party resource

manager. The Integration Service is unable to access the resource manager interface.

User Response:

Contact the third-party resource manager technical support.

LB_47012

The external resource manager interface failed to initialize due to error <error text>.

Explanation:

The PowerCenter administrator configured PowerCenter to work with a third-party resource

Verify that the supportedControl attribute under Root DSE is configured and accessible.

LDAPRDR_2046

The PowerCenter Integration Service failed to read the change log information from the file
<CDC file name>.

Explanation:

The user associated with the connection does not have the read permission on the Change
Data Capture file.

LDAP Messages

181

User Response:

Verify that the user associated with the connection has the read permission on the Change
Data Capture file.

LDAPRDR_2047

The PowerCenter Integration Service failed to write the change log information to the file
<CDC file name>.

Explanation:

The user associated with the connection does not have the write permission on the Change
Data Capture file.

User Response:

Verify that the user associated with the connection has the write permission on the Change
Data Capture file.

LDAPRDR_2048

The PowerCenter Integration Service could not retrieve response for the Sort request control
from the context. Reason: <reason>

Explanation:

The LDAP directory server is not configured for the Sort response control.

User Response:

Verify that the LDAP directory server is configured for the Sort response control.

LDAPRDR_2049

The PowerCenter Integration Service could not retrieve response for PagedResultControl
from the context.

Explanation:

The LDAP directory server is not configured for PagedResultResponseControl.

User Response:

Verify that the LDAP directory server is configured for PagedResultResponseControl.

LDAPRDR_2050

The PowerCenter Integration Service could not retrieve the modification details for the
change log entry <entry_name> due to missing values for one of the required attributes.

Explanation:

The values for the attributes changeNumber, changeType, or targetDn are missing or not
accessible.

User Response:

Verify that the attributes changeNumber, changeType, or targetDn exist, and the user
associated with the connection has read permission on the attributes for each change that is
logged in change log DN.

LDAPRDR_2051

The PowerCenter Integration Service could not retrieve the entry for dn=<attribute value>
from the LDAP directory server.

Explanation:

The DN is either renamed or deleted from the LDAP directory server.

User Response:

Verify that the session is configured for the required LDAP directory server and the DN entry
exists in the server.

LDAPRDR_2052

The PowerCenter Integration Service failed to expand the variable to get the Change Data
Capture file location. Reason: <reason>

Explanation:

The $PMRootDir property is not configured for the PowerCenter Integration Service .

User Response:

Verify that $PMRootDir property is configured for the PowerCenter Integration Service .
-or-

182

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

LDAPRDR_2053

The PowerCenter Integration Service failed to propagate the modrdn change for dn=<attribute
value>.

Explanation:

The source attribute dn is not linked to the target attribute dn.

Chapter 12: L Message Codes

User Response:

Link the source attribute dn to the target attribute dn.

LDAPRDR_2056

The PowerCenter Integration Service failed to create the Sort control.

Explanation:

The LDAP directory server is not configured for the Sort control.

User Response:

Verify that LDAP directory server is configured for the Sort control.

LDAPRDR_2058

The PowerCenter Integration Service failed to create the directory in which the Change Data
Capture file is to be created.

Explanation:

The user associated with the connection does not have permission to create a directory in the
specified location.

User Response:

Verify that the user associated with the connection has the permission to create a directory in
the specified location.

LDAPRDR_2059

The PowerCenter Integration Service could not retrieve the newRdn attribute for the old
targetDn <attribute value> from the LDAP directory server.

Explanation:

The value for the newRdn attribute of modrdn chagneType is missing or not accessible.

User Response:

Verify that the value for the newRdn attribute exists, and the user associated with the
connection has the read permission on the change log DN to read the attribute for each
logged modrdn changeType.

LDAPRDR_2062

The PowerCenter Integration Service could not find the change log entries under DN <change
log DN name>.

Explanation:

The change log is not enabled on the LDAP directory server.

-orThe user associated with the connection does not have the access permission on the change
log.

User Response:

Verify that the change log is enabled on the directory server and is accessible.

LDAPRDR_2072

The PowerCenter Integration Service failed to perform an initial check for Change Data
Capture data transfer. Reason: <reason>

Explanation:

The change log is either modified or deleted from the LDAP directory server.

User Response:

Verify that the change log is not modified or deleted. Modify the Change Data Capture file to
update the change number to -1.
-or-

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

LDAPRDR_2076

An error occurred while expanding variable to get search filter expression. Reason: <reason>

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

LDAP Messages

183

LDAPRDR_2078

The PowerCenter Integration Service failed to process the referral entry <entry DN name> due
to error in authenticating the user against the referenced directory server.

Explanation:

The specified credentials are invalid and cannot resolve the referral entries on the referenced
directory server.

User Response:

Create a user on the referenced directory server with the same name and password.
-orSpecify the credentials that work on both the directory servers to resolve referral entries.

LDAPWRT_1000

Failed to find the PowerExchange for LDAP license key.

Explanation:

A valid license key for PowerExchange for LDAP was not found.

User Response:

Add a valid license key through the Administrator tool.

LDAPWRT_3031

Unable to <operation type> entry <entry DN name>.

Explanation:

The PowerCenter Integration Service failed to insert or update the entry in the LDAP
directory server due to violation of the LDAP schema or object class rules.

User Response:

Verify that the entry to be inserted or updated in the LDAP directory server conforms to the
LDAP schema or object class rules.

LDAPWRT_3032

Unable to insert the entry <entry DN name> because it already exists in the LDAP directory
server.

User Response:

Verify that the entry to be inserted does not exist in the LDAP directory server.

LDAPWRT_3037

The PowerCenter Integration Service failed to delete the entry <entry DN name> because it
does not exist in the LDAP directory server.

User Response:

Verify that the entry to be deleted exists in the LDAP directory server.

LDAPWRT_3043

The PowerCenter Integration Service failed to update the entry <entry DN name> as the
attribute value to be updated is used in RDN.

Explanation:

The RDN of the entry uses the attribute value that is to be modified in the LDAP directory
server.

User Response:

Verify that the RDN of the entry does not use the attribute value that is to be modified in the
LDAP directory server.
-orIn the target session properties, select the option to delete the old RDN when the attribute
value used in the RDN is updated.

LDAPWRT_3052

Unable to <operation type> the attribute <attribute name> for the entry <entry DN name>.

Explanation:

The PowerCenter Integration Service failed to insert or update the attribute value for the
entry in the LDAP directory server due to violation of the LDAP schema or object class rules.

User Response:

Verify that the attribute value to be inserted or updated conforms to the LDAP schema or
object class rules.
-or-

Explanation:

184

Chapter 12: L Message Codes

The PowerCenter Integration Service failed to delete the attribute value for the entry as the
attribute value does not exist.

User Response:

Verify that the attribute value to be deleted exists for the entry in the LDAP directory server.

LDBG Messages
LDBG_8316

Error. The DTM server ran out of buffer pool data blocks for Partition Point <partition point
name> where <transformation name> is the transformation name.

Explanation:

During a user-defined commit session, the Data Transformation Manager ran out of buffer
pool data blocks, which caused the session to fail.

User Response:

In the session properties, increase the DTM buffer block size.

Modify the Transaction Control expression or the Custom transformation procedure code so
that the transformation issues commits more frequently.

LDBG_21035

Datablock write-lock error. offset <offset value>, reason [No space left on device].

Explanation:

The Integration Service could not write data to the disk because there is not enough space.

User Response:

Increase the amount of free space on the Integration Service system disk. Verify that the
operating system does not limit the amount of disk space for the user who starts the
Integration Service.

Explanation:

This message follows CMN_1107. The Integration Service could not write to a Joiner index or
data cache file because there is not enough space on the disk.

User Response:

Increase the Joiner index and data cache sizes. If possible, increase the index and data
cache sizes to hold all of the data.

LDBG_21149

ERROR determining truncate table order - could not create constraint load dependencies for
target.

Explanation:

You are attempting to truncate target tables, but the Integration Service is unable to
determine dependencies between target tables, possibly due to errors such as circular key
relationships.

User Response:

Ensure the validity of dependencies between target tables.

LDBG_21178

ERROR: Self-referential constraint in target.

Explanation:

You have set the session for constraint-based loading, but the Integration Service is unable
to determine dependencies between target tables, possibly due to errors such as circular key
relationships.

User Response:

Ensure the validity of dependencies between target tables.

LDBG_21409

Target <target name> Warning: Primary key table for Foreign key <foreign key port name> is
not from the same active source or transaction generator. This constraint will not be
enforced; as a result, the session may hang because of potential deadlock.

Explanation:

The mapping writes to target tables that have a primary key-foreign key relationship, but the
targets receive data from different transaction generators, such as a Transaction Control
transformation, or active sources. The Integration Service cannot enforce the primary keyforeign key relationship. The session might hang depending on the source data.

LDBG Messages

185

User Response:

If the session hangs, design the mapping to enforce constraint-based loading. Or, remove the
primary key-foreign key relationship between the targets in the target database.

LDBG_21511

TE: Fatal Transformation Error.

Explanation:

The Integration Service encountered a fatal row error and failed the session.

User Response:

See the additional error messages for more information.

LDBG_21604

Data block read-lock error, offset <number>, reason: <reason>.

Explanation:

Error occurred trying to read from the joiner cache.

User Response:

Truncate the targets and run the session again.

LDBG_21605

Cannot open files in the directory <directory name>.

Explanation:

Cannot open files in the joiner cache directory.

User Response:

Check file system permission and free space in the cache directory.

LDBG_21633

For the dynamic lookup cache for <Lookup transformation>, an input row has NULL value in
condition fields. This row will not be used for update of the lookup cache.

Explanation:

The Lookup transformation in the mapping uses a dynamic lookup cache, and the source row
contains a null value in a column used in the lookup condition.

User Response:

None. When the row exists in the lookup cache, the Integration Service does not update the
row in the cache or target table.

LDBG_21668

Error: The Informatica server license does not allow more than one database license to be
used at a time.

Explanation:

The Integration Service configuration contains more than one database license.

User Response:

The Informatica license does not allow you to use more than one database license at a time.
Configure the Integration Service with only one database license.

LGS Messages

186

LGS_10006

The file <file name> was skipped during automatic purge.

Explanation:

The day limit or size limit for log event files was reached, and the Log Manager purged the
log event files. However, the Log Manager did not delete the file because it was in use or
recently modified.

User Response:

None. The Log Manager will delete the file during the next log purge if the file is not in use or
recently modified.

LGS_10010

Not all files are deleted in directory: <directory name>.

Explanation:

Explanation:

The Log Manager could not create the directory in the shared location for log event files. This
error can occur because the Log Manager does not have sufficient access permissions on
the shared directory location for the log event files.

User Response:

Make sure the user account that runs Informatica Services has read and write permission on
the shared directory location.

LGS_10019

Failed to open the file stream <file name> due to the following error <error text>.

Explanation:

The Log Manager was unable to open the log event file for reading or writing. This error can
occur when the permissions for a log event file or the log event directory are modified after
the Log Manager begins reading or writing or because the file was removed.

User Response:

Correct the error indicated in the message and make sure the user account that runs
Informatica Services has read and write permission on the file.

LGS_10021

Failed to read log event from the file stream <file name> due to the following error <error text>.

Explanation:

The Log Manager attempted to retrieve log events from the log event file. However, the log
event file contains inconsistent data.

User Response:

Correct the error indicated in the message.

LGS_10024

Log request failed due to the following error <error text>.

Explanation:

The Log Manager attempted to retrieve log events from the shared directory location, but the
retrieval failed due to an error.

User Response:

Correct the error indicated in the message and view logs events again.

LGS_10026

The log service configuration is missing the log service directory value for the node <node
name>.

Explanation:

The Log Manager could not write to the shared directory path for the log event files because
the directory location is missing in the domain configuration.

User Response:

Configure a directory for the log event files.

LGS Messages

187

LGS_10028

The index file <file name> is corrupt.

Explanation:

The Log Manager uses an index file in each log file directory for quick access to log event
data files. The Log Manager was unable to read from or write to the index file. This error can
occur when the permissions for an index file are modified or because the file was removed.

User Response:

Correct the error indicated in the message and view log events, export log events, or purge
log events again. Make sure the user account that runs Informatica Services has read and
write permission on the file.

LGS_10034

Log request failed due to the following error <error text>. Unable to rollback changes due to
the following error <error text>.

Explanation:

The Log Manager wrote to log event files. However, the process was interrupted due to an
error, and the Log Manager could not roll back the changes it made to the log event file. This
error can occur if the Log Manager writes to a shared directory location that becomes
unavailable during the write process.

User Response:

Correct the errors indicated in the message and make sure the shared directory location is
available.

LGS_10035

The timestamp index file <file name> is corrupted.

Explanation:

The Log Manager uses the timestamp index file to access the log event files in a directory.
However, the timestamp index file contains inconsistent data and the Log Manager cannot
access the log event files in the directory.

User Response:

Contact Informatica Global Customer Support.

LGS_10052

The Log Manager has no record of the requested session or workflow run.

Explanation:

The Log Manager has no information about the session or workflow run. The name is invalid,
the run is not the latest, or the database table was purged.

User Response:

If you are using infacmd, verify that the workflow or session name is valid. If you are trying to
get the session or workflow log in the Workflow Monitor, select the latest session or workflow
run.

Chapter 12: L Message Codes

User Response:

Wait for a new master gateway to be elected. The new master gateway will enable its Service
Manager. If a new master gateway does not come up automatically, manually recycle this
node.

LIC_10019

Request parameters must contain a valid service name followed by a valid node name.

Explanation:

A request was received with the wrong number of parameters.

LIC Messages

189

190

User Response:

If the problem persists, contact Informatica Global Customer Support.

LIC_10020

The operating system type could not be established for node <node name>.

Explanation:

A service was attempting to start on a node where the platform could not be established.

User Response:

If the problem persists, contact Informatica Global Customer Support.

LIC_10025

Cannot unassign from license <name of license> because services <list of services enabled>
are enabled and/or services <list of services missing> were not found.

Explanation:

A request was received to unassign enabled services.

User Response:

Disable services before continuing.

Explanation:

A request was received to unassign an unknown service.

User Response:

Verify the service names and resubmit.

LIC_10026

License <license name>/<license serial number> cannot start service <service name> as it is
not licensed to execute on platform <platform name>.

Explanation:

A service was attempting to start on an unlicensed platform.

User Response:

Contact Informatica Global Customer Support to update the license key for the specified
platform.

LIC_10027

Failed to add a license key that expired on <expiration date>.

Explanation:

A request was received to add a license key that has already expired.

User Response:

Either assign service to a license that supports a grid or remove the grid from service.

Chapter 12: L Message Codes

LIC_10035

License <license name>/<license serial number> cannot start repository instance <repo
name> as license does not have a valid repository count.

Explanation:

A Repository Service is assigned to a license that does not allocate Repository Services.

LIC Messages

191

User Response:

Either assign service to a license that supports high availability or remove backup nodes from
service.

LIC_10061

Cannot validate license usage with invalid service name <service name>.

Explanation:

License authorization was requested for a missing or invalid service name.

User Response:

If the problem persists, contact Informatica Global Customer Support.

LIC_10062

Cannot validate license usage with invalid node name <node name>.

Explanation:

License authorization was requested for a missing or invalid node name.

User Response:

If the problem persists, contact Informatica Global Customer Support.

LIC_10063

License <license name/license serial number> cannot start service <service name> as license
does not support operating system profiles.

Explanation:

An Integration Service that uses operating system profiles is assigned to a license that does
not support operating system profiles.

User Response:

Assign the Integration Service to a license that supports operating system profiles.
Disable the use of operating system profiles for the Integration Service.

LIC_10064

Cannot start service <service name> on node <node name> because this would exceed the
number of licensed CPUs for platform <platform name>.

Explanation:

You cannot start the service with the current number of licensed CPUs.

User Response:

Contact an Informatica sales representative to purchase additional logical CPUs for this
platform. If you do not know who your sales representative is, contact Informatica Global
Customer Support to log a service request.

LM Messages

192

LM_36053

The server mode <current server mode> is invalid. Default server mode <default server
mode> will be used.

Explanation:

You have modified the data movement mode in the Administrator tool.

User Response:

Change the data movement mode to ASCII or Unicode by modifying the Administrator tool.

LM_36072

Cannot get $PMStorageDir from configuration.

Explanation:

A service process could not determine the storage directory used for failover and recovery.

User Response:

Verify that $PMStorageDir is configured properly in the Integration Service process properties.

LM_36129

Cannot open log file <name>.

Explanation:

The Integration Service cannot open the named log file.

User Response:

Verify that the log file exists in the directory you specified in the session or workflow
properties. Also, verify that the user attempting to access the log file has read permission for
the file.

Chapter 12: L Message Codes

LM_36133

Fail in reading log file <name>.

Explanation:

The Integration Service was able to open the named log file, but cannot read it. An
administrator could have deleted the log file while you were attempting to access it.

User Response:

Verify that the log file exists in the directory you specified in the session or workflow
properties. Then try to access the file again.

LM_36134

Session is initializing. Session log file is temporarily unavailable.

Explanation:

You are trying to access a session log file while the session is still initializing.

User Response:

Wait and open the file when the session has finished initializing.

LM_36136

Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration
Service.

Explanation:

The specified task instance did not run.

User Response:

Review the workflow log to view detailed information about why the task instance did not run.

User Response:

Contact Informatica Global Customer Support.

LM_36220

Log file <name> contains no data.

Explanation:

The log file is empty, most likely because someone deleted its contents.

User Response:

If you need to see the log file data, rerun the session or workflow to generate the log file
again.

LM_36225

The session log file was not created for session instance [ID = <number> in folder [ID =
<number>, workflow [ID = <number> [run ID = <number>, worklet [ID = <number> (possibly
because the session failed during initialization).

Explanation:

The Integration Service failed to create the named session log file because the session failed
during initialization.

User Response:

Check the workflow or server log file to see why the session failed.

LM_36229

Request failed because the connection was broken or the client is too slow in processing
replies, client <name>, connection <name>, request ID <number>.

Explanation:

The Integration Service tried to retrieve a session or workflow log file over a network
connection, but the connection was broken or timed out.

LM Messages

193

194

User Response:

Check the network connection and try to open the log file again.

LM_36269

Connection request was made from client <PowerCenter Client> on host <host machine> for
connection to service type <service type>, service name <service>, and service process name
<node>. The connection request failed because the service process <node> is not the
intended service process.

Explanation:

A client application attempted a connection to a service process that is not the master service
process. With pmcmd, this error occurs if you use the host name and port number options
rather than the pmcmd options -d <domain> and -sv <service>.

User Response:

Verify that the node is available and attempt the connection again. If you use pmcmd, use the
options -d <domain> and -sv <service>.

Yes, which is the default value.

Chapter 12: L Message Codes

LM_36310

Workflow <name>: Cannot open log file <name>.

Explanation:

The Integration Service could not open the named log file during execution of the named
workflow. The workflow failed.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

LM Messages

195

196

LM_36363

Workflow <name>: Cannot rename workflow log file <file name> to <file name>.

Explanation:

You saved the workflow logs for the named workflow by number of runs. The Integration
Service encountered an error when it tried to rename an existing log file. The disk on which
the log files are located might be out of space.

User Response:

Check the disk and directory where the log file is located. Make sure the disk is not out of
space.

LM_36364

Workflow <name>: Failed to increment the log file number in the repository.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

LM_36366

<Worklet name>: Failed to set the passed value for variable <name>.

Explanation:

Internal error. The Integration Service failed to pass the initial value of the named variable to
the named worklet.

User Response:

Contact Informatica Global Customer Support.

LM_36367

<Task instance name and path>: Suspension email has an empty user name.

Explanation:

You configured the workflow to send a suspension email, but the email address for the
suspension email is missing.

User Response:

Enter an email address in the Email User Name field for the suspension Email task.

LM_36368

LM Messages

197

198

LM_36471

<Workflow name>: Failover of workflow schedule failed because the information in storage is
inconsistent or incomplete.

Explanation:

Trace message. If you have the high availability option, workflow schedule information is
written to a storage file in the storage directory, $PMStorageDir. The Integration Service
could not retrieve the information required to start up the scheduled workflow on another
node.

User Response:

Explicitly schedule the workflow again to run it.

LM_36476

<Workflow name>: Failover of workflow execution failed because the workflow cannot be
internally scheduled in recovery mode.

Explanation:

After the Integration Service failed over the workflow to another node, an internal limit was
exceeded.

User Response:

Try to recover the workflow manually. Also, verify the availability of the node where the
service process started the workflow.

LM_36477

<Workflow name>: Failed to save workflow information for failover.

Explanation:

The Integration Service was unable to write the workflow data to a storage file to enable
failover.

User Response:

Verify that the Integration Service can access the storage directory $PMStorageDir. To
access the storage directory, the directory must be properly mapped or mounted, and the
Integration Service must have the necessary security permissions. If the directory does not
exist or cannot be written to, the requests cannot be stored for persistence. Verify that the
directory is not full.

Explanation:

You selected the On Failure Email option for the session, but the email address for the postsession email is missing.

User Response:

Enter an email address in the Email User Name field for the post-session Email task.

Chapter 12: L Message Codes

LM_36530

<Task instance name and path>: Failed to send post session failure e-mail for this session
instance.

Explanation:

You selected the On Failure Email option for the session, but the Integration Service failed to
send the post-session email. This might occur if you did not specify an email profile on the
machine hosting the Integration Service, or if the machine does not have an email client.

User Response:

Verify you specify an email profile on the machine hosting the Integration Service, and that
the machine has the correct email client.

LM_36538

<Session instance path>: Unable to write to temporary parameter file <parameter file name>
with error <error number> <cause of error>.

Explanation:

The workflow is configured to run on a grid. The master service process distributed a session
that uses a parameter file to a worker service process. The worker service process needs to
create a temporary parameter file in its $PMTempDir directory using parameter file
information received from the master service process. However, the worker service process
failed to create the temporary parameter file because the Informatica Services account or the
operating system user in the operating system profile does not have write permission on
$PMTempDir, or because the directory contains a file with the same name.

User Response:

Grant read and write permissions on $PMTempDir to the Informatica Services account or the
operating system user in the operating system profile on the worker node, and then run the
workflow again. Or, if $PMTempDir contains a file with the same name as the temporary
parameter file, delete it and run the workflow again.

LM_36539

<Session instance path>: Unable to unlink temporary parameter file <parameter file name>
with error <error number> <cause of error>.

Explanation:

The workflow was configured to run on a grid. The master service process distributed the
session to a worker service process. The worker service process created a temporary
parameter file in $PMTempDir, but it failed to delete the file.

User Response:

On the worker node, grant permissions to delete a file in $PMTempDir for the Informatica
Services account or the operating system user in the operating system profile, and verify that
there is enough disk space. Or, manually delete the temporary parameter file from the
$PMTempDir directory.

LM_36543

<Task name> condition expression eval error < expression >.

Explanation:

The expression you entered may have invalid characters or cannot be evaluated.

User Response:

Verify that the expression is valid in the Workflow Manager.

LM_36544

<Task name>: condition expression <expression> will not evaluate to a numeric value.

Explanation:

You may have entered the wrong datatype in the expression.

User Response:

Review the expression in the Workflow Manager to ensure that it uses Numeric datatypes.

LM_36564

<Task name>: Invalid datatype conversion for variable <name>, expression datatype
<datatype>, variable datatype <datatype>.

Explanation:

In the Workflow Manager, you assigned a value to a variable using the Assignment task. The
Integration Service cannot convert the datatype of the expression to the datatype of the
variable.

User Response:

Either fix the expression in the Assignment task or change the datatype of the variable.

LM Messages

LM_36601

<Timer name> Unable to schedule timer with the timer task manager.

Explanation:

The time specified is invalid. The range must be between 00:00:00 January 1, 1970 UTC, and
3:14:07 January 19, 2038 UTC.

User Response:

Specify a time within the valid range.

LM_36602

<Variable name> Wait for absolute time specified by variable <variable type>. The variable
does not exist.

Explanation:

The variable is not specified in the workflow.

User Response:

Specify the variable in the workflow properties.

LM_36603

<Variable name> Wait for absolute time specified by variable <variable type>. The variable is
not of type date/time.

Explanation:

The variable type entered was not the Date/Time datatype.

User Response:

Change the datatype to Date/Time.

Chapter 12: L Message Codes

By default, the Integration Service creates one asynchronous thread for every 10 repository
connections. The number of threads specified by the LMRepoConnAsyncThreads custom
Integration Service property is less than 10. The specified number of threads is not sufficient
for the number of repository connections.

LM Messages

201

202

User Response:

To use the default number of threads, remove the LMRepoConnAsyncThreads custom

Integration property. Alternatively, you can increase the LMRepoConnAsyncThreads value.

LM_44181

Workflow <workflow name> is impacted. The Integration Service is not configured to run
sessions impacted by dependency updates.

User Response:

In the Administrator tool, configure the Integration Service advanced property to run sessions
impacted by dependency updates.

LM_44183

Scheduling workflow is not allowed because the Integration Service is running in safe mode.

Explanation:

The Integration Service assigned to the workflow is running in safe mode. You cannot
schedule workflows when the Integration Service runs in safe mode.

User Response:

If you have the required privilege, you can manually start the workflow. You can also change
the operating mode for the Integration Service to normal.

LM_44184

Scheduled workflow <workflow name> was not rescheduled because the Integration Service
is running in safe mode.

Explanation:

The workflow runs on a schedule. However, the Integration Service does not run scheduled
workflows in safe mode.

User Response:

If you have the required privilege, you can manually start the workflow. You can also change
the operating mode for the Integration Service to normal.When you change the operating
mode to normal, all scheduled workflows will begin running.

LM_44185

User <user name> does not have sufficient privilege to log on while the Integration Service is
running in safe mode.

Explanation:

You do not have the required privilege to connect to an Integration Service running in safe
mode.

User Response:

Use a user account with the required privilege or wait until the Integration Service is no
longer in safe mode.

LM_44188

<Task name>: Failed to expand email user <name> for this email task.

Explanation:

The Integration Service cannot expand a parameter or variable in the email user name.

User Response:

Verify that the parameter or variable is defined properly in the parameter file and that its
value in the parameter file matches the parameter or variable datatype. For example, you
cannot set an integer workflow variable to a text string in the parameter file.

Explanation:

The Integration Service cannot expand the parameter or variable in the email user name due
to an internal error.

User Response:

Contact Informatica Global Customer Support.

LM_44189

<Workflow name>: Failed to expand email user <name> for this suspension email.

Explanation:

The Integration Service cannot expand a parameter or variable in the email user name.

User Response:

Verify that the parameter or variable is defined properly in the parameter file and that its
value in the parameter file matches the parameter or variable datatype. For example, you
cannot set an integer workflow variable to a text string in the parameter file.

Explanation:

The Integration Service cannot expand the parameter or variable in the email user name due
to an internal error.

User Response:

Contact Informatica Global Customer Support.

Chapter 12: L Message Codes

LM_44190

<Command task name>: Failed to expand command <command name>, with command value
<command text>.

Explanation:

The Integration Service cannot expand a parameter or variable in the command text.

User Response:

Verify that the parameter or variable is defined properly in the parameter file and that its
value in the parameter file matches the parameter or variable datatype. For example, you
cannot set an integer workflow variable to a text string in the parameter file.

Explanation:

The Integration Service cannot expand a parameter or variable in the command text due to
an internal error.

User Response:

Contact Informatica Global Customer Support.

LM_44193

Integration Service <name> will not perform workflow and schedule failover or recovery when
running in safe mode.

Explanation:

The workflow is assigned to an Integration Service running in safe mode. The Integration
Service will perform workflow and schedule failover and workflow recovery when you change
the Integration Service operating mode to normal.

User Response:

Change the Integration Service operating mode to normal.

LM_44205

Error using operating system profiles to run task <task name>: <error message>.

Explanation:

The Integration Service could not use the operating system profile assigned to the workflow.

User Response:

See additional error message for more information.

LM_44207

Cannot stop or abort workflow <ID = run ID> or a task within the workflow. The specified run
ID is not found on the Integration Service.

Explanation:

The Integration Service could not stop or abort the workflow because the stopworkflow or
abortworkflow pmcmd has an incorrect run ID parameter.

User Response:

Verify that you entered the correct run ID for the workflow. You can find the workflow run ID
number in the Workflow Monitor by opening the workflow log or the workflow properties panel.

LM_44208

Cannot stop or abort workflow <ID = run ID> or a task within the workflow. There is more than
one instance of this workflow running on the Integration Service. Specify the run ID to stop or
abort.

Explanation:

The Integration Service could not stop or abort the workflow because two or more instances
of the same workflow are running.

User Response:

When you enter the abortworkflow or stopworkflow pmcmd, enter the run ID option. The run
ID is unique for each workflow instance. You can find the workflow run ID number in the
Workflow Monitor by opening the workflow log or the workflow properties panel of the
workflow you want to stop.

LM_44210

Cannot wait for workflow <ID = run ID> or a task within the workflow. The run ID is not found
on the Integration Service.

Explanation:

You entered the pmcmd waitworkflow with an invalid run ID argument.

User Response:

Verify that you entered the correct run ID for the workflow. You can find the workflow run ID
number in the Workflow Monitor by opening the workflow log or the workflow properties panel.

LM Messages

203

LM_44211

Cannot wait for workflow or a task within the workflow. The Integration Service is running
more than one instance of the workflow. Specify the workflow run ID to wait for.

Explanation:

You entered the pmcmd waitworkflow with a workflow name, but the Integration Service is
running more than one instance of the workflow.

User Response:

Enter pmcmd waitworkflow with a run ID argument. The run ID is unique for each workflow
instance. You can find the workflow run ID number in the Workflow Monitor by opening the
workflow log or the workflow properties panel.

LM_44220

<Workflow or worklet name>: Failed to set the variable assignment value for variable <name>.

Explanation:

The Integration Service cannot assign a value to the variable in a post-session variable
assignment.

User Response:

Verify that the variable exists and that the name is spelled correctly in the assignment
statement. Verify that the datatypes of both variables in the assignment statement match.

LM_44222

Request to recover workflow <workflow name> run ID <run ID> does not match the current
workflow run ID.

Explanation:

You entered the pmcmd recoverworkflow with a workflow run ID argument that does not
match a run ID for a recoverable workflow.

User Response:

Verify that you entered the correct run ID for the workflow. You can find the workflow run ID
number in the Workflow Monitor by opening the workflow log or the workflow properties panel
of the workflow you want to stop.

LM_44223

The workflow <name> failed because an operating system profile was not specified and the
Integration Service uses operating system profiles.

Explanation:

The Integration Service uses operating system profiles.

User Response:

Specify an operating system profile for the workflow in the folder properties or when you
manually start a workflow.

LM_44224

The workflow <name> failed because the Integration Service is not enabled to use operating
system profiles and an operating system profile was specified.

Explanation:

An operating system profile was assigned to the workflow and the Integration Service does
not use operating system profiles.

User Response:

Remove the assignment of an operating system profile.

Configure the Integration Service to use operating system profiles.

204

LM_44225

The Integration Service failed to read parameter file <file name> using the operating system
profile.

Explanation:

The Integration Service could not open the parameter file specified for the session.

User Response:

Verify that the operating system user specified in the operating system profile has read
permissions on the parameter file.

LM_44226

The maximum number of allowed concurrent runs has been exceeded.

206

User Response:

Verify that the Integration Service is running. Also verify that the LMAPITarget application
connection is configured correctly.

LMTGT_17802

All relational targets must share the same relational database connection.

Explanation:

The relational targets in the mapping do not use the same relational database connection.

User Response:

Edit the session properties so that each relational target uses the same relational connection.

LMTGT_17803

Cannot create the relational database connection.

Explanation:

There is not enough memory on the node where the Integration Service process runs to
create the database connection objects the Integration Service uses to connect to the
relational database.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the node.

LMTGT_17804

Cannot connect to database.

Explanation:

The Integration Service could not connect to a relational database. The relational database
connection used for all relational targets in the mapping contains inaccurate information for
the connection parameters.

User Response:

Verify that the relational database connection is configured correctly.

LMTGT_17809

Identifier port is not connected in the mapping. The port must be connected when using the
Wait for Commit option.

Explanation:

The Identifier port in the LMAPI target is not connected. However, the Wait for Commit option
is selected in the session properties.

User Response:

Connect the Identifier port in the mapping when you select Wait for Commit in the session
properties.

LMTGT_17810

Could not find workflow details for key <key name>.

Explanation:

The LMAPI target received data for a key which does not exist on the Scheduling Information
tab of the LMAPI target properties.

Chapter 12: L Message Codes

User Response:

Enter a key in the Scheduling Information tab for each value that the LMAPI target will
receive in the UKey port.

LMTGT_17811

Indicator Table <table name> not found in the mapping.

Explanation:

The mapping containing the LMAPI target does not include the indicator table. However, an
indicator table name is specified on the Scheduling Information tab of the LMAPI target
properties.

User Response:

Verify that the table entered for the Indicator Table field exists in the mapping. The table must
contain the fields UKey, Identifier, and Status.

LMTGT_17812

Indicator Table name is not specified in the mapping. Indicator Table name is required when
using the Wait for Commit option.

Explanation:

The Indicator Table field on the Scheduling Information tab of the LMAPI target properties
does not contain a value. However, the Wait for Commit option is selected in the session
properties.

User Response:

Enter the name of the indicator table in the Indicator Table field when you select Wait for
Commit in the session properties.

LMTGT_17818

The Integration Service cannot fetch workflow <workflow name> for key <key name>.

Explanation:

The Integration Service cannot start the workflow because it does not exist or because it
does not have a unique name in the repository.

User Response:

Verify that all workflows scheduled in the LMAPI target exist in the repository and have
unique names in the repository.

LMTGT_17820

Warning: Lost server connection.

Explanation:

The LMAPI target lost its connection to the Integration Service.

User Response:

Verify that the Integration Service is running.

LMTGT_17821

Error communicating with Integration Service.

Explanation:

The LMAPI target failed to communicate with the Integration Service.

User Response:

Verify that the Integration Service is running.

Lotus Notes Messages

LNRDR_1017

Failed to load the NCSO.jar file.

Explanation:

The PowerCenter Integration Service could not find the .jar file in the PowerCenter
installation directory.

User Response:

Copy the NCSO.jar file from the <Domino Server Installation Directory>\data\domino\java
directory to the <PowerCenter Installation Directory>/server/bin/javalib directory.

LNWRT_1000

Failed to find the PowerExchange for Lotus Notes license.

Explanation:

A valid license key for PowerExchange for Lotus Notes was not found.

Lotus Notes Messages

207

User Response:

Use the Administrator tool to add a valid license key.

LNWRT_1010

Failed to connect to the Domino server <servername:portnumber>. Reason: <reason>.

Explanation:

A parameter in the connection object is incorrect.

User Response:

Ensure that parameters specified in the connection object are correct.

-or-

Explanation:

The DIIOP process is not configured to run on the specified Domino server or the port
number.

-or-

Explanation:

The PowerCenter Integration Service does not have the privileges to run the agent.

User Response:

Contact the Lotus Notes system administrator.

LNWRT_1025

Internal error. The PowerCenter Integration Service received an abort or a stop request from
the Data Transformation Manager (DTM) process. Terminating the session.

User Response:

Contact Informatica Global Customer Support.

LNWRT_1035

An error occurred while creating the error log file <file name>.

Explanation:

The path for the error log file is not valid.

User Response:

In the session properties, verify that the specified path is valid.

-or-

208

Explanation:

The user configured to start the Informatica Services does not have the write permission on
the directory where the log file is to be created.

User Response:

Ensure that the user configured to start the Informatica Services has the write permission on
the directory.

LNWRT_1041

Error threshold value <threshold> reached.

Explanation:

The session failed because the PowerCenter Integration Service reached the error threshold
specified in the session properties.

Chapter 12: L Message Codes

User Response:

Eliminate the errors in the data.

-orIn the session properties, increase the error threshold.

Lotus Notes Messages

209

CHAPTER 13

M Message Codes
This chapter includes the following topics:
MBC_EXCL Messages, 210
MMS Messages, 212
MPSVCCMN Messages, 212
MQ Messages, 212
MSRdr Messages, 221

MBC_EXCL_E0015 Failed to process Excel XML spreadsheet. The XML file may be corrupted.
Explanation:

The Import or Export Metadata wizard is configured to import from or export to a file with
an .xml extension.

User Response:

Verify that the import or export file has an .xlsx extension.

MBC_EXCL_E0019 The MetaMap must be in XLSM format. To create one with pre-2007 Excel, install the 2007
Office Compatibility Pack.
Explanation:

Microsoft Office Excel 2003 is installed on the machine hosting the PowerCenter Client.
However, the 2007 Office Compatibility Pack is not installed.

User Response:

MBC_EXCL_E0070 Cannot unpack OpenXML- it might be corrupted or in use by another program: <file name>
Explanation:

Java 1.5 or later is not installed on the machine hosting the PowerCenter Client.

User Response:

Verify that Java 1.5 or later is installed. If Java 1.5 or later is installed, contact Informatica
Global Customer Support.

MBC_EXCL_E0122 Cannot open file <file name>. File may be locked by another process or is protected or you
must install the Office Compatibility Pack to open XLSB files.
Explanation:

The Import or Export Metadata wizard is configured to import from or export to a file with
an .xls extension.

User Response:

Verify that the import or export file has an .xlsx extension.

Explanation:

Microsoft Office Excel 2003 is installed on the machine hosting the PowerCenter Client.
However, the 2007 Office Compatibility Pack is not installed.

Chapter 13: M Message Codes

MQ_29003

Error disconnecting from queue manager <queue manager> reason <reason> <reason
message>.

Explanation:

The Integration Service could not disconnect from the queue manager due to the reason
code stated in the message.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29004

Filter parse error: <parse error message>.

Explanation:

The filter condition in the MQ Source Qualifier is invalid.

User Response:

Correct the error stated in the parse error message.

MQ_29005

Error getting message from queue <queue>:<queue manager> reason <reason> <reason
message>.

Explanation:

The Integration Service failed to get a message from the queue due to the reason code
stated in the message.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29006

Message data truncated reading from queue <queue>:<queue manager> reason <reason>
<reason message>.

Explanation:

The message size is too large for the Integration Service to read.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29007

No message under cursor while attempting to remove message from queue <queue>:<queue
manager> reason <reason> <reason message>.

Explanation:

You might not have the permission to remove the message from the queue.
The message was removed by another process.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29008

Error putting message on queue <queue>:<queue manager> reason <reason> <reason

message>.

Explanation:

The Integration Service could not put message on the queue due to reason code stated in
message.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29009

Invalid RowsPerMesage value for queue <queue>:<queue manager> (<rows per message> >
0).

Explanation:

The Rows Per Message parameter in the session properties is incorrect.

User Response:

Specify a value greater than 0 for the Rows Per Message in the session properties.

MQ Messages

213

MQ_29010

Error opening cache <cache file> for reading: <operating system error>.

Explanation:

You might not have permission to read from the cache file.
The $PMCacheDir variable is incorrect.

User Response:

Fix the operating system error stated in the message.

MQ_29011

Error opening cache <cache file> for writing: <operating system error>.

Explanation:

You might not have permission to write to the cache file.

The hard disk is full.
The $PMCacheDir variable is incorrect.

User Response:

Fix the operating system error stated in the message. Look in the directory $PMCacheDir.

MQ_29012

Error attempting to load MQ driver.

Explanation:

PowerCenter could not load the MQ driver shared library because the file does not exist.

User Response:

Verify the search path for the MQ driver shared library. Depending on the platform, look for
the driver file in the appropriate location:
Windows - pmmqdrvc.dll
Solaris - libpmmqdrvc.so
Linux - libpmmqdrvc.so
AIX - libpmmqdrvc.a
HP - libpmmqdrvc.sl

214

Explanation:

PowerCenter could not load the MQ driver shared library due to insufficient permissions.

User Response:

Make sure the permissions for the MQ driver file are correct.

MQ_29013

Delete operation for this target not enabled. Queue connection is <queue>:<queue manager>.

Explanation:

The WebSphere MQ target received a row with the delete flag set to TRUE. However, the
Integration Service does not have delete permission for the queue.

User Response:

Enable delete permission for the Integration Service on the target queue.

MQ_29014

MsgId field has not been set. Queue connection is <queue>:<queue manager>.

Explanation:

There may be no port projected to the MsgId column in the dynamic WebSphere MQ target.
The Integration Service cannot delete messages from the queue.

User Response:

Project a port to the MsgId column of the dynamic WebSphere MQ target.

MQ_29100

Line <line>, column <column>: Unknown character '<character>' in filter.

Explanation:

A filter condition has a general parsing error.

User Response:

Check the syntax of the expression.

MQ_29101

Line <line>, column <column>: Invalid operator.

Explanation:

A filter condition has a general parsing error.

User Response:

The logical operators [=, <>, >=, <=, >, <] in the left-hand and right-hand sub-expression
have incompatible datatypes.

User Response:

Edit the filter condition with compatible datatypes for relational operators in the left-hand and
right-hand sub-expression.

User Response:

Use the <correct date format> for the argument in the filter condition.

User Response:

None. You can enter a filter condition in the MQ Source Qualifier or in the session properties.

MQ_29214

MQ Driver initialization failure <error message>.

Explanation:

An error occurred during the initialization of the MQ driver.

User Response:

Check the additional error message for more information.

MQ_29218

Filter Condition for MQSeries: StartTime should be prior to EndTime.

Explanation:

This is an informational message. The value for StartTime in the filter condition is equal to or
greater than the value entered for EndTime.

User Response:

Make sure the StartTime value is less than the EndTime value.

MQ Messages

217

MQ_29221

Partial message written into queue <queue>:<queue manager> due to commit.

Explanation:

This is an informational message. The Integration Service did not commit all rows in a
message to the target. This might occur when the Integration Service reaches the end of a
commit interval or a short FlushLatency interval. It commits the remaining rows at the next
commit interval.

User Response:

None.

MQ_29222

Error committing from queue manager <queue manager>: reason <reason> <reason
message>.

Explanation:

The Integration Service could not commit messages to the target. The WebSphere MQ
system may not contain enough log space.

User Response:

Verify that the WebSphere MQ system contains enough log space.

Check the additional error message for more information.

218

MQ_29223

Error backing out from queue manager <queue manager>: reason <reason> <reason
message>.

Explanation:

Recovery cache folder is not available.

User Response:

Check that the recovery cache folder exists and has write permission.

Explanation:

The target may have insufficient disk space.

User Response:

Verify that enough disk space is available in the target.

Chapter 13: M Message Codes

MQ_29237

Failure occurred while reading messages from the queue in destructive mode.

Explanation:

The WebSphere MQ installation may not allow deleting messages from the queue.

User Response:

Look up the reason code in the WebSphere MQ documentation for instructions to correct the
error.

MQ_29238

Invalid recovery cache folder specified.

Explanation:

The recovery cache folder is invalid.

User Response:

From the properties settings on the Mapping tab (Sources node) in the session properties,
specify a valid recovery cache folder.

MQ_29239

Reader partition <partition name> failed to close checkpoint at real-time flush: <additional
error message>.

Explanation:

There may be insufficient disk space when the Integration Service commits messages to the
target after the Real-time Flush Latency period expires.

User Response:

Verify that enough disk space is available in the target.

220

MQ_29245

You cannot specify both Destructive Read and RemoveMsg(TRUE).

Explanation:

You selected the Destructive Read option and specified the RemoveMsg(TRUE) function as
a filter condition.

User Response:

You must set the RemoveMsg(TRUE) function to RemoveMsg(FALSE) in the filter condition
or remove the function from the filter condition.

MQ_29246

The mapping contains an associated source qualifer.

Explanation:

You specify the Destructive Read option in a mapping with an associated source qualifier.

User Response:

The Integration Service ignores the Destructive Read option if the mapping contains an
associated source qualifier. To remove messages from the source queue for mappings that
contain an associated source qualifier, use the RemoveMsg(TRUE) function.

MQ_29248

MQ queue manager <queue manager> encountered a transient connection failure.

Explanation:

The Integration Service could not connect to the MQ queue manager. The network or the MQ
server may be down. The Integration Service will attempt to connect to the MQ queue during
the retry connection period. If it does not connect to the MQ queue during the retry
connection period the session fails.

User Response:

Verify the MQ queue manager is running. Or, verify that the network is active.

MQ_29250

Connection retry period expired. The Integration Service could not connect to MQ queue
manager <queue manager>.

Explanation:

The Integration Service could not connect to the MQ queue manager during the retry
connection period. The network or the MQ server may be down. As a result, the session
failed.

User Response:

Verify the MQ queue manager is running. Or, verify that the network is active. Restart the
session.

MQ_29251

Resilience is disabled, because Destructive Read and recovery are not configured.

Explanation:

The Integration Service could not make multiple connection attempts to the MQ queue
manager, because Destructive Read and recovery are not configured for the session.

User Response:

In the session properties, configure Destructive Read and recovery.

MQ_29255

The Integration Service truncated message data while reading from queue <queue>:<queue
manager> in destructive read mode.

Explanation:

The Integration Service read a WebSphere MQ message that exceeded the precision of the
MESSAGE_DATA column in the MQSeries source definition. As a result, the Integration
Service truncated the data. Because the session is running in destructive read mode, the
session failed and the Integration Service did not delete the message from the source queue.

User Response:

Increase the precision of the MESSAGE_DATA column in the MQSeries source definition.

MQ_29265

The repository data for source <source name> is corrupt.

Explanation:

The connection object for the specified source instance contains inconsistencies.

User Response:

Delete the connection object for the source instance. Create a connection object and assign
it to the source instance.

Chapter 13: M Message Codes

MQ_29270

The Integration Service could not create a locale for code page ID: <code page>.

Explanation:

The Integration Service failed to create an I18N converter object.

User Response:

Contact Informatica Global Customer Support.

The session failed because the incorrect user name and password is specified.

User Response:

Verify that the correct user name and password is specified.

MSRdr Messages

221

MSRdr_1020

Failed to connect to server <servername>. Reason: Unknown Server Hostname.

Explanation:

The session failed because the mail server name or IP address is not correct.

User Response:

Verify that the mail server name or IP address is valid. Also, verify that the mail server is
running.

MSRdr_1021

Failed to connect to server <servername>. Reason: Valid trusted certificate not found in the
cacerts keystore. <reason>.

Explanation:

The session failed because you are connecting to the mail server over a secure protocol such
as IMAPS or POP3S. A valid trusted certificate for the mail server is not found in the cacerts
keystore on the machine hosting the PowerCenter Integration Service.

User Response:

Verify that a valid trusted certificate for this mail server is present in the cacerts keystore. The
cacerts keystore is located in the following directory:
{monospace-font}
<PowerCenter Installation Directory>\java\jre\lib\security
</monospace-font}
For example, use the following syntax to add the certificate certificate.cer to the cacerts
keystore:
<PowerCenter Installation Directory>\java\bin\keytool -import -alias <certificate alias> -file
certificate.cer -keystore <PowerCenter Installation Directory>\java\jre\lib\security\cacerts v
Note: For more information about the trust certificates, contact your system administrator.
Specify the trusted certificate file name in the application connection attributes.

MSRdr_1050

The PowerCenter Integration Service cannot connect to the Microsoft Exchange Server
<servername>. Reason: <reason>.

Explanation:

PowerExchange for Email Server uses the Exchange Messaging Application Programming
Interface (MAPI) protocol to connect to the Microsoft Exchange Server and at least one of the
following statements is true:
The mailbox user does not have the Log On as a Service permission.
The PowerCenter Integration Service is running under the account of a user who does not

have the Act as a Part of the Operating System permission on the machine.

222

User Response:

Verify that the mailbox user has the Log On as a Service permission on the PowerCenter
Integration Service machine and the PowerCenter Integration Service machine is running
under the account of a user who has the Act as a Part of the Operating System permission.

MSRdr_1080

Failed to connect to Outlook PST file <PST filename>. Reason: Error configuring message
service. Invalid password for PST File.

Explanation:

The session failed because the Outlook PST file is password protected and you may not have
specified a correct password.

User Response:

Verify that you have specified a correct password for the Outlook PST file.

Chapter 13: M Message Codes

CHAPTER 14

N Message Codes
This chapter includes the following topics:
NODE Messages, 223
NTSERV Messages, 223
NZRDR Messages, 230
NZWRT Messages, 231

NODE Messages
NODE_10014

<Resource type> resource <resource name> not found in node configuration.

Explanation:

The EnableNodeResource or DisableNodeResource command was used to enable or disable

a resource on a node. infacmd could not find a resource with the name and type shown on
the node.

User Response:

Verify the following conditions:

The resource shown exists on the node.
The resource is of the type shown.
The resource name was entered correctly.

NTSERV Messages
NTSERV_10000

Cannot close service main thread handle.

User Response:

Contact the system administrator to gain privileges access to the registry. If the problem
persists, contact Informatica Global Customer Support.

NTSERV_10025

Cannot close registry key.

Explanation:

The Integration Service failed to read a value from the registry. You may not have the
privileges to access that portion of the registry.

User Response:

Contact the system administrator to gain privileges access to the registry. If the problem
persists, contact Informatica Global Customer Support.

NTSERV_10026

Cannot initialize security descriptor.

Explanation:

Explanation:

Operating system error. You might be low on resources.

NTSERV Messages

Explanation:

Operating system error. The machine hosting the Integration Service might be low on
resources.

User Response:

Contact the system administrator, or free system resources.

Contact Informatica Global Customer Support.

NTSERV_10091

Install failed.

Explanation:

The Informatica installation failed.

NTSERV Messages

227

228

User Response:

Check the .mif file in the Windows directory for related error messages.

NTSERV_10092

Update failed.

Explanation:

The Informatica installation failed.

User Response:

Check the .mif file in the Windows directory for related error messages.

NTSERV_10093

Deinstall failed.

Explanation:

Operating system error.

User Response:

Contact the system administrator.

Verify that you spelled the COM object correctly and verify that it is not corrupt or invalid.

User Response:

Verify the directory and file name for the attachment file are entered correctly in the session
properties. Verify the file exists in the specified directory.

NTSERV_10147

Permissions do not allow read access of attachment <file name>.

Explanation:

You configured a session to send a post-session email with an attached file. The Integration
Service on Windows could not access the specified file.

User Response:

Check the ODBC message in the session log.

Contact Informatica Global Customer Support.

230

NZRDR_10109

Reading data failed.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

NZRDR_10013

Integration Service could not connect to Netezza Performance Server.

Explanation:

The connection information is incorrect.

User Response:

Enter a user name, password, and verify that the DSN entry is valid.

NZRDR_10027

Create locale failed.

Explanation:

Invalid code page set for connection object.

User Response:

Set the code page in the connection object compatible with Netezza Performance Server.

Chapter 14: N Message Codes

NZRDR_10028

Failed to create pipe.

Explanation:

The Integration Service cannot allocate sufficient memory to create pipe.

User Response:

Check the system resources for available space in the Central Processing Unit (CPU).

Explanation:

The user does not have the necessary privileges to create the pipe.

User Response:

Get the read and write access privileges for the files and folders where the connector is
installed.

NZRDR_10030

Thread creation failed.

Explanation:

The Integration Service cannot allocate sufficient memory to create thread.

User Response:

Check the system resources for available space in the CPU.

NZRDR_10034

Opening pipe failed.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

NZRDR_10036

Failed to create child process.

Explanation:

The total number of processes under execution has exceeded the system limit.

User Response:

Close any running application that is not required on the node and try again.

User Response:

Contact Informatica Global Customer Support.

NZWRT_20042

Relation <table name> does not exist in the Netezza Performance Server or no column found
in the table.

Explanation:

The target does not exist or there are no columns in the target.

User Response:

Create a valid Netezza target table in Netezza Performance Server.

NZWRT Messages

User Response:

In the session properties, specify an escape character value.

Chapter 14: N Message Codes

CHAPTER 15

O Message Codes
This chapter includes the following topics:
OBJM Messages, 233
ODL Messages, 234
OHS Messages, 238
OPT Messages, 239

OBJM Messages
OBJM_54505

The object for which rbrowser information was requested does not exist.

Explanation:

The Repository Agent process could not retrieve object properties from the repository
because the object does not exist.

User Response:

The object may be deleted. Refresh the Navigator windows. Check for other error messages
in the Repository Service log.

OBJM_54509

Rbrowser fetch: Unable to get children info. Maybe the childType is invalid. (childType =
<type>).

Unable to connect to the repository <repository name> on database <database name>.

Explanation:

The Repository Agent process could not connect to the repository.

User Response:

Verify that the repository database is running. Check preceding error messages to see the
cause of the error.

OBJM_54543

Database error: <database error message>.

Explanation:

Database error.

User Response:

Check the session log for related messages. Also, contact the database administrator.

OBJM_54544

Internal Repository Service error: error number <error number>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

OBJM_54545

Received fetch request with invalid rbrowser node ID <ID>.

Explanation:

Internal error.

Explanation:

You omitted the JOIN keyword from the syntax for an outer join.

User Response:

Correct the join syntax in the Source Qualifier.

The Integration Service encountered one of the following Teradata errors that aborted the
current transaction:
2801 Duplicate unique prime key error.
2802 Duplicate row error.
2803 Secondary index uniqueness violation.
3604 Cannot place a null value in a NOT NULL field.

236

User Response:

Remove the row that caused the Teradata error and restart the session.

ODL_26069

Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>.

Explanation:

The Repository Service or Integration Service failed to connect to the Microsoft SQL Server
database because one or more Microsoft SQL Server API function calls failed.

User Response:

Verify that all specified Microsoft SQL Server classes are properly registered in the registry.
Then re-register oledb32.dll. [Regsvr32 \Program Files\Common Files\System\Ole DB
\oledb32.dll]. Use the returned error code and error message to determine the cause of this
error.

ODL_26071

Graphic/vargraphic partition key types are supported only on servers with UNICODE data
movement enabled.

Explanation:

You ran a session using database partitioning on an Integration Service running in ASCII
mode and the IBM DB2 target table uses a partitioning key with either a Graphic or
Vargraphic column.

Chapter 15: O Message Codes

User Response:

Run the session on an Integration Service in Unicode mode.

ODL_26095

BigInt partition key type can be used only in high-precision mode.

Explanation:

A session that loads data to an IBM DB2 target is configured for database partitioning and
the target table partition key is a Bigint column, but high precision is not enabled for the
session.

User Response:

Enable high precision for the session, or select a target table partition key that is not a Bigint
column.

ODL_26111

High availability license is absent. Resilience timeout specified for database connection
<connection name> is ignored.

Explanation:

The connection retry period is configured in the database connection object, but you do not
have the high availability option. The retry period is ignored.

User Response:

None.

ODL_26113

Number of Bulk mode parameters=<number of parameters> exceeded the number of

parameters supported <number of parameters>.

Explanation:

The number of parameters specified for the DB2BulkModeParameters custom property is

greater than four.

User Response:

Verify that the number of parameters specified in the DB2BulkModeParameters custom

Explanation:

At least one connection parameter in the application connection is missing.

User Response:

Enter values for the connection parameters in the SAP BW OHS Reader application
connection.

OHS_99002

Connection to SAP system failed. Reason: <error name>.<error message>.

Explanation:

At least one parameter value in the SAP BW OHS Reader application connection is invalid.

User Response:

Enter correct values for the connection parameters in the SAP BW OHS Reader application
connection.

OHS_99003

The Integration Service did not set a status for request ID <request ID>.

Explanation:

The metadata of the BW OHS source definition and the InfoSpoke do not match. You might
have modified the InfoSpoke in SAP NetWeaver BI after you imported the source definition.

User Response:

Reimport the BW OHS source definition.

Chapter 15: O Message Codes

OPT Messages
OPT_63005

ERROR: Pushdown optimization failed for the session <transformation name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

OPT_63006

ERROR: Pushdown optimization could not match PowerCenter datatype <datatype> to a

datatype on database <database>.

Explanation:

The Integration Service could not map the datatype correctly.

An internal error occurred while parsing a timestamp.

User Response:

Contact Informatica Global Customer Support.

OPT_63014

Pushdown optimization to source stops at the transformation <transformation name>

because the mapping contains too many pipeline branches.

Explanation:

The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 fourway branches. The Integration Service cannot generate SQL to push all the branches of the
mapping to the database.

User Response:

None.

OPT_63015

Pushdown optimization to target stops at the transformation <transformation name> because

the mapping contains too many pipeline branches.

Explanation:

The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 fourway branches. The Integration Service cannot generate SQL to push all the branches of the
mapping to the database.

User Response:

None.

OPT Messages

239

240

OPT_63021

Pushdown optimization stops at the transformation <transformation name> because it is

connected to multiple targets.

Explanation:

You attempted to push a transformation to multiple targets for target-side partial pushdown
optimization. The Integration Service cannot generate the SQL to push the transformation to
both targets.

User Response:

None.

OPT_63022

Pushdown optimization stops at the transformation <transformation name> because no port

depends on values from the upstream transformation <transformation name>.

Explanation:

You created an expression that does not use upstream output port values. The Integration
Service cannot generate an SQL statement for an expression that does not use output ports
from upstream transformations because it cannot determine the values to use.

User Response:

None.

OPT_63070

Pushdown optimization to the source stops at the transformation <transformation name>

because it is a partition point and the partition type is not hash auto-keys or pass-through.

Explanation:

To push transformation logic for a partitioned transformation to the database, the partition
type must be hash auto-keys or pass-through. If the partition type is hash auto-keys, the
source must be key-range partitioned, and the key ranges cannot gap or overlap.

User Response:

Change the partition type for the transformation to hash auto-keys or pass-through.

OPT_63072

Pushdown optimization to the source stops at the partition point <transformation name>
because the source is not key-range partitioned.

Explanation:

The transformation uses a hash auto-keys partition, and the source is not key-range
partitioned. When the partition is hash auto-keys, you must also configure the source for keyrange partitioning.

User Response:

Configure the source for key-range partitioning.

OPT_63076

Pushdown optimization to the source stops at the partition point <transformation name>
because the source has a partition with an end key- range different from the start key range of
the next partition.

Explanation:

You configured the source for key range partitioning, but you did not ensure that the end key
range for a partition matches the start range for the next partition. The end key range for
each partition must equal the start range for the next partition, and it cannot overlap with the
next partition.

User Response:

Modify the start or end key-range to ensure that the end key range for the partition equals the
start range for the next partition.

OPT_63077

OPT_63083

Pushdown optimization to the source stops at the partition point <transformation name>
because a downstream Joiner transformation is not properly partitioned on the join key.

Explanation:

You configured a join condition for the upstream Joiner transformation that is different from
the partition key specified for the key-range partition. The join condition and partition key
must match.

User Response:

Configure the join condition and the key-range partition to match.

OPT_63102

Pushdown optimization stops at Source Qualifier transformation <transformation name>

because it contains an SQL override, and view creation is not enabled.

Explanation:

You configured a session that contains an SQL override for pushdown optimization, but you
did not configure the session to create a view.

OPT Messages

241

242

User Response:

When you configure the session containing an SQL override for pushdown optimization,
ensure that you configure the session to create a view. You configure this setting on the
Properties tab of the session properties.

Chapter 15: O Message Codes

OPT_63147

Pushdown optimization stops at the Lookup transformation <transformation name> because

it is downstream from an Aggregator transformation.

the expression <expression name> uses a boolean expression for parameter <parameter
name>.

Explanation:

The numeric expression contains a boolean subexpression. Numeric and boolean values are
not compatible in SQL. To convert a boolean expression to a numeric expression, the
database requires a case statement, which cannot be performed with target-side pushdown
optimization.

OPT Messages

243

244

User Response:

None.

OPT_63205

Error encountered while attempting to partition session at runtime.

Explanation:

The Integration Service could not dynamically partition the session.

User Response:

Review previous messages in the session log to determine the cause.

OPT_63206

Invalid Partition Count <count>.

Explanation:

You set dynamic partitioning based on the number of partitions but the attribute does not
contain a valid value.

User Response:

Set the Number of Partitions to the $DynamicPartitionCount session parameter or enter a

number greater than 1.

OPT_63207

Partition Count is 1. Dynamic Partitioning has been disabled.

Explanation:

The Number of Partitions session attribute is 1. The session runs in one partition.

User Response:

Set the number of partitions to a number greater than 1, or change the method of partitioning.

OPT_63218

Key range not closed.

Explanation:

You cannot enable dynamic partitioning for a transformation that uses an open range of
partition key numbers.

Chapter 15: O Message Codes

User Response:

Disable dynamic partitioning or change the key range to a closed range of numbers.

OPT_63219

246

OPT_63226

Transformation <transformation name> will not be partitioned because partitionable attribute

<attribute name> has a user specified value.

Explanation:

The Integration Service does not partition a transformation when you enter a value for a
partition-level attribute.

User Response:

To use dynamic partitioning with a Custom transformation, clear the referenced attribute. For
other transformations, set the cache directory to the default, $PMCacheDir.

OPT_63227

Transformation <transformation name> is not partitionable.

Explanation:

You enabled dynamic partitioning for a session that contains a transformation that is not
partitionable. The session runs in one partition by default.

User Response:

Disable dynamic partitioning or change the transformation that is not partitionable.

OPT_63229

Unable to determine count of partitions for Dynamic Partitioning because an error was
encountered while expanding parameter <parameter name>.

Explanation:

The Integration Service could not determine the number of partitions to create.

User Response:

Verify that the $DynamicPartitionCount session parameter contains a number greater than 1.

OPT_63234

Dynamic partitioning failed to detect the number of CPUs because of the following system
error: <error>.

Explanation:

A fatal error occurred. If the Integration Service runs on a grid, the fatal error occurred on the
node which ran the preparer DTM process.

User Response:

Review the session log for related messages, or contact Informatica Global Customer
Support.

OPT_63282

Source-side pushdown optimization stops at partition point <partition name>.

Explanation:

The Integration Service is unable to determine why pushdown optimization stops at this
partition point.

User Response:

Contact Informatica Global Customer Support.

Chapter 15: O Message Codes

CHAPTER 16

P Message Codes
This chapter includes the following topics:
PCCL Messages, 247
PCSF Messages, 250
PETL Messages, 264
PMF Messages, 267
PMJVM Messages, 269
PR Messages, 269
PWX Messages, 274
PWXPC Messages, 276

PCCL Messages
PCCL_97001

Cannot get connection property <property name>.

PCCL_97009

The Integration Service failed to initialize connection properties for the Source Qualifier
instance <Source Qualifier name>.

Failed to deserialize cache message: <error message>.

Explanation:

The Integration Service could not read the message from the recovery cache.

User Response:

Check the additional error message for more information.

PCCL_97024

The Integration Service partition <partition> truncated last cached message from cache.

Explanation:

This is an informational message. The Integration Service truncated the last message in the
cache.

User Response:

None.

PCCL_97025

The Integration Service partition <partition> failed to truncate message cache to last
serialized message: <error message>.

Explanation:

The Integration Service could not truncate the last message in the cache.

User Response:

Check the additional error message for more information.

PCCL_97026

The Integration Service partition <partition> failed to flush the cache: <error message>.

Explanation:

The Integration Service could not flush the cache.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PCCL_97033

The Integration Service failed to initialize the metadata extension for the Source Qualifier
instance <Source Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PCCL_97034

Error threshold for the session is reached. The number of errors encountered has exceeded
the threshold value <error threshold number>.

Explanation:

The Integration Service has reached the error threshold configured in the session properties.

User Response:

Eliminate the errors in the data.

Increase the error threshold.

PCSF Messages

250

PCSF_10004

Authentication for <user name> failed because <error message>.

Explanation:

The authentication failed for the specified user.

User Response:

Resolve the issue using the details provided in the error message.

PCSF_10005

An attempt to <activity> access <object name> failed for <user name> because: <error text>.

Explanation:

A user attempted to run a command that accesses the object specified. The command could
not be executed because the command line program cannot access the object.

User Response:

Verify that the user specified in the command has permission on the object.

PCSF_10006

No Integration Service Ref were provided.

Explanation:

Validation failed for an SAP BW Service because no Integration Service references were
found.

User Response:

Configure the Integration Service for the SAP BW Service.

PCSF_10007

Cannot connect to repository <repository name> because: <error text>.

Explanation:

The Repository Service encountered an error connecting to the repository.

User Response:

Correct the error indicated in the message.

Chapter 16: P Message Codes

PCSF_10013

The file domains.infa was not defined in the system properties.

Explanation:

The system was unable to locate the domains.infa file required to communicate with the
domain.

User Response:

Internal error. Attempt to start Informatica Services again. If the problem persists, contact
Informatica Global Customer Support.

PCSF_10027

No gateway connectivity is found for domain <name>.

Explanation:

The command line program was unable to find the domain specified in the command.

User Response:

Verify that the domain exists and that the domain name was entered correctly.

PCSF_10028

Cannot respond to operation <operation name> of service <service name>: <error text>.

Explanation:

The Service Manager attempted an operation. However, the operation failed because of an
error.

User Response:

Correct the error indicated in the message and retry the operation.

PCSF Messages

251

PCSF_10131

The license key was previously applied.

Explanation:

You tried to add an incremental key that has already been added.

User Response:

To enable additional options, use a different incremental key.

PCSF_10132

You cannot apply more than one original key to a license. To update an existing license,
select a license file with an incremental key.

Explanation:

Each license requires one original key. You cannot apply more than one original key to the
same license. You must use an incremental key to update an existing license. You use an
original key to create a license.

User Response:

Apply the incremental key to the existing license to update the license.
Create a license using the original key.

252

PCSF_10133

The issue date for the original key must be earlier than the issue dates for the incremental
keys.

Explanation:

Each incremental key must be issued after the original key.

User Response:

Contact Informatica Global Customer Support to get a valid incremental key.

PCSF_10135

Cannot decrypt the license key.

Explanation:

The license key file is unreadable.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10136

License is invalid. The Licensing Service encountered an invalid attribute value in the license.

Explanation:

The key provided was not validated as having proper encryption.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

Chapter 16: P Message Codes

PCSF_10137

License is invalid. The Licensing Service encountered an invalid value <begin date value> for
the Begin Date attribute.

Explanation:

The license is invalid. The Begin Date attribute encountered in the license file is invalid.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10138

License is invalid. The Licensing Service encountered an invalid value <expiry date value> for
the Expiry Date attribute.

Explanation:

The Expiry Date attribute in the license file is invalid.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10139

License is invalid. The Licensing Service encountered an invalid value <issue date value> for
the Issue Date attribute.

Explanation:

The Issue Date attribute in the license file is invalid.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10140

License is invalid. The Licensing Service encountered an invalid value <number of CPUs> for
the CPUs attribute.

Explanation:

The CPUs attribute in the license file is invalid.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10141

License is invalid. The Licensing Service encountered an invalid value <number of

repositories> for the repositories attribute.

Explanation:

The Service Manager failed to validate the license because the number of repositories is
invalid.

User Response:

Contact Informatica Global Customer Support to get a new license key file.

PCSF_10304

Cannot connect to URL <URL> to perform operation <operation name> of service <service
name>.

Explanation:

A client or service attempted to connect to the URL to perform an operation. However, the
operation failed because the client or service could not connect to the URL within the
resilience timeout.

User Response:

Verify that the host name and port number for the URL and retry the operation.

PCSF_10305

Cannot connect to gateway <node address> to look up service <service name>.

Explanation:

The PowerCenter component could not connect to the Service Manager on the gateway node
to look up a service within the resilience timeout for the domain.

User Response:

Verify that the gateway node is running.

PCSF_10306

Operation <operation name> of service <service name> was interrupted.

Explanation:

The service could not complete the operation. This error can occur because the Service
Manager is in the process of shutting down.

User Response:

Restart the node.

PCSF Messages

253

254

PCSF_10322

The following error occurred while logging to Log Service: <error text>.

Explanation:

The Log Manager cannot process log events because of the operating system error shown.
For example, the shared file system may be unavailable.

User Response:

Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs
directory.

PCSF_10325

Error threshold exceeded for number of failed log attempts. Disabling guaranteed messaging.

Explanation:

Too many errors occurred while the Log Manager was processing log events.

User Response:

Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs
directory.

PCSF_10326

The following error occurred while generating the guaranteed message file: <error text>.

Explanation:

An application service process could not create the Guaranteed Message Delivery file
because of the operating system error shown. For example, the shared file system may be
unavailable.

User Response:

Try to fix the operating system error.

PCSF_10327

The following error occurred while writing to the guaranteed message file <file name>: <error
text>.

Explanation:

An application service process could not write log events to the Guaranteed Message
Delivery file because of the operating system error shown. For example, the shared file
system may be unavailable.

User Response:

Try to fix the operating system error.

PCSF_10336

Incremental key is of a different deployment type than the original key. To update a license,
use an incremental key that has same deployment type as the original key that was used to
create the license.

Explanation:

The incremental key has a different deployment type than the original key that was used to
create the license.

User Response:

Contact Informatica Global Customer Support to get a new incremental license key with the
correct deployment type.

PCSF_10337

Incremental key is for a different distributor than the original key. To update a license, use an
incremental key that has same distributor as the original key that was used to create the
license.

Explanation:

The incremental key is for a different distributor than the original key that was used to create
the license. The distributor is the organization that issued the PowerCenter product.

User Response:

Contact Informatica Global Customer Support to get a new incremental license key with the
correct distributor.

PCSF_10338

Incremental key is for a different PowerCenter edition than the original key. To update a
license, use an incremental key that has the same PowerCenter edition as the original key
that was used to create the license.

Explanation:

The incremental key is for a different PowerCenter edition than the original key that was used
to create the license.

Chapter 16: P Message Codes

User Response:

Contact Informatica Global Customer Support to get a new incremental license key with the
correct PowerCenter edition.

PCSF_10339

Incremental key has a different serial number than the original key. To update a license, use
an incremental key that has same serial number as the original key that was used to create
the license.

Explanation:

The incremental key uses a different serial number than the original key that was used to
create the license.

User Response:

Contact Informatica Global Customer Support to get a new incremental license key with the
correct serial number.

PCSF_10340

Incremental key is for a different PowerCenter version than the original key. To update a
license, use an incremental key that is for the same PowerCenter version as the original key
that was used to create the license.

Explanation:

The incremental key is for a different PowerCenter version than the original key that was
used to create the license.

configuration file and could not validate the file.

User Response:

Correct the error indicated in the message and validate the file again.

PCSF_10354

Unable to identify the service type for configuration file <file name>. The file might be an
invalid configuration file.

Explanation:

The Upgrade Wizard could not determine if the configuration file is a Repository Agent or
PowerCenter Server configuration file. A Repository Agent configuration file must contain the
<RepositoryName> property. A PowerCenter Server configuration file must contain the
<ServerName> property.

User Response:

Correct the contents of the configuration file and validate the file again. If you created the
PowerCenter Server configuration file with the pmserverexportreg utility, the registry for the
machine running the PowerCenter Server may contain inconsistent data.

PCSF_10355

Configuration file <file name> is missing the required option(s) <option names>.

Explanation:

The Upgrade Wizard could not validate the Repository Agent or PowerCenter Server
configuration file because the file is missing one or more of the required properties.

User Response:

Add the required property or properties to the configuration file and validate the file again.

PCSF Messages

255

256

PCSF_10356

File <file name> has extension other than .cfg. Upgrade only works with .cfg file.

Explanation:

You placed a file in the global_repo, local_repo, or PCServer directory in the server/upgrade/
cfgfiles directory on a node. However, you can only upgrade Repository Agent or
PowerCenter configuration files with the .cfg extension. The Upgrade Wizard cannot validate
or upgrade the file.

User Response:

If the file is a Repository Agent or PowerCenter Server configuration file, rename the file with
the correct extension. If the file is not a configuration file, remove the file from the upgrade
directory or ignore the error.

PCSF_10357

File <file name> contains service <service name> which already exists in domain <domain
name>.

Explanation:

The <RepositoryName> or <ServerName> property in the Repository Agent or PowerCenter

Server configuration file matches a Repository Service or Integration Service name in the
domain. As a result, the Upgrade Wizard cannot upgrade the configuration file.

User Response:

If you already upgraded the Repository Agent or PowerCenter Server configuration file,
ignore the error and do not upgrade the configuration file. If you want to upgrade the
configuration file again, remove the service from the domain and upgrade the file again.

PCSF_10358

Upgrade configuration files directory is not found on node <node name>.

Explanation:

You selected a node that contains Repository Agent and PowerCenter Server configuration
files to upgrade in the Upgrade Wizard. However, the server/upgrade/cfgfiles directory does
not exist on the node. The directory was removed after installation.

User Response:

Create the directory and place Repository Agent and PowerCenter Server configuration files
in the appropriate global_repo, local_repo, and PCServer directories under the server/
upgrade/cfgfiles directory on the node, and then validate the files again.

PCSF_10359

File <file name> contains service <service name> which already exists in other configuration
files selected for upgrade.

Explanation:

The value for the <RepositoryName> or <ServerName> property in the Repository Agent or
PowerCenter Server configuration file matches the same property in another configuration file
under the server/upgrade/cfgfiles directory on the node. All configuration files you want to
upgrade must contain different values for the <RepositoryName> or <ServerName>
properties. There may be duplicate configuration files in the upgrade directory.

User Response:

Make sure the configuration file have unique values for the <RepositoryName> or
<ServerName> properties and validate the files again.

PCSF_10360

File <file name> contains configuration for Integration Service <service name> is associated
with repository service <service name>. The repository service is not found in domain
<domain name>.

Explanation:

The PowerCenter Server configuration file contains an associated repository that does not
have a corresponding Repository Service in the domain. The Upgrade Wizard requires
information from the repository to upgrade the PowerCenter Server. As a result, the Upgrade
Wizard cannot upgrade the Powercenter Server.

User Response:

Upgrade the Repository Agent for the associated repository before you upgrade the
PowerCenter Server.

Chapter 16: P Message Codes

PCSF_10361

Configuration for Integration Service <service name> is associated with repository service
<service name>. The repository service is not found in domain <domain name> and in the list
of configuration files selected for upgrade.

Explanation:

The PowerCenter Server configuration file contains an associated repository that does not
have a corresponding Repository Service in the domain or in any of the Repository Agent
configuration files you want to upgrade. The Upgrade Wizard will not be able to upgrade the
PowerCenter configuration file without an upgraded Repository Service for the associated
repository.

User Response:

Make sure the domain has an upgraded Repository Service for the associated repository or
that the upgrade directory has a Repository Agent configuration file for the associated
repository. Otherwise, remove the PowerCenter Server configuration file from the upgrade
directory.

PCSF_10374

Failed to persist <object> with error <error message>.

Explanation:

PowerCenter could not create the object because of the database error shown.

User Response:

Correct the database error.

Explanation:

The infasetup DefineDomain command was used to create a domain on IBM DB2 and the
primary tablespace default page size is too small.

User Response:

If the domain configuration database type is IBM DB2, make sure that the primary tablespace
default page size is at least 16K.

PCSF_10386

Unable to decrypt the password for option <option name>. It's possible that the password is
corrupted. Please use previous installation of PowerCenter to re-generate the password and
try again.

Explanation:

The Upgrade Wizard cannot decrypt the encrypted password in the Repository Agent or
PowerCenter Server configuration file.

User Response:

Use pmpasswd in the previous version of PowerCenter to encrypt the password. Correct the
password in the configuration file, revalidate the configuration file, and upgrade the
Repository Agent or PowerCenter Server configuration file again.

PCSF_10389

The Repository Agent configuration file <configuration file name> is located in the PCServer
directory. This directory should only contain PowerCenter Server configuration files.

Explanation:

The Repository Agent configuration file is not in the correct directory.

User Response:

Move the Repository Agent configuration file to the global_repo or local_repo directory.

PCSF_10391

Configuration file contains required option(s) <option names> with empty value.

Explanation:

A property or properties in a Repository Agent or PowerCenter Server configuration files does

not have a corresponding value.

User Response:

Add a value for the property in the configuration file and validate and upgrade the
configuration file again.

PCSF_10392

Explanation:

The Repository Agent or PowerCenter Server configuration contains an error and the
Upgrade Wizard cannot upgrade the configuration file.

User Response:

Correct the error indicated in the message and validate and upgrade the configuration file
again.

PCSF Messages

257

258

PCSF_10402

Unable to validate the log directory <shared disk> due to the error <error>.

Explanation:

The permissions of the shared disk was not validated.

User Response:

Verify the path and directory. The user that starts Informatica Services on the node must
have permissions to write to the directory.

PCSF_10421

Error parsing upgrade configuration file at line #<line number>. The end string */ for block
comment must be at the end of the line.

Explanation:

In a Repository Agent or PowerCenter Server configuration file, the end block comment string
*/ occurs in the middle of a line, but can only appear at the end of a line.

User Response:

Correct the configuration file and place the end comment string at the end of the line. Then
validate and upgrade the configuration file again.

PCSF_10422

Error parsing upgrade configuration file. The start of block comment was detected at line
#<line number>; however, the end string */ for ending block comment was never found.

Explanation:

You started a comment block that was not ended in a Repository Agent or PowerCenter
Server configuration file.

User Response:

Correct the configuration file and place the end comment string in the file. Then validate and
upgrade the configuration file again.

Chapter 16: P Message Codes

PCSF_10423

File <file name> is a Repository Agent configuration file. Choose a PowerCenter Server
configuration file or change the configuration file type.

Explanation:

In the Upgrade Wizard, you chose a Repository Agent configuration file, but selected a
PowerCenter Server file type.

User Response:

Choose a PowerCenter Server configuration file or change the file type.

PCSF_10424

File <file name> is a PowerCenter Server configuration file. Choose a Repository Agent
configuration file or change the configuration file type.

Explanation:

In the Upgrade Wizard, you chose a PowerCenter Server configuration file, but selected a
Repository Agent file type.

User Response:

Choose a Repository Agent configuration file or change the file type.

PCSF_10426

Cannot find server <server name> in repository <repository name>.

Explanation:

The PowerCenter Server is not registered to the associated repository in the PowerCenter
Server configuration file.

User Response:

Back up the domain, correct the backup XML file, and restore the domain.

PCSF Messages

259

260

PCSF_10433

Option field cannot be empty.

Explanation:

Domain metadata is invalid with empty option.

User Response:

Back up the domain, correct the backup XML file, and restore the domain.

Explanation:

A minimum option value is greater than a maximum option value.

User Response:

Make sure the minimum value is less than or equal to the maximum.

PCSF_10446

Option memory size <invalid value> must be blank or a number followed by optional K or M.

Explanation:

A number option contained invalid memory size format.

User Response:

Enter a valid memory size format.

PCSF_10458

Database name should not be defined with connection string.

Explanation:

You specified both database service name and database connection string.

Chapter 16: P Message Codes

User Response:

Define absolute paths for $WorkflowLogDir and $PMStorageDir in the Integration Service
Process properties before you use operating system profiles.

PCSF_10507

The Integration Service cannot use operating system profiles on Windows node <node name>
in <service name>.

Explanation:

Integration Services can use operating system profiles on UNIX nodes. The Integration
Service cannot use operating system profiles on Windows nodes.

User Response:

Enable operating system profiles for an Integration Service that runs on UNIX nodes.
Disable operating system profiles for the Integration Service.

PCSF_10524

The selected database type <database type> does not support tablespaces.

Explanation:

The database type you specified does not support tablespaces.

User Response:

Omit the -tablespace option from the command.

PCSF_10535

Cannot read PowerCenter installation directory and version from nodemeta.xml.

Explanation:

The Service Manager cannot read the values for the PowerCenter installation directory and
PowerCenter version in nodemeta.xml. As a result, the Service Manager could not start the
node. This error occurs when nodemeta.xml contains inconsistent data.

User Response:

Back up the domain metadata in the domain configuration database, use infasetup to
redefine the node, and restart the node.

PCSF_10536

Cannot start node because nodemeta.xml does not contain values for the PowerCenter
installation directory or version.

Explanation:

nodemeta.xml for the node does not contain values for the PowerCenter installation directory
or PowerCenter version. As a result, the Service Manager could not start the node. This error
can occur if you edit nodemeta.xml and do not specify the correct values for the PowerCenter
installation directory or PowerCenter version.

User Response:

Back up the domain metadata in the domain configuration database, use infasetup to
redefine the node, and restart the node.

PCSF Messages

261

262

PCSF_10537

Cannot run application service <service name> of version <service version> on node <node
name>.

Explanation:

You cannot run the application service on the node because the version of PowerCenter
required to run the service is not installed on the node. In a mixed-version domain, the
PowerCenter version for the service must be installed on the node where you want to run the
service.

User Response:

Change the node assignment for the service to a node that contains the required version of
PowerCenter.

PCSF_10538

Cannot create application service <service name> of version <service version> in domain of
version <domain version>.

Explanation:

You cannot create the service because the current domain does not contain the version of
PowerCenter you want to create the service for.

User Response:

Create an application service of a service version that is supported by the domain.

PCSF_46000

INFA_DOMAINS_FILE is not set in the environment variable.

Explanation:

You can use the environment variable INFA_DOMAINS_FILE to store the domains.infa path.
You will receive an error if the environment variable INFA_DOMAINS_FILE is not set.

User Response:

Add the environment variable INFA_DOMAINS_FILE, and set the path to the domains.infa
file. By default, the domains.infa file resides in the infa_home directory.

PCSF_46002

Failed to communicate with the server at <server address>.

Explanation:

The request exceeded the timeout period due to an invalid connection or domain not running.

User Response:

Ping the domain using infacmd ping and provide the gateway address. If the connection is
invalid, infacmd ping adds or updates domains.infa file. If the domain is not running, ask the
domain administrator to start Informatica Services.

Explanation:

The HTTPS port number was used to connect to the PowerCenter domain from the
PowerCenter Client.

User Response:

Use the HTTP port number to connect to the PowerCenter domain from the PowerCenter
Client.

PCSF_46003

Failed to understand the response <response text> from server at <server address>: <error
text>.

Explanation:

A PowerCenter component failed to understand the response from a PowerCenter service

due to an error.

User Response:

Correct the error indicated in the message.

PCSF_46006

Domain name is not specified.

Explanation:

Explanation:

The request exceeded the timeout period due to an invalid connection or domain not running.

User Response:

Explanation:

The HTTPS port number was used to connect to the PowerCenter domain from the
PowerCenter Client.

User Response:

Use the HTTP port number to connect to the PowerCenter domain from the PowerCenter
Client.

PCSF_46010

Cannot parse message: <reason for error>

Explanation:

You specified the incorrect domain name, gateway host name, or port number from a
PowerCenter client application, such as pmcmd or the Designer.

User Response:

Verify that you use the correct gateway information. If the gateway information is correct, and
you continue to receive this error, contact Informatica Global Customer Support.

Explanation:

The Domain Service could not parse the SOAP message received from a remote client, such
as an FTP server.

User Response:

Review the log for related messages to find out more information.
Contact Informatica Global Customer Support.

PCSF_46012

Cannot write to file <file name>.

Explanation:

The domains.infa file is read-only, or there is not enough disk space available.

User Response:

Make sure the domains.infa file is not read-only and that there is enough disk space available.

PCSF Messages

263

PCSF_46013

Cannot connect to URL < URL > to perform operation <operation name> of service <service
name>.

Explanation:

A client or service attempted to connect to the URL to perform an operation. However, the
operation failed because the client or service could not connect to the URL within the
resilience timeout.

User Response:

Verify that the host name and port number for the URL and retry the operation.

PCSF_46014

Cannot connect to gateway to look up service <service>.

Explanation:

The PowerCenter component could not connect to the Service Manager on the gateway node
to look up a service within the resilience timeout for the domain.

User Response:

Verify that the gateway node is running.

PCSF_46015

An unexpected token was encountered during deserialization.

Explanation:

The preparer DTM process was unable to retrieve run time properties from the Integration
Service due to an error.

User Response:

Use the returned error code error message to determine the cause of this error.

PETL_24061

The Master DTM exceeded the maximum wait time while waiting for all Worker DTMs to
connect.

Explanation:

The master DTM process waited longer than the maximum amount of time allotted to wait for
worker DTM processes to connect. The node running the worker DTM process may have
failed, or connectivity to the worker DTM process may have failed. Or, the worker DTM
process may have shut down unexpectedly.

User Response:

PETL_24063

The Preparer DTM encountered error <error message> with error code <error code> while
notifying the Integration Service of the prepare phase status.

Explanation:

An error prevented the preparer DTM process from connecting to the Integration Service.

User Response:

Use the returned error code message to determine the cause of this error.

PETL_24064

Thread <thread ID> waited for <time in seconds> seconds for a message. The current number
of attempts is <attempt number> and the maximum number of attempts is <maximum number
of attempts>.

Explanation:

An error prevented the preparer DTM process from connecting to the Integration Service.

User Response:

Use the returned error code message to determine the cause of this error.

PETL Messages

265

266

PETL_24065

Error: Thread <thread name> exceeded the maximum wait time while waiting for a reply from
the Master DTM.

Explanation:

A worker DTM process waited longer than the maximum amount of time allotted to wait for a
reply from the master DTM process.

User Response:

PETL_24066

The Master DTM connection with the Worker DTM running partition group <partition group
ID> was broken unexpectedly. The Master DTM will abort processing.

Explanation:

The master DTM process detected that a worker DTM process failed unexpectedly.

User Response:

PETL_24067

The Worker DTM connection with the Master DTM terminated unexpectedly. The Worker DTM
will stop processing the session.

Explanation:

The worker DTM process detected that a connection to the master DTM process failed. The
master DTM process and worker DTM process may be on different nodes and there may be a
network failure.

User Response:

PETL_24072

Error: Thread <thread name> failed to get a reply from the Master DTM.

Explanation:

Internal error. The Master DTM process failed to respond to the thread due to any of the
following reasons: network failure, maximum CPU usage, a maximum number of processes
on the node, or no available ports.

User Response:

Contact the network administrator to verify that the network does not have connectivity
issues. Contact the domain administrator to verify that the Integration Service is running. Run
the session again. If the issue exists, then contact Informatica Global Customer Support.

PETL_24074

Failed to send updates to the master service process. Session run will be terminated.

Explanation:

The master DTM process was unable to send updates to the master service process.

User Response:

Chapter 16: P Message Codes

PMF Messages
PMF_15000

Failed to read from file <file name>.

Explanation:

The Integration Service failed to read the file. The file might be already open, or the disk
might be corrupt.

User Response:

Check the session log for related errors.

PMF_15001

Failed to write to file, there may not be enough space left on the device.

Explanation:

The hard disk is full.

User Response:

Check the disk for free space, and check the session log for related errors.

PMF_15002

Failed to seek in file <file name>.

Explanation:

The file pointer failed to locate the file. You might have deleted or moved the file, or the hard
disk might be corrupt.

User Response:

Check the session log for related errors.

PMF_15003

File <file name> is not in the correct format.

Explanation:

You might have altered the format of the file. For example, you copied another file to the file.

User Response:

Use a previous copy of the file that has the correct format.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PMF_15004

Unable to open file <file name>.

Explanation:

The Informatica Services account or operating system profile does not have the write file
permissions.

User Response:

Grant write permissions on the file to the Informatica Services account or the operating
system user in the operating system profile.

Explanation:

The Integration Service could not locate the specified file because an incorrect file name or
cache directory was provided.

User Response:

Provide the correct file name and aggregation cache directory in the Workflow Manager.

PMF_15005

File <file name> is in an unknown state due to error from a previous run.

Explanation:

The system shut down unexpectedly during the previous run.

User Response:

Use the backup file filename.bak.

PMF_15006

Failed to create file <file name> because file exists and contains data.

Explanation:

The Integration Service failed to remove the previous file and detected a file containing data
and failed to overwrite it.

User Response:

Check the file and manually delete it or rename it. Run the session again.

PMF_15007

Failed to read file <file name> because PowerCenter/PowerMart file header is corrupt.

Explanation:

The file might be corrupt due to a system crash on a previous session run.

PMF Messages

267

User Response:

Use the backup file filename.bak, if available, and run the session again.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PMF_15008

I/O requested for invalid file ID.

Explanation:

Internal error.

User Response:

Use the backup file filename.bak.

Contact Informatica Global Customer Support.

User Response:

Contact Informatica Global Customer Support.

PMF_15016

Failed to get a shared lock on file <cache file name>. System error is <error number> <error
message>.

Explanation:

The file might be in use. A session could be writing to the file.

User Response:

Check the session that is running. See the system error for more information.

PMF_15017

Failed to get an exclusive lock on file <cache file name>. System error is <error number>
<error message>.

Explanation:

The file might be in use. A session could be writing to the file.

Chapter 16: P Message Codes

User Response:

Check the session that is running. See the system error for more information.

PMF_15018

Failed to unlock file <cache file name>. System error is <error number> <error message>.

Explanation:

The file might be in use. A session could be reading or writing to the file.

User Response:

Check the session that is running. See the system error for more information.

PMF_15019

Failed to open file <file name>.

Explanation:

The file may be in use. Some other session that uses this file may be running.

User Response:

Wait until the session completes.

PMJVM Messages
PMJVM_42011

The DTM process failed to close the JVM session.

User Response:

No action is required because the operating system terminates the JVM session when the
DTM process completes.

PR Messages
PR_18001

Application Source Qualifier instance <Application Source Qualifier name> has tree source
<tree source definition name> and an Extract Override. Extract override will be ignored.

Explanation:

The listed Application Source Qualifier is connected to an imported PeopleSoft tree source
definition and has an extract override. You cannot use extract overrides for imported tree
sources.

User Response:

The Integration Service ignores the extract override. If you want to perform an extract
override on records connected to the Application Source Qualifier, connect the tree source
definition to a different Application Source Qualifier.
To keep this message from appearing again, remove the extract override from the session
properties.

PR_18003

Tree <tree name> with SetId <tree setid> and Effective Date <date> was not created.

Explanation:

The listed tree does not exist in the PeopleSoft source system or has unexpected conditions.

User Response:

Check the tree in the PeopleSoft source system for problems. If necessary, contact
PeopleSoft technical support.

Explanation:

The listed tree has no ports connected to an Application Source Qualifier.

User Response:

If you do not need the tree in the mapping, delete the tree source definition. Otherwise,
connect the necessary ports to an Application Source Qualifier.

PMJVM Messages

269

PR_18004

Application Source Qualifier instance <Application Source Qualifier name> has more than one
tree attached.

Explanation:

The listed Application Source Qualifier is associated or connected to more than one imported
PeopleSoft tree source definition. You can associate or connect only one imported tree
source definition to a single Application Source Qualifier.

User Response:

Disconnect one of the tree source definitions from the Application Source Qualifier. Or,
remove one of the associated tree source definitions.
To use more than one imported tree source in a single mapping, create an Application
Source Qualifier for each imported tree source you want to use. Use a Joiner transformation
to join two related tree sources.

PR_18005

Tree may only be joined with Detail record: <PeopleSoft record name>.

Explanation:

You connected or associated an imported tree and a record in an Application Source

Qualifier, and the record is not the detail record for the tree.

User Response:

You can connect or associate an imported tree with a non-detail record if the non-detail
record is related to the detail record and you connect or associate the detail record with the
Application Source Qualifier.
You can connect the tree and non-detail record to separate Application Source Qualifiers and
join them with a Joiner transformation.
To determine which record provides detail data for a tree, open the tree source definition in
the Mapping Designer and click the Attributes tab.

PR_18006

Not all sources are related in Application Source Qualifier <Application Source Qualifier
name>.

Explanation:

You tried to connect or associate two unrelated sources in the listed Application Source
Qualifier. You can only connect or associate related sources in an Application Source
Qualifier.

User Response:

Disconnect one of the unrelated sources.

Remove one of the associated source definitions.

270

PR_18007

Unknown error occurred in Application Source Qualifier <Application Source Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PR_18009

Error in converting <string> to Date. Internal Error.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

PR_18010

Tree <tree name> was changed after session run was started.

Explanation:

The listed tree changed in the PeopleSoft system after the Integration Service started the
session.

User Response:

The Integration Service completes the session with version of the tree as it was at the
beginning of the session. If this is not the version you want, correct the session targets and
run the session again.

Chapter 16: P Message Codes

PR_18011

Application Source Qualifier <Application Source Qualifier name> has projected port with no
inbound link.

Explanation:

The listed Application Source Qualifier has a connected output port, and the corresponding
input port is not connected.

User Response:

Connect the necessary input port, or disconnect the connected output port.

PR_18012

SQL Error <SQL statement>.

Explanation:

Internal error. The Integration Service encountered an error in the listed SQL statement.

User Response:

Contact Informatica Global Customer Support.

PR_18013

Warning: Application Source Qualifier transformation <Application Source Qualifier name>

has a larger number of sorted ports than projected output ports.

Explanation:

In an Application Source Qualifier, the number of sorted ports option on the Properties tab
has a higher value than the number of connected output ports.

User Response:

Either lower the Number of Sorted Ports value or increase the number of connected output
ports in the Application Source Qualifier.

PR_18020

The language table <language table name>, for the base table <base table name>, does not
have rows for the language <language code>.

Explanation:

The application connection for the session specifies a PeopleSoft language code, and the
source table listed in the error message does not have related data for the language you
specified. When there is no data for the specified language, the Integration Service returns
data from the base source table.

User Response:

If you require data in the specified language, that data must be entered into the PeopleSoft
system. If you want data in a different language, you can edit the application connection or
create a connection for a different language code.

PR_18021

The Application Source Qualifier <Application Source Qualifier> has invalid user defined
query <query> with character error at <number> location.

Explanation:

You entered a query containing characters that are not valid in the source application
connection code page.

User Response:

Edit the query so all characters are valid in the source database connection code page.

PR_18022

The Application Source Qualifier <Application Source Qualifier> has invalid filter clause
<filter> with character error at <number> location.

Explanation:

You entered a filter condition containing characters that are not valid in the application
connection code page.

User Response:

Edit the filter condition so all characters are valid in the application connection code page.

PR_18023

The Application Source Qualifier <Application Source Qualifier> has invalid join and/or filter
override <join override> with character error at <number> location.

Explanation:

You entered a join condition and/or a source filter condition that contains characters that are
not valid in the application connection code page.

User Response:

Edit the join and/or filter conditions so all characters are valid in the application connection
code page.

PR Messages

271

272

PR_18026

The session failed because Application Source Qualifier <Application Source Qualifier name>
contains a vertical tree source definition with no PeopleSoft tree attributes assigned. (At least
provide Tree Name and Effective Date.)

Explanation:

You did not import PeopleSoft tree attributes into the created tree source definition.

User Response:

Import tree attributes in the created tree source definition. You can import the tree attributes
in either the source definition in the Mapping Designer or in the session properties. You must
enter at least the PeopleSoft tree name and its effective date.

PR_18027

Application Source Qualifier <Application Source Qualifier name>: Error in preparing the
query for effective date data extraction.

Explanation:

You have defined this Application Source Qualifier to extract current rows from an effective
dated record that has no primary keys or PeopleSoft keys defined.

User Response:

Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in
the Source Analyzer.

Explanation:

You have specified an effective date join order in this Application Source Qualifier, and at
least one of the effective dated records has no primary keys or PeopleSoft keys defined.

User Response:

Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in
the Source Analyzer.

PR_18028

Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract
Join Order with invalid source names.

Explanation:

In the Effective Date Join Order field, you typed a PeopleSoft record name that is not
connected to the Application Source Qualifier.

User Response:

Edit the Effective Date Join Order field so that each PeopleSoft record name is spelled
correctly. The record names you enter in the Effective Date Join Order field must match the
records associated with the Application Source Qualifier. Separate each record name with a
comma.

PR_18029

Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract
Join Order with invalid number of source names. This should be equal to the number of
effective dated records in the DSQ.

Explanation:

In the Effective Date Join Order field, you entered too few or too many PeopleSoft record
names.

User Response:

Edit the Effective Date Join Order field so the number of records you enter equals the number
of records associated with the Application Source Qualifier. Verify that you separated each
PeopleSoft record name with a comma.

PR_18030

Application Source Qualifier <Application Source Qualifier name> cannot have Effective Date
Extract Join Order when number of Effective Dated sources is one.

Explanation:

You entered an effective date join order in the session properties, but there is only one
effective dated record connected to the Application Source Qualifier.

User Response:

Delete the text from the Effective Date Join Order field in the session properties.

PR_18031

Application Source Qualifier <Application Source Qualifier name> has invalid Extract Date.

Explanation:

You entered the Extract Date in the wrong date format.

User Response:

Enter the Extract Date in the following format: MM/DD/YYYY HH24:MI:SS.

Chapter 16: P Message Codes

PR_18032

Application Source Qualifier <Application Source Qualifier name> has extract date mapping
variable which cannot be expanded or Parameter File has invalid value for extract date
mapping variable.

Explanation:

You entered a mapping parameter or variable for the Extract Date transformation option that
does not exist in the mapping parameter file for the session.

User Response:

Specify the correct mapping parameter file for the session. Make sure the parameter file
contains a value for the mapping parameter or variable that you entered for the extract date.

Explanation:

You entered an invalid value in the parameter file for the extract date mapping parameter or
variable.

User Response:

Verify that the value you entered in the mapping parameter file for the extract date mapping
parameter or variable is in the correct datatype format. Enter the value in Informatica default
date format: MM/DD/YYYY HH24:MI:SS.

PR_18033

Application Source Qualifier <Application Source Qualifier name> has a tree instance
<created tree source definition name>, whose source name through a mapping variable
cannot be expanded or resolved correctly.

Explanation:

You entered a mapping parameter or variable for the PeopleSoft tree name that does not
exist in the mapping parameter file for the session.

User Response:

Specify the correct mapping parameter file for the session. Verify that the parameter file
contains a value for the mapping parameter or variable that you entered for the PeopleSoft
tree name.

Explanation:

You entered an invalid value in the parameter file for the PeopleSoft tree name mapping
parameter or variable.

User Response:

Verify that the value you entered in the mapping parameter file for the PeopleSoft tree name
mapping parameter or variable is in the correct datatype format.

PR_18034

Application Source Qualifier <Application Source Qualifier name> has a tree instance
<created tree source definition name>, whose effective date through a mapping variable
cannot be expanded or resolved correctly.

Explanation:

You entered a mapping parameter or variable for the Effective Date option that does not exist
in the mapping parameter file for the session.

User Response:

Specify the correct mapping parameter file for the session. Verify that the parameter file
contains a value for the mapping parameter or variable that you entered for the Effective
Date option.

Explanation:

You entered an invalid value in the parameter file for the Effective Date option mapping
parameter or variable.

User Response:

Verify that the value you entered in the mapping parameter file for the Effective Date option
mapping parameter or variable is in the correct datatype format.

PR_18035

Application Source Qualifier <Application Source Qualifier name> has a tree instance
<created tree source definition name>, whose Set Id through a mapping variable cannot be
expanded or resolved correctly.

Explanation:

You entered a mapping parameter or variable for the Set ID option that does not exist in the
mapping parameter file for the session.

User Response:

Specify the correct mapping parameter file for the session. Verify that the parameter file
contains a value for the mapping parameter or variable that you entered for the Set ID option.

PR Messages

273

Explanation:

You entered an invalid value in the parameter file for the Set ID option mapping parameter or
variable.

User Response:

Verify that the value you entered in the mapping parameter file for the Set ID option mapping
parameter or variable is in the correct datatype format.

PR_18036

Application Source Qualifier <Application Source Qualifier name> has a tree instance
<created tree source definition name>, whose Set Control Value through a mapping variable
cannot be expanded or resolved correctly.

Explanation:

You entered a mapping parameter or variable for the Set Control Value option that does not
exist in the mapping parameter file for the session.

User Response:

Specify the correct mapping parameter file for the session. Verify that the parameter file
contains a value for the mapping parameter or variable that you entered for the Set Control
Value option.

Explanation:

You entered an invalid value in the parameter file for the Set Control Value option mapping
parameter or variable.

User Response:

Verify that the value you entered in the mapping parameter file for the Set Control Value
option mapping parameter or variable is in the correct datatype format.

PR_18037

Application Source Qualifier <Application Source Qualifier name> has a tree instance
<created tree source definition name>, with an invalid effective date.

Explanation:

You entered an invalid value in the Effective Date option in the created tree source definition
in the Mapping Designer or in the session properties.

User Response:

Verify that the date you entered for the Effective Date is in the Informatica default date
format: MM/DD/YYYY HH24:MI:SS.

PR_18038

ERROR: One or more fields used to partition source(s) of Source Qualifier <Application
Source Qualifier name> have been deleted. Please edit and save the session to correct the
partitioning information.

Explanation:

You defined a partition key for a port in the Application Source Qualifier that you deleted.

User Response:

Edit the session to remove the partition key from the Application Source Qualifier. Then save
the new partition information in the session and run it again.

PR_18040

Application Source Qualifier <Application Source Qualifier name>: Error! The TO_EFFDT field
cannot be projected if there is no primary or PeopleSoft key in the source.

Explanation:

You have defined this Application Source Qualifier to connect a TO_EFFDT field from a
source that has no primary keys or PeopleSoft keys defined.

User Response:

Disconnect the link between the TO_EFFDT field in the source and the Application Source
Qualifier.

PWX Messages

274

PWX-34000

Unable to stop PowerExchange Task. iSync not established.

Explanation:

An internal error occurred.

The user credentials are not sufficient to perform the attempted action.

User Response:

Change the privileges assigned to the user, or use a different user name.

PWX-34504

Trying to connect to PowerExchange Task. Approx seconds seconds remaining...

Explanation:

The PowerExchange Service will keep trying to connect to the PowerExchange task for the
specified number of seconds before abandoning the connection attempt.

User Response:

No response is required.

PWXPC Messages
For information about PowerExchange Client for PowerCenter messages, see the PowerExchange Message
Reference.

276

Chapter 16: P Message Codes

CHAPTER 17

R Message Codes
This chapter includes the following topics:
REGEX Messages, 277
REP Messages, 278
REP_CORE Messages, 327
RFC Messages, 327
RR Messages, 329
RS Messages, 331

277

REGEX_34010

The Integration Service failed to validate the subject because of a perl compatible regular
expression syntax error.

Explanation:

The Integration Service could not validate the value for the subject argument, because there
was a perl compatible regular expression syntax error. There might not be enough system
memory. Or, the value of the subject argument may contain invalid syntax.

User Response:

Verify that the system contains enough memory.

Verify the syntax of the expression. Use perl compatible regular expression syntax.

REGEX_34011

The Integration Service failed to extract the subpattern because of a perl compatible regular
expression syntax error.

Explanation:

The Integration Service could not extract the subpattern, because there was a perl
compatible regular expression syntax error. There might not be enough system memory. Or,
the subpattern may contain invalid syntax.

User Response:

Verify that the system contains enough memory.

Verify the syntax of the expression. Use perl compatible regular expression syntax.

REGEX_34014

REG_REPLACE function takes three or four arguments.

Explanation:

The number of arguments passed to the function was invalid.

User Response:

Verify the syntax of the function.

REP Messages

278

REP_12001

Failed to log onto database server.

Explanation:

The Integration Service failed to connect to the database server. You may have logged in
incorrectly.

User Response:

REP_12005

An error occurred while opening a packaged SQL script file for execution. The product was
probably not installed correctly. Contact customer support for assistance.

Explanation:

The Integration Service cannot locate a necessary SQL script file.

User Response:

In the win.ini file, make sure the HOME entry in the Informatica PowerMart entry points to the
directory where the SQL script is located. If the HOME entry is correct, contact Informatica
Global Customer Support.

REP_12014

An error occurred while accessing the repository.

Explanation:

The Repository Service encountered an error while accessing the repository.

User Response:

If the repository is older, upgrade the repository. If the software is older, upgrade the software.

REP_12119

A repository does not exist at the specified database connection.

Explanation:

The Integration Service failed to connect to the database. You may have logged in incorrectly.

User Response:

Explanation:

You do not have the appropriate database privilege to view repository tables.

User Response:

Have the database administrator review the database privileges.

REP Messages

repository.

User Response:

Connect to the registered repository and correct the configuration parameters.

REP_12327

Internal error. Connection callback returned an error.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_12328

The repository at this location does not have the same name.

Explanation:

Either the database connection or the repository name entered is incorrect.

User Response:

The status bar displays the correct repository name. Correct the inaccurate information.

Explanation:

You tried to connect to a repository on the network, but there was a network failure during the
connect process.

User Response:

Verify that the PowerCenter Client and the repository are connected to the network. When
you connect to the repository again, enter the host name and port number of the repository in
the Connect to Repository dialog box.

REP_12330

Failed to fetch repository information.

Explanation:

This is a database error.

User Response:

Check the server event or error log for related database error messages. If no database error
is reported, contact Informatica Global Customer Support.

Chapter 17: R Message Codes

REP_12332

Error initializing repository object information.

Explanation:

You are low or out of memory.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the system.

Explanation:

You tried a global repository operation, such as registering a repository, when you were not
connected to a global repository.

User Response:

If desired, promote the repository to a global repository.

Warning: Once a repository becomes a global repository, you cannot change it to a local
repository.

REP_12336

This repository is already registered with the GDR <global repository name>.

Explanation:

You tried to register a repository to a global repository that is registered with a different global
repository.

User Response:

If the repository should be registered with the new global repository, unregister the repository
from the original global repository. Register with the new global repository.

REP_12337

This is not a local repository.

Explanation:

You tried to register a dependent repository with a global repository. Only independent
repositories can be registered with a global repository.

User Response:

If the repository should be registered with a new global repository, unregister the repository
from the original global repository. Then register with the new global repository.

REP_12338

A repository with this name has already been registered.

Explanation:

You tried to register a local repository when a local repository of the same name exists in the
global repository.

User Response:

Unregister the repository. Copy the repository to another location with a new name, then reregister the repository.

REP_12339

Internal error. Error allocating a new repository ID.

Explanation:

Database error.

REP Messages

281

282

User Response:

Check the server event or error log for related database error messages. If no database error
is reported, contact Informatica Global Customer Support.

REP_12340

Error updating remote repository.

Explanation:

Database error.

User Response:

Check the server event or error log for related database error messages. If no database error
is reported, contact Informatica Global Customer Support.

REP_12341

Error updating GDR.

Explanation:

Database error.

User Response:

Check the server event or error log for related database error messages. If no database error
is reported, contact Informatica Global Customer Support.

Explanation:

The Repository Service of the local repository is running on a node that is not configured to
run the service version of the Repository Service.

User Response:

Configure the Repository Service of the local repository to run on a node that is configured to
run the service version of the Repository Service.

REP_12342

The selected repository is not registered with the current Global Repository.

Explanation:

You tried to unregister a repository that is not registered with the current global repository.

User Response:

You can only unregister repositories registered with a global repository.

REP_12346

Memory allocation failed.

Explanation:

Insufficient memory allocation.

User Response:

Close any unnecessary applications and restart the system. If this problem persists, you may
need to add RAM to the system.

REP_12347

An error occurred while updating connection information in the repository.

Explanation:

A database error occurred while updating connection information during repository

registration or while editing connection information.

User Response:

Check the Repository Service event or error log for a related database error message. If no
database error is reported, contact Informatica Global Customer Support.

REP_12352

The current user does not have the privilege to perform this operation.

Explanation:

You tried to perform an operation without the appropriate privileges.

User Response:

Have the database administrator review the privileges.

REP_12355

The object <object name> has been modified since the time it was read.

Explanation:

You tried to edit a repository object that has been modified and saved by another user since
you opened the object.

User Response:

Close the object and open it again to view the edited object.

REP_12357

The object <object name> is already locked by <user name>. Do you want to reobtain the lock?

Explanation:

You tried to edit an object that has been locked by the user name. Either someone used the
user name and password to access this object, or the client shut down while you were
working on the object.

Chapter 17: R Message Codes

User Response:

If someone is using the user name and password, click No, then ask that person to close the
object and log out. If the PowerCenter Client shut down while you were working on the object,
and you are sure that no one else has the object open, click Yes.
Warning: Choosing Yes when someone else is working on the object may cause permanent
damage to the repository.

REP_12363

Warning: Unable to check whether correct indices for the Teradata repository have been
created. Please verify that you backup the repository and then restore it after you upgrade it.

Explanation:

The database user starting the repository does not have permission to query the Teradata
dictionary. The Repository Service needs to query the Teradata dictionary to verify whether
the Teradata repository tables have the correct primary indexes.

User Response:

After you upgrade a Teradata repository, verify you back it up and restore it before starting it.
This causes the Repository Service to create new primary indexes for the repository tables.
You must back up and restore a Teradata repository before you can start it.

REP_12364

For Teradata upgrade process to be complete, please take a backup of the repository
(repository_name), delete existing repository and restore from the backup file. Then start the
repository.

Explanation:

You upgraded the Teradata repository and tried to start it without backing it up and restoring
it.

User Response:

Back up the repository and restore it. This causes the Repository Service to create primary
indexes for the repository tables. You must back up and restore the repository before you can
start it.

REP_12370

The repository version is incompatible with this release of the product. (The repository
version is <version> while the product expects <version>). A repository upgrade is required.

Explanation:

The repository needs to be upgraded to the current version expected by the product.

User Response:

Use the Administrator tool to upgrade the repository.

REP_12371

The repository version is incompatible with this release of the product. (The repository
version is <version> while the product expects <version>). A product upgrade is required.

Explanation:

The repository has been upgraded to a newer version of the product.

User Response:

Upgrade the PowerCenter Client, Repository Service, and the Integration Service.

REP_12372

The repository has data that is newer than this release of the product expects. (The repository
data version is <version> while the product expects <version>). A product upgrade may be
required.

Explanation:

The repository has been upgraded to a newer version of the product.

User Response:

Upgrade the PowerCenter Client, Repository Service, and the Integration Service.

REP_12373

The repository has data that may be too old for this release of the product. (The repository
data version is <version> while the product expects <version>). A repository data upgrade
may be required.

Explanation:

The repository needs to be upgraded to the current version expected by the product.

User Response:

Use the Administrator tool to upgrade the repository.

REP Messages

283

284

REP_12381

Unable to perform the operation since an expected object was not found. Please check the
repository.

Explanation:

Internal error. The repository may contain inconsistencies.

User Response:

Contact Informatica Global Customer Support.

REP_12382

Error while updating the object information in the repository. Either no row or more than one
row was updated.

Explanation:

Internal error. The repository may contain inconsistencies.

User Response:

Contact Informatica Global Customer Support.

REP_12386

There is no database object available for the repository <repository name>. (A repository is
not supported on the requested database or the appropriate database driver is not available.

Explanation:

A repository is not supported on the database type specified in the configuration file.

User Response:

Check the Integration Service Setup and correct the database type of the repository.

REP_12387

The attempt to get a <save/fetch> lock on the <object type> <object name> timed out due to
the following conflicting lock: User <user name> on the computer <hostname> running the
<application> obtained a <save/fetch> lock on the <object type> <object name> at <time>.
Please try again.

Explanation:

You tried to access or save a repository object, and the repository could not create the
necessary fetch or save lock to allow you to perform the task. This occurred because another
user has the object locked.

User Response:

Try again the operation again. If the problem persists, use the information provided to
determine if the listed user is accessing the object. If you can verify the object is not being
used or accessed, ask the administrator to unlock the object as necessary.

REP_12389

Unable to set database connection property <number>.

Explanation:

A database error prevented the repository connection from setting required database
connection parameters.

User Response:

Make sure the repository database server is up and running. If there is no problem in the
database, try connecting to the repository again. If the problem persists, contact Informatica
Global Customer Support.

REP_12390

Mapping <mapping name> contains a dependency that points to a non existent port. The
mapping is assumed to be invalid.

Explanation:

You started a session that uses a mapplet, and information about the mapping is inconsistent
in the repository.

User Response:

Open the mapping in the Designer, validate the mapping and save it again. If the problem
persists, the inconsistency is in the mapplet used by the mapping. Open the mapplet,
validate, and save it. Then validate and save the mapping again.

REP_12392

GID creation failed for repository <repository name>.

Explanation:

Internal error. This might be caused by hardware failure.

User Response:

Contact Informatica Global Customer Support.

Chapter 17: R Message Codes

Explanation:

A repository database error occurred causing the internal ID generation to fail.

User Response:

If a repository database error occurred, try again after correcting the database problem.

Explanation:

The repository has inconsistent data.

User Response:

Verify that the connectivity information is the same on all client systems. If the connection is a
secondary connection, make sure the connectivity information for the global repository did
not change after the local repository was registered. If you moved the global repository to a
different Repository Service, or edited the configuration information for the global repository,
the connectivity information may have changed. To update the connectivity information in the
repository domain, propagate the connectivity information for the global repository to the local
repository.

REP_12449

Internal error.

Explanation:

Internal error.

User Response:

Explanation:

A repository was not created, upgraded, or restored correctly. If the problem occurs in a
repository that is in use, the database may have inconsistencies.

Chapter 17: R Message Codes

User Response:

Contact Informatica Global Customer Support.

REP_12470

Error updating repository information.

Explanation:

A repository database error caused the repository creation or upgrade to fail.

User Response:

Try to create or upgrade the repository after fixing the database error. If the problem persists,
contact Informatica Global Customer Support.

REP_12471

Error creating first user.

Explanation:

A repository database error caused the repository creation to fail.

User Response:

Try to create the repository again after fixing the database error. If the problem persists,
contact Informatica Global Customer Support.

REP_12477

This repository contains folders which are currently in use. A repository cannot be deleted
while it is in use.

Explanation:

You tried to delete a repository while other users are logged in to the repository. Even if there
are no users connected, the repository could contain residual locks.

User Response:

REP_12488

Unable to add new internal sequence generator.

Explanation:

A repository database error caused the repository creation or upgrade to fail.

User Response:

Try to create or upgrade the repository after fixing the database error. If the problem persists,
contact Informatica Global Customer Support.

REP_12492

This repository contains folders which are currently in use. A repository cannot be upgraded
while folders are in use.

Explanation:

You tried to upgrade a repository when other users are logged in to the repository. If there
are no users connected, the repository might contain residual locks.

User Response:

REP_12494

The Repository is newer than the version supported by this software release. Unable to do an
upgrade.

Explanation:

The product version is older than the repository version.

User Response:

Release all old locks in the repository. Upgrade the PowerCenter Client to the latest version,
then upgrade the repository.

REP_12496

This repository is too old to be upgraded.

Explanation:

You tried to upgrade a repository with a newer release of the Repository Manager that does
not support upgrading that repository version.

User Response:

Contact Informatica Global Customer Support.

REP Messages

287

288

REP_12505

Error while executing script file <file name>.

Explanation:

A database error or a problem occurred in the script.

User Response:

Correct the database error and try the operation again. If there is no database error, contact
Informatica Global Customer Support.

REP_12581

An error occurred while opening a packaged SQL script file for execution. The product was
probably not installed correctly. Contact customer support for assistance.

Explanation:

The script file cannot be found in the PowerCenter Client installation directory or the file is
corrupt.

User Response:

Install the PowerCenter Client again to get the correct scripts. If the problem persists, contact
Informatica Global Customer Support.

REP_12589

Error occurred in locking.

Explanation:

An internal error occurred due to a database error or inconsistent data in the repository. This
error might be accompanied by a more descriptive error message or a database error
message.

User Response:

Abort the operation and try again. If the problem persists and there is no database error,
contact Informatica Global Customer Support.

REP_12590

Error updating <repository name> in GDR.

Explanation:

A database error occurred while registering or unregistering a repository.

User Response:

If a database error occurred, correct the database error and try again. Otherwise, contact
Informatica Global Customer Support.

REP_12591

Error updating <repository name> in GDR (Repository may be left in inconsistent state).

Explanation:

A repository database error occurred when you tried to register or unregister a repository.

User Response:

If a repository database error occurred, correct the database error and try again. If the
operation succeeds then the inconsistency in the repository will have been corrected.
Otherwise, contact Informatica Global Customer Support.

REP_12651

Memory allocation failed.

Explanation:

The Integration Service machine is out of memory.

User Response:

Increase virtual memory or close other applications.

REP_12654

Password is too long.

Explanation:

You entered a password that exceeded the limit of 76 characters.

User Response:

Use a shorter password.

REP_12678

The connection to Global DataMart Repository is unavailable for some reason.

Explanation:

Explanation:

Validation error. The code page of the source database connection is not a subset of the
Integration Service code page. This causes the session to fail when the Integration Service
runs in the Unicode data movement mode.

User Response:

If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration
Service runs in Unicode mode, correct the problem with one of the following actions:
Choose a different source database connection for the session.
Choose a different Integration Service to run the workflow.
Correct the code page configured for the source database connection.
Correct the code page registered for the Integration Service.

REP_12735

The source file <file name> and Integration Service <Integration Service name> do not have
compatible code pages. (One way compatibility is required.)

Explanation:

Validation error. The code page of the source file is not a subset of the Integration Service
code page. This causes the session to fail when the Integration Service runs in the Unicode
data movement mode.

User Response:

If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration
Service runs in Unicode mode, correct the problem with one of the following actions:
Choose a different source file and code page for the session.
Choose a different Integration Service to run the workflow.
Correct the code page registered for the Integration Service.

REP_12736

The database <database name> and Integration Service <Integration Service name> do not
have compatible code pages.

Explanation:

Validation error. The session contains a Lookup or Stored Procedure transformation and the
code page for the lookup or stored procedure database is not compatible with the Integration
Service code page. This causes the session to fail when the Integration Service runs in the
Unicode data movement mode.

User Response:

If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration
Service runs in Unicode mode, correct the problem with one of the following actions:
Choose a different Integration Service to run the workflow.
Correct the configured code page for the database in the Workflow Manager.
Choose a different lookup or stored procedure database in the session properties.
Correct the code page registered for the Integration Service.

REP Messages

289

290

REP_12773

The Global Repository code page (<code page name>) is not compatible with the selected
code page (<code page name>).

Explanation:

While upgrading a local repository, the local repository code page must be a superset of the
global repository code page.

User Response:

Choose an appropriate code page.

REP_12782

The repository <repository name>s code page <code page name> and <PowerCenter
Client>s code page <code page name> are incompatible.

Explanation:

The PowerCenter Client code page is not compatible with the code page of the repository to
which you are trying to connect. The PowerCenter Client and repository code pages must be
compatible. Their code pages must also be compatible with the Integration Service code
page.

User Response:

Change the code page for the PowerCenter Client to one that is compatible with the
repository code page. Or, if you need to change the repository code page, you can copy the
repository to a new location or backup and restore it. Both actions allow you to configure a
different code page for the repository.

REP_12934

Failed to fetch information for user <user name>.

Explanation:

This is a database error.

User Response:

Read the accompanying database error message for more details.

Explanation:

The computer running the PowerCenter Client is out of memory.

User Response:

Close other applications.

REP_12950

Lookup Transformation <transformation name> has INVALID lookup condition: Lookup Table
Column <column name> and Transformation Port <port name> are the same.

Explanation:

You entered an incorrect expression value for the lookup condition in the XML file. The
lookup table column is the same as the transformation port.

User Response:

Edit the XML file and make sure the lookup table column is different from the transformation
port. Or, export the object again and then import it.

REP_12951

The lookup condition is not valid: Lookup Table Column <column name> and Transformation
Port <port name> are the same. Transformation is not valid.

Explanation:

You entered an incorrect expression value for the lookup condition in the XML file. The
lookup table column is the same as the transformation port.

User Response:

Edit the XML file and make sure the lookup table column is different from the transformation
port. Or, export the object again and then import it.

REP_12952

Joiner Transformation <transformation name> has INVALID joiner condition: Master <port
name> and Detail <port name> are the same.

Explanation:

You entered an incorrect expression value for the join condition in the XML file. The master
port is the same as the detail port.

User Response:

Edit the XML file and make sure the master port is different from the detail port. Or, export
the object again and then import it.

Chapter 17: R Message Codes

REP_12953

The joiner condition is not valid: Master <port name> and Detail <port name> are the same.
Transformation is not valid.

Explanation:

You entered an incorrect expression value for the join condition. The master port is the same
as the detail port.

User Response:

Edit the XML file and make sure the master port is different from the detail port. Or, export
the object again and then import it.

REP_12954

Warning: The Call Text attribute of Stored Procedure transformation <transformation name>
has non-empty value when the Stored Procedure Type attribute is set to Normal.

Explanation:

The call text attribute for the stored procedure contains a value when you defined the stored
procedure type attribute as Normal in the XML file.

User Response:

Edit the XML file and make sure the call text attribute value is empty when you define the
stored procedure type attribute as Normal. Or, export the object again and then import it.

REP_12955

Warning: The Call Text attribute of Stored Procedure transformation has non-empty value
when attribute Store Procedure Type is set to Normal.

Explanation:

The call text attribute contains a value when you defined the stored procedure type attribute
as Normal in the XML file.

User Response:

Edit the XML file and make sure the call text attribute value is empty when you define the
stored procedure type attribute as Normal. Or, export the object again and then import it.

REP_12975

There is no existing MQ Connection to choose for <connection string> in the target repository.

Explanation:

This is an informational message. You tried to copy a WebSphere MQ session to a target

repository with no defined queue connections.

User Response:

Create at least one queue connection in the target repository.

REP_12991

Failed to connect to <repository name> Repository Agent on host <host name> (port number:
<port number>). System error message: <error message>.

Explanation:

A repository client could not connect to a Repository Agent process. The Repository Agent
host name or port number may be incorrect.

User Response:

Verify that the host name and port number specified in the repository client connection
information is the same as the information specified in the Repository Agent configuration.

REP_12994

Server system error (errno = <error number>): <system error message>.

Explanation:

An error occurred on the Repository Service system.

User Response:

For Repository Service on Windows, check the system event log for related error messages.
See Windows help and look up the specified system error number.
For Repository Service on UNIX, locate the error in the /usr/include/sys/errno.h file. See the
UNIX Documentation for explanation of the error.

REP_12995

Failed to shutdown Integration Service.

Explanation:

The Integration Service would not shut down.

User Response:

Check preceding messages to see the cause of the error.

REP Messages

291

292

REP_12996

No key is selected for Sorter transformation <transformation name>.

Explanation:

You did not configure a sort key for the Sorter transformation.

User Response:

Edit the Sorter transformation and select one or more ports to use as a sort key.

REP_12999

No key is selected for Sorter transformation. This transformation is not valid.

Explanation:

You did not configure a sort key for the Sorter transformation.

User Response:

Edit the Sorter transformation and select one or more ports to use as a sort key.

REP_22674

Custom Transformation <transformation name> has non-ASCII character(s) in its class name.

Explanation:

The Custom transformation class name contains non 7-bit ASCII characters.

User Response:

Edit the transformation properties and enter 7-bit ASCII characters for the class name.

REP_32000

Error: Could not find DSQ instance <Source Qualifier name> for <source>.

Explanation:

The Source Qualifier transformation associated with the source is missing in the XML file.

User Response:

Edit the XML file and verify that it has a valid entry for the Source Qualifier transformation.
Or, export the object again and then import it.

REP_32001

Error: Source Reference: <source> DBD: <source> for DSQ <Source Qualifier name> not
found.

Explanation:

The source associated with a specified Source Qualifier transformation is missing in the XML
file.

User Response:

Edit the XML file and verify it has a valid source for the specified Source Qualifier
transformation. Or, export the object again and then import it.

REP_32002

Error: There are more than one groups with the order: <number> in <group>.

Explanation:

The XML file specifies more than one group with the same order for that particular source,
target, or transformation.

User Response:

Check the ORDER entry under the GROUP node for that specified source, target, or
transformation in the XML file. Or, export the object again and then import it.

REP_32003

Error: Field order does not match group order.

Explanation:

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

User Response:

Edit the XML file and make sure the field order matches the group order. Or, export the
object again and then import it.

REP_32004

Error: Invalid Transformation type <type> for transformation <transformation name>.

Explanation:

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

User Response:

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

REP_32007

Folder referenced by the shortcut object does not exist, object will be created in the current
folder.

Explanation:

The shortcut to an object does not contain folder information. You might have renamed or
deleted the folder.

Chapter 17: R Message Codes

User Response:

Restore the folder in the target repository. Otherwise the object is imported as the actual
object the shortcut references, as defined by the metadata in the XML file, under the current
folder.

REP_32010

Error: Object referenced by shortcut: <shortcut>. Referring to <object> in Repository:

<repository name>. Folder: <folder name> not found.

Explanation:

You deleted or renamed a folder that contains a shortcut in the specified repository.

User Response:

Restore the folder or re-create the shortcut to the object in the folder.

REP_32015

Code page in file: <file name> not compatible with repository code page: <code page>.

Explanation:

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

User Response:

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

REP_32016

Error: Invalid Database Type: <database type>.

Explanation:

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

User Response:

Edit the XML file and verify the database type. Or, export the object again and then import it.

REP_32018

Invalid Delimiters: <delimiter>.

Explanation:

You defined invalid delimiters for a flat file source in the XML file.

User Response:

Edit the XML file under the FLAT FILE node. Or, export the object again and then import it.

REP_32019

Error: Invalid table attribute: <attribute>.

Explanation:

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

User Response:

Edit the XML file for that attribute. Or, export the object again and then import it.

REP_32020

Warning: Could not link fields <field name>:<field name>:<field name>: Instance <instance>
to Field: <field name> Instance <instance>.

Explanation:

An invalid connector node exists for a mapping or mapplet in the XML file.

User Response:

Fix the CONNECTOR node under the mapping or mapplet. Or, export the object again and
then import it.

REP Messages

User Response:

Edit the group type node in the XML file.

REP_32032

Error: Cannot import tables of type <TABLETYPE value>.

Explanation:

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

Chapter 17: R Message Codes

User Response:

Edit the XML file and enter NONE for the TABLETYPE attribute. Or, export the object again
and then import it.

REP_32033

Error: This target cannot have groups.

Explanation:

You specified a target in the XML file that does not support groups.

User Response:

Edit the XML file and remove the group node. Or, export the object again and then import it.

REP_32034

Database Error: while Assigning Ids for Target: <target name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_32035

Error: Invalid Initialization Property: <INITPROP name>.

Explanation:

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

User Response:

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,
export the object again and then import it.

REP_32036

Error: This transformation cannot have groups.

Explanation:

In the XML file, you entered a GROUP element for a transformation that does not support
groups.

User Response:

Edit the XML file to remove the GROUP element from the transformation that does not
support groups. Or, export the object again and then import it.

REP_32037

Database Error: while Assigning Ids for Transformation: <transformation>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_32038

Error: Invalid Datatype: <datatype> for field: <field name>.

Explanation:

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

User Response:

Edit the XML file to specify a supported datatype. Or, export the object again and then import
it.

REP_32039

Error: Missing ATTRIBUTE <XML attribute name> for field: <SOURCEFIELD name or
TRANSFORMFIELD name>.

Explanation:

The specified attribute is missing or empty in the specified element in the XML file.

User Response:

Edit the XML file and enter the necessary attribute in the specified element or add a value for
the specified attribute. Or, export the object again and then import it.

REP_32040

Error: Could not find associated source field: <SOURCEFIELD name> for <Normalizer
transformation>.

Explanation:

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.

REP Messages

295

296

User Response:

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

REP_32041

Error: Invalid Instance Type: <TYPE value>.

Explanation:

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

User Response:

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

REP_32042

Error: Invalid reference field <REF_FIELD name> for Transformation field:

<TRANSFORMFIELD name>.

Explanation:

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

User Response:

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

REP_32043

Error: Missing attribute <MAPPLETGROUP> or <REF_FIELD> for Field: <mapplet name>.

Explanation:

REP_32047

Error: Invalid Mapplet Group <MAPPLETGROUP> for Field: <MAPPLETGROUP value>

Transformation: <transformation name>.

Explanation:

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

User Response:

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

REP_32050

Error: Could not find Transformation definition for: <transformation or source or target name>.

Explanation:

The TRANSFORMATION_NAME attribute in the INSTANCE element does not match a

TRANSFORMATION element name in the XML file.

User Response:

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

REP_32056

Error: Missing or Empty Attribute: <attribute name>.

Explanation:

You did not enter the specified attribute in either a SOURCE, SOURCEFIELD, or
TARGETFIELD element in the XML file.

User Response:

Edit the XML file and enter the necessary attribute. Or, export the object again and then
import it.

REP Messages

297

298

REP_32063

Error: An Unknown target field attribute: <attribute ID> has been detected for Field: <field
name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_32066

Error: Could not get group for source field: <source field>.

Explanation:

Explanation:

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

User Response:

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

REP_32097

Warning: FTP connection <FTP connection> not found. Session will be imported without
reference to FTP connection.

Explanation:

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

User Response:

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

REP_32098

Warning: Loader connection <external loader connection> not found. Session will be
imported without reference to Loader connection.

Explanation:

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

User Response:

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

REP_32101

Error: Internal Error encountered in initializing Parser.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_32103

Warning: Invalid Usage type: <type> for field: <field name>.

Explanation:

You defined an invalid usage type description under the flat file node in the XML file.

REP Messages

299

300

User Response:

Edit the XML file. Or, export the object again and then import it.

REP_32105

Error: Invalid Codepage: <code page> for Flat File.

Explanation:

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

User Response:

Cannot import the source.

REP_32111

Error: Invalid Database Type: <DATABASETYPE value> for source: <SOURCE name>.

Explanation:

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

User Response:

Edit the XML file and correct the DATABASETYPE attribute in the SOURCE element. Or,
export the object again and then import it.

REP_32112

Error: Missing or Empty Name for: <element>.

Explanation:

You did not enter a NAME attribute for the specified element.

User Response:

Edit the XML file and add a NAME attribute in the specified element. Or, export the object
again and then import it.

REP_32113

Error: Invalid number of fields for transformation: <Sequence transformation name>.

Explanation:

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

User Response:

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

REP_32115

Error: <object> <object name> cannot be imported as it is potentially unsafe. Importing any
associated mapping/mapplet might result in an error.

Explanation:

You created or modified an object in the XML file that cannot be created or modified.

User Response:

Export the object again and then import it.

REP_32116

Error: The mapping: <mapping name> is potentially unsafe and cannot be imported.

Explanation:

In the XML file, you modified an object that contains a CRCVALUE code. The object is a part
of the specified mapping.

User Response:

Export the object again and then import it.

REP_32117

Error: <transformation type> <transformation name> is potentially unsafe and will not be
available for import.

Explanation:

In the XML file, you modified either a source, target, or transformation that contains a
CRCVALUE code.

User Response:

Export the object again and then import it.

REP_32118

Error: Invalid Usage Flags: <flag>.

Explanation:

You specified an invalid usage flag in the XML file.

User Response:

User Response:

Edit the XML file and make sure there is only one field which has the port type as Rank. Or,
export the object again and then import it.

REP_32132

Error: Transformation <transformation name> has duplicate group <group> due to the same
group order.

Explanation:

You defined duplicated groups in the group order in the XML file.

User Response:

Edit the XML file and make sure the group order has different groups. Or, export the object
again and then import it.

REP_32135

Error: Invalid precision: <number> specified for field: <field name>. The maximum precision
is 65535.

Explanation:

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

User Response:

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

REP_32136

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

Explanation:

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.

REP Messages

301

302

User Response:

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

REP_32137

The first field of lookup transformation <transformation name> has to be a Dynamic Lookup
field when dynamic lookup cache is enabled. Transformation is not valid.

Explanation:

In the XML file, you defined the dynamic lookup cache attribute to YES, but you did not
define the first lookup port as NewLookupRow.

User Response:

When the dynamic lookup cache attribute is set to YES, the first field has to be
NewLookupRow. Edit the XML file, or export the object again and then import it.

REP_32138

Field <field name> for lookup transformation <transformation name> cannot be a Dynamic
Lookup field when dynamic lookup cache is disabled. Transformation is not valid.

Explanation:

In the XML file, you defined a lookup port as NewLookupRow, but you defined the dynamic
lookup cache as NO.

User Response:

You cannot have the NewLookupRow when the dynamic lookup cache attribute is set to NO.
Edit the XML file, or export the object again and then import it.

REP_32139

In Lookup transformation <transformation name>, the content(s) of the generated Dynamic

Lookup field <field name> has been changed. Transformation is not valid.

Explanation:

You modified the definition of the NewLookupRow port in the XML file.

User Response:

Do not change the NewLookupRow port in the XML file. Export the object again and then
import it.

REP_32140

In Rank transformation <transformation name>, the content(s) of the RANKINDEX field <field
name> has been changed. Transformation is not valid.

Explanation:

You modified the contents of the RANKINDEX field in the Rank transformation in the XML file.

User Response:

Do not modify the RANKINDEX field in the XML file. Export the object again and then import
it.

REP_32141

In Sequence Generator transformation <transformation name>, the content(s) of field <field

name> has been changed. Transformation is not valid.

Explanation:

You modified the definitions of the NEXTVAL and CURRVAL fields in the Sequence
Generator transformation in the XML file.

User Response:

Do not modify these fields in the XML file. Export the object again and then import it.

REP_32144

Error: Missing or invalid attribute <attribute name> for <element name>: <attribute value>.

Explanation:

In the XML file, you entered an invalid value or no value for the specified attribute in the
specified element.

User Response:

Edit the XML file and define a valid value for the specified attribute. Or, export the object
again and then import it.

REP_32148

Error: Invalid datatype for mapping variable <MAPPINGVARIABLE name>.

Explanation:

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

User Response:

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

Chapter 17: R Message Codes

REP_32149

Error: Invalid datatype for aggregate COUNT for mapping variable <MAPPINGVARIABLE
name>.

Explanation:

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.

User Response:

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

REP_32150

Error: Invalid aggregate type for mapping variable <MAPPINGVARIABLE name>.

Explanation:

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.

User Response:

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

REP_32151

Error: No name for the imported mapping variable.

Explanation:

In the XML file, the NAME attribute is missing from the MAPPINGVARIABLE element.

User Response:

Edit the XML file and add a NAME attribute to the MAPPINGVARIABLE element. Or, export
the object again and then import it.

REP_32167

Error: Duplicate instances of type: <instance type> name: <instance name>.

Explanation:

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

User Response:

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.

REP_32171

The mapping originally assigned to this session has been changed. Cannot import the
session.

Explanation:

You copied a mapping to a repository, but the mapping was modified, deleted or renamed.

User Response:

Copy or import the original mapping to the target repository again.

REP_32173

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

Explanation:

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

User Response:

Correct the value in the XML file. Or, export the object again and then import it.

REP_32174

Error: Invalid value: <value>, expecting unsigned value for attribute: <attribute>, for
<element>: <element name>.

Explanation:

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

User Response:

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

REP_32175

Error: Invalid target database type: <target database name> for target: <target name>.

Explanation:

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

User Response:

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

REP Messages

303

304

REP_32176

Two or more fields in the xml data Source Qualifier transformation: <Source Qualifier name>
refer to the same field: <field name> in the source.

Explanation:

In the XML file, you defined two transformation fields for the XML Source Qualifier
transformation with the same value for the REF_SOURCEFIELD attribute.

User Response:

Edit the XML file and provide the correct value. Or, export the object again and then import it.

REP_32177

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

Explanation:

In the XML file, you defined a plugin database type for the target, but you did not register the
plugin in the PowerCenter Client.

User Response:

Register the plugin the PowerCenter Client before importing the file. Or, edit the XML file and
specify an existing database type.

REP_32178

Error: Invalid Database Type: <database type> for target: <target name>, or the Database
Type is not installed in this repository.

Explanation:

In the XML file, you defined a plugin database type for the target, but you did not install the
plugin in the repository.

User Response:

Install the plugin in the repository before importing the file. Or, edit the XML file and specify
an existing database type.

REP_32180

Error: Invalid Task type <task type> for task <task name>.

Explanation:

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

User Response:

Edit the XML file, and specify a valid TYPE for the TASK. Or, export the object again and
then import it.

REP_32181

Error: Invalid Extension type: <session extension type> for element <SESSIONEXTENSION
element>.

Explanation:

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

User Response:

Edit the XML file, and specify a valid TYPE for the SESSIONEXTENSION. Or, export the
object again and then import it.

REP_32185

Error: The mapping <mapping name> associated with the session <session name> is invalid.

Explanation:

In the XML file, you specified a mapping that is invalid.

Edit the XML file and specify a valid attribute for the element. Or, export the object again and
then import it.

REP_32192

Error: Invalid Component Type <session component type> for element

<SESSIONCOMPONENT name>.

Explanation:

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

User Response:

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

REP_32193

Error: missing or empty attribute <attribute name> for element <element name>.

Explanation:

The XML file contains an empty attribute, or the attribute is missing.

User Response:

Edit the XML file and specify a valid attribute for the element. Or, export the object again and
then import it.

REP_32194

Error: Invalid partition type <PARTITIONTYPE name> for session transformation

<SESSTRANSFORMATIONINST name>.

Explanation:

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

User Response:

Edit the XML file, and specify a valid PARTITIONTYPE. Or, export the object again and then
import it.

REP_32195

Error: extension subType <SESSIONEXTENSION subtype> for extension type

<SESSIONEXTENSION type> is invalid for element <SESSIONEXTENSION name>.

Explanation:

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.

User Response:

Edit the XML file, and specify a valid SUBTYPE. Or, export the object again and then import
it.

REP_32196

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

Explanation:

In the SESSIONEXTENSION element, the referenced CONNECTIONREFERENCE element

does not exist.

REP Messages

305

306

User Response:

Edit the XML file, and specify a valid CONNECTIONREFERENCE. Or, export the object
again and then import it.

REP_32198

Error: Invalid connection type <connection type> for connection reference <connection
reference>.

Explanation:

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

User Response:

Edit the XML file, and specify a valid CONNECTIONTYPE attribute. Or, export the object
again and then import it.

REP_32199

Error: Invalid partition name <partition name> for element <element name>.

Explanation:

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

User Response:

Edit the XML file, and specify a valid PARTITIONNAME attribute. Or, export the object again
and then import it.

REP_32202

Error: Invalid DSQ instance name < Source Qualifier transformation name> for session
transformation instance <session transformation instance name>.

Explanation:

In the XML file, you specified a DSQINSTNAME attribute in a SESSIONEXTENSION element

that references a non-existent SESSTRANSFORMATIONINST element.

User Response:

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

REP_32203

Error: the number of partition <PARTITION name> is out of range [1-32] for session
transformation <SESSTRANSFORMATIONINST name> in session <session name>.

Explanation:

The number of PARTITIONs under SESSTRANSFORMATIONINST is invalid.

User Response:

Remove, as appropriate, the PARTITIONs from under the SESSTRANSFORMATIONINST so

that the number of PARTITIONs is less than or equal to 32.

REP_32204

Error: building session <session name>.

Explanation:

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

User Response:

View the Output window for more information. Export the object again and then import it.

REP_32205

Error: Invalid DSQ <Source Qualifier name> of type <DSQINSTTYPE> for the extension in
session transformation instance <SESSTRANSFORMATIONINST name>.

Explanation:

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.

User Response:

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

REP_32207

Error: Invalid datatype for workflow variable <workflow variable name>.

Explanation:

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

Chapter 17: R Message Codes

User Response:

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

REP_32208

Error: The extension of type <SESSIONEXTENSION type> and subtype <SESSIONEXTENSION

subtype> does not exist for session transformation instance <SESSTRANSFORMATIONINST
name>.

Explanation:

In the XML file, the TYPE and SUBTYPE attributes for the SESSIONEXTENSION element
are not supported for the SESSTRANSFORMATIONINST element.

User Response:

Edit the XML file, and specify TYPE and SUBTYPE attributes in the SESSIONEXTENSION
element that the SESSTRANSFORMATIONINST element supports.

REP_32209

Error: Invalid suspension email <SUSPENSION_EMAIL name> for workflow <workflow name>.

Explanation:

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

User Response:

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

REP_32210

Error: Name conflict or invalid object name <object name> for element <element name>.

Explanation:

In the XML file, you entered invalid characters for the specified element name, or you
specified an element name that conflicts with another element name.

User Response:

Edit the XML file, and rename the element using valid characters only. Or, export the object
again and then import it.

Explanation:

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

User Response:

Edit the XML file, and specify a valid DSQINSTTYPE attribute. Or, export the object again
and then import it.

REP_32216

Error: connection reference <CONNECTIONREFERENCE name> type <TYPE> and subtype

SESSTRANSFORMATIONINST element.

User Response:

Edit the XML file, and enter a valid PARTITIONTYPE. Or, export the object again and then
import it.

REP_32222

Error: duplicate object <object name> of type <object type>.

Explanation:

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

User Response:

Edit the XML file, and rename the duplicate object. Or, export the object again and then
import it.

Chapter 17: R Message Codes

REP_32223

Error: two Schedulers of conflicting types specified for workflow <WORKFLOW name>:
reusable <SCHEDULER under FOLDER> and nonreusable <SCHEDULER under WORKFLOW>.

Explanation:

Explanation:

You imported a Custom transformation defined with no input groups.

User Response:

Edit the XML file and define at least one input group. Or, export the object and import it again.

REP_32293

Error: The transformation <transformation name> has no output groups.

Explanation:

You imported a Custom transformation defined with no output groups.

User Response:

Edit the XML file and define at least one output group. Or, export the object and import it
again.

REP_32294

Error: Group <group> of the transformation <transformation name> is both an input group
and an output group.

Explanation:

You imported a Custom transformation with a group defined as both an output and input
group.

User Response:

Edit the XML file and define the group as either an input, output, or input/output group. Or,
export the object and import it again.

REP_32409

Session <session name> has a log file name which is longer than 600 characters. Session is
not valid.

Explanation:

The session log file name is too long.

User Response:

On the session Properties tab, specify a session log file name of 600 characters or fewer,
including the file extension.

REP Messages

309

310

REP_32410

Session has a log file name which is longer than 600 characters. Session is not valid.

Explanation:

The session log file name is too long.

User Response:

On the session Properties tab, specify a session log file name of 600 characters or fewer,
including the file extension.

REP_32413

Session <session name> has a log directory name which is longer than 600 characters.
Session is not valid.

Explanation:

The session log file directory name is too long.

User Response:

On the session Properties tab, specify a session log file directory name of 600 characters or
fewer, including delimiters.

REP_32414

Session has a log directory name which is longer than 600 characters. Session is not valid.

Explanation:

The session log file directory name is too long.

User Response:

On the session Properties tab, specify a session log file directory name of 600 characters or
fewer, including delimiters.

REP_32426

Session config <session configuration object name>. The number of runs to save session log
on must be in the range 0 to 2147483647.

Explanation:

For the named session configuration object, you are saving session logs by number of runs.
The number of runs you specified is out of range.

User Response:

On the session properties Config Object tab, Log Options settings, specify a number of runs
between 0 and 2,147,483,647.

REP_32427

The number of runs to save session log on must be in the range 0 to 2147483647.

Explanation:

You are saving session logs by number of runs. The number of runs you specified is out of
range.

Chapter 17: R Message Codes

User Response:

On the workflow Properties tab, specify a workflow log file directory name of 600 characters
or fewer, including delimiters.

REP_32472

'Save workflow log for these runs' must be in the range of 0 to 2147483647.

Explanation:

You are saving workflow logs for the named workflow for a certain number of runs. The
number of runs you specified is out of range.

User Response:

Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure
the number of runs is between 0 and 2,147,483,647.

REP_32483

Save workflow log for these runs must be in the range of 0 to 2147483647.

Explanation:

You are saving workflow logs by number of runs. The number of runs you specified is out of
range.

REP Messages

311

312

User Response:

On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647.

REP_32490

Workflow task <workflow name> log directory name must have a delimiter.

Explanation:

The workflow log file directory name for the named workflow does not end in a delimiter,
either use \ on Windows systems, or / on UNIX systems.

User Response:

On the workflow Properties tab, include the appropriate delimiter after the workflow log file
directory name.

REP_32491

Log directory name must have a delimiter.

Explanation:

The workflow log file directory name does not end in a delimiter, either use \ on Windows
systems, or / on UNIX systems.

User Response:

On the workflow Properties tab, include the appropriate delimiter after the workflow log file
directory name.

REP_32523

Session <session name> has different connection subtype across partitions.

Explanation:

Explanation:

User Response:

Edit the session properties and either specify a hash key at the named transformation or
change the partition type.

REP_32534

Invalid hash key <key name> for <transformation name> in session <session name>.

Explanation:

You selected hash user keys partitioning at the named transformation, but the hash key you
chose is no longer valid. This may have occurred because you updated the mapping and the
selected key is no longer in the named transformation.

User Response:

Edit the session properties and specify a new hash key at the transformation.

REP_32535

Invalid hash key <key name> for instance <transformation name>.

Explanation:

You selected hash user keys partitioning at the named transformation instance, but the hash
key you chose is no longer valid. This may have occurred because you updated the mapping
and the selected key is no longer in the named transformation.

User Response:

Edit the session properties and specify a new hash key at the transformation instance.

REP_32536

Hash key <key name> for instance <transformation name> in session <session name> has
invalid port type.

Explanation:

You selected key range or hash user keys partitioning at the named transformation instance,
but the key is no longer an input or an input/output port. This may have occurred because
you updated the mapping and changed the port types in the named transformation instance.

User Response:

Edit the session properties and select an input or input/output port as the key.

REP_32537

Hash key <key name> for instance <transformation name> has invalid port type.

Explanation:

Same as REP_32536.

REP_32542

Empty key range for <transformation name> in session <session name>.

Explanation:

You selected key range partitioning at the named transformation. Both the start and end
values for at least one key range are empty, and there is no a SQL override or filter condition
for the transformation.

REP Messages

313

314

User Response:

Either supply the missing start and end values for the key range, or specify a SQL override or
filter condition for the transformation.

REP_32543

Missing required hash key for <transformation name>.

Explanation:

User Response:

Either supply the missing start and end values for the key range, or specify a SQL override or
filter condition for the transformation.

REP_32544

Timer task <Timer task name> uses an empty workflow variable.

Explanation:

The Timer task uses a workflow variable to calculate the wait, but the variable has a null
value.

User Response:

Verify that the Timer task uses the correct variable. Also check the workflow or server log to
determine why the variable value is null.

REP_32546

Timer task <Timer task name> uses an invalid workflow variable.

Explanation:

The Timer task uses a workflow variable to calculate the wait, but the variable is invalid.

User Response:

Verify that the Timer task uses the correct variable. Also check the workflow to make sure the
variable exists.

REP_32548

Timer task <Timer task name> uses a workflow variable which is not Date/Time datatype.

Explanation:

The named Timer task uses a workflow variable to calculate the wait, but the variable
datatype is not Date/Time.

User Response:

Check the timer task to make sure you specified the correct variable. Also check the workflow
to make sure the variable datatype is Date/Time.

REP_32550

Key not specified for key range partition for <partition name:transformation name> in session
<session name>.

Explanation:

You selected key range partitioning at the named transformation, but there is no partition key.
This may have occurred because you updated the mapping and replaced the transformation
with one that contains different ports.

User Response:

Edit the session properties and either specify a partition key at the transformation or change
the partition type.

REP_32551

Key not specified for key range partition for <partition name:transformation>.

Explanation:

User Response:

Edit the session properties and either specify a partition key at the transformation or change
the partition type.

REP_32558

Workflow task <workflow name>: Save workflow log for these runs has an invalid Integration
Service variable associated with it.

Explanation:

You are saving workflow logs for the named workflow by number of runs. The number of runs
you specified is based on an invalid variable.

Chapter 17: R Message Codes

User Response:

Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure
that you specified the correct service variable. Also, verify that the variable you specified is
an integer variable.

REP_32559

Save workflow log for these runs has an invalid Integration Service variable associated with
it.

Explanation:

You are saving workflow logs by number of runs. The number of runs you specified is based
on an invalid service variable.

User Response:

Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure
that you specified the correct service variable. Also verify that the service variable you
specified is an integer variable.

REP_32701

Key not specified for Hash User Keys partition (group <group>, instance <transformation
instance name>, session <session name>).

Explanation:

You ran a session with a hash user keys partition point at a multi-group transformation, but
you did not specify a key.

User Response:

Edit the session properties and specify a key for the group. Or, change the partition type of
the group.

REP_32702

Key not specified for Hash User Keys partition (group <group>, instance <transformation
instance name>).

Explanation:

You ran a session with a hash user keys partition point at a multi-group transformation, but
you did not specify a key.

User Response:

Edit the session properties and specify a key for the group. Or, change the partition type of
the group.

REP_32705

Key not specified for Key Range partition (group <group>, instance <transformation instance
name>, session <session instance name>).

Explanation:

You selected key range partitioning, but you did not specify a key for the group.

User Response:

Edit the session properties to specify a key for the group or change the partition type for the
group.

REP_32706

Key not specified for Key Range partition (group <group> instance <transformation instance
name>).

Explanation:

You selected key range partitioning, but you did not specify a key for the group.

User Response:

Edit the session properties to specify a key for the group or change the partition type for the
group.

REP_32827

Syntax error: bad variable name <variable name>.

Explanation:

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.

User Response:

Make sure mapping variable names follow the correct format.

REP_32828

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

Explanation:

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

REP Messages

315

316

User Response:

Make sure mapping variable names are unique within any mapping.

REP_51042

Repository Agent connection failed. System Error (errno = <error number>) <error message>:
Cannot read message header. Read <number> bytes.

Explanation:

The connection to the Repository Agent process failed due to a system error.

User Response:

Check the system event log for related error messages to see the cause of the error. Try the
operation again. If the problem persists, contact the network administrator.

REP_51048

Communication failed because of network errors. [System Error (errno = <error number>):
<error message>.] Please try connecting to the repository again.

Explanation:

The PowerCenter Client or the Integration Service cannot connect to the Repository Agent.

User Response:

Read the operating system error referenced in this message and make any necessary
changes. There might be network problems.

REP_51054

Internal error: Cannot allocate buffer of size <size> bytes to receive incoming message. The
system may be out of memory.

User Response:

Verify that the Repository Agent process is running. If the Repository Agent is not running,
restart it. Also, verify the repository database is running.

Chapter 17: R Message Codes

REP_51058

Unknown TCP/IP error. Please try connecting to the repository again.

Explanation:

The PowerCenter Client or the Integration Service cannot connect to the Repository Agent
due to a network problem. This might happen if the Repository Agent machine was
disconnected from the network, or if it lost power.

User Response:

Verify the PowerCenter Client and Integration Service machines can connect to the
Repository Agent machine and try to connect again.

REP_51059

Repository Agent connection failed, another Repository Agent on host <host name> port
<port number> is already connected to this repository <repository name>.

Explanation:

There is another Repository Agent process already running for the repository.

User Response:

Connect to the running Repository Agent, or wait for it to shut down before connecting again.

REP_51074

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

Explanation:

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

User Response:

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.

REP_51075

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

Explanation:

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

User Response:

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

REP_51112

The reserved keyword <keyword> cannot be used.

Explanation:

You specified a keyword that is reserved. You cannot use reserved keywords.

User Response:

Specify a non-keyword.

REP Messages

317

318

REP_51115

A table with the name <table name> already exists. Please enter a unique name.

Explanation:

You specified a table name that is already in use.

User Response:

Enter a unique table name.

REP_51116

This business name has already been used by the source table <database name>:<table
name> in the repository and has been renamed to <table name>. You must save your changes
before renaming this table.

Explanation:

You changed the value for the business name in a source definition. You then attempted to
enter the old business name in another source definition. This is not allowed. For example,
you changed the business name in the source S1 from B1 to B2. You then entered the
business name B1 to another source definition, S2.

User Response:

Save the changes in the repository after entering the new business name for the target
definition. Then you can use the old business name for another target definition.

REP_51178

Warning: A matching Application connection was detected, but you do not have permission
to access this Application connection <connection name>. This Application connection will
be copied and renamed to <new connection name>.

Explanation:

Explanation:

You attempted to delete, create, or rename an initialization property that is a built-in

User Response:

Contact Informatica Global Customer Support.

REP_51304

Partition number <number> is not valid.

Explanation:

Plug-in internal error.

User Response:

Contact the plug-in application vendor.

REP_51343

Unable to connect to the database server. Please check the connection to the database server.

Explanation:

The Repository Agent process could not connect to the repository database server.

REP Messages

319

320

User Response:

Verify the repository database is running. Verify that you have a network connection to the
repository database system. Verify the database user name, password, and connect string
are correct. Verify the database type specified in the repository configuration is correct.

REP_51357

Failed to fetch the connection <connection name> specified for $Source because multiple
connections of different types have this name and the Integration Service cannot determine
which one of these connections to use.

Explanation:

The specified database connection name exists as both a relational and application
connection. When you entered the database connection name for the $Source Connection
Value session property, you did not specify Relational: or Application: before the connection
name.

User Response:

Enter Relational: or Application: before the connection name for $Source Connection Value
on the Properties tab of the session properties.

REP_51358

Failed to fetch the connection <connection name> specified for $Target because multiple
connections of different types have this name and the Integration Service cannot determine
which one of these connections to use.

Explanation:

The specified database connection name exists as both a relational and application
connection. When you entered the database connection name for the $Target Connection
Value session property, you did not specify Relational: or Application: before the connection
name.

User Response:

Enter Relational: or Application: before the connection name for $Target Connection Value
on the Properties tab of the session properties.

REP_51378

Failed to fetch the connection <connection name> specified for REH DB Log because multiple
connections of different types have this name and the Integration Service cannot determine
which one of these connections to use.

Explanation:

User Response:

Enter Relational: or Application: before the connection name for $Target Connection Value
on the Properties tab of the session properties.

REP_51444

MessageSendBufferSize value <message send buffer size> is invalid, ignoring invalid value
<message send buffer size>. Using system default value.

Explanation:

The repository is on a Windows machine and the repository configuration file specifies an
invalid value for the MessageSendBufferSize parameter. The Repository Agent uses the
default message send buffer size.

User Response:

Edit the repository configuration file and verify the MessageSendBufferSize size is greater
than or equal to zero. When you specify zero, the Repository Agent ignores the
MessageSendBufferSize parameter.

REP_51445

MessageReceiveBufferSize value <message receive buffer size> is invalid, ignoring invalid

value <message receive buffer size>. Using system default value.

Explanation:

The repository is on a Windows machine and the repository configuration file specifies an
invalid value for the MessageReceiveBufferSize parameter. The Repository Agent uses the
default message receive buffer size.

Chapter 17: R Message Codes

User Response:

Edit the repository configuration file and verify the MessageReceiveBufferSize size is greater
than or equal to zero. When you specify zero, the Repository Agent ignores the
MessageReceiveBufferSize parameter.

REP_51447

A repository request has timed out. [System Error (errno = <error number>): <system error
message>]. Please try connecting to the repository again.

Explanation:

The timeout values of the Repository Service requests are too small. Or, you made a request
for a large repository object, which decreased network performance.

User Response:

Increase the MessageReceiveTimeout value and MessageSendTimeout value from the

repository configuration.

Explanation:

Repository Service request timed out due to a slow network.

Enter a valid value for Database Pool Expiry Timeout in the Repository Service advanced
properties.

REP_51503

The value <number of connections> specified for Database Pool Expiry Threshold value is
invalid. The Repository Service is using the default value <number>.

Explanation:

The value specified for Database Pool Expiry Threshold is invalid. For example, it may be
less than the minimum, or it may be a negative number or a letter.

User Response:

Accept the default value for Database Pool Expiry Threshold.

Enter a valid value for Database Pool Expiry Threshold in the Repository Service advanced
properties.

REP_51507

Target <target name> cannot have FileName field.

Explanation:

You are importing a target that has a column defined as a FileName port, but the target does
not support a FileName port. The target must be a flat file.

User Response:

Remove the ISFILENAMEFIELD = YES field attribute in the XML file.

REP_51508

Target <target name> has existing FileName field.

Explanation:

You are importing a target the has two FileName ports. A flat file target can have one
FileName port.

User Response:

Remove the ISFILENAMEFIELD =YES field attribute for one of the columns in the XML file.

REP_51509

Workflow task <workflow ID> maximum automatic recovery attempts must be in the range of
0 to 2147483647.

Explanation:

The Maximum Automatic Recovery Attempts option contains a negative number.

REP Messages

321

322

User Response:

Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab.
The number must be zero or greater.

REP_51510

Maximum automatic recovery attempts must be in the range of 0 to 2147483647.

Explanation:

The Maximum Automatic Recovery Attempts is a negative number.

User Response:

Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab.
The number must be zero or greater.

Apply the Repository Service to a license that has the team-based development option. You
can purchase this option from Informatica.

REP_51961

The value of the environment variable <environment variable name> needs to be encrypted
with the latest version of pmpasswd.

Explanation:

The environment variable was encrypted using an old version of pmpasswd. Effective in
PowerCenter 8.1, pmpasswd uses a new, more robust encryption algorithm.

User Response:

Use the current version of pmpasswd to encrypt all passwords that you store as environment
variables, and update the environment variables with the new encrypted passwords.

REP_55035

An error occurred during deployment.

Explanation:

The Repository Agent process could not copy a folder.

User Response:

Check preceding messages to see the cause of the error. This error message may be
preceded by REP_51056.

Chapter 17: R Message Codes

REP_55036

An error occurred during folder comparison.

Explanation:

The Repository Agent process could not compare two folders.

User Response:

Check preceding messages to see the cause of the error.

REP_55102

Failed to connect to Repository Service <service name>.

Explanation:

The login information is not valid or the user does not have permissions on the repository.

User Response:

Action: Verify that the user name and password is correct. Also verify that the user has
permissions on the repository.

Explanation:

The host is not accessible from the client machine because of a firewall or an incorrect host
name and port number was specified for the repository connection.

User Response:

Verify that the connection information is valid and that the client machine can access the host
machine.

Explanation:

The repository version is not the same version as the PowerCenter Client or the Integration
Service.

User Response:

Verify that the PowerCenter Client, the Integration Service, and the Repository Service are
the same product version. If not, upgrade them to the same version.

Explanation:

The application encountered an error while connecting to the repository.

User Response:

Check the preceding messages to see the cause of the error.

REP_57060

Explanation:

The Service Manager could not authenticate the user.

User Response:

Check the additional error messages for more information.

REP_57064

Maximum number of connections exceeded.

Explanation:

The maximum number of connections to the Repository Agent process exceeded the number
of connections specified in the repository configuration.

User Response:

Edit the repository configuration and increase the value of the MaximumConnections
configuration option. Also, closed inactive connections to the repository.

REP_57071

Unable to connect to the repository database. Please check the Repository Agent
configuration.

Contact Informatica Global Customer Support.

REP_57151

Invalid function arguments.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_57169

Multiple connections of different types have the same name, and some sessions and/or
transformations contain this name without a type prefix (such as Relational:) as connection
information. This ambiguity must be resolved by prefixing those connection information.

Explanation:

The specified database connection name exists as both a relational and application
connection. You entered the database connection name for the Stored Procedure or Lookup
transformation location in the session properties, but you did not specify Relational: or
Application: before the connection name.

User Response:

Enter Relational: or Application: before the connection name for the Stored Procedure or
Lookup transformation location in the session properties.

Explanation:

The database connection name in the From field in the Replace Connections dialog box
exists as both a relational and application connection. You entered the database connection
name in at least one session or transformation, but you did not specify Relational: or
Application: before the connection name.

User Response:

Enter Relational: or Application: before the connection name in all transformation properties
and session properties that specify this database connection name.

REP_57201

Internal Error: Repository object is inconsistent.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

REP_57269

This connection has been terminated.

Explanation:

A repository connection ended because a repository or domain administrator terminated the

repository connection, and then a PowerCenter Client tried to reconnect to the repository with
the same connection.

User Response:

Verify that the repository administrator does not need to have all users disconnected from the
repository for maintenance or other purposes. Then retry the operation in the PowerCenter
Client.

REP_58224

Failed to connect from <PowerCenter Client tool> to repository <repository name> because
the repository users and groups have not been upgraded.

Explanation:

The PowerCenter Client could not connect to a repository because the repository users and
groups have not been upgraded.

User Response:

Upgrade the repository users and groups in the Administrator tool. Then retry the operation in
the PowerCenter Client.

REP_61002

WARNING: <XML definition> contained elements or attributes whose prefixes were removed.

Explanation:

You are upgrading an XML definition that contains prefixed attributes or elements. The XML
parser removes prefixes from attributes and elements and completes the repository upgrade.

User Response:

Complete the repository upgrade and import the XML definition again.

Chapter 17: R Message Codes

REP_61003

Empty key range for key <key name> (group <group>, instance <transformation instance
name>, session <session instance name>).

Explanation:

You did not specify a key range for the specified key.

User Response:

Edit the key range and specify the start and end value for the key.

REP_61004

Empty key range for key <key name> (group <group> session <session name>).

Explanation:

You did not specify a key range for the specified key.

User Response:

Edit the key range and specify the start and end value for the key.

REP_61010

Failed to validate transformation field <field name>.

326

REP_61059

Warning: Failed to upgrade XML source <source>, version <version>, folder <folder>.

Explanation:

You cannot upgrade the source XML definition because it has inconsistencies.

User Response:

The XML definition is unusable. You must recreate it.

REP_61060

Warning: Failed to upgrade XML target <target>, version <version>, folder <folder>.

Explanation:

You cannot upgrade the target XML definition because it has inconsistencies.

User Response:

The XML definition is unusable. You must recreate it.

REP_61063

Explanation:

The user name for a connection object is defined in a parameter file using session parameter
$ParamName. The session parameter value is incorrect. For example, the parameter value is
blank, or the parameter is not defined in the parameter file.

User Response:

Verify that the parameter is defined in the parameter file. Verify that the parameter value is
not blank.

REP_62378

Password variable <variable name> is not well defined.

Explanation:

The password for a connection object is defined in a parameter file using session parameter
$ParamName. The session parameter value is incorrect. For example, the parameter value is
blank, or the parameter is not defined in the parameter file.

User Response:

Verify that the parameter is defined in the parameter file. Verify that the parameter value is
not blank.

Chapter 17: R Message Codes

REP_62379

Connection name <parameter value> for connection variable <variable name> is not well
defined.

Explanation:

A session parameter such as $DBConnectionName was used to define a session connection.

In the parameter file, the session parameter value is incorrect. For example, the parameter
value is blank, or the parameter is not defined in the parameter file.

User Response:

Verify that the parameter is defined in the parameter file. Verify that the parameter value is
not blank.

REP_62385

Advanced recovery cannot be enabled since the session has mapping variables.

Explanation:

If a session uses mapping variables, you cannot configure the session recovery strategy to
resume from the last checkpoint.

User Response:

To set the recovery strategy to resume from the last checkpoint, remove the mapping
variables in the session.

REP_62386

Advanced recovery cannot be enabled for session <session name> since the session has
mapping variables.

Explanation:

If a session uses mapping variables, you cannot configure the session recovery strategy to
resume from the last checkpoint.

User Response:

To set the recovery strategy to resume from the last checkpoint, remove the mapping
variables in the session.

REP_CORE Messages
REP_CORE_59046

The high availability license is absent for the Repository Service process <process name>.

Explanation:

The high availability option is required for failover of the Repository Service process. You do
not have the high availability option.

User Response:

None.

RFC Messages
RFC_17403

Function return parameter is specified. However, only <value> out of <value> required values
found when parsing the property value string.

Explanation:

Valid return values are not specified in the function return parameter when parsing the
property value string.

User Response:

Enter valid return values in the function return parameter.

RFC_17405

Status or text field of return parameter must have ABAP type char in the source definition.

Explanation:

The ABAP datatype in the status or text field for the return structure is not specified as char
in the source definition.

REP_CORE Messages

327

328

User Response:

Specify the ABAP datatype as char in the status or text field for the return structure in the
source definition.

RFC_17411

Output data conversion error for row number <row number> of table parameter <parameter>.
This row will be skipped.

Explanation:

An invalid value has been provided for the function table parameter. This error occurs if the
input data to the function table parameter field is not convertible to the data type of the
corresponding field in the mapping.

User Response:

Enter a valid value for the function table parameter.

RFC_17412

Output data conversion error for Scalar Output parameter. This row will be skipped.

Explanation:

An invalid value has been provided for the scalar output parameter. This error occurs if the
input data to the scalar output parameter field is not convertible to the data type of the
corresponding field in the mapping.

User Response:

Enter a valid value for the scalar output parameter.

RFC_17416

Exception <exception> has been raised from the RFC function call with IntegrationID
<Integration ID>.

Explanation:

The RFC call to the SAP system from the SAP application server failed with an exception.

User Response:

Enter valid input data for the SAP system. Verify that the SAP application server is running.

RFC_17422

Function Name <Function name> and Sequence ID <Sequence ID> do not match. One of them
is incorrect.

Explanation:

The specified function name and sequence ID for the incoming row to the Custom
transformation is not in sync. Data may be incorrect or corrupt.

User Response:

Prepared data might be modified or incorrectly prepared in the prepared data pipeline. Check
the specified row data.

RFC_17423

Input for function <Function name> is received while expecting input for function <Function
name>.

Explanation:

There is only one function in the mapping and the value of sequence ID is not 1, or you have
more than one function in the mapping and the order of SequenceID is not in sequential
order. For example, the first row comes into the RFCMSFunctionCall Custom transformation
with SeqID = 1, the second row comes into the RFCMSFunctionCall Custom transformation
with SeqID = 3.

User Response:

The RFCFunctionCall Custom transformation expects the SequenceID to increase by

increment of 1 from the previous SequenceID. Check the data in the PreparedData targets.

RFC_17424

Call to function <Function name> corresponding to TransactionID = <Transaction ID>,

IntegrationID = <Integration ID> failed. Cannot continue transaction.

Explanation:

The function call to SAP with the specified TransactionID and IntegrationID has failed.

User Response:

See the error messages in the session log for more information.

RFC_17425

Commit call failed for TransactionID <Transaction ID>.

Explanation:

The commit function call to SAP has failed.

User Response:

See the error messages in the session log for more information.

Chapter 17: R Message Codes

RFC_17427

Error when trying to create SAP internal table for function table parameter <Parameter name>.

Explanation:

The Integration Service failed to create new SAP internal table.

User Response:

Check if the node where the Integration Service process runs is out of memory.

RFC_17439

The value of all connected input indicator ports is NULL. The source file may be invalid. See
the session log to find the row with the error.

Explanation:

You have requested a stored procedure that does not exist in the source databases.

User Response:

Check the source database for the stored procedure you have specified.

Explanation:

The Integration Service encountered an error while trying to run a stored procedure.

User Response:

Check the session log for related error messages.

RR_4032

Warning: # of sorted ports <number of ports> must be less than # of projected fields <number
of connected output ports>. Ignoring sort request.

Explanation:

The number of output ports connected from the Source Qualifier transformation to another
transformation is less than the number entered in the Source Qualifier number of sorted ports
option.

User Response:

Change the sort count to less than or equal to connected ports in the Designer.

RR_4033

Error parsing stored procedure call text <call text>.

Explanation:

The specified stored procedure call text is incorrect.

User Response:

Correct the call text before running the session again.

RR Messages

329

330

RR_4034

Projected column metadata fetch failed.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

RR_4035

SQL error.

Explanation:

Error executing SQL query.

User Response:

Make sure the query can run using SQL Override in the Source Qualifier transformation.
Also, verify that the source definition name matches the table name in the source database.
Otherwise, contact Informatica Global Customer Support.

RR_4036

Error connecting to database <database name>.

Explanation:

The Integration Service failed to connect to the database. You may have logged in incorrectly.

User Response:

Enter the correct login information. User names and passwords may be case sensitive.

RR_4038

Error setting stored procedures. Session-> m_pMapping corrupt.

Explanation:

Internal error. The repository might be out of memory or have inconsistencies.

User Response:

Contact Informatica Global Customer Support.

RR_4039

User defined query <query> contains character(s) that is (are) not valid in the code page of
the source database connection. The invalid character starts at position <number> of the
query.

Explanation:

You entered a query containing characters that are invalid in the source database connection
code page.

User Response:

Change the query to contain characters included in the source database connection code
page only.

RR_4040

User defined join condition and/or source filter condition <string> contains character(s) that
is(are) not valid in the code page of the source database connection. The invalid character
starts at position <number> in the above condition.

Explanation:

The join condition or the source filter condition or the combination of both join and filter
conditions contain characters that are invalid in the source database connection code page
only.

User Response:

Change either the join, filter, or both conditions to contain characters included in the source
database connection code page.

RR_4041

User defined source filter condition <string> contains character(s) that is (are) not valid in the
code page of the source database connection. The invalid character starts at position
<number> of the filter condition.

Explanation:

You entered a filter condition containing characters that are invalid in the source database
connection code page.

User Response:

Change the filter condition to contain characters included in the source database connection
code page.

Chapter 17: R Message Codes

RR_4043

ERROR: One or more fields used to partition source(s) of Source Qualifier <Source Qualifier
name> have been deleted. Please edit and save the session to correct the partitioning
information.

Explanation:

You defined a partition key for a port in the source qualifier that you deleted.

User Response:

Edit the session to remove the partition key from the Source Qualifier. Then save the new
partition information in the session and run it again.

RS Messages
RS_39037

Failed to start repository <repository name>.

Explanation:

The Repository Service failed to start a Repository Agent process for the repository.

User Response:

Check preceding error messages in the Repository Service log file to see the cause of the
error. Verify that the repository database is running. Verify that the repository configuration
information is correct. Verify that another Repository Service is not running a Repository
Agent for the repository.

RS_39061

Cannot start repository <repository name> as it is being shut.

Explanation:

You cannot start the repository because it is in the process of being shut down.

User Response:

The Repository Service could not promote a local repository to a global repository because it
could not start a Repository Agent process for the repository.

User Response:

RS_39107

Cannot start repository <repository name> as it has been disabled.

Explanation:

The Repository Service cannot start the repository because it is disabled.

User Response:

Enable the repository. If you cannot enable it, a repository administrator may have disabled
the repository for maintenance.

RS_39109

Cannot enable repository <repository name> as it is not disabled.

Explanation:

The Repository Service cannot enable the repository because it is already enabled.

User Response:

None.

RS_39120

ERROR: This product license does not allow global repositories. Only a PowerCenter license
does that.

Explanation:

You cannot create global repositories or promote a local repository to a global repository with
the current license.

User Response:

If you want to create global repositories, you need to purchase the Team-based Development
option.

RS_39121

ERROR: This product license does not allow registering or unregistering repositories. Only a
PowerCenter license does that.

Explanation:

You cannot register a local repository with or unregister a local repository from a global
repository with the current license.

Chapter 17: R Message Codes

RS_39209

Failed to complete a call to repository <repository name>.

Explanation:

The Repository Service failed to connect to the Repository Agent for the specified repository.
The Repository Agent may have stopped.

User Response:

Verify the Repository Agent is running. Read related error messages for more information.

RS Messages

333

CHAPTER 18

S Message Codes
This chapter includes the following topics:
SAPUTIL Messages, 334
SDKC Messages, 335
SDKS Messages, 335
SDKXML Messages, 336
SF Messages, 336
SFDC Messages, 341
SM Messages, 344
SORT Messages, 348
SPC Messages, 350
SQL Messages, 351
SR Messages, 354

SDKS Messages
SDKS_38005

Couldnt load the library <library> for plug-in #<ID>.

Explanation:

PowerCenter could not load the specified library for the repository plug-in. The library or
dependent libraries may not be in the proper directory.

User Response:

Verify that the library and any dependent libraries are in the proper directories.

SDKS_38006

Plug-in #<ID>s interface version <version> is not compatible with SDK interface version
<version>.

Explanation:

The version of the plug-in and the SDK version are not compatible.

User Response:

Update the plug-in version to an SDK-compatible version.

SDKS_38007

Error occurred during <phase> <reader/writer> plug-in #<ID>.

Explanation:

There was an error during plug-in initialization or deinitialization.

Explanation:

The plug-in for a Java Custom transformation or Java transformation failed during the
execution of a plug-in level function.

User Response:

If the message occurs for a session that contains a Java transformation, recompile the code
for the transformation in the Designer and run the session again.

SF Messages

336

SF_31143

Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following
error: <error message>.

Explanation:

The Integration Service could not connect to Salesforce using the configured proxy.

User Response:

Correct the error and run the session again.

SF_31233

Could not set up cURL to connect to the Salesforce Bulk API. Using the standard Salesforce
API.

Explanation:

The Integration Service cannot connect to the Salesforce Bulk API. Instead, it connects using
the standard Salesforce API.

User Response:

Run the session again. If the same error occurs, contact Informatica Global Customer
Support.

Chapter 18: S Message Codes

SF_31234

Bulk API error received from Salesforce. Exception code <code>. Exception message
<message>.

Explanation:

The Integration Service could not connect to Salesforce using the configured proxy.

User Response:

Correct the error and run the session again.

SF_31255

Salesforce could not process batch <batch ID> of job ID <job ID> because of the following
error: <message>.

Explanation:

Salesforce could not process a batch in the Salesforce Bulk API session.

User Response:

Correct the error and run the session again.

SF_31259

ZLib compression returned the following error: <message>.

Explanation:

An error occurred when compressing data for a Salesforce Bulk API session.

User Response:

Run the session again. If the same error occurs, contact Informatica Global Customer
Support.

SF_31324

Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following
error: <error message>.

Explanation:

The Integration Service could not connect to Salesforce using the configured proxy.

User Response:

Correct the error and run the session again.

SF_31426

Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following
error: <error message>.

Explanation:

The Integration Service could not connect to Salesforce using the configured proxy.

User Response:

Correct the error and run the session again.

SF_31523

Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following
error: <error message>.

Explanation:

The Integration Service could not connect to Salesforce using the configured proxy.

User Response:

Correct the error and run the session again.

SF Messages

337

338

SF_34030

Client application <application>, connection <connection ID>: recv failed. System returns
error code <error number>, error message <error message>.

Explanation:

The client application failed to establish a connection.

User Response:

See the additional error message for more information. Also, disable and enable the
Integration Service.

SF_34032

SF_34062

Cannot open service control manager.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

SF_34063

Cannot close service control manager.

Explanation:

Explanation:

Internal error. This message is preceded by SF_34094.

SF Messages

339

User Response:

Contact Informatica Global Customer Support.

SF_34096

Caught SIGFPE signal. Aborting this server process.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

SF_34098

Failed to allocate memory. Out of virtual memory.

Explanation:

The Integration Service requires more memory.

User Response:

Increase the amount of available virtual memory on the Integration Service system.

340

SF_34120

Cannot persist request GUID <GUID>, made by client application <client name> on host <host
name> through connection <connection name>. Request might not be executed following a
service process failure.

Explanation:

During a transient failure, the Integration Service could not access the $PMStorageDir to
store the request for recovery.

User Response:

Verify that the Integration Service can access $PMStorageDir. If the directory does not exist
or cannot be written to, the request cannot be persisted.

SF_34130

Cannot get the storage files in directory <directory name>.

Explanation:

The storage directory does not exist or there are no storage files in this directory.

User Response:

Make sure the $PMStorageDir directory path is set to directory that exists, and you have
proper write permissions to the directory.

Chapter 18: S Message Codes

SF_34155

Child process <process ID> terminated due to spurious abort errno <error number>.

Explanation:

The Session or Command task exited unexpectedly and the machine running the Integration
Service process generated an error.

User Response:

Use the error number to determine the cause of the error. If it indicates an out-of-memory
error, increase the swap space or reduce the maximum processes threshold. You define the
maximum processes threshold on the Properties tab for the node in the Administrator tool.
Review the core file of the process for the Command task.

SF_34160

High availability has been disabled. Contact Informatica Global Customer Support.

Explanation:

A custom property for the Integration Service is configured to disable high availability.

User Response:

Contact Informatica Global Customer Support.

SFDC Messages
SFDC_31101

Explanation:

You attempted to log in to Salesforce.com with an incorrect user name or password.

User Response:

Verify that the user name and password are correct.

SFDC_31102

Query failed. User <login user name>. SOSQL <SOSQL query>. Fault code <error code>.
Reason <error message>.

Explanation:

The SOQL query could not be executed.

User Response:

See the additional error message for more information.

SFDC Messages

341

342

SFDC_31103

QueryMore failed. User <login user name>. SOSQL <SOSQL query>. Query Batch Index
<query batch>. Fault code <error code>. Reason <error message>.

Explanation:

The queryMore operation could not be executed.

User Response:

See the additional error message for more information.

SFDC_31105

Fields mis-matched. Expected field name <field name>. Returned field name <field name>.

Explanation:

The field name defined in the source or target definition does not match the field name
returned from Salesforce.com.

User Response:

Change the field name in the source or target definition to match the field name in the
Salesforce object.

SFDC_31106

GetServerTimestamp failed. User <login user name>. Fault code <error code>. Reason <error
message>.

Explanation:

The Integration Service could not retrieve the current system timestamp from the Salesforce
service.

User Response:

See the additional error message for more information.

SFDC_31107

GetDeleted failed. User <login user name>. Start Time <time>. End Time <time>. Fault code
<error code>. Reason <error message>.

Explanation:

The Integration Service could not retrieve a list of object instances that were deleted from the
data of an organization within the specified time span.

User Response:

See the additional error message for more information.

SFDC_31112

Invalid Flush Interval value <number of seconds>. It must be set to a positive integer value.

Explanation:

The value for the change data capture flush interval is invalid.

User Response:

In the session properties, set the flush interval to a positive integer value if you use change
data capture.

SFDC_31113

Conversion Error Occurred. Field name <field name>. Data Value <field value before
conversion>.

Explanation:

An error occurred while converting data from the Salesforce datatype to the PowerCenter
datatype.

User Response:

Verify the datatype of the field and make any necessary changes before running the session
again.

SFDC_31114

Row Errors <number of row errors> exceeded session threshold <error threshold>.

Explanation:

The number of row errors was greater than the number of errors allowed by the session error
threshold.

User Response:

Fix the row errors and then run the session again.

SFDC_31115

Source <source name> and Application Source Qualifier <Application Source Qualifier name>
have different number of fields.

Explanation:

The source and the Application Source Qualifier transformation do not have the same
number of fields.

Chapter 18: S Message Codes

User Response:

Verify that the source and the Application Source Qualifier transformation have the same
number of fields.

SFDC_31116

Source field <source field name> and Application Source Qualifier field <Application Source
Qualifier field name> do not have the same name.

Explanation:

The source field name does not match the Application Source Qualifier port name.

User Response:

Change the port name in the Application Source Qualifier transformation to match the field
name in the source.

SFDC_31117

Source field <source field name> and Application Source Qualifier field <Application Source
Qualifier field name> do not have the same field position.

Explanation:

The field in the source does not have the same position as the field in the Application Source
Qualifier transformation.

User Response:

Move the field in the Application Source Qualifier transformation to match the field position in
the source.

SFDC_31118

Source field <source field name> and Application Source Qualifier field <Application Source
Qualifier field name> do not have the same datatype, precision, or scale.

Explanation:

The field in the source does not have the same datatype, precision, or scale as the field in
the Application Source Qualifier transformation.

User Response:

Change the datatype, precision, and scale of the field in the Application Source Qualifier to
match the datatype, precision, and scale of the field in the source.

SFDC_31201

Explanation:

You attempted to log in to Salesforce.com with an incorrect user name or password.

User Response:

Verify that the user name and password are correct.

SFDC_31202

Error received from salesforce.com. Fields <field names>. Status code <status code>.
Message <error message>.

Explanation:

The Integration Service failed to create, update, upsert, or delete a Salesforce.com object.

User Response:

Read the error message and make any necessary changes. For more information, look up
the error code in the Salesforce.com documentation.

User Response:

See the additional error message for more information.

SFDC_31206

A fault is received in an upsert request. Fault code <error code>. Fault subcode <error
subcode>. Reason <error message>. Detail <error detail>.

Explanation:

An error occurred in an upsert request.

User Response:

See the additional error message for more information.

SFDC_31207

Upsert is turned on but external ID is missing.

SM_7027

Transformation evaluation error; current row skipped. trying to delete a non-existing row.

Explanation:

The Integration Service failed to evaluate an expression with a particular row, forcing it to
skip that row.

User Response:

Check the session log for information about the skipped row.

SM_7038

Aggregate Error: The data movement mode <data movement mode for Integration Service>
for the Integration Service does not match the data movement mode <data movement mode in
cache> in cache.

Explanation:

You started a session using incremental aggregation after changing the Integration Service
data movement mode. The Integration Service cannot access incremental aggregation files
created in a different data movement mode.

User Response:

Delete the existing incremental aggregation files. Or, configure the session to reinitialize the
aggregate cache. Or, if the Integration Service data movement mode was changed in error,
change the data movement mode back to its original setting.

Chapter 18: S Message Codes

SM_7051

Aggregate error: index file timestamp is earlier than the timestamp of the Aggregator
transformation or mapping.

Explanation:

You modified a mapping containing an Aggregator transformation or modified the Aggregator

transformation. Then, when you ran the incremental aggregation session, the Integration
Service tried to reuse the existing cache file that was invalid with the Aggregator
modifications.

User Response:

The mapping and Aggregator transformation timestamp must be earlier than the cache file.
Either reinitialize the aggregate cache or delete the cache file manually.

SM_7072

Aggregate Error: Expecting keys to be descending.

Explanation:

You selected the Sorted Input option in an Aggregator transformation, but the data entering
the Aggregator transformation is not sorted.

User Response:

Sort the data before the Aggregator transformation, or clear the Sorted Input option. You can
sort the data using the Sorted Ports option in the Source Qualifier transformation, or you can
use a Sorter transformation.

SM_7073

Aggregate Error: Expecting keys to be ascending.

Explanation:

You selected the Sorted Input option in an Aggregator transformation, but the data entering
the Aggregator transformation is not sorted.

User Response:

SM_7087

Aggregate Error: code page <code page> and cached code page <code page> are not twoway compatible.

Explanation:

You changed the session code page using incremental aggregation. The new code page is
not compatible with the previous code page. Therefore, the data in the existing aggregate
cache is not compatible with the new session code page.

User Response:

To reuse the data in the cache, set the code page of the current session to a compatible code
page. Otherwise, reinitialize the cache or manually delete the cache file.

SM_7088

Aggregate Error: sort order <sort order> and cached sort order <sort order> mismatch.

Explanation:

You changed the session sort order. The new sort order is not compatible with the previous
code page sort order. Therefore, the data in the existing aggregate cache is not compatible
with the new session code page.

User Response:

If you want to reuse the data in the cache, set the sort order of the current session to a
compatible code page sort order. Otherwise, reinitialize the cache or manually delete the
cache file.

SM_7089

Aggregate error: Unknown code page <code page> in the aggregation cache.

Explanation:

The Integration Service cannot identify the code page used to create the incremental
aggregate cache because the cache was generated in a different server environment with a
different code page.

User Response:

Reinitialize the cache or manually delete the cache file.

SM Messages

345

346

SM_7091

Transformation Parse Fatal Error: Update Strategy Expression did not evaluate to a numeric
value.

Explanation:

The update strategy expression you specified in the Update Strategy transformation does not
evaluate to a numeric value.

User Response:

Verify that the update strategy expression evaluates to a numeric value.

SM_7096

Aggregate Error: Unable to execute cache upgrade utility <utility name>.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because it could
not locate the specified cache upgrade utility.

User Response:

Verify that the cache upgrade utility, pmcacheupgr on UNIX or pmcacheupgr.exe on

Windows, exists in the PowerCenter Services installation directory.

SM_7099

Fatal Error: Header from incremental aggregation files for Aggregator transformation
<transformation name> has invalid data.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because the files
contain corrupt data.

User Response:

If you have a backup of the incremental aggregation files, replace the corrupted files with the
backup files and run the session again. Otherwise, delete the existing incremental
aggregation files or configure the session to reinitialize the aggregate cache.

SM_7200

Error reading from incremental aggregation files for Aggregator transformation

<transformation name>.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because the
Integration Service does not have read permission on the cache directory.

User Response:

Verify that the user configured to start Informatica Services has read permission on the cache
directory.

SM_7202

The upgrade of the incremental aggregation files for Aggregator transformation

<transformation name> failed. Unable to write data to new cache file. Check if enough disk
space is available.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because the
cache directory has inadequate disk space or the Integration Service does not have write
permission on the cache directory.

User Response:

Check the disk for free space. Or, verify that the user configured to start Informatica Services
has write permission on the cache directory.

SM_7203

Key length for transformation <transformation name> has changed.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because you
changed the precision for one or more of the group by ports in the Aggregator transformation.

User Response:

To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete
the existing incremental aggregation files or configure the session to reinitialize the
aggregate cache.

SM_7204

Row size for transformation <transformation name> has changed.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because you
changed the precision for one or more of the ports in the Aggregator transformation that are
not defined as group by ports.

Chapter 18: S Message Codes

User Response:

To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete
the existing incremental aggregation files or configure the session to reinitialize the
aggregate cache.

SM_7207

Incremental aggregation upgrade error.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files.

User Response:

See additional error messages for more information.

SM_7208

Mapping has been modified since the incremental aggregation files for transformation
<transformation name> were last saved.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because you
modified a mapping containing an Aggregator transformation or modified the Aggregator
transformation. Then, when you ran the incremental aggregation session, the Integration
Service tried to reuse the existing cache file that was invalid with the Aggregator
modifications.

User Response:

To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete
the existing incremental aggregation files or configure the session to reinitialize the
aggregate cache.

SM_7209

Cache for transformation <transformation name> was created in a precision mode different
from the one specified by the session.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because the
Enable High Precision session option used for the incremental aggregation files differs from
the option used for the current session.

User Response:

If the Enable High Precision session option was changed in error, change the option back to
its original setting. Otherwise, delete the existing incremental aggregation files or configure
the session to reinitialize the aggregate cache.

SM_7210

Number of partitions has changed since cache creation.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because you
changed the number of partitions in the session.

User Response:

To reuse the data in the cache, change the number of partitions back to the original value.
Otherwise, delete the existing incremental aggregation files or configure the session to
reinitialize the aggregate cache.

SM_7211

The Integration Service data movement mode differs from the data movement mode used
when the cache was created.

Explanation:

The Integration Service failed to upgrade the incremental aggregation files because you
started a session using incremental aggregation after changing the Integration Service data
movement mode. The Integration Service cannot access incremental aggregation files
created in a different data movement mode.

User Response:

If the Integration Service data movement mode was changed in error, change the data
movement mode back to its original setting. Otherwise, delete the existing incremental
aggregation files or configure the session to reinitialize the aggregate cache.

SM_7217

Error: Failed to expand update override <text> for target instance <target name>.

Explanation:

The Integration Service cannot expand a parameter or variable in the target update override.

SM Messages

347

User Response:

Explanation:

The Integration Service cannot expand the parameter or variable in the target update
override due to an internal error.

User Response:

Contact Informatica Global Customer Support.

SM_7218

Aggregate functions are allowed in Aggregator transformations only.

Explanation:

A transformation that is not an Aggregator transformation contains an expression with an

aggregate function. Since aggregate functions may be used in Aggregator transformations
only, the expression is invalid. The aggregate function might have been passed into the
transformation expression using a mapping parameter or variable.

User Response:

Check the transformation expression to see if it uses an aggregate function. If the

transformation expression contains mapping parameters or variables, make sure that their
values do not contain aggregate functions.

SM_7219

Fatal error parsing the Lookup transformation. Verify that the update dynamic cache
condition of the Lookup transformation <transformation name> evaluates to a numeric value.

Explanation:

The expression to update the dynamic cache for the Lookup transformation does not evaluate
to a numeric value.

User Response:

Verify that the update dynamic cache condition of Lookup transformation evaluates to a
numeric value.

SORT Messages

348

SORT_40046

Mmap <number of bytes> bytes of /dev/zero failed: <error message>. Either increase the swap
space or decrease the Cache Size in the Transformation <transformation name>.

Explanation:

The Integration Service could not allocate memory for the Sorter or Lookup transformation
because there is not enough available memory.

User Response:

Free memory resources or increase the swap space on the Integration Service system. You
can also reduce the cache size to match the amount of available memory.

SORT_40090

There are only <amount of available memory> megabytes of <total memory> available. Either
increase the swap space or decrease the Cache Size in the Transformation <transformation
name>.

Explanation:

You ran the session on a UNIX Integration Service and the necessary cache size of the
specified transformation exceeds the maximum memory allowed for processes that run on
the UNIX machine.

User Response:

Increase the memory limit for processes on the UNIX machine.

SORT_40095

File or filesystem <file or file system name> could not be accessed.

Explanation:

The Integration Service could not access the specified file.

User Response:

Verify you have read permission for the specified file.

User Response:

Free memory resources or increase the swap space on the Integration Service system. You
can also reduce the cache size to match the amount of available memory.

SORT_40189

The sort library could not create a thread.

Explanation:

The Integration Service system does not have enough resources to run the sort operation.

User Response:

Free Integration Service system resources by closing applications. After you free system
resources, restart the workflow.

SORT_40304

This operation appears to need <value> MB of memory; excessive paging is possible;

continuing.

Explanation:

You specified a Sorter cache size above the minimum required cache size, but the Sorter
cache size is small compared to the size of the incoming data. The Integration Service can
proceed with the sort operation, but the session will have decreased performance.

Internal sorter error <error>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

SORT_40414

Error: Total row size <row size> in transformation <transformation name> is more than the
allowed maximum [8 MB].

Explanation:

The sum of all port sizes in the specified Sorter or Lookup transformation exceeds 8 MB.

User Response:

Disconnect any port that you do not need in the mapping. Consider redesigning the mapping
to reduce the number of ports in the specified transformation. Or, reduce the precision of
large string or binary ports.

User Response:

To enable the service, disable the service, and then enable it again.

Chapter 18: S Message Codes

SPC_10039

Could not start Informatica PowerCenter Web Services Hub service on port <port number>
because this port is in use.

Explanation:

The port number assigned to the Web Services Hub is already in use.

User Response:

Reconfigure the Web Services Hub to use a different port number.

SPC_10052

The domain failed to restart the service <service name> after trying for maximum <number of
restart attempts> restart attempts.

Explanation:

The application service process became unavailable. The domain could not restart the
application service process for the specified number of restart attempts or the service version
installation directory is no longer valid.

User Response:

Check the domain and application service log events for errors. Fix the errors and restart the
application service process in the Administrator tool.
If the service version installation directory was changed, update the node using infasetup
UpdateGatewayNode or UpdateWorkerNode.

SQL Messages
SQL_50001

IOutputBuffer::setRowType() API has failed.

Explanation:

The Integration Service failed to generate an output row from the SQL transformation.

User Response:

Review previous error messages for more information.

SQL_50002

NULL DB Handle returned.

Explanation:

The Integration Service failed to connect to a database using a dynamic connection with an
SQL transformation.

User Response:

The source data contains invalid connection data. The database user name, database
password, server, or connect string is not correct for the database.

SQL_50003

ScriptName is empty.

Explanation:

The SQL transformation is configured to run an external SQL script but the ScriptName port
contains no data.

User Response:

The ScriptName port must contain the name and path of the file containing an SQL script to
run for each input row. Verify ScriptName port is connected and the source data contains the
file name.

SQL_50004

SetProperty failed.

Explanation:

The Integration Service failed to set database properties for an SQL transformation dynamic
connection.

User Response:

The dynamic connection contains Advanced Option name-value pairs. Verify that you spelled
the options correctly and each option is valid for the database type. The Advanced Options
are not case sensitive.

SQL Messages

351

352

SQL_50005

Logical Connection Object Name is empty.

Explanation:

The Integration Service failed to connect to a database for this row because the
LogicalConnectionObject port of the SQL transformation contains no data.

User Response:

Verify that the LogicalConnectionObject port is connected and the source data contains a
valid connection object name in each row.

SQL_50006

FlushOutRow failed.

Explanation:

The Integration Service failed to generate an output row from the SQL transformation.

User Response:

Review previous error messages for more information.

SQL_50007

ODL Error has occurred. Please see the pre-defined error port for detailed error message.

Explanation:

The Integration Service encountered a database error while processing an SQL query from
the SQL transformation.

User Response:

Review the error messages from the SQL transformation SQLError port.

SQL_50008

Number of columns in the select query is greater than the number of output ports in the SQL
transformation.

Explanation:

The Integration Service was unable to access the source data for the SQL transformation.

User Response:

See previous error messages for more information.

Review SQL errors in the SQLError port. The SQLError port contains the failed SQL
statements and error messages.

SQL_50071

Session failed because a connection failure occurred after the SQL transformation passed
some of the output rows downstream.

Explanation:

A database connection failure occurred while the SQL transformation was executing a
SELECT statement. Some database rows were already passed from the SQL transformation
to the pipeline. The Integration Service could not re-connect to the database and continue
processing without duplicating the output rows.

User Response:

None. Informational message.

SQL_50072

An error occurred expanding a parameter or variable in the environment SQL <connection or

transaction environment SQL> for the connection object <connection name>.

Explanation:

The SQL transformation is using a connection object that is configured with connection or
transaction SQL. The SQL contains a parameter or variable that the Integration Service
cannot resolve.

User Response:

SQL Messages

353

SR Messages

354

SR_17005

ERROR: Connect failed: SAP error message <SAP message>.

Explanation:

Connection could not be established between PowerCenter and SAP.

User Response:

Contact the SAP administrator. Also see the RFC trace file or SAP system log for more
details.

SR_17006

Unknown data transfer mode. The mode can only be staging or streaming.

Explanation:

Internal Error.

User Response:

Contact Informatica Global Customer Support.

SR_17007

ERROR: Run failed: SAP error message <ABAP program name or staging file name or
Application Source Qualifier form name> SAP <error message>.

Explanation:

The SAP system is down.

Chapter 18: S Message Codes

User Response:

Contact the SAP system administrator.

SR_17015

Could not delete the Staging File <file name>: <SAP message>.

Explanation:

You accessed the staging file through NFS mount, and the Integration Service user may not
have write permission on the staging file or directory.

User Response:

Get write permissions from the system administrator for the Integration Service user.

SR_17016

The program <program name> was generated but not installed for mapping <mapping name>
version <version number>.

Explanation:

You generated an ABAP program for this mapping, but you did not install it on the SAP
system.

User Response:

Open the Generate and Install dialog box in the Mapping Designer and install the ABAP
program for the mapping.

SR_17020

Memory allocation for tree <tree name> failed.

Explanation:

Insufficient heap memory allocation.

User Response:

Reduce the number of processes running, or increase the virtual memory on the Integration
Service host.

SR_17021

ERROR in getting information for SetId <SetID name> and Table Name <table name>.

Explanation:

You might have transported the ABAP program to a system that contains different hierarchy
and/or master table information.

User Response:

Verify the SAP source matches the definition in the repository.

Explanation:

RFC error.

User Response:

Contact the SAP administrator.

SR_17022

No hierarchy data found for <hierarchy name>.

Explanation:

The leaf nodes of the hierarchy are empty. There are no key values.

User Response:

Verify the hierarchy from which you are trying to extract.

The pmlocale.bin file is missing or does not have the code page ID you selected in the
database connection.

User Response:

Verify the existence of the pmlocale.bin file and the code page information.

SR_17058

Unable to create a locale from code page <code page> <code page ID>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

Chapter 18: S Message Codes

SR_17059

SAP Code page: <code page ID> is not compatible with the user selected code page <code
page>.

Explanation:

The PowerCenter Client or Integration Service cannot communicate with the SAP system.

SR Messages

357

358

User Response:

See the additional error message for more information. Also see the SAP trace file for more
information.

SR_17069

RFC registered server was cancelled.

Explanation:

The PowerCenter Client or Integration Service cannot communicate with the SAP system.

User Response:

See the additional error message for more information. Also see the SAP trace file for more
information.

SR_17073

No program was generated as mapping contains only SAP Information Hierarchies.

Explanation:

You generated a program for a mapping that has an SAP table reader source of type
hierarchy.

User Response:

You do not need to generate a program if the mapping has an SAP table reader source that
is of type hierarchy.

SR_17090

The Application Source Qualifier <Application Source Qualifier name> has invalid user
defined query <query> with character error at <number> location.

Explanation:

You entered a query containing characters that are not valid in the source database
connection code page.

User Response:

Change the query to contain characters in the source database connection code page.

SR_17091

The Application Source Qualifier <Application Source Qualifier name> has invalid filter clause
<filter> with character error at <number> location.

Explanation:

You entered a filter condition containing characters that are not valid with the source
database connection code page.

User Response:

Change the filter condition to contain characters included in the source database connection
code page.

SR_17092

The Application Source Qualifier <Application Source Qualifier name> has invalid join and/or
filter override <join override> with character error at <number> location.

Explanation:

You entered a join condition and/or a source filter condition that contain characters that are
not valid in the source database connection code page.

User Response:

Change either the join, filter, or both conditions to contain characters in the source database
connection code page.

SR_17138

Explanation:

You defined a partition key for a port in the Application Source Qualifier that you deleted.

User Response:

Edit the session to remove the partition key from the Application Source Qualifier. Then save
the new partition information in the session and run again.

SR_17156

Error: The filter expression is missing a source or a list of sources or a source field for which
this expression is specified.

Explanation:

You entered a wrong syntax for the filter expression.

User Response:

Enter the filter expression using the proper syntax.

Delete the table level filter in the field level filter expression.

SR_17163

Current server data movement mode is <mode> and SAP system mode is <mode>. To extract
data from Unicode enabled SAP system, server must be run in <mode> mode.

Explanation:

The SAP system is Unicode data-enabled, but the Integration Service is running in ASCII
data movement mode.

User Response:

Change the data movement mode of the Integration Service to Unicode.

SR_17171

The Integration Service could not open the SFTP connection.

Explanation:

The Integration Service could not connect to the remote SFTP server. The user name or
password might be invalid.

User Response:

See the additional error message for more information.

SR Messages

359

CHAPTER 19

T Message Codes
This chapter includes the following topics:
TE Messages, 360
TIB Messages, 362
TM Messages, 373
TPTRD Messages, 384
TPTWR Messages, 390
TT Messages, 403

TE Messages

360

TE_7102

Initialization error. Failed to get the last saved time for mapping <mapping name>.

Explanation:

The repository database server could not provide the last saved time of the mapping. A
previous problem with the database might have caused some data inconsistencies.

User Response:

Contact Informatica Global Customer Support.

TE_7104

An error occurred while creating group <group number> of target <target name>.

Explanation:

During session initialization, the Integration Service failed to create a group object.

User Response:

Review the session log for related messages.

TE_7105

An error occurred while creating transformation <transformation name>.

Explanation:

During session initialization, the Integration Service failed to create a transformation object.

User Response:

Review the session log for related messages.

TE_7106

Failed to allocate or initialize the group ID <group ID> for target <target name>.

Explanation:

During session initialization, the Integration Service failed to create an XML group ID.

User Response:

Check the previous message in the session log for more information.

User Response:

Use a source-based commit, disable flush latency, or enable forced EOQ.

TE_7131

The transformation <transformation> is not configured to propagate transactions. The

session cannot run in real time.

Explanation:

You configured real-time flush latency in the session or through the FlushLatency(n) filter
condition for WebSphere MQ. The mapping configuration prevents the session from being
run in real time.

User Response:

Disable flush latency, or verify that the mapping does not contain any real-time limitations.

TE_7133

The master input for the unsorted Joiner transformation <transformation name> cannot be
partitioned because the Joiner transformation is not a partition point.

Explanation:

You partitioned the master pipeline without adding a partition point at the unsorted Joiner
transformation. This can cause input rows from the same key value to be routed to different
partitions.

User Response:

Add a hash auto-keys partition point at the Joiner transformation to ensure data of the same
key value is routed to the same partition.

TE_7134

Warning. The master input for the sorted Joiner transformation <transformation name> is
partitioned.

Explanation:

You partitioned the master pipeline, which contains a sorted Joiner transformation. If you did
not group the sorted data before passing it to the Joiner transformation, you can get
unexpected results.

User Response:

Verify that the partitions in the master pipeline are configured to pass sorted and grouped
data to the sorted Joiner transformation.

TE_7135

You cannot recover a session when the target load group has multiple sources, and at least
one source is a real-time source. The source names are <source names>.

Explanation:

You tried to recover a session that contains one target load order group with multiple
sources, and one or more of those sources is a real-time source. The real-time sources in the
target load order group are connected to a multiple input group transformation or target.

TE Messages

361

User Response:

If the sources are connected to a Joiner transformation, you can enable the backward
compatibility flag. The backward compatibility flag allows the Integration Service to read
sources connected to a Joiner transformation sequentially as it did in versions prior to 6.x.
If the sources in the target load order group are connected to a multiple input group other
than the Joiner transformation, disable session recovery.

TIB Messages
TIB_34001

Cannot get connection property <connection property>.

Explanation:

Internal error. The PowerCenter repository contains inconsistencies.

User Response:

Contact Informatica Global Customer Support.

TIB_34002

Invalid subject <subject>.

Explanation:

The Subject attribute in the application connection for TIBCO sources and targets is invalid.

User Response:

Enter a valid subject name for the Subject attribute in the application connection for the
TIBCO source or target.

Explanation:

The ReplySubject value in the session properties is invalid.

User Response:

Enter a valid reply subject name for the ReplySubject property in the session properties.

Explanation:

A TIBCO target message contains an invalid subject.

User Response:

Verify that the value for the subject for TIBCO target messages is valid. For more information
about subject names, see the TIBCO documentation.

User Response:

Enter a valid CM name.

Modify the mapping to include datatypes that are compatible.

TIB_34026

Data overflow happened when trying to insert value <value> into field of type <datatype>.

Explanation:

The Integration Service could not pass all the data from one column to another. The specified
value is too large for the column with the specified datatype.

User Response:

Modify the datatype for the column in the mapping.

TIB_34027

Invalid date.

Explanation:

The date value for the column is invalid.

User Response:

Check the data. Make sure the data contains valid values for the date.

TIB_34028

Data overflow.

Explanation:

The Integration Service failed to initialize the session. The proper TIB/Rendezvous libraries
are not installed.

User Response:

Check the PowerExchange for TIBCO installation. Verify that TIB/Rendezvous is properly
installed.

TIB_35001

TIBCO reader cannot get connection reference for the source qualifier instance <Source
Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

366

TIB_35021

TIBCO reader failed to connect to TIBCO.

Explanation:

The Integration Service encountered an error connecting to TIBCO. The application

connection attributes for the TIBCO source might be invalid.

User Response:

Verify the application connection attributes for the TIBCO source.

Explanation:

The network may be down.

User Response:

Verify the network connection.

TIB_35022

Reader partition <partition> failed to close checkpoint at EOF: <error message>.

Explanation:

The Integration Service could not commit messages to the target when it reached the session
condition(s) you specified in the session properties. The session failed.

User Response:

Check the additional error message for more information.

TIB_35024

Fatal error occurred while fetching TIBCO messages.

Explanation:

The Integration Service encountered an error getting reading from TIBCO. There is a TIB/
Rendezvous error.

Chapter 19: T Message Codes

User Response:

Check the additional error message for more information.

TIB_35025

Reader partition <partition> failed to close checkpoint at real-time flush point: <error
message>.

Explanation:

This is an informational message. You did not configure the session to run in real time.

User Response:

If you want to run the session in real time, you must configure the session properties for realtime data extraction.

TIB_35030

TIBCO reader cannot get source property <property> for the source qualifier instance
<Source Qualifier name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TIB_35031

TIBCO reader cannot get the source qualifier instances from the mapping.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TIB_35033

TIBCO reader failed to support recovery for the source qualifier instance <Source Qualifier
name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TIB_35037

Reader partition <partition> failed to read cached message.

Explanation:

The Integration Service could not read the cached message. The cache might contain
inconsistencies.

User Response:

Check the additional error message for more information.

TIB_35039

The source qualifier instance <Source Qualifier name> contains the datatype msg, which is
incompatible with a TIB/Adapter SDK connection.

Explanation:

A field in the source definition contains the datatype msg. This datatype is incompatible with
the TIB/Adapter SDK application connection. As a result, the session failed.

TIB Messages

367

368

User Response:

Remove any fields in the source definition with the datatype msg. To include the message
metadata in this field, add the metadata as separate columns in the source definition.

TIB_35040

The source qualifier instance <Source Qualifier name> contains the header field Time Limit,
which is incompatible with a TIB/Adapter SDK connection.

Explanation:

You attempted to run a session with a TIB/Adapter SDK application connection for the
specified Source Qualifier transformation. However, the TIBCO source definition associated
with the Source Qualifier contains the field Time Limit. As a result, the session failed.

User Response:

Remove the Time Limit field from the source definition.

TIB_36001

Tibrv driver failed to connect to TIB/Rendezvous.

Explanation:

The Integration Service cannot connect to TIB/Rendezvous. The application connection

attributes for the TIBCO source or target may be invalid.

User Response:

Verify the application connection attributes for the TIBCO source or target.

Explanation:

The network may be down.

User Response:

Increase the system memory. Change the queue limit policy in the session properties.

TIB_36021

TIB/Rendezvous license will expire or has already expired on <date>.

Explanation:

The TIB/Rendezvous license expires soon or expired on the specified date.

User Response:

See the TIBCO documentation for instructions to correct the error.

TIB_36022

Tibrv driver failed to get confirmation for the message with sequence number <number>.

Explanation:

The Integration Service did not receive confirmation for the specified message. If the time
limit expired, the message may have been deleted. PowerCenter may not know if the
message reached the subscriber.

TIB Messages

369

370

User Response:

Change the time limit policy in the session properties. Verify that the subscriber is running.

TIB_36023

CmName conflicts: <TIBCO error message>.

Explanation:

Two subscribers or publishers on the same network have the same CmName. Each
application must use a unique CmName.

User Response:

Verify that each application on the network uses a unique CmName. See the TIBCO
documentation for instructions to correct the error.

TIB_36036

Tibrv driver failed to get message sequence number: <TIBCO error messages>.

Explanation:

You passed invalid data to a column with the datatype msg. The Integration Service rejected
the row.

User Response:

See the TIBCO documentation for information about fixing the error.

TIB_36058

Failed to get the number of fields in a TIB/Rendezvous message: <TIBCO error message>.

Explanation:

The Integration Service encountered an error while trying to determine the number of fields in
the TIB/Rendezvous message.

User Response:

See the TIBCO documentation for information about fixing the error.

TIB_37001

Tibsdk driver failed to connect.

Explanation:

The Integration Service could not start the session.

User Response:

Check the additional error message for more information.

TIB_37006

Tibsdk driver failed to create the publisher: <TIBCO error message>.

Explanation:

The Integration Service could not initialize the session.

The Integration Service could not read a TIBCO message in AE wire format. The session
failed.

User Response:

See the TIBCO documentation for information on fixing the error.

TIB_37011

Tibsdk driver failed to start adapter instance <adapter instance>: <TIBCO error message>.

Explanation:

The Integration Service could not start the specified adapter instance. As a result, the
Integration Service could not initialize the session.

User Response:

See the TIBCO documentation for information on fixing the error.

TIB_37012

Tibsdk driver failed to pre-register a listener <pre-registered listener>: <TIBCO error

message>.

Explanation:

The Integration Service could not initialize the session.

User Response:

Check the additional error message for more information.

TIB Messages

371

372

TIB_37027

Tibsdk driver failed to read a cached message: <error message>.

Explanation:

The Integration Service could not a read a cached message during a recovery session.

User Response:

Check the additional error message for more information.

TIB_37028

Invalid session communication protocol. Must be either RV or RVCM.

Explanation:

The session protocol for the TIB/Repository session you specified is invalid. The protocol
must be RV or RVCM.

User Response:

Set RV or RVCM as the session protocol in TIB/Adapter Administrator. For more information,
see the TIBCO documentation.

TIB_38000

TIBCO writer failed to insert null value into field <field>, which can't take a null value.

Explanation:

You selected Not Null for the specified field in the target properties.

User Response:

From the Columns tab of the Edit Table properties for the target definition, clear the Not Null
option for the field.

TIB_38001

TIBCO writer failed to initialize writer properties for the target instance <target>: <error
message>.

Explanation:

The Integration Service could not initialize the writer properties for the specified target. The
session failed.

User Response:

Check the additional error message for more information.

TIB_38002

TIBCO writer failed to initialize connection properties for the target instance <target>: <error
message>.

Explanation:

An attribute in the application connection for the TIBCO target is invalid. The session failed.

User Response:

Check the additional error message for more information.

TIB_38003

TIBCO writer can't get connection information for the target instance <target>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TIB_38004

TIBCO writer initialization failed for the target instance <target>: <error message>.

Explanation:

The Integration Service could not initialize the target. The session failed.

User Response:

Check the additional error message for more information.

TIB_38007

TIBCO writer rejected the row because of the overflow error for field <field>.

Explanation:

Row error. Data overflow occurred in the specified field.

User Response:

Use a larger datatype for the output field. For example, use int64 instead of int32.

TIB_38008

Data was truncated for field <field>.

Explanation:

This is a warning message. The data for a string field was truncated.

User Response:

Increase the precision of the output field.

TIB_38009

TIBCO writer failed to get error threshold value.

Explanation:

Internal error. The repository may contain inconsistencies.

Chapter 19: T Message Codes

User Response:

Contact Informatica Global Customer Support.

TIB_38010

SendSubject field cannot be connected when pre-registered listeners are specified for the
writer.

Explanation:

The session properties contain pre-registered listeners for a TIBCO target. Also, the mapping
contains a link to the SendSubject port in the target definition. This is not allowed.

User Response:

Remove the link to the SendSubject port in the target definition to use the default subject.
Remove the pre-registered listeners you specified in the session properties.

TIB_38012

The target instance contains the datatype msg, which is incompatible with a TIB/Adapter SDK
connection.

Explanation:

A field in the target definition contains the datatype msg. This datatype is incompatible with
the TIB/Adapter SDK application connection. As a result, the session failed.

User Response:

Remove any fields in the source definition with the datatype msg. To include the message
metadata in this field, add the metadata as separate columns in the target definition.

TIB_38013

Target instance contains the header field Time Limit, which is incompatible with a TIB/Adapter
SDK connection.

Explanation:

You attempted to run a session with a TIB/Adapter SDK application connection for a TIBCO
target. However, the TIBCO target definition contains the port Time Limit, which is linked with
the Time Limit port in another transformation. As a result, the session failed.

User Response:

Remove the link to the Time Limit port in the target definition.

TIB_38014

Target instance contains the datatype ipaddr32 or ipport16, which is incompatible with a TIB/
Adapter SDK connection.

Explanation:

You selected a TIB/Adapter SDK application connection for a TIBCO target. However, the
TIBCO target definition contains fields with the datatypes ipaddr32 and/or ipport16. This is
not allowed.

User Response:

Use the datatype string for fields with ipaddr32 or ipport16 datatypes.

TM Messages
TM_6004

There was an error connecting to the repository.

Explanation:

The Integration Service failed to connect to the repository.

User Response:

Verify that the Repository Service is running.

TM_6018

The session completed with <number> row transformation errors.

User Response:

Review the session log for related messages.

TM_6059

An error occurred updating the Sequence Generator transformation <transformation name>

to the repository.

User Response:

Review the Repository Service logs for more information about the error.

Explanation:

Internal error.

TM Messages

373

374

User Response:

Check the syntax of the stored procedure. Test the stored procedure in the database. Then
run the session again.

Chapter 19: T Message Codes

TM_6159

An error occurred executing stored procedure.

Explanation:

The context for executing the stored procedure might be invalid.

User Response:

Review the session log for related messages. Verify the stored procedure in the database.
Check the database error messages for further explanations.

TM_6186

The stored procedure call text <call text> contains one or more characters that are not valid in
the code page of the stored procedure database connection. The invalid character starts at
position <character position> of the query.

Explanation:

The stored procedure call text for a pre-target or post-target stored procedure contains one or
more characters that are not in the character set of the stored procedure database code page.

User Response:

Identify the invalid character referenced in the session log. Edit the call text so that the stored
procedure call text contains characters encoded in the character sets of both the Integration
Service code page and the stored procedure database code page.
Configure the stored procedure database to use a code page that contains encoding for the
store procedure data character set and is compatible with the Integration Service code page.

Explanation:

The stored procedure database uses a code page that is not supported by PowerCenter.

User Response:

Select a code page for the stored procedure database that is supported by PowerCenter and
contains encoding for the stored procedure database character set.

TM_6188

The session sort order <sort order name> is incompatible with the Integration Service code
page <code page name>.

Explanation:

The specified sort order is incompatible with the Integration Service code page.

User Response:

To validate code pages, select a sort order compatible with the Integration Service code
page. To relax code page validation, configure the Integration Service to relax code page
validation in Unicode data movement mode.

TM_6190

Cannot identify the unique relational connection or application connection that is used as
$Source or $Target for a Lookup or Stored Procedure transformation.

Explanation:

The Lookup or Stored Procedure transformation is configured with the $Source or $Target
variable. The mapping has more than one relational source or relational target database
connection.

User Response:

In the session properties, enter a database connection for the $Source or $Target connection.

TM_6193

An error occurred expanding the connection parameter <parameter name>.

Explanation:

A session parameter, such as $DBConnectionName, was used to define a session

connection. In the parameter file, the session parameter value does not match the name of
one of the connection objects in the Workflow Manager.

User Response:

Update the session parameter value in the parameter file so that it matches the name of a
connection object in the Workflow Manager. Make sure that the session parameter type
matches the connection object type. For example, use $FTPConnectionName to define an
FTP connection, not a queue connection.

TM_6200

The session log path exceeds limits of <session log path limit> characters <session log path>.

User Response:

Enter a session log path that is within the session log path limit. You may need to specify a
different directory or shorten the length of the name of the log file.

TM Messages

375

376

TM_6202

DTM event. There was an error incrementing the log file number in the repository.

Explanation:

The repository was unable to update the log file number in the database.

User Response:

Verify that the database server and Repository Service are running.

Explanation:

There is not enough available virtual memory.

User Response:

Increase the amount of available virtual memory on the Integration Service system.

Chapter 19: T Message Codes

TM_6289

Aborting the DTM process due to memory allocation failure.

Explanation:

The Integration Service requires more memory.

User Response:

Increase the amount of available virtual memory on the Integration Service system.

TM_6294

The target load order has been changed. Revalidate the mapping <mapping name>.

Explanation:

If a mapplet associated with a mapping is changed in such a way that the target load order
for the mapplet changes after you saved the mapping, the Integration Service cannot run the
session.

User Response:

Open the mapping and save it.

TM_6316

Error: <database error message> setting up <table name> table.

Explanation:

The user name specified in the target database connection does not have table creation
privileges on the target database.

User Response:

Grant table creation privileges to the database user name specified in the target database
connection.

Explanation:

The Integration Service could not create the recovery table due to a database error.

User Response:

Check the database error message to determine the cause of the error, and contact the
database administrator.

TM_6317

The following database error occurred creating the recovery table <table name>: <database
error message>.

Explanation:

The user name specified in the target database connection does not have table creation
privileges on the target database.

User Response:

Grant table creation privileges to the database user name specified in the target database
connection.

Explanation:

The Integration Service could not create the recovery table due to a database error.

User Response:

Check the database error message to determine the cause of the error, and contact the
database administrator.

TM_6318

The following database error occurred when preparing to fetch the target run ID from the
recovery table <table name>: <database error message>.

Explanation:

The Integration Service could not retrieve information from the recovery table due to a
database error.

User Response:

Check the database error message to determine the cause of the error, and contact the
database administrator.

TM_6319

The following database error occurred when fetching the target run ID from the recovery table
<table name>: <database error message>.

Explanation:

The user name specified in the target database connection does not have permission to
select information from the target database.

User Response:

Grant select privileges to the user name specified in the target database connection.

Explanation:

The Integration Service could not retrieve information from the recovery table due to a
database error.

TM Messages

377

378

User Response:

Check the database error message to determine the cause of the error, and contact the
database administrator.

TM_6320

The following database error occurred when inserting the target run ID into the recovery table
<table name>:<database error message>.

Explanation:

The user name specified in the target database connection does not have permission to
insert information into the PM_RECOVERY recovery table.

User Response:

Grant the database user name specified in the target database connection permission to
insert data into the PM_RECOVERY recovery table.

Explanation:

The Integration Service could not insert information into PM_RECOVERY due to a database
error.

User Response:

Check the database error message for the cause of the error, and contact the database
administrator.

TM_6321

The recovery table format is in version <version number>, while version 6.2 is expected.

Explanation:

The Integration Service cannot perform recovery because the recovery tables are not
correctly formatted.

User Response:

If you created the recovery tables manually, review the format and correct any error. You may
want to allow the Integration Service to create the tables. Grant table creation privileges to
the user name specified in the target database connection.

TM_6322

The following error occurred when generating a sequence ID: <database error message>.

Explanation:

The Integration Service could not initialize the PM_TGT_RUN_ID recovery table.

User Response:

Query the PM_RECOVERY recovery table for the maximum value in the TGT_RUN_ID
column. Insert this value into PM_TGT_RUN_ID.

TM_6323

The following database error occurred when committing the new sequence ID to the
database: <database error message>.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6324

The following database error occurred when preparing the UPDATE recovery statement:
<database error message>.

Explanation:

The user specified in the target database connection does not have permission to access the
recovery tables.

User Response:

Grant permission to access the recovery tables to the user name specified in the target
database connection.

Explanation:

The Integration Service could not access the recovery tables due to a database error.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6325

The following database error occurred when updating recovery information for the recovery
table <table name>: <database error>.

Explanation:

The user name specified in the target database connection does not have permission to
update the recovery table.

Chapter 19: T Message Codes

User Response:

Grant permission to access the recovery tables to the user name specified in the target
database connection.

Explanation:

The Integration Service could not update the recovery table due to a database error.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6326

The following database error occurred when deleting recovery information from the recovery
table <table name>: <database error message>.

Explanation:

The user name specified in the target database connection does not have permission to
delete information from the recovery table.

User Response:

Grant permission to delete information from the recovery tables to the user name specified in
the target database connection.

Explanation:

The Integration Service could not delete information from the recovery table due to a
database error.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6327

The following database error occurred when resetting recovery information for the recovery
table <table name>: <database error message>.

Explanation:

The user specified in the target database connection does not have permission to reset
information in the recovery table.

User Response:

Grant permission to access, insert, and delete information in the recovery tables to the
database user name specified in the target database connection.

Explanation:

The Integration Service could not reset information in the recovery table due to a database
error.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6328

The following database error occurred when fetching the partition count from the recovery
table <table name>: <database error message>.

Explanation:

The user specified in the target database connection does not have permission to access the
recovery table.

User Response:

Grant permission to access the recovery tables to the user name specified in the target
database connection.

Explanation:

The Integration Service could not access the recovery table due to a database error.

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6329

The following database error occurred when fetching recovery information from the recovery
table <table name>: <database error message>.

Explanation:

The user specified in the target database connection does not have permission to access the
recovery table.

User Response:

Grant permission to access the recovery tables to the user name specified in the target
database connection.

Explanation:

The Integration Service could not access the recovery table due to a database error.

TM Messages

379

User Response:

Check the database error message for the cause of the error and contact the database
administrator.

TM_6330

An error occurred retrieving recovery information from the target database.

User Response:

Verify that the recovery tables exist on the target database. Review the session log for
related messages.

TM_6331

An error occurred initializing recovery for target <target table>.

User Response:

Verify that the recovery tables exist on the target database. Review the session log for
related messages. Verify that the database user name specified in the target database
connection has permission to create, access, and update the recovery tables.

TM_6332

An error occurred deleting information from the recovery tables for the target <target>.

User Response:

Verify that the recovery tables exist on the target database. Check previous error messages
for possible causes of the error. Verify that the database user name specified in the target
database connection has permission to create, access, and update the recovery tables.

TM_6336

An error occurred initializing the recovery session because the recovery information for the
target <target> was not found.

User Response:

Verify that the recovery tables exist on the target database. If the tables do not exist, you
must run the session again normally with recovery enabled to create the tables and insert
recovery information into them. You can also manually create the recovery tables and then
run the session normally to create recovery information.
If the recovery tables exist, run the session normally to create recovery information. Do not
drop the recovery tables while the session is enabled for recovery.

380

TM_6341

A database error occurred updating the recovery tables. The session updated <number of
records> recovery records but expected to update one row.

User Response:

Check the database error message log for possible causes of the error, and contact the
database administrator.

TM_6342

An error occurred updating information in the recovery tables for the target <target name>.

User Response:

Review the session log for related messages. Verify that the recovery tables exist on the
target database and that the user name specified in the target database connection has
permission to update the tables.

TM_6343

Session recovery is not possible because the session is not enabled for recovery.

User Response:

Enable the session for recovery. While enabled for recovery, the session must run normally
and fail before you can perform recovery.

TM_6345

The connection object <connection name> is not a valid database partition connection type.

Explanation:

The Integration Service failed the session because it cannot load to the target type using
database partitioning.

User Response:

Use pass-through partitioning for targets that do not support database partitioning.

TM_6349

Session recovery is not possible because the session is also configured to perform a test
load.

User Response:

To perform recovery, disable test load in the session properties.

Chapter 19: T Message Codes

TM_6376

The Integration Service failed while processing the recovery file.

User Response:

Restart the session. If the problem persists, contact Informatica Global Customer Support.

TM_6687

The DTM buffer size specified <DTM buffer size> exceeds the 32-bit address space. It cannot
be more than <number> on a 32-bit Integration Service.

Explanation:

You tried to run a session on a 32-bit Integration Service, but the DTM buffer size is too large.

User Response:

Decrease the DTM buffer size or run the session on a 64-bit Integration Service.

TM_6698

An error was encountered loading library: <reason for failure>.

Explanation:

The Integration Service failed to load the external session log library, possibly because of
missing or invalid .dll files.

User Response:

Take necessary action to correct the error.

TM_6700

The following error was encountered accessing the file <file name> for error logging: <error
message>.

Explanation:

The Integration Service could not access the specified file. The user running the Integration
Service does not have permission to read or write to the specified file for error logging.

User Response:

Review the error message, and check the permissions on the specified file.

TM_6701

Warning. The flat file delimiter <delimiter> is the same as the data column delimiter for error
logging. You may find it difficult to read the error log.

User Response:

Update the session to use a different data column delimiter for error logging.

TM_6712

Concurrent sources with the same transactional requirements must have the same number of
partitions. The number of partitions between transformation instance <transformation
instance name> and <transformation instance name> are different.

Explanation:

The session ran in change or real-time mode, but the number of partitions for the specified
transformation instances differ. Transformation instances must have the same number of
partitions.

User Response:

Configure the transformation instances to have the same number of partitions.

TM_6713

Concurrent sources with the same transactional requirements must have consecutive
execution order.

Explanation:

When a session runs in change or real-time mode, the execution of the target load order
groups must be consecutive.

User Response:

To ensure consecutive execution of target load order groups, set the target load order in the
Designer.

TM_6765

The Debugger cannot run a session on a grid.

User Response:

Disable session on grid, or debug the mapping in the Designer.

TM_6772

The worker DTM running partition group <partition group ID> failed to connect to the master
DTM at <host name and port number of master DTM process> with the timeout of <timeout
value> seconds.

Explanation:

The worker DTM could not connect to the master DTM in the specified timeout period. The
master DTM process may have shut down unexpectedly, or there may be a network failure.

TM Messages

381

382

User Response:

Contact the network administrator to verify that the network does not have connectivity
issues. Contact the PowerCenter domain administrator to verify that the Integration Service is
running.

TM_6775

The master DTM process was unable to connect to the master service process to update the
session status with the following message: error message <error message text> and error
code <error code>.

Explanation:

The master DTM process was unable to connect to the master service process to update the
session status. The master DTM process may have shut down unexpectedly, or there may be
a network failure.

User Response:

Contact the network administrator to verify that the network does not have connectivity
issues. Contact the PowerCenter domain administrator to verify that the Integration Service is
running.

TM_6777

Temporary profiling sessions cannot be grid-enabled.

User Response:

Create a persistent profile session, or run the temporary profile session on an Integration
Service that is not assigned to a grid.

TM_6788

Error: Unable to open temporary log file <log file name> with error <error code>. The session
log will not be attached to post-session email.

Explanation:

The Integration Service attempted to create a log file in the PowerCenter Services installation
directory but was unable to access the directory. The Integration Service could not attach the
session log to the post-session email because it could not create the file in the specified
directory.

User Response:

Verify that the PowerCenter Services user has write permission for the PowerCenter Services
installation directory.

TM_6795

The Repository Service marked the session as impacted, and the Integration Service is not
configured to run impacted sessions.

User Response:

Validate the session or configure the Integration Service to run impacted sessions.

TM_6796

An error occurred expanding the owner name <owner name> for the transformation
<transformation name>.

Explanation:

The Integration Service cannot expand a parameter or variable in the table owner name or
table name prefix.

User Response:

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TM_6797

An error occurred expanding a parameter or variable in the environment SQL <SQL text> for
the connection object <connection name>.

User Response:

Explanation:

Internal error.

Chapter 19: T Message Codes

User Response:

Contact Informatica Global Customer Support.

TM_6798

An error occurred expanding a parameter or variable in the table name prefix <prefix> for
error logs.

User Response:

Explanation:

The variable is assigned in both a pre-session variable assignment statement and in a

parameter file. The Integration Service uses the value in the parameter file.

User Response:

To use the value in the pre-session variable assignment statement, remove the variable from
the parameter file. Or, configure the session and workflow so that they do not run with a
parameter file.

TM_6845

The parent workflow or worklet variable <variable name> listed in a pre-session variable
assignment statement cannot be found. The variable assignment will be ignored.

User Response:

Verify that the variable has not been deleted or renamed.

TM_6848

Unable to resolve variable <variable name> as a user-defined workflow or worklet variable.

User Response:

Verify that the variable has not been deleted or renamed.

TM_6849

Unable to resolve variable <variable name> as a mapping parameter, mapping variable,

session parameter or predefined variable.

User Response:

Verify that the variable has not been deleted or renamed.

TM_6850

An error was encountered setting the value from variable <variable name> to value for
variable <variable name>.

Explanation:

The session contains a pre- or post-session variable assignment statement, but the
Integration Service could not perform the variable assignment.

User Response:

Verify that the parameters or variables in the assignment statement exist and that the names
are spelled correctly.

TM Messages

383

TM_6851

An error was encountered performing the post-session variable assignment.

User Response:

Verify that the parameters or variables in the assignment statement exist and that the names
are spelled correctly.

TM_6956

An error was encountered starting a new workflow instance because the number of workflow
instances is at the configured limit.

User Response:

Start the workflow instance after one of the instances completes running.

TM_6957

The workflow failed because it persists the same mapping variables as another workflow
instance that is running concurrently.

User Response:

To persist mapping variables for concurrent workflows, configure different workflow instance
names and parameters.

TM_6958

The workflow failed to start because a workflow with the same instance name is already
running.

User Response:

Verify that the workflow is enabled to run concurrently. Configure unique instance names for
each workflow, or enable the workflow to run concurrently without unique instance names.

TPTRD Messages

384

TPTRD_11001

Plug-in failed to create the TPTLogging class object.

Explanation:

The system does not have enough memory to allocate to the logging object.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

Explanation:

The schema defined in the mapping is incorrect.

User Response:

Validate or re-create the mapping. Verify that the column names, precision, and scale are the
same as the table definition.

TPTRD Messages

385

TPTRD_21211

Plug-in failed to Initiate Teradata database connection.

TPTRD_21215

Plug-in failed to fetch data on row <row number> with status <status code>.

Explanation:

GetRow() call failed on the row <row number>.

User Response:

Contact Informatica Global Customer Support.

TPTRD_21220

Invalid TDPID.

Explanation:

Invalid host name.

User Response:

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTRD_21506

Plug-in failed to build DML statement.

Explanation:

The PowerCenter Integration Service could not create the DML statement for data extraction.

User Response:

Verify that the custom SQL is correct.

Verify that field names and table names are same as in the Teradata table definition.

TPTRD_21507

Plug-in failed to create TPTAPI class instance.

Explanation:

The system does not have enough memory to allocate to the Teradata PT API object.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

TPTRD_21508

Plug-in failed to create connection to Teradata database.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTRD Messages

387

388

TPTRD_21509

Plug-in failed to read data from table <table name> of Teradata database.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTRD_21517

Plug-in failed to retrieve source extension attached with particular source qualifier.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTRD_21518

Plug-in failed to retrieve connection reference associated with particular partition.

Explanation:

Contact Informatica Global Customer Support.

TPTRD_21529

Number of Max Sessions must be greater than 0.

Explanation:

The Max Sessions attribute for a Teradata PT connection object is set to an illegal value.

TPTRD Messages

389

User Response:

Update the Max Sessions attribute and then restart the session.

TPTRD_21530

Sleep must be greater than 0.

Explanation:

The Number of Sorted Ports attribute in the Teradata PT source properties exceeds the
number of output fields.

User Response:

Update the Number of Sorted Ports for the Teradata source and then restart the session.

TPTRD_35061

The following system error occurred when the PowerCenter Integration Service tried to get
the values of some session attributes: <error message>.

Explanation:

The PowerCenter Integration Service could not get the values of some session-level
properties. A system error might have occurred or the repository might have inconsistencies.

User Response:

Fix the operating system error. Contact Informatica Global Customer Support.

TPTWR Messages

390

TPTWR_11001

Plug-in failed to create the TPTLogging class object.

Explanation:

The system does not have enough memory to allocate to the logging object.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

TPTWR_11002

Plug-in failed to convert Code Page to Unicode.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTWR_11003

Plug-in failed to convert Unicode to Code Page.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

Explanation:

The system does not have enough memory to allocate to the delete DML statement.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

TPTWR_31217

Plug-in failed to set Truncate Table DML Statement.

Explanation:

The system does not have enough memory to allocate to the TRUNCATE TABLE statement.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

Chapter 19: T Message Codes

TPTWR_31218

Plug-in failed to create Teradata database connection object.

Explanation:

The system does not have enough memory to allocate to the Teradata Parallel Transporter
connection object.

The PowerCenter Integration Service cannot commit the connection object.

User Response:

Check the DBS/CLI error message for more information.

TPTWR_31226

Plug-in failed in End Acquisition.

Explanation:

The PowerCenter Integration Service failed in end acquisition.

User Response:

Check the DBS/CLI error message for more information.

TPTWR Messages

393

394

TPTWR_31227

Plug-in failed to Apply rows.

Explanation:

The PowerCenter Integration Service cannot apply rows.

User Response:

Check the DBS/CLI error message for more information.

TPTWR_31228

Plug-in failed to set DML Group <DML group name> to connection object.

Explanation:

DML group built is invalid.

Chapter 19: T Message Codes

User Response:

Drop the error and log tables if they exist in database, and restart the session.

TPTWR_31237

Plug-in failed to set Update Recovery_Table DML Statement.

Explanation:

Internal error.

TPTWR Messages

395

396

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

TPTWR_31403

Plug-in failed to retrieve Group list.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTWR_31603

Plug-in failed to retrieve Teradata Parallel Transporter connection and session level attributes.

Explanation:

Connection object has some invalid parameters.

User Response:

Check whether all attributes in the connection object are correct.

TPTWR_31604

Plug-in failed to retrieve table information.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

TPTWR_31605

Plug-in failed to build DML statements on table <table name> for system operator <system
operator name>.

Explanation:

Explanation:

The system does not have enough memory to allocate to the Delete DML statement.
The PowerCenter Integration Service cannot read target table information from vector.

User Response:

Make sure that there is enough memory on the machine where the PowerCenter Integration
Service is running.

TPTWR_31610

Primary Key is not defined for any of the fields of table <table_name>. Cannot build DELETE
DML Statement.

Explanation:

Row type is deleted and no primary key is defines in the target table.

User Response:

Define a primary key in the target table and restart the session.

TPTWR_31611

Primary key is defined for all fields of table <table_name>. Cannot build UPDATE DML
Statement.

Explanation:

The entire field in target table is primary key and no other column exists for update.

User Response:

Make sure you have at least one column for update.

TPTWR_31612

Primary Key is not defined for any of the fields of table <table_name>. Cannot build UPDATE
DML Statement.

Explanation:

Row type is update and no primary key is defined in the target table.

User Response:

Define a primary key in the target table and restart the session.

TPTWR_31613

Plug-in failed to retrieve Truncate Table attribute.

Explanation:

Explanation:

Explanation:

As system operator is LOAD and row type is Update.

TPTWR Messages

Explanation:

Explanation:

A connection error occurred when the PowerCenter Integration Service tried to delete
recovery information.

User Response:

Review the session log and Teradata PT log tables for related connection errors.

TPTWR Messages

401

402

TPTWR_34731

Acquisition failed in connection for deleting recovery information.

Explanation:

A connection error occurred when the PowerCenter Integration Service tried to delete
recovery information.

User Response:

Review the session log and Teradata PT log tables for related connection errors.

TPTWR_34732

PutRow call failed in connection for deleting recovery information.

Explanation:

A connection error occurred when the PowerCenter Integration Service tried to delete
recovery information.

User Response:

Review the session log and Teradata PT log tables for related connection errors.

TPTWR_35001

ODBC Connection failed to create INFARecoveryTable.

Explanation:

The session uses a connection object of type Teradata Parallel Transporter Connection,
which is deprecated.

User Response:

Replace the deprecated connection object with a connection object of type Teradata PT
Connection.

Chapter 19: T Message Codes

TT Messages
TT_11009

Overflow error. The Sequence Generator transformation has reached the end of the
configured end value.

User Response:

Change the end value or cycle the sequence.

TT_11013

An error occurred parsing group by ports.

Explanation:

In an Aggregator or Rank transformation, an aggregate expression is specified as a group by

port. Group by ports cannot be aggregate expressions.

User Response:

If you do not want to abort the session when the port contains an error, change the default
value.

TT_11021

An error occurred moving data from the transformation <transformation name> to the
transformation <transformation name>. The row was dropped.

User Response:

Review the session log for related messages about the row error. If you enabled row error
logging, review the error log for related messages.

TT_11023

An error occurred converting data in the port <port name>. The row was dropped.

User Response:

Review the session log for related messages about the row error. If you enabled row error
logging, review the error log for related messages.

TT_11041

Failed to initialize the transformation <transformation name>.

Explanation:

An error occurred preparing parameters for input and output ports of the transformation.

User Response:

Check the transformation input and output parameters.

TT Messages

403

404

TT_11070

The lookup override <lookup query> contains one or more characters that are not valid in the
code page of the database connection. The invalid character starts at position <character
position> in the query.

User Response:

Change the lookup override query to contain characters included in the lookup database
connection code page.

TT_11077

The lookup query <lookup query> contains one or more characters that are not valid in the
code page of the database connection. The invalid character starts at position <character
position> in the query.

Explanation:

The lookup query contains one or more characters that are not encoded in the lookup
database code page.

User Response:

Edit the lookup query so that the Integration Service can convert it from the Integration
Service code page to the lookup database code page without loss of data.

Explanation:

The lookup database uses a code page that is not supported by Informatica.

User Response:

Select a code page for the lookup database that is supported by Informatica and contains
encoding for the lookup data character set.

TT_11078

The stored procedure name <name of stored procedure> contains one or more characters
that are not valid in the code page of the database connection. The invalid character starts at
position <character position> in the name.

Explanation:

The stored procedure name contains one or more characters that are not encoded in the
stored procedure database code page.

User Response:

Identify the invalid character referenced in the session log. Edit the stored procedure name
so that the Integration Service can convert it from the Integration Service code page to the
stored procedure database code page without loss of data.

Explanation:

The stored procedure database uses a code page that is not supported by Informatica.

User Response:

Select a code page for the stored procedure database that is supported by Informatica and
contains encoding for the stored procedure data character set.

TT_11079

The field name <name of field> of stored procedure <name of stored procedure> contains one
or more characters that are not valid in the code page of the database connection. The invalid
character starts at position <character position> of the name.

Explanation:

The field name of a stored procedure contains one or more characters that are not encoded
in the stored procedure database code page.

User Response:

Identify the invalid character referenced in the session log. Edit the stored procedure field
name so that the Integration Service can convert it from the Integration Service code page to
the stored procedure database code page without loss of data.

Verify that the session and mapping properties maintain sort order between the sorted data
and the Joiner transformation.
In the mapping, verify that the columns in the join condition match the columns of the sorted
data and that the mapping does not contain active transformations between the sorted data
and the Joiner transformation.
In the session, verify that the partitioning properties maintain sort order between the sorted
data and the Joiner transformation.

TT_11118

The cache directory configured for the transformation <transformation name> is empty or not
valid.

User Response:

Specify a cache directory in the session or the transformation.

TT_11124

Warning. The number of rows output by a group of the source qualifier <transformation
name> exceeds the limit of rows <number of rows> specified in the IDN license. No more rows
will be processed on this group of the source qualifier.

Explanation:

The IDN license restricts the number of rows you can process in a group.

User Response:

Decrease the number of rows in the group or get a different license from Informatica.

TT Messages

405

TT_11134

The lookup cache file with the named prefix <prefix name> used by the Lookup
transformation <Lookup transformation name> cannot be reused.

Explanation:

You attempted to use a persistent lookup cache that was incompatible with the Lookup
transformation, and the Integration Service does not delete the lookup cache files when you
use a named prefix. The lookup cache files can be unusable for the following reasons:
If you change an attribute, such as the database connection in, the persistent cache may

become incompatible with the Lookup transformation.

If more than one session uses the same lookup cache name, the lookup cache may be

incompatible with a Lookup transformation in one of the sessions. For example, if you
modify the attributes in one session, but you do not modify the second session, the lookup
cache becomes unusable for the second session.
You upgraded the Integration Service. The format for information in the Lookup

transformation in the upgraded version of the Integration Service is incompatible with the
format of information in the cache file that was created by an earlier version of the
Integration Service.

406

User Response:

Update the Lookup transformation attributes, or remove the existing lookup cache files. You
must remove both the .idx and .dat files. This allows the Integration Service to create a
lookup cache.

TT_11141

The transformation <transformation name> returned a row error status on receiving an input
row on group <group>.

Explanation:

The Custom transformation procedure returned an error when it received a row in the
specified input group. The Custom transformation procedure returned INFA_ROWERROR in
the input row notification function.

User Response:

This is an informational message. If this is a recurring error, you may want to verify that the
data passing into the Custom transformation meets the criteria defined by the Custom
transformation procedure.

TT_11144

The cache for the Lookup transformation <transformation name> indicates that the source
type is <source type>, but the source type for this transformation is <source type>.

Explanation:

The source type for the Lookup transformation was changed after the Integration Service
saved the cache.

User Response:

Recache the lookup source, or change the source type to the previous type.

TT_11145

The cache for the Lookup transformation <transformation name> indicates that the source file
is <file name>, but the source file specified is <file name>.

Explanation:

The source file name was changed after the Integration saved the lookup cache.

User Response:

Recache the lookup source, or change the lookup file name to the previous name.

TT_11146

The cache for the Lookup transformation <transformation name> indicates that the type of
source file <source file type> does not match the one specified for the transformation.

Explanation:

The source file type in the session properties was changed after the session ran. For
example, you may have changed the source file type from direct to indirect or from indirect to
direct.

User Response:

Recache the lookup source, or change the lookup source file type in the session properties.

Chapter 19: T Message Codes

TT_11147

Lookup transformations <transformation name> and <transformation name> have the same
cache file name prefix <prefix name> but have different source files <file name> and <file
name>.

Explanation:

The cache file name prefix matches for each Lookup transformation, but the lookup sources
have different file names.

User Response:

Configure the mapping so that the cache is no longer shared, or configure the session to use
the same lookup source file.

TT_11148

The cache file name prefix for the Lookup transformations <transformation name> and
<transformation name> have the same cache file name prefix <file name prefix> but have
different source file types.

User Response:

Configure the session with the same lookup source file type for each Lookup transformation
sharing the cache.

TT_11149

The Lookup transformation <Lookup transformation name> has an illegal file name <file
name>.

Explanation:

You ran a session with a flat file lookup, and the Integration Service could not find the lookup
file. Either the file name or directory was missing or invalid.

User Response:

In the session properties, verify the file name and directory of the lookup file source.

TT_11152

An error occurred processing the Normalizer transformation <transformation name>.

Explanation:

The mapping connects an active transformation and a passive transformation to the same
downstream transformation or transformation input group.

User Response:

Remove the concatenation.

TT_11158

An error occurred reading the lookup source for the Lookup transformation <transformation
name>.

Explanation:

The Integration Service encountered errors while reading the lookup source.

User Response:

Review the session log for related messages.

TT_11161

An error occurred reading the lookup source for the transformation <transformation name>. It
fetched <number of read rows> rows and <number of error rows> error rows.

User Response:

Enable row error logging in the session, and check other error messages logged for more
details. Also, verify that the code page for the lookup source is two-way compatible with the
Integration Service and target code page.

TT_11166

You cannot connect the transformation <transformation name> downstream from a Sequence
Generator transformation.

Explanation:

You connected a Sequence Generator transformation upstream from a Custom

transformation or a transformation developed using the Custom transformation.

User Response:

Update the mapping.

TT_11168

The code page specified for transformation <transformation name> is not valid for the file
<file name>.

User Response:

Specify a valid code page. The code page should specify the proper locale for the lookup
source file.

TT Messages

407

408

TT_11169

The transformation <transformation name> code page <code page ID> is not found.

User Response:

Specify a valid code page. The code page should specify the proper locale for the lookup
source file.

TT_11170

An error occurred processing transformation <transformation name> and creating locale from
the code page <code page name> for file <file name>.

Explanation:

The code page you specified is not valid.

User Response:

Specify a valid code page. The code page should specify the proper locale for the lookup
source file.

TT_11171

The Sequence Generator transformation <transformation name> has the CURRVAL port
connected. When you connect the CURRVAL port, the Integration Service processes one row
in each block.

User Response:

You can optimize performance by connecting only the NEXTVAL port in a mapping.

TT_11172

The dynamic Lookup transformation <transformation name> requires that a String or Binary
lookup port and its associated port have the same length. Since lookup port <port name> has
a length of <length> and the associated port <port name> has a length of <length>, the
Integration Service used the larger length for both ports.

Explanation:

The dynamic Lookup transformation uses a String or Binary lookup port of a certain precision
with an associated port of a different precision. The Integration Service uses the larger
precision for both ports.

User Response:

Edit the Lookup transformation and use the same precision for both ports.

TT_11180

The lookup cache <file name> was created with a match policy different from the multiple
match policy used for the dynamic Lookup transformation <transformation name>.

User Response:

Verify that both lookup transformations use the same multiple match policy.

TT_11195

Warning. Unsorted input found when building the cache for the Lookup transformation
<transformation name>. The current number of entries in the index cache is <number of
entries>. The cache will be built by insertion. This will cause it to take longer and the index
cache may require more space.

Explanation:

The SQL in the Lookup transformation does not sort data in the sort order that the Integration
Service expects. The SQL sorts data in an incorrect order due to an ORDERBY clause in the
SQL or because the user-defined SQL override retrieves the port data in a different order.

User Response:

To improve performance, review the SQL and fix the SQL to retrieve data in the sort order
that the Integration Service expects.

Explanation:

The sort order settings for the database server and Integration Service do not match.

User Response:

To improve performance, configure a consistent sort order for the database server and the
Integration Service.

TT_11204

An error occurred expanding a parameter or variable in the Lookup transformation

<transformation name> for the cache file name prefix <prefix>.

User Response:

Explanation:

Internal error.

Chapter 19: T Message Codes

User Response:

Contact Informatica Global Customer Support.

TT_11209

The upgrade process failed to complete. The Sequence Generator transformation has an
invalid datatype.

Explanation:

The mapping contains a Sequence Generator transformation in which the datatype for the
NEXTVAL or CURRVAL output port is not Bigint.

User Response:

Import the mapping again or re-create the Sequence Generator transformation.

TT_11210

An error occurred expanding a parameter or variable in the Lookup transformation

<transformation name> for the lookup table name <lookup table name>.

Explanation:

The session contains a mapplet variable or parameter to define a lookup table name. The
Integration Service failed to expand the parameter or variable.

User Response:

Verify that the parameter file contains a parameter and value for the lookup table name. If
you are using a mapping variable, verify the variable has a value.

TT Messages

409

CHAPTER 20

U Message Codes
This chapter includes the following topics:
UDT Messages, 410
UM Messages, 413

UDT Messages

410

UDT_50007

Invalid output type: <output type>.

Explanation:

The Unstructured Data transformation OutputType attribute is not valid.

User Response:

Open the Unstructured Data transformation UDT Settings tab. Choose file, buffer, or splitting
OutputType.

UDT_50008

Failed to flush the output.

Explanation:

An error occurred while flushing XML from the output buffer downstream in the pipeline.

User Response:

Check system resources and review session log for other errors.

UDT_50010

Unstructured Data transformation can only have one default output port.

Explanation:

The Unstructured Data transformation must have only one OutputBuffer port.

User Response:

The Designer does not allow you to delete OutputBuffer ports. Recreate the transformation or
export the transformation, edit the .XML file, and re-import the definition to the repository.

UDT_50011

Unstructured Data transformation can only have one default input port.

Explanation:

The Unstructured Data transformation must have only one InputBuffer port.

User Response:

The Designer does not allow you to delete an InputBuffer port. Recreate the transformation or
export the transformation, edit the .XML file, and re-import the definition to the repository.

UDT_50014

There must be two default input ports in the Unstructured Data transformation.

Explanation:

The Unstructured Data transformation is configured for file output. When the output type is
file, the Unstructured Data transformation receives the source file in the InputBufferPort and
the output file name in the OutputFileName port. One of the default input ports is missing or
one of the ports is a duplicate.

User Response:

The Designer creates the default input ports. You cannot delete or add them. You can
change the output type to update the default ports or recreate the transformation.

UDT_50020

License for Unstructured Data Option has not been enabled.

Explanation:

The Unstructured Data Option does not have valid license key to run in PowerCenter.

User Response:

View license details using the Administrator tool or the infacmd ShowLicense command.
Contact Informatica Global Customer Support to obtain a new incremental license key for the
Unstructured Data Option.

UDT_50021

Failed to set output data for row <row number>.

Explanation:

The Unstructured Data transformation failed to write data to the OutputBuffer port.

User Response:

Review the session log for related messages.

UDT Messages

411

412

UDT_50022

Unable to open specified file <file name>.

Explanation:

The Data Transformation Engine cannot open a source file because the file is missing or the
file location is invalid.

User Response:

The Unstructured Data transformation is passing a file name and path from the InputBuffer
port to the Data Transformation Engine. Verify the file name and location are valid in the
source data.

UDT_50026

Data Transformation port <port name> not found in the group <group>.

Explanation:

The Data Transformation service is returning data to ports that you defined on the Relational
Hierarchy tab of the Unstructured Data transformation. A port is missing from one of the
groups on the tab.

User Response:

When you define hierarchical output groups in the Unstructured Data transformation, you
must define the same structure in the Data Transformation project. To change the Data
Transformation project, export the group hierarchy schema file from the Unstructured Data
transformation. Import the schema to the Data Transformation project and recreate the
project.

UDT_50027

Data Transformation group <group> not found in the Unstructured Data transformation.

Explanation:

The Data Transformation service is returning data to groups of ports that you defined on the
Relational Hierarchy tab of the Unstructured Data transformation. A group is missing from the
Unstructured Data transformation.

User Response:

UDT_50028

Invalid XSD schema for service <service name>.

Explanation:

Explanation:

The Data Transformation service cannot run because the service name is not in the Data
Transformation repository or the Data Transformation Engine is not running on the machine
where the PowerCenter Client is installed.

User Response:

Verify that the Data Transformation service is in the ServiceDB folder of the Data
Transformation installation and the Data Transformation server component is installed on the
PowerCenter Client machine.

UDT_50034

'Service Name' cannot be left blank in the transformation. Enter a service name in the UDT
Settings tab.

Explanation:

The Service Name attribute is blank in the Unstructured Data transformation. The Service
Name attribute contains the name of the Data Transformation service to run. The service
name cannot be blank unless you enable dynamic service names.

User Response:

Enter a valid Data Transformation service on the UDT Settings tab of the Unstructured Data
transformation. The service must be present in the Data Transformation repository.

UM Messages
UM_10000

The Service Manager failed to load the domain privileges.

Explanation:

PowerCenter Services is not properly installed.

User Response:

Reinstall PowerCenter Services.

UM_10001

The user management metadata is inconsistent.

Explanation:

The domain configuration database has inconsistent metadata.

UM Messages

UM_10020

The user <user name> belonging to <security domain name> was not associated with the
node <node name>.

Explanation:

The user specified in the node configuration does not match the domain configuration.

User Response:

Either modify the user in the domain node or redefine the node with the same user as the
domain node.

UM_10021

The host name for node <node name> is inconsistent between node configuration and
domain configuration.

Explanation:

The node configuration is incorrect.

User Response:

Redefine the node.

Explanation:

The node is defined twice.

User Response:

Create a node with a different name.

Chapter 20: U Message Codes

UM_10022

The port number for node <node name> is inconsistent between node configuration and
domain configuration.

Explanation:

The node configuration is incorrect.

User Response:

Redefine the node.

Explanation:

The node is defined twice.

User Response:

Create a node with a different name.

UM_10023

The gateway setting for node <node name> is inconsistent between node configuration and
domain configuration.

Explanation:

You configure a gateway node in the domain properties and in the node properties. The node
is configured as a gateway node in one location and as a worker node in the other location.

User Response:

Update the domain or node properties so that the node is configured as a gateway node or a
worker node in both locations.

UM_10024

The Service Manager cannot encrypt the credential because the characters in the user name,
password, or domain name are not UTF-8 compliant.

Explanation:

The user name, password, or domain name contain characters that are not UTF-8 compliant.

User Response:

Ensure that the user name, password, and domain name contain characters that are UTF-8
compliant.

User Response:

Run the Repository Service in normal mode.

UM_10032

The Service Manager could not load privileges from the service <service name>.

Explanation:

The application service does not exist in the domain.

User Response:

Create the application service in the domain.

Explanation:

The application service is disabled or the application service contents, users, or groups have
not been upgraded.

User Response:

Enable the application service or upgrade the application service contents, users, or groups.

Explanation:

The Repository Service is running in exclusive mode.

User Response:

Run the Repository Service in normal mode.

UM Messages

415

416

UM_10061

UM_10088

The Service Manager failed to add users to service <service name>. The service users and
groups are not synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

The Service Manager periodically synchronizes the list of users and groups in the application
service repository with the users and groups in the domain configuration database. Either
wait until the Service Manager finishes synchronization, or restart the application service so
that the Service Manager synchronizes immediately.

UM_10089

The Service Manager failed to add groups to service <service name>. The service users and
groups are not synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

UM Messages

417

418

UM_10090

The Service Manager failed to remove users from service <service name>. The service users
and groups are not synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

UM_10091

The Service Manager failed to remove groups from service <service name>. The service users
and groups are not synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

UM_10092

The Service Manager failed to update privileges for user <user name> in security domain
<security domain name> for service <service name>. The service users and groups are not
synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

UM_10093

The Service Manager failed to update privileges for user <user name> in security domain
<security domain name> for service <service name> with error <error message>.

Explanation:

The Service Manager cannot communicate with the application service.

User Response:

Review the error message from the application service.

UM_10094

The Service Manager failed to update privileges for group <group> in security domain
<security domain name> for service <service name>. The service users and groups are not
synchronized with the domain.

Explanation:

The users and groups in the application service repository are not synchronized with the
users and groups in the domain configuration database.

User Response:

UM_10095

The Service Manager failed to update privileges for group <group> in security domain
<security domain name> for service <service name> with error <error message>.

Explanation:

The Service Manager cannot communicate with the application service.

User Response:

Review the error message from the application service.

Chapter 20: U Message Codes

UM_10096

Unable to perform the requested operation because this would violate the maximum number
of licensed Metadata Manager users: [<number of users]

Explanation:

The license object assigned to a Metadata Manager Service determines the number of users
you can assign to a Metadata Manager Service. The Metadata Manager Service already has
the maximum numbers of users assigned to it.

User Response:

Remove existing users from the Metadata Manager Service before you assign other users to
the service. To increase the number of users you can assign to the Metadata Manager
Service, get a new license file from Informatica Global Customer Support.

UM_10097

Unable to perform the requested operation because groups may not have Metadata Manager
privileges or roles when Metadata Manager user count enforcement is enabled.

Explanation:

You attempted to add Metadata Manager privileges or roles to a group. However, the license
object for the Metadata Manager Service is enabled to validate the number of licensed users
assigned to a Metadata Manager Service. If the license object is enabled to validate the
number of licensed users, you cannot assign Metadata Manager privileges or roles to groups
in the Administrator tool.

User Response:

None.

UM_10098

Unable to perform the requested operation because Reporting Service <service name> does
not support value of username@securitydomain <name> greater than 80 characters.

Explanation:

Data Analyzer uses the user account name and security domain to determine the length of
the user account name, in the format UserName@SecurityDomain. The Service Manager
cannot assign privileges or roles to a user for the Reporting Service when the combination of
the user name, @ symbol, and security domain exceeds 80 characters.

User Response:

Edit the user name or security domain name for the Data Analyzer user so that the
combination of the user name, @ symbol, and security domain is less than 80 characters.

UM_10099

User <user name> in security domain <security domain name> cannot disable own account.

Explanation:

You cannot disable the own user account.

User Response:

Select another user account to disable.

UM_100100

The Service Manager failed to authenticate user <user name> belonging to <security domain
name>. The password was not specified.

Explanation:

The Service Manager requires that LDAP users log in to a PowerCenter application using a
password even though an LDAP directory service may allow a blank password for
anonymous mode.

User Response:

Log in using a password.

UM_100102

The created value provided for user <user name> was not used within its valid timeframe.

Explanation:

The time frame in which you can use the created value expired.

User Response:

Resend the request with a new created value.

UM Messages

419

CHAPTER 21

V Message Codes
This chapter includes the following topic:
VAR Messages, 420

VAR Messages
VAR_27001

Error: There is a recursive reference from <session parameter/mapping parameter type>:

<name> back to itself. Error detected when resolving initial value for <session parameter/
mapping parameter type>: <name>.

Explanation:

The initial value of the mapping variable you specified in the Designer has a circular
dependency when referencing another variable.

User Response:

If the initial value is defined in a parameter file, edit the parameter file associated with the
session. Verify that datatype and corresponding data are compatible.
If the initial value is not defined in the parameter file, go to the mapping and edit the initial
value specified in the variable/parameter dialog box.

420

VAR_27002

Error occurred in expanding reference for <string to expand>.

Explanation:

The repository might have inconsistencies.

User Response:

Contact Informatica Global Customer Support.

VAR_27018

Error: cannot find mapping parameter or variable of name <variable name> in transformation
<transformation name>.

Explanation:

The Integration Service is referencing an undeclared parameter or variable in an expression.

Error: cannot have null data value.

Explanation:

The Integration Service has to check if the data is valid before saving the final value of the
mapping variable in the repository. The data value is null.

Chapter 21: V Message Codes

User Response:

Look at the data set. Make sure the mapping variable value is not null.

VAR_27046

Error in parsing last saved timestamp <date/time value> for mapping variable <name>.
Ignoring the persisted value in repository.

Explanation:

Internal error. The Integration Service ignored the timestamped persisted value because the
timestamp of the variable is invalid in the repository.

User Response:

Contact Informatica Global Customer Support.

VAR_27047

Error in parsing last saved timestamp <date/time value> for persisted value of mapping
variable <name>. Ignore the persisted value in repository.

Explanation:

The Integration Service checks if the data is valid before saving the final value in the
repository. The data value overflowed.

VAR Messages

423

424

User Response:

Change the precision of the variable/parameter if necessary.

VAR_27061

Error: cannot find <workflow/worklet> variable of name <name> referenced in <workflow/

worklet> <name>.

Explanation:

The workflow or worklet expression contains a variable that is not declared. You may have
mistyped the variable name in the expression.

User Response:

Check the variable name in the workflow or worklet expression.

VAR_27062

Warning! Cannot find section for <workflow/worklet> <name> and folder <name> in parameter
file <name>.

Explanation:

The parameter file does not contain a section for the named workflow or worklet.

User Response:

Check the parameter file. Create a section for the workflow or worklet, or correct the folder,
workflow, or worklet name in the parameter file.

Explanation:

The folder name contains a period character (.). The Integration Service uses the period
character (.) to qualify folder, workflow, and session names when you run a workflow with a
parameter file. If the folder name contains a period (.), the Integration Service cannot qualify
the names properly and fails the workflow.

User Response:

Check the folder name and make sure that it does not contain a period. If the folder name
contains a period, deploy the mapping and the workflow to another folder.

VAR_27064

Error: failed to persist <workflow/worklet> variable value(s) for <name> into the repository.

Explanation:

Internal error. The Integration Service failed to write a persistent workflow or worklet variable
value to the repository.

User Response:

Contact Informatica Global Customer Support.

VAR_27067

Error in parsing last saved timestamp <date/time value> for <workflow/worklet> variable
<name>. Ignore the persisted value in the repository.

Explanation:

Internal error. The Integration Service failed to pass the timestamp value for the named
workflow or worklet variable.

User Response:

Contact Informatica Global Customer Support.

VAR_27068

Error in parsing last saved timestamp <date/time value> for persisted value of <workflow/
worklet> variable <name>. Ignore the persisted value in the repository.

Explanation:

Internal error. The Integration Service failed to pass the timestamp value for the persistent
value of the named workflow or worklet variable.

User Response:

Contact Informatica Global Customer Support.

VAR_27069

Error in getting the final value for workflow variable <name>. Skip updating the persisted
value for this variable.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

VAR_27072

Error: illegal to set the override value for pre-defined workflow variable <name>.

Explanation:

You are trying to override the value of a pre-defined workflow variable in a parameter file.
This is not allowed.

Chapter 21: V Message Codes

User Response:

Either remove the variable from the parameter file or use a user-defined workflow variable in
the expression.

VAR_27073

Internal error: decimal datatype is not supported for <variable type>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

VAR_27075

Error: cannot reference to <variable/parameter type> <variable/parameter name> whose value

is NULL.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

VAR_27079

Warning: <variable type>: <variable name>, NULL override value not valid. The override value
is set to empty string.

Explanation:

You set a mapping variable to NULL in the parameter file, but the variable cannot have a null
value. The Integration Service reset the variable value to an empty string.

User Response:

Check the value of the variable in the parameter file. Set it to a value other than NULL.

VAR_27086

Cannot find specified parameter file <file name> for <workflow/session name>.

Explanation:

The Integration Service cannot find the parameter file.

User Response:

Verify that the parameter file exists in the location specified in the pmcmd command line,
workflow properties, or session properties. Verify that the parameter file name is spelled
correctly.

VAR_27097

Error: Failed to read line from parameter file <file name> for <workflow/session name>.

Explanation:

The Integration Service cannot read the parameter file.

User Response:

Verify that the user configured to start Informatica Services has read permission on the
parameter file directory. Verify that the parameter file is valid.

VAR Messages

425

CHAPTER 22

W Message Codes
This chapter includes the following topics:
WEBM Messages, 426
WRT Messages, 429
WSC Messages, 447
WSH Messages, 449
WSP Messages, 457

WEBM Messages

426

WEBM_1004

Preserve Client State option is set, but no client ID is given in application connection
<application connection name>.

Explanation:

In the specified webMethods application connection, you selected the Preserve Client State
option. However, you did not specify a client ID.

User Response:

Set a value for the client ID if you select the Preserve Client State option.

WEBM_2004

Client Group does not have the permission to subscribe to document type <document type>.

Explanation:

The Integration Service could not read a webMethods document from the source. The
document belongs to a document type the client group specified in the webMethods
application connection does not have permission to subscribe to.

User Response:

If you want to receive webMethods documents of this document type, configure the
webMethods client to allow the client group to receive documents of this type.

WEBM_2005

Source <source name> is configured to receive messages, but no client ID is given in

application connection <application connection name>.

Explanation:

This is a warning message. You configured the session to receive documents in deliver/
receive mode. However, the application connection for the webMethods source definition in
the session properties does not contain a client ID.

User Response:

You can configure a value for client ID in the webMethods application connection properties.

WEBM_2010

Reader received and rejected a document with a mismatched document type <document
type>: <document>.

Explanation:

The Integration Service read a document that does not match the document type in the
source definition. The document is rejected.

User Response:

None.

WEBM_2011

Failed to store a document in the recovery cache: <error message>.

Explanation:

The Integration Service could not store a document it read from the source in the recovery
cache.

User Response:

See the additional error message for more information.

WEBM_2012

Failed to retrieve a document from the recovery cache: <error message>.

Explanation:

During a recovery session, the Integration Service could not read a document from the
recovery cache.

User Response:

See the additional error message for more information.

WEBM Messages

427

428

WEBM_2013

The data retrieved from the recovery cache is not a valid webMethods document.

Explanation:

The Integration Service could not convert the data for the specified field. For example, the
field is of datatype integer, but the data for the field is out of range.

User Response:

Make sure the data for the field uses the proper range and precision.

WEBM_3005

Client Group does not have the permission to publish document type <document type>.

Explanation:

The Integration Service tried to write documents to the target of the specified document type.
However, the client group specified in the webMethods application connection for the target
does not have permission to publish documents of this type.

User Response:

If you want to publish webMethods documents of this document type, configure the
webMethods client to allow the client group to publish documents of this type.

Chapter 22: W Message Codes

WRT Messages
WRT_8000

Error processing table.

Explanation:

The database failed to write to a target table.

User Response:

Check the session log for related error messages.

WRT_8001

Error connecting to database.

Explanation:

The Integration Service failed to connect to the target database. You may have logged in
incorrectly.

User Response:

WRT_8004

Writer initialization failed <error message>. Writer terminating.

Explanation:

The Integration Service failed to connect to the target database. You may be logged in
incorrectly.

User Response:

Explanation:

The Integration Service does not have access to the one of the error/output/session log files.

User Response:

Ask the PowerCenter administrator to review write privileges for the user running the
Integration Service.

Explanation:

The mapping includes target tables that do not exist or have not been appropriately updated
in the target database.

User Response:

Check the target database for the appropriate tables. If necessary, create or update the
tables.

WRT_8012

Writer Run: Data out of order for targets, Terminating.

Explanation:

A violation of a load-order criteria specified in a mapping occurred. This is an internal error.

User Response:

Contact Informatica Global Customer Support.

WRT_8019

No column marked as primary key for table <table name>.

Explanation:

The Integration Service could not locate the primary key for the specified target table, so it
could not perform the delete operation.

User Response:

In the Target Designer, specify a primary key in the target table definition, then generate and
execute the SQL.

WRT_8020

No column marked as primary key for table <table name>.

Explanation:

The Integration Service could not locate the primary key for the specified target table, so it
could not perform the update operation.

User Response:

In the Target Designer, specify a primary key in the target table definition, then generate and
execute the SQL.

WRT_8023

Error truncating target table <target name>. <database error string>.

Explanation:

Could not truncate the target table.

User Response:

Look at the database error string for more information.

WRT Messages

429

WRT_8028

Error <error number> forking <loader type> external loader process for target <target name>.

Explanation:

The external loader process could not be forked.

Explanation:

The Windows system encountered an error while attempting to check for external loader
completion.

User Response:

Look up the Windows system error code and/or check the Windows system log.

WRT_8047

Error: External loader process <process ID> exited with error <exit loader error number>.

Explanation:

The external loader process exited with an error.

User Response:

Look up the error code in the database external loader documentation.

WRT_8048

Error <Windows system error number> retrieving the termination status for completed
external loader [handle=<process ID>].

Explanation:

The Windows system encountered an error while attempting to retrieve the exit code for the
external loader.

User Response:

Look up the Windows system error code and/or check the Windows system log.

WRT_8049

Error: External loader process <process ID> exited due to receipt of signal <UNIX signal
number>.

Explanation:

External loader on UNIX exited due to receipt of a UNIX signal.

User Response:

Look up the UNIX signal number in signal.h, which is in /usr/include/sys/signal.h.

Chapter 22: W Message Codes

WRT_8053

Warning! Error executing pre-load stored procedures. Session <session name> user name
<user name> Error <database error message>.

Explanation:

You ran a session with a pre-load stored procedure that failed to execute.

User Response:

Contact the database administrator.

WRT_8058

Error <system error number> opening session bad (reject) file <bad file name>.

Explanation:

During the initialization of a session, the Integration Service failed to open the reject file
specified due to an operating system error.

User Response:

For Integration Service on Windows, see Windows help and look up the specified system
error number.
For Integration Service on UNIX, locate the error in the /usr/include/sys/errno.h file. See the
UNIX Documentation for explanation of the error.

WRT_8059

Writer initialization failed [Failed to Initialize OuputFile.] Writer terminating.

Explanation:

During the initialization of a session with a flat file target, the Integration Service failed to
initialize the output file.

User Response:

Contact the system administrator.

WRT_8060

Writer initialization failed [Failed to get external loader information]. Writer terminating.

Explanation:

Internal error. You may have repository inconsistencies.

User Response:

Contact Informatica Global Customer Support.

WRT_8062

Writer initialization failed [Failed to generate external loader control file]. Writer terminating.

Chapter 22: W Message Codes

WRT_8075

Writer initialization failed [Error creating truncate table order]. Writer terminating.

Explanation:

Internal error. The repository may have inconsistencies.

Internal error.

User Response:

Check preceding error messages to see the cause for the error.

WRT_8082

Writer run terminated. [Errors encountered.]

Explanation:

Internal error.

User Response:

Check preceding error messages to see the cause for the error.

WRT_8085

Writer run terminated. [Internal Error].

Explanation:

Internal error.

User Response:

Check preceding error messages to see the cause for the error. Also, contact Informatica
Global Customer Support.

WRT_8086

Writer run terminated. [Error in executing post-load stored procedures.]

Explanation:

Database error.

User Response:

Check preceding error messages to see the cause for the error. Also, contact the database
administrator.

WRT_8088

Writer run terminated. [External loader error.]

Explanation:

Internal error.

User Response:

For a more specific error message, see the external loader log.

WRT Messages

433

434

WRT_8091

Error truncating target table <table name>. Error forming query.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

WRT_8092

Error truncating target table <table name>. Error preparing truncate target table query: <table
query>.

Explanation:

Database error.

WRT_8110

BW Statement Init.

Explanation:

The Integration Service failed to initialize the InfoSource.

User Response:

You attempted to INSERT rows into the target table. However, you might not have been
granted rights to INSERT into the specified table.

User Response:

Contact the database administrator.

WRT_8118

ERROR: Target table <table name> does not allow UPDATE. Row # <row ID> in bad file.

Explanation:

You attempted to UPDATE rows into the target table. However, you might not have been
granted rights to UPDATE into the specified table.

User Response:

Contact the database administrator.

WRT_8119

ERROR: Target table <table name> does not allow DELETE. Row # <row ID> in bad file.

Explanation:

You attempted to DELETE rows from the target table. However, you might not have the rights
to DELETE from the specified table.

User Response:

Contact the database administrator.

WRT_8120

ERROR: Invalid row type for target table <table name>. Row # <row ID> in bad file.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

WRT_8123

Failed to prepare target table load. Database error: <database error number>.

Increase the target column size in the Designer.

436

WRT_8171

Cannot locate CreateWrtTargetInstance function in the <library file name> shared library.

Explanation:

The DLL loaded for the specified target does not contain a function called
CreateWrtTargetInstance.

User Response:

Make sure this is the correct DLL.

WRT_8172

Cannot create ASCII locale.

Explanation:

Third party library error.

User Response:

Make sure the paths to libraries and environments are set properly.

WRT_8173

Conversion from UNICODE failed - not all the characters were converted.

Explanation:

The number of characters converted from Unicode does not match the number of characters
in the buffer. The number is less than the expected number.

User Response:

Contact Informatica Global Customer Support.

WRT_8174

Error while flushing the buffer to output file <output file name>. Error message is <error
message>, data buffer <buffer>.

Explanation:

There was an operating system input/output error trying to output into target file.

User Response:

Check that the output file is not locked and has the correct user permissions. Make sure the
system has enough disk space.

Chapter 22: W Message Codes

WRT_8175

Field separator string for file <file name> contains non-ASCII characters <Unicode
characters>.

Explanation:

At initialization time, the Integration Service is in ASCII data movement mode, but the field
separator string specified in the session for that target file contains some non-ASCII symbols.

User Response:

Change the Integration Service to UNICODE data movement mode or change the field
separator string to be ASCII-only.

WRT_8176

NULL character for file <file name> is not ASCII <Unicode character>.

Explanation:

At initialization time, the Integration Service is in ASCII data movement mode, but the null
character specified in the session for that target file is a non-ASCII character.

User Response:

Change the Integration Service to UNICODE data movement mode or change the null
character to an ASCII character.

WRT_8178

Failed to get quote option for file <file name>.

Explanation:

Error getting options for the file from the repository.

User Response:

Save the session to reset a flag then run the session again. Or contact Informatica Global
Customer Support.

WRT_8179

Unknown error occurred while trying to close output file <file name>.

Explanation:

Operating system input/output error occurred when closing the output target file.

User Response:

Check that the file is not locked, is accessible, and has the correct permissions. Check that
there is sufficient disk space.

WRT_8180

Failed to generate indicator file name using <output file name>.

Explanation:

You used an unsuitable file name for automatic indicator file name generation.

User Response:

Contact Informatica Global Customer Support. The following are valid names (/ is treated
the same way as \). The Integration Service appends the following file names with the
extension .ind:
FNAME
.FNAME
FNAME
./FNAME
DIR/FNAME

The Integration Service replaces the following file names that have the file extension (.ext)
with .ind:
FNAME.EXT
.FNAME.EXT
/FNAME.EXT
./FNAME.EXT
DIR/FNAME.EXT

DIR.DIREXT/FNAME is an invalid input name. You cannot use a period (.) in the directory
name because the Integration Service cannot process the input name.

WRT Messages

437

438

WRT_8181

Specified locale <locale name> for the file <output file name> is not valid for NULL character
<character>.

Explanation:

The null character you specified does not exist in the target code page.

User Response:

Make sure the target code page is compatible with the Integration Service code page or
change the null character so that it exists in the target code page.

WRT_8183

Rollback failed for the target <target instance name>.

Explanation:

The database experienced a deadlock and the rollback failed for the specified target. The
rollback segment could be too small to occur successfully.

User Response:

Check the database setup. Make sure the rollback segment is large and try the rollback again.

WRT_8184

WARNING: The output codepage specified for the target file <target file name> is not ASCIIbased, whereas the Informatica Server is running in ASCII mode.

Explanation:

The Integration Service is running in ASCII data movement mode, but the code page you
specified for the target is not ASCII-based.

User Response:

Change the Integration Service data movement mode to Unicode and run the session again.

WRT_8185

Error transferring data from target <target name> using FTP.

Explanation:

The Integration Service encountered an error while preparing to transfer the file using FTP.

User Response:

Verify that the FTP server is running, verify the file permissions and connection information,
and run the session again.

WRT_8186

Error while finalizing load. Writer run terminated.

Explanation:

After the target finished processing, the Integration Service finalized the file for FTP and
encountered an error.

User Response:

See previous message in the log for more information.

WRT_8187

Error resolving output file <file name> for target <target name>.

Explanation:

Operating system error.

User Response:

Contact the system administrator.

The delete from command impacts performance. If the database supports the truncate table
command and you want to improve performance, review database table privileges and key
constraints.

WRT_8209

External loader error, Teradata external loader cannot take table names greater than 24
characters. The table name <table name> has <table length> characters.

Explanation:

Teradata does not support external loads for table names greater than 24 characters.

User Response:

Use a table name of less than 24 characters.

WRT_8218

Error: Teradata external loader requires a primary key on table <table name> when using load
mode <load mode>.

Explanation:

You did not set a primary key on the table when using load mode update, upsert, or delete.

User Response:

Set a primary key on the target table.

WRT_8219

Error: Table mismatch, target table <table name> with <number of columns> columns
mismatch with physical table with <number of columns> columns.

Explanation:

Explanation:

The Integration Service encountered an error from the database.

User Response:

See the Informatica Knowledge Base.

WRT_8244

Error outputting row # <row number> for output file <flat file target>. The row was rejected.

Explanation:

The Integration Service encountered an error outputting the row to the flat file target, and
wrote the row in the reject file. The Integration Service may have rejected the row for one of
the following reasons:
The target is a fixed-width file, and the field width for a datetime column is not large

enough to accommodate the datetime value, including the datetime format.

The target is a fixed-width file, and the field width for a numeric column is not large

enough for the numeric value, including the decimal and thousand separator.
User Response:

Edit the target definition in the Designer, and verify you configure the precision and field
width to accommodate the total length of the target column.

WRT_8246

Error: External loader is not supported for direct flat files. Target instance <target instance
name>.

Explanation:

In the session properties, you chose an external loader connection for a target based on a
flat file target definition. This might have happened if you chose an external loader
connection for a target based on a relational target definition and then in the Designer, you
changed the relational target definition to a flat file definition.

User Response:

In the Designer, change the flat file target definition to a relational target definition. You can
only choose an external loader connection when the target is based on a relational target
definition.

WRT_8247

Error: Cannot run in bulk mode for a test load for connection <target name>.

Explanation:

In the session properties, you configured the Integration Service to perform a test load and
you chose bulk mode for a relational target.

User Response:

Choose Normal for the target load type. You can perform a test load for relational targets
when you configure a session for normal mode. If you configure the test load session for bulk
mode, the session fails.

WRT Messages

441

442

WRT_8250

Target (test load not supported for this target type): <target name> (Instance Name: <target
instance name>).

Explanation:

In the session properties, you configured the Integration Service to perform a test load, but
the Integration Service does not perform a test load on some of the targets in the mapping.

User Response:

None. The Integration Service only performs a test load on relational targets.

WRT_8270

Target connection group #<group number> consists of target(s) <target name>.

Explanation:

Informational message.

User Response:

None. The Integration Service writes in the session log which targets belong to a target
connection group. The target connection group number is an arbitrary number. It does not
specify the order the Integration Service loads to the targets. A target connection group is a
group of targets that the Integration Service uses to determine commits and loading.

WRT_8281

Error: The same character <character> is used as both field and decimal separator for the
field <port name> of the target <target name>.

Explanation:

For the delimited flat file target definition, you chose the specified character as the decimal
separator and as the field delimiter.

User Response:

In the session properties, choose a different delimiter for the target. Or, in the Designer,
choose a different decimal separator for the target definition.

WRT_8282

Error: The same character <character> is used as both field and thousand separator for the
field <port name> of the target <target name>.

Explanation:

For the delimited flat file target definition, you chose the specified character as the thousand
separator and as the field delimiter.

User Response:

In the session properties, choose a different delimiter for the target. Or, in the Designer,
choose a different thousand separator for the target definition.

WRT_8297

External loader process <loader process> exited with warning code <action file code>.

Explanation:

You are using an external loader warning action file. The external loader returned a non-zero
warning code.

User Response:

Locate the warning code in the external loader warning action file. You can edit the warning
action file to treat each warning code as a warning or as a fatal error. For details on loader
warning codes, see the loader documentation.

WRT_8299

External loader error. Cannot find loader warning action file.

Explanation:

You configured the Integration Service to use an external loader warning action file. The
Integration Service cannot locate the loader warning action file.

User Response:

Locate the warning action file and copy it to the location you specified for the loader warning
action file when you configured the Integration Service. Verify that the name of the action file
matches the name you specified when you configured the Integration Service.

WRT_8300

External loader error. Error opening loader warning action file <file name> for reading. errno =
<system error code>.

Explanation:

You configured the Integration Service to use an external loader warning action file. The
Integration Service cannot read the warning action file.

Chapter 22: W Message Codes

User Response:

Verify that the system account that started the Integration Service has read permission for
the directory the loader warning action file is located in.

Explanation:

System error.

User Response:

Contact the system administrator.

WRT_8301

Error loading warning codes from external loader warning action file <file name>.

Explanation:

The Integration Service could not load the warning codes from the external loader warning
action file.

User Response:

Check preceding messages to see the cause of the error.

Explanation:

The Integration Service could not load the warning codes from the external loader warning
action file because you did not specify the name or location of the file when you configured
the Integration Service.

User Response:

Specify a name and location for the external loader warning action file.

WRT_8302

External loader error. Error duplicating handle to stderr for DB2 EEE external loader. System
error message is <system error message>. errno = <error number>.

Explanation:

System error.

User Response:

Contact the system administrator.

WRT_8303

External loader error. Error opening DB2 EEE external loader log file for writing. System error
message is <system error message>. errno = <error number>.

Explanation:

System error.

User Response:

Contact the system administrator.

WRT_8304

External loader error. Error redirecting stderr to loader log file for DB2 EEE external loader.
System error message is <system error message>. errno = <error number>.

Explanation:

System error.

User Response:

Contact the system administrator.

WRT_8305

External loader error. Error restoring stderr for DB2 EEE external loader. System error
message is <system error message>. errno = <error number>.

Explanation:

System error.

User Response:

Contact the system administrator.

WRT_8308

Error: Failed to write metadata for target table <target instance> to the output file <target file
name>.

Explanation:

You configured the Integration Service to write flat file metadata to the target file. The
Integration Service could not write to the target.

User Response:

Verify the Integration Service can connect to the flat file target directory and that the disk has
enough space.

WRT_8309

External loader error. The Date Format <format> is invalid. Target instance <target instance
name>.

Explanation:

You entered an invalid value for the Date Format option when you configured the MultiLoad
external loader.

WRT Messages

443

User Response:

Edit the MultiLoad external loader connection and enter a valid value for Date Format.
Restart the session.

WRT_8310

External loader error. Update is not valid for target instance <target instance name> since no
primary key(s) is mapped to the target.

Explanation:

The MultiLoad or TPump external loader cannot run in update mode because you did not
define a primary key for the target.

User Response:

Run the external loader in a different mode, or define a primary key for the target.

WRT_8311

External loader error. Update is not valid for target instance <target instance name> since no
non-key field(s) is mapped to the target.

Explanation:

The MultiLoad or TPump external loader cannot run in update mode because you did not
define any non-key columns in the target instance.

User Response:

Run the external loader in a different mode, or add a non-key column to the target.

WRT_8312

External loader error. Delete is not valid for target instance <target instance name> since no
primary key(s) is mapped to the target.

Explanation:

The MultiLoad or TPump external loader cannot run in delete mode because you did not
define a primary key for the target.

User Response:

Run the external loader in a different mode, or define a primary key for the target.

WRT_8313

External loader error. Upsert is not valid for target instance <target instance name> since
update is not valid for the target.

Explanation:

The MultiLoad or TPump external loader cannot run in upsert mode for one of the following
reasons:
You did not define a primary key for the target.
You did not define any non-key columns for the target.

444

User Response:

Run the external loader in a different mode, define a primary key for the target, or add a nonkey column to the target.

WRT_8315

The user-defined commit session is not supported for this type of mapping (no targets in
commit groups).

Specify a directory name for LoaderControlFileDirectory.

WRT_8343

Error: Target filename <file name> exceeded maximum allowable length <bytes>.

Explanation:

The target file name length exceeds the system limit (260 on Windows, 255 on UNIX).

User Response:

Reduce the length of the file name.

WRT_8371

Row rejected since a rollback was issued due to errors in the transaction.

Explanation:

The Integration Service encountered an error in the transaction and the session is configured
to roll back on error.

User Response:

Read other messages in the log file to find the row that caused the error.

Explanation:

The transaction control expression in a Transaction Control transformation evaluated to roll

back the transaction. The Integration Service rolled back all rows in the transaction, including
this row.

User Response:

Read other messages in the log file to find the row that caused the transaction control
expression that evaluated to roll back.

WRT_8372

Row rejected since a rollback was issued due to a failed commit.

Explanation:

The Integration Service failed to commit a transaction and the session is configured to roll
back on failed commit.

User Response:

Read other messages in the session log to find the cause of the failed commit.

WRT_8398

Error opening session output file <file name>. Error: <error text>.

Explanation:

The Integration Service could not open the target output file for the session. This error can
occur if the target output file does not exist, the path to the file is invalid, the Informatica
Services account or the operating system user in the operating system profile does not have
permission to open the file, or another process is using the file. As a result, the session failed.

User Response:

Verify that the target output file exists, grant read and write permissions on the file to the
Informatica Services account or the operating system user in the operating system profile,
and verify that the file is not currently in use by another process. If the session is enabled for
recovery, recover the session. Otherwise, run the session again.

WRT_8399

Error closing target output file <file name>. Error: <error text>.

Explanation:

The Integration Service could not close the target output file. This error can occur if there is
not sufficient disk space available to close the file. As a result, the session failed.

User Response:

Verify that there is sufficient disk space for the target output file. If the session is enabled for
recovery, recover the session. Otherwise, run the session again.

WRT_8414

High availability license is absent. Retry period specified for Integration Service connection to
target is ignored.

Explanation:

The connection object properties are configured, but you do not have the high availability
option. The connection retry period is ignored.

WRT Messages

445

446

User Response:

None.

WRT_8419

Flat file target <target name> FileName port is not supported with connection or merge option.

Explanation:

The Integration Service failed the session because the FileName port is not supported with
the target type or connection. You cannot configure a FileName port with an FTP target,
merge file, or file list.

User Response:

Remove the FileName port from the target.

WRT_8424

The Integration Service cannot read the control file template <control file template name>.

Explanation:

The Integration Service was unable to find the control file template.

Chapter 22: W Message Codes

WRT_8439

The following error occurred reading recovering information from the recovery queue: <error
message>.

WSC Messages
WSC_33021

Web Service connection <application connection name> cannot have a negative timeout
value <timeout value>.

Explanation:

The value for the Timeout parameter in the Web Service application connection is a negative
number.

User Response:

Set the Timeout value in the Web Service application connection equal to zero or higher.

WSC_33023

Encountered a problem during SOAP request conversion (DOC to RPC): <error details>.

Explanation:

The SOAP request for a web service source contains invalid or incomplete data. See the
error details for more information.

User Response:

Modify the SOAP request in the Edit Tables dialog box.

WSC_33024

Error encountered in getting Operation Name for the table <operation name>.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

WSC_33026

Cannot retrieve HTTP proxy port number.

Explanation:

You might not have entered a value for the HTTP proxy port number when you configured the
Integration Service.

User Response:

Configure the HTTP proxy port number for the Integration Service in the Administrator tool.

WSC Messages

447

448

WSC_33028

Cannot retrieve HTTP proxy password.

Explanation:

You might not have entered a value for the password for the HTTP proxy settings when you
configured the Integration Service.

User Response:

Configure the HTTP proxy password for the Integration Service in the Administrator tool.

WSC_33030

Cannot retrieve NT Domain value for authentication.

Explanation:

You might not have specified a value for the domain connection attribute in the Web Service
application connection.

User Response:

Enter a value for the domain connection attribute in the Web Service application connection.

Explanation:

The PATH setting is incorrect.

Check the PATH setting for the specified library. Make sure that library belongs to the
PowerCenter version that you want to use.

WSH Messages
WSH_501

Service Workflow <workflow name> in repository <repository name> and folder <folder
name> is invalid. This workflow cannot be accessed using the Web Services Hub.

Explanation:

The Web Services Hub could not access the workflow because the workflow is not configured
as a web services workflow.

User Response:

Use a valid web services workflow.

WSH_502

Failed to initialize the repository <repository name>: <error message>.

Explanation:

The Web Services Hub could not initialize the repository.

User Response:

See the additional error message for more information.

WSH Messages

449

450

WSH_521

Workflow <workflow name> in folder <folder name> failed to complete. Workflow notification
handler is invoked.

Explanation:

The web service workflow encountered an internal error and failed.

User Response:

Review the notification. Resolve the issue and restart the workflow.

WSH_522

Failed to fetch details of the workflow <workflow name>, in folder <folder name> while
fetching data for the repository <repository name> : <error message>.

Explanation:

The Web Services Hub could not retrieve the details of the workflow from the repository.

User Response:

See the additional error message for more information.

WSH_523

Failed to update data cache for folder <folder name> in the repository <repository name> :
<error message>

Explanation:

The Web Services Hub could not update the folder cache.

User Response:

See the additional error message for more information.

WSH_524

Failed to update data cache for workflow <workflow name>, in the folder <folder name> in the
repository <repository name> : <error message>.

Explanation:

The Web Service Hub could not update the workflow cache.

User Response:

See the additional error message for more information.

WSH_526

Failed to fetch repository data for the repository <repository name> : <error message>.

Explanation:

The Web Services Hub could not retrieve the data for the repository.

User Response:

See the additional error message for more information.

WSH_530

Failed to update data cache for repository <repository name> : <error message>.

Explanation:

The Web Services Hub could not update the data cache for the repository.

User Response:

See the additional error message for more information.

WSH_535

Web Services Hub initialization failed : <error message>.

Explanation:

The Web Services Hub could not be initialized.

Chapter 22: W Message Codes

User Response:

See the additional error message for more information.

WSH_547

Service <web service name>: Failed to initialize service proxy.

Explanation:

The Web Services Hub could not create the web service proxy for the web service workflow.

User Response:

Review the workflow log for more information. Restart the web service workflow.

WSH_553

Failed to find service proxy for the Service <web service name>.

Explanation:

The Web Services Hub could not find the web service proxy for the web service workflow.

User Response:

Review the workflow log for more information. Restart the web service workflow.

WSH_557

Service <web service name>: Failed to activate the service workflow with error <error
message>.

Explanation:

The Web Services Hub could not activate the web service workflow.

User Response:

See the additional error message for more information.

WSH_567

Request <request instance ID>: Invocation timed out for Service <web service name>.
Sending the response containing SOAP fault to the client.

Explanation:

The web service request has timed out. The Web Services Hub will return a SOAP fault
message to the client.

User Response:

Review the workflow log for more information. Restart the web service workflow.

WSH_572

Request <request instance ID>: Client request is no longer active. Discarding the response
message from the WS Writer.

Explanation:

The Web Services Hub discarded the response message because the client request is no
longer active.

User Response:

Resend the web service request.

WSH_578

Request <request instance ID> Client IP <client IP address>: Request message for the Service
<web service name> failed with error <error message>.

Explanation:

The Web Services Hub could not process the web service request.

User Response:

See the additional error message for more information. Resend the web service request.

WSH_601

Service <web service name>: Failed to start the workflow with error <error message>.

Explanation:

The Web Services Hub could not start the workflow.

User Response:

See the additional error message for more information. Resolve the problem and restart the
web service workflow.

WSH_606

Failed to connect to LM Server <domain name>:<integration service name> : <error message>.

Explanation:

The Web Services Hub could not connect to the PowerCenter Integration Service.

User Response:

See the additional error message for more information.

WSH_608

Failed to execute task <task name> : <error message>.

Explanation:

The Web Services Hub could not run the task in the web service workflow.

User Response:

See the additional error message for more information.

WSH Messages

451

452

WSH_617

Invocation failed for <request instance ID> with client IP <client IP address> using Service
<web service name> with instance id <DTM instance ID>. Sending SOAP fault in response.

Explanation:

The Web Services Hub could not start the web service using the PowerCenter Integration
Service and the web service instance and returned a SOAP fault message to the client.

User Response:

Review the SOAP fault message. Resolve the issue and resend the web service request.

WSH_622

Service <web service name>: Failed to update/add service proxy in the folder <folder name>
in repository <repository name>.

Explanation:

The Web Services Hub could not update or add the web service proxy to the folder in the
repository.

User Response:

Review the Repository Service log for more information.

WSH_706

Failed to connect to the repository <repository name> : <error message>.

Explanation:

The Web Services Hub could not connect to the repository.

User Response:

Review the login details. Resolve the issue and log in again.

WSH_721

Failed to start workflow for <workflow name>.

Explanation:

The Web Services Hub could not start the workflow.

User Response:

Review the workflow log for more information. Restart the web service workflow.

Chapter 22: W Message Codes

WSH_1011

Web Services Provider source or target contains incompatible versions of metadata.

Explanation:

The versions of the web service source and target metadata are not compatible. The source
and target must be compatible.

User Response:

Use the same method to create the source and target definitions in a web service workflow.
Use the same encoding style for the input and output messages.

WSH_1012

Web Services Provider source or target contains an invalid type.

Explanation:

A datatype in the web service source or target schema is not valid.

User Response:

Create the web service source and target with the correct datatype.

WSH_1013

Web Services Provider source or target contains an invalid key. Expected Key: [key name].

Explanation:

The web service source or target contains a key column that is not valid.

User Response:

Review the workflow log for more information. Create the web service source and target with
the correct key columns.

WSH_1014

Web Services Provider source or target does not contain a required key.

Explanation:

The web service source or target does not contain the required key.

User Response:

Review the workflow log for more information. Create the web service source and target with
the appropriate primary or foreign key.

WSH_1016

The web service workflow <workflow name> does not exist or is invalid.

Explanation:

The Web Services Hub could not find the web service workflow in the repository.

User Response:

Verify that the workflow is a valid web service and restart the web service workflow.

WSH_1017

Invalid schema name : Schema <XML schema name> is not imported by the WSDL for the
service workflow <workflow name>.

Explanation:

The Designer could not import the source or target from the WSDL because of a schema
name that is not valid.

User Response:

Review the repository log for more information. Reimport the source and target from the
WSDL.

WSH_1026

Failed to read from input stream.

Explanation:

The Web Services Hub could not read the web service request message.

User Response:

Verify that the PowerCenter Integration Service is running. Resend the web service request.

WSH_1027

Failed to parse the MIME message.

Explanation:

The Web Services Hub could not parse the MIME message.

User Response:

Use the correct MIME type if you include a MIME attachment in the web service request.

WSH_1070

Request <request instance ID> ClientIP <client IP address>: Failed to read client message for
Service <web service name> with payload of size <payload size>.

Explanation:

The Web Services Hub could not read the message from the client.

User Response:

Verify that the PowerCenter Integration Service is running. Resend the web service request.

WSH Messages

453

454

WSH_1071

Request <request instance ID> ClientIP <client IP address>: Failed to decode client encoding
for Service <web service name>.

Explanation:

The Web Services Hub could not translate the SOAP encoding of the message in the request.

User Response:

Verify that the encoding style is valid and that the source and target have the same encoding
style.

WSH_1072

Request <request instance ID> ClientIP <client IP address>: Reading client message for
Service <web service name> failed with error <error message>.

Explanation:

The Web Services Hub could not read the message in the web service request.

User Response:

See the additional error message for more information. Verify that the PowerCenter
Integration Service is running. Resend the web service request.

WSH_1077

Failed to send Request <request instance ID> with ClientIP <client IP address> to the service
workflow instance.

Explanation:

The Web Services Hub could not send the web service request.

User Response:

Check the connection between the Web Services Hub and the PowerCenter Integration
Service. Resend the web service request.

WSH_1078

Request <request instance ID> ClientIP <client IP address>: Failed to send client reply for
Service <web service name> with error <error message>.

Explanation:

The Web Services Hub could not send the response to the client.

User Response:

See the additional error message for more information. Resend the web service request.

WSH_1079

Service <web service name>: Web service source connection has been reset due to error
<error message>.

Explanation:

The connection to the web service source was reset because of the error described in the
message.

User Response:

See the additional error message for more information. Check the connection between the
Web Services Hub and the PowerCenter Integration Service. Resend the web service
request.

WSH_1084

Request contains invalid encoding.

Explanation:

The encoding style of the message in the web service request is not valid.

User Response:

Correct the message encoding style and resend the request.

WSH_1104

Service statistics operation <operation name> failed with error <error message>.

Explanation:

The web service operation failed.

User Response:

See the additional error message for more information.

WSH_1124

Service <web service name>: Cannot find schema for namespace <namespace>.

Explanation:

The Web Services Hub could not find the namespace schema.

User Response:

Verify that the namespace included in the message is correct and resend the request.

Chapter 22: W Message Codes

WSH_1126

Service <web service name>: Request or response with attachment is not supported for RPC
encoding style.

Explanation:

You cannot include an attachment in a request or response message that uses the RPC
SOAP binding.

User Response:

To include an attachment in a request or response message, use MIME binding.

WSH_1127

Service <web service name>: Inconsistent binding namespace between Web Service Provider
source and target.

Explanation:

The binding style for the source and target messages must be the same.

User Response:

Change the binding style for the source or target so that they match.

WSH_1128

Service <web service name>: Binding namespace not set.

Explanation:

The request message does not include a binding namespace. The binding namespace is
required in a request message.

User Response:

Set the binding namespace in the message and resend the request.

WSH_1129

Service <web service name>: Message <message> has empty content.

Explanation:

The SOAP message included in the request does not have any content.

User Response:

Add content to the message and resend the request.

WSH_1137

The folder <folder name> does not exist in repository <repository name>.

Explanation:

The folder name is not valid and cannot be found in the repository.

User Response:

Use a valid folder name.

WSH_1138

Invalid service timeout is specified for workflow <workflow name>. The default value <timeout
value> is used.

Explanation:

The timeout value set for the workflow is not valid. The Web Services Hub will use the default
timeout value.

User Response:

If you do not want to use the default value, set the timeout property to a valid value and
restart the web service workflow. Or set the value to 0 to disable the timeout period. Negative
values are not valid. Restart the web service workflow.

WSH_1140

Invalid maximum instance run per hub is specified for workflow <workflow name>. The
default value <Maximum Run Count Per Hub value> is used.

Explanation:

The value for the Maximum Run Count Per Hub property of the workflow is not valid. The
Web Services Hub will use the default value.

User Response:

If you do not want to use the default value, set the Maximum Run Count Per Hub property of
the workflow to a valid value. Negative values are not valid. Restart the web service workflow.

WSH_1141

Invalid service time is specified for workflow <workflow name>. The default value <service
time threshold value> is used.

Explanation:

The value set for the Service Time Threshold property of the workflow is not valid. The Web
Services Hub will use the default value.

User Response:

If you do not want to use the default value, set the Service Time Threshold property of the
workflow to a valid value. Negative values are not valid. Restart the web service workflow.

WSH Messages

455

456

WSH_1142

Folder <folder name> is incorrectly formatted. Please use '[repository_name:]folder_name'

and the repository name is required when the hub is associated with multiple repositories.

Explanation:

The format for the folder name provided is not valid. If the Web Services Hub is associated
with multiple repositories, the repository name must be provided with the folder name in the
format <repository name>:<folder name>.

User Response:

Correct the folder name to include the repository name and restart the workflow.

WSH_1143

Repository <repository name> is not associated with Web Service hub.

Explanation:

The repository is not associated with the Web Services Hub. The Web Services Hub requires
an associated repository.

User Response:

Use a repository that is associated with the Web Services Hub.

WSH_1149

Nonce and created values are required for a PasswordDigest request .

Explanation:

The web service request uses a digested password but the password does not include the
nonce value or the created timestamp.

User Response:

Modify the request so that the UsernameToken element in the SOAP message contains
values for the Nonce and Created elements.

WSH_1150

The nonce value provided has been used. Provide a new nonce value for this login.

Explanation:

The web service request uses a digested password but the password includes a nonce value
that is not valid because it has been used.

User Response:

Nonce values can be used only once. Modify the request so that the UsernameToken
element in the SOAP message contains a new Nonce value.

WSH_1151

The created timestamp provided has expired or has been modified.

Explanation:

The web service request uses a digested password but the password includes a created
timestamp value that is not valid because it has expired or was modified.

User Response:

Modify the request so that the UsernameToken element in the SOAP message contains a
new created timestamp value.

WSH_1152

Nonce and created values must not be specified for a PasswordText request.

Explanation:

The web service workflow uses a text password but the password includes a nonce value and
created timestamp. The nonce value and created timestamp cannot be used with a text
password.

User Response:

Modify the request so that the UsernameToken element in the SOAP message does not
contain values for the Nonce and Created elements.

WSH_1153

The password request is of an unknown type. The request must be a PasswordDigest or

PasswordText request.

Explanation:

The password Type attribute contains an invalid value.

User Response:

Modify the request so that the Type attribute of the Password element in the SOAP message
contains the value PasswordText or PasswordDigest based on the type of password you
want to use. If the attribute is not set, the Web Services Hub uses the password type
PasswordText.

Chapter 22: W Message Codes

WSH_1154

The login information provided is not valid.

Explanation:

The user account information in the UsernameToken element in the SOAP message is not
valid.

User Response:

Modify the request so that the UsernameToken element in the SOAP message contains the
correct login values.

WSH_95063

Could not log in to the repository <repository name> with the specified username and
password.

Explanation:

This occurs when you use a user name or password that is not valid to connect to a
repository to perform a batch web service operation.

User Response:

Use a valid user name and password to log in to the repository.

WSP Messages
WSP_33002

Failed to get attribute <attribute name>.

Explanation:

A session attribute for the Web Services Provider source or target contains inconsistencies.

User Response:

Contact Informatica Global Customer Support.

WSP_33006

The mapping contains more than one Web Services Provider source.

Explanation:

You tried to run a session that contains more than one Web Services Provider source.

User Response:

Edit the mapping to ensure that it contains only one Web Services Provider source.

WSP_33007

The mapping contains more than one Web Services Provider target.

Explanation:

You tried to run a session that contains more than one Web Services Provider output target.

User Response:

Edit the mapping to ensure that it contains only one Web Services Provider output target. The
mapping can contain multiple fault targets and multiple instances of one output target.

WSP_33008

Out of memory.

Explanation:

The Integration Service machine is out of memory.

User Response:

Check memory usage of the machine. Other processes may be using too much memory.
Close unnecessary applications and restart the system. You might want to increase swap
space.

WSP_33009

Valid Real-time options key is not found, unable to run this Web Service session. Please
obtain a valid real-time options key.

Explanation:

The Real-time license is expired, or you have not applied the license key to the license file.

User Response:

Apply the current Real-time license key to the license file. If you do not have a current
license, contact Informatica Global Customer Support.

WSP_34007

Failed to build the acknowledgement message.

Explanation:

Internal error.

WSP Messages

457

458

User Response:

Contact Informatica Global Customer Support.

Chapter 22: W Message Codes

WSP_35008

Reader partition <partition number> failed to flush the cache: <message text>.

Explanation:

The Integration Service encountered an error flushing the message cache.

User Response:

Check the additional error message for more information.

WSP Messages

459

460

462

XMLR_82061

Error: View {XML view} column {column name} was not found and cannot be NULL. Row will
not be processed.

Explanation:

The XML document is missing data for a required column. The column cannot be NULL in the
XML instance document.

User Response:

Change the XML document to include the correct instance data for the schema.

XMLR_82065

Error: Row in XML view [{XML view name}] is not valid because the primary key column
[{column name}] and the foreign key column [{column name}] are different types.

Explanation:

The primary key and the foreign key must be the same datatype.

User Response:

Set the primary key and the foreign key columns to the same datatype.

XMLR_82078

Fatal Error: Infinite length is set for xsd:string for group [group name] column [column name].
Change the size to an appropriate value.

Explanation:

There is a mismatch between the datatype of the XML source and the source qualifier. The
source port is a string datatype with infinite precision. The source qualifier port takes a finite
value. This occurs when the XML source is created from an XML file instead of an XML
schema.

User Response:

Set the string precision to a finite value of the column in the XML source, and re-create the
source qualifier.

XMLW Messages
XMLW_31001

An error occurred while trying to initialize XML environment.

Explanation:

The function that initializes the XML environment returned a failure code.

User Response:

Verify the XML environment is set up correctly, such as the environment variables are set
properly, the .dll files are in the correct location on Windows or the shared libraries on UNIX,
and the supporting .dat files are present.

XMLW_31002

An error occurred while trying to initialize XML manager.

Explanation:

Every XML group must have at least one field. The repository has inconsistencies.

User Response:

Import the target again. Or, contact Informatica Global Customer Support.

XMLW_31006

There already was a row inserted into output for the topmost group. Rejecting the row# <row
number>.

Explanation:

The topmost group must have only one row of data since the XML file can have only one root.

User Response:

Make sure that the data to this group is limited to one row.

XMLW_31007

Row# <row number> has a NULL PK value for XML group <group>.

Explanation:

The XML Writer received data for a primary key that is null.

User Response:

The primary key cannot be null. Check the data and the mapping for inconsistencies. Run the
Debugger.

XMLW_31008

Row# <row number> has a NULL FK value for NOT TOPMOST XML group <group>.

Explanation:

The foreign key is null and cannot find the parent row. The child group rows must attach to
the parent group by primary-foreign key relationships.

User Response:

Check the data and the mapping for inconsistencies. Run the Debugger.

XMLW_31009

Unexpected error processing schema definition <schema definition>.

Explanation:

When the Integration Service attempted to recreate the XML target definition structure from
the metadata, it encountered an error while parsing.

XMLW Messages

463

464

User Response:

Contact Informatica Global Customer Support.

XMLW_31010

Unexpected error occurred while trying to set the value of the element <XML element> with
XML mapping <XML Map> to <value>.

Explanation:

Internal error. You tried to set a value for the element. Some reasons might be that the value
is incorrect or the process ran out of memory.

User Response:

Contact Informatica Global Customer Support.

XMLW_31011

An error occurred while trying to convert the data for field <field name> repository ID <ID
number> of the row <row number> to text.

Explanation:

The XML Writer failed to convert the data into text.

User Response:

Check previous messages in the log for more information. Then contact Informatica Global
Customer Support.

XMLW_31012

Cannot register XML group <group> for target <target instance> - no corresponding group
definition found in the target.

Explanation:

Internal error. The target requested a group that does not exist.

User Response:

Contact Informatica Global Customer Support.

XMLW_31013

Unknown (or illegal) attribute value <value> for attribute <attribute name>. Check repository
for possible data corruption.

Explanation:

Neither the first nor the last values were saved in the repository due to repository
inconsistencies.

User Response:

Contact Informatica Global Customer Support.

XMLW_31014

Unexpected error while generating XML text for the row being removed from the DOM tree.
Row's PK value is <value>.

Explanation:

The XML writer encountered errors while generating code for values.

User Response:

Run the Debugger to check the data for inconsistencies. Contact Informatica Global
Customer Support.

XMLW_31016

Unknown error generating the output XML text.

Explanation:

The Integration Service encountered an error while trying to generate XML output.

User Response:

Run the Debugger to check the data. Contact Informatica Global Customer Support.

XMLW_31017

The mapping text <mapping text> for field <field name> of the XML target <target instance> is
not valid for target's code page <code page>. Failed character code is <character number in
Unicode>.

Explanation:

At initialization time, the Integration Service found that the text in the mapping is not in the
target code page.

User Response:

Check that the XML mapping is compatible with the target code page.

XMLW_31018

Unexpected error occurred while initializing the XML output generator.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

Chapter 23: X Message Codes

XMLW_31019

Error initializing output file for XML target <target name>.

Explanation:

The XML Writer failed to create an output file.

User Response:

Check that the path to the output file exists and is accurate. Verify the disk space is
sufficient. Verify write permissions to the output file.

XMLW_31020

Cannot find an XML group for the incoming block of rows. Fatal error.

Explanation:

The XML Writer cannot find the appropriate group corresponding to the block of data.

User Response:

Run the session again. If it fails, contact Informatica Global Customer Support.

XMLW_31021

Error occurred while processing EOF for the XML target <target instance> group <group>.

Explanation:

The XML Writer encountered errors when processing the end of file (EOF) for the group.

User Response:

Contact Informatica Global Customer Support.

XMLW_31022

Fatal error while flushing to file <file name>. System error message is <error message>.

Explanation:

When writing to file, the XML Writer failed with the operating system message.

User Response:

Check file write permissions, disk space, and that the path to the file exists. Check the
operating system error message and contact the system administrator.

XMLW_31023

Error initializing XML DOM object.

Explanation:

Internal error.

User Response:

Contact Informatica Global Customer Support.

XMLW_31024

Error transferring staged file for XML target <target instance> using FTP.

Explanation:

The Integration Service could not transfer the XML file by FTP.

User Response:

Verify FTP permissions, directory path, network connection, and that the FTP server is
running. Run the session again.

XMLW_31026

Fatal error opening file <file name> for XML output.

Explanation:

The XML Writer failed to open the file. Some reasons could be that the file did not have write
permissions. The path to the file is incorrect.

User Response:

Check file write permissions, directory path, disk space, and that the file exists.

XMLW_31027

Fatal error closing XML output file <file name>. System error message is <error message>.

Explanation:

The XML Writer could not close the XML output file. Some reasons could be that the file did
not have write permissions. The path to the file is incorrect.

User Response:

Check the operating system message for more information.

XMLW_31029

Cannot locate XML init/deinit functions in the DLL <.dll file name>.

Explanation:

The XML .dll file does not contain the initialization and deinitialization functions.

User Response:

Verify that the .dll file is the correct file shipped with the product. If it is incorrect, contact
Informatica Global Customer Support.

XMLW Messages

465

466

XMLW_31030

FK field <field name> for group <group> has to be projected, i.e. there has to be an input field
for it.

Explanation:

The foreign key must be connected in the mapping.

User Response:

Check that the mapping and that the foreign key are connected. Contact Informatica Global
Customer Support.

Explanation:

The target is not defined as a flat file or XML target. It is an undefined object.

User Response:

Contact Informatica Global Customer Support.

XMLW_31040

Field <field name> of the *ROOT* XML group <group> is projected while the PK field is not.

Explanation:

Internal error. If the Primary Key is not connected, none of the fields must be connected. If
the Primary Key is connected, other fields may be connected.

User Response:

Connect the PK field of the root group.

XMLW_31041

FK of the group <group> and PK of the parent group <group> should both either have an
input field or not.

Explanation:

Internal error. If you connect the Primary Key of the root group, then the Foreign Key of all
the immediate child groups must be connected, unless the child group fields do not have
input values. If the Primary Key is not connected, none of the fields may be connected.

User Response:

Validate the mapping and run the session again. Or contact Informatica Global Customer
Support.

XMLW_31043

FK is the only projected field from group <group>.

Explanation:

You are running a session against a mapping with an XML target. The foreign key in the
named group is the only projected field in that group.

User Response:

Edit the mapping to project additional fields into the named group.

XMLW_31047

MQ error occurred while flushing XML output.

Explanation:

The Integration Service could process XML data from the WebSphere MQ queue.

User Response:

Verify that the WebSphere MQ environment settings are correct, that the queue you specified
in the queue connection properties exists, and that the connection properties are valid.

XMLW_31056

Fatal error opening WebSphere MQ queue <queue> for XML output.

Explanation:

The Integration Service could not open the WebSphere MQ queue.

User Response:

Verify that the WebSphere MQ environment settings are correct, that the queue you specified
in the queue connection properties exists, and that the connection properties are valid.

XMLW_31059

Fatal error returned while closing XML document <target name> after incremental flush/
commit.

Explanation:

The Integration Server could not close the XML target file. The file might not have write
permissions or the path to the file is incorrect.

User Response:

Check previous error messages for more information.

XMLW_31060

Fatal error <error number> occurred while flushing XML output <target name>.

Explanation:

The XML Writer failed to write data to a target file.

Chapter 23: X Message Codes

User Response:

Check file write permissions, disk space, and that the path to the file exists. Check other error
messages for more information.

XMLW_31061

Fatal error <error number> occurred while closing XML document <target name>.

Explanation:

The XML Writer could not close the XML target file. The file might not have write permissions
or the path to the file is incorrect.

User Response:

Check previous error messages for more information.

XMLW_31063

Fatal error <error number> occurred while opening file list <target>.

Explanation:

The XML Writer failed to open the file list. The file might not have write permissions or the
path to the file is incorrect.

User Response:

Check the file write permissions, the directory path, disk space, or if the file exists.

XMLW_31064

Fatal error transferring local file <file name> into remote location <path> using FTP. The file
list will not be produced.

Explanation:

The Integration Service could not transfer the XML file by FTP to produce a file list at the
remote location.

User Response:

Verify FTP permissions, the directory path, network connections, and that the FTP server is
running.

XMLW_31065

Fatal error <error number> opening an FTP connection for a file list <file name>.

Explanation:

The Integration Service failed to open an FTP connection for a source using a file list.

User Response:

Verify FTP permissions, the directory path, network connections, and that the FTP server is
running. Check other error messages for more information.

XMLW_31066

Fatal error <error number> while generating file list.

Explanation:

The Integration Service failed to generate a file list. The file might not have write permissions
or the path to the file is incorrect.

User Response:

Check the file write permissions, the directory path, disk space, or if the file exists. Check
previous error messages for more information.

XMLW_31078

Error: Output XML on Flush/Commit option for the MQ session is no longer supported. Open
this mapping in the designer and edit the XML target instance. Change the value of On
Commit property to Create New Document.

Explanation:

You are using an upgraded MQ session that uses the Output XML on Flush/Commit attribute.
PowerCenter no longer supports this option.

User Response:

Open the mapping. Edit the XML target instance. Clear the Output XML on Flush/Commit
option. Choose the Create New Document option for the On Commit property.

XMLW_31079

Error: Unknown On Commit attribute value in target <target name>. Check repository for
possible corruption.

Explanation:

You are using an upgraded XML session that uses the Output XML on Flush/Commit
attribute. PowerCenter no longer supports this option.

User Response:

Open the mapping. Edit the XML target instance. Clear the Output XML on Flush/Commit
option. Choose the Create New Document option for the On Commit property.

XMLW Messages

467

468

XMLW_31080

Error: Orphans were encountered.

Explanation:

The Integration Service encountered child rows that have no parents in the XML Generator
transformation.

User Response:

To avoid failing a session with orphan rows, set the Orphan Row Handling session property
to Ignore. The Integration Service ignores the orphan rows.

XMLW_31086

Row <row number> in XML group <group> has more than one non-NULL hierarchical foreign
key value. This row will be dropped.

Explanation:

When a row has two possible parents, one of the foreign keys in the row must be NULL.

User Response:

None.

XMLW_31089

Error: The cache size <cache size> specified for XML target <target name> exceeds the 32-bit
address space. It cannot be more than <cache size> on a 32-bit server.

Explanation:

The XML Writer failed to write data to a target file.

User Response:

Check file write permissions, disk space, and that the path to the file exists. Check other error
messages for more information.

XMLW_31093

Error: Encountered an error while establishing type hierarchical relationship.

Explanation:

The session could not process XML data for a child view because there is no data for the
parent view.

User Response:

Check the data for inconsistencies, or change the mapping.

XMLW_31108

Error: An appropriate start row was not found for XML root group <group> with circular
reference. No output was generated.

Explanation:

If the data has multiple root rows with circular references, but none of the root rows has a null
foreign key, the Integration Service cannot find a start row.

User Response:

Verify the source data has one row going to the root that is not a child of another group.

Chapter 23: X Message Codes

XMLW_31110

Error: Duplicate row detected for single occurring group <group>, with parent group <parent
group>.

Explanation:

The Integration Service detected a duplicate row in a group.

User Response:

To avoid failing the session for duplicate rows, set the Duplicate Row Handling session
property to First Row or Last Row for the target.

XMLW_31118

Error: The FK field <foreign key> for the XML derived group <group> in XML Target <target
name> is not projected. No output rows for the group can be generated due to missing base
type information.

Explanation:

The session failed because the foreign key in a derived XML group has no data.

User Response:

Add a link to the foreign key in the mapping.

XMLW_31210

Fatal error transferring local file <file name> into remote location <path> using SFTP. The file
list will not be produced.

Explanation:

The Integration Service could not transfer the XML file by SFTP to produce a file list at the
remote location.

User Response:

Verify SFTP permissions, the directory path, network connections, and that the SFTP server
is running.

XMLW_31211

Fatal error opening remote list file <file name> using SFTP.

Explanation:

The Integration Service failed to open an SFTP connection for a source using a file list.

User Response:

Verify SFTP permissions, the directory path, network connections, and that the SFTP server
is running. Check other error messages for more information.

XMLW Messages

469

INDEX

E
error messages
TPTRD 384
TPTWR 390

470

The Long Journey to Software Valuation
From Everand
The Long Journey to Software Valuation
Dwight Olson
5/5 (2)
Getting Started: Informatica Powercenter (Version 9.1.0)
No ratings yet
Getting Started: Informatica Powercenter (Version 9.1.0)
122 pages
Getting Started with FortiGate
From Everand
Getting Started with FortiGate
Fabrizio Volpe
No ratings yet
PWX 951 CommandReference en
No ratings yet
PWX 951 CommandReference en
152 pages
PWX 951 UtilitiesGuide en
No ratings yet
PWX 951 UtilitiesGuide en
179 pages
PWX 910HF6 ReferccccenceManual en
No ratings yet
PWX 910HF6 ReferccccenceManual en
347 pages
PC 951HF1 GettingStarted en
No ratings yet
PC 951HF1 GettingStarted en
121 pages
DQ 951 PC Integration UserGuide en
No ratings yet
DQ 951 PC Integration UserGuide en
23 pages
PC 950 DataValidationOption UserGuide en
No ratings yet
PC 950 DataValidationOption UserGuide en
161 pages
DQ 951 Upgrade950 en
No ratings yet
DQ 951 Upgrade950 en
73 pages
DQ 951 InstallationAndConfigurationGuide en
No ratings yet
DQ 951 InstallationAndConfigurationGuide en
155 pages
DQ 951HF1 Analyst UserGuide en
No ratings yet
DQ 951HF1 Analyst UserGuide en
64 pages
Data Services User Guide
No ratings yet
Data Services User Guide
84 pages
PWX 910hf5 (CDC) Guidefor (I5os) en
No ratings yet
PWX 910hf5 (CDC) Guidefor (I5os) en
124 pages
User Guide: Informatica Data Quality (Version 9.5.1 Hotfix 1)
No ratings yet
User Guide: Informatica Data Quality (Version 9.5.1 Hotfix 1)
114 pages
DT_961_InstallationAndConfigurationQuickStartGuide_en
No ratings yet
DT_961_InstallationAndConfigurationQuickStartGuide_en
8 pages
DQ 951HF3 GettingStartedGuide en
No ratings yet
DQ 951HF3 GettingStartedGuide en
79 pages
System Performance Guidelines: Informatica Data Explorer and Informatica Data Quality (Version 9.5.0)
No ratings yet
System Performance Guidelines: Informatica Data Explorer and Informatica Data Quality (Version 9.5.0)
34 pages
PWX 951 (CDC) GuideForLinux (UNIX) AndWindows en
No ratings yet
PWX 951 (CDC) GuideForLinux (UNIX) AndWindows en
246 pages
PCX 961 GettingStartedGuide en
No ratings yet
PCX 961 GettingStartedGuide en
66 pages
DA 951 UserGuide en
No ratings yet
DA 951 UserGuide en
360 pages
In 100 TransformationLanguageReference en
No ratings yet
In 100 TransformationLanguageReference en
207 pages
User Guide: Informatica Data Quality Analyst (Version 9.5.0)
No ratings yet
User Guide: Informatica Data Quality Analyst (Version 9.5.0)
61 pages
In 100 ReferenceDataGuide en
No ratings yet
In 100 ReferenceDataGuide en
70 pages
Power Exchange Interfaces For Power Center
No ratings yet
Power Exchange Interfaces For Power Center
227 pages
MDM 960 Sif
No ratings yet
MDM 960 Sif
150 pages
New Features Guide: Informatica (Version 9.1.0)
No ratings yet
New Features Guide: Informatica (Version 9.1.0)
18 pages
Transformation Language Reference: Informatica Powercenter (Version 9.1.0)
No ratings yet
Transformation Language Reference: Informatica Powercenter (Version 9.1.0)
213 pages
New Features Guide: Informatica (Version 9.5.1 Hotfix 3)
No ratings yet
New Features Guide: Informatica (Version 9.5.1 Hotfix 3)
34 pages
PC 910 Adv Work Flow Guide en
No ratings yet
PC 910 Adv Work Flow Guide en
298 pages
PWX 100 JMSUserGuideForPowerCenter en
No ratings yet
PWX 100 JMSUserGuideForPowerCenter en
38 pages
DX 910 DeveloperGuide en
No ratings yet
DX 910 DeveloperGuide en
81 pages
Getting Started
No ratings yet
Getting Started
124 pages
In 100 AnalystToolGuide en
No ratings yet
In 100 AnalystToolGuide en
66 pages
MDM_971_Overview_en
No ratings yet
MDM_971_Overview_en
31 pages
Web ServicesProvider
No ratings yet
Web ServicesProvider
124 pages
MDM 950 MetadataManagerGuide en
No ratings yet
MDM 950 MetadataManagerGuide en
96 pages
MM 910 AdministratorGuide en
No ratings yet
MM 910 AdministratorGuide en
214 pages
DQ 100 AddressValidatorPortReference en
No ratings yet
DQ 100 AddressValidatorPortReference en
274 pages
Getting Started: Informatica Powercenter (Version 9.1.0)
No ratings yet
Getting Started: Informatica Powercenter (Version 9.1.0)
122 pages
PDF Informatica
No ratings yet
PDF Informatica
122 pages
PC 100 DesignerGuide en PDF
No ratings yet
PC 100 DesignerGuide en PDF
286 pages
MDM 1000 InstallationGuideFor (JBoss) MSSQL en
No ratings yet
MDM 1000 InstallationGuideFor (JBoss) MSSQL en
115 pages
Getting Started en
No ratings yet
Getting Started en
125 pages
Informatica PowerExchange v10.0 - Installation and Upgrade Guide
No ratings yet
Informatica PowerExchange v10.0 - Installation and Upgrade Guide
196 pages
PC 961 DesignerGuide en PDF
No ratings yet
PC 961 DesignerGuide en PDF
295 pages
PWX 100 SddalesforceUserGuideForPowerCenter en
No ratings yet
PWX 100 SddalesforceUserGuideForPowerCenter en
59 pages
MDM 1000 InstallationGuideForWebLogicMSSQL en
No ratings yet
MDM 1000 InstallationGuideForWebLogicMSSQL en
112 pages
XML Guide: Informatica Powercenter (Version 9.1.0)
No ratings yet
XML Guide: Informatica Powercenter (Version 9.1.0)
135 pages
XML Guide: Informatica Powercenter (Version 9.1.0)
No ratings yet
XML Guide: Informatica Powercenter (Version 9.1.0)
135 pages
DT 102 LibrariesGuide en
No ratings yet
DT 102 LibrariesGuide en
95 pages
PC_101_DesignerGuide_en
No ratings yet
PC_101_DesignerGuide_en
285 pages
DVO 100 UserGuide en
No ratings yet
DVO 100 UserGuide en
250 pages
In 100 NewFeaturesGuide en
No ratings yet
In 100 NewFeaturesGuide en
61 pages
In 100 ApplicationServiceGuide en
No ratings yet
In 100 ApplicationServiceGuide en
464 pages
PC 910 Web Services Provider Guide en
No ratings yet
PC 910 Web Services Provider Guide en
117 pages
Heaven Sent Me
From Everand
Heaven Sent Me
Mary Jinkens
No ratings yet
Open Source: Introduction & Outline of Office Suite
From Everand
Open Source: Introduction & Outline of Office Suite
Durgesh
No ratings yet
Software Suite: Revolutionizing Computer Vision with the Ultimate Software Suite
From Everand
Software Suite: Revolutionizing Computer Vision with the Ultimate Software Suite
Fouad Sabry
No ratings yet
Implementing SSL / TLS Using Cryptography and PKI
From Everand
Implementing SSL / TLS Using Cryptography and PKI
Joshua Davies
No ratings yet
Informatica Commandline Reference
No ratings yet
Informatica Commandline Reference
95 pages
Informatica 951 MessageReference
No ratings yet
Informatica 951 MessageReference
481 pages
OBIEE Metadata Development
No ratings yet
OBIEE Metadata Development
10 pages
BI Dashboard Design Common Pitfalls
No ratings yet
BI Dashboard Design Common Pitfalls
31 pages