In 901HF1 MessageReference
In 901HF1 MessageReference
In 901HF1 MessageReference
1 HotFix1)
Message Reference
Informatica Message Reference Version 9.0.1 HotFix1 September 2010 Copyright (c) 1998-2010 . 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 and Informatica On Demand 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 2007 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 Rouge 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. 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. This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. 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:// svn.dojotoolkit.org/dojo/trunk/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, and http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3license-agreement. 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) and the BSD License (http:// www.opensource.org/licenses/bsd-license.php). 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 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,254,590; 7,281,001; 7,421,458; and 7,584,422, 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 non-infringement, 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-90100-HF1-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
Table of Contents
ii
Table of Contents
Table of Contents
iii
iv
Table of Contents
Table of Contents
Preface
The Informatica Message Reference is written for all Informatica users. It contains troubleshooting information for all aspects of data warehouse development, including source analysis, transformation development, mapping development, and running sessions. This guide assumes you have knowledge about your operating systems, relational database concepts, and the interface requirements for your supporting applications.
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 infa_documentation@informatica.com. 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.
vi
Standard Rate Belgium: +32 15 281 702 France: 0805 804632 Germany: +49 1805 702 702 Netherlands: +31 306 022 797
Preface
vii
viii
CHAPTER 1
User Response:
Field <field name> is invalid because JMS source field does not allow NOTNULL.
Explanation: You wanted to import a repository object that represents a JMS source definition from an XML file. However, the specified field in the XML file is set to Not Null. The XML file may have been modified. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
If an XML file represents a JMS source definition, you must import it as a JMS source definition. You wanted to import a repository object that represents a JMS target definition from an XML file. However, you attempted to import an XML file that represents a JMS source. If an XML file represents a JMS target definition, you must import it as a JMS target definition. A header field is missing. The XML file may have been modified. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
User Response:
User Response:
User Response:
User Response:
User Response:
User Response:
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. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
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. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
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. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
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. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
User Response:
No output links found or no input link found for the output link.
Explanation: User Response: The mapping is not valid. Provide at least one output link for the Source Qualifier or provide input links for all the output links.
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.
Application source qualifier <application source qualifier name> has invalid Extract Date.
Explanation: User Response: You entered the Extract Date in the wrong date format. 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. 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.
User Response:
Application source qualifier <application source qualifier name> has projected port with no inbound link.
Explanation: User Response: The listed application source qualifier has a connected output port, and the corresponding input port is not connected. Connect the necessary input port or disconnect the connected output port.
Application Source Qualifier <application source qualifier name> has tree and Extract Override.
Explanation: User Response: 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. 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. Disconnect either the winter tree or the other sources from the application source qualifier.
User Response:
Application source qualifier <application source qualifier name> is not a valid PeopleSoft SQ
Explanation: User Response: The listed application source qualifier is invalid. See related error messages for more information.
Application Source Qualifier <application source qualifier name> sources are not related.
Explanation: User Response: You tried to connect or associate two unrelated sources in the listed application source qualifier. Disconnect one of the unrelated sources. Or, remove one of the associated source definitions. You can only connect or associate related sources in an application source qualifier.
Application source qualifier <application source qualifier name> tree is joined with non-detail source.
Explanation: User Response: 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. 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 an imported tree, open the tree source definition in the Mapping Designer and click on the Attributes tab.
The language code <language code> specified is either invalid or not configured on the current PeopleSoft system.
Explanation: 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: User Response: The language code you entered in the Import from PeopleSoft dialog box is not a valid PeopleSoft language code or is not registered with the PeopleSoft system. Enter a valid PeopleSoft language code.
DescribeSObject <object name> failed. Error code: <error code> Reason: <error message>.
Explanation: User Response: The Designer could not retrieve the field list and object properties for the object. 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. 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.
User Response:
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. Associate each source definition in the mapping with a single Application Source Qualifier transformation.
User Response:
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: User Response: Explanation: You tried to import a hierarchy definition that is empty. The hierarchy has no nodes. Import a hierarchy definition that contains nodes. You selected to import some SAP functions that you have already imported in the repository.
User Response:
Select SAP functions that you have not already imported in the repository.
In the Application Source Qualifier <Application Source Qualifier name>, as Exec SQL option is selected Outer Joins are not allowed.
Explanation: User Response: You joined sources with an outer join and selected to generate the ABAP program using exec SQL. 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: User Response: You cannot have a space in an operator, such as < =. 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: User Response: Explanation: User Response: The source table specified to the left of the condition is not part of the condition. Edit the condition so that the source table specified to the left of the condition is also specified in the condition. You have an invalid source table name or field name in the filter condition. Verify all source table and field names.
In filter expression for <Application Source Qualifier name>: <filter condition>; <token>: constant or literal has to follow an operator.
Explanation: User Response: You cannot have a space in an operator, such as < =. Edit the filter expression and remove the space from the operator.
In Application Source Qualifier <Application Source Qualifier name>, as reverted to Nested Loop Outer Joins are not allowed.
Explanation: User Response: You selected the Outer Join option in the ABAP program flow when the mapping contains pool or cluster tables. Select Force Nested Loop in the Properties tab in the Application Source Qualifier.
Warning: Join Override for the first source <source> will be ignored. No syntax error detected.
Explanation: User Response: The qualifying table is not the outer most table of the join order. 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.
In the function <SAP function name> the value of the variable <variable name> does not match with the function parameter <parameter name>.
Explanation: User Response: 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. Click the Variables button in the ABAP program flow and modify the variable value to match the function parameter.
10
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: User Response: You removed the variable that you assigned to the function parameter. Click the Variable button in the ABAP program flow and define the variable again.
User Response:
Error obtaining program name from destination <connect string> for mapping <mapping name>.
Explanation: User Response: RFC error. Contact the SAP administrator.
Error opening selected ABAP file with associated file viewer or Notepad.exe.
Explanation: User Response: You do not have the file type associated with a viewer. Associate the file type .ab4 with the Wordpad or Notepad viewer.
11
In Application Source Qualifier <Application Source Qualifier name>, for ABAP join syntax, source <source name> cannot be outer joined multiple sources.
Explanation: User Response: You joined multiple sources using outer join. Edit the ABAP program flow so that you only join two sources with outer join.
User Response:
Code generation for mapping <mapping name> failed. WARNING: No program was generated as mapping contains only SAP Info Hierarchies.
Explanation: User Response: You tried to generate an ABAP program for a mapping containing a hierarchy only. You do not need to generate an ABAP program for mappings with hierarchies only. You can run the session without an ABAP program.
Code generation is not allowed for a shortcut to a mapping. Code generation for mapping <mapping name> failed.
Explanation: User Response: You tried to generate or install an ABAP program from a shortcut mapping. Generate the ABAP program from the original instance of the mapping, or make a copy of the mapping to the folder.
Extraction of Info Hierarchies is not allowed in Stream Mode. Code Generation for mapping <mapping name> failed.
Explanation: User Response: You tried to generate a stream mode ABAP program for a mapping that contains a hierarchy and a table. You can only use file mode for mappings that contain hierarchies and tables. Generate the ABAP program using file mode.
For Application SQ <Application Source Qualifier name>, Select Single option is ignored as all the sources dont have select single option in ABAP join mode.
Explanation: User Response: You cannot use the Select Single option and generate the ABAP program using Exec SQL or ABAP join syntax. Clear the Select Single option and generate the ABAP program again.
12
For Application SQ <Application Source Qualifier name>, Select Distinct option is ignored as all the sources dont have Select Distinct option in Exec SQL mode.
Explanation: User Response: You did not choose Select Distinct for all the sources connected to the Application Source Qualifier. Choose Select Distinct for each source connected to the Application Source Qualifier. Generate the ABAP program again.
For Application SQ <Application Source Qualifier name>, Select Distinct option is ignored as all the sources dont have Select Distinct option in ABAP join mode.
Explanation: User Response: You did not choose Select Distinct for all the sources connected to the Application Source Qualifier. Choose Select Distinct for each source connected to the Application Source Qualifier. Generate the ABAP program again.
Invalid entry. ABAP Program name should start with 'Y' or 'Z.' Operation canceled. No code generated for mapping <mapping name>.
Explanation: User Response: You entered an ABAP program name that does not start with 'Y' or 'Z.' Generate or install the ABAP program again and enter a program name that starts with 'Y' or 'Z.'
Only variable ports are projected from an Application SQ. Code generation requires that at least one source field to be projected out.
Explanation: User Response: You have only variable ports in the Application Source Qualifier. Create at least one output field in the Application Source Qualifier.
The ABAP program name is empty. No code generated for mapping <mapping name>.
Explanation: User Response: You did not enter a program name. Generate or install the ABAP program again and enter the program name in the ABAP Program Name dialog box.
The source <source name> does not have a join condition with any of the sources above it.
Explanation: User Response: You did not select a table you want to join using ABAP join syntax. Select the table you want to join in the Source(s) To Join To section of the ABAP Program Flow dialog box.
There are no fields projected out from an Application SQ for which code generation is required in mapping <mapping name>.
Explanation: You tried to generate or install an ABAP program for a mapping with an Application Source Qualifier that is not connected to other transformations.
13
User Response:
Connect the output ports in the Application Source Qualifier to another transformation or target instance. Then generate an ABAP program.
There is no program generation information for program found in the repository. This program may be generated from other repository.
Explanation: User Response: You tried to install an ABAP program from an invalid file or a file that was generated from another repository. 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: User Response: You tried to generate an ABAP program for a mapping that contains more than one hierarchy definition in a single Application Source Qualifier. 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: User Response: You tried to join two IDocs in one Application Source Qualifier. Remove other IDocs in the Application Source Qualifier.
14
Error: No name for the imported SAP function instance parameter field.
Explanation: User Response: You edited the XML file and deleted a function name or other function information. Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping and import it again.
15
User Response:
Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping and import it again.
16
The SAP code page <code page> is not compatible with the Designer's code page.
Explanation: User Response: The SAP code page and Designer code page are not compatible. Connect to an SAP system with a code page that is compatible with the Designer code page.
Found the tag <tag(s)> while expecting the tag <tag(s)>. Use a valid DMI file.
Explanation: User Response: You attempted to import an invalid DMI file. Import a valid DMI file.
17
18
User Response:
User Response:
19
Attributes <attribute> is ignored. Another sibling attribute with the same name already exists.
Explanation: This is an informational message. You connected to a TIB/Repository instance to display metadata to import a TIBCO source or target definition. The PowerCenter Designer ignored the specified attribute from the TIB/Repository instance because the PowerCenter Designer found an identical attribute in the TIB/Repository instance. For example, the class ADDRESS in the TIB/Repository instance contained two attributes with the name STREET. The PowerCenter Designer displays only one of these attributes when you view the list of attributes in the Import TIBCO Metadata dialog box. None.
User Response:
Conversion from TIBCO source <source> to TIBCO target failed: <error message>.
Explanation: You tried to drag the specified TIBCO source definition to the Target Designer. The source definition may contain both a subgroup and a field from the subgroup as columns in the source definition. This is not allowed for target definitions. Remove one of the fields in the source definition before dragging it to the Target Designer.
User Response:
Field <field> has invalid map value <map value> based on the source/target's metadata.
Explanation: User Response: You wanted to import a TIBCO source or target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Import the TIBCO source or target definition from a new XML object.
For TIBCO targets, a non-header field cannot coexist with any of its direct/indirect parent groups in the TIBCO metadata tree.
Explanation: 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. If you want to add a group to a target definition, do not add any fields from the group to the target definition.
User Response:
20
Metadata is invalid. Non-empty TIBCO source/target must have one metadata group.
Explanation: User Response: You wanted to import a TIBCO source or target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Import the TIBCO source or target definition from a new XML object.
User Response:
User Response:
Unexpected error happened when trying to retrieve metadata from TIBCO Repository.
Explanation: User Response: Internal error. Contact Informatica Global Customer Support.
21
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. Make sure that any document types you want to import as webMethods source or target definitions contain fields that use datatypes that PowerCenter supports.
User Response:
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.
Importing webMethods source from document type <document type name> failed.
Explanation: User Response: The Designer could not import the webMethods source definition. See the additional error message for more information.
Importing webMethods target from document type <document type name> failed.
Explanation: User Response: The Designer could not import the webMethods target definition. See the additional error message for more information.
Importing failed. PowerCenter Connect for webMethods was not installed correctly.
Explanation: User Response: The Designer could not import the source or target definition, because PowerExchange for webMethods is not properly installed. Reinstall PowerExchange for webMethods.
22
User Response:
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. Import the repository object from a new XML file. Avoid editing the XML file before importing.
User Response:
User Response:
Invalid SOAP Request. Body cannot have more than one operation.
Explanation: User Response: The SOAP request contains a request for more than one web service operation. Reimport the web service operation and run the session again. Use a third-party 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.
23
Invalid SOAP Request. The SOAP Operation parameters in the request are inconsistent with the WSDL file.
Explanation: User Response: The SOAP request contains parameters for the web service operation that you want to import that the WSDL file does not describe. 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.
24
The operation you selected contains multiple namespaces - which is not supported. Please select another operation.
Explanation: You tried to import a web service operation from a WSDL file that specifies RPC encoding and a namespace that differs from the target namespace. If the WSDL file specifies RPC encoding, the namespace that the SOAP body specifies must match the target namespace. Choose another web service operation to import.
User Response:
Unable to delete links from an MQ Source Qualifier transformation to an associated source qualifier transformation.
Explanation: User Response: You tried to delete the link between MQ Source Qualifier and the associated source qualifier. 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.
25
User Response:
Connect an MQSeries, VSAM, or XML source definition to only one Source Qualifier or Normalizer transformation.
XML Messages
<Column name> cannot be pivoted since it is a key column.
Explanation: User Response: You tried to pivot a column designated as a primary key. Select another column to pivot. You cannot pivot a column that is designated as a primary key.
Cannot change cardinality! The selected cardinality will cause groups <group names> to be invalid.
Explanation: User Response: You tried to change the cardinality of an element that invalidates the group. You cannot change the cardinality of an element if it violates the structure defined in the associated DTD or XML schema.
Denormalized group cannot be created since XML Element/Attribute <column name> has a many to many relationship with XML Element/Attribute <column name>.
Explanation: User Response: You have at least two multiple-occurring element in the group with a many-to-many relationship. You cannot put more than one multiple-occurring element with a many-to-many relationship in the same group. The multiple-occurring elements in a denormalized group must have a one-to-many relationship.
Element/Attribute <element or attribute name> occurs only once and cannot be pivoted.
Explanation: User Response: You tried to pivot an element that occurs only once. This is a warning. It is not necessary to pivot a column that occurs only once. You can proceed with the action if you are sure you want to pivot the column.
Group <group> cannot be related to group <group>. Related groups should be under the same XML tree branch.
Explanation: User Response: You tried to set a foreign key to relate to the primary key of a group that is lower on the parent chain than the current group. Relate to another primary key. You can only set a foreign key to relate to the primary key of a group that is higher in the parent chain than the current group.
A key <column name> already exists at this level. <column name> has a one-one correspondence with <column name>.
Explanation: User Response: You tried to add a key to a hierarchy level that already has a key. You cannot have more than one key for one hierarchy level.
Only leaf elements can be pivoted. <column name> refers to a non-leaf element <element name> and cannot be pivoted.
Explanation: You tried to pivot a column that points to an element that is not a leaf element.
26
User Response:
Select another column to pivot. You can pivot only attributes and leaf elements.
Only one reference port can reference a pass-through port in an XML Generator transformation.
Explanation: User Response: More than one reference port is referencing the same pass-through port. Remove the duplicate reference ports.
The XML file has fewer elements than the pivot value specified. Element <element name> appears only <number> times in the XML file.
Explanation: User Response: The pivot value you set is larger than the number of times the element appears in the XML file you are importing from. This is a warning. You can proceed with the action if you know that the pivot value will match the number of times the element appears in the source XML file when you run the session.
You cannot have a pivoted column and an unpivoted column referring to the same element. Column <column name> is pivoted while column <column name> is not.
Explanation: User Response: You have a pivoted and an unpivoted column in one group pointing to the same element. 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
27
CHAPTER 2
User Response:
The Domain Service could not disable the process due to the following error: <error message>.
Explanation: User Response: 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. 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: User Response: 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. 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.
28
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. 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.
User Response:
Enter a valid location for the shared configuration on the node <node name>.
Explanation: User Response: No location was supplied for the shared configuration file. Enter the storage location for the shared configuration file.
The following error occurred while attempting to remove the node. Error - <error message>.
Explanation: The Service Manager could not remove the node from the domain. A problem may have occurred when the Service Manager attempted to abort the processes running on the node. The Service Manager may have encountered a problem when shutting down the node. Also, a problem may have occurred when the Service Manager attempted to remove the node from the domainmeta.xml file. Read the error description and make any necessary changes. For more information, look up the cause and action for the error code.
User Response:
The following error occurred while attempting to remove the service. Error - <error message>.
Explanation: User Response: The Service Manager could not remove the service. Read the error description and make any necessary changes. For more information, look up the cause and action for the error code.
The following error occurred while attempting to shut down the node. Error - <error message>.
Explanation: User Response: The Service Manager could not shut down the node. Read the error description and make any necessary changes. For more information, look up the cause and action for the error code.
The following error occurred while enabling this service. Error - <error message>.
Explanation: 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.
29
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.
This key was already used to update the license. Please use another key for the update.
Explanation: User Response: The same key cannot be used more than once to update a license. 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: User Response: 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. 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: User Response: The Service Manager could not export logs for a query. 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: User Response: The Service Manager could not fetch logs for the query. 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: User Response: The Service Manager could not purge logs for a query. 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. 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.
User Response:
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.
30
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: User Response: The nodes you designated as gateway nodes have been shut down. 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: User Response: All domains require at least one gateway node. You cannot remove a gateway node if it is the only gateway in the domain. If you have the high availability option, create another gateway node for the domain before removing this gateway.
31
CHAPTER 3
ADV Messages
ADV_13226
Explanation: User Response:
Could not open the following dll: <dynamic link library name>.The reason is: <error message>.
The Integration Service cannot load an external Custom transformation library that is dependent on other libraries. See the additional error message for more information.
ALERT Messages
ALERT_10000
Explanation: User Response:
ALERT_10001
Explanation: User Response:
32
ALERT_10002
Explanation: User Response:
ALERT_10003
Explanation: User Response:
ALERT_10004
Explanation: User Response:
Unable to send alert of type <alert type> for object <object name>, alert message <alert message>, with error <error message>.
Unable to send the referenced alert. Verify that the SMTP connectivity and user email information are correct in the domain.
ALERT_10010
Explanation: User Response:
Unable to remove the user <user name> from the alert service.
Unable to remove the alert user. Verify that the master gateway node is running on the domain.
ATHR Messages
ATHR_10000
Explanation: User Response:
ATHR_10003
Explanation: User Response:
ATHR_10006
Explanation: User Response:
ATHR_10007
Explanation: User Response:
A request was received with wrong <actual object type> parameter (expected: <expected object type>).
A request was received that had the wrong type of parameter. If the problem persists, contact Informatica Global Customer Support.
ATHR Messages
33
ATHR_10010
Explanation: User Response:
The Service Manager could not find <type of object> <object name>.
A request was received to authorize access to an object that could not be located. If the problem persists, contact Informatica Global Customer Support.
ATHR_10011
Explanation: User Response:
The Service Manager requires <expected parameter count> parameters within message but received <actual parameter count> parameters.
A request was received with the wrong number of parameters. If the problem persists, contact Informatica Global Customer Support.
ATHR_10012
Explanation: User Response:
The Service Manager denied authorization access to <type of object> <object name>.
A user was trying to access an object without proper permissions. The user should only access objects where permission was granted.
ATHR_10013
Explanation: User Response:
The Service Manager cannot process <type of object> authorization access object type.
A request was received on an unknown type of object. If the problem persists, contact Informatica Global Customer Support.
ATHR_10014
Explanation: User Response:
The Service Manager for domain <this domain> received an authorization request for another domain <other domain>.
This domain received a request to authorize an object on another domain. If the problem persists, contact Informatica Global Customer Support.
ATHR_10015
Explanation: User Response:
The Service Manager received an external request to execute an internal operation by <the source of the credential used>.
An internal request was received by an unauthorized sender. Verify that the domain is secure from unauthorized users.
ATHR_10017
Explanation: User Response:
The Service Manager received an authorization request which did not contain a credential.
A request was received that did not have credential. Log in again or wait until after master elections are finished.
ATHR_10018
Explanation: User Response:
The Service Manager cannot process authorization <type of activity> activity type.
A request was received for an unknown activity type. If the problem persists, contact Informatica Global Customer Support.
ATHR_10019
Explanation: User Response:
The Service Manager denied authorization access to read-only user <user name> attempting to modify <type of object> <object name>.
A user was trying to modify an object without proper permissions. The user can read objects where permission was granted.
ATHR_10021
Explanation:
The Service Manager denied authorization access to user <user name> attempting to access <type of object> <object name>.
A user was trying to access an object outside of the repository logs.
34
User Response:
Users can only access objects with reference to the repository they logged in to.
ATHR_10022
Explanation: User Response:
The Service Manager denied authorization access for user <user name> as service\folder is wrongly specified: <service and folder>.
A user was trying to access a service and folder that was not specified correctly. If the problem persists, contact Informatica Global Customer Support.
ATHR_10023
Explanation: User Response:
The Service Manager denied authorization access for user <user name> as service <service name> is not found.
A user was trying to access a service not referenced in this domain. Make sure that no changes have occurred with services in this domain.
ATHR_10024
Explanation: User Response:
The Service Manager denied authorization access for user <user name> as request was for the wrong type of service <service type>.
A user was trying to access an invalid service type. If the problem persists, contact Informatica Global Customer Support.
ATHR_10025
Explanation: User Response:
The Service Manager denied authorization access for user <user name> as request was for another domain <domain name>.
A user was trying to access another domain. If the problem persists, contact Informatica Global Customer Support.
ATHR_10026
Explanation: User Response:
User <user name> does not have permission to access another user in the domain.
A user trying to access another user does not have adequate permission. The user should ask the domain administrator to perform desired request.
AUTH Messages
AUTH_10000
Explanation: User Response: Explanation: User Response: Explanation: User Response:
The Service Manager could not enable Authentication because authentication state is invalid.
The network shared disk that stores the domain configuration data is not accessible. Ensure access to the shared disk that stores the domain configuration database. Node configuration is not synchronized with the domain configuration. Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix the node configuration with infacmd. Authentication configuration has invalid data. Contact Informatica Global Customer Support. Before restoring the domain configuration database from the last known good backup file, back up the invalid domain configuration database to another file to help Informatica Global Customer Support troubleshoot the problem.
AUTH Messages
35
AUTH_10001
Explanation: User Response:
AUTH_10005
Explanation: User Response:
AUTH_10007
Explanation: User Response:
AUTH_10009
Explanation: User Response:
AUTH_10010
Explanation: User Response:
Cannot encrypt the credential because the characters in the user name, password, or domain name are not UTF-8 compliant.
User name, password, or domain name contain characters that are not UTF-8 compliant. Ensure that the user name, password, and domain name contain characters that are UTF-8 compliant.
AUTH_10011
Explanation: User Response: Explanation: User Response: Explanation: User Response:
AUTH_10014
Explanation: User Response:
36
AUTH_10015
Explanation: User Response:
A request for operation <operation name> required input that was not supplied.
The input required by the operation was not provided. Contact Informatica Global Customer Support.
AUTH_10016
Explanation: User Response:
AUTH_10018
Explanation: User Response:
A request for operation <operation name> expected input of type <expected input type>, but was supplied with <actual input type>.
Authentication did not receive the required input. Contact Informatica Global Customer Support.
AUTH_10019
Explanation: User Response:
AUTH_10022
Explanation: User Response:
AUTH_10023
Explanation: User Response:
AUTH_10024
Explanation: User Response:
Message request failed because the message contained invalid credentials that were not recognized by the system.
The message request contained invalid credentials. 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
Explanation: User Response:
The thread was interrupted while associating node <node name> with the domain.
A problem occurred with threads while associating a node. Try again. If the problem persists, then contact Informatica Global Customer Support.
AUTH_10027
Explanation: User Response:
The user <user name> associated with node <node name> was not found in the domain.
The user specified in the node was not found in the domain. Either add the user in the domain or redefine node with a user.
AUTH Messages
37
AUTH_10028
Explanation: User Response:
AUTH_10029
Explanation: User Response:
AUTH_10030
Explanation: User Response:
User <user name> was not associated with node <node name>.
The user specified in the node configuration does not match the domain configuration. Either modify the user in the domain node or redefine node with the same user as the domain node.
AUTH_10031
Explanation: User Response: Explanation: User Response:
The host name for node <node name> is inconsistent between node configuration and domain configuration.
The node configuration is incorrect. Redefine the node. The node is defined twice. Create a node with a different name.
AUTH_10032
Explanation: User Response: Explanation: User Response:
The port number for node <node name> is inconsistent between node configuration and domain configuration.
The node configuration is incorrect. Redefine the node. The node is defined twice. Create a node with a different name.
AUTH_10033
Explanation: User Response:
The gateway setting for node <node name> is inconsistent between node configuration and domain configuration.
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. 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
Explanation: User Response:
User <user name> does not have permission on any object within the domain.
The user trying to log in does not have any permission within the domain. The user should ask the domain administrator to add permissions for the user or remove the user.
AUTH_10037
Explanation:
Domain <domain name> for Repository Service <Repository Service name> is not linked within this domain.
The user trying to log in through this domain for service not used within this domain.
38
User Response:
The user should log directly in to the Repository Service domain or define the link.
AUTH_10038
Explanation: User Response:
Repository Service <Repository Service name> is not defined or referenced within this domain.
The requested service is not known within this domain. The user should select a Repository Service known to this domain.
AUTH_10039
Explanation: User Response:
Repository Service <Repository Service name> is defined in multiple known domains <list of domains>.
Repository services with the same name exist in multiple domains. The user must also specify the requested domain.
AUTHEN Messages
AUTHEN_10001
Explanation: User Response:
The Service Manager failed to authenticate user <user name> in security domain <security domain name>. The user is disabled.
A disabled user tried to log in. Enable the user account.
AUTHEN_10002
The Service Manager failed to authenticate LDAP user <user name> in security domain <security domain name>. The LDAP server failed to authenticate the user with the error <LDAP error message>.
The LDAP server could not authenticate the user. Check the error message from the LDAP server for more information.
AUTHEN Messages
39
CHAPTER 4
BAPI Messages
BAPI_99101
Explanation: User Response:
BAPI_99102
Explanation: User Response:
None of the parameters of function <function name> has been selected as STATUS RETURN structure.
No parameter of the specified function is selected as the RETURN structure status in the BAPI/RFC transformation. Specify a RETURN structure for the table export parameters.
BAPI_99103
Explanation: User Response:
Function RETURN parameter is specified. However, only <number> out of <number> required values found when parsing the property value string.
The Integration Service could not find valid return values for the function return parameter when parsing the property value string. Enter valid return values in the function return parameter.
BAPI_99105
Explanation: User Response:
STATUS or TEXT field of RETURN parameter must have ABAP type CHAR or NUMC.
The ABAP datatype in the status or text field for the RETURN parameter in the BAPI/RFC transformation is not CHAR or NUMC. Set the ABAP datatype to CHAR or NUMC in the status or text field for the RETURN parameter in the BAPI/RFC transformation.
40
BAPI_99106
Explanation: User Response:
Could not find the STATUS field [{0}] in the RETURN structure.
A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC transformation. Specify a valid value in the status field for the RETURN structure in the BAPI/RFC transformation.
BAPI_99107
Explanation: User Response:
Could not find the TEXT field [{0}] in the RETURN structure.
A valid value in the text field for the return structure is not specified in the BAPI/RFC transformation. Specify a valid value in the text field or the return structure in the BAPI/RFC transformation.
BAPI_99109
Explanation:
Could not read the internal table for the function table parameter.
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. Export and import the BAPI/RFC transformation again.
User Response:
BAPI_99113
Explanation: User Response:
Exception <exception> has been raised from the RFC function call with IntegrationID <integration_ID>.
The RFC call to the SAP system from the SAP application server failed. Enter valid input data for the SAP system. Verify that the SAP application server is running.
BAPI_99116
Explanation: User Response:
The Integration Service could not create an SAP internal table for function table parameter [{0}].
The Integration Service could not create an SAP internal table. The node where the Integration Service process runs might be out of memory. Verify that the machine on which the node resides has enough memory.
BAPI_99118
Explanation: User Response:
The Integration Service could not find field [{0}] in the RETURN structure.
A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC transformation. Specify a valid value in the status field for the RETURN structure in the BAPI/RFC transformation.
BAPI_99129
Explanation: User Response:
BAPI_99133
Explanation: User Response: Explanation: User Response:
BAPI Messages
41
BAPI_99135
Explanation:
Data overflow occurred when the Integration Service applied default value <value> to function parameter <function parameter name> for Integration ID <ID number>.
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. Verify that the value complies with the metadata of the parameter.
User Response:
BAPI_99136
Explanation:
Data <data> overflow at port <port number> for Integration ID <ID number>.
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. Verify that the value complies with the metadata of the parameter.
User Response:
BAPI_99138
Explanation: User Response: Explanation: User Response:
Data conversion error for port <port number> with data <data>.
The SAP system might have sent data with a precision or scale that does not comply with the parameter metadata. Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port. The data contains inconsistencies. Contact Informatica Global Customer Support.
BAPI_99139
Explanation: User Response: Explanation: User Response:
BAPI_99140
Explanation: User Response: Explanation: User Response:
The Integration Service could not retrieve metadata for parameter <parameter name> of RFC function <function name> from SAP.
The SAP system may not contain the metadata for the specified parameter. See the additional error message for more information. The Integration Service could not connect to the SAP system. Verify the connection parameters in the RFC/BAPI application connection. Or, verify that the Integration Service and SAP systems are running. See the additional error message for more information.
42
BR Messages
BR_16001
Explanation: User Response:
BR_16002
Explanation: User Response:
BR_16004
Explanation: User Response: Explanation: User Response:
BR_16009
Explanation: User Response:
BR_16034
Explanation: User Response:
BR_16036
Explanation: User Response:
BR_16037
Explanation: User Response:
BR_16038
Explanation: User Response:
BR Messages
43
BR_16045
Explanation: User Response:
Reader run terminating. Error threshold <maximum number of errors> reached reading data from <file name>.
The Integration Service reached the error threshold reading data from a source file. See the previous error in the session log.
BR_16046
Explanation: User Response:
User defined query <query name> has references to mapping parameters or variable that cannot be resolved correctly.
The Integration Service encountered an error while expanding referenced parameters and variables in the specified query. Make sure you declare the parameters and variables in the specified query and have valid start values.
BR_16047
Explanation: User Response:
User defined join condition and/or source filter <condition name> has references to mapping parameters or variable that cannot be resolved correctly.
The Integration Service encountered an error while expanding referenced parameters and variables in the specified join or filter condition. Make sure you declare the parameters and variables in the specified join or filter condition and have valid start values.
BR_16048
Explanation: User Response:
User defined source filter condition <condition name> has references to mapping parameters or variables that cannot be resolved correctly.
The Integration Service encountered an error while expanding parameters and variables in the specified filter condition. Make sure you declare the parameters and variables in the specified string and that they have valid start values.
BR_16050
Explanation: User Response:
User provided string <string value> has references to mapping parameters or variables that cannot be resolved correctly.
The Integration Service encountered an error while expanding parameters and variables in the specified string. Make sure you declare the parameters and variables in the specified string and that they have valid start values.
BR_16056
Explanation: User Response:
BTree Messages
BTree_90002
Explanation: User Response:
Error: Specified cache size is too small. It must be larger than <size>.
The session failed because the cache size specified for the transformation is insufficient. In the session properties, increase the cache size.
44
BTree_90004
Explanation: User Response: Explanation: User Response:
BTree_90005
Explanation: User Response:
BTree_90006
Explanation: User Response:
BTree_90007
Explanation: User Response:
BTree_90009
Explanation: User Response:
BTree_90010
Explanation: User Response: Explanation: User Response:
Error locking cache block in group <group>. Increase the cache size.
The session failed because the cache size specified for the transformation is insufficient. In the session properties, increase the cache size. The cache directory has inadequate disk space. Check the disk for free space.
BTree_90011
Explanation: User Response: Explanation: User Response:
Error inserting a row into the foreign key index for group <group>.
The Integration Service does not have write permission on the cache directory. Verify that the user configured to start Informatica services has write permission on the cache directory. The cache directory has inadequate disk space. Check the disk for free space.
BTree_90012
Explanation:
Error inserting a row into the primary key index for group <group>.
The Integration Service does not have write permission on the cache directory.
BTree Messages
45
Verify that the user configured to start Informatica services has write permission on the cache directory. The cache directory has inadequate disk space. Check the disk for free space.
BTree_90013
Explanation: User Response: Explanation: User Response:
BTree_90014
Explanation: User Response: Explanation: User Response: Explanation: User Response:
BW Messages
BW_41013
Explanation: User Response:
Cannot connect to Integration Service <Integration Service name> in domain <domain name>.
The connection setting for the Integration Service is incorrect. Verify that the Integration Service is running. Check the user name, password, hostname, and port number settings for the Integration Service.
BW_41014
Explanation: User Response:
The BW Server sent a request to the SAP BW Service that did not include a PowerCenter workflow name.
The 3rd Party Selection tab of the InfoPackage does not include a PowerCenter workflow name. Specify a PowerCenter workflow name in the 3rd Party Selection tab of the InfoPackage.
BW_41020
Explanation: User Response:
46
BW_41027
Explanation: User Response:
The Integration Service could not prepare the data in row number <row number> for the BW target <target name>.
The source data contains invalid data for the row. Correct the source data so that it matches the datatype, scale, and precision for the fields in the target definition.
BW_41031
Explanation: User Response:
The SAP BW Service could not open the parameter file <parameter file> for data selection: <data selection>.
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. 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.
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. 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>.
Explanation:
User Response:
BW_41052
Explanation: User Response:
BW_41058
Explanation: User Response:
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.
The SAP BW Service tried to connect to the SAP NetWeaver BI system five times without succeeding. Verify that the saprfc.ini file is configured correctly.
BW_41065
Explanation: User Response:
BW_41073
Explanation: User Response:
BW Messages
47
BW_41076
Explanation: User Response:
BW_41077
Explanation: User Response:
BW_41082
Explanation:
The SAP BW Service could not find the Integration Service <Integration Service name> in domain <domain name>.
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. In the SAP NetWeaver BI system, verify that the domain and Integration Service name entered in the 3rd Party Selection tab are valid. The Integration Service might not be enabled. Verify that the Integration Service is enabled.
48
CHAPTER 5
CFG Messages
CFG_10000
Explanation: User Response: Explanation: User Response: Explanation: User Response:
The Service Manager could not enable Domain Configuration because the domain state is invalid.
The network shared disk that stores the domain configuration database is not accessible. Ensure access to the shared disk that holds the domain configuration database. Node configuration is not synchronized with the domain configuration. Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix the node configuration with infacmd. Domain configuration database has invalid data. Before restoring the domain configuration database from the last known good backup file, back up the invalid domain configuration database to another file to help Informatica Global Customer Support troubleshoot the problem.
CFG_10001
Explanation: User Response:
CFG_10005
Explanation:
The Service Manager is disabled and cannot accept domain configuration requests.
The Service Manager on the master gateway node experienced a problem and disabled itself.
49
User Response:
Wait for a new master gateway node to be elected. The new master gateway node will enable its Service Manager. If a new master gateway node does not come up automatically, manually recycle this node.
CFG_10008
Explanation: User Response:
CFG_10009
Explanation: User Response:
A request was received with wrong <actual object type> parameter (expected: <expected object type>).
A request was received that had the wrong type of parameter. If the problem persists, contact Informatica Global Customer Support.
CFG_10012
Explanation: User Response:
CFG_10013
Explanation: User Response:
CFG_10014
Explanation: User Response:
CFG_10015
Explanation: User Response:
CFG_10017
Explanation: User Response:
Cannot delete domain node <node name> because it is the only gateway in the domain.
A request was received to delete the last gateway in the domain. Select or create another node to be a gateway before continuing.
CFG_10018
Explanation: User Response:
CFG_10019
Explanation: User Response:
50
CFG_10020
Explanation: User Response:
Cannot change list of nodes associated with Integration Service <service name> while the service is enabled.
A request was received to change nodes to grid, grid to nodes, or one grid to another grid on an enabled Integration Service. Disable the service prior to making this type of change.
CFG_10021
Explanation: User Response: Explanation: User Response:
The Service Manager failed to read the domain configuration from <database type> database on <database host>:<database port> with error <error message>.
The Service Manager failed to read the domain configuration from the database. Ensure the database connectivity information specified for the domain is correct. Domain configuration database has invalid data. Contact Informatica Global Customer Support. Before restoring the domain configuration database from the last known good backup file, back up the invalid domain configuration database to another file to help Informatica Global Customer Support troubleshoot the problem.
CFG_10022
Explanation: User Response:
Cannot associate service <service name> with repository because: <reason of failure>.
An attempt to associate a service with a repository failed. Fix the listed error before attempting again.
CFG_10023
Explanation: User Response:
Cannot unassociate service <service name> with repository because: <reason of failure>.
An attempt to unassociate a service with a repository failed. Fix the listed error before attempting again.
CFG_10025
Explanation: User Response:
Cannot delete grid <grid name> because it is referenced by these services: <list of services>.
A request was received to delete a grid that is referenced by services. Assign the listed services to other grids or nodes before continuing.
CFG_10026
Explanation: User Response:
Grid <grid name> contains nodes <list of nodes> that are not defined in the domain.
A request was received to include nodes in a grid that do not exist. Use only existing nodes while modifying the grid.
CFG_10027
Explanation: User Response:
CFG_10028
Explanation: User Response:
Cannot delete linked domain <linked domain name> because it is referenced by these services: <list of services>.
A request was received to delete a linked domain that is referenced. Move the listed services to another domain.
CFG_10029
Explanation:
CFG Messages
51
User Response:
CFG_10030
Explanation: User Response:
Cannot add <object name> because the name is already in use within the domain.
A request was received to add an object whose name is in use. Select an object name that is not in use.
CFG_10031
Explanation: User Response:
CFG_10032
Explanation: User Response:
CFG_10033
Explanation: User Response:
CFG_10037
Explanation: User Response:
Cannot delete license <license name> because services are assigned to it.
A request was received to delete a license that has services assigned to it. Move the assigned services to another license.
CFG_10040
Explanation: User Response:
Cannot add linked domain <linked domain name> because it has the same name as the domain.
A request was received to add a linked domain with name already in use. Select a different name for one of the domains.
CFG_10041
Explanation: User Response:
CFG_10042
Explanation:
User Response:
CFG_10043
Explanation: User Response:
52
CFG_10044
Explanation: User Response:
Node option group <option group> for node <node the option group belongs to> was not found.
A request was received to access an option group that cannot be found. Use infacmd listNodeOptions to list the available option groups.
CFG_10045
Explanation: User Response:
Cannot add existing node option group <option group> to node <node name>.
A request was received to add an existing option group for the node. Update the individual options in the option group or choose another name.
CFG_10046
Explanation: User Response:
Cannot add existing <type of resource> resource <resource name> to node <node name>.
A request was received to add an existing node resource. Provide a different resource name or a different resource type.
CFG_10047
Explanation: User Response:
<type of resource> resource <resource name> cannot be found on node <node name>.
A request was received to act on a non-existing node resource. Provide the resource name before continuing.
CFG_10048
Explanation: User Response:
User <name of the user> does not have permission on node <node name>.
A request was received to add or update a node with an invalid login user. Either assign permission to that user to access the node or choose a user who has node permission.
CFG_10049
Explanation: User Response:
Cannot associate a gateway node <node name> without specifying the log directory.
A request was received to associate a gateway node without the log directory being specified. Verify that the log directory is specified.
CFG_10050
Explanation: User Response:
CFG_10051
Explanation: User Response:
CFG_10052
Explanation: User Response:
CFG_10055
Explanation:
CFG Messages
53
User Response:
Contact Informatica Global Customer Support. Before restoring the domain configuration database from the last known good backup file, back up the invalid domain configuration database to another file to help Informatica Global Customer Support troubleshoot the problem.
CFG_10057
Explanation: User Response:
Unable to connect to the linked domain <domain name> because: <error message>.
The domain cannot communicate with the linked domain specified. Verify that the Service Manager on the linked domain is running and that its gateway host:port address is correct.
CFG_10059
Explanation: User Response:
CFG_10060
Explanation: User Response:
CFG_10062
Explanation: User Response:
Cannot add service <service name> because license <license name> is not found in the domain.
A request was received to add a service using a non-existing license. Specify a valid license to assign the service to.
CFG_10080
Explanation: User Response:
The input list must contain a user name followed by at least one object name.
A request was received with invalid parameters. Provide the user name followed by at least one object name.
CFG_10081
Explanation: User Response:
Object at full path <full path of object> cannot be found in the domain.
A request was received for an object that cannot be found. Verify that the object path and the object name are correct.
CFG_10082
Explanation: User Response:
The value <option value> for option <option name> of service <service name> is not valid.
The option value specified for the service is not valid. Check to make sure option specified is valid.
CFG_10083
Explanation: User Response:
The operating mode of service <service name> cannot be changed to safe mode while the service is enabled.
The operating mode cannot be changed to safe while the service is enabled. Disable the service first.
CFG_10084
Explanation: User Response:
54
CFG_10085
Explanation: User Response:
CFG_10086
Explanation: User Response:
CFG_10087
Explanation: User Response:
Service <service name> contains references to linked domains <list of linked domains> not defined in the domain.
A request was received to add a service referencing undefined linked domains. Link the domains.
CFG_10088
Explanation: User Response:
Node <node name> was modified to be a gateway node in the domain but failed to update node metadata file.
A problem was encountered communicating with the node that did not update its metadata file. Go to the node and run infacmd defineGatewayNode to match domain definition.
CFG_10089
Explanation: User Response:
Node <node name> was modified to be a worker node in the domain but failed to update node metadata file.
A problem was encountered communicating with the node that did not update its metadata file. Go to the node and run infacmd defineWorkerNode to match the domain definition.
CFG_10091
Explanation: User Response:
The full path was not specified for object <object name>.
A request was received for an object requiring the full path. Provide the object full path.
CFG_10095
Explanation: User Response: Explanation: User Response:
The Service Manager failed to read the domain configuration from <database type> database with connection string <database connection string> with error <error message>.
The port number assigned to the Web Services Hub is already in use. Verify that the database connectivity information specified for the domain is correct. The domain configuration database has invalid data. 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
Explanation:
Cannot enable service <service name> with the same name as the domain. Rename your service.
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
55
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
Explanation: User Response:
Cannot add service <service name> with the same name as the domain. Rename your service.
An application service cannot have the same name as the PowerCenter domain. Enter a different name for the application service.
CFG_10105
Explanation: User Response:
The code page of an existing Repository Service <Repository Service name> cannot be changed.
After a Repository Service is created, the code page cannot be changed in the Repository Service properties. 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
User Response:
Cannot create an OS profile with the system user name set to root because this may result in a security breach.
Assign a different operating system user to the OS profile.
CFG_10107
User Response:
Cannot start the service upgrade process as the following services have already been upgraded to version <service version>: <list of service>
Verify that the service requires an upgrade or contact Informatica Global Customer Support.
CFG_10110
User Response:
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.
Contact Informatica Global Customer Support.
CFG_10111
User Response:
Cannot upgrade services as the list of services received by the domain does not contain one or more dependent services.
Contact Informatica Global Customer Support.
CFG_10116
User Response:
The version of the domain <domain name> is different from the version of the current domain. Upgrade the domain to version <domain version>.
Upgrade the domain to the current domain version before you add it to the current domain.
CMD Messages
CMD_35197
Explanation: User Response:
The Value <value> for INFA_CLIENT_RESILIENCE_TIMEOUT is invalid. Using default value <value> instead.
The environment variable INFA_CLIENT_RESILIENCE_TIMEOUT is set to an invalid value. Change the value to 0 or any positive integer.
56
CMD_35198
Explanation: User Response:
CMN Messages
CMN_1003
Explanation: User Response:
CMN_1006
Explanation: User Response:
CMN_1008
Explanation: User Response:
Internal error.
An internal error occurred. Related error messages may appear to further diagnose the error. Contact Informatica Global Customer Support.
CMN_1009
Explanation: User Response:
CMN_1011
Explanation: User Response:
Error allocating system shared memory of <number> bytes for [DTM Buffer Pool]. Error is <system error code>: <system error message>.
An error occurred while the system allocated shared memory. Close any unnecessary programs and restart the Integration Service before running the session again. Check the system parameters for shared memory allocation.
CMN_1012
Explanation: User Response:
CMN_1017
Explanation: User Response:
CMN Messages
57
CMN_1021
Explanation: User Response:
CMN_1022
Explanation: User Response:
'CMN_1023
Explanation: User Response:
CMN_1024
Explanation: User Response:
CMN_1026
Explanation: User Response:
CMN_1028
Explanation: User Response:
CMN_1029
Explanation:
CMN_1030
Explanation:
CMN_1035
Explanation: User Response:
Sybase event.
A Sybase event has occurred. Check the session log for a related Sybase event. If necessary, see the Sybase documentation for appropriate action.
CMN_1036
Explanation: User Response:
Sybase error.
A Sybase error has occurred. Check the session log for a related Sybase error message. If necessary, see the Sybase documentation for appropriate action.
58
CMN_1037
Explanation: User Response:
Oracle event.
An Oracle event has occurred. Check the session log for a related Oracle event. If necessary, see the Oracle documentation for appropriate action.
CMN_1038
Explanation: User Response:
Oracle error.
An Oracle error has occurred. Check the session log for a related Oracle error message. If necessary, see the Oracle documentation for appropriate action.
CMN_1040
Explanation: User Response:
CMN_1044
Explanation: User Response:
DB2 Error.
A DB2 error has occurred. Check the session log for a related DB2 error message. If necessary, see the DB2 documentation for appropriate action.
CMN_1046
Explanation: User Response: Explanation:
ODBC Error.
You created an ODBC data source, but no longer have the underlying native connectivity software or environment. Reconfigure the native connectivity environment and then run the session. 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. Do not use an ODBC connection. Be sure to only use a native DB2 CAE connection to a DB2 database.
User Response:
CMN_1049
Explanation: User Response:
PM error.
This is a generic error. Check the session log for related error messages.
CMN_1050
Explanation: User Response:
PM event.
This is a generic error. Check the session log for related error messages.
CMN_1053
Explanation: User Response:
Error information.
This is a generic error. This message varies depending on the error. Check the session log for more specific messages.
CMN Messages
59
CMN_1054
Explanation: User Response:
CMN_1055
Explanation: User Response: Explanation: User Response: Explanation: User Response:
CMN_1056
Explanation:
CMN_1057
Explanation:
CMN_1061
Explanation: User Response:
CMN_1062
Explanation: User Response:
CMN_1063
Explanation: User Response:
CMN_1064
Explanation:
CMN_1065
Explanation:
60
CMN_1066
Explanation:
CMN_1075
Explanation:
User Response:
CMN_1076
Explanation: User Response: Explanation: User Response:
CMN_1077
Explanation: User Response:
CMN_1078
Explanation: User Response:
CMN_1079
Explanation: User Response: Explanation: User Response:
CMN_1082
Explanation: User Response:
CMN_1083
Explanation: User Response:
CMN_1086
Explanation:
CMN Messages
61
User Response:
Examine the incoming data and the transformation configuration to locate the problem, then correct the problem. Or increase the error threshold.
CMN_1087
Explanation: User Response:
CMN_1088
Explanation: User Response:
CMN_1089
Explanation: User Response:
CMN_1093
Explanation: User Response: Explanation: User Response:
CMN_1094
Explanation: User Response: Explanation: User Response:
CMN_1095
Explanation: User Response:
CMN_1096
Explanation: User Response:
CMN_1097
Explanation:
62
User Response:
Make sure each Joiner transformation has at least one linked output port.
CMN_1098
Explanation: User Response: Explanation: User Response:
ERROR: Cache Directory may not exist or insufficient privilege/space in the supplied cache directory.
The directory specified for the index and data caches has run out of memory. Free up disk space in the cache directory. The Informatica services account or the operating system user in the operating system profile does not have the appropriate privileges to access that directory. Grant write permission on the directory to the Informatica services account or the operating system user in the operating system profile.
CMN_1099
Explanation:
ERROR: Master and detail relations are flipped from user specification.
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. 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.
User Response:
CMN_1100
Explanation:
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.
Same as CMN_1099.
CMN_1101
Explanation:
ERROR: Alter the mapping and place the target tables violating this constraint in different target load order groups.
Same as CMN_1099.
CMN_1102
Explanation: User Response:
CMN_1103
Explanation:
WARNING: No row found from the master relation. Joiner will not produce any output row.
The master source contained no rows. Since the data from the master source is read before the detail source data can load, the Joiner transformation is unable to produce data when the master source contains no data. Make sure the correct source tables are named in the mapping and those tables contain data.
User Response:
CMN_1104
Explanation: User Response:
ERROR: The conversion from source type to target type is not supported.
The mapping contains an invalid datatype conversion. In the Designer, validate the mapping to locate the invalid conversion.
CMN Messages
63
CMN_1105
Explanation: User Response:
ERROR populating index using the key value from the master relation row.
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. This message is preceded by a file error. Correct the file error before running the session again.
CMN_1106
Explanation: User Response:
CMN_1107
Explanation:
CMN_1108
Explanation: User Response:
CMN_1109
Explanation: User Response:
CMN_1111
Explanation: User Response:
CMN_1120
Explanation:
User Response:
CMN_1121
Explanation: User Response:
CMN_1122
Explanation:
User Response:
64
CMN_1123
Explanation:
User Response:
CMN_1124
Explanation: User Response:
CMN_1125
Explanation:
Error opening temporary email <temporary file name> file for write.
An Integration Service on UNIX encountered an error trying to create post-session email. The directory from where the Integration Service was started does not have write permissions for the Integration Services account. Make sure the directory has write permissions.
User Response:
CMN_1126
Explanation: User Response:
CMN_1127
Explanation: User Response:
CMN_1128
Explanation: User Response:
CMN_1129
Explanation: User Response:
CMN_1134
Explanation:
This PowerMart Server build does not support database type (Microsoft SQL Server).
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.
CMN Messages
65
User Response:
Use the DataDirect ODBC SQL Server driver for UNIX to load Microsoft SQL Server.
CMN_1141
Explanation:
ERROR: Unexpected condition at file <file name> line <line number>. Application terminating. Contact Informatica Global Customer Support for assistance.
An application error occurred. Note the file name and line number and contact Informatica Global Customer Support.
CMN_1164
Explanation: User Response:
Database driver error. Bulk write initialization failed (blk_init returned failure).
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. 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
User Response:
The mapping was changed after the saved disk cache file was created.
Recache the lookup source.
CMN_1557
Explanation:
User Response:
CMN_1564
Explanation: User Response:
The Integration Service data movement mode is different from the saved disk cache.
The Lookup transformation uses a persistent named cache, and the Integration Service data movement mode was changed between session runs. Recache the lookup source, or change the data movement mode to the previous mode.
CMN_1565
Explanation:
The Integration Service code page is different from the saved disk cache.
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. Recache the lookup source, or change the code page to the previous code page.
User Response:
CMN_1573
Explanation: User Response:
Error: Unknown code page <code page ID> for data source <source name>.
The system could not find a code page for the source. The pmlocale.bin file might be corrupt or incomplete. Install a complete pmlocale.bin file from the installation DVD.
CMN_1574
Explanation: User Response:
Error: Failed to create locale from code page <code page ID> for data source <source name>.
The system could not locate locale information for the source. The pmlocale.bin file that contains the locale information might be corrupt or incomplete. Install pmlocale.bin file from the installation DVD.
66
CMN_1575
Explanation: User Response:
The Integration Service sort order is different from the saved disk cache.
The Lookup transformation uses a persistent named cache, and the Unicode mode sort order was changed between session runs. Recache the lookup source, or change the sort order to the previous sort order.
CMN_1576
Explanation: User Response:
Error: The current lookup index cache size of <number> bytes is too small. Increase the lookup index cache to at least <number> bytes.
In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value. Increase the lookup index cache size to the value recommended in the error message.
CMN_1577
Explanation: User Response:
Error: The current lookup index cache size of <number> bytes is too small. Increase the lookup index cache size to at least <number> bytes.
In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value. Increase the lookup index cache size to the value recommended in the error message.
CMN_1579
Explanation: User Response:
Input lookup precision is greater than the output lookup precision. Verify that the Lookup transformation and linked transformations have the same port precision.
The precision for the lookup input port and the lookup output port do not match. In the lookup condition, verify that the ports in the Lookup Table Column and the Transformation Port have the same precision.
CMN_1625
Explanation: User Response:
ERROR: Joiner <Joiner transformation> has <number> inputs for the master relation. There should only be one master relation.
The mapping is invalid and you cannot run the session. Check the mapping, make changes, and revalidate it.
CMN_1626
Explanation: User Response:
ERROR: Joiner <Joiner transformation name> has <number> inputs for the detail relation. There should only be one detail relation.
The mapping is invalid and you cannot run the session. Check the mapping, make changes, and revalidate it.
CMN_1627
Explanation: User Response:
CMN_1628
Explanation: User Response:
Joiner <Joiner transformation name> initialization error creating detail input row data.
Internal error. Contact Informatica Global Customer Support.
CMN_1629
Explanation: User Response:
Joiner <Joiner transformation name> initialization error creating master input row data.
Internal error. Contact Informatica Global Customer Support.
CMN Messages
67
CMN_1630
Explanation: User Response:
ERROR: Unexpected error encountered at file <file name> line <line number>.
Unexpected error. Review error messages preceding this message. Otherwise, note the file name and line number and contact Informatica Global Customer Support.
CMN_1636
Explanation: User Response:
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.
You cannot share static and dynamic lookups in the same target load order group. 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.
You cannot share two dynamic lookups in the same target load order group. 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_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.
You cannot share static and dynamic or two dynamic lookups in the same target load order group. 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
Explanation: User Response:
Error: Failed to get shared access to cache files <cache file name>. [dat/idx] for lookup <Lookup transformation>.
One session is trying to read from a cache file while another session is still writing to it. Wait until the first session completes, then run the session.
CMN_1646
Explanation: User Response:
Error: Failed to get exclusive access to cache files <cache file name>. [dat/idx] for lookup <Lookup transformation>.
One session is trying to write to a cache file while another session is reading from it. Wait until the first session completes, then run the session.
CMN_1647
Explanation: User Response:
Error: Failed to upgrade to exclusive access for cache files <cache file name> for lookup <Lookup transformation>.
A session is trying to write to a cache file while another session is reading from the file. Wait until the first session completes, and then run the session.
68
CMN_1650
Explanation: User Response:
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.
You configured a Lookup transformation to use a dynamic lookup cache and the lookup table contains duplicate rows. 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>.
Two Lookup transformations have different connect strings, but have the same cache file name. 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>.
Two Lookup transformations have different query overrides, but have the same cache file name. 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_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>.
Two Lookup transformations have different query overrides, but have the same cache file name. 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>.
Two Lookup transformations use different lookup tables, but have the same cache file name. 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>.
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. 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.
Explanation:
User Response:
CMN Messages
69
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.
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. 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.
Explanation:
User Response:
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.
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. 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.
Explanation:
User Response:
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>.
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. 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.
Explanation:
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.
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. 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.
Explanation:
User Response:
CMN_1664
Explanation:
Error: Out of sequence IDs to generate for port <port name> of Lookup <transformation name> for insertion.
You reached the limit of unique sequence IDs that can be generated for inserting rows in the dynamic lookup cache.
70
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
Explanation: User Response:
Error: Failed to form key row for insertion in index cache file for Lookup <transformation name>.
Internal error. Contact Informatica Global Customer Support.
CMN_1666
Explanation: User Response:
Error: Failed to form data row for insertion in data cache file for Lookup <transformation name>.
Internal error. Contact Informatica Global Customer Support.
CMN_1667
Explanation: User Response:
CMN_1675
Explanation: User Response:
Cache for Lookup <Lookup transformation name> expects lookup override <SQL override> but Cache file <file name> has <SQL override>.
The Lookup transformation uses a persistent named cache, and the lookup SQL override was changed between session runs. 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.
Another session with a named lookup cache in the mapping may be running that is using this cache file. 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.
Another session with an unnamed Lookup transformation in the mapping may be running that is using this cache file. 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.
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. Change the Lookup properties to either remove the cache file name prefix or use a persistent cache.
Explanation:
User Response:
CMN Messages
71
CMN_1683
Explanation:
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.
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. Use unique cache file names for the transformations.
User Response:
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.
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. Use unique cache file names for the transformations.
Explanation:
User Response:
CMN_1686
Explanation: User Response:
Error allocating <number of bytes requested> in memory for cache transformation: <transformation name>.
You specified a cache size larger than the system can allocate. Either reduce cache size for the transformation or increase virtual memory available in the machine.
CMN_1687
Explanation: User Response:
Error: Cache not enabled for Dynamic Lookup transformation <transformation name>.
In the session, you disabled caching for a Lookup transformation that you configured to use as a dynamic cache. If you configure a Lookup transformation with a dynamic cache, you must enable caching in the session.
CMN_1689
Explanation: User Response:
Failed to allocate <number> bytes from process memory for [DTM Buffer Pool].
There is insufficient process memory. Reduce the DTM buffer pool size, or free system resources.
CMN_1691
Explanation: User Response:
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.
Two Lookup transformations are configured to share a lookup cache, but the datatypes of the cached columns in the Lookup transformations do not match. 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
Explanation: User Response:
Database Event Unable to set DBARITHABORT: Arithmetic exceptions from Microsoft SQL Server will not cancel query execution.
The Integration Service failed to set database option DBARITHABORT for a database connection to Microsoft SQL Server. 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.
72
CMN_1695
Explanation: User Response:
Database Event Unable to set options: Options cannot be set in Microsoft SQL Server.
The Integration Service failed to set any database option for a database connection to Microsoft SQL Server. Make sure Microsoft SQL Server is running and you can set the database connection and database connection options.
CMN_1701
Explanation: User Response:
Error: Data for Lookup <transformation name> fetched from the database is not sorted on the condition ports. Please check your Lookup SQL override.
You specified a SQL override for this Lookup transformation and specified the ORDER BY clause incorrectly. When you override the lookup query ORDER BY clause, you must put the condition ports first.
CMN_1702
Explanation: User Response:
Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number> <error message>. (UNIX only)
Internal error. Contact Informatica Global Customer Support.
CMN_1703
Explanation: User Response:
Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number>. (Windows only)
The address you specified in the Shared Memory Base Address is already in use. Change the address in the Integration Service configuration.
CMN_1704
Explanation: User Response:
Error attaching to system shared memory <ID> for <Load Manager Shared Memory>. Expected to attach at address <address>, but attached at <address>.
Internal error. Contact Informatica Global Customer Support.
CMN_1705
Explanation: User Response:
Error attaching to system shared memory <ID> because it has been removed.
The Load Manager terminated unexpectedly. Or the system shared memory was manually removed using the ipcrm command. Restart the Integration Service.
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.
The lookup query contains one or more characters that are not encoded in character set of the lookup database code page. 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.
The lookup database uses a code page that is not supported by PowerCenter. Select a code page for the lookup database that is supported by PowerCenter and contains encoding for the lookup data character set.
CMN Messages
73
CMN_1720
Explanation: User Response:
The persistent lookup cache was created in a format that is incompatible with this release.
You upgraded a session using a persistent lookup cache and the Integration Service ran it for the first time since the upgrade. None. The Integration Service rebuilds the cache from the lookup table.
CMN_1764
Explanation: User Response:
CMN_1765
Explanation: User Response:
CMN_1766
Explanation: User Response:
CMN_1767
Explanation: User Response:
CMN_1768
Explanation: User Response:
CMN_1769
Explanation: User Response:
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.
74
CMN_1770
Explanation: User Response:
CMN_1771
Explanation:
The connection <database connection> specified is ambiguous. The connection name exists in both relational and application connections.
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
Explanation: User Response:
Guaranteed Message Delivery cache directory <directory name> does not exist.
The Integration Service cannot find the cache file directory for message recovery. 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.
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. 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.
Explanation:
User Response:
CMN_1774
Explanation:
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.
Same as CMN_1773.
CMN_1775
Explanation: User Response:
CMN_1777
Explanation:
The connection <database connection name> specified can not run SQL query; hence can not be used as a lookup or stored procedure connection.
For a Lookup or Stored Procedure transformation, you selected an Application database connection type that is not a relational database.
CMN Messages
75
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
Explanation: User Response:
CMN_1779
Explanation: User Response:
CMN_1780
Explanation:
Guaranteed Message Delivery timestamp was changed, message cache will be cleaned and session will continue running.
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. None.
User Response:
CMN_1781
Explanation: User Response:
Error: A connection must be specified for $Target when using 3.5 LOOKUP function.
An expression in the mapping uses the LOOKUP function and you did not specify a database connection for the $Target Connection Value session property. 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
Explanation: User Response:
Error: A connection must be specified for $Source when using 3.5 LOOKUP function.
An expression in the mapping uses the LOOKUP function and you did not specify a database connection for the $Source Connection Value session property. 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
Explanation: User Response:
Connect string <connection name in Location Information property> too long. Maximum length allowed is <maximum length>.
In the Location Information session property for a Lookup transformation, you specified a database connection name that is too long. Edit the database connection name in either the Relational or Application Connection Browser.
CMN_1785
Explanation:
Lookup SQL override <Lookup transformation> has references to mapping parameters or variables that cannot be resolved correctly.
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.
76
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
Explanation: User Response:
CMN_1796
Explanation:
An error was encountered while writing prior message(s) to this log file. Those messages may be lost. Please check for available disk space.
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. Check the available space on the machine that hosts the server log file.
User Response:
CMN_1798
Explanation: User Response:
Cache for Lookup <Lookup transformation name> expects <number of> partitions but Cache file <file name> has <number of> partitions.
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. 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.
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. 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:
User Response:
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. 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.
User Response:
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.
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. 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.
Explanation:
User Response:
CMN Messages
77
CMN_1804
Explanation: User Response:
CMN_1806
Explanation: User Response:
Failed to get information for file <cache file>. Error message: <error message>.
The Integration Service could not read the recovery cache file. See the additional error message for more information.
CMN_1807
Explanation: User Response:
CMN_1808
Explanation:
User Response:
CMN_1809
Explanation: User Response:
CMN_1813
Explanation: User Response:
ERROR: Some cache files with name prefix <name prefix> for Lookup <Lookup transformation name> are missing or invalid.
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. 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
Explanation: User Response:
Error: Data for Lookup fetched from the file is not sorted on the condition ports.
You ran a flat file lookup session configured for sorted input, but the data for the condition columns is not grouped. Clear the sorted input option in the Lookup transformation. Ensure that data in the condition columns are grouped.
78
CMN_1919
Explanation: User Response:
CMN_1920
Explanation:
External loader error. Error getting Flat-File information required for Loader.
Same as CMN_1919.
CMN_1921
Explanation:
External loader error. Control File will be generated for First Partition Only.
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. Verify the control file in the first partition of the session uses the attributes you want for the session.
User Response:
CMN_1922
Explanation: User Response:
External loader error. Update is not valid for target instance <target definition name> since no primary key(s) is mapped to the target.
The Teradata target table does not have a primary key, so the Integration Service cannot generate a control file and update the target. Define a primary key on the target table and run the session again.
CMN_1923
Explanation:
External loader error. Update is not valid for target instance <target definition name> since no non-key field(s) is mapped to the target.
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. Connect the primary key column in the Teradata target definition to an upstream port in the mapping. Run the session again.
User Response:
CMN_1924
Explanation:
External loader error. Delete is not valid for target instance <target definition name> since no primary key(s) is mapped to the target.
Same as CMN_1923.
CMN_1926
Explanation:
Error: Teradata external loader requires a primary key on table <target table name> when using load mode <load mode>.
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. Define a primary key on the target table and run the session again.
User Response:
CMN_1927
Explanation: User Response:
CMN Messages
79
CMN_1928
Explanation: User Response:
External loader error. Upsert is not valid for target instance <target definition name> since update is not valid for the target.
The Integration Service cannot perform upserts on the Teradata target table. 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
Explanation: User Response:
CMN_1986
Explanation: User Response:
Service <service name> encountered an error while communicating with Licensing Service: <error code and message>.
The service encountered an error while communicating with the Licensing Service. See the additional error message for more information.
CMN_1989
Explanation: User Response:
CMN_2005
Explanation: User Response:
CMN_2006
Explanation: User Response:
CMN_2018
Explanation: User Response:
Error: Failed to expand call text <text> for Stored Procedure transformation <transformation name>.
The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure. 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 mapping variable to a text string in the parameter file. The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure due to an internal error.
Explanation:
80
User Response:
CMN_2028
Explanation: User Response:
The Integration Service cannot parse user variable at position <user variable position> in file <file>.
The Integration Service cannot find a value for the user variable in the specified position in the control file. In the connection object attributes, verify that the user variable is defined and contains the correct syntax.
CMN_7136
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.
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. Edit the mapping and move the Transaction Control transformation either before or after the concatenation.
Explanation:
User Response:
CMN_17800
Explanation: User Response:
CMN_17802
Explanation: User Response:
CMN_17804
Explanation: User Response:
Port <port number>: The transformation type <transformation datatype> is incompatible with SAP type <SAP datatype>.
The transformation datatype and SAP datatype are not compatible for the specified transformation. You may have modified the transformation. If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again.
CMN_17807
Explanation: User Response: Explanation: User Response:
Data conversion error for port <port number> with data <data>.
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. Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port. The data contains inconsistencies. Contact Informatica Global Customer Support.
CMN Messages
81
CMN_17808
Explanation: User Response: Explanation: User Response:
CMN_17809
Explanation: User Response:
CMN_17810
Explanation: User Response:
CMN_17815
Explanation: User Response:
CMN_17816
Explanation: User Response:
CMN_17817
Explanation: User Response:
CMN_17818
Explanation: User Response:
CMN_17825
Explanation: User Response:
82
CMN_17829
Explanation:
User Response:
CMN_17831
Explanation: User Response:
Incorrect source file name may have been specified in the session.
The source file name specified for the 6.x IDoc_Writer AEP transformation may be incorrect. Verify that the source file name is correct.
CMN_17833
Explanation: User Response:
Binary datatypes are not supported in RFC/BAPI function mappings. Disconnect port <port name> in the mapping.
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. Disconnect the specified port.
CMN_17838
Explanation: User Response:
SAP code page <code page> is not compatible with the connection code page <code page>.
The code page specified in the SAP RFC/BAPI Interface application connection is not compatible with the SAP server. Verify that the code page entered for the application connection is compatible with the SAP server.
CMN_17839
Explanation: User Response:
SAP code page <code page> is not compatible with the Integration Service code page.
The code page specified for the Integration Service is not compatible with the SAP server. Verify that the Integration Service code page is compatible with the SAP server.
CMN_17840
Explanation: User Response:
Data <data> overflow at port <port number>. See below to find the row with error.
The Integration Service encountered a row error. As a result, the session failed. See the session error log to determine the row that contains the error and view more information about the error.
CMN_17848
Explanation: User Response:
CMN_17851
Explanation:
User Response:
CMN_17853
Explanation:
CMN Messages
83
User Response:
CMN_17856
Explanation: User Response:
Control field <control field> cannot have length greater than the precision <value>.
The length of the control field exceeds the precision set for it. Eliminate the errors in the data. Increase the precision for the control field.
CMN_65011
Explanation: User Response:
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.
The Lookup transformation uses a dynamic cache and the workflow is configured to run concurrently with same instance name. Configure the Lookup transformation to use a static cache or define unique names for each workflow instance.
CMN_65013
Explanation: User Response:
CMN_65014
Explanation: User Response:
CMN_65015
Explanation: User Response:
The Integration Service failed to open a pipe <pipe name> to read the parameter file, perform a file wait task, or to read a session log.
The Integration Service failed to open a pipe to read the parameter file, perform a file wait task, or to read a session log. Contact Informatica Global Customer Support.
CMN_65016
Explanation: User Response:
CMN_65017
Explanation: User Response:
The Integration Service could not use operating system profiles because pmimprocess was not configured.
The pmimprocess was not configured. Set the user and groups to root and enable the setuid bit for pmimprocess before you use operating system profiles.
CMN_65018
Explanation: User Response:
The workflow failed because the operating system user name specified in the operating system profile is invalid.
The operating system profile contains an invalid operating system user name. Verify that the operating system user name is valid for nodes in the domain.
84
CMN_65019
Explanation: User Response:
Error using operating system profiles to run a workflow. Contact Informatica Global Customer Support.
An internal error occurred when using an operating system profile to run a workflow. Contact Informatica Global Customer Support.
CMN_65020
Explanation: User Response:
CMN_65025
User Response:
Recovery file <recovery file name> is inconsistent. The expected recovery file size is <expected recovery file size>, but the recovery file size is <recovery file size>.
Restart the session in cold start mode.
CMN_65040
User Response:
Recovery file <recovery file name> is inconsistent. The size <recovery file size> is less than the minimum size of 4 bytes.
Restart the session in cold start mode.
CMN_65050
Explanation: User Response:
CMN_65051
Explanation: User Response:
The Integration Service could not send an email to the SMTP server.
The SMTP server machine may not be accessible. 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
Explanation: User Response:
The timeout period expired before the Integration Service could connect to the SMTP server.
The SMTP server custom properties for the Integration Service process may contain invalid values. 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
Explanation: User Response:
The Integration Service could not locate the SMTP server because the server address is invalid.
The SMTP server address custom property for the Integration Service process contains an invalid server address. 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
85
CMN_65070
Explanation: User Response:
ERROR: Update dynamic cache condition is not valid for Lookup transformation.
The dynamic Lookup transformation does not have a conditional expression to update the dynamic cache. Create an expression that returns a boolean or numeric value.
CMN_65071
Explanation: User Response:
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.
A Lookup transformation that returns multiple rows is sharing a lookup cache with a Lookup transformation that returns one row for each input row. Verify that the Lookup transformations that share named cache have the same multiple match properties.
CNX Messages
CNX_53117
Explanation: User Response:
Failed processing request ID <request ID>, req opcode <request operation ID>, reply opcode <reply operation ID>. Return Status: <return status>.
Repository agent failed to complete the requested operation. If error persists, contact Informatica Global Customer Support.
CNX_53119
Explanation: User Response:
CONF Messages
CONF_45006
Explanation: User Response:
Error: The Service Manager could not validate the Integration Service <Integration Service Name> because the Integration Service does not have an associated repository.
The Integration Service validation failed because an associated repository was not configured for the Integration Service. Configure an associated repository for the Integration Service.
86
CSE Messages
CSE_34005
Explanation:
The Integration Service could not set the encryption key for encryption.
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. Run the session again. If the error persists, contact Informatica Global Customer Support and provide the data you are trying to encrypt.
User Response:
CSE_34010
Explanation:
The Integration Service could not set the encryption key for decryption.
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. Run the session again. If the error persists, contact Informatica Global Customer Support and provide the data you are trying to decrypt.
User Response:
CSE_34039
Explanation: User Response:
CSE_34040
Explanation: User Response:
CSE_34041
Explanation: User Response:
CSE_34042
Explanation: User Response:
CSE Messages
87
CTSDK Messages
CTSDK_43000
Explanation: User Response:
Couldn't load the library <library name> for plug-in <plug-in name>.
The plug-in has been installed incorrectly or is not compatible with the PowerCenter version. Reinstall the plug-in.
CTSDK_43001
Explanation: User Response:
CTSDK_43002
Explanation: User Response:
Couldn't find address of function <function name> for plug-in <plug-in name>.
The function for the plug-in is not defined or is incorrectly defined. Reinstall the plug-in.
CTSDK_43003
Explanation: User Response:
88
CHAPTER 6
DBGR Messages
DBGR_25011
Explanation: User Response:
DBGR_25013
Explanation: User Response:
DBGR_25015
Explanation: User Response:
DBGR_25016
Explanation: User Response:
DBGR_25017
Explanation: User Response:
89
DBGR_25018
Explanation: User Response:
DBGR_25019
Explanation: User Response:
DBGR_25020
Explanation: User Response:
DBGR_25021
Explanation: User Response:
DBGR_25022
Explanation: User Response:
DBGR_25024
Explanation: User Response:
DBGR_25025
Explanation:
Cannot modify data for transformations other than the current one.
Same as DBGR_25024.
DBGR_25026
Explanation: User Response:
DBGR_25027
Explanation: User Response:
DBGR_25028
Explanation: User Response:
Use of port <port name> in debug condition is invalid. Maybe it is not connected.
You specified an unconnected port in the port column of the condition for a breakpoint. An unconnected port either has a default value if it is specified, or it always has a null value. Do not specify the value in a debug condition. Either make a connection to that port or choose a connected port.
90
DBGR_25029
Explanation: User Response:
Use of port <port name> as value in debug condition is invalid. Maybe it is not connected.
You specified an unconnected port in the value column of the condition for a breakpoint when the type column is port. An unconnected port either has a default value if it is specified, or it always has a null value. Do not specify the value in a debug condition. Either make a connection to that port or choose a connected port.
DBGR_25030
Explanation: User Response:
DBGR_25033
Explanation: User Response:
DBGR_25034
Explanation: User Response:
DBGR_25035
Error: Socket connect failed for reqType: <request type>. Debugger client may have timed out if session start up time exceeded time out value specified in Workflow Manager. Please increase timeout value and try again.
The DTM could not connect to the Designer due to the Integration Service timeout. Increase the timeout value for the Integration Service connection in the Workflow Manager and run session again.
DBGR_25036
Explanation: User Response:
DBGR_25040
Explanation: User Response:
DBGR_25041
Explanation: User Response:
Error: Invalid groupIndex <number> resulted from groupId <number> specified for modifying Router transformation.
Internal error. Contact Informatica Global Customer Support.
DBGR_25044
Explanation: User Response:
Data Type mismatch: <value> cannot be used in a condition with port <port name>.
You entered an invalid value for the port datatype for a conditional breakpoint. Make sure the value is in the correct format: MM/DD/YYYY hh:mm:ss.
DBGR Messages
91
DBGR_25045
Explanation:
Error in breakpoint condition: Port <port name> and Port <port name> are from different groups.
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. Do not use ports from different groups to set the conditional breakpoint.
User Response:
DBGR_25046
Explanation: User Response:
DBGR_25047
Explanation: User Response:
DBGR_25048
Explanation: User Response:
Breakpoint condition cannot be specified for binary port <port> <port name>.
You tried to specify a conditional breakpoint using a binary port. Do not specify a conditional breakpoint for a binary port.
DBGR_25049
Explanation: User Response:
DBGR_25050
Explanation: User Response:
Port <port name> used in expression is unconnected and has no default value.
You tried to evaluate an expression using a port that is unconnected and has no default value. An expression port never receives a value. 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
Explanation: User Response:
Failed to create a socket to listen for connections from the client <PowerCenter Client machine name>.
The Integration Service could not create a socket for Debugger connections. The PowerCenter Client machine may have failed during the connection. Restart the Debugger session.
DBGR_25060
Explanation: User Response:
Failed to find an available port between <DebuggerMinPort> and <DebuggerMaxPort> to listen for connections from the client <PowerCenter Client machine name>.
The Integration Service could not find an available port for Debugger connections. Stop other Debugger sessions or wait for those sessions to complete before you restart the current Debugger session. Increase the DebuggerMaxPort value to provide additional ports for Debugging on the Integration Service.
92
DBGR_25061
Explanation: User Response:
DBGR_25062
Explanation: User Response:
Failed to notify client of the port we are listening on: no RepServer connection is available.
The Integration Service could not connect to the Repository Service or lost the connection to the PowerCenter Client machine. Restart the Debugger session.
DBGR_25068
Explanation: User Response:
DMI Messages
DMI_17501
Explanation: User Response:
DMI_17503
Explanation: User Response:
At least one field other than primary and foreign keys must be connected for each group.
Only primary and foreign keys are connected. At least one other port must be connected. Connect at least one port per group other than the primary and foreign keys.
DMI_17504
Explanation: User Response:
DMI_17505
Explanation:
DMI_17506
Explanation: User Response:
DMI_17507
Explanation: User Response:
NULL data obtained for all connected fields for the segment <segment name>.
The data for all connected fields is missing for the named segment. Make sure the data exists for all connected fields for the named segment.
DMI Messages
93
DMI_17508
Explanation:
DMI_17509
Explanation:
DMI_17511
Explanation: User Response:
<Number> orphan rows were received by the SAP DMI Prepare transformation.
The SAP DMI Prepare transformation received orphan rows. Make sure that all child rows have parent rows.
DMI_17512
Explanation: User Response:
Orphan row <row> received in group <group> with primary key <primary key> and foreign key <foreign key>.
The SAP DMI Prepare transformation received orphan rows. Make sure that all child rows have parent rows.
DMI_17513
Explanation: User Response:
<Value> duplicate rows were received by the SAP DMI Prepare transformation.
The DMI Prepare transformation received duplicate rows. Eliminate the duplicate rows in the data.
DMI_17514
Explanation: User Response:
DMI_17515
Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>.
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. Verify that the SAP DMI Prepare transformation for the DMI document contains values for the mandatory segment.
Explanation:
User Response:
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>.
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. Correct the source data so that the number of records for the segment does not exceed the maximum number of records allowed.
Explanation:
User Response:
94
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>.
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. Correct the source data, so that the number of records for the segment meet at least the minimum number of records allowed.
Explanation:
User Response:
DMI_17518
Explanation: User Response:
Data <data> overflow at port <port number>. If the error threshold is not met, the row will be sent through the ErrorDMIData port.
The SAP DMI Prepare transformation received data that is larger than the precision for the row. Correct the source data so that the value matches the precision for the row.
DMI_17519
Explanation:
DMI_17520
Explanation: User Response:
The SAP DMI Prepare transformation has an unconnected input group. All input groups must be connected for the transformation.
An input group does not have any connected ports. Make sure that at least one port for each input group is connected.
DMI_17525
Explanation: User Response:
Cache folder specified for the SAP DMI Prepare transformation <transformation name> is invalid.
The cache directory specified for the SAP DMI Prepare transformation does not exist. In the session properties, enter a valid directory for the Cache Directory property.
DMI_17526
Explanation: User Response:
The Integration Service could not access the cache block in group <group>. Increase the cache size.
The cache size specified for the SAP DMI Prepare transformation is inadequate. In the session properties, increase the cache size.
DMI_17527
Explanation: User Response:
The SAP DMI Prepare transformation did not receive data for the DMI object.
The source in the DMI mapping does not contain valid data for the DMI object. Verify that the source data is valid.
DMI Messages
95
DOM Messages
DOM_10009
Explanation: User Response:
Cannot find the specified domain <linked domain name> from domain <current domain name>.
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. Verify that the domain information in the domain is up to date. Also, verify that the linked domain in the lookup request is running.
DOM_10013
Explanation: User Response:
DOM_10166
Explanation: User Response:
DOM_10174
Explanation: User Response:
Unable to update the operating mode to <operating mode> on service <service name>.
The domain failed to update the service configuration. Make sure the service configuration is valid in the domain.
DOM_10176
Explanation: User Response:
Unable to queue the alert of type <alert type> for object <object name> with alert message <alert message> to the alert service.
The domain failed to connect to the alert service. Restart the master gateway node.
DOM_10181
Explanation: User Response:
Unable to communicate with node <node name> at host <host name> and port <port number> from the master node <node name>.
The master node cannot communicate with the node in the domain. The node may be behind a fire wall that is not accessible from the master gateway node. Reconfigure network so the node is accessible from the master gateway node.
DOM_10182
The runtime state change from <original runtime state> to <requested runtime state> is invalid for service <service name> on service process <node the service process is running on>.
An invalid value has been entered for the run-time state. Shut down the domain, and then start Informatica services on the gateway nodes and worker nodes.
DOM_10184
Explanation:
The Integration Service cannot use operating system profiles on Windows node <node name> in <service name>.
Integration Services can use operating system profiles on UNIX nodes. The Integration Service cannot use operating system profiles on Windows nodes.
96
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
Explanation: User Response:
User <user name> in security domain <security domain name> does not have the Administrator role required to shut down the domain.
To shut down a PowerCenter domain, a user must have the Administrator role for the domain. Ask the domain administrator to shut down the PowerCenter domain.
DOM_10188
User Response:
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.
Start this service on a node that is configured to run this service version.
DOM_10189
User Response:
Unable to start the service <service name> of service version <service version> as the associated services <service names> belong to a different version.
Verify that associated and dependent services are of the same service version as the service, and then restart the service.
DP Messages
DP_90001
Explanation: User Response:
Invalid target type. Profile mapping targets should either be relational or null.
The profile mapping contains target definitions that are not relational or null. The targets in the profile mapping might have been modified. Recreate the profile.
DP_90002
Explanation: User Response:
All the targets in a profiling mapping should use the same connection and have the same connection attributes.
There are two or more relational database connections configured for targets in the profile mapping. Make sure you use the same relational database connection for all targets in a profiling mapping.
DP_90003
Explanation: User Response:
DP_90004
Explanation: User Response:
Connection to the database using user <user name>, connect string <database connect string> failed. Reason: <error message>.
The user name or connect string is invalid. Verify that the user name and connect string values are valid. See the additional error message for more information.
DP Messages
97
DP_90005
Explanation:
User Response:
DP_90008
Explanation: User Response:
DP_90009
Explanation: User Response:
SQL Prepare failed for statement <SQL statement> with error <database error>.
The SQL query failed. Fix the database error indicated in the message, and rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
DP_90010
Explanation: User Response:
SQL Bind failed for statement <SQL statement> with error <database error>.
The Data Profiling warehouse tables are invalid. Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
DP_90011
Explanation: User Response:
SQL Execute failed for statement <SQL statement> with error <database error>.
The Data Profiling warehouse tables are invalid. Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
DP_90012
Explanation: User Response:
SQL Fetch failed for statement <SQL statement> with error <database error>.
The Data Profiling warehouse tables are invalid. Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
DP_90013
Explanation:
User Response:
Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
98
You attempted to run an existing profile session in an upgraded PowerCenter repository against a new Data Profiling warehouse. Regenerate the profile mapping and run the profile session again.
DP_90014
Explanation: User Response:
There must be one input group and one output group for this transformation.
The Custom transformation in the profile mapping has been modified and is invalid. Regenerate the profile mapping.
DP_90015
Explanation: User Response:
DP_90016
Explanation: User Response:
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.
You tried to use two repositories for the same Data Profiling warehouse. Create a second Data Profiling warehouse. Also, create a relational database connection to the second Data Profiling warehouse in the Workflow Manager.
DP_90017
Explanation: User Response:
The profile warehouse tables are not present in the target database connection. Please check the target connection information.
The Data Profiling warehouse tables are not in the target database. Run the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it.
DP_90019
Explanation: User Response:
DP_90020
Explanation: User Response: Explanation: User Response:
Failed to get the metadata extension <metadata extension> for the mapping.
You copied a profile mapping without copying the metadata extensions. Copy the metadata extensions from the original profile mapping to the copied mapping and run the session again. You are running a session with an original profile mapping that corresponds to a data profile, but the metadata extensions are deleted. Regenerate the profile mapping.
DP_90022
Explanation: User Response:
DP_90023
Explanation: User Response:
Warehouse table PMDP_WH_VERSION is missing. The target warehouse version is incorrect. You may need to upgrade the warehouse.
The version of the Data Profiling warehouse does not match the version of PowerCenter. Upgrade the Data Profiling warehouse using the upgrade script for the database type.
DP Messages
99
DP_90024
Explanation: User Response:
The target warehouse uses schema version <version> and data version <version>. You may need to upgrade the warehouse.
The version of the Data Profiling warehouse does not match the version of PowerCenter. Upgrade the Data Profiling warehouse using the upgrade script for the database type.
DP_90026
Explanation: User Response:
Warehouse table PMDP_WH_VERSION is missing or column SCHEMA_VERSION/ DATA_VERSION/DATABASE_TYPE is missing. You need to upgrade the warehouse.
The version of the Data Profiling warehouse does not match the version of PowerCenter. Upgrade the Data Profiling warehouse using the upgrade script for the database type.
DP_90029
Explanation: User Response:
DP_90030
Explanation: User Response:
DP_90031
Explanation: User Response:
DP_90401
Explanation: User Response: Explanation: User Response: Explanation: User Response:
DP_90403
Explanation: User Response:
DP_90404
Explanation: User Response:
100
DP_90405
Explanation: User Response:
DP_90406
Explanation: User Response:
DP_90407
Explanation: User Response:
DP_90408
Explanation: User Response: Explanation: User Response:
DP_90409
Explanation: User Response: Explanation: User Response:
DP_90410
Explanation: User Response: Explanation: User Response:
DP_90411
Explanation: User Response: Explanation: User Response:
DP Messages
101
DP_90603
Explanation: User Response:
DP_90604
Explanation: User Response:
DP_90606
Explanation: User Response:
DP_90607
Explanation: User Response:
DP_90802
Explanation: User Response:
DP_90803
Explanation: User Response:
DP_90804
Explanation: User Response:
DS Messages
DS_10008
Explanation: User Response:
Cannot find node <name> specified in the service lookup request in domain <name>.
The node is not running or does not exist in the domain. Verify that the node is running. Verify that the node name was entered correctly.
DS_10009
Explanation:
102
User Response:
Verify the domain exists on the domain gateway host machine. Verify the domain name was entered correctly.
DS_10012
Explanation: User Response:
The disable mode specified <mode> is invalid to disable service <service name>.
The DisableService command was used to disable the service shown. The mode specified is invalid. Verify the mode is either complete, stop, or abort.
DS_10036
Explanation: User Response:
DS_10037
Explanation: User Response:
DS_10059
Explanation: User Response:
DSP Messages
DSP_20307
Explanation: User Response:
Error fetching node information from Configuration Service (domain name <domain>, node name <node>). Error message: <message text>.
The Integration Service could not fetch node metadata from the Service Manager. Start Informatica services on the referenced node. Check the error message text for more information about the cause of the failure.
DSP Messages
103
CHAPTER 7
EP Messages
EP_13001
Explanation:
Invalid conversion.
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. Either change the external procedure datatype or the port datatype before running the session again.
User Response:
EP_13002
Explanation: User Response:
EP_13003
Explanation: User Response:
EP_13004
Explanation:
EP_13005
Explanation:
104
EP_13006
Explanation: User Response:
EP_13007
Explanation: User Response:
EP_13008
Explanation: User Response:
EP_13010
Explanation: User Response:
EP_13011
Explanation: User Response:
EP_13012
Explanation: User Response:
EP_13013
Explanation: User Response:
EP_13014
Explanation: User Response:
EP_13015
Explanation:
EP Messages
105
EP_13020
Explanation: User Response:
EP_13021
Explanation: User Response:
EP_13022
Explanation: User Response:
EP_13023
Explanation: User Response:
EP_13024
Explanation: User Response:
EP_13025
Explanation: User Response:
EP_13026
Explanation:
EP_13027
Explanation: User Response:
EP_13028
Explanation: User Response:
106
EP_13030
Explanation: User Response:
Exception error was thrown from external procedure <external procedure name>.
The Integration Service encountered a serious exception while running the external procedure. Debug the external procedure code before running the session again.
EP_13033
Explanation: User Response:
EP_13034
Explanation: User Response:
EP_13035
Explanation: User Response:
EP_13036
Explanation: User Response:
EP_13037
Explanation: User Response:
EP_13038
Explanation: User Response:
EP_13039
Explanation: User Response:
EP_13040
Explanation: User Response:
EP_13041
Explanation: User Response:
EP Messages
107
EP_13042
Explanation: User Response:
EP_13043
Explanation: User Response:
EP_13044
Explanation: User Response:
EP_13045
Explanation: User Response:
EP_13046
Explanation: User Response:
IDispatch::Invoke failed.
The Integration Service encountered a major exception in a COM-style external procedure. Debug the external procedure code.
EP_13047
Explanation: User Response:
EP_13048
Explanation: User Response:
EP_13049
Explanation: User Response:
EP_13050
Explanation: User Response:
EP_13051
Explanation: User Response:
108
EP_13052
Explanation: User Response:
EP_13053
Explanation: User Response:
EP_13054
Explanation: User Response:
EP_13055
Explanation: User Response:
EP_13056
Explanation: User Response:
EP_13057
Explanation:
EP_13058
Explanation:
EP_13059
Explanation:
EP_13060
Explanation:
EP_13061
Explanation:
EP_13062
Explanation:
EP_13063
Explanation:
EP Messages
109
EP_13064
Explanation:
EP_13065
Explanation: User Response:
NULL BSTR.
A COM external procedure did not allocate memory for a B-String in a COM-style procedure. Allocate more memory for the B-String.
EP_13066
Explanation:
User Response:
EP_13067
Explanation:
EP_13068
Explanation: User Response:
EP_13069
Explanation: User Response:
EP_13070
Explanation: User Response:
EP_13071
Explanation: User Response:
EP_13072
Explanation: User Response:
EP_13073
Explanation:
110
User Response:
If necessary, examine the external procedure for the cause of the message.
EP_13074
Explanation: User Response:
EP_13075
Explanation: User Response:
The version of the Informatica external module is not supported by the server.
The Integration Service encountered an external procedure that is not supported. Do not use unsupported external procedure modules.
EP_13083
Explanation: User Response:
<External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.
The Init or InitParams method in the specified external procedure returned a fatal error. 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
Explanation:
EP_13089
Explanation:
Error converting initialization parameter to correct data type for constructor parameter.
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. 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.
User Response:
EP_13103
Explanation: User Response:
<External Procedure transformation>: Fatal error returned from external procedure <external procedure>.
The specified external procedure returned a fatal error. 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
Explanation:
<External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.
The Init or InitParams method in the specified external procedure returned a fatal error.
EP Messages
111
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
Explanation:
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.
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. Change the transformation scope to row. The procedure code for an active Custom transformation uses the INFA_CTSetPassThruPort() function and the data access mode is array-based. 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
Explanation:
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.
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. Change the transformation scope to row. 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. Edit the procedure code and use the INFA_CTASetRowStrategy() function to define the default row strategy to pass through.
User Response:
EP_13263
Explanation: User Response:
Fatal Error: It is illegal to call INFA_CTASetInputErrorRow when the data access mode is not ARRAY.
The Custom transformation procedure code uses the INFA_CTASetInputErrorRowM() or INFA_CTASetInputErrorRowU() function and the data access mode is row-based. 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
Explanation: User Response:
EP_13265
Explanation:
Fatal Error: It is illegal to call INFA_CTGetRowStrategy when the data access mode is ARRAY.
The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function when the data access mode is array-based.
112
User Response:
Edit the procedure code and use the INFA_CTAGetRowStrategy() function to get the default row strategy.
EP_13266
Explanation:
Fatal Error: It is illegal to call INFA_CTOutputNotification outside inputRowNotification when the transformation scope is ROW.
The Custom transformation procedure code uses the INFA_CTOutputNotification() function inside a function other than the p_<proc_name>_inputRowNotification() function when the transformation scope is row. Change the transformation scope to transaction or all input.
User Response:
EP_13267
Explanation: User Response:
EP_13268
Explanation: User Response:
EP_13269
Explanation: User Response:
EP_13270
Explanation: User Response:
Fatal Error: Downstream Transformations have encountered a fatal error. Please refer to session log.
A transformation downstream from a Custom transformation encountered a fatal error. Read the session log for other error messages.
EXP Messages
EXP_19007
Explanation: User Response:
EXP_19108
Explanation: User Response:
The Integration Service failed to parse the date format <date format string>.
An invalid date format was entered in a date function. Check the function syntax and enter a valid date format string.
EXP Messages
113
EXP_19138
Explanation: User Response:
The Integration Service failed to parse the date format <unit portion of date format>.
A date format was entered in a date function. Part of the date format string is invalid. Check the function syntax and enter a valid date format string.
EXP_19145
Explanation: User Response:
EXP_19160
Explanation: User Response:
EXP_19161
Explanation: User Response: Explanation:
User Response:
EXP_19162
Explanation:
Module <module name> interface version <version number> is incompatible with framework version <version number>.
The custom function developer did not configure the plug-in version to be compatible with the Custom Function API version. The Custom Function API version includes major release number, minor release number, and patch number, such as 8.0.0. The custom function developer needs to configure the plug-in version in INFA_EXPR_GetPluginVersion to be compatible with the Custom Function API version.
User Response:
EXP_19163
Explanation: User Response:
EXP_19164
Explanation: User Response:
EXP_19165
Explanation: User Response: Explanation:
114
User Response:
The custom function developer may need to correct the function syntax.
EXP_19166
Explanation: User Response:
EXP_19167
Explanation: User Response:
EXP_19168
Explanation: User Response:
Failed to find function instance API <function name> in module <module name>.
The custom function developer did not implement INFA_EXPR_FunctionInstanceGetUserInterface. The custom function developer needs to implement the function in the implementation file.
EXP_19169
Explanation: User Response: Explanation: User Response:
EXP_19170
Explanation: User Response:
EXP_19171
Explanation: User Response:
EXP_19172
Explanation: User Response:
EXP_19173
Explanation: User Response: Explanation: User Response:
EXP Messages
115
EXP_19174
Explanation: User Response: Explanation: User Response:
EXP_19175
Explanation: User Response: Explanation: User Response:
EXP_19176
Explanation: User Response: Explanation: User Response:
EXP_19177
Explanation: User Response: Explanation: User Response:
EXP_19178
Explanation: User Response: Explanation: User Response:
EXP_19179
Explanation: User Response:
EXP_19180
Explanation: User Response:
116
The function failed for the reason specified in the additional error message. The custom function developer may need to correct the function syntax.
EXP_19181
Explanation: User Response:
EXP_19182
Explanation: User Response:
User-defined function <user-defined function> has a cyclic dependency. Call stack is <call stack>.
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. Modify the user-defined function so that it does not refer to itself or to another user-defined function that refers to the user-defined function specified in the error message.
EXP_19183
Explanation: User Response:
EXP_19185
Explanation: User Response:
EXP_19186
Explanation:
User Response:
EXP_19187
Explanation: User Response: Explanation: User Response:
EXP_19188
Explanation:
EXP Messages
117
EXP_19189
Explanation: User Response:
EXP_19190
Explanation: User Response:
EXP_19191
Explanation: User Response:
EXP_19192
Explanation: User Response:
EXP_19193
Explanation:
User Response:
EXP_19194
Explanation:
Argument index <index number> exceeds the expected number of arguments, <number>, in the expression.
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. Use the correct number of arguments for the expression when you invoke the expression.
User Response:
EXP_19195
Explanation:
Error: A non-callable user-defined function <user-defined function> is being called directly in the expression.
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. Edit the user-defined function to be callable. Or, remove the user-defined function from the expression.
User Response:
118
EXP_19197
Explanation: User Response:
Error: The Designer cannot find function <function name>. The function name may be incorrect.
An expression contains a function that has an incorrect function name. Ensure that the function name is correct.
EXP_20010
Explanation: User Response:
Integration Service failed to parse the date format <date format>. Expected format is seconds and above.
An invalid date format was entered in the SYSTIMESTAMP function. Check the function syntax and enter a valid date format.
EXP_20011
Explanation: User Response:
EXPFN Messages
EXPFN_34016
Explanation:
User Response:
EXPFN_34017
Explanation: User Response:
EXPFN Messages
119
CHAPTER 8
FEXP Messages
FEXP_87001
Explanation: User Response:
The following system error occurred opening the file <file name>: <error number>: <error message>.
The Integration Service could not open the FastExport output file or control file because of a system error. For example, the output file may not exist. Verify that the file exists and is not corrupted.
FEXP_87004
Explanation: User Response:
FEXP_87005
Explanation: User Response:
FEXP_87009
Explanation: User Response:
The following system error occurred spawning the process <ID number>: <error number>: <error message>.
The Integration Service could not start the FastExport process because of the error shown. For example, the machine may be overloaded or low on resources. Fix the error and restart the session.
FEXP_87015
Explanation: User Response:
The following system error occurred reading the output file: <error number>: <error message>.
The Integration Service could not read data from the FastExport output file because of a system error. For example, the output file may be corrupt. Verify that the output file exists and is not corrupted.
120
FEXP_87016
Explanation: User Response:
FEXP_87017
Explanation: User Response:
FEXP_87018
Explanation: User Response:
The following system error occurred closing the file <file name>: <error number>: <error message>.
The Integration Service could not close the FastExport output file or control file because of a system error. For example, the output file may no longer exist. Verify that the file exists.
FEXP_87024
Explanation:
Problem in line number <line number> in code page map file <file name>. Please check the file format specified in file.
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.
FR Messages
FR_3000
Explanation: User Response:
Error opening file <file name>. Operating system error message <error message>.
A file name specified in the session properties is incorrect. The operating system error displays when the file does not exist. In the Workflow Manager, correct the file name in the session properties.
FR_3002
Explanation: User Response:
Error reading file <file name>. Operating system error message <error message>.
This is an operating system error. An operating system error number appears with this message. If necessary, see the operating system documentation for appropriate action.
FR_3013
Explanation: User Response:
FR Messages
121
FR_3015
Explanation: User Response:
FR_3016
Explanation: User Response:
Record length <record ID> is longer than line sequential buffer length <number> for <string>.
Insufficient buffer length. In the session properties, increase the setting for Line Sequential Buffer Length. The record length may not be the size to which the Line Sequential Buffer Length should be increased. Check the source data file.
FR_3023
Explanation: User Response:
FR_3024
Explanation: User Response: Explanation: User Response:
FR_3029
Explanation: User Response:
Delimited file attribute error: escape character cannot be the same as quote character.
You specified the same quote mark for the escape character and the optional quotes character in a delimited flat file source. Specify a different escape or quote character.
FR_3030
Explanation: User Response:
FR_3031
Explanation: User Response:
FR_3032
Explanation: User Response:
FR_3033
Explanation:
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.
There is a missing closing quote in the specified column.
122
User Response:
Review the file and add a closing quote character where appropriate.
FR_3034
Explanation: User Response:
Delimited file reader: Warning! Skipped extra character(s) after the closing quote of column <column name> in file <file name>.
There are additional characters after the closing quote delimiter in the specified column. The Integration Service did not read the extra characters. 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
Explanation: User Response:
FR_3036
Explanation:
Error: Escape character <escape character value> is not in Latin1 code page in ASCII data movement mode.
You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected an escape character for the file source that is not valid in the Latin1 code page. Select an escape character that is valid in the Latin1 code page.
User Response:
FR_3037
Explanation:
Error: Field delimiter string has at least one character <delimiter value> that is not in Latin1 code page in ASCII data movement mode.
You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected a delimiter for the file source that is not valid in the Latin1 code page. Select a delimiter that is valid in the Latin1 code page.
User Response:
FR_3038
Explanation: User Response:
Error: Escape character <escape character value> is invalid in current file code page <code page name> in UNICODE data movement mode.
You configured the Integration Service to run in Unicode mode, and you selected an escape character for the file source that is not valid for the file source code page. Select an escape character that is valid in the source code page.
FR_3039
Explanation: User Response:
Error: Field delimiter string has at least one character <delimiter value> invalid in current file code page <code page name> in UNICODE data movement mode.
You configured the Integration Service to run in Unicode mode, and you selected a delimiter for the file source that is not valid for the file source code page. Select a delimiter that is valid in the source code page.
FR_3041
Explanation: User Response:
Error: Invalid code page <code page name> for delimited flat file.
The code page you selected is not valid for delimited flat file formats. Select a code page that is valid for delimited flat files.
FR Messages
123
FR_3043
Explanation: User Response:
Error: Using EBCDIC-based Multibyte code page <code page name> in ASCII data movement mode is invalid.
You configured the Integration Service to run in ASCII mode and selected an EBCDIC-based multibyte code page for a file source. If data requires an EBCDIC-based multibyte code page, run the Integration Service in Unicode mode. Otherwise, select a valid code page for the source.
FR_3045
Explanation: User Response:
Error: Code page <code page ID> not found. Please install it first.
The Integration Service could not find the code page you specified. Install the correct code page.
FR_3046
Explanation: User Response:
Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width boundary for field <field name>.
Multibyte data does not fit into the fixed-width boundary for this column. Change the field width or pad the column with blanks so that fields fit correctly.
FR_3047
Explanation: User Response:
Error: Invalid code page <code page name> for fixed-width flat file.
The code page you selected is not valid for fixed-width files. Select a code page that is valid for fixed-width files.
FR_3048
Explanation: User Response:
Error: Null character <null character value> is invalid in current file code page <code page name> in Unicode data movement mode.
The null character you specified is invalid in the source flat file code page. Use a null character that is valid in the source flat file code page.
FR_3049
Explanation: User Response:
Error: Null character <null character value> is not in Latin1 code page in ASCII data movement mode.
You configured the Integration Service to run in ASCII mode and specified a null character that is not valid in the Latin1 code page. Specify a null character that is valid in the Latin1 code page.
FR_3050
Explanation: User Response:
Error: Invalid code page <code page name> for fixed-width VSAM file.
The code page you selected is not valid for VSAM files. Select a code page that is valid for VSAM files.
FR_3051
Explanation: User Response:
Error: Invalid binary null character <null character value>. The decimal value is not between 0 and 255.
You entered an invalid null character value. Specify a null character value between 0 and 255.
FR_3053
Explanation:
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.
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.
124
User Response:
Fix the data and the number of bytes to skip between rows/records setting.
FR_3054
Explanation: User Response:
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>.
Remaining data in a non-repeating, binary null field does not end at the fixed-width boundary for that field. Fix the data and/or the fixed-width settings.
FR_3056
Explanation: User Response:
FR_3057
Explanation: User Response:
Error: Insufficient data for fixed-width flat file or fixed-width VSAM file. Row data is <row data>.
The non line-sequential data is too small. The data displayed is the row, including the trailing bytes between records. Make sure the data is the correct length and the bytes between rows match the source file options.
FR_3058
Explanation: User Response:
Error processing COBOL file: cannot parse the input [numeric character in <data> at position <position> has to be in the Latin1 code page].
The reader cannot read the input field because the input field contains characters that are not in the Latin 1 code page. 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).
In a file source, at least one of the REDEFINES statements results in a character exceeding the field boundary. Examine and correct the row where the error occurred. The definition is incorrect. Edit the REDEFINES statement.
FR_3060
Explanation: User Response:
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.
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. Examine and correct the row where the error occurred or edit the REDEFINES statement.
FR_3061
Explanation: User Response:
FR Messages
125
FR_3064
Explanation: User Response:
FR_3065
Explanation: User Response:
Row <row number>, field <column name>: Invalid number - <column data>. The row will be skipped.
The source file contains string data in a numeric column. The Integration Service skips the row. Verify the row in the source file contains valid data.
FR_3066
Explanation: User Response:
Error: Date format string has at least one character decimal value=<number> that is not in Latin1 codepage in ASCII data movement mode.
The date format string for a datetime column contains a character that is not in 7-bit ASCII. In the Designer, edit the flat file source definition using 7-bit ASCII characters for the datetime column format string.
FR_3067
Explanation: User Response:
Row <row number>, field <column name>: Invalid date - <column data>. The row will be skipped.
The source file contains invalid data in a datetime column. The Integration Service skips the row. Verify the row in the source file contains valid data.
FR_3068
Explanation: User Response:
FR_3069
Explanation: User Response:
Error: The character <character> is used as a delimiter and a thousands separator for field <column name>.
In the Designer, you specified the same character as both the file delimiter and as the thousands separator for the specified numeric column. 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
Explanation: User Response:
Error: The character <character> is used as a delimiter and a decimal separator for field <column name>.
In the Designer, you specified the same character as both the file delimiter and as the decimal separator for the specified numeric column. 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
Explanation:
126
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
Explanation: User Response:
Error at row <row number>. A multibyte character spans over two fields or two lines. Record will be skipped.
In the fixed-width file source, a multibyte character in a column spans over two columns. The Integration Service skips the row. 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
Explanation: User Response:
Error: Source file type cannot be indirect for an MQ associated source qualifier.
You selected Indirect for the Source file type. When the mapping contains an associated source qualifier, the source file type must be direct. Select Direct as the source file type.
FR_3077
Explanation: User Response:
Fatal Error: The column <column name> has corrupt formatting information. Resave the information in the repository.
Internal error. Contact Informatica Global Customer Support.
FR_3078
Explanation: User Response:
FR_3085
Explanation: User Response:
ERROR: Row <row number>: <character>-th character is a null character, which is not allowed in a text input file <file name>.
The Integration Service cannot read the input field because it contains a null character. Verify that the source does not have null values.
FR_3107
Explanation: User Response:
ERROR: The character <character> is used as both a column delimiter and a row delimiter.
The session failed because the line break character is the same character as the column delimiter in the flat file. Configure different characters for the flat file line break character and column delimiter character.
FR_3108
Explanation: User Response:
ERROR: DSQ <Source Qualifier name> UCS-2 code page UTF-16BE or UTF-16LE are not supported with this type of file.
The session failed because the UTF-16BE or UTF-16LE code page is not supported for fixedwidth flat files. You can use these code pages with delimited flat files.
FR Messages
127
FR_3110
Explanation: User Response:
FR_3111
Explanation: User Response: Explanation: User Response:
FR_3115
Explanation:
Error: Conflicting settings for NULL handling are specified for the delimited file source <source name>.
The FileRdrTruncateStringNull and FileRdrTreatNullCharAs custom properties are enabled at the same time. These custom properties determine how the Integration Service handles null characters in the flat file source. Disable one of the properties. For more information about custom properties, contact Informatica Global Customer Support.
User Response:
FR_3116
Explanation: User Response:
Error: Invalid NULL replacement character is specified for the delimited file source <source name>.
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. 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.
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. Define a valid single-byte character. For more information about custom properties, contact Informatica Global Customer Support.
Explanation:
User Response:
FTP Messages
FTP_14002
Explanation:
Unable to transfer file using FTP because the TCP/IP address for the specified host could not be obtained.
Could not obtain the TCP/IP address of the remote FTP remote host using the remote host name specified in the FTP connection.
128
User Response:
Verify that the FTP host name provided in the FTP connection is correct. Contact the FTP system administrator.
FTP_14003
Explanation: User Response:
Unable to transfer file using FTP because Integration Service could not create a socket.
The Integration Service could not create the socket due to insufficient resources such as file descriptors, memory, or permissions on the FTP server. Contact the FTP system administrator.
FTP_14004
Explanation: User Response:
Unable to transfer the file using FTP because socket option could not be set.
Internal error. Contact the Informatica Global Customer Support.
FTP_14005
Explanation: User Response: Explanation: User Response:
Unable to transfer the file using FTP because the Integration Service could not connect to the FTP server.
The Integration Service could not connect to the FTP server, possibly because the network is down. Contact the network administrator. The FTP server is not properly configured on the remote machine. Contact the FTP system administrator.
FTP_14006
Explanation: User Response:
Unable to transfer the file using FTP because the Integration Service cannot read the remote file.
The network connection went down after the Integration Service connected to the FTP server. Contact the network administrator, the FTP system administrator, and the Informatica system administrator.
FTP_14007
Explanation: User Response:
Unable to transfer the file using FTP because the format of the FTP response is not expected. The FTP server is not supported.
The Integration Service does not recognize the FTP protocol. Contact Informatica Global Customer Support.
FTP_14008
Explanation: User Response:
FTP_14009
Explanation: User Response:
Unable to transfer file using FTP. Could not log in due to invalid user.
The user name in the FTP connection object is incorrect. Verify the FTP user name in the Workflow Manager.
FTP_14010
Explanation: User Response:
Unable to transfer the file using FTP. Could not log in due to rejected password.
The password in the FTP connection object is incorrect. Verify the FTP password in the connection object.
FTP Messages
129
FTP_14011
Explanation: User Response:
Unable to transfer file using FTP. Connect request rejected by the FTP server.
The FTP server denied connection from the Integration Service. Contact the FTP system administrator.
FTP_14012
Explanation: User Response:
Unable to transfer file using FTP. FTP command <command name> rejected by FTP server.
The FTP user in the FTP connection object does not have read permissions. 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
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. None.
User Response:
FTP_14017
Explanation: User Response:
FTP_14018
Explanation: User Response:
FTP_14019
Explanation: User Response:
Unable to transfer file using FTP file. Error writing to local file.
The Integration Service encountered an error when writing to the source staging file location. Confirm the staging directory specified in the session properties.
FTP_14020
Explanation: User Response:
FTP_14024
Explanation: User Response:
FTP host name <host name> has incorrect format. Specify <hostname> or <hostname>:<port> where 0 <port< 65536.
You entered an FTP host name in the wrong format in the Host Name field in the FTP Connection Editor dialog box. Edit the FTP connection in the Workflow Manager. Specify the host name format as <hostname> or <hostname:port>.
130
FTP_14040
Explanation:
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.
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. 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.
User Response:
FTP_14046
Explanation: User Response:
Cannot reconnect to FTP server at <FTP host>: <control port number> within retry period.
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. Check the status of the FTP server and run the session again. If the session is enabled for recovery, recover the session.
FTP_14047
Explanation:
The source file <file name> or its timestamp was changed after the previous read. Session should now terminate.
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. Run the session again. If the session is enabled for recovery, recover the session.
User Response:
FTP_14048
Explanation:
FTP server does not support the FTP command <FTP command>. Resilience is disabled.
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. For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP commands.
User Response:
FTP_14049
Explanation:
FTP server does not support the FTP command <FTP command>. Cannot restart file transfer to FTP server.
Same as FTP_14048.
FTP_14050
Explanation:
DTM buffer does not contain enough data to restart file transfer. Terminating session.
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. Run the session again.
User Response:
FTP_14055
Explanation: User Response:
FTP Messages
131
FTP_14056
Explanation: User Response:
High availability license is absent. Retry period specified for Integration Service connection to the FTP server is ignored.
The retry period is configured in the FTP connection object, but you do not have the high availability option. The retry period is ignored. None.
FTP_14057
Explanation: User Response:
Unable to transfer files using SFTP because the Integration Service could not get the TCP/IP address for the specified host.
Could not obtain the TCP/IP address of the remote SFTP remote host using the remote host name specified in the SFTP connection. Verify that the SFTP host name provided in the SFTP connection is correct. Contact the SFTP system administrator.
FTP_14058
Explanation: User Response:
Unable to transfer files using SFTP because the Integration Service could not create a socket.
The Integration Service could not create the socket due to insufficient resources such as file descriptors, memory, or permissions on the SFTP server. Contact the SFTP system administrator.
FTP_14059
Explanation: User Response: Explanation: User Response:
Unable to transfer file using SFTP because the Integration Service could not connect to SFTP server.
The Integration Service could not connect to the SFTP server, possibly because the network is down. Contact the network administrator. The SFTP server is not properly configured on the remote machine. Contact the SFTP system administrator.
FTP_14060
Explanation: User Response:
SFTP host name <host name> has incorrect format. Specify <host name>; or <host name>:<port> where 0<port<65536.
The host name specified in the FTP connection is not in the format that the Integration Service expects. Edit the FTP connection in the Workflow Monitor. Specify the host name format as <host name> or <host name:port>.
FTP_14061
Explanation: User Response:
FTP_14062
Explanation: User Response:
132
FTP_14063
Explanation: User Response:
FTP_14064
Explanation: User Response:
Unable to delete the remote file <file name> over SFTP: <system error>.
The SFTP user does not have permission to delete the staging file. Delete the file manually, and contact the administrator of the SFTP system to get permission to delete SFTP files for future sessions.
FTP_14065
Explanation: User Response: Explanation: User Response:
Failed to initialize SSH2 session (transport layer) with SFTP server: <system message>.
The SSH library that the Integration Service uses is not compatible with the library files on the SFTP server. Verify that the SFTP server supports the SSH version that the Integration Service uses. The Integration Service encountered a socket error. As a result, the session failed. Review the error message, correct the error, and run the session again.
FTP_14066
Explanation: User Response:
FTP_14067
Explanation: User Response:
FTP_14068
Explanation: User Response:
Unable to open the remote file <file name> over SFTP: <system message>.
The file does not exist or you do not have the permissions to open the file. Verify the file name and file permissions.
FTP_14074
Explanation: User Response:
The Integration Service did not attempt to connect to SFTP server with publickey authentication because the public key and private key files name were not specified.
The public key and private key file names were not provided in the FTP connection. Specify the public key and private key file name in the FTP connection.
FTP_14081
Explanation: User Response: Explanation: User Response:
FTP_14083
Explanation:
Error: The remote file name for the SFTP connection <connection name> was not specified.
The remote file name in the FTP connection object was not specified.
FTP Messages
133
User Response:
FTP_14084
Explanation: User Response:
Unable to access the private key or public key file. Verify that the correct file path was specified.
The public key or private key file was not specified correctly. Verify that the correct file name and file path is specified in the FTP connection object.
134
CHAPTER 9
HIER Messages
HIER_28004
Explanation: User Response:
HIER_28020
Explanation: User Response:
DTM buffer block is filled, and we can't send the block yet. Need to use heap memory to hold data.
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. Restructure the file so that all of the leaf elements of a parent element appear before the multiple-occurring enclosure elements.
HIER_28028
Explanation: User Response:
HIER_28031
Explanation: User Response:
There are two fields pointing to the same XML node, but the datatypes and lengths do not match.
The Source Qualifier transformation contains different ports based on the same XML element. The datatypes or lengths for these ports are different. Check the Source Qualifier transformation and make sure the datatypes and lengths for all occurrences of the element match.
HIER_28032
Explanation:
Error: There are no fields in any of the groups defined that have a reference to a node in the XML tree.
The XML map for an element in the XML file is blank.
135
User Response:
HIER_28034
Explanation: User Response:
HIER_28041
Explanation: User Response:
HIER_28043
Explanation:
Reader failure: The node <element name> occurs multiple times. This node was marked in the schema as occurring one or less times.
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. Recreate the XML Source Qualifier transformation using a more accurate XML file.
User Response:
HIER_28044
Explanation:
Reader failure: The root node for the given XML does not match the root node in the repository.
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. Check the XML file and then import it again.
User Response:
HIER_28045
Explanation:
User Response:
HIER_28051
Explanation: User Response:
136
CHAPTER 10
ICMD Messages
ICMD_10000
Explanation: User Response:
ICMD_10001
Explanation: User Response:
ICMD_10002
Explanation: User Response:
ICMD_10003
Explanation: User Response:
ICMD_10006
Explanation: User Response:
137
ICMD_10007
Explanation: User Response:
ICMD_10011
Explanation: User Response:
ICMD_10014
Explanation: User Response:
The specified service does not have a process defined on the specified node.
The node is not defined for the service. Verify the command values.
ICMD_10015
Explanation: User Response:
ICMD_10016
Explanation: User Response:
ICMD_10018
Explanation: User Response: Explanation: User Response:
ICMD_10019
Explanation: User Response:
ICMD_10020
Explanation: User Response:
ICMD_10021
Explanation: User Response:
138
ICMD_10022
Explanation:
User Response:
ICMD_10023
Explanation: User Response:
ICMD_10024
Explanation: User Response:
ICMD_10029
Explanation: User Response:
ICMD_10030
Explanation: User Response:
ICMD_10031
Explanation: User Response:
ICMD_10033
Explanation: User Response:
Command [createContents] failed with error [[RSVCSHARED_00208] The session for user [name of the user] has expired and failed to be renewed.
The time settings of the worker node and the gateway node are not synchronized. Synchronize the time settings of the worker node and the gateway node.
ICMD_10035
Explanation: User Response:
ICMD_10036
Explanation: User Response:
ICMD_10038
Explanation: User Response:
ICMD Messages
139
ICMD_10039
Explanation: User Response:
ICMD_10040
Explanation: User Response:
ICMD_10041
Explanation: User Response:
ICMD_10042
Explanation: User Response:
ICMD_10043
Explanation: User Response:
ICMD_10045
Explanation: User Response:
ICMD_10046
Explanation: User Response:
ICMD_10047
Explanation: User Response:
ICMD_10048
Explanation: User Response:
ICMD_10050
Explanation: User Response:
140
ICMD_10051
Explanation: User Response:
ICMD_10053
Explanation: User Response: Explanation: User Response:
ICMD_10058
Explanation: User Response:
Internal error: This command has two options with the same name <option >.
Two identical options exist in infacmd parsing. Contact Informatica Global Customer Support.
ICMD_10061
Explanation: User Response:
ICMD_10064
Explanation: User Response:
ICMD_10065
Explanation: User Response:
ICMD_10066
Explanation: User Response:
ICMD_10067
Explanation: User Response:
ICMD_10068
Explanation: User Response:
ICMD_10069
Explanation: User Response:
ICMD Messages
141
ICMD_10070
Explanation: User Response:
ICMD_10071
Explanation: User Response:
ICMD_10072
Explanation: User Response:
Invalid date format: <date>. Expected date formats are MM/dd/yyyy or yyyy-MM-dd optionally followed by HH:mm:ss.
Invalid date specified. Specify date in format MM/dd/yyyy or yyyy-MM-dd optionally followed by HH:mm:ss.
ICMD_10073
Explanation: User Response:
ICMD_10082
Explanation: User Response:
ICMD_10084
Explanation: User Response:
ICMD_10085
Explanation: User Response:
ICMD_10086
Explanation: User Response:
ICMD_10089
Explanation: User Response:
Invalid port number <port number> for command option <command option>.
Invalid port number specified. Enter a valid port number.
ICMD_10090
Explanation: User Response:
142
ICMD_10091
Explanation: User Response:
ICMD_10092
Explanation: User Response:
ICMD_10093
Explanation: User Response:
ICMD_10097
Explanation: User Response:
ICMD_10098
Explanation: User Response:
ICMD_10099
Explanation: User Response:
ICMD_10100
Explanation: User Response:
ICMD_10101
Explanation: User Response:
ICMD_10104
Explanation: User Response:
ICMD Messages
143
ICMD_10105
Explanation: User Response:
The value <database type> specified for database type option <option name> is not a supported database type. The supported database types are <database types>.
The database type is not supported. Specify one of the supported database types.
ICMD_10106
Explanation: User Response:
The database type specified <database type> requires the additional option <option name> to be specified.
This database type requires that a service name also be specified. Specify the service name.
ICMD_10111
Explanation: User Response:
ICMD_10113
Explanation: User Response:
The domain metadata XML file <file name> is invalid, parse error <error message>.
The domain metadata file specified is not valid. Use another domain metadata file.
ICMD_10114
Explanation: User Response:
ICMD_10115
Explanation: User Response:
ICMD_10116
Explanation: User Response:
ICMD_10117
Explanation: User Response:
ICMD_10118
Explanation: User Response:
ICMD_10119
Explanation: User Response:
Both the port range options <option name> and <option name> need to be specified if used.
Only one port range option was specified. Specify both the minimum and maximum port range options.
144
ICMD_10121
Explanation: User Response:
The backup file <file name> already exists. Use the option <option name> to overwrite it.
The backup file already exists. Specify another backup file or use the -Force option.
ICMD_10122
Explanation: User Response:
ICMD_10129
Explanation: User Response:
When changing the database type, all other database fields are required.
The database type was entered but other database fields were not. Specify all database fields because the database type was modified.
ICMD_10130
Explanation: User Response:
ICMD_10131
Explanation: User Response:
ICMD_10132
Explanation: User Response:
ICMD_10133
Explanation: User Response:
ICMD_10135
Explanation: User Response:
ICMD_10136
Explanation: User Response:
ICMD_10137
Explanation: User Response:
Incorrect date format: <date format>. Expected date formats are [MM/dd/yyyy] or [yyyy-MMdd].
The date is in an unsupported format. Specify the date in the correct format.
ICMD_10138
Explanation:
Repository <repository name> is already associated with the <service name> service.
The repository is already associated with a Web Services Hub.
ICMD Messages
145
User Response:
ICMD_10139
Explanation: User Response:
Repository <repository name> is not associated with the <service name> service.
The repository is not associated with a Web Services Hub. Specify a different repository.
ICMD_10140
Explanation: User Response:
The directory value <file path> is a relative path. Only absolute paths are allowed for log directory.
Relative directory paths are not allowed. Specify an absolute path for the log directory.
ICMD_10141
Explanation: User Response:
ICMD_10142
Explanation: User Response:
Unable to create backup file <file name> with error <error message>.
The backup file is invalid. Specify another backup file.
ICMD_10143
Explanation: User Response:
ICMD_10145
Explanation: User Response:
Unable to add node <node> to the requested domain <domain> with error <error message>.
Unable to add the domain node to the domain. Check the error message and address it accordingly.
ICMD_10146
Explanation: User Response:
Metadata is up to date.
You are attempting to upgrade an object that has been upgraded already. None.
ICMD_10147
Explanation: User Response:
ICMD_10148
Explanation: User Response:
ICMD_10149
Explanation: User Response:
146
ICMD_10150
Explanation: User Response:
ICMD_10152
Explanation: User Response:
ICMD_10155
Explanation: User Response:
The specified object type <object type> is invalid, please see help for valid types.
You did not specify the right object type. Correct the object type and try again.
ICMD_10194
Explanation: User Response:
The input <value> does not conform to the required name=value format.
The input does not match the required format. Reenter the data with name=value without spacing.
ICMD_10195
Explanation: User Response:
Repository Service requires service name, user name, and user password if any are specified.
Not all required Repository Service fields were entered. Make sure that all required fields are entered and try again.
ICMD_10199
Explanation: User Response:
ICMD_10201
Explanation: User Response:
ICMD_10204
Explanation: User Response:
ICMD_10205
Explanation: User Response:
ICMD_10206
Explanation: User Response:
ICMD_10208
Explanation:
ICMD Messages
147
User Response:
ICMD_10209
Explanation: User Response:
The LDAP type value specified <value> is not a valid LDAP type. Use one of the following <types>.
The LDAP directory service specified is not valid. Specify a valid LDAP directory service.
ICMD_10210
Explanation: User Response:
To use HTTPS, specify both the HTTPS port and the keystore file location.
The HTTPS port or the keystore file was not specified. Specify the HTTPS port and the keystore file location.
ICMD_10211
Explanation: User Response:
The keystore password option should only be specified along with the other HTTPS options.
The keystore password cannot be defined without defining the HTTPS port. Omit the keystore password from the command. Define the HTTPS port, keystore password, and the keystore file location.
ICMD_10212
Explanation: User Response:
ICMD_10213
Explanation: User Response:
The keystore file should point to a file, not a directory: <file location>.
The command requires a keystore file name, not a directory. Specify the directory path and file name of the keystore file.
ICMD_10221
Explanation: User Response:
Integration Service <Integration Service name> is not associated with the <Metadata Manager Service name> service.
The Integration Service you specified is not associated with the Metadata Manager Service. Specify a different Integration Service.
ICMD_10226
Explanation: User Response:
ICMD_10228
Explanation: User Response:
The user and group export file <file name> already exists. Use the option <option name> to overwrite it.
The export file already exists. Specify another export file name or use the -Force option.
ICMD_10229
Explanation: User Response:
Cannot find the user and group export file <file name>.
The export file does not exist. Specify the location of the export file.
148
ICMD_10230
Explanation: User Response:
User import conflict: user <user name> and security domain <security domain> already exists in the target domain.
The import file contains users that exist in the target domain. Specify the -ReuseDomainUsersAndGroups option to continue import.
ICMD_10231
Explanation: User Response:
Group import conflict: group <group> and security domain <security domain> already exists in target domain.
The import file contains users that exist in the target domain. Specify the -ReuseDomainUsersAndGroups option to continue import.
ICMD_10232
Explanation: User Response:
ICMD_10324
Explanation: User Response:
Data Source type <data source type> is invalid. Use one of the following data sources: <supported data source types>.
The specified data source type is invalid. Use one of the supported data source types.
ICMD_10325
Explanation: User Response:
Missing required command option <missing lineage option> for lineage integration.
The command is missing a required lineage option. Specify the lineage option for the command.
ICMD_10326
Explanation: User Response:
ICMD_10327
Explanation: User Response:
ICMD_10328
Explanation: User Response:
ICMD_10329
Explanation: User Response: Explanation: User Response:
The Reporting Service repository commands were not found in the classpath.
A CLASSPATH entry is missing or inaccurate. Make sure that the CLASSPATH contains the JAR files that the Reporting Service requires. The JDK version is incorrect. Check the version of the installed JDK.
ICMD_10330
Explanation:
ICMD Messages
149
Make sure that the CLASSPATH contains the JAR files that the Reporting Service requires. The JDK version is incorrect. Check the version of the installed JDK.
ICMD_10331
Explanation: User Response:
The command <command name> on <URL> failed with Error code <error code>.
The infacmd operation failed. Use the returned error code and error message to determine the cause of this error.
ICMD_10333
Explanation: User Response:
The specified Reporting Service <Reporting Service> is enabled. Unable to perform repository action.
Reporting Service is enabled. Disable the service and try again.
ICMD_10334
Explanation: User Response:
ICMD_10335
Explanation: User Response:
The format of the specified user name <user name> for the Administrator is invalid or the user does not exist.
The user name specified in the argument is invalid. Specify the existing user in the format username@securitydomain.
ICMD_10336
Explanation: User Response:
ICMD_10337
Explanation: User Response:
Use option <option name> to specify the path to the keystore file. This option is required to enable SSL.
The LDAP server you want to connect to uses SSL and requires a keystore file. The directory path specified for the keystore file may be invalid. Specify a valid directory path to the keystore file. If a keystore file is not available, connect to the LDAP server without using SSL.
ICMD_10338
Explanation: User Response:
ICMD_10339
Explanation: User Response:
150
ICMD_10343
User Response:
Unable to determine PowerCenter version because operation failed with error <system error message>.
Specify a valid PowerCenter installation directory.
IDM Messages
IDM_24007
Explanation: User Response:
The Data Masking transformation could not read the highgroup.txt file.
The highgroup.txt file is either unavailable or damaged. Download the latest highgroup.txt file to the <PowerCenter Installation Directory>\infa_shared \SrcFiles\.
IDM_24013
Explanation:
User Response:
IDM_24023
Explanation: User Response:
IDM_24030
User Response:
IDM_24036
Explanation: User Response:
IDM_24038
Explanation: User Response:
IDM_24039
User Response:
IDM_24045
User Response:
The Data Masking transformation failed to read the data masking rules.
Run the session again. If the problem persists, contact Informatica Global Customer Support.
IDM Messages
151
IDM_24051
User Response:
IDM_24055
Explanation:
Seed is not between 1 and 1000. Using default value for seed.
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. Configure the mapping parameter value to be a number between 1 and 1000.
User Response:
IDM_24056
Explanation:
Seed defined in the Data Masking default file is not between 1 and 1000. Using 725 as value for seed.
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. 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.
User Response:
IDM_24057
Explanation:
User Response:
IDM_24058
Explanation: User Response:
IDM_24059
Explanation: User Response:
Expression parse fatal error; Failed to parse expression <expression>. Should be: Fatal error while parsing Data Masking transformation expression.
The session failed when the Data Masking transformation attempted to evaluate an expression. 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.
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.
Explanation:
152
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
Explanation: User Response:
IDM_24062
Explanation: User Response:
IDM_24063
Explanation: User Response:
Storage table does not exist. Create the storage table before running a session.
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. 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
Explanation: User Response:
IDM_24065
Explanation:
User Response:
IDM_24066
Explanation: User Response:
IDM_24067
Explanation:
IDM Messages
153
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
Explanation: User Response:
IDM_26001
User Response:
IDM_26002
User Response:
IDM_26003
Explanation: User Response:
IDM_26004
Explanation:
Bounds and blurring do not generate valid range of values for <source>.
The Data Masking transformation cannot apply a mask to a source column. The range masking rule and blurring masking rule combination restricts the Data Masking transformation from generating mask values. Change the range masking rule to a range of values that fall within the blurring range.
User Response:
IDM_26005
Explanation: User Response:
IDM_26006
User Response:
IDM_26007
User Response:
154
IDM_26008
User Response:
IDM_26009
Explanation: User Response:
IDM_26010
Explanation: User Response:
IDM_26011
Explanation: User Response:
IDOC Messages
IDOC_17601
Explanation: User Response:
IDOC_17605
Explanation: User Response:
IDOC_17606
Explanation:
IDOC Messages
155
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.
IDOC_17607
Explanation: User Response:
IDOC_17608
Explanation: User Response:
The number of IDoc types in the property <property> does not match the number specified in <property>.
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. Edit the transformation so that the value for the NumberOfIDocTypes property matches the number of IDoc types listed in the IDocTypeList property.
IDOC_17610
Explanation: User Response:
Error getting metadata for some of the IDocs in the list: <list>.
The Integration Service failed to retrieve the metadata for the IDoc_Writer AEP transformation in a 6.x inbound IDoc mapping. 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.
IDOC_17613
Explanation: User Response:
IDOC_17614
Explanation: User Response:
IDOC_17615
Explanation: User Response:
Error parsing control data. Check the control data for IDoc type <IDoc type>.
The Integration Service failed to parse the IDoc control record data received by the 6.x IDoc_Writer AEP transformation. Correct the source data so that it contains valid control record data.
IDOC_17617
Explanation: User Response:
The segment <IDoc segment> is not allowed in the current IDoc type <type>.
The 6.x IDoc_Writer AEP transformation received data for an invalid segment for the IDoc type. Correct the source data so that it contains only valid segment data as defined by the metadata for the IDoc type.
156
IDOC_17618
Explanation: User Response:
IDOC_17619
Explanation: User Response:
IDOC_17620
Explanation: User Response:
IDOC_17621
Explanation: User Response:
IDOC_17622
Explanation: User Response:
Error appending control record <control record>. Failed to allocate enough memory.
There is not enough memory on the node where the Integration Service process runs to perform the desired operation. Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node.
IDOC_17623
Explanation:
Error appending data record <data record>. Failed to allocate enough memory.
Same as IDOC_17622.
IDOC_17624
Explanation:
The SAPALEIDoc target definition did not receive a control record segment for IDoc type: <IDoc type>.
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. Verify that valid IDoc data is passed to the SAPALEIDoc target definition.
User Response:
IDOC_17625
Explanation:
The SAPALEIDoc target definition did not receive a control record segment. Error encountered in IDoc processing.
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. Verify that valid IDoc data is passed to the SAPALEIDoc target definition.
User Response:
IDOC Messages
157
IDOC_17626
Explanation:
The SAPALEIDoc target definition received an incorrect number of control record segments. Error encountered in IDoc processing.
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. Verify that valid IDoc data is passed to the SAPALEIDoc target definition.
User Response:
IDOC_17627
Explanation:
The SAPALEIDoc target definition did not receive any data segments for IDoc type <IDoc type>. Error encountered in IDoc processing.
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. Verify that valid IDoc data is passed to the SAPALEIDoc target definition.
User Response:
IDOC_17633
Explanation:
IDOC_17642
Explanation: User Response:
IDOC_17643
Explanation: User Response:
IDOC_17644
Explanation: User Response:
IDOC_17645
Explanation: User Response:
IDOC_17646
Explanation: User Response:
Failed to get connection reference for source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
158
IDOC_17647
Explanation: User Response:
Failed to get connection for source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
IDOC_17648
Explanation: User Response:
Failed to initialize reader properties for source qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize the session. The session properties for the Source Qualifier instance might be invalid. Check the additional error message for more information.
IDOC_17649
Explanation:
User Response:
IDOC_17652
Explanation: User Response:
IDOC_17655
Explanation: User Response:
IDOC_17656
Explanation: User Response:
The Integration Service failed to process the IDoc packet for transaction ID = <ID>.
The RFC Destination created in the SAP system for the Integration Service may be invalid. Verify that the RFC Destination is valid.
IDOC_17658
Explanation: User Response:
The SAPALEIDoc source definition can have only one input group.
The SAPALEIDoc source definition contains more than one input group. Recreate the SAPALEIDoc source definition.
IDOC_17659
Explanation: User Response:
IDOC_17662
Explanation: User Response:
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.
The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive.
IDOC Messages
159
IDOC_17666
Explanation: User Response:
IDOC_17668
Explanation: User Response:
IDOC_17669
Explanation:
User Response:
IDOC_17670
Explanation: User Response:
IDoc writer cannot get connection information for the target instance <target>.
Internal error. Contact Informatica Global Customer Support.
IDOC_17671
Explanation: User Response:
IDOC_17672
Explanation: User Response:
IDOC_17675
Explanation: User Response:
IDoc reader failed to support recovery for the Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
IDOC_17676
Explanation: User Response:
IDOC_17677
Explanation: User Response:
160
IDOC_17678
Explanation: User Response:
IDOC_17679
Explanation: User Response:
IDOC_17680
Explanation: User Response:
Reader partition <partition> failed to truncate message cache to last serialized message: <error message>.
The Integration Service could not truncate the last IDoc in the cache. Check the additional error message for more information.
IDOC_17681
Explanation: User Response:
IDOC_17682
Explanation: User Response:
IDOC_17684
Explanation: User Response:
IDOC_17685
Explanation: User Response:
IDOC_17690
Explanation: User Response:
Reader partition <partition> failed to close checkpoint at real-time flush point: <error message>.
The Integration Service could not commit IDocs to the target at the end of the Real-time Flush Latency interval. The session failed. Check the additional error message for more information.
IDOC_17691
Explanation: User Response:
IDOC Messages
161
IDOC_17692
Explanation: User Response:
Recovery is not supported for old versions of SAP outbound IDoc mappings.
This is an informational message. The Integration Service cannot support recovery for outbound IDoc mappings you created in PowerCenter Connect for SAP R/3 7.0 or earlier. If you want to run a session to read outbound IDocs from SAP using ALE, create an outbound IDoc mapping.
IDOC_17695
Explanation: User Response:
IDOC_17696
Explanation: User Response:
IDOC_17697
Explanation:
IDOC_17698
Explanation:
IDOC_17699
Explanation:
IDOC_17700
Explanation:
IDOC_17704
Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>.
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. Verify that the SAP/ALE IDoc Prepare transformation for the inbound IDoc contains values for the mandatory segment.
Explanation:
User Response:
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>.
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. Correct the source data so that the number of records for the segment do not exceed the maximum number allowed.
Explanation:
User Response:
162
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>.
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. Correct the source data so that the number of records for the segment meet the minimum number of records allowed.
Explanation:
User Response:
IDOC_17707
Explanation: User Response:
IDOC_17708
Explanation: User Response:
NULL data obtained for all connected fields for the segment <segment name>.
Data for the connected fields in the named segment is missing. Make sure the data exists for the connected fields in the named segment.
IDOC_17709
Explanation: User Response:
Data <data> overflow at port <port number>. If the error threshold is not met, the row will be sent through the ErrorIDocData port.
The SAP/ALE IDoc Prepare transformation received data that is larger than the precision for the row. Correct the source data so that the value matches the precision for the row.
IDOC_17710
Explanation:
<Value> orphan rows were received by the SAP/ALE IDoc Prepare transformation.
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. Verify that all child rows have parent rows.
User Response:
IDOC_17711
Explanation: User Response:
<Value> duplicate rows were received by the SAP/ALE IDoc Prepare transformation.
The SAP/ALE IDoc Prepare transformation received duplicate rows. Eliminate the duplicate rows in the data.
IDOC_17712
Explanation:
The SAP/ALE IDoc Prepare transformation received orphan row <index of the row> in group <group> with primary key <primary key> and foreign key <foreign key>.
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. Verify that all child rows have parent rows.
User Response:
IDOC_17713
Explanation: User Response:
Duplicate row received in group <group> with primary key: <primary key>.
The SAP/ALE IDoc Prepare transformation received duplicate rows. Eliminate the duplicate rows in the data.
IDOC Messages
163
IDOC_17714
Explanation: User Response:
IDOC_17720
Explanation: User Response:
The SAP/ALE IDoc Prepare transformation has an unconnected input group. Connect all input groups for the transformation.
One or more input groups in the SAP/ALE IDoc Prepare transformation are not connected. Make sure that all input groups are connected.
IDOC_17721
Explanation: User Response:
IDOC_17722
Explanation:
Syntax validation failed for document number <document number> because mandatory segment is missing: <segment name>.
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. Correct the source data so that the mandatory segment contains values.
User Response:
IDOC_17723
Explanation:
Syntax validation failed for document number <document number> because maximum occurrence is higher than maximum limit for: <segment name>.
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. Correct the source data so that the number of records for the segment do not exceed the maximum number allowed.
User Response:
IDOC_17724
Explanation:
Syntax validation failed for document number <document number> because minimum occurrence is less than the minimum limit for: <segment name>.
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. Correct the source data so that the number of records for the segment meet the minimum number of records allowed.
User Response:
IDOC_17725
Explanation:
Extended Syntax Check skipped because Error Output port is missing. Recreate the SAP/ALE IDoc Interpreter transformation.
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. Recreate the SAP/ALE IDoc Interpreter transformation.
User Response:
164
IDOC_17742
Explanation: User Response:
Cache folder specified for the SAP/ALE IDoc Prepare transformation <transformation name> is invalid.
The cache directory specified for the SAP/ALE IDoc Prepare transformation does not exist. In the session properties, enter a valid directory for the Cache Directory property.
IDOC_17743
Explanation: User Response:
The Integration Service could not access the cache block in group <group>. Increase the cache size.
The cache size specified for the SAP/ALE IDoc Prepare transformation is inadequate. In the session properties, increase the cache size.
IDOC_17744
Explanation: User Response:
The SAP/ALE IDoc Prepare transformation did not receive control record data for the IDoc type <IDoc type>.
The source in the inbound IDoc mapping does not contain valid data for the IDoc control record. Verify that the source data contains valid control record data.
IDOC_17747
Explanation:
<Value> orphan rows were received by the SAP/ALE IDoc Interpreter transformation.
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. Verify that all child rows have parent rows.
User Response:
IDOC_17748
Explanation:
The SAP/ALE IDoc Interpreter transformation received orphan row <index of the row> in group <group> with primary key <primary key>.
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. Verify that all child rows have parent rows.
User Response:
IDOC_17749
Explanation:
<Value> duplicate rows were received by the SAP/ALE IDoc Interpreter transformation.
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. Verify that each segment in the IDoc message has a unique segment number.
User Response:
IDOC_17750
Explanation: User Response:
IDOC_17755
Explanation: User Response:
IDOC Messages
165
CHAPTER 11
JMS Messages
JMS_1001
Explanation: User Response:
JMS_1002
Explanation: User Response:
The object <object name> looked up from JNDI is not a Destination object.
The value for JMS Destination in the JMS application connection is not valid. Enter a valid value for JMS Destination. Use a value that exists in the JNDI configuration.
JMS_1003
Explanation: User Response:
JMS_1004
Explanation:
User Response:
JMS_1005
Explanation:
User Response:
166
JMS_1006
Explanation:
User Response:
JMS_1007
Explanation: User Response:
JMS_1008
Explanation: User Response:
JMS_1009
Explanation: User Response:
JMS_1010
Explanation: User Response:
JMS_1011
Explanation: User Response:
JMS_1012
Explanation: User Response:
JMS_1013
Explanation: User Response:
JMS_1014
Explanation: User Response:
JMS Messages
167
JMS_1015
Explanation: User Response: Explanation: User Response:
JMS_1018
Explanation: User Response:
JMS_1019
Explanation: User Response: Explanation: User Response:
JMS_1020
Explanation: User Response:
JMS_1021
Explanation: User Response:
Failed to create the message consumer because of conflicting JMS session and JMS connection objects.
Internal error. Contact Informatica Global Customer Support.
JMS_1022
Explanation: User Response:
JMS_1023
Explanation: User Response: Explanation: User Response:
Failed to get the Queue Connection Factory <queue connection factory>. Reason: <error message>.
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. Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in the JNDI configuration. The JNDI server may not be running. Verify that the JNDI server is running. If necessary, start the JNDI server.
168
JMS_1024
Explanation: User Response: Explanation: User Response:
Failed to get the Topic Connection Factory <topic connection factory>. Reason: <error message>.
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. Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in the JNDI configuration. The JNDI server may not be running. Verify that the JNDI server is running. If necessary, start the JNDI server.
JMS_1026
Explanation: User Response:
The file jndi.properties is not found. No additional SSL related properties are used at runtime.
The Integration Service could not run the session with SSL, because it could not find the JNDI.properties file. 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
Explanation: User Response:
Error in getting the session extension information for Source Qualifier <Source Qualifier name>.
The Integration Service cannot read the session properties. The repository may contain inconsistencies. Contact Informatica Global Customer Support.
JMS_2025
Explanation: User Response:
An error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.
The Integration Service could not process a message. Check the additional error message for more information.
JMS_2026
Explanation: User Response:
JMS error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.
The Integration Service encountered a JMS error while processing a message. Check the additional error message for more information.
JMS_2027
Explanation: User Response:
The data received is too large for processing the field <field name> by Source Qualifier <Source Qualifier name>. Reason: <error message>.
The Integration Service cannot process data for the specified field. The data is too large. Check the additional error message for more information.
JMS_2028
Explanation: User Response:
The message received by Source Qualifier <Source Qualifier name> does not match the body definition.
The Integration Service received a message whose body fields do not match the source definition. The Integration Service rejected the message. Make sure the body fields of the messages the Integration Service reads from the source match the format of the source definition. Otherwise, the Integration Service rejects the messages.
JMS Messages
169
JMS_2029
Explanation: User Response:
The Source Qualifier <Source Qualifier name> encountered an error in closing the consumer. Reason: <error message>.
The Integration Service could not close the JMS consumer. Check the additional error message for more information.
JMS_2032
Explanation: User Response:
Unknown error occurred while writing the data to the DTM buffer by Source Qualifier <Source Qualifier name>. Reason: <error message>.
The Integration Service encountered an unknown error. Check the additional error message for more information.
JMS_2035
Explanation: User Response:
The partition #<number> of Source Qualifier <Source Qualifier name> failed to get cache coordinator for recovery.
Internal error. Contact Informatica Global Customer Support.
JMS_2036
Explanation: User Response:
File cache folder is not provided. Please enter a file cache folder.
You enabled message recovery for the session, but did not specify a file cache folder. In the session properties, enter a file cache folder.
JMS_2037
Explanation: User Response:
Failed to create storage information object for Guaranteed Message Delivery. Reason: <error message>.
You ran a session with message recovery enabled for the session. The session failed when the Integration Service tried to write data to the recovery cache. Check the additional error message for more information.
JMS_2038
Explanation: User Response:
JMS_2041
Explanation: User Response:
JMS_2042
Explanation: User Response:
JMS_2043
Explanation: User Response:
170
JMS_2044
Explanation: User Response:
Source Qualifier <Source Qualifier name> encountered an error while acknowledging the message. Reason: <error message>.
The Integration Service encountered an error acknowledging a source message. Check the additional error message for more information.
JMS_2046
Explanation:
A data conversion error happened while processing the message for field <field name> in the Source Qualifier <Source Qualifier name>.
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. Make sure that the datatype for the field in the JMS source messages is compatible with the datatype in the source definition.
User Response:
JMS_2047
Explanation: User Response:
JMS_2048
Explanation: User Response:
JMS_2050
Explanation: User Response:
Source Qualifier <Source Qualifier name> encountered error while receiving the JMS message. Reason: <error message>.
The Integration Service encountered a JMS error. Check the additional error message for more information.
JMS_2051
Explanation: User Response:
The requested datatypes do not match the data written to the recovery cache. The cache may be corrupt.
The message recovery cache file may contain inconsistencies. Manually delete the corrupted cache file.
JMS_2052
Explanation: User Response:
JMS_2063
Explanation: User Response:
The Integration Service fails a JMS real-time session that is enabled for recovery and contains multiple partitions.
A JMS real-time session that contains multiple partitions cannot be enabled for recovery. Delete the partitions or do not enable the session for recovery.
JMS Messages
171
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>.
Restart the session. If the problem persists, contact Informatica Global Customer Support.
User Response:
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>.
Restart the session. If the problem persists, contact Informatica Global Customer Support.
User Response:
JMS_3003
Explanation: User Response:
JMS_3004
Explanation: User Response:
JMS_3005
Explanation: User Response:
JMS_3006
Explanation: User Response:
JMS_3007
Explanation: User Response:
JMS_3008
Explanation:
User Response:
Check the additional error message for more information. Contact Informatica Global Customer Support.
JMS_3009
Explanation:
User Response:
Check the additional error message for more information. Contact Informatica Global Customer Support.
172
JMS_3013
Explanation: User Response:
JMS_3014
Explanation: User Response:
JMS_3015
Explanation: User Response:
An invalid row type was encountered. JMS writer will publish a message if the row type is INSERT, UPDATE, and DELETE.
The row type for the source rows is Data Driven, but must be Insert, Update, or Delete. 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
Explanation: User Response:
JMS_3017
Explanation: User Response:
The value provided for <property name> in the JMS connection <connection name> is invalid. Reason: <error message>.
The value for the specified property is not valid. Provide a valid value for the property in the session properties.
JMS_3018
Explanation: User Response:
JMS writer encountered a JMS exception while field <field name> was being processed: <error message>.
The Integration Service encountered a JMS exception while processing the specified field. The Integration Service increased the error threshold as a result of the error. Check the additional error message for more information.
JMS_3020
Explanation:
JMS writer encountered a data conversion error while field <field name> was being processed.
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. Make sure the datatypes in the target definition are compatible with JMS datatypes.
User Response:
JMS_3021
Explanation: User Response:
JMS_3022
Explanation: User Response:
JMS Messages
173
JMS_3023
Explanation: User Response:
JMS_3024
Explanation: User Response:
JMS_3025
Explanation: User Response:
JMS writer received NULL for the field <field name>, which is set to Not Null. The message will be rejected.
The specified field is set to Not Null in the target definition for the mapping. 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
Explanation: User Response:
JMS_3027
Explanation: User Response:
JMS_3028
Explanation: User Response:
JMS writer encountered an error in getting the default JMSReplyTo object <object name> from JNDI. Reason: <error message>.
The Integration Service could not obtain a value for JMSReplyTo from JNDI. Check the additional error message for more information.
JMS_3029
Explanation: User Response:
JMS writer encountered an error in processing the data for the field <field name> in the target <target name>. Reason: <error message>.
The Integration Service could not process data for the specified field in the target. Check the additional error message for more information.
JMS_3030
Explanation: User Response:
JMS_3031
Explanation:
The Integration Service cannot guarantee that it will process messages only once. Some messages may be lost or duplicated.
Integration Service did not register the JMS writer with the cache coordinator.
174
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>.
Review the reason for error and make any appropriate changes.
User Response:
JMS_3034
Explanation:
Field <field name> for target <target name> can be projected if IsDestinationNameDynamic is set to true in session properties.
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. Enable IsDestinationNameDynamic in session properties, or remove the link to the destination in the JMS target.
User Response:
JSDK Messages
JSDK_42021
Explanation:
User Response:
JTX Messages
JTX_1001
Explanation: User Response:
Failed to create partition driver. Exception occurred while loading partition driver class from byte code: <exception text>.
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. Use the Designer to recompile the byte code for the Java transformation, and run the session again.
JSDK Messages
175
JTX_1002
Explanation:
User Response:
JTX_1003
Explanation:
User Response:
JTX_1005
Explanation: User Response:
JTX_1006
Explanation: User Response:
Invalid number of groups. Java Transformation should have exactly one input and one output group.
The Java transformation contains more than one input group or output group. Edit the Java transformation in the Designer and remove the extra group or groups.
JTX_1008
Explanation: User Response:
Row type <row type> is invalid. Valid row types for setOutRowType API are INSERT, DELETE, and UPDATE.
You used the setOutRowType API to set the output row type for the Java transformation. However, the row type is invalid. Valid row types are INSERT, DELETE, and UPDATE. Change the row type for the setOutRowType API to a valid type.
JTX_1009
Explanation: User Response:
Failed to create partition driver. Invalid byte code for Java transformation.
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. Use the Designer to recompile the byte code for the Java transformation, and run the session again.
JTX_1010
Explanation: User Response:
JTX_1011
Explanation: User Response:
176
JTX_1013
Explanation: User Response:
JTX_1014
Explanation: User Response:
JTX_1015
Explanation: User Response:
JTX_1016
Explanation:
Cannot use Java transformation API <method name> when transformation property <name> is not selected.
You used the API method in an active Java transformation. However, the transformation property was not selected. You must select the transformation property to use the API method in an active Java transformation. Use the API method only after setting the appropriate transformation property.
User Response:
JTX_1017
Explanation: User Response:
Cannot use Java transformation API <method name> in a passive Java transformation.
You used the API method in a passive Java transformation, However, you cannot use the specified API method in a passive transformation. If you want to use the API method, create an active Java transformation.
JTX1018
Explanation: User Response:
Cannot set default value for port <name>. Error: <error text>.
The Integration Service failed to evaluate the default value for the port. Verify the default value for the port in the Designer.
JTX_1101
Explanation: User Response:
JTX_1102
Explanation: User Response:
Row type <type> for Java expression is invalid. Valid row types are: INSERT, DELETE and UPDATE.
You used an invalid row type in a Java expression. Valid row types are INSERT, DELETE, and UPDATE. Use a valid row type.
JTX_1103
Explanation:
JTX Messages
177
User Response:
JTX_1104
Explanation: User Response:
JTX_1105
Explanation: User Response:
JTX_1106
Explanation: User Response:
JTX_1107
Explanation: User Response:
JTX_1108
Explanation: User Response:
String parameter of Java expression API method <method name> cannot be NULL.
You passed a NULL value for the String parameter of a Java expression API method. The String parameter cannot take a NULL value. Modify the call the Java expression API method to pass a non-NULL value to the String parameter.
JTX_1109
Explanation: User Response:
Incorrect number of parameters passed to expression <expression name>. <number> parameters passed, expression requires <number>.
You did not pass the required number of parameters to an expression in a Java transformation. Edit the Java code for the transformation and pass the correct number of parameters to the expression.
JTX_1110
Explanation: User Response:
JTX_1111
Explanation: User Response:
Cannot use NULL value for parameter in Java expression API method <method name>.
You passed a NULL value to a parameter in a Java expression API method. However, you cannot pass NULL values for Java expression API method parameters. Pass a non-NULL value for the Java expression API method.
178
JTX_1112
Explanation: User Response:
Truncated string data <data> for parameter X <parameter name> in expression <expression name>.
The length of the string data for the expression exceeded the precision for the string parameter. As a result, the Integration Service truncated the data for the parameter. Increase the precision of the parameter for the expression.
JTX_1113
Explanation: User Response:
Truncated binary data for parameter <parameter name> in expression <expression name>.
The length of the binary data for the expression exceeded the precision for the binary data parameter. As a result, the Integration Service truncated the data. Increase the precision for the binary data parameter for the expression.
JTX_1114
Explanation:
User Response:
JTX_1115
Explanation: User Response:
JTX_1117
Explanation:
User Response:
JTX_60000
Explanation: User Response:
Cannot validate Java transformation. Unable to retrieve metadata extensions from repository.
The Designer or Integration Service encountered an internal error when retrieving the metadata extensions for the Java transformation. Contact Informatica Global Customer Support.
JTX_60001
Explanation: User Response:
Cannot validate Java transformation. Unable to retrieve Java code snippets from the repository.
The Designer or Integration Service encountered an internal error when retrieving the Java code snippets for the transformation from the repository. Contact Informatica Global Customer Support.
JTX_60002
Explanation: User Response:
Cannot validate Java transformation. Unable to retrieve byte code from the repository.
The Designer or Integration Service encountered an internal error when retrieving the byte code for the transformation from the repository. Contact Informatica Global Customer Support.
JTX Messages
179
JTX_60003
Explanation:
Cannot validate Java transformation. Unable to retrieve CRC value from the repository.
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. Contact Informatica Global Customer Support.
User Response:
JTX_60004
Explanation: User Response:
Byte code for the transformation is not in the repository. Java transformation is invalid.
The byte code for the transformation is not in the repository. Compile the Java code for the transformation, and validate the transformation or mapping.
JTX_60005
Explanation: User Response:
JTX_60007
Explanation:
User Response:
JTX_60008
Explanation:
User Response:
JTX_60009
Explanation:
User Response:
JTX_60010
Explanation:
User Response:
JTX_60011
Explanation:
User Response:
180
JTX_60012
Explanation: User Response:
JTX_60013
Explanation:
Cannot validate Java transformation. Unable to retrieve classpath from the repository.
The Designer or Integration Service could not retrieve the value of the classpath for the Java transformation from the repository. This error can occur due to inconsistent data in the repository. Contact Informatica Global Customer Support.
User Response:
JTX_60014
Explanation:
Cannot validate Java transformation. Unable to retrieve precision mode from the repository.
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. Contact Informatica Global Customer Support.
User Response:
JTX Messages
181
CHAPTER 12
LB Messages
LB_47007
Explanation: User Response:
LB_47008
Explanation: User Response:
Submitted task <task name> was canceled because no available node has the resources required by the task.
The Session or Command task failed because no available node has the resources required by the task. 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
Explanation: User Response:
The Integration Service failed to load the external resource manager library due to error <error text>.
The PowerCenter administrator configured PowerCenter to work with a third-party resource manager. The Integration Service is unable to load the resource manager library. 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
182
LB_47011
Explanation: User Response:
The Integration Service failed to retrieve the external resource manager interface due to error <error text>.
The PowerCenter administrator configured PowerCenter to work with a third-party resource manager. The Integration Service is unable to access the resource manager interface. Contact the third-party resource manager technical support.
LB_47012
Explanation: User Response:
The external resource manager interface failed to initialize due to error <error text>.
The PowerCenter administrator configured PowerCenter to work with a third-party resource manager and the resource manager failed to initialize. Contact the third-party resource manager technical support.
LB_47047
Explanation: User Response:
LB_47050
Explanation: User Response:
Received final notice for request on invalid node <node name> with event code <code>.
Internal error. The Load Balancer received a request from a node that has shut down. Contact Informatica Global Customer Support.
LDBG Messages
LDBG_8316
Explanation: User Response:
Error. The DTM server ran out of buffer pool data blocks for Partition Point <partition point name> where <transformation name> is the transformation name.
During a user-defined commit session, the Data Transformation Manager ran out of buffer pool data blocks, which caused the session to fail. 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
Explanation: User Response:
Datablock write-lock error. offset <offset value>, reason [No space left on device].
The Integration Service could not write data to the disk because there is not enough space. 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. 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. Increase the Joiner index and data cache sizes. If possible, increase the index and data cache sizes to hold all of the data.
LDBG Messages
183
LDBG_21149
Explanation:
ERROR determining truncate table order - could not create constraint load dependencies for target.
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. Ensure the validity of dependencies between target tables.
User Response:
LDBG_21178
Explanation:
User Response:
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.
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. 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.
Explanation:
User Response:
LDBG_21511
Explanation: User Response:
LDBG_21604
Explanation: User Response:
LDBG_21605
Explanation: User Response:
LDBG_21633
Explanation: User Response:
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.
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. 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
Explanation:
Error: The Informatica server license does not allow more than one database license to be used at a time.
The Integration Service configuration contains more than one database license.
184
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
LGS_10006
Explanation:
User Response:
LGS_10010
Explanation: User Response:
LGS_10011
Explanation:
Failed to access index file <file name> due to the following error <error text>.
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. 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.
User Response:
LGS_10013
Explanation:
User Response:
LGS_10016
Explanation:
Failed to close the file merge stream due to the following error <error text>.
The Log Manager could not close multiple file streams to the same log event file. This error can occur because the permissions for the log event file were modified after the Log Manager began writing or because the file was removed. 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.
User Response:
LGS_10017
Explanation:
LGS Messages
185
User Response:
Make sure the user account that runs Informatica Services has read and write permission on the shared directory location.
LGS_10019
Explanation:
Failed to open the file stream <file name> due to the following error <error text>.
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. 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.
User Response:
LGS_10021
Explanation: User Response:
Failed to read log event from the file stream <file name> due to the following error <error text>.
The Log Manager attempted to retrieve log events from the log event file. However, the log event file contains inconsistent data. Correct the error indicated in the message.
LGS_10024
Explanation: User Response:
LGS_10026
Explanation: User Response:
The log service configuration is missing the log service directory value for the node <node name>.
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. Configure a directory for the log event files.
LGS_10028
Explanation:
LGS_10029
Explanation:
Failed to flush the file stream <file name> due to the following error <error text>.
The Log Service could not close the log event file. This error can occur when the permissions for a log event file are modified after the Log Service began writing or because the file was removed. 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.
User Response:
LGS_10034
Explanation:
Log request failed due to the following error <error text>. Unable to rollback changes due to the following error <error text>.
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. Correct the errors indicated in the message and make sure the shared directory location is available.
User Response:
186
LGS_10035
Explanation:
User Response:
LGS_10036
Explanation:
User Response:
LGS_10052
Explanation: User Response:
The Log Manager could not find the session or workflow run.
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. 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.
LGS_10060
Explanation: User Response:
The log fetch operation does not accept both Run ID and Run instance name as inputs.
You specified both Run ID and Run instance name. Use the -RunInstance or -RunId option, but not both.
LIC Messages
LIC_10000
Explanation: User Response:
LIC_10004
Explanation: User Response:
LIC_10006
Explanation: User Response:
LIC Messages
187
LIC_10007
Explanation: User Response:
A request was received with the wrong <actual object type> parameter (expected: <expected object type>).
A request was received that had the wrong type of parameter. If the problem persists, contact Informatica Global Customer Support.
LIC_10010
Explanation: User Response:
The input vector must contain license name followed by at least one service name.
A request was received with invalid parameters. If the problem persists, contact Informatica Global Customer Support.
LIC_10011
Explanation: User Response:
LIC_10013
Explanation: User Response:
LIC_10014
Explanation: User Response:
Request parameters must contain a license name followed by an encrypted license key.
A request was received with the wrong number of parameters. If the problem persists, contact Informatica Global Customer Support.
LIC_10015
Explanation: User Response:
LIC_10017
Explanation: User Response:
LIC_10018
Explanation: User Response:
LIC_10019
Explanation: User Response:
Request parameters must contain a valid service name followed by a valid node name.
A request was received with the wrong number of parameters. If the problem persists, contact Informatica Global Customer Support.
LIC_10020
Explanation: User Response:
The operating system type could not be established for node <node name>.
A service was attempting to start on a node where the platform could not be established. If the problem persists, contact Informatica Global Customer Support.
188
LIC_10025
Explanation: User Response: Explanation: User Response:
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.
A request was received to unassign enabled services. Disable services before continuing. A request was received to unassign an unknown service. Verify the service names and resubmit.
LIC_10026
Explanation: User Response:
License <license name>/<license serial number> cannot start service <service name> as it is not licensed to execute on platform <platform name>.
A service was attempting to start on an unlicensed platform. Contact Informatica Global Customer Support to update the license key for the specified platform.
LIC_10027
Explanation: User Response:
LIC_10028
Explanation: User Response:
Failed to add a license key that is invalid because: <reason license key is invalid>.
A request was received to add a license key that is invalid. Verify that the license key being used is correct.
LIC_10030
Explanation: User Response:
Attempted to use license <license name/<license serial number> for PowerCenter <product version> where license was purchased for <license version>.
A service was assigned to a license for a different version. Assign the service to a license for this version.
LIC_10033
Explanation: User Response:
License <license name>/<license serial number> cannot start service <service name> as license has expired on <expiration date>.
A service is assigned to an expired license. Contact Informatica Global Customer Support to extend the license.
LIC_10034
Explanation: User Response:
License <license name>/<license serial number> cannot start service <service name> as license does not support grid processes.
A service with a grid is assigned to a license that does not support grids. Either assign service to a license that supports a grid or remove the grid from service.
LIC_10035
Explanation: User Response:
License <license name>/<license serial number> cannot start repository instance <repo name> as license does not have a valid repository count.
A Repository Service is assigned to a license that does not allocate Repository Services. Assign the Repository Service to a license that supports Repository Services.
LIC_10048
Explanation:
Failed to write license <license name>/<license serial number> new day record for logical CPUs on platform <platform>.
A database write request failed to update records.
LIC Messages
189
User Response:
LIC_10049
Explanation: User Response:
Failed to write license <license name>/<license serial number> new day record for repository instances.
A database write request failed to update records. Verify that the domain configuration database is running.
LIC_10050
Explanation: User Response:
Failed to write license <license name>/<license serial number> record for <actual CPU count for platform> logical CPUs on platform <platform>.
A database write request failed to update records. Verify that the domain configuration database is running.
LIC_10051
Explanation: User Response:
Failed to write license <license name>/<license serial number> record for <actual repo count> repository instances.
A database write request failed to update records. Verify that the domain configuration database is running.
LIC_10052
Explanation: User Response:
Change occurred to service <service name> that could not be found within domain.
The service must have been just deleted. If the problem persists, contact Informatica Global Customer Support.
LIC_10053
Explanation: User Response:
Change occurred to node <node name> that could not be found within domain.
The node must have been just deleted. If the problem persists, contact Informatica Global Customer Support.
LIC_10054
Explanation: User Response:
LIC_10055
Explanation: User Response:
LIC_10056
Explanation: User Response:
License <license name>/<license serial number> cannot start service <service name> as license does not support backup nodes.
A service with a backup node is assigned to a license that does not support high availability. Either assign service to a license that supports high availability or remove backup nodes from service.
LIC_10061
Explanation: User Response:
Cannot validate license usage with invalid service name <service name>.
License authorization was requested for a missing or invalid service name. If the problem persists, contact Informatica Global Customer Support.
190
LIC_10062
Explanation: User Response:
Cannot validate license usage with invalid node name <node name>.
License authorization was requested for a missing or invalid node name. If the problem persists, contact Informatica Global Customer Support.
LIC_10063
Explanation: User Response:
License <license name/license serial number> cannot start service <service name> as license does not support operating system profiles.
An Integration Service that uses operating system profiles is assigned to a license that does not support operating system profiles. 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
Explanation: User Response:
Cannot start service <service name> on node <node name> because this would exceed the number of licensed CPUs for platform <platform name>.
You cannot start the service with the current number of licensed CPUs. 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
LM_36053
Explanation: User Response:
The server mode <current server mode> is invalid. Default server mode <default server mode> will be used.
You have modified the data movement mode in the Administrator tool. Change the data movement mode to ASCII or Unicode by modifying the Administrator tool.
LM_36072
Explanation: User Response:
LM_36129
Explanation: User Response:
LM_36133
Explanation: User Response:
LM Messages
191
LM_36134
Explanation: User Response:
LM_36136
Explanation: User Response:
Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration Service.
The specified task instance did not run. Review the workflow log to view detailed information about why the task instance did not run.
LM_36138
Explanation: User Response:
LM_36210
Explanation: User Response: Explanation: User Response: Explanation: User Response:
LM_36220
Explanation: User Response:
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).
The Integration Service failed to create the named session log file because the session failed during initialization. Check the workflow or server log file to see why the session failed.
LM_36229
Explanation: User Response:
Request failed because the connection was broken or the client is too slow in processing replies, client <name>, connection <name>, request ID <number>.
The Integration Service tried to retrieve a session or workflow log file over a network connection, but the connection was broken or timed out. Check the network connection and try to open the log file again.
192
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.
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>. Verify that the node is available and attempt the connection again. If you use pmcmd, use the options -d <domain> and -sv <service>.
Explanation:
User Response:
LM_36271
Connection request was made from client <client> on host <node> for connection to service type <type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the lookup for the service failed.
The Service Manager could not find the Integration Service in the domain. Verify that the Integration Service is running in the domain. Use the pmcmd options -d <domain> and -sv <service>, rather than the host name and port number options.
LM_36272
Explanation: User Response:
LM_36273
Explanation: User Response:
Failed to look up service in domain <domain>, service <service>, service process <node> from name service lookup using the URI <universal resource identifier>.
Internal error. Contact Informatica Global Customer Support.
LM_36274
Failed to look up service in domain <domain>, service <service>, service process <service process> from name service lookup using this URI <service process> with fault code <code>, fault message <message text>.
The Service Manager failed to provide the connectivity information for the Integration Service for the specified reason. Verify that the domain and the Integration Service are running. Verify that you used the correct uniform resource identifier (URI).
LM_36275
Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the service is not configured to redirect connections.
The Integration Service is configured so that connections are not redirected. In the Integration Service properties, set the custom flag EnableConnectionRedirection to Yes, which is the default value.
LM_36310
Explanation:
LM Messages
193
User Response:
Verify that the workflow log file directory specified in the workflow properties exists and that the user attempting to access the log file has write permission for the file.
LM_36311
Explanation: User Response:
LM_36312
Explanation: User Response:
LM36320
Explanation: User Response:
LM_36338
Explanation: User Response: Explanation: User Response: Explanation: User Response:
Workflow <name> Could not start execution of this workflow because the current run on this Integration Service has not completed yet.
You may be running the specified workflow. Wait until the workflow completes to restart it. You may have attempted to restart a workflow that is suspended but not stopped. To restart a suspended workflow, choose resume to complete the workflow. You made a change to a workflow that is set to run continuously. Stop or unschedule the workflow, save the workflow, and then restart or reschedule the workflow.
LM_36348
Explanation: User Response:
<Workflow, worklet, or session instance name>: Parameter file <name> not found.
The Integration Service cannot locate the parameter file for the named workflow, worklet, or session. Check the workflow or session properties to make sure the named parameter file exists in the specified directory. Also, check to make sure the user accessing the file has read permission for the file.
LM_36349
Explanation: User Response:
LM_36350
Explanation: User Response:
194
LM_36351
Explanation: User Response:
LM_36362
Explanation: User Response:
Workflow <name>: The workflow log count in the repository is negative <number>.
Internal error. Contact Informatica Global Customer Support.
LM_36363
Explanation:
Workflow <name>: Cannot rename workflow log file <file name> to <file name>.
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. Check the disk and directory where the log file is located. Make sure the disk is not out of space.
User Response:
LM_36364
Explanation: User Response:
Workflow <name>: Failed to increment the log file number in the repository.
Internal error. Contact Informatica Global Customer Support.
LM_36366
Explanation: User Response:
<Worklet name>: Failed to set the passed value for variable <name>.
Internal error. The Integration Service failed to pass the initial value of the named variable to the named worklet. Contact Informatica Global Customer Support.
LM_36367
Explanation: User Response:
<Task instance name and path>: Suspension email has an empty user name.
You configured the workflow to send a suspension email, but the email address for the suspension email is missing. Enter an email address in the Email User Name field for the suspension Email task.
LM_36368
Explanation:
User Response:
LM_36369
Explanation:
<Session task instance> <task instance path> Encountered task instance <task instance name> of unknown type.
The Integration Service has encountered a task type that it cannot recognize because the version of the Integration Service and repository are inconsistent. You have upgraded the repository but not the Integration Service. Upgrade the Integration Service.
User Response:
LM Messages
195
LM_36381
Explanation: User Response:
<Worklet name>: Failed to set the passed value for variable <name>. Cannot find a userdefined variable with this name.
The Integration Service attempted to override the initial value of the named variable in the named worklet, but it could not locate the named worklet variable. Make sure you defined the named variable in the worklet.
LM_36382
Explanation:
<Worklet name>: Failed to set the passed value for variable <name>. The variable <name> cannot be found at the parent <workflow or worklet name>.
The Integration Service attempted to override the initial value of the named variable in the named worklet. It could not do this because it could not locate the named parent workflow or worklet variable. Make sure you defined the named variable in the parent workflow or worklet.
User Response:
LM_36383
Explanation: User Response:
LM_36385
Explanation: User Response:
Workflow <name>: Could not acquire the execute lock for Workflow <name>.
You started the specified workflow, but the Load Manager could not lock the workflow before running it. This message occurs when you or another user is currently running the workflow. Make sure that the workflow has finished running before running it again.
LM_36401
Explanation: User Response:
LM_36440
Explanation: User Response:
<Task type> task instance <task instance path>: Error in fetching persistent variable values for <workflow or worklet> <workflow or worklet name>.
The Integration Service failed to get a persistent variable value for the workflow or worklet. Check the Integration Service log and Repository Agent log for more information.
LM_36441
Explanation: User Response:
LM_36471
Explanation:
<Workflow name>: Failover of workflow schedule failed because the information in storage is inconsistent or incomplete.
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. Explicitly schedule the workflow again to run it.
User Response:
196
LM_36476
Explanation: User Response:
<Workflow name>: Failover of workflow execution failed because the workflow cannot be internally scheduled in recovery mode.
After the Integration Service failed over the workflow to another node, an internal limit was exceeded. Try to recover the workflow manually. Also, verify the availability of the node where the service process started the workflow.
LM_36477
Explanation: User Response:
LM_36527
Explanation: User Response: Explanation: User Response:
<Task instance name and path>: Failed to fetch session to send post session email for this session instance.
The repository containing the session object is not running. Start the repository. Internal error. Contact Informatica Global Customer Support.
LM_36528
Explanation: User Response:
<Task instance name and path>: Failed to expand E-mail user name <user name> for this session instance.
Internal error. Contact Informatica Global Customer Support.
LM_36529
Explanation: User Response:
<Task instance name and path>: The e-mail user name in the post session failure e-mail component for this session instance is empty.
You selected the On Failure Email option for the session, but the email address for the postsession email is missing. Enter an email address in the Email User Name field for the post-session Email task.
LM_36530
Explanation:
<Task instance name and path>: Failed to send post session failure e-mail for this session instance.
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. Verify you specify an email profile on the machine hosting the Integration Service, and that the machine has the correct email client.
User Response:
LM Messages
197
LM_36538
Explanation:
<Session instance path>: Unable to write to temporary parameter file <parameter file name> with error <error number> <cause of error>.
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. 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.
User Response:
LM_36539
Explanation:
<Session instance path>: Unable to unlink temporary parameter file <parameter file name> with error <error number> <cause of error>.
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. 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.
User Response:
LM_36543
Explanation: User Response:
LM_36544
Explanation: User Response:
<Task name>: condition expression <expression> will not evaluate to a numeric value.
You may have entered the wrong datatype in the expression. Review the expression in the Workflow Manager to ensure that it uses Numeric datatypes.
LM_36564
Explanation:
<Task name>: Invalid datatype conversion for variable <name>, expression datatype <datatype>, variable datatype <datatype>.
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. Either fix the expression in the Assignment task or change the datatype of the variable.
User Response:
LM_36565
Explanation: User Response:
198
LM_36566
Explanation:
<Task name>: Unable to resolve the left-hand side variable <name> as a user-defined workflow/worklet variable.
In the Workflow Manager, you assigned a value to a variable using the Assignment task. The Integration Service does not recognize the variable as a user-defined workflow or worklet variable. Check the variable declaration in the Assignment task and make sure it matches the name of a user-defined workflow or worklet variable.
User Response:
LM_36567
Explanation: User Response:
LM_36580
Explanation: User Response:
LM_36581
Explanation:
User Response:
LM_36601
Explanation: User Response:
<Timer name> Unable to schedule timer with the timer task manager.
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. Specify a time within the valid range.
LM_36602
Explanation: User Response:
<Variable name> Wait for absolute time specified by variable <variable type>. The variable does not exist.
The variable is not specified in the workflow. Specify the variable in the workflow properties.
LM_36603
Explanation: User Response:
<Variable name> Wait for absolute time specified by variable <variable type>. The variable is not of type date/time.
The variable type entered was not the Date/Time datatype. Change the datatype to Date/Time.
LM_36604
Explanation: User Response:
<Variable name> Wait for absolute time specified by variable <variable type>. The variable value is null.
The value of the variable was null. Specify a value that is not null.
LM Messages
199
LM_36648
Explanation: User Response:
<Event-Wait task>: watch file <indicator file name> was detected, but encountered an error deleting the file. Error code [errno = <error number>, error message <error message>.
An Event-Wait task was configured to delete the file watch indicator file when the Integration Service detected the file. The Integration Service detected the file but failed to delete it. Grant permission to delete the file for the Informatica Services account or the operating system user in the operating system profile.
LM_36823
Explanation: User Response:
LM_44122
Explanation:
LM_44124
Explanation: User Response:
LM_44125
Explanation: User Response:
LM_44127
Explanation: User Response:
LM_44136
Explanation:
User Response:
LM_44180
Explanation:
The number of asynchronous threads for repository connections specified <number of threads> is too low, using default of <number of threads>.
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. To use the default number of threads, remove the LMRepoConnAsyncThreads custom Integration property. Alternatively, you can increase the LMRepoConnAsyncThreads value.
User Response:
200
LM_44181
User Response:
Workflow <workflow name> is impacted. The Integration Service is not configured to run sessions impacted by dependency updates.
In the Administrator tool, configure the Integration Service advanced property to run sessions impacted by dependency updates.
LM_44183
Explanation: User Response:
Scheduling workflow is not allowed because the Integration Service is running in safe mode.
The Integration Service assigned to the workflow is running in safe mode. You cannot schedule workflows when the Integration Service runs in safe mode. 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
Explanation: User Response:
Scheduled workflow <workflow name> was not rescheduled because the Integration Service is running in safe mode.
The workflow runs on a schedule. However, the Integration Service does not run scheduled workflows in safe mode. 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
Explanation: User Response:
User <user name> does not have sufficient privilege to log on while the Integration Service is running in safe mode.
You do not have the required privilege to connect to an Integration Service running in safe mode. Use a user account with the required privilege or wait until the Integration Service is no longer in safe mode.
LM_44188
Explanation: User Response:
<Task name>: Failed to expand email user <name> for this email task.
The Integration Service cannot expand a parameter or variable in the email user name. 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. The Integration Service cannot expand the parameter or variable in the email user name due to an internal error. Contact Informatica Global Customer Support.
LM_44189
Explanation: User Response:
<Workflow name>: Failed to expand email user <name> for this suspension email.
The Integration Service cannot expand a parameter or variable in the email user name. 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. The Integration Service cannot expand the parameter or variable in the email user name due to an internal error. Contact Informatica Global Customer Support.
LM Messages
201
LM_44190
Explanation: User Response:
<Command task name>: Failed to expand command <command name>, with command value <command text>.
The Integration Service cannot expand a parameter or variable in the command text. 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. The Integration Service cannot expand a parameter or variable in the command text due to an internal error. Contact Informatica Global Customer Support.
LM_44193
Explanation:
Integration Service <name> will not perform workflow and schedule failover or recovery when running in safe mode.
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. Change the Integration Service operating mode to normal.
User Response:
LM_44205
Explanation: User Response:
Error using operating system profiles to run task <task name>: <error message>.
The Integration Service could not use the operating system profile assigned to the workflow. See additional error message for more information.
LM_44207
Explanation: User Response:
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.
The Integration Service could not stop or abort the workflow because the stopworkflow or abortworkflow pmcmd has an incorrect run ID parameter. 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.
The Integration Service could not stop or abort the workflow because two or more instances of the same workflow are running. 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
Explanation: User Response:
Cannot wait for workflow <ID = run ID> or a task within the workflow. The run ID is not found on the Integration Service.
You entered the pmcmd waitworkflow with an invalid run ID argument. 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.
202
LM_44211
Explanation: User Response:
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.
You entered the pmcmd waitworkflow with a workflow name, but the Integration Service is running more than one instance of the workflow. 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
Explanation: User Response:
<Workflow or worklet name>: Failed to set the variable assignment value for variable <name>.
The Integration Service cannot assign a value to the variable in a post-session variable assignment. 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
Explanation: User Response:
Request to recover workflow <workflow name> run ID <run ID> does not match the current workflow run ID.
You entered the pmcmd recoverworkflow with a workflow run ID argument that does not match a run ID for a recoverable workflow. 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
Explanation: User Response:
The workflow <name> failed because an operating system profile was not specified and the Integration Service uses operating system profiles.
The Integration Service uses operating system profiles. Specify an operating system profile for the workflow in the folder properties or when you manually start a workflow.
LM_44224
Explanation: User Response:
The workflow <name> failed because the Integration Service is not enabled to use operating system profiles and an operating system profile was specified.
An operating system profile was assigned to the workflow and the Integration Service does not use operating system profiles. Remove the assignment of an operating system profile. Configure the Integration Service to use operating system profiles.
LM_44225
Explanation: User Response:
The Integration Service failed to read parameter file <file name> using the operating system profile.
The Integration Service could not open the parameter file specified for the session. Verify that the operating system user specified in the operating system profile has read permissions on the parameter file.
LM_44226
Explanation: User Response:
LM Messages
203
LM_44227
Explanation: User Response:
LM_44228
Explanation: User Response:
LM_44254
Explanation: User Response:
Workflow [Folder ID = <folder ID>, Workflow ID = <workflow ID>] is enabled for concurrency with same instances names, but workflow run ID is not given for recovery.
You attempted to recover a concurrent workflow with the same instance name without specifying the workflow run ID. Specify the run ID to identify which workflow instance to recover.
LM_44255
Explanation: User Response: Explanation: User Response:
Failed to fetch workflow [Folder ID = <folder ID>, Workflow ID = <workflow ID>] from the repository.
The workflow has been removed from the repository. Specify a valid workflow. The repository contains inconsistent data. Contact Informatica Global Customer Support.
LM_44256
Run instance name [<instance name>] is provided but workflow [Folder ID = <folder ID>, Workflow ID = <workflow ID>] is not enabled for concurrent execution. The instance name will be ignored.
You attempted to run a workflow instance for a workflow that is not enabled for concurrent execution. Do not provide an instance name when running the workflow.
LM_44269
Explanation: User Response:
LMTGT Messages
LMTGT_17801
Explanation:
204
User Response:
Verify that the Integration Service is running. Also verify that the LMAPITarget application connection is configured correctly.
LMTGT_17802
Explanation: User Response:
All relational targets must share the same relational database connection.
The relational targets in the mapping do not use the same relational database connection. Edit the session properties so that each relational target uses the same relational connection.
LMTGT_17803
Explanation:
User Response:
LMTGT_17804
Explanation:
User Response:
LMTGT_17805
Explanation: User Response:
LMTGT_17806
Explanation: User Response:
LMTGT_17808
Explanation: User Response:
LMTGT_17809
Explanation: User Response:
Identifier port is not connected in the mapping. The port must be connected when using the Wait for Commit option.
The Identifier port in the LMAPI target is not connected. However, the Wait for Commit option is selected in the session properties. Connect the Identifier port in the mapping when you select Wait for Commit in the session properties.
LMTGT_17810
Explanation:
LMTGT Messages
205
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
Explanation:
User Response:
LMTGT_17812
Explanation:
Indicator Table name is not specified in the mapping. Indicator Table name is required when using the Wait for Commit option.
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. Enter the name of the indicator table in the Indicator Table field when you select Wait for Commit in the session properties.
User Response:
LMTGT_17818
Explanation: User Response:
The Integration Service cannot fetch workflow <workflow name> for key <key name>.
The Integration Service cannot start the workflow because it does not exist or because it does not have a unique name in the repository. Verify that all workflows scheduled in the LMAPI target exist in the repository and have unique names in the repository.
LMTGT_17820
Explanation: User Response:
LMTGT_17821
Explanation: User Response:
206
CHAPTER 13
MMS Messages
MMS_10109
Explanation:
User Response:
MQ Messages
MQ_29000
Explanation: User Response: Explanation: User Response:
Cannot connect to queue manager <queue manager> reason <reason> <reason message>.
The queue manager name is inaccurate. Check the queue manager name. You might not have proper permission to connect to the queue manager. Verify the privileges to connect to the queue manager.
MQ_29001
Explanation: User Response: Explanation: User Response:
207
MQ_29002
Explanation: User Response:
MQ_29003
Explanation: User Response:
Error disconnecting from queue manager <queue manager> reason <reason> <reason message>.
The Integration Service could not disconnect from the queue manager due to the reason code stated in the message. Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.
MQ_29004
Explanation: User Response:
MQ_29005
Explanation: User Response:
Error getting message from queue <queue>:<queue manager> reason <reason> <reason message>.
The Integration Service failed to get a message from the queue due to the reason code stated in the message. Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.
MQ_29006
Explanation: User Response:
Message data truncated reading from queue <queue>:<queue manager> reason <reason> <reason message>.
The message size is too large for the Integration Service to read. Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.
MQ_29007
Explanation:
No message under cursor while attempting to remove message from queue <queue>:<queue manager> reason <reason> <reason message>.
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
Explanation: User Response:
Error putting message on queue <queue>:<queue manager> reason <reason> <reason message>.
The Integration Service could not put message on the queue due to reason code stated in message. Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.
208
MQ_29009
Explanation: User Response:
Invalid RowsPerMesage value for queue <queue>:<queue manager> (<rows per message> > 0).
The Rows Per Message parameter in the session properties is incorrect. Specify a value greater than 0 for the Rows Per Message in the session properties.
MQ_29010
Explanation:
Error opening cache <cache file> for reading: <operating system error>.
You might not have permission to read from the cache file. The $PMCacheDir variable is incorrect.
User Response:
MQ_29011
Explanation:
Error opening cache <cache file> for writing: <operating system error>.
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
Explanation: User Response:
PowerCenter could not load the MQ driver shared library due to insufficient permissions. Make sure the permissions for the MQ driver file are correct.
MQ_29013
Explanation: User Response:
Delete operation for this target not enabled. Queue connection is <queue>:<queue manager>.
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. Enable delete permission for the Integration Service on the target queue.
MQ_29014
Explanation: User Response:
MsgId field has not been set. Queue connection is <queue>:<queue manager>.
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. Project a port to the MsgId column of the dynamic WebSphere MQ target.
MQ_29100
Explanation: User Response:
MQ Messages
209
MQ_29101
Explanation:
MQ_29102
Explanation:
MQ_29103
Explanation:
MQ_29104
Explanation:
MQ_29105
Explanation: User Response:
MQ_29106
Explanation: User Response:
MQ_29107
Explanation: User Response:
MQ_29108
Explanation: User Response:
MQ_29109
Explanation: User Response:
Line <line>, column <column>: Not enough arguments. <function name> () should have argument(s).
The function in the filter condition does not enough arguments. Apply arguments to the function in the filter condition.
MQ_29110
Explanation: User Response:
Line <line>, column <column>: Too many arguments. <function name> () should have argument(s).
There are too many arguments in a function. Use fewer arguments in a function.
MQ_29111
Explanation: User Response:
Line <line>, column <column>: Wrong type in <function name> (). Argument should be CHAR/ BYTE.
The function expects an argument in MQCHAR or MQBYTE type. Make sure argument is of MQCHAR or MQBYTE type in the filter expression.
210
MQ_29112
Explanation: User Response:
Line <line>, column <column>: Wrong type in <function name> (). Argument should be BOOLEAN.
The function expects an argument in boolean type. Make sure argument is of boolean type in the filter condition.
MQ_29113
Explanation: User Response:
Line <line>, column <column>: Wrong type in <function name> (). Argument should be LONG.
The function expects an argument in MQLONG type. Make sure argument is of MQLONG type in the filter condition.
MQ_29114
Explanation: User Response:
MQ_29115
Explanation: User Response:
Line <line>, column <column>: Bad date format in <function name> (), Argument <argument number> should be <correct date format>.
The argument in the function does not contain the correct date format. Use the <correct date format> for the argument in the filter condition.
MQ_29200
Explanation: User Response:
MQ_29201
Explanation: User Response:
MQ_29202
Explanation: User Response:
MQ_29203
Explanation:
User Response:
MQ_29204
Explanation: User Response:
Error fetching message from queue <queue>:<queue manager> because <error message>.
The Integration Service could not fetch message from the queue due to the error. Correct the error indicated in the error message.
MQ Messages
211
MQ_29207
Explanation: User Response:
MQ_29208
Explanation: User Response:
MQ_29210
Explanation: User Response:
MQ_29211
Explanation:
Warning: Some message data was truncated reading from queue <queue>:<queue manager>.
This is only a warning. The MQ reader truncated one or more MESSAGE_DATA columns because the size of the message exceeded the maximum size for the MESSAGE_DATA port in the MQ Source Qualifier. However, you can increase the size of the MESSAGE_DATA column in the MQ Source Qualifier.
User Response:
MQ_29212
Explanation: User Response:
MQ_29213
Explanation: User Response:
MQ_29214
Explanation: User Response:
MQ_29218
Explanation: User Response:
MQ_29221
Explanation:
212
User Response:
None.
MQ_29222
Explanation: User Response:
Error committing from queue manager <queue manager>: reason <reason> <reason message>.
The Integration Service could not commit messages to the target. The WebSphere MQ system may not contain enough log space. Verify that the WebSphere MQ system contains enough log space. Check the additional error message for more information.
MQ_29223
Explanation: User Response:
Error backing out from queue manager <queue manager>: reason <reason> <reason message>.
The Integration Service could not roll back messages from the target. Check the additional error message for more information.
MQ_29224
Explanation: User Response:
MQ_29225
Explanation: User Response:
MQ_29226
Explanation: User Response:
MQ_29231
Explanation: User Response:
Transactional MQ targets with the same queue manager name cannot be in different TCUs.
The WebSphere MQ targets have the same queue connection but belong to different transaction control units. As a result, the session failed. Make sure that all WebSphere MQ targets with the same queue connection belong to the same transaction control unit.
MQ_29234
Explanation: User Response: Explanation: User Response:
MQ_29237
Explanation: User Response:
Failure occurred while reading messages from the queue in destructive mode.
The WebSphere MQ installation may not allow deleting messages from the queue. Look up the reason code in the WebSphere MQ documentation for instructions to correct the error.
MQ Messages
213
MQ_29238
Explanation: User Response:
MQ_29239
Explanation: User Response:
Reader partition <partition name> failed to close checkpoint at real-time flush: <additional error message>.
There may be insufficient disk space when the Integration Service commits messages to the target after the Real-time Flush Latency period expires. Verify that enough disk space is available in the target.
MQ_29240
Explanation: User Response:
MQ_29241
Explanation: User Response:
MQ_29242
Explanation: User Response:
MQ_29243
Explanation: User Response:
MQ_29244
Explanation: User Response: Explanation: User Response:
Reader partition <partition name> failed doing GMD flush: <additional error message>.
The recovery cache folder may have insufficient memory. Verify the recovery cache folder has sufficient memory for large files. The recovery cache folder may not have write permission. Verify the recovery cache folder has write permission.
MQ_29245
Explanation: User Response:
214
MQ_29246
Explanation: User Response:
MQ_29248
Explanation:
User Response:
MQ_29250
Explanation:
Connection retry period expired. The Integration Service could not connect to MQ queue manager <queue manager>.
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. Verify the MQ queue manager is running. Or, verify that the network is active. Restart the session.
User Response:
MQ_29251
Explanation: User Response:
Resilience is disabled, because Destructive Read and recovery are not configured.
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. In the session properties, configure Destructive Read and recovery.
MQ_29255
Explanation:
The Integration Service truncated message data while reading from queue <queue>:<queue manager> in destructive read mode.
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. Increase the precision of the MESSAGE_DATA column in the MQSeries source definition.
User Response:
MQ_29265
Explanation: User Response:
MQ_29270
Explanation: User Response:
The Integration Service could not create a locale for code page ID: <code page>.
The Integration Service failed to create an I18N converter object. Contact Informatica Global Customer Support.
MQ Messages
215
MQ_29280
Explanation: User Response:
The Integration Service fails a WebSphere MQ real-time session that is enabled for recovery and contains multiple partitions.
A WebSphere MQ real-time session that contains multiple partitions cannot be enabled for recovery. Delete the partitions or do not enable the session for recovery.
216
CHAPTER 14
The following system error occurred when the PowerCenter Integration Service tried to open the control file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not open the HP Neoview Transporter control file because of a system error. For example, the user running the PowerCenter Integration Service does not have write privileges on the directory. Fix the operating system error. For example, assign the user running the PowerCenter Integration Service write privileges on the directory.
User Response:
NEOVIEW_325359
Explanation:
The following system error occurred when the PowerCenter Integration Service tried to spawn process <ID number>: <error number>: <error message>.
The PowerCenter Integration Service could not start the HP Neoview Transporter process because of the error shown. For example, the machine may be overloaded or low on resources. Fix the error and restart the session.
User Response:
NEOVIEW_325362
User Response:
Process <ID number> with the name <name> exited with an unknown status. Please see HP Neoview java transporter logs for more information.
Check the HP Neoview Transporter log file, fix the error, and restart the session.
NEOVIEW_325363
The following system error occurred when the PowerCenter Integration Service tried to get the exit status of Process <ID number> with the name <name>: <error number>: <error message>.
The HP Neoview Transporter process terminated because of the error shown.
Explanation:
217
User Response:
Check the HP Neoview Transporter log file, fix the error, and restart the session.
NEOVIEW_325364
Explanation: User Response:
Process <ID number> with the name <name> exited after receiving signal <number>. Please see HP Neoview java transporter logs for more information.
The HP Neoview Transporter process failed because of the operating signal shown. Check the HP Neoview Transporter log file, fix the error, and restart the session.
NEOVIEW_325365
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to close data file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not close the HP Neoview Transporter data file because of a system error. For example, the file may no longer exist. Fix the operating system error. For example, verify that the file exists.
NEOVIEW_325374
User Response:
NEOVIEW_325378
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to write to control file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not write data to the control file because of a system error. For example, the disk may not have enough free space. Fix the operating system error. For example, free space on the machine.
NEOVIEW_325382
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to open pipe <pipe name>: <error number>: <error message>.
The PowerCenter Integration Service could not open the pipe because of a system error. Fix the operating system error. Check the HP Neoview Transporter log file for more information.
NEOVIEW_325385
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to close pipe <pipe name>: <error number>: <error message>.
The PowerCenter Integration Service could not close the pipe because of a system error. Fix the operating system error. Check the HP Neoview Transporter log file for more information.
NEOVIEW_325388
Explanation: User Response:
NEOVIEW_325389
Explanation: User Response:
The PowerCenter Integration Service failed to open file <file name>. File exists with read-only permissions.
The PowerCenter Integration Service could not open the data file or pipe because a readonly file or pipe with the same name already exists in the directory. Delete the existing file or specify a different name for the data file or pipe.
218
NEOVIEW_325391
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to delete file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not delete the file because of a system error. Fix the operating system error. Check the HP Neoview Transporter log file for more information.
NEOVIEW_325393
Explanation: User Response:
The Neoview writer received an error row with row ID <ID number>.
A transformation in the mapping rejected the row. Check the session log for more information.
NEOVIEW_325394
Explanation: User Response:
The Neoview writer rejected the row with row ID <ID number>.
HP Neoview Transporter rejected the row. Check the session log for more information.
NEOVIEW_325395
Explanation: User Response:
The PowerCenter Integration Service received the following error while writing to the data file <file name>: <error message>.
The PowerCenter Integration Service could not write data to the data file because of a system error. For example, the disk may not have enough free space. Fix the operating system error. For example, free space on the machine.
NEOVIEW_325396
Explanation: User Response:
The PowerCenter Integration Service received the following error while writing to the pipe <pipe name>: <error message>.
The PowerCenter Integration Service could not write data to the pipe because of a system error. For example, the pipe might be broken. Fix the operating system error. Check the HP Neoview Transporter log file for more information.
NEOVIEW_325397
Explanation: User Response:
The PowerCenter Integration Service received the following error while flushing the data file <file name>: <error message>.
The PowerCenter Integration Service could not write data to the data file because of a system error. For example, the disk may not have enough free space. Fix the operating system error. For example, free space on the machine.
NEOVIEW_325398
Explanation: User Response:
The PowerCenter Integration Service received the following error while flushing the pipe <pipe name>: <error message>.
The PowerCenter Integration Service could not write data to the pipe because of a system error. For example, the pipe might be broken. Fix the operating system error. Check the HP Neoview Transporter log file for more information.
NEOVIEW_325399
Explanation:
The following system error occurred when the PowerCenter Integration Service tried to open the data file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not open the HP Neoview Transporter data file because of a system error. For example, the user running the PowerCenter Integration Service does not have write privileges on the directory.
219
User Response:
Fix the operating system error. For example, assign the user running the PowerCenter Integration Service write privileges on the directory.
NEOVIEW_325400
User Response:
There is no HP Neoview Transporter code page that corresponds to the connection object code page.
Update the connection object code page. Or, override the control file and update the encoding value that the HP Neoview Transporter uses for the code page of the data file or pipe. For more information about entering the encoding value in the control file, see the HP Neoview Transporter documentation.
NEOVIEW_325401
Explanation: User Response:
Failed to find the PowerExchange for HP Neoview Transporter license key. Please contact Informatica Global Customer Support.
The license key in the Informatica Administrator does not contain the PowerExchange for HP Neoview Transporter option. Contact Informatica Global Customer Support to get a valid license key.
NEOVIEW_325402
Explanation: User Response:
The PowerCenter Integration Service received the following error while setting the environment for HP Neoview Transporter <error number>: <error message>.
The PowerCenter Integration Service could not set the environment for HP Neoview Transporter because of a system error. Fix the operating system error.
NEOVIEW_325403
Explanation: User Response:
The following system error occurred when the PowerCenter Integration Service tried to read the data file <file name>: <error number>: <error message>.
The PowerCenter Integration Service could not read the HP Neoview Transporter data file or pipe because of a system error. For example, the pipe might be broken. Fix the operating system error. For more information, check the HP Neoview Transporter log file.
NEOVIEW_325404
Explanation:
A data conversion error occurred in row number <number> and column <name>.
The PowerCenter Integration Service encountered illegal characters while parsing the HP Neoview Transporter data file or pipe. For example, the PowerCenter Integration Service encountered letter characters while parsing data for an integer column. Verify that the columns in the source definition have the same datatype as the columns in the Neoview source.
User Response:
NEOVIEW_325405
Explanation: User Response:
NEOVIEW_325407
Explanation: User Response:
Data overflow. Precision of a source column exceeds the column precision in the Source Qualifier.
The precision of the source definition column is lower than the precision of the corresponding column in the HP Neoview source. Update the mapping so that the precision of the source column in the Designer matches the precision of the source column in the database.
220
NEOVIEW_325408
Explanation: User Response:
Number of sorted ports cannot be more than the number of connected ports.
The number of sorted ports specified in the Source Qualifier exceeds the number of connected ports. Reduce the number of sorted ports in the Source Qualifier.
NEOVIEW_325409
Explanation:
The following system error occurred when the PowerCenter Integration Service tried to get the value of some session attributes: <error message>.
The PowerCenter Integration Service could not get the values of some session-level properties such as Number of Sorted Ports, Select Distinct, SQL Query, Source Filter, Source Table Parameter Name, and Target Table Parameter Name. A system error might have occurred or the repository might have inconsistencies. Fix the operating system error. Contact Informatica Global Customer Support.
User Response:
NODE Messages
NODE_10014
Explanation:
User Response:
NTSERV Messages
NTSERV_10000
Explanation: User Response:
NTSERV_10001
Explanation: User Response:
NTSERV_10003
Explanation: User Response:
NODE Messages
221
NTSERV_10005
Explanation: User Response:
NTSERV_10007
Explanation:
NTSERV_10009
Explanation:
NTSERV_10011
Explanation:
NTSERV_10013
Explanation: User Response:
NTSERV_10024
Explanation: User Response:
NTSERV_10025
Explanation:
NTSERV_10026
Explanation:
NTSERV_10027
Explanation:
NTSERV_10028
Explanation:
NTSERV_10029
Explanation:
NTSERV_10031
Explanation: User Response:
222
NTSERV_10032
Explanation: User Response:
NTSERV_10033
Explanation:
NTSERV_10042
Explanation:
NTSERV_10043
Explanation:
NTSERV_10044
Explanation:
NTSERV_10045
Explanation:
NTSERV_10046
Explanation:
NTSERV_10047
Explanation:
NTSERV_10065
Explanation: User Response:
NTSERV_10066
Explanation:
NTSERV_10067
Explanation:
NTSERV_10068
Explanation:
NTSERV_10069
Explanation:
NTSERV_10070
Explanation:
NTSERV Messages
223
NTSERV_10071
Explanation: User Response:
NTSERV_10072
Explanation:
NTSERV_10073
Explanation:
NTSERV_10080
Explanation: User Response:
NTSERV_10081
Explanation: User Response:
NTSERV_10085
Explanation:
NTSERV_10086
Explanation:
NTSERV_10087
Explanation:
NTSERV_10088
Explanation: User Response:
NTSERV_10089
Explanation: User Response:
NTSERV_10091
Explanation: User Response:
Install failed.
The Informatica installation failed. Check the .mif file in the Windows directory for related error messages.
NTSERV_10092
Explanation:
Update failed.
Same as NTSERV_10091.
NTSERV_10093
Explanation:
Deinstall failed.
Windows failed to install the Integration Service.
224
User Response:
NTSERV_10096
Explanation: User Response:
NTSERV_10097
Explanation: User Response:
NTSERV_10098
Explanation: User Response:
NTSERV_10099
Explanation:
NTSERV_10100
Explanation: User Response:
NTSERV_10101
Explanation: User Response:
NTSERV_10102
Explanation: User Response:
NTSERV_10103
Explanation: User Response:
NTSERV_10105
Explanation: User Response:
NTSERV_10106
Explanation: User Response:
NTSERV_10129
Explanation:
NTSERV Messages
225
User Response:
NTSERV_10132
Explanation: User Response:
NTSERV_10133
Explanation: User Response:
NTSERV_10139
Explanation: User Response:
NTSERV_10141
Explanation: User Response:
NTSERV_10143
Explanation: User Response:
NTSERV_10144
Explanation: User Response:
NTSERV_10145
Explanation: User Response:
NTSERV_10146
Explanation: User Response:
NTSERV_10147
Explanation: User Response:
226
NTSERV_10148
Explanation:
User Response:
NTSERV_10246
Explanation: User Response:
NZRDR Messages
NZRDR_10015
Explanation: User Response:
NZRDR_10017
Explanation: User Response:
NZRDR_10109
Explanation: User Response:
NZRDR_10013
Explanation: User Response:
NZRDR_10027
Explanation: User Response:
NZRDR_10028
Explanation: User Response: Explanation: User Response:
NZRDR Messages
227
NZRDR_10030
Explanation: User Response:
NZRDR_10034
Explanation: User Response:
NZRDR_10036
Explanation: User Response: Explanation: User Response:
NZWRT Messages
NZWRT_20029
Explanation: User Response: Explanation: User Response:
NZWRT_20034
Explanation: User Response:
NZWRT_20042
Explanation: User Response:
Relation <table name> does not exist in the Netezza Performance Server or no column found in the table.
The target does not exist or there are no columns in the target. Create a valid Netezza target table in Netezza Performance Server.
NZWRT_20057
Explanation: User Response:
NZWRT_20072
Explanation: User Response:
228
NZWRT_20073
Explanation: User Response:
NZWRT_20075
Explanation: User Response:
NZWRT_20076
Explanation: User Response:
NZWRT_20126
Explanation: User Response:
NZWRT Messages
229
CHAPTER 15
OBJM Messages
OBJM_54505
Explanation: User Response:
The object for which rbrowser information was requested does not exist.
The Repository Agent process could not retrieve object properties from the repository because the object does not exist. The object may be deleted. Refresh the Navigator windows. Check for other error messages in the Repository Service log.
OBJM_54509
Explanation: User Response:
Rbrowser fetch: Unable to get children info. Maybe the childType is invalid. (childType = <type>).
Internal error. Contact Informatica Global Customer Support.
OBJM_54510
Explanation: User Response:
OBJM_54513
Explanation: User Response:
Internal: Do not have proper parent lock to access the summary tree node.
Internal error. Contact Informatica Global Customer Support.
OBJM_54515
Explanation: User Response:
230
OBJM_54538
Explanation: User Response:
OBJM_54543
Explanation: User Response:
OBJM_54544
Explanation: User Response:
OBJM_54545
Explanation: User Response:
ODL Messages
ODL_26001
Explanation: User Response:
ODL_26002
Explanation: User Response:
ODL_26003
Explanation: User Response:
ODL_26004
Explanation: User Response:
ODL Messages
231
ODL_26005
Explanation: User Response:
ODL_26006
Explanation: User Response:
ODL_26007
Explanation: User Response:
ODL_26008
Explanation: User Response:
ODL_26009
Explanation: User Response:
ODL_26012
Explanation: User Response:
ODL_26023
Explanation: User Response:
ODL_26025
Explanation: User Response:
ODL_26026
Explanation: User Response:
ODL_26028
Explanation:
232
User Response:
ODL_26035
Explanation: User Response:
ODL_26036
Explanation: User Response:
ODL_26045
Explanation: User Response:
ODL_26046
Explanation: User Response:
ODL_26047
Explanation: User Response:
ODL_26060
Explanation:
User Response:
Remove the row that caused the Teradata error and restart the session.
ODL_26069
Explanation: User Response:
Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>.
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. 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
Explanation:
Graphic/vargraphic partition key types are supported only on servers with UNICODE data movement enabled.
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.
ODL Messages
233
User Response:
ODL_26095
Explanation:
User Response:
ODL_26111
Explanation: User Response:
High availability license is absent. Resilience timeout specified for database connection <connection name> is ignored.
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. None.
ODL_26113
Explanation: User Response:
Number of Bulk mode parameters=<number of parameters> exceeded the number of parameters supported <number of parameters>.
The number of parameters specified for the DB2BulkModeParameters custom property is greater than four. Verify that the number of parameters specified in the DB2BulkModeParameters custom property is less than or equal to four.
ODL_26114
User Response:
ODL_26115
Explanation: User Response:
<Value> is not a valid key:value pair for the DB2BulkModeParameters custom property.
The value of DATABUFFER, CPUPARALLELISM or WARNINGCOUNT was not specified correctly. Verify that the value of DATABUFFER, CPUPARALLELISM or WARNINGCOUNT is an integer.
ODL_26116
User Response:
The FILETYPEMOD parameter requires single quotes at the start and end of the string value.
Verify that single quotes appear at the start and end of the string value for the FILETYPEMOD parameter. For example, enter FILETYPEMOD:string.
OHS Messages
OHS_99001
Explanation: User Response:
234
OHS_99002
Explanation: User Response:
OHS_99003
Explanation: User Response:
The Integration Service did not set a status for request ID <request ID>.
The Integration Service did not set the status for a successful data extraction request in SAP NetWeaver BI. A successful data extraction request has the status G. Set the status of the data extraction to G in SAP NetWeaver BI.
OHS_99007
Explanation: User Response:
OHS_99012
Explanation: User Response:
The session contains a BW OHS source. BW OHS extraction sessions can only be started by process chain.
OHS data extraction was started from the Workflow Monitor or from the Workflow Manager. Start the process chain manually from SAP or run the Pmstartchain command.
OHS_99014
Explanation: User Response:
OHS_99019
Explanation: User Response:
The BW InfoSpoke metadata has changed since it was imported as a BW OHS source definition. Reimport the source definition.
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. Reimport the BW OHS source definition.
OPT Messages
OPT_63005
Explanation: User Response:
OPT_63006
Explanation:
ERROR: Pushdown optimization could not match PowerCenter datatype <datatype> to a datatype on database <database>.
The Integration Service could not map the datatype correctly. Contact Informatica Global Customer Support.
OPT Messages
235
OPT_63007
Explanation:
User Response:
OPT_63008
Explanation: User Response:
OPT_63009
ERROR: Source-side pushdown optimization stops at transformation <transformation name> because of an internal error that occurred while parsing a timestamp. Contact Informatica Global Customer Support.
An internal error occurred while parsing a timestamp. Contact Informatica Global Customer Support.
OPT_63014
Explanation:
Pushdown optimization to source stops at the transformation <transformation name> because the mapping contains too many pipeline branches.
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. None.
User Response:
OPT_63015
Explanation:
Pushdown optimization to target stops at the transformation <transformation name> because the mapping contains too many pipeline branches.
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. None.
User Response:
OPT_63021
Explanation:
Pushdown optimization stops at the transformation <transformation name> because it is connected to multiple targets.
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. None.
User Response:
OPT_63022
Explanation:
Pushdown optimization stops at the transformation <transformation name> because no port depends on values from the upstream transformation <transformation name>.
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. None.
User Response:
236
OPT_63070
Explanation:
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.
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. Change the partition type for the transformation to hash auto-keys or pass-through.
User Response:
OPT_63072
Explanation:
Pushdown optimization to the source stops at the partition point <transformation name> because the source is not key-range partitioned.
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. Configure the source for key-range partitioning.
User Response:
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.
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. 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.
Explanation:
User Response:
OPT_63077
Explanation:
Pushdown optimization to the source stops at the partition point <transformation name> because the source contains a user-defined filter on a per-partition basis.
You added a user-defined distinct filter condition at the Source Qualifier transformation. Two or more partitions use a different filter condition. The Integration Service cannot push transformation logic to the source when you use a distinct user-defined filter. None.
User Response:
OPT_63078
Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Aggregator transformation is not properly partitioned on the aggregate key.
You configured a group by port for the upstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match. Configure the group by port and partition key to match.
Explanation:
User Response:
OPT_63079
Explanation: User Response:
Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Sorter transformation is not properly partitioned on the distinct sort key.
You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match. Configure the sort key and partition key to match.
OPT Messages
237
OPT_63080
Explanation:
Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Joiner transformation is not properly partitioned on the join key.
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. Configure the join condition and the partition key to match.
User Response:
OPT_63081
Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Aggregator transformation is not properly partitioned on the aggregate key.
You configured a group by port for the downstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match. Configure the group by port and partition key to match.
Explanation:
User Response:
OPT_63082
Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Sorter transformation is not properly partitioned on the distinct sort key.
You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match. Configure the sort key and partition key to match.
OPT_63083
Explanation:
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.
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. Configure the join condition and the key-range partition to match.
User Response:
OPT_63102
Explanation: User Response:
Pushdown optimization stops at Source Qualifier transformation <transformation name> because it contains an SQL override, and view creation is not enabled.
You configured a session that contains an SQL override for pushdown optimization, but you did not configure the session to create a view. 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.
OPT_63106
Explanation: User Response:
Pushdown optimization stops at the Source Qualifier transformation <transformation name> because SQL override is specified for some but not all partitions.
When you configure a session that contains an SQL override for pushdown optimization, you must configure the SQL override for all partitions in the session. Configure an SQL override for all partitions in the session.
OPT_63107
Explanation:
Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains an SQL override with Informatica join syntax.
The SQL override contains Informatica join syntax. Because the Integration Service creates a view to process the SQL override, the syntax must be compatible with the source database.
238
User Response:
Use source database syntax when you write the SQL override.
OPT_63108
Explanation:
Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains a user-defined join with Informatica join syntax.
The user-defined join contains Informatica join syntax. Because the Integration Service pushes the transformation logic for the join to the source database, the syntax must be compatible with the source database. Use source database syntax when you write the user-defined join.
User Response:
OPT_63120
Explanation:
Pushdown optimization stops at the Aggregator transformation <transformation name> because there is an upstream Aggregator transformation.
The Aggregator transformation is the second Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for more than one Aggregator transformation in a pipeline. This occurs because the SQL generated for two consecutive Aggregator transformations results in a nested Aggregator function, which cannot be processed on the database. None.
User Response:
OPT_63131
Explanation:
Pushdown optimization stops at the Joiner transformation <transformation name> because an input pipeline contains an Aggregator transformation.
An Aggregator transformation exists in an input pipeline. The database must perform join operations before aggregation operations, so the Integration Service cannot generate an SQL statement for a Joiner transformation that is downstream from an Aggregator transformation. None.
User Response:
OPT_63133
Explanation: User Response:
Pushdown optimization stops at the Joiner transformation <transformation name> because it is configured for an outer join and the master source joins multiple tables.
The master source joins multiple tables. The Integration Service cannot generate SQL to join multiple tables with an outer join. None.
OPT_63147
Explanation:
Pushdown optimization stops at the Lookup transformation <transformation name> because it is downstream from an Aggregator transformation.
The Lookup transformation is downstream from an Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for a Lookup transformation downstream from an Aggregator transformation. None.
User Response:
OPT_63152
Explanation: User Response:
Pushdown optimization stops at the Sorter transformation <transformation name> because the distinct key <port name> is not used downstream.
The Integration Service cannot generate SQL for a Sorter transformation configured for a distinct sort when the distinct key is not used downstream. None.
OPT Messages
239
OPT_63157
Explanation: User Response:
Pushdown optimization stops at the Union transformation <transformation name> because the sources use different database connections.
The Union transformations joins sources that are from different databases or that use different database connections. If the Union transformation joins sources from the same database, ensure that you specify the same database connection in the session properties.
OPT_63170
Explanation: User Response:
ERROR: Pushdown optimization stops at the transformation <transformation name> because it contains an invalid expression.
Internal error. Contact Informatica Global Customer Support.
OPT_63175
Explanation:
ERROR: Pushdown optimization stops at the transformation <transformation name> because the mapping parameter <mapping parameter name> cannot be expanded.
The transformation contains a mapping parameter that cannot be expanded. The parameter file may be corrupt, the path to the parameter file may be incorrect, or the parameter file name may be incorrect. Modify the parameter file, the path to the parameter file, or the parameter file name.
User Response:
OPT_63177
Pushdown optimization stops at the transformation <transformation name> because expression <expression name> with < parameter name> parameters cannot be pushed to the database.
The expression uses a parameter that represents a datatype that is unsupported on the database. None.
OPT_63193
Pushdown optimization to target stops at the transformation <transformation name> because the expression <expression name> uses a boolean expression for parameter <parameter name>.
The numeric expression contains a boolean subexpression. Numeric and boolean values are not compatible in SQL. To covert a boolean expression to a numeric expression, the database requires a case statement, which cannot be performed with target-side pushdown optimization. None.
Explanation:
User Response:
OPT_63205
Explanation: User Response:
OPT_63206
Explanation: User Response:
240
OPT_63207
Explanation: User Response:
OPT_63213
Explanation:
User Response:
OPT_63214
Explanation: User Response:
OPT_63215
Explanation: User Response:
OPT_63216
Explanation: User Response:
OPT_63217
Explanation: User Response:
Transformation <transformation name> uses a key range data type that cannot be partitioned.
The key range partition key must be a number or a date for a dynamic partitioned session. Disable dynamic partitioning or change the key type to a number or date.
OPT_63218
Explanation: User Response:
OPT_63219
Explanation: User Response:
OPT_63220
Explanation:
Transformation <transformation name> specifies user defined SQL that will not be partitioned.
You enabled dynamic partitioning for a session with a transformation that has user-defined SQL. The session runs in one partition by default.
OPT Messages
241
User Response:
OPT_63221
The Source Qualifier transformation <transformation name> will not be partitioned because one or more transformations upstream from the Source Qualifier transformation cannot be partitioned.
The number of partitions must be consistent across a pipeline in a mapping. If the Integration Service cannot dynamically partition a transformation in a pipeline, it does not partition the pipeline. The session runs in one partition by default. Disable dynamic partitioning.
Explanation:
User Response:
OPT_63222
Explanation:
Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK readers is not supported.
You enabled dynamic partitioning in a session containing an SDK source. You cannot enable dynamic partitioning for SDK and PowerExchange sources and targets. The session runs in one partition by default. Disable dynamic partitioning.
User Response:
OPT_63223
Explanation:
Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK writers is not supported.
You enabled dynamic partitioning in a session containing an SDK target. You cannot enable dynamic partitioning for SDK and PowerExchange sources and targets. The session runs in one partition by default. Disable dynamic partitioning.
User Response:
OPT_63224
Explanation: User Response:
Transformation <transformation name> will not be partitioned because dynamic partitioning of XML readers is not supported.
You enabled dynamic partitioning for a pipeline that contains an XML source transformation. The session runs in one partition by default. Disable dynamic partitioning.
OPT_63225
Explanation: User Response:
Transformation <transformation name> will not be partitioned because dynamic partitioning of XML writers is not supported.
You enabled dynamic partitioning for a pipeline that contains an XML target transformation. The session runs in one partition by default. Disable dynamic partitioning.
OPT_63226
Explanation: User Response:
Transformation <transformation name> will not be partitioned because partitionable attribute <attribute name> has a user specified value.
The Integration Service does not partition a transformation when you enter a value for a partition-level attribute. 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
Explanation:
242
User Response:
OPT_63229
Explanation: User Response:
Unable to determine count of partitions for Dynamic Partitioning because an error was encountered while expanding parameter <parameter name>.
The Integration Service could not determine the number of partitions to create. Verify that the $DynamicPartitionCount session parameter contains a number greater than 1.
OPT_63234
Explanation: User Response:
Dynamic partitioning failed to detect the number of CPUs because of the following system error: <error>.
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. Review the session log for related messages, or contact Informatica Global Customer Support.
OPT Messages
243
CHAPTER 16
PCCL Messages
PCCL_97001
Explanation: User Response:
PCCL_97006
Explanation: User Response:
The Integration Service failed to support recovery for the Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
PCCL_97007
Explanation: User Response:
Failed to get connection reference for Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
PCCL_97008
Explanation: User Response:
Failed to get connection for Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
244
PCCL_97009
Explanation: User Response:
The Integration Service failed to initialize connection properties for the Source Qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize a connection to the source. The connection attributes are invalid. Verify the connection attributes in the connection object.
PCCL_97010
Explanation: User Response:
PCCL_97011
Explanation: User Response:
The Integration Service failed to initialize session properties for the Source Qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize the session. Session properties for the Source Qualifier instance are invalid. Check the additional error message for more information.
PCCL_97012
Explanation: User Response:
The Integration Service failed to initialize the driver for the Source Qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize the session. Session properties for the Source Qualifier instance are invalid. Check the additional error message for more information.
PCCL_97013
Explanation: User Response:
The Integration Service failed to initialize the source for the Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
PCCL_97014
Explanation: User Response:
PCCL_97015
Explanation: User Response:
PCCL_97019
Explanation: User Response:
PCCL_97020
Explanation:
The Integration Service partition <partition> failed to close checkpoint at real-time flush point: <error message>.
The Integration Service could not commit messages to the target at the end of the real-time flush latency interval. The session failed.
PCCL Messages
245
User Response:
PCCL_97021
Explanation: User Response:
The Integration Service partition <partition> failed to close checkpoint at EOF: <error message>.
The Integration Service could not commit messages to the target when it reached the terminating conditions. The session failed. Check the additional error message for more information.
PCCL_97022
Explanation: User Response:
PCCL_97023
Explanation: User Response:
PCCL_97024
Explanation: User Response:
The Integration Service partition <partition> truncated last cached message from cache.
This is an informational message. The Integration Service truncated the last message in the cache. None.
PCCL_97025
Explanation: User Response:
The Integration Service partition <partition> failed to truncate message cache to last serialized message: <error message>.
The Integration Service could not truncate the last message in the cache. Check the additional error message for more information.
PCCL_97026
Explanation: User Response:
The Integration Service partition <partition> failed to flush the cache: <error message>.
The Integration Service could not flush the cache. Check the additional error message for more information.
PCCL_97027
Explanation: User Response:
PCCL_97028
Explanation: User Response:
PCCL_97029
Explanation: User Response:
246
PCCL_97030
Explanation: User Response:
PCCL_97031
Explanation: User Response:
PCCL_97033
Explanation: User Response:
The Integration Service failed to initialize the metadata extension for the Source Qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
PCCL_97034
Explanation: User Response:
Error threshold for the session is reached. The number of errors encountered has exceeded the threshold value <error threshold number>.
The Integration Service has reached the error threshold configured in the session properties. Eliminate the errors in the data. Increase the error threshold.
PCSF Messages
PCSF_10004
Explanation: User Response:
PCSF_10005
Explanation: User Response:
An attempt to <activity> access <object name> failed for <user name> because: <error text>.
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. Verify that the user specified in the command has permission on the object.
PCSF_10006
Explanation: User Response:
PCSF_10007
Explanation: User Response:
PCSF Messages
247
PCSF_10013
Explanation: User Response:
PCSF_10015
Explanation: User Response:
A message was being sent without specify either the domain name or host/port.
The command requires that the domain name or host name and port number be entered as a command option. No domain name or host and port number was entered. Enter the domain name or host name and port number as a command option.
PCSF_10017
Explanation: User Response:
PCSF_10019
Explanation: User Response:
Operation <operation name> of service <service name> failed because: <error text>.
The Service Manager attempted an operation. However, the operation failed because of an error. Correct the error indicated in the message and retry the operation.
PCSF_10020
Explanation: User Response:
PCSF_10024
Explanation: User Response:
Timed out while trying to connect to domain <domain name> to lookup service <service name>.
The PowerCenter Client could not connect the domain within the resilience timeout period. Verify that the domain is running and reconnect to the domain. If the domain is not running, ask the domain administrator to start PowerCenter Services.
PCSF_10025
Explanation: User Response:
PCSF_10027
Explanation: User Response:
PCSF_10028
Explanation: User Response:
Cannot respond to operation <operation name> of service <service name>: <error text>.
The Service Manager attempted an operation. However, the operation failed because of an error. Correct the error indicated in the message and retry the operation.
248
PCSF_10039
Explanation: User Response:
Linked domain <linked domain name> must specify at least one gateway.
Validation for a linked domain failed as no gateways were specified. Make sure you specify at least one gateway.
PCSF_10040
Explanation: User Response:
PCSF_10041
Explanation: User Response:
PCSF_10042
Explanation: User Response:
PCSF_10060
Explanation: User Response:
PCSF_10081
Explanation: User Response:
PCSF_10083
Explanation: User Response:
PCSF_10085
Explanation: User Response:
Failed to read the configuration file from <metadata file name> or <backup metadata file name>.
The disk that stores the metadata file is not accessible. Verify that the metadata file is in an accessible location.
PCSF_10095
Explanation: User Response:
PCSF_10131
Explanation: User Response:
PCSF Messages
249
PCSF_10132
Explanation:
You cannot apply more than one original key to a license. To update an existing license, select a license file with an incremental key.
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. Apply the incremental key to the existing license to update the license. Create a license using the original key.
User Response:
PCSF_10133
Explanation: User Response:
The issue date for the original key must be earlier than the issue dates for the incremental keys.
Each incremental key must be issued after the original key. Contact Informatica Global Customer Support to get a valid incremental key.
PCSF_10135
Explanation: User Response:
PCSF_10136
Explanation: User Response:
License is invalid. The Licensing Service encountered an invalid attribute value in the license.
The key provided was not validated as having proper encryption. Contact Informatica Global Customer Support to get a new license key file.
PCSF_10137
Explanation: User Response:
License is invalid. The Licensing Service encountered an invalid value <begin date value> for the Begin Date attribute.
The license is invalid. The Begin Date attribute encountered in the license file is invalid. Contact Informatica Global Customer Support to get a new license key file.
PCSF_10138
Explanation: User Response:
License is invalid. The Licensing Service encountered an invalid value <expiry date value> for the Expiry Date attribute.
The Expiry Date attribute in the license file is invalid. Contact Informatica Global Customer Support to get a new license key file.
PCSF_10139
Explanation: User Response:
License is invalid. The Licensing Service encountered an invalid value <issue date value> for the Issue Date attribute.
The Issue Date attribute in the license file is invalid. Contact Informatica Global Customer Support to get a new license key file.
PCSF_10140
Explanation: User Response:
PCSF_10141
Explanation:
License is invalid. The Licensing Service encountered an invalid value <number of repositories> for the repositories attribute.
The Service Manager failed to validate the license because the number of repositories is invalid.
250
User Response:
Contact Informatica Global Customer Support to get a new license key file.
PCSF_10304
Explanation:
Cannot connect to URL <URL> to perform operation <operation name> of service <service name>.
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. Verify that the host name and port number for the URL and retry the operation.
User Response:
PCSF_10305
Explanation: User Response:
PCSF_10306
Explanation: User Response:
PCSF_10322
Explanation: User Response:
The following error occurred while logging to Log Service: <error text>.
The Log Manager cannot process log events because of the operating system error shown. For example, the shared file system may be unavailable. Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs directory.
PCSF_10325
Explanation: User Response:
Error threshold exceeded for number of failed log attempts. Disabling guaranteed messaging.
Too many errors occurred while the Log Manager was processing log events. Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs directory.
PCSF_10326
Explanation:
The following error occurred while generating the guaranteed message file: <error text>.
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. Try to fix the operating system error.
User Response:
PCSF_10327
Explanation:
The following error occurred while writing to the guaranteed message file <file name>: <error text>.
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. Try to fix the operating system error.
User Response:
PCSF Messages
251
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.
The incremental key has a different deployment type than the original key that was used to create the license. 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.
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. 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.
The incremental key is for a different PowerCenter edition than the original key that was used to create the license. 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.
The incremental key uses a different serial number than the original key that was used to create the license. 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.
The incremental key is for a different PowerCenter version than the original key that was used to create the license. Contact Informatica Global Customer Support to get a new incremental license key with the correct PowerCenter version.
PCSF_10341
Explanation: User Response:
PCSF_10342
Explanation:
252
User Response:
PCSF_10352
Explanation: User Response:
Upgrade configuration file <file name> is not found. Error: <error text>.
You selected a single Repository Agent or PowerCenter Server configuration file in the Upgrade Wizard, but the file you selected does not exist. Verify that the file exists and open the file again.
PCSF_10353
Explanation: User Response:
PCSF_10354
Explanation:
Unable to identify the service type for configuration file <file name>. The file might be an invalid configuration file.
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. 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.
User Response:
PCSF_10355
Explanation: User Response:
Configuration file <file name> is missing the required option(s) <option names>.
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. Add the required property or properties to the configuration file and validate the file again.
PCSF_10356
Explanation:
File <file name> has extension other than .cfg. Upgrade only works with .cfg file.
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. 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.
User Response:
PCSF_10357
Explanation:
File <file name> contains service <service name> which already exists in domain <domain name>.
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. 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.
User Response:
PCSF Messages
253
PCSF_10358
Explanation:
User Response:
PCSF_10359
Explanation:
File <file name> contains service <service name> which already exists in other configuration files selected for upgrade.
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. Make sure the configuration file have unique values for the <RepositoryName> or <ServerName> properties and validate the files again.
User Response:
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>.
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. Upgrade the Repository Agent for the associated repository before you upgrade the PowerCenter Server.
Explanation:
User Response:
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.
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. 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.
Explanation:
User Response:
PCSF_10374
Explanation: User Response: Explanation:
254
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.
The Upgrade Wizard cannot decrypt the encrypted password in the Repository Agent or PowerCenter Server configuration file. 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
Explanation: User Response:
The Repository Agent configuration file <configuration file name> is located in the PCServer directory. This directory should only contain PowerCenter Server configuration files.
The Repository Agent configuration file is not in the correct directory. Move the Repository Agent configuration file to the global_repo or local_repo directory.
PCSF_10391
Explanation: User Response:
Configuration file contains required option(s) <option names> with empty value.
A property or properties in a Repository Agent or PowerCenter Server configuration files does not have a corresponding value. Add a value for the property in the configuration file and validate and upgrade the configuration file again.
PCSF_10392
Explanation: User Response:
<error text>
The Repository Agent or PowerCenter Server configuration contains an error and the Upgrade Wizard cannot upgrade the configuration file. Correct the error indicated in the message and validate and upgrade the configuration file again.
PCSF_10402
Explanation: User Response:
Unable to validate the log directory <shared disk> due to the error <error>.
The permissions of the shared disk was not validated. Verify the path and directory. The user that starts Informatica Services on the node must have permissions to write to the directory.
PCSF_10404
Explanation: User Response:
PCSF_10407
Explanation: User Response:
PCSF Messages
255
PCSF_10408
Explanation: User Response:
PCSF_10410
The PowerCenter Server configuration file <configuration file name> is located in the global_repo or local_repo directory. These directories should only contain Repository Agent configuration files.
The PowerCenter Server configuration file is not in the correct directory. Move the PowerCenter Server configuration file to the PCServer directory.
PCSF_10414
<error text> Use the previous version of PowerCenter to backup the repository contents and restore them to a new repository with a name that contains valid characters. Then rerun the upgrade utility.
The <RepositoryName> property in the Repository Agent contains a tab character, a trailing space, or one of the following characters: ? " : < > * / \ | . Back up the repository, restore it using a name that does not contain these characters, and the upgrade the Repository Agent configuration file again.
PCSF_10421
Explanation: User Response:
Error parsing upgrade configuration file at line #<line number>. The end string */ for block comment must be at the end of the line.
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. 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
Explanation: User Response:
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.
You started a comment block that was not ended in a Repository Agent or PowerCenter Server configuration file. Correct the configuration file and place the end comment string in the file. Then validate and upgrade the configuration file again.
PCSF_10423
Explanation: User Response:
File <file name> is a Repository Agent configuration file. Choose a PowerCenter Server configuration file or change the configuration file type.
In the Upgrade Wizard, you chose a Repository Agent configuration file, but selected a PowerCenter Server file type. Choose a PowerCenter Server configuration file or change the file type.
PCSF_10424
Explanation: User Response:
File <file name> is a PowerCenter Server configuration file. Choose a Repository Agent configuration file or change the configuration file type.
In the Upgrade Wizard, you chose a PowerCenter Server configuration file, but selected a Repository Agent file type. Choose a Repository Agent configuration file or change the file type.
256
PCSF_10426
Explanation: User Response:
PCSF_10427
Explanation: User Response:
PCSF_10428
Explanation: User Response:
PCSF_10429
Explanation: User Response:
PCSF_10430
Explanation: User Response:
PCSF_10431
Explanation: User Response:
PCSF_10432
Explanation: User Response:
PCSF_10433
Explanation: User Response:
PCSF_10434
Explanation: User Response:
PCSF_10436
Explanation: User Response:
PCSF Messages
257
PCSF_10439
Explanation: User Response:
Failed to load the list of codepages: <SDK exception message from locale manager>
Loading the list of codepages failed when fetching from locale manager. If the problem persists, contact Informatica Global Customer Support
PCSF_10440
Explanation: User Response:
PCSF_10441
Explanation: User Response:
PCSF_10442
Explanation: User Response:
PCSF_10443
Explanation: User Response:
PCSF_10445
Explanation: User Response:
PCSF_10446
Explanation: User Response:
Option memory size <invalid value> must be blank or a number followed by optional K or M.
A number option contained invalid memory size format. Enter a valid memory size format.
PCSF_10458
Explanation: User Response:
PCSF_10459
Explanation: User Response:
PCSF_10460
Explanation: User Response:
Either database service name or connection string should be specified, but not both.
You specified both database service name and database connection string. Use the -DatabaseServiceName or -DatabaseConnectionString option, not both.
258
PCSF_10464
Service process variable <service process variable name> is not an absolute path. Define an absolute path for $WorkflowLogDir and $PMStorageDir in the Integration Service process properties before you use operating system profiles.
The $WorkflowLogDir and $PMStorageDir do not have absolute paths defined in the Integration Service Process properties. Define absolute paths for $WorkflowLogDir and $PMStorageDir in the Integration Service Process properties before you use operating system profiles.
PCSF_10507
Explanation: User Response:
The Integration Service cannot use operating system profiles on Windows node <node name> in <service name>.
Integration Services can use operating system profiles on UNIX nodes. The Integration Service cannot use operating system profiles on Windows nodes. Enable operating system profiles for an Integration Service that runs on UNIX nodes. Disable operating system profiles for the Integration Service.
PCSF_10524
Explanation: User Response:
The selected database type <database type> does not support tablespaces.
The database type you specified does not support tablespaces. Omit the -tablespace option from the command.
PCSF_10535
Explanation:
User Response:
PCSF_10536
Explanation:
Cannot start node because nodemeta.xml does not contain values for the PowerCenter installation directory or version.
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. Back up the domain metadata in the domain configuration database, use infasetup to redefine the node, and restart the node.
User Response:
PCSF_10537
Explanation:
Cannot run application service <service name> of version <service version> on node <node name>.
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. Change the node assignment for the service to a node that contains the required version of PowerCenter.
User Response:
PCSF Messages
259
PCSF_10538
Explanation: User Response:
Cannot create application service <service name> of version <service version> in domain of version <domain version>.
You cannot create the service because the current domain does not contain the version of PowerCenter you want to create the service for. Create an application service of a service version that is supported by the domain.
PCSF_10540
Cannot create service <service name> of version <service version> because the domain has a service <existing service name> of version <service version> associated with a service <service name>.
Create a service that is of same version as its dependent service.
User Response:
PCSF_46000
Explanation: User Response:
PCSF_46002
Explanation: User Response:
PCSF_46003
Explanation: User Response:
Failed to understand the response <response text> from server at <server address>: <error text>.
A PowerCenter component failed to understand the response from a PowerCenter service due to an error. Correct the error indicated in the message.
PCSF_46006
Explanation: User Response:
PCSF_46007
Explanation:
260
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. If the domain is not running, ask the domain administrator to start Informatica Services. If you attempted to connect to a repository with the PowerCenter Client, remove the repository in the Navigator and add the repository again.
PCSF_46008
Explanation: User Response:
PCSF_46009
Explanation:
PCSF_46010
Explanation: User Response: Explanation: User Response:
PCSF_46012
Explanation:
PCSF_46013
Explanation:
Cannot connect to URL < URL > to perform operation <operation name> of service <service name>.
Same as PCSF_10304.
PCSF_46014
Explanation:
PCSF_46015
Explanation:
PCSF Messages
261
PETL Messages
PETL_24042
Explanation:
The Preparer DTM has timed out after waiting <time in seconds> seconds for the Master DTM to connect.
The master DTM process was unable to connect with the preparer DTM process. The master DTM process may have shut down unexpectedly. The master DTM process may be on another node and there may be a network failure. View the workflow log to see if the DTM process started on the node. If the DTM process started and shut down unexpectedly, the error is internal. If the error is not internal, 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.
User Response:
PETL_24045
Explanation:
User Response:
PETL_24046
Explanation:
The Master DTM timed out after <time in seconds> seconds while trying to connect to the Preparer DTM.
The master DTM process timed out attempting to connect with the preparer DTM process. The master DTM and the preparer DTM processes may be running on separate nodes and there is a network failure. The preparer DTM process may have shut down unexpectedly. Same as PETL_24042.
User Response:
PETL_24048
Explanation:
The Master DTM failed to fetch the prepared session from the Preparer DTM.
The master DTM process was unable to connect with the preparer DTM process. The master DTM and preparer DTM processes may be on separate nodes and there may be a network failure. The preparer DTM process may have shut down unexpectedly. Same as PETL_24042.
User Response:
PETL_24049
Explanation: User Response:
Failed to get the initialization properties from the master service process for the prepare phase <error message> with error code <error code>.
The preparer DTM process was unable to retrieve run time properties from the Integration Service due to an error. Use the returned error code error message to determine the cause of this error.
PETL_24061
Explanation:
The Master DTM exceeded the maximum wait time while waiting for all Worker DTMs to connect.
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. Same as PETL_24042.
User Response:
262
PETL_24063
Explanation: User Response:
The Preparer DTM encountered error <error message> with error code <error code> while notifying the Integration Service of the prepare phase status.
An error prevented the preparer DTM process from connecting to the Integration Service. 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>.
An error prevented the preparer DTM process from connecting to the Integration Service. Use the returned error code message to determine the cause of this error.
PETL_24065
Explanation: User Response:
Error: Thread <thread name> exceeded the maximum wait time while waiting for a reply from the Master DTM.
A worker DTM process waited longer than the maximum amount of time allotted to wait for a reply from the master DTM process. Same as PETL_24042.
PETL_24066
Explanation: User Response:
The Master DTM connection with the Worker DTM running partition group <partition group ID> was broken unexpectedly. The Master DTM will abort processing.
The master DTM process detected that a worker DTM process failed unexpectedly. Same as PETL_24042.
PETL_24067
Explanation:
The Worker DTM connection with the Master DTM terminated unexpectedly. The Worker DTM will stop processing the session.
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. Same as PETL_24042.
User Response:
PETL_24072
Explanation:
Error: Thread <thread name> failed to get a reply from the Master DTM.
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. 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.
User Response:
PETL_24074
Explanation: User Response:
Failed to send updates to the master service process. Session run will be terminated.
The master DTM process was unable to send updates to the master service process. Same as PETL_24042.
PETL Messages
263
PMF Messages
PMF_15000
Explanation: User Response:
PMF_15001
Explanation: User Response:
Failed to write to file, there may not be enough space left on the device.
The hard disk is full. Check the disk for free space, and check the session log for related errors.
PMF_15002
Explanation: User Response:
PMF_15003
Explanation: User Response: Explanation: User Response:
PMF_15004
Explanation: User Response: Explanation: User Response:
PMF_15005
Explanation: User Response:
File <file name> is in an unknown state due to error from a previous run.
The system shut down unexpectedly during the previous run. Use the backup file filename.bak.
PMF_15006
Explanation: User Response:
Failed to create file <file name> because file exists and contains data.
The Integration Service failed to remove the previous file and detected a file containing data and failed to overwrite it. Check the file and manually delete it or rename it. Run the session again.
PMF_15007
Explanation:
Failed to read file <file name> because PowerCenter/PowerMart file header is corrupt.
The file might be corrupt due to a system crash on a previous session run.
264
Use the backup file filename.bak, if available, and run the session again. Internal error. Contact Informatica Global Customer Support.
PMF_15008
Explanation: User Response:
PMF_15009
Explanation: User Response:
Specified file name <file name> exceeds the maximum length of 256 characters.
Internal error. You may have repository inconsistencies. Contact Informatica Global Customer Support.
PMF_15010
Explanation: User Response:
PMF_15011
Explanation: User Response:
PMF_15012
Explanation: User Response:
Unable to delete file <cache file name>. System error is <error number> <error message>.
This file might be in use. Check the session that is running. See the system error for more information.
PMF_15013
Explanation: User Response:
Unable to rename file <cache file name> to <cache file name>. System error is <error number> <error message>.
This file might be in use. Check the session that is running. See the system error for more information.
PMF_15014
Explanation: User Response:
Unable to stat file <cache file name>. System error is <error number> <error message>.
The call to get cache file properties failed. Contact Informatica Global Customer Support.
PMF_15016
Explanation: User Response:
Failed to get a shared lock on file <cache file name>. System error is <error number> <error message>.
The file might be in use. A session could be writing to the file. Check the session that is running. See the system error for more information.
PMF_15017
Explanation:
Failed to get an exclusive lock on file <cache file name>. System error is <error number> <error message>.
The file might be in use. A session could be writing to the file.
PMF Messages
265
User Response:
Check the session that is running. See the system error for more information.
PMF_15018
Explanation: User Response:
Failed to unlock file <cache file name>. System error is <error number> <error message>.
The file might be in use. A session could be reading or writing to the file. Check the session that is running. See the system error for more information.
PMF_15019
Explanation: User Response:
PMJVM Messages
PMJVM_42011
User Response:
PR Messages
PR_18001
Explanation:
Application Source Qualifier instance <Application Source Qualifier name> has tree source <tree source definition name> and an Extract Override. Extract override will be ignored.
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. 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.
User Response:
PR_18003
Explanation: User Response: Explanation: User Response:
Tree <tree name> with SetId <tree setid> and Effective Date <date> was not created.
The listed tree does not exist in the PeopleSoft source system or has unexpected conditions. Check the tree in the PeopleSoft source system for problems. If necessary, contact PeopleSoft technical support. The listed tree has no ports connected to an Application Source Qualifier. 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.
266
PR_18004
Explanation:
Application Source Qualifier instance <Application Source Qualifier name> has more than one tree attached.
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. 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.
User Response:
PR_18005
Explanation: User Response:
Tree may only be joined with Detail record: <PeopleSoft record name>.
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. 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
Explanation:
Not all sources are related in Application Source Qualifier <Application Source Qualifier name>.
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. Disconnect one of the unrelated sources. Remove one of the associated source definitions.
User Response:
PR_18007
Explanation: User Response:
Unknown error occurred in Application Source Qualifier <Application Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
PR_18009
Explanation: User Response:
PR_18010
Explanation: User Response:
Tree <tree name> was changed after session run was started.
The listed tree changed in the PeopleSoft system after the Integration Service started the session. 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.
PR Messages
267
PR_18011
Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name> has projected port with no inbound link.
The listed Application Source Qualifier has a connected output port, and the corresponding input port is not connected. Connect the necessary input port, or disconnect the connected output port.
PR_18012
Explanation: User Response:
PR_18013
Explanation: User Response:
Warning: Application Source Qualifier transformation <Application Source Qualifier name> has a larger number of sorted ports than projected output ports.
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. Either lower the Number of Sorted Ports value or increase the number of connected output ports in the Application Source Qualifier.
PR_18020
Explanation:
The language table <language table name>, for the base table <base table name>, does not have rows for the language <language code>.
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. 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.
User Response:
PR_18021
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier> has invalid user defined query <query> with character error at <number> location.
You entered a query containing characters that are not valid in the source application connection code page. Edit the query so all characters are valid in the source database connection code page.
PR_18022
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier> has invalid filter clause <filter> with character error at <number> location.
You entered a filter condition containing characters that are not valid in the application connection code page. Edit the filter condition so all characters are valid in the application connection code page.
PR_18023
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier> has invalid join and/or filter override <join override> with character error at <number> location.
You entered a join condition and/or a source filter condition that contains characters that are not valid in the application connection code page. Edit the join and/or filter conditions so all characters are valid in the application connection code page.
268
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.)
You did not import PeopleSoft tree attributes into the created tree source definition. 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
Explanation: User Response: Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name>: Error in preparing the query for effective date data extraction.
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. Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer. 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. Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer.
PR_18028
Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract Join Order with invalid source names.
In the Effective Date Join Order field, you typed a PeopleSoft record name that is not connected to the Application Source Qualifier. 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.
In the Effective Date Join Order field, you entered too few or too many PeopleSoft record names. 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
Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name> cannot have Effective Date Extract Join Order when number of Effective Dated sources is one.
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. Delete the text from the Effective Date Join Order field in the session properties.
PR_18031
Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name> has invalid Extract Date.
You entered the Extract Date in the wrong date format. Enter the Extract Date in the following format: MM/DD/YYYY HH24:MI:SS.
PR Messages
269
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.
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. 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. You entered an invalid value in the parameter file for the extract date mapping parameter or variable. 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.
You entered a mapping parameter or variable for the PeopleSoft tree name that does not exist in the mapping parameter file for the session. 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. You entered an invalid value in the parameter file for the PeopleSoft tree name mapping parameter or variable. 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.
You entered a mapping parameter or variable for the Effective Date option that does not exist in the mapping parameter file for the session. 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. You entered an invalid value in the parameter file for the Effective Date option mapping parameter or variable. 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.
You entered a mapping parameter or variable for the Set ID option that does not exist in the mapping parameter file for the session. 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.
270
You entered an invalid value in the parameter file for the Set ID option mapping parameter or variable. 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.
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. 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. You entered an invalid value in the parameter file for the Set Control Value option mapping parameter or variable. 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
Explanation: User Response:
Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, with an invalid effective date.
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. 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.
You defined a partition key for a port in the Application Source Qualifier that you deleted. 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
Explanation: User Response:
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.
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. Disconnect the link between the TO_EFFDT field in the source and the Application Source Qualifier.
PWX Messages
PWX-34000
Explanation:
PWX Messages
271
User Response:
PWX-34001
Explanation: User Response:
PWX-34002
Explanation: User Response:
PowerExchange Task call to set Sync URI failed - caught exception. Message ''message''.
An internal error occurred. Contact Informatica Global Customer Support.
PWX-34003
Explanation: User Response:
PWX-34004
Explanation: User Response:
PWX-34005
Explanation: User Response:
PWX-34006
Explanation: User Response:
PWX-34007
Explanation: User Response:
PWX-34008
Explanation: User Response:
PWX-34009
Explanation: User Response:
PWX-34010
Explanation: User Response:
272
PWX-34011
Explanation: User Response:
PWX-34012
Explanation: User Response:
PWX-34013
Explanation: User Response:
PWX-34504
Explanation: User Response:
PWXPC Messages
For information about PowerExchange Client for PowerCenter messages, see the PowerExchange Message Reference.
PWXPC Messages
273
CHAPTER 17
REGEX Messages
REGEX_34005
Explanation: User Response:
REGEX_34006
Explanation: User Response:
REGEX_34007
Explanation: User Response:
REGEX_34008
Explanation: User Response:
REGEX_34009
Explanation: User Response:
274
REGEX_34010
Explanation:
The Integration Service failed to validate the subject because of a perl compatible regular expression syntax error.
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. Verify that the system contains enough memory. Verify the syntax of the expression. Use perl compatible regular expression syntax.
User Response:
REGEX_34011
Explanation:
The Integration Service failed to extract the subpattern because of a perl compatible regular expression syntax error.
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. Verify that the system contains enough memory. Verify the syntax of the expression. Use perl compatible regular expression syntax.
User Response:
REGEX_34014
Explanation: User Response:
REP Messages
REP_12001
Explanation: User Response:
REP_12005
Explanation: User Response:
An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.
The Integration Service cannot locate a necessary SQL script file. 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
Explanation: User Response:
REP Messages
275
REP_12021
Failed to connect to local repository <local repository name> in domain <PowerCenter domain of local repository> from global repository <global repository name> in <PowerCenter domain of global repository>.
The Service Manager was unable to connect to a local repository from the global repository. Verify that the local repository is registered with the global repository. Also, verify that the Repository Services for both repositories are running. In addition verify that the connectivity information for the local repository is up to date.
REP_12022
Failed to connect to global repository <global repository name> in domain <PowerCenter domain of global repository> from local repository <local repository name> in <PowerCenter domain of local repository>.
The Service Manager was unable to connect to the global repository from a local repository. Verify that the local repository is registered with the global repository. Also, verify that the Repository Services for both repositories are running. In addition, verify that the connectivity information for the global repository is up to date.
REP_12033
Explanation: User Response:
REP_12119
Explanation: User Response: Explanation: User Response:
REP_12122
Explanation: User Response:
REP_12123
Explanation:
REP_12124
Explanation: User Response:
REP_12164
Explanation:
276
User Response:
Read the error description and make any necessary changes to the domain connectivity. For more information, look up the cause and action for the error code.
REP_12225
Explanation: User Response:
REP_12233
Explanation: User Response:
REP_12325
Explanation: User Response:
REP_12326
Explanation: User Response:
REP_12327
Explanation: User Response:
REP_12328
Explanation: User Response: Explanation: User Response:
The repository at this location does not have the same name.
Either the database connection or the repository name entered is incorrect. The status bar displays the correct repository name. Correct the inaccurate information. You tried to connect to a repository on the network, but there was a network failure during the connect process. 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
Explanation: User Response:
REP_12332
Explanation:
REP Messages
277
Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the system. This is a database error. Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.
REP_12333
Explanation: User Response:
REP_12334
Explanation: User Response:
REP_12335
Explanation: User Response:
REP_12336
Explanation: User Response:
This repository is already registered with the GDR <global repository name>.
You tried to register a repository to a global repository that is registered with a different global repository. 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
Explanation: User Response:
REP_12338
Explanation: User Response:
REP_12339
Explanation: User Response:
278
REP_12340
Explanation:
REP_12341
Explanation: User Response: Explanation: User Response:
REP_12342
Explanation: User Response:
The selected repository is not registered with the current Global Repository.
You tried to unregister a repository that is not registered with the current global repository. You can only unregister repositories registered with a global repository.
REP_12346
Explanation: User Response:
REP_12347
Explanation: User Response:
REP_12352
Explanation: User Response:
The current user does not have the privilege to perform this operation.
You tried to perform an operation without the appropriate privileges. Have the database administrator review the privileges.
REP_12355
Explanation: User Response:
The object <object name> has been modified since the time it was read.
You tried to edit a repository object that has been modified and saved by another user since you opened the object. Close the object and open it again to view the edited object.
REP_12357
Explanation:
The object <object name> is already locked by <user name>. Do you want to reobtain the lock?
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.
REP Messages
279
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
Explanation:
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.
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. 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.
User Response:
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.
You upgraded the Teradata repository and tried to start it without backing it up and restoring it. 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
Explanation: User Response:
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.
The repository needs to be upgraded to the current version expected by the product. Use the Administrator tool to upgrade the repository.
REP_12371
Explanation: User Response:
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.
The repository has been upgraded to a newer version of the product. 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.
The repository has been upgraded to a newer version of the product. 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.
The repository needs to be upgraded to the current version expected by the product. Use the Administrator tool to upgrade the repository.
280
REP_12381
Explanation: User Response:
Unable to perform the operation since an expected object was not found. Please check the repository.
Internal error. The repository may contain inconsistencies. Contact Informatica Global Customer Support.
REP_12382
Explanation: User Response:
Error while updating the object information in the repository. Either no row or more than one row was updated.
Internal error. The repository may contain inconsistencies. Contact Informatica Global Customer Support.
REP_12386
Explanation: User Response:
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.
A repository is not supported on the database type specified in the configuration file. 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.
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. 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.
Explanation:
User Response:
REP_12389
Explanation: User Response:
REP_12390
Explanation: User Response:
Mapping <mapping name> contains a dependency that points to a non existent port. The mapping is assumed to be invalid.
You started a session that uses a mapplet, and information about the mapping is inconsistent in the repository. 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
Explanation: User Response:
REP Messages
281
REP_12403
Explanation: User Response:
REP_12404
Explanation: User Response: Explanation: User Response:
Failed to allocate new IDs for internal sequence generator: <sequence name>.
A repository database error occurred causing the internal ID generation to fail. If a repository database error occurred, try again after correcting the database problem. The repository has inconsistent data. Contact Informatica Global Customer Support.
REP_12405
Explanation:
REP_12415
Explanation: User Response:
REP_12416
Explanation:
REP_12422
Explanation: User Response:
REP_12449
Explanation: User Response:
Internal error.
Internal error. Contact Informatica Global Customer Support.
REP_12450
Explanation: User Response:
282
REP_12452
Explanation: User Response:
REP_12454
Explanation: User Response:
REP_12456
Explanation:
REP_12457
Explanation: User Response:
REP_12466
Explanation: User Response:
REP_12467
Explanation: User Response:
REP_12468
Explanation:
REP_12469
Explanation: User Response:
REP_12470
Explanation:
REP_12471
Explanation: User Response:
REP Messages
283
REP_12477
Explanation: User Response:
This repository contains folders which are currently in use. A repository cannot be deleted while it is in use.
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. Ask all users to close all client tools. Use the Repository Manager to view locks. If necessary, remove old locks. Then perform the operation again. Warning: Removing valid locks can cause repository inconsistencies.
REP_12488
Explanation:
REP_12492
Explanation: User Response:
This repository contains folders which are currently in use. A repository cannot be upgraded while folders are in use.
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. Ask all users to close all client tools. Use the Repository Manager to view locks. If necessary, remove old locks. Then perform the operation again. Warning: Removing valid locks can cause repository inconsistencies.
REP_12494
Explanation: User Response:
The Repository is newer than the version supported by this software release. Unable to do an upgrade.
The product version is older than the repository version. Release all old locks in the repository. Upgrade the PowerCenter Client to the latest version, then upgrade the repository.
REP_12496
Explanation: User Response:
REP_12505
Explanation: User Response:
REP_12581
Explanation: User Response:
An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.
The script file cannot be found in the PowerCenter Client installation directory or the file is corrupt. Install the PowerCenter Client again to get the correct scripts. If the problem persists, contact Informatica Global Customer Support.
284
REP_12589
Explanation:
User Response:
REP_12590
Explanation: User Response:
REP_12591
Explanation: User Response:
Error updating <repository name> in GDR (Repository may be left in inconsistent state).
A repository database error occurred when you tried to register or unregister a repository. 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
Explanation: User Response:
REP_12654
Explanation: User Response:
REP_12678
Explanation:
User Response:
REP_12708
Explanation: User Response:
REP_12709
Explanation: User Response:
REP Messages
285
REP_12734
Explanation:
The source database <source database connection> and Integration Service <Integration Service name> do not have compatible code pages (one way compatibility is required).
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. 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.
User Response:
REP_12735
Explanation:
The source file <file name> and Integration Service <Integration Service name> do not have compatible code pages. (One way compatibility is required.)
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. 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.
User Response:
REP_12736
Explanation:
The database <database name> and Integration Service <Integration Service name> do not have compatible code pages.
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. 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.
User Response:
REP_12773
Explanation: User Response:
The Global Repository code page (<code page name>) is not compatible with the selected code page (<code page name>).
While upgrading a local repository, the local repository code page must be a superset of the global repository code page. Choose an appropriate code page.
286
REP_12782
Explanation:
The repository <repository name>s code page <code page name> and <PowerCenter Client>s code page <code page name> are incompatible.
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. 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.
User Response:
REP_12934
Explanation: User Response: Explanation: User Response:
REP_12950
Explanation: User Response:
Lookup Transformation <transformation name> has INVALID lookup condition: Lookup Table Column <column name> and Transformation Port <port name> are the same.
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. 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
Explanation: User Response:
The lookup condition is not valid: Lookup Table Column <column name> and Transformation Port <port name> are the same. Transformation is not valid.
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. 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
Explanation: User Response:
Joiner Transformation <transformation name> has INVALID joiner condition: Master <port name> and Detail <port name> are the same.
You entered an incorrect expression value for the join condition in the XML file. The master port is the same as the detail port. 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_12953
Explanation: User Response:
The joiner condition is not valid: Master <port name> and Detail <port name> are the same. Transformation is not valid.
You entered an incorrect expression value for the join condition. The master port is the same as the detail port. 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 Messages
287
REP_12954
Explanation: User Response:
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.
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. 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
Explanation: User Response:
Warning: The Call Text attribute of Stored Procedure transformation has non-empty value when attribute Store Procedure Type is set to Normal.
The call text attribute contains a value when you defined the stored procedure type attribute as Normal in the XML file. 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
Explanation: User Response:
There is no existing MQ Connection to choose for <connection string> in the target repository.
This is an informational message. You tried to copy a WebSphere MQ session to a target repository with no defined queue connections. Create at least one queue connection in the target repository.
REP_12991
Explanation: User Response:
Failed to connect to <repository name> Repository Agent on host <host name> (port number: <port number>). System error message: <error message>.
A repository client could not connect to a Repository Agent process. The Repository Agent host name or port number may be incorrect. 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
Explanation: User Response:
REP_12995
Explanation: User Response:
REP_12996
Explanation: User Response:
REP_12999
Explanation: User Response:
288
REP_22674
Explanation: User Response:
Custom Transformation <transformation name> has non-ASCII character(s) in its class name.
The Custom transformation class name contains non 7-bit ASCII characters. Edit the transformation properties and enter 7-bit ASCII characters for the class name.
REP_32000
Explanation: User Response:
Error: Could not find DSQ instance <Source Qualifier name> for <source>.
The Source Qualifier transformation associated with the source is missing in the XML file. 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
Explanation: User Response:
Error: Source Reference: <source> DBD: <source> for DSQ <Source Qualifier name> not found.
The source associated with a specified Source Qualifier transformation is missing in the XML file. 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
Explanation: User Response:
Error: There are more than one groups with the order: <number> in <group>.
The XML file specifies more than one group with the same order for that particular source, target, or transformation. 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
Explanation: User Response:
REP_32004
Explanation: User Response:
REP_32007
Explanation: User Response:
Folder referenced by the shortcut object does not exist, object will be created in the current folder.
The shortcut to an object does not contain folder information. You might have renamed or deleted the folder. 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
Explanation: User Response:
Error: Object referenced by shortcut: <shortcut>. Referring to <object> in Repository: <repository name>. Folder: <folder name> not found.
You deleted or renamed a folder that contains a shortcut in the specified repository. Restore the folder or re-create the shortcut to the object in the folder.
REP Messages
289
REP_32011
Explanation: User Response:
REP_32013
Explanation: User Response:
REP_32014
Explanation: User Response:
REP_32015
Explanation: User Response:
Code page in file: <file name> not compatible with repository code page: <code page>.
The repository code page specified in the XML file is not compatible with the target repository code page. Cannot import the XML file. Edit the XML file and make sure the code pages are compatible.
REP_32016
Explanation: User Response:
REP_32018
Explanation: User Response:
REP_32019
Explanation: User Response:
REP_32020
Explanation: User Response:
Warning: Could not link fields <field name>:<field name>:<field name>: Instance <instance> to Field: <field name> Instance <instance>.
An invalid connector node exists for a mapping or mapplet in the XML file. Fix the CONNECTOR node under the mapping or mapplet. Or, export the object again and then import it.
REP_32021
Explanation: User Response:
REP_32022
Explanation: User Response:
290
REP_32023
Explanation: User Response:
Error: Cannot determine ODBC Data type for field <field name>.
You defined an invalid ODBC type for a table field in the XML file. Edit the XML file for the ODBC data type for that particular field.
REP_32025
Explanation: User Response:
REP_32026
Explanation: User Response:
REP_32027
Explanation: User Response:
Error: Could not Resolve Foreign key dependency For Field: <field> in Source: <source>.
The DBD or source for a specified foreign key field name is missing in the XML file. Edit the XML file. Or, export the object again and then import it.
REP_32028
Explanation: User Response:
REP_32029
Explanation: User Response:
REP_32030
Explanation: User Response:
REP_32031
Explanation: User Response:
REP_32032
Explanation: User Response:
REP_32033
Explanation: User Response:
REP Messages
291
REP_32034
Explanation: User Response:
REP_32035
Explanation: User Response:
REP_32036
Explanation: User Response:
REP_32037
Explanation: User Response:
REP_32038
Explanation: User Response:
REP_32039
Explanation: User Response:
Error: Missing ATTRIBUTE <XML attribute name> for field: <SOURCEFIELD name or TRANSFORMFIELD name>.
The specified attribute is missing or empty in the specified element in the XML file. 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
Explanation:
Error: Could not find associated source field: <SOURCEFIELD name> for <Normalizer transformation>.
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. 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.
User Response:
REP_32041
Explanation: User Response:
292
REP_32042
Explanation: User Response:
Error: Invalid reference field <REF_FIELD name> for Transformation field: <TRANSFORMFIELD name>.
In the XML file, a TRANSFORMFIELD element contains a value for the REF_FIELD attribute that does not match a SOURCEFIELD element. 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
Explanation: User Response:
REP_32044
Explanation:
User Response:
REP_32045
Explanation: User Response:
Error: Invalid reference field: <REF_FIELD> for Lookup Field: <TRANSFORMFIELD name> Transformation: <transformation name>.
The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file. Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, export the object again and then import it. The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name. Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it.
Explanation:
User Response:
REP_32046
Explanation: User Response:
Error: Invalid reference field: <REF_FIELD> for Field: <TRANSFORMFIELD name> Transformation: <TRANSFORMATION name>.
The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file. Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, export the object again and then import it. The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name.
Explanation:
REP Messages
293
User Response:
Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it.
REP_32047
Explanation: User Response:
Error: Invalid Mapplet Group <MAPPLETGROUP> for Field: <MAPPLETGROUP value> Transformation: <transformation name>.
In the XML file, the MAPPLETGROUP attribute value does not match the name of the GROUP element for the mapplet. 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
Explanation: User Response:
Error: Could not find Transformation definition for: <transformation or source or target name>.
The TRANSFORMATION_NAME attribute in the INSTANCE element does not match a TRANSFORMATION element name in the XML file. 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
Explanation: User Response:
REP_32057
Explanation: User Response:
REP_32058
Explanation: User Response:
REP_32060
Explanation: User Response:
Error: Could not get datatype description for field: <field name>.
Internal error. Contact Informatica Global Customer Support.
REP_32063
Explanation: User Response:
Error: An Unknown target field attribute: <attribute ID> has been detected for Field: <field name>.
Internal error. Contact Informatica Global Customer Support.
REP_32066
Explanation: User Response:
Error: Could not get group for source field: <source field>.
Internal error. Contact Informatica Global Customer Support.
294
REP_32072
Explanation: User Response:
REP_32074
Explanation: User Response:
REP_32079
Explanation: User Response:
REP_32081
Explanation: User Response:
REP_32087
Explanation: User Response:
REP_32088
Explanation: User Response:
REP_32089
Explanation: User Response:
REP_32090
Explanation: User Response:
REP_32091
Explanation: User Response:
REP Messages
295
REP_32092
Explanation: User Response:
Error: Unable to fetch database connection: <database connection> associated with the data Source Qualifier transformation: <transformation name>.
The database connection specified for the session in the XML file does not exist in the target repository. Create a database connection in the target repository with the name defined in the XML file, or select an existing database connection from the Workflow Manager.
REP_32093
Explanation: User Response:
REP_32095
Explanation: User Response:
REP_32096
Explanation: User Response:
REP_32097
Explanation: User Response:
Warning: FTP connection <FTP connection> not found. Session will be imported without reference to FTP connection.
Unable to retrieve the connection object defined in the XML file for that session. Create a connection object or select an existing one using the Workflow Manager.
REP_32098
Explanation: User Response:
Warning: Loader connection <external loader connection> not found. Session will be imported without reference to Loader connection.
Unable to retrieve the connection object defined in the XML file for that session. Create a connection object or select an existing one using the Workflow Manager.
REP_32101
Explanation: User Response:
REP_32103
Explanation: User Response:
REP_32105
Explanation: User Response:
296
REP_32111
Explanation: User Response:
Error: Invalid Database Type: <DATABASETYPE value> for source: <SOURCE name>.
You entered an invalid database type in the DATABASETYPE attribute in the SOURCE element for the specified source. Edit the XML file and correct the DATABASETYPE attribute in the SOURCE element. Or, export the object again and then import it.
REP_32112
Explanation: User Response:
REP_32113
Explanation: User Response:
REP_32115
Explanation: User Response:
Error: <object> <object name> cannot be imported as it is potentially unsafe. Importing any associated mapping/mapplet might result in an error.
You created or modified an object in the XML file that cannot be created or modified. Export the object again and then import it.
REP_32116
Explanation: User Response:
Error: The mapping: <mapping name> is potentially unsafe and cannot be imported.
In the XML file, you modified an object that contains a CRCVALUE code. The object is a part of the specified mapping. Export the object again and then import it.
REP_32117
Explanation: User Response:
Error: <transformation type> <transformation name> is potentially unsafe and will not be available for import.
In the XML file, you modified either a source, target, or transformation that contains a CRCVALUE code. Export the object again and then import it.
REP_32118
Explanation: User Response:
REP_32121
Explanation: User Response:
Warning: Removing instance <instance name>. Could not find source instance for this Source Qualifier transformation instance.
You defined a Source Qualifier transformation in the XML file that is not associated with a source. Edit the XML file. Or, export the object again and then import it.
REP_32122
Explanation:
REP Messages
297
User Response:
Edit the XML file. Or, export the object again and then import it.
REP_32123
Explanation: User Response:
Error: Rank transformation <transformation name> has an invalid first field name. It has to be RANKINDEX.
You deleted or renamed the first field for the Rank transformation in the XML file. Edit the XML file and make sure the first field name for the Rank transformation is RANKINDEX. Or, export the object again and then import it.
REP_32124
Explanation: User Response:
REP_32131
Explanation: User Response:
Error: Rank transformation <transformation name> has no RANK PORT. This transformation is invalid.
You did not define a Rank port type for the Rank transformation in the XML file. 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
Explanation: User Response:
Error: Transformation <transformation name> has duplicate group <group> due to the same group order.
You defined duplicated groups in the group order in the XML file. Edit the XML file and make sure the group order has different groups. Or, export the object again and then import it.
REP_32135
Explanation: User Response:
Error: Invalid precision: <number> specified for field: <field name>. The maximum precision is 65535.
You defined the field precision in the XML file greater than the maximum of 65,535. Edit the XML file and make sure the precision is less than or equal to the maximum precision, which is 65,535.
REP_32136
Explanation:
Error: Invalid scale: <number> specified for field: <field name>. The scale cannot be greater than the precision or the maximum scale which is 65535.
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. Edit the XML file and make sure the scale for the field is less than or equal to the precision for the field.
User Response:
REP_32137
Explanation: User Response:
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.
In the XML file, you defined the dynamic lookup cache attribute to YES, but you did not define the first lookup port as NewLookupRow. 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.
298
REP_32138
Explanation: User Response:
Field <field name> for lookup transformation <transformation name> cannot be a Dynamic Lookup field when dynamic lookup cache is disabled. Transformation is not valid.
In the XML file, you defined a lookup port as NewLookupRow, but you defined the dynamic lookup cache as NO. 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
Explanation: User Response:
In Lookup transformation <transformation name>, the content(s) of the generated Dynamic Lookup field <field name> has been changed. Transformation is not valid.
You modified the definition of the NewLookupRow port in the XML file. Do not change the NewLookupRow port in the XML file. Export the object again and then import it.
REP_32140
Explanation: User Response:
In Rank transformation <transformation name>, the content(s) of the RANKINDEX field <field name> has been changed. Transformation is not valid.
You modified the contents of the RANKINDEX field in the Rank transformation in the XML file. Do not modify the RANKINDEX field in the XML file. Export the object again and then import it.
REP_32141
Explanation: User Response:
In Sequence Generator transformation <transformation name>, the content(s) of field <field name> has been changed. Transformation is not valid.
You modified the definitions of the NEXTVAL and CURRVAL fields in the Sequence Generator transformation in the XML file. Do not modify these fields in the XML file. Export the object again and then import it.
REP_32144
Explanation: User Response:
Error: Missing or invalid attribute <attribute name> for <element name>: <attribute value>.
In the XML file, you entered an invalid value or no value for the specified attribute in the specified element. Edit the XML file and define a valid value for the specified attribute. Or, export the object again and then import it.
REP_32148
Explanation: User Response:
REP_32149
Explanation: User Response:
Error: Invalid datatype for aggregate COUNT for mapping variable <MAPPINGVARIABLE name>.
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. 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 Messages
299
REP_32150
Explanation: User Response:
REP_32151
Explanation: User Response:
REP_32167
Explanation: User Response:
REP_32171
Explanation: User Response:
The mapping originally assigned to this session has been changed. Cannot import the session.
You copied a mapping to a repository, but the mapping was modified, deleted or renamed. Copy or import the original mapping to the target repository again.
REP_32173
Explanation: User Response:
Error: Expected unsigned value for attribute: <attribute value>, found value: <value>.
You provided a negative or invalid value for an unsigned number in the XML file. Correct the value in the XML file. Or, export the object again and then import it.
REP_32174
Explanation: User Response:
Error: Invalid value: <value>, expecting unsigned value for attribute: <attribute>, for <element>: <element name>.
You provided a negative or invalid value for an unsigned number in the XML file. Edit the XML file and define a valid value for the attribute OCCURS. Or, export the object again and then import it.
REP_32175
Explanation: User Response:
Error: Invalid target database type: <target database name> for target: <target name>.
You defined an invalid database type in the XML file, or the database type is not valid for a target. 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_32176
Explanation: User Response:
Two or more fields in the xml data Source Qualifier transformation: <Source Qualifier name> refer to the same field: <field name> in the source.
In the XML file, you defined two transformation fields for the XML Source Qualifier transformation with the same value for the REF_SOURCEFIELD attribute. Edit the XML file and provide the correct value. Or, export the object again and then import it.
300
REP_32177
Explanation: User Response:
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.
In the XML file, you defined a plugin database type for the target, but you did not register the plugin in the PowerCenter Client. Register the plugin the PowerCenter Client before importing the file. Or, edit the XML file and specify an existing database type.
REP_32178
Explanation: User Response:
Error: Invalid Database Type: <database type> for target: <target name>, or the Database Type is not installed in this repository.
In the XML file, you defined a plugin database type for the target, but you did not install the plugin in the repository. Install the plugin in the repository before importing the file. Or, edit the XML file and specify an existing database type.
REP_32180
Explanation: User Response:
Error: Invalid Task type <task type> for task <task name>.
In the XML file, you specified an invalid TYPE attribute for the TASK element. Edit the XML file, and specify a valid TYPE for the TASK. Or, export the object again and then import it.
REP_32181
Explanation: User Response:
Error: Invalid Extension type: <session extension type> for element <SESSIONEXTENSION element>.
In the XML file, you specified an invalid TYPE attribute for the SESSIONEXTENSION element. Edit the XML file, and specify a valid TYPE for the SESSIONEXTENSION. Or, export the object again and then import it.
REP_32185
Explanation: User Response:
Error: The mapping <mapping name> associated with the session <session name> is invalid.
In the XML file, you specified a mapping that is invalid. In the Designer, validate the mapping before importing the session. Or, choose a different valid mapping for the session.
REP_32186
Explanation: User Response:
REP_32188
Explanation: User Response:
Error: The mapping <mapping name> for session <session name> is not found in the target repository.
The XML file references a mapping that does not exist in the repository. Create a valid mapping in the Designer before importing, or choose a different mapping for the session.
REP_32190
Explanation:
Warning: session transformation instance <session transformation instance name> of type <transformation type> is not found for element <SESSIONEXTENSION>.
In the XML file, the type of the SESSIONEXTENSION element does not match a SESSTRANSFORMATIONINST element.
REP Messages
301
User Response:
Edit the XML file, and verify the type of the SESSIONEXTENSION element matches a SESSTRANSFORMATIONINST element. Or, export the object again and then import it.
REP_32191
Explanation: User Response:
Warning: missing or empty attribute <attribute name> for element <element name>.
The XML file contains an empty or missing attribute. Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it.
REP_32192
Explanation: User Response:
Error: Invalid Component Type <session component type> for element <SESSIONCOMPONENT name>.
In the XML file, you specified an invalid TYPE attribute for the SESSIONCOMPONENT element. 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
Explanation: User Response:
Error: missing or empty attribute <attribute name> for element <element name>.
The XML file contains an empty attribute, or the attribute is missing. Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it.
REP_32194
Explanation: User Response:
Error: Invalid partition type <PARTITIONTYPE name> for session transformation <SESSTRANSFORMATIONINST name>.
In the XML file, you specified an invalid PARTITIONTYPE attribute for the SESSTRANSFORMATIONINST element. Edit the XML file, and specify a valid PARTITIONTYPE. Or, export the object again and then import it.
REP_32195
Explanation:
Error: extension subType <SESSIONEXTENSION subtype> for extension type <SESSIONEXTENSION type> is invalid for element <SESSIONEXTENSION name>.
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. Edit the XML file, and specify a valid SUBTYPE. Or, export the object again and then import it.
User Response:
REP_32196
Explanation: User Response:
Error: connection reference <connection reference> with connection number <number> is not found for element <SESSIONEXTENSION name> due to the following error:
In the SESSIONEXTENSION element, the referenced CONNECTIONREFERENCE element does not exist. Edit the XML file, and specify a valid CONNECTIONREFERENCE. Or, export the object again and then import it.
REP_32198
Explanation:
Error: Invalid connection type <connection type> for connection reference <connection reference>.
In the XML file, you specified an invalid CONNECTIONTYPE attribute for the CONNECTIONREFERENCE element.
302
User Response:
Edit the XML file, and specify a valid CONNECTIONTYPE attribute. Or, export the object again and then import it.
REP_32199
Explanation: User Response:
Error: Invalid partition name <partition name> for element <element name>.
In the XML file, you specified an invalid PARTITIONNAME attribute for the specified element. Edit the XML file, and specify a valid PARTITIONNAME attribute. Or, export the object again and then import it.
REP_32202
Explanation: User Response:
Error: Invalid DSQ instance name < Source Qualifier transformation name> for session transformation instance <session transformation instance name>.
In the XML file, you specified a DSQINSTNAME attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element. 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
Explanation: User Response:
Error: the number of partition <PARTITION name> is out of range [1-32] for session transformation <SESSTRANSFORMATIONINST name> in session <session name>.
The number of PARTITIONs under SESSTRANSFORMATIONINST is invalid. Remove, as appropriate, the PARTITIONs from under the SESSTRANSFORMATIONINST so that the number of PARTITIONs is less than or equal to 32.
REP_32204
Explanation: User Response:
REP_32205
Explanation:
Error: Invalid DSQ <Source Qualifier name> of type <DSQINSTTYPE> for the extension in session transformation instance <SESSTRANSFORMATIONINST name>.
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. 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.
User Response:
REP_32207
Explanation: User Response:
REP_32208
Error: The extension of type <SESSIONEXTENSION type> and subtype <SESSIONEXTENSION subtype> does not exist for session transformation instance <SESSTRANSFORMATIONINST name>.
In the XML file, the TYPE and SUBTYPE attributes for the SESSIONEXTENSION element are not supported for the SESSTRANSFORMATIONINST element.
Explanation:
REP Messages
303
User Response:
Edit the XML file, and specify TYPE and SUBTYPE attributes in the SESSIONEXTENSION element that the SESSTRANSFORMATIONINST element supports.
REP_32209
Explanation: User Response:
Error: Invalid suspension email <SUSPENSION_EMAIL name> for workflow <workflow name>.
In the XML file, you specified a SUSPENSION_EMAIL attribute for the WORKFLOW element that references a non-existent Email task. 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
Explanation: User Response:
Error: Name conflict or invalid object name <object name> for element <element name>.
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. Edit the XML file, and rename the element using valid characters only. Or, export the object again and then import it.
REP_32211
Explanation: User Response:
Warning: missing both start and end range in key <KEYRANGE> for element <element name>.
In the XML file, both the STARTRANGE and ENDRANGE attributes are empty for the specified KEYRANGE element. Edit the XML file, and enter a value for the STARTRANGE, ENDRANGE, or both. Or, edit the start range and end range values in the session after you import it.
REP_32212
Explanation:
Warning: the session transformation <SESSTRANSFORMATIONINST name> does not exist in the mapping <mapping name> in target folder.
In the XML file, you specified SINSTANCENAME and TRANSFORMATIONTYPE attributes in a SESSTRANSFORMATIONINST element that does not match a transformation in the mapping associated with the session. This might have happened if you deleted the transformation in the mapping after you exported the session. Edit the XML file, and verify the SESSTRANSFORMATIONINST element refers to an existing transformation in the referenced mapping. Or, edit the session after you import it.
User Response:
REP_32213
Explanation: User Response:
Error: the session transformation <SESSTRANSFORMATIONINST name> is not partitionable and is connected to a stage with more than one partitions.
In the XML file, you included a non-partitionable SESSTRANSFORMATIONINST element in a pipeline with more than one partition. Export the object again and then import it.
REP_32214
Explanation: User Response:
Warning: invalid key name <KEYRANGE or HASHKEY name> for element <element name>.
In the XML file, you specified a NAME attribute in a KEYRANGE or HASHKEY element that references a non-existent transformation port. Edit the XML file, and enter a valid NAME. Or, export the object again and then import it.
REP_32215
Explanation: User Response:
304
REP_32216
Explanation:
Error: connection reference <CONNECTIONREFERENCE name> type <TYPE> and subtype <SUBTYPE> is not valid for the extension.
In the XML file, you specified CONNECTIONTYPE and CONNECTIONSUBTYPE attributes in the specified CONNECTIONREFERENCE element that are not valid for the TYPE and SUBTYPE attributes of the SESSIONEXTENSION element. Edit the XML file, and verify the type and subtypes of the CONNECTIONREFERENCE and SESSIONEXTENSION elements are compatible. Or, export the object again and then import it.
User Response:
REP_32217
Explanation: User Response:
Error: a partition name <PARTITIONNAME> is given for a non-partitionable connection reference for session transformation instance <session transformation instance name>.
In the XML file, you included a PARTITIONNAME attribute in a CONNECTIONREFERENCE element that is not partitionable. Edit the XML file, and remove the PARTITIONNAME attribute from the CONNECTIONREFERENCE element. Or, export the object again and then import it.
REP_32218
Explanation: User Response:
Error: Invalid task type <task type> for element <element name>.
In the XML file, you specified an invalid TYPE attribute in the TASK element. Edit the XML file, and enter a valid TYPE for the TASK. Or, export the object again and then import it.
REP_32219
Explanation: User Response:
Warning: cannot find the referenced config object <REFOBJECTNAME>, default session config is used.
In the XML file, you specified a REFOBJECTNAME attribute in a CONFIGREFERNCE element that references a non-existent CONFIG element. This is a warning. The Workflow Manager uses a default session configuration.
REP_32220
Explanation: User Response:
REP_32222
Explanation: User Response:
REP_32223
Explanation:
Error: two Schedulers of conflicting types specified for workflow <WORKFLOW name>: reusable <SCHEDULER under FOLDER> and nonreusable <SCHEDULER under WORKFLOW>.
In the XML file, you specified SCHEDULERNAME and REUSABLE_SCHEDULER attributes in a WORKFLOW element that does not match a SCHEDULER element under the WORKFLOW element or a SCHEDULER element under the FOLDER element.
REP Messages
305
User Response:
Edit the XML file, and verify the SCHEDULERNAME and REUSABLE_SCHEDULER attributes refer to only one SCHEDULER. Include reusable schedulers under the FOLDER element, and include non-reusable schedulers under the WORFKLOW element. Or, export the object again and then import it.
REP_32224
Explanation: User Response:
REP_32225
Explanation: User Response:
REP_32292
Explanation: User Response:
REP_32293
Explanation: User Response:
REP_32294
Explanation: User Response:
Error: Group <group> of the transformation <transformation name> is both an input group and an output group.
You imported a Custom transformation with a group defined as both an output and input group. 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
Explanation: User Response:
Session <session name> has a log file name which is longer than 600 characters. Session is not valid.
The session log file name is too long. On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension.
REP_32410
Explanation: User Response:
Session has a log file name which is longer than 600 characters. Session is not valid.
The session log file name is too long. On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension.
306
REP_32413
Explanation: User Response:
Session <session name> has a log directory name which is longer than 600 characters. Session is not valid.
The session log file directory name is too long. On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters.
REP_32414
Explanation: User Response:
Session has a log directory name which is longer than 600 characters. Session is not valid.
The session log file directory name is too long. On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters.
REP_32426
Explanation: User Response:
Session config <session configuration object name>. The number of runs to save session log on must be in the range 0 to 2147483647.
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. On the session properties Config Object tab, Log Options settings, specify a number of runs between 0 and 2,147,483,647.
REP_32427
Explanation: User Response:
The number of runs to save session log on must be in the range 0 to 2147483647.
You are saving session logs by number of runs. The number of runs you specified is out of range. Specify a number of runs between 0 and 2,147,483,647 for the session log options settings.
REP_32467
Explanation: User Response:
REP_32469
Explanation: User Response:
REP_32473
Explanation: User Response:
REP_32471
Explanation: User Response:
REP Messages
307
REP_32472
Explanation: User Response:
'Save workflow log for these runs' must be in the range of 0 to 2147483647.
You are saving workflow logs by number of runs. The number of runs you specified is out of range. On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647.
REP_32475
Explanation: User Response:
REP_32477
Explanation: User Response:
REP_32479
Explanation: User Response:
REP_32480
Explanation: User Response:
REP_32481
Explanation: User Response:
REP_32482
Explanation: User Response:
Workflow task <workflow name>: Save workflow log for these runs must be in the range of 0 to 2147483647.
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. 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
Explanation: User Response:
Save workflow log for these runs must be in the range of 0 to 2147483647.
You are saving workflow logs by number of runs. The number of runs you specified is out of range. On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647.
308
REP_32490
Explanation: User Response:
Workflow task <workflow name> log directory name must have a delimiter.
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. On the workflow Properties tab, include the appropriate delimiter after the workflow log file directory name.
REP_32491
Explanation: User Response:
REP_32494
Explanation: User Response:
REP_32495
Explanation: User Response:
REP_32496
Explanation: User Response:
REP_32497
Explanation: User Response:
REP_32498
Explanation: User Response:
REP_32499
Explanation: User Response:
REP_32523
Explanation: User Response:
REP Messages
309
REP_32524
Explanation: User Response:
REP_32532
Explanation:
User Response:
REP_32533
Explanation:
REP_32534
Explanation:
Invalid hash key <key name> for <transformation name> in session <session name>.
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. Edit the session properties and specify a new hash key at the transformation.
User Response:
REP_32535
Explanation:
User Response:
REP_32536
Explanation:
Hash key <key name> for instance <transformation name> in session <session name> has invalid port type.
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. Edit the session properties and select an input or input/output port as the key.
User Response:
REP_32537
Explanation:
Hash key <key name> for instance <transformation name> has invalid port type.
Same as REP_32536.
REP_32542
Explanation:
User Response:
310
REP_32543
Explanation:
REP_32544
Explanation: User Response:
REP_32546
Explanation: User Response:
REP_32548
Explanation: User Response:
Timer task <Timer task name> uses a workflow variable which is not Date/Time datatype.
The named Timer task uses a workflow variable to calculate the wait, but the variable datatype is not Date/Time. 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
Explanation:
Key not specified for key range partition for <partition name:transformation name> in session <session name>.
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. Edit the session properties and either specify a partition key at the transformation or change the partition type.
User Response:
REP_32551
Explanation:
Key not specified for key range partition for <partition name:transformation>.
Same as REP_32550.
REP_32558
Explanation: User Response:
Workflow task <workflow name>: Save workflow log for these runs has an invalid Integration Service variable associated with it.
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. 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
Explanation: User Response:
Save workflow log for these runs has an invalid Integration Service variable associated with it.
You are saving workflow logs by number of runs. The number of runs you specified is based on an invalid service variable. 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 Messages
311
REP_32701
Explanation: User Response:
Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>, session <session name>).
You ran a session with a hash user keys partition point at a multi-group transformation, but you did not specify a key. Edit the session properties and specify a key for the group. Or, change the partition type of the group.
REP_32702
Explanation:
Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>).
Same as REP_32701.
REP_32705
Explanation: User Response:
Key not specified for Key Range partition (group <group>, instance <transformation instance name>, session <session instance name>).
You selected key range partitioning, but you did not specify a key for the group. Edit the session properties to specify a key for the group or change the partition type for the group.
REP_32706
Explanation:
Key not specified for Key Range partition (group <group> instance <transformation instance name>).
Same as REP_32705.
REP_32827
Explanation:
User Response:
REP_32828
Explanation: User Response:
A variable with this name, <variable name>, already exists in the mapping.
You altered the XML file or created an invalid mapping variable name. The imported mapping variable name is not unique within the imported mapping. Make sure mapping variable names are unique within any mapping.
REP_32898
Explanation:
User Response:
REP_32899
Explanation:
User Response:
REP_51037
Explanation:
312
User Response:
Check preceding messages to see the cause of the error. Check the database log for related error messages. Verify the database user name, password, and connect string are correct.
REP_51042
Explanation: User Response:
Repository Agent connection failed. System Error (errno = <error number>) <error message>: Cannot read message header. Read <number> bytes.
The connection to the Repository Agent process failed due to a system error. 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
Explanation: User Response:
Communication failed because of network errors. [System Error (errno = <error number>): <error message>.] Please try connecting to the repository again.
The PowerCenter Client or the Integration Service cannot connect to the Repository Agent. Read the operating system error referenced in this message and make any necessary changes. There might be network problems.
REP_51054
Explanation: User Response: Explanation: User Response:
Internal error: Cannot allocate buffer of size <size> bytes to receive incoming message. The system may be out of memory.
The system is low on resources. Free some system resources. Internal error. Contact Informatica Global Customer Support.
REP_51056
Explanation: User Response:
REP_51058
Explanation:
User Response:
REP_51059
Explanation: User Response:
Repository Agent connection failed, another Repository Agent on host <host name> port <port number> is already connected to this repository <repository name>.
There is another Repository Agent process already running for the repository. Connect to the running Repository Agent, or wait for it to shut down before connecting again.
REP_51071
Explanation: User Response:
REP Messages
313
REP_51072
Explanation: User Response:
A metadata extension named <metadata extension name> already exists in the current domain.
You tried to create or rename a metadata extension. However, another metadata extension with the name you specified already exists for the same type of object in the domain. Specify a unique name for the metadata extension.
REP_51073
Explanation: User Response:
<Value> is not a valid integer value. Please enter an integer value between <minimum value> and <maximum value>.
You entered a value for an integer metadata extension that is either too large or too small. Enter a value that is between the minimum and maximum values.
REP_51074
Explanation: User Response:
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.
You tried to change the precision for a string metadata extension, but the existing string is longer than the precision you specified. 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
Explanation: User Response:
The maximum length is too large. Please specify a value smaller than or equal to <maximum length>.
You tried to enter a precision for a string metadata extension that is too long. Specify a precision that is less than or equal to the maximum length.
REP_51112
Explanation: User Response:
REP_51115
Explanation: User Response:
A table with the name <table name> already exists. Please enter a unique name.
You specified a table name that is already in use. 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.
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. Save the changes in the repository after entering the new business name for the source definition. Then you can use the old business name for another source definition.
Explanation:
User Response:
REP_51120
Explanation: User Response:
314
REP_51134
Explanation: User Response:
The absolute value of the scale cannot be larger than the length/precision.
The absolute value of the scale you entered is larger than the value for length or precision. For example, you set the precision to 5, but set the scale to 7. Enter a value for scale whose absolute value does not exceed the value for length or precision.
REP_51135
Explanation: User Response:
REP_51137
This business name has already been used by the target table <table name> in the repository and has been renamed to <table name>. You must save your changes before renaming this table.
You changed the value for the business name in a target definition. You then attempted to enter the old business name in another target definition. This is not allowed. For example, you changed the business name in the target T1 from B1 to B2. You then entered the business name B1 to another target definition, T2. 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.
Explanation:
User Response:
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>.
When you copy a folder, you do not have permission to a connection object in the target repository. The Copy Folder Wizard will copy the connection from the source repository and rename it.
REP_51292
Explanation: User Response:
REP_51294
Explanation: User Response:
REP_51295
Explanation: User Response:
REP_51296
Explanation: User Response:
REP Messages
315
REP_51297
Explanation: User Response:
REP_51298
Explanation: User Response:
REP_51300
Explanation: User Response: Explanation: User Response:
Error: Inconsistent repository. Repository <repository name> does not have an Administrator user. Repository initialization failed.
The repository database may have inconsistencies. Restore the repository from a backup file and check the database server log for errors. Internal error. Contact Informatica Global Customer Support.
REP_51301
Explanation: User Response:
Unable to send messages to the Repository Service. Initialization of repository <repository name> failed.
Internal error. Contact Informatica Global Customer Support.
REP_51304
Explanation: User Response:
REP_51343
Explanation: User Response:
Unable to connect to the database server. Please check the connection to the database server.
The Repository Agent process could not connect to the repository database server. 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.
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. Enter Relational: or Application: before the connection name for $Source Connection Value on the Properties tab of the session properties.
Explanation:
User Response:
316
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.
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. Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties.
Explanation:
User Response:
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.
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. Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties.
Explanation:
User Response:
REP_51444
Explanation:
MessageSendBufferSize value <message send buffer size> is invalid, ignoring invalid value <message send buffer size>. Using system default value.
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. 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.
User Response:
REP_51445
Explanation:
MessageReceiveBufferSize value <message receive buffer size> is invalid, ignoring invalid value <message receive buffer size>. Using system default value.
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. 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.
User Response:
REP_51447
Explanation: User Response: Explanation: User Response: Explanation:
A repository request has timed out. [System Error (errno = <error number>): <system error message>]. Please try connecting to the repository again.
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. Increase the MessageReceiveTimeout value and MessageSendTimeout value from the repository configuration. Repository Service request timed out due to a slow network. Verify that the network is running properly. The repository is stopped.
REP Messages
317
User Response:
REP_51502
Explanation: User Response:
The value <number of seconds> specified for Database Pool Expiry Timeout value is invalid. The Repository Service is using the default value <number>.
The value specified for Database Pool Expiry Timeout is invalid. For example, it may be less than the minimum, or it may be a negative number or a letter. Accept the default value for Database Pool Expiry Timeout. Enter a valid value for Database Pool Expiry Timeout in the Repository Service advanced properties.
REP_51503
Explanation: User Response:
The value <number of connections> specified for Database Pool Expiry Threshold value is invalid. The Repository Service is using the default value <number>.
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. 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
Explanation: User Response:
REP_51508
Explanation: User Response:
REP_51509
Explanation: User Response:
Workflow task <workflow ID> maximum automatic recovery attempts must be in the range of 0 to 2147483647.
The Maximum Automatic Recovery Attempts option contains a negative number. Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab. The number must be zero or greater.
REP_51510
Explanation: User Response:
REP_51814
Explanation: User Response:
318
REP_51815
Explanation: User Response:
REP_51832
Explanation: User Response:
REP_51848
Explanation: User Response:
REP_51849
Explanation: User Response:
The versioned repository cannot be enabled or restored without a team-based development license key.
PowerCenter cannot enable object versioning until you have a team-based development license key. Apply the Repository Service to a license that has the team-based development option. You can purchase this option from Informatica.
REP_51961
Explanation: User Response:
The value of the environment variable <environment variable name> needs to be encrypted with the latest version of pmpasswd.
The environment variable was encrypted using an old version of pmpasswd. Effective in PowerCenter 8.1, pmpasswd uses a new, more robust encryption algorithm. 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
Explanation: User Response:
REP_55036
Explanation: User Response:
REP_55102
Explanation: User Response: Explanation:
REP Messages
319
Verify that the connection information is valid and that the client machine can access the host machine. The repository version is not the same version as the PowerCenter Client or the Integration Service. 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. The application encountered an error while connecting to the repository. Check the preceding messages to see the cause of the error.
REP_57060
Explanation: User Response:
Login failure.
The Service Manager could not authenticate the user. Check the additional error messages for more information.
REP_57064
Explanation: User Response:
REP_57071
Explanation: User Response:
Unable to connect to the repository database. Please check the Repository Agent configuration.
The Repository Agent could not connect to the repository database. Verify the connectivity information in the repository configuration is correct. Verify that the repository database is running.
REP_57084
Explanation: User Response:
REP_57145
Explanation: User Response:
REP_57151
Explanation: User Response:
320
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.
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. Enter Relational: or Application: before the connection name for the Stored Procedure or Lookup transformation location in the session properties. 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. Enter Relational: or Application: before the connection name in all transformation properties and session properties that specify this database connection name.
Explanation:
User Response:
REP_57201
Explanation: User Response:
REP_57269
Explanation:
User Response:
REP_58224
Explanation: User Response:
Failed to connect from <PowerCenter Client tool> to repository <repository name> because the repository users and groups have not been upgraded.
The PowerCenter Client could not connect to a repository because the repository users and groups have not been upgraded. Upgrade the repository users and groups in the Administrator tool. Then retry the operation in the PowerCenter Client.
REP_61002
Explanation: User Response:
WARNING: <XML definition> contained elements or attributes whose prefixes were removed.
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. Complete the repository upgrade and import the XML definition again.
REP_61003
Explanation: User Response:
Empty key range for key <key name> (group <group>, instance <transformation instance name>, session <session instance name>).
You did not specify a key range for the specified key. Edit the key range and specify the start and end value for the key.
REP Messages
321
REP_61004
Explanation:
Empty key range for key <key name> (group <group> session <session name>).
Same as REP_61003.
REP_61010
Explanation: User Response:
REP_61011
Explanation: User Response:
REP_61012
Explanation: User Response:
Error: Field <port name> of transformation <transformation name> could not be validated.
The Designer could not validate the port in the transformation. Check other error messages preceding this error message.
REP_61013
Explanation: User Response:
REP_61014
Explanation: User Response:
REP_61027
Explanation: User Response:
REP_61031
Explanation: User Response:
Failed to upgrade <XML definition> because removal of prefixes generated an invalid XPATH.
The upgrade process removed a prefix from an element or an attribute. The resulting XML map is not unique and could not be upgraded to a valid XPath. Import the XML definition again.
REP_61032
Explanation: User Response:
Failed to upgrade <XML source> because removal of prefixes caused element names to conflict!
The upgrade strips prefixes from XML element names. The upgraded names may conflict with other element names. Import the XML definition again.
REP_61059
Explanation: User Response:
Warning: Failed to upgrade XML source <source>, version <version>, folder <folder>.
You cannot upgrade the source XML definition because it has inconsistencies. The XML definition is unusable. You must recreate it.
322
REP_61060
Explanation: User Response:
Warning: Failed to upgrade XML target <target>, version <version>, folder <folder>.
You cannot upgrade the target XML definition because it has inconsistencies. The XML definition is unusable. You must recreate it.
REP_61063
Explanation:
User Response:
REP_62340
Explanation:
Transformation <source or target instance name> uses connection variable <connection variable name>, but its value is not specified.
The source or target connection name is specified using the connection variable $Source or $Target. The value of the connection variable is not defined and the Integration Service cannot determine which database connection to use when it runs the session. Enter a value for the $Source or $Target connection variable on the General Options settings of the Properties tab in the session properties.
User Response:
REP_62373
Explanation:
Lookup Transformation <transformation name> has no associated Partial Pipeline. No single group Source Qualifier of name <Lookup table name>. Transformation is not valid.
The Pipeline Lookup transformation is not valid because there is no valid partial pipeline to lookup. The partial pipeline does not have a single group source in the Source Qualifier for a lookup. Therefore, the Lookup Table Name attribute in the Pipeline Lookup transformation does not match the Source Qualifier name in the partial pipeline. Verify that the partial pipeline is valid and has a single group source in the Source Qualifier for the lookup.
User Response:
REP_62377
Explanation:
User Response:
REP_62378
Explanation:
User Response:
REP_62379
Explanation:
Connection name <parameter value> for connection variable <variable name> is not well defined.
A session parameter such as $DBConnection Name 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.
REP Messages
323
User Response:
Verify that the parameter is defined in the parameter file. Verify that the parameter value is not blank.
REP_62385
Explanation: User Response:
Advanced recovery cannot be enabled since the session has mapping variables.
If a session uses mapping variables, you cannot configure the session recovery strategy to resume from the last checkpoint. To set the recovery strategy to resume from the last checkpoint, remove the mapping variables in the session.
REP_62386
Explanation:
Advanced recovery cannot be enabled for session <session name> since the session has mapping variables.
Same as REP_62385.
REP_CORE Messages
REP_CORE_59046
Explanation: User Response:
The high availability license is absent for the Repository Service process <process name>.
The high availability option is required for failover of the Repository Service process. You do not have the high availability option. None.
RFC Messages
RFC_17403
Explanation: User Response:
Function return parameter is specified. However, only <value> out of <value> required values found when parsing the property value string.
Valid return values are not specified in the function return parameter when parsing the property value string. Enter valid return values in the function return parameter.
RFC_17405
Explanation: User Response:
Status or text field of return parameter must have ABAP type char in the source definition.
The ABAP datatype in the status or text field for the return structure is not specified as char in the source definition. Specify the ABAP datatype as char in the status or text field for the return structure in the source definition.
RFC_17411
Explanation:
Output data conversion error for row number <row number> of table parameter <parameter>. This row will be skipped.
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.
324
User Response:
RFC_17412
Explanation:
Output data conversion error for Scalar Output parameter. This row will be skipped.
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. Enter a valid value for the scalar output parameter.
User Response:
RFC_17416
Explanation: User Response:
Exception <exception> has been raised from the RFC function call with IntegrationID <Integration ID>.
The RFC call to the SAP system from the SAP application server failed with an exception. Enter valid input data for the SAP system. Verify that the SAP application server is running.
RFC_17422
Explanation: User Response:
Function Name <Function name> and Sequence ID <Sequence ID> do not match. One of them is incorrect.
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. Prepared data might be modified or incorrectly prepared in the prepared data pipeline. Check the specified row data.
RFC_17423
Explanation:
Input for function <Function name> is received while expecting input for function <Function name>.
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. The RFCFunctionCall Custom transformation expects the SequenceID to increase by increment of 1 from the previous SequenceID. Check the data in the PreparedData targets.
User Response:
RFC_17424
Explanation: User Response:
Call to function <Function name> corresponding to TransactionID = <Transaction ID>, IntegrationID = <Integration ID> failed. Cannot continue transaction.
The function call to SAP with the specified TransactionID and IntegrationID has failed. See the error messages in the session log for more information.
RFC_17425
Explanation: User Response:
RFC_17427
Explanation: User Response:
Error when trying to create SAP internal table for function table parameter <Parameter name>.
The Integration Service failed to create new SAP internal table. Check if the node where the Integration Service process runs is out of memory.
RFC_17439
Explanation:
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.
The source file may be invalid.
RFC Messages
325
User Response:
Examine the session log and the source file and eliminate errors.
RR Messages
RR_4004
Explanation: User Response:
RR_4006
Explanation:
User Response:
RR_4025
Explanation: User Response: Explanation: User Response:
RR_4032
Explanation:
Warning: # of sorted ports <number of ports> must be less than # of projected fields <number of connected output ports>. Ignoring sort request.
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. Change the sort count to less than or equal to connected ports in the Designer.
User Response:
RR_4033
Explanation: User Response:
RR_4034
Explanation: User Response:
RR_4035
Explanation:
SQL error.
Error executing SQL query.
326
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
Explanation: User Response:
RR_4038
Explanation: User Response:
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.
You entered a query containing characters that are invalid in the source database connection code page. 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.
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. Change either the join, filter, or both conditions to contain characters included in the source database connection code page.
Explanation:
User Response:
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.
You entered a filter condition containing characters that are invalid in the source database connection code page. Change the filter condition to contain characters included in the source database connection code page.
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.
You defined a partition key for a port in the source qualifier that you deleted. 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.
RR Messages
327
RS Messages
RS_39037
Explanation: User Response:
RS_39061
Explanation: User Response:
RS_39068
Explanation:
Failed to register LDR <local repository name> to GDR <global repository name>.
The Repository Service could not register the local repository to the global repository because you specified incorrect connectivity information for either the local or global repository. Message RS_39090 or message RS_39091 may precede this message. Check preceding messages for more information.
User Response:
RS_39090
Explanation: User Response:
Cannot complete [Register] operation because of failure to start or connect to repository <repository_name>.
The Repository Service could not register a local repository to a global repository because it could not start the Repository Agent process for one of the repositories. Check preceding messages to see the cause of the error. Also, verify that the local and global repository databases are running, and that you entered correct connectivity information.
RS_39091
Explanation: User Response:
Cannot complete [UnRegister] operation because of failure to start or connect to repository <repository_name>.
The Repository Service could not unregister a local repository from a global repository because it could not start the Repository Agent process for one of the repositories. 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_39092
Explanation: User Response:
Cannot promote repository <repository_name> to be a Global repository because of failure to start or connect to the repository.
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. 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.
328
RS_39107
Explanation: User Response:
RS_39109
Explanation: User Response:
RS_39120
Explanation: User Response:
ERROR: This product license does not allow global repositories. Only a PowerCenter license does that.
You cannot create global repositories or promote a local repository to a global repository with the current license. If you want to create global repositories, you need to purchase the Team-based Development option.
RS_39121
Explanation: User Response:
ERROR: This product license does not allow registering or unregistering repositories. Only a PowerCenter license does that.
You cannot register a local repository with or unregister a local repository from a global repository with the current license. If you want to register or unregister repositories in a repository domain, you need to purchase the Team-based Development option.
RS_39141
Explanation: User Response:
RS_39145
Explanation: User Response: Explanation: User Response:
RS_39209
Explanation: User Response:
RS Messages
329
CHAPTER 18
SAPUTIL Messages
SAPUTIL_99506
Explanation: User Response:
SAPUTIL_99057
Explanation: User Response:
SAPUTIL_99072
Explanation: User Response:
SAPUTIL_99076
Explanation:
330
User Response:
SDKC Messages
SDKC_37005
Explanation: User Response:
SDKC_37006
Explanation: User Response:
SDKC_37007
Explanation: User Response:
SDKC_37008
Explanation: User Response:
SDKS Messages
SDKS_38005
Explanation: User Response:
SDKS_38006
Explanation: User Response:
Plug-in #<ID>s interface version <version> is not compatible with SDK interface version <version>.
The version of the plug-in and the SDK version are not compatible. Update the plug-in version to an SDK-compatible version.
SDKS_38007
Explanation: User Response:
SDKC Messages
331
SDKS_38200
Explanation: User Response:
SDKS_38505
Explanation: User Response:
Plug-in #<ID>s target <target> indicated that the error threshold <number> has been reached.
The Integration Service reached the maximum number of errors for the session. The session failed. If you want to increase the number of allowable errors per session, increase the session error threshold.
SDKS_38605
Explanation: User Response:
SDKXML Messages
SDKXML_43009
Explanation: User Response:
SF Messages
SF_34030
Explanation: User Response:
Client application <application>, connection <connection ID>: recv failed. System returns error code <error number>, error message <error message>.
The client application failed to establish a connection. See the additional error message for more information. Also, disable and enable the Integration Service.
SF_34032
Explanation: User Response:
Closing client application <application>s connection dues to PROTOCOL ERROR. Please contact Informatica Global Customer Support.
Internal error. Contact Informatica Global Customer Support.
SF_34033
Explanation:
PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.
Internal error.
332
User Response:
SF_34034
Explanation: User Response:
PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.
Internal error. Contact Informatica Global Customer Support.
SF_34035
Explanation: User Response:
PROTOCOL ERROR: Got request ID <request ID> while expecting request ID <request ID> from client application <application> on connection <connection ID>.
Internal error. Contact Informatica Global Customer Support.
SF_34036
Explanation: User Response:
PROTOCOL ERROR: Got request key <key> while expecting request key <key> from client application <application> on connection <connection ID>.
Internal error. Contact Informatica Global Customer Support.
SF_34037
Explanation: User Response:
PROTOCOL ERROR: Got request type <request type> while in state <state> from client application <application> on connection <connection ID>.
Internal error. Contact Informatica Global Customer Support.
SF_34062
Explanation: User Response:
SF_34063
Explanation: User Response:
SF_34064
Explanation: User Response:
SF_34065
Explanation: User Response:
SF_34066
Explanation: User Response:
SF_34067
Explanation:
SF Messages
333
User Response:
SF_34068
Explanation: User Response:
SF_34069
Explanation: User Response:
SF_34070
Explanation: User Response:
SF_34071
Explanation: User Response:
SF_34072
Explanation: User Response:
SF_34094
Explanation: User Response:
SF_34095
Explanation: User Response:
SF_34096
Explanation: User Response:
SF_34098
Explanation: User Response:
SF_34105
Explanation:
Failed to redirect standard error (stderr) messages to the file <file name>. System error is <system error number> <system error message>.
You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard error messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory.
334
User Response:
SF_34106
Explanation:
Failed to redirect standard output (stdout) messages to the file <file name>. System error is <system error number> <system error message>.
You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard output messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory. Review the system error and contact the system administrator.
User Response:
SF_34109
Explanation:
Failed to open file <file name> for redirecting console output (stdout/stderr) messages System error is <system error number> <system error message>.
You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service failed to open the file to write messages. Verify that the user starting the Integration Service has write permission on the file directory. Review the system error and contact the system administrator.
User Response:
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.
During a transient failure, the Integration Service could not access the $PMStorageDir to store the request for recovery. 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
Explanation: User Response:
SF_34132
Explanation: User Response:
SF_34134
Explanation: User Response:
SF_34135
Explanation: User Response:
SF Messages
335
SF_34136
Explanation: User Response:
SF_34155
Explanation: User Response:
Child process <process ID> terminated due to spurious abort errno <error number>.
The Session or Command task exited unexpectedly and the machine running the Integration Service process generated an error. 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
Explanation: User Response:
High availability has been disabled. Contact Informatica Global Customer Support.
A custom property for the Integration Service is configured to disable high availability. Contact Informatica Global Customer Support.
SFDC Messages
SFDC_31101
Explanation: User Response:
Login failed. User <login user name>. Fault code <error code>. Reason <error message>.
You attempted to log in to Salesforce.com with an incorrect user name or password. Verify that the user name and password are correct.
SFDC_31102
Explanation: User Response:
Query failed. User <login user name>. SOSQL <SOSQL query>. Fault code <error code>. Reason <error message>.
The SOQL query could not be executed. See the additional error message for more information.
SFDC_31103
Explanation: User Response:
QueryMore failed. User <login user name>. SOSQL <SOSQL query>. Query Batch Index <query batch>. Fault code <error code>. Reason <error message>.
The queryMore operation could not be executed. See the additional error message for more information.
SFDC_31105
Explanation: User Response:
Fields mis-matched. Expected field name <field name>. Returned field name <field name>.
The field name defined in the source or target definition does not match the field name returned from Salesforce.com. Change the field name in the source or target definition to match the field name in the Salesforce object.
336
SFDC_31106
Explanation: User Response:
GetServerTimestamp failed. User <login user name>. Fault code <error code>. Reason <error message>.
The Integration Service could not retrieve the current system timestamp from the Salesforce service. See the additional error message for more information.
SFDC_31107
Explanation: User Response:
GetDeleted failed. User <login user name>. Start Time <time>. End Time <time>. Fault code <error code>. Reason <error message>.
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. See the additional error message for more information.
SFDC_31112
Explanation: User Response:
Invalid Flush Interval value <number of seconds>. It must be set to a positive integer value.
The value for the change data capture flush interval is invalid. In the session properties, set the flush interval to a positive integer value if you use change data capture.
SFDC_31113
Explanation: User Response:
Conversion Error Occurred. Field name <field name>. Data Value <field value before conversion>.
An error occurred while converting data from the Salesforce datatype to the PowerCenter datatype. Verify the datatype of the field and make any necessary changes before running the session again.
SFDC_31114
Explanation: User Response:
Row Errors <number of row errors> exceeded session threshold <error threshold>.
The number of row errors was greater than the number of errors allowed by the session error threshold. Fix the row errors and then run the session again.
SFDC_31115
Explanation: User Response:
Source <source name> and Application Source Qualifier <Application Source Qualifier name> have different number of fields.
The source and the Application Source Qualifier transformation do not have the same number of fields. Verify that the source and the Application Source Qualifier transformation have the same number of fields.
SFDC_31116
Explanation: User Response:
Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same name.
The source field name does not match the Application Source Qualifier port name. Change the port name in the Application Source Qualifier transformation to match the field name in the source.
SFDC_31117
Explanation:
Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same field position.
The field in the source does not have the same position as the field in the Application Source Qualifier transformation.
SFDC Messages
337
User Response:
Move the field in the Application Source Qualifier transformation to match the field position in the source.
SFDC_31118
Explanation: User Response:
Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same datatype, precision, or scale.
The field in the source does not have the same datatype, precision, or scale as the field in the Application Source Qualifier transformation. 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: User Response:
Login failed. User <login user name>. Fault code <error code>. Reason <error message>.
You attempted to log in to Salesforce.com with an incorrect user name or password. Verify that the user name and password are correct.
SFDC_31202
Explanation: User Response:
Error received from salesforce.com. Fields <field names>. Status code <status code>. Message <error message>.
The Integration Service failed to create, update, upsert, or delete a Salesforce.com object. Read the error message and make any necessary changes. For more information, look up the error code in the Salesforce.com documentation.
SFDC_31203
Explanation: User Response:
A fault is received in a create request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
An error occurred in a create request. See the additional error message for more information.
SFDC_31204
Explanation: User Response:
A fault is received in an update request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
An error occurred in an update request. See the additional error message for more information.
SFDC_31205
Explanation: User Response:
A fault is received in a delete request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
An error occurred in a delete request. See the additional error message for more information.
SFDC_31206
Explanation: User Response:
A fault is received in an upsert request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
An error occurred in an upsert request. See the additional error message for more information.
SFDC_31207
Explanation: User Response:
338
SFDC_31208
Explanation: User Response:
SM Messages
SM_7024
Explanation: User Response:
Transformation Parse Fatal Error: Filter clause did not evaluate to a numeric value.
The filter condition you specified in Filter transformation does not evaluate to a numeric value. Verify that the filter condition evaluates to a numeric value.
SM_7027
Explanation: User Response:
Transformation evaluation error; current row skipped. trying to delete a non-existing row.
The Integration Service failed to evaluate an expression with a particular row, forcing it to skip that row. 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.
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. 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.
Explanation:
User Response:
SM_7051
Explanation:
Aggregate error: index file timestamp is earlier than the timestamp of the Aggregator transformation or mapping.
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. The mapping and Aggregator transformation timestamp must be earlier than the cache file. Either reinitialize the aggregate cache or delete the cache file manually.
User Response:
SM_7072
Explanation: User Response:
SM Messages
339
SM_7073
Explanation:
SM_7087
Explanation:
Aggregate Error: code page <code page> and cached code page <code page> are not twoway compatible.
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. 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.
User Response:
SM_7088
Explanation:
Aggregate Error: sort order <sort order> and cached sort order <sort order> mismatch.
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. 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.
User Response:
SM_7089
Explanation:
Aggregate error: Unknown code page <code page> in the aggregation cache.
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. Reinitialize the cache or manually delete the cache file.
User Response:
SM_7091
Explanation: User Response:
Transformation Parse Fatal Error: Update Strategy Expression did not evaluate to a numeric value.
The update strategy expression you specified in the Update Strategy transformation does not evaluate to a numeric value. Verify that the update strategy expression evaluates to a numeric value.
SM_7096
Explanation: User Response:
SM_7099
Explanation: User Response:
Fatal Error: Header from incremental aggregation files for Aggregator transformation <transformation name> has invalid data.
The Integration Service failed to upgrade the incremental aggregation files because the files contain corrupt data. 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.
340
SM_7200
Explanation: User Response:
Error reading from incremental aggregation files for Aggregator transformation <transformation name>.
The Integration Service failed to upgrade the incremental aggregation files because the Integration Service does not have read permission on the cache directory. 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.
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. Check the disk for free space. Or, verify that the user configured to start Informatica Services has write permission on the cache directory.
Explanation:
User Response:
SM_7203
Explanation: User Response:
SM_7204
Explanation:
User Response:
SM_7207
Explanation: User Response:
SM_7208
Explanation:
Mapping has been modified since the incremental aggregation files for transformation <transformation name> were last saved.
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. 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.
User Response:
SM Messages
341
SM_7209
Explanation:
Cache for transformation <transformation name> was created in a precision mode different from the one specified by the session.
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. 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.
User Response:
SM_7210
Explanation: User Response:
SM_7211
Explanation:
The Integration Service data movement mode differs from the data movement mode used when the cache was created.
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. 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.
User Response:
SM_7217
Explanation: User Response:
Error: Failed to expand update override <text> for target instance <target name>.
The Integration Service cannot expand a parameter or variable in the target update override. 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 mapping variable to a text string in the parameter file. The Integration Service cannot expand the parameter or variable in the target update override due to an internal error. Contact Informatica Global Customer Support.
SM_7218
Explanation:
User Response:
342
SORT Messages
SORT_40046
Explanation: User Response:
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>.
The Integration Service could not allocate memory for the Sorter or Lookup transformation because there is not enough available memory. 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>.
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. Increase the memory limit for processes on the UNIX machine. Same as SORT_40046.
Explanation:
User Response:
SORT_40095
Explanation: User Response:
SORT_40096
Explanation: User Response:
SORT_40102
Explanation: User Response:
SORT_40111
Explanation: User Response:
SORT_40179
Insufficient space to map <amount of memory> MB of memory: <error message>. Either increase the swap space or decrease the Cache Size in the Transformation <transformation name>.
Same as SORT_40046.
Explanation:
SORT_40189
Explanation:
SORT Messages
343
User Response:
Free Integration Service system resources by closing applications. After you free system resources, restart the workflow.
SORT_40304
Explanation:
This operation appears to need <value> MB of memory; excessive paging is possible; continuing.
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. To increase session performance, increase the Sorter transformation cache size.
User Response:
SORT_40401
Explanation: User Response:
A fatal Sort error has occurred in function <function name>. Errno = <error number>.
Internal error. Contact Informatica Global Customer Support.
SORT_40406
Explanation: User Response:
SORT_40407
Explanation: User Response:
In transformation <transformation name> in partition <partition number>, an error has occurred <error message>.
The Integration Service encountered an error when it processed a row in the specified partition and transformation. Read the error message displayed in this error message and other messages in the session log for more information.
SORT_40409
Explanation: User Response:
SORT_40414
Explanation: User Response:
Error: Total row size <row size> in transformation <transformation name> is more than the allowed maximum [8 MB].
The sum of all port sizes in the specified Sorter or Lookup transformation exceeds 8 MB. 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.
SORT_40415
Explanation: User Response:
SORT_40416
Explanation:
344
User Response:
Grant read, write, and execute permissions for the Sorter transformation work directory to the user who starts the Integration Service.
SORT_40424
Explanation: User Response:
Error: The memory size <memory size> specified for Sorter Transformation exceeds the 32-bit address space. It cannot be more than <number> on a 32-bit server.
The Sorter transformation cache size is too large. Reduce the Sorter transformation cache size in the session properties.
SPC Messages
SPC_10027
Explanation: User Response:
Cannot start process for service <service name> on node <node name>. Process is shutting down. Try again later.
The service is shutting down. You cannot enable the service until it completely shuts down. To enable the service, disable the service, and then enable it again.
SPC_10039
Explanation: User Response:
Could not start Informatica PowerCenter Web Services Hub service on port <port number> because this port is in use.
The port number assigned to the Web Services Hub is already in use. Reconfigure the Web Services Hub to use a different port number.
SPC_10050
Explanation:
The domain failed to restart the service <service name> after trying for maximum <number of restart attempts> restart attempts.
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. 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.
User Response:
SQL Messages
SQL_50001
Explanation: User Response:
SQL_50002
Explanation:
SPC Messages
345
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
Explanation: User Response:
ScriptName is empty.
The SQL transformation is configured to run an external SQL script but the ScriptName port contains no data. 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
Explanation: User Response:
SetProperty failed.
The Integration Service failed to set database properties for an SQL transformation dynamic connection. 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_50005
Explanation: User Response:
SQL_50006
Explanation: User Response:
FlushOutRow failed.
The Integration Service failed to generate an output row from the SQL transformation. Review previous error messages for more information.
SQL_50007
Explanation: User Response:
ODL Error has occurred. Please see the pre-defined error port for detailed error message.
The Integration Service encountered a database error while processing an SQL query from the SQL transformation. Review the error messages from the SQL transformation SQLError port.
SQL_50008
Explanation: User Response:
Number of columns in the select query is greater than the number of output ports in the SQL transformation.
The SQL transformation does not have an output port for each column in the SQL SELECT statement. Add the missing output ports to the SQL transformation.
SQL_50009
Explanation: User Response:
SQL_50010
Explanation:
346
User Response:
Verify the script file exists and is accessible by the Integration Service.
SQL_50011
Explanation: User Response:
SQL_50013
Explanation: User Response:
SQL_50014
Explanation: User Response:
SQL_50015
Explanation: User Response:
SQL_50017
Explanation: User Response:
SQL_50018
Explanation: User Response:
SQL_50070
Explanation:
User Response:
SQL_50071
Explanation:
Session failed because a connection failure occurred after the SQL transformation passed some of the output rows downstream.
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. None. Informational message.
User Response:
SQL Messages
347
SQL_50072
Explanation:
An error occurred expanding a parameter or variable in the environment SQL <connection or transaction environment SQL> for the connection object <connection name>.
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. 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 mapping variable to a text string in the parameter file.
User Response:
SR Messages
SR_17000
Explanation: User Response:
SR_17001
Explanation: User Response:
SR_17004
Explanation: User Response:
SR_17005
Explanation: User Response:
SR_17006
Explanation: User Response:
Unknown data transfer mode. The mode can only be staging or streaming.
Internal Error. Contact Informatica Global Customer Support.
SR_17007
Explanation: User Response:
ERROR: Run failed: SAP error message <ABAP program name or staging file name or Application Source Qualifier form name> SAP <error message>.
There was a problem with the RFC communication with SAP. Get the detailed message from the session log. See the RFC trace file, SAP system log, and SAP documentation for more details. contact Informatica Global Customer Support for further assistance.
SR_17009
Explanation:
348
User Response:
Regenerate the ABAP program for the mapping against the source system and run the session on the same SAP system.
SR_17010
Explanation: User Response:
SR_17011
Explanation: User Response:
SR_17012
Explanation: User Response:
SR_17013
Explanation: User Response:
Could not get status information for a Background job: <SAP message>.
The connection to the SAP system is broken. Check with the SAP system administrator or contact Informatica Global Customer Support.
SR_17014
Explanation: User Response:
SR_17015
Explanation: User Response:
Could not delete the Staging File <file name>: <SAP message>.
You accessed the staging file through NFS mount, and the Integration Service user may not have write permission on the staging file or directory. Get write permissions from the system administrator for the Integration Service user.
SR_17016
Explanation: User Response:
The program <program name> was generated but not installed for mapping <mapping name> version <version number>.
You generated an ABAP program for this mapping, but you did not install it on the SAP system. Open the Generate and Install dialog box in the Mapping Designer and install the ABAP program for the mapping.
SR_17020
Explanation: User Response:
SR Messages
349
SR_17021
Explanation: User Response: Explanation: User Response:
ERROR in getting information for SetId <SetID name> and Table Name <table name>.
You might have transported the ABAP program to a system that contains different hierarchy and/or master table information. Verify the SAP source matches the definition in the repository. RFC error. Contact the SAP administrator.
SR_17022
Explanation: User Response:
SR_17023
Explanation: User Response:
Tree is inconsistent.
Internal SAP error. Contact the SAP administrator.
SR_17024
Explanation: User Response:
Error in passing parameters to SAP system for hierarchy with SetID <setid name> and TableName <table name>.
SAP could not import hierarchy information from PowerCenter, possibly because the SAP administrator did not run the transport program, YPMPARSQ. Have the SAP administrator run the program YPMPARSQ from the ZERP development class.
SR_17025
ERROR: Run failed for hierarchy with SetID <setid name> and TableName <table name>: SAP error message <ABAP program name or staging filename or Application Source Qualifier form name>.
Either the SAP system failed or the program to extract from a hierarchy failed. Check with the SAP administrator.
SR_17054
The time at which a stream mode program was installed for this mapping is older than the time at which this mapping was saved last. The mapping name is <mapping name>, version <version number> and the program name is <program name>. Please regenerate and install the program using PowerCenter Designer for this mapping.
You saved the repository with the mapping open after you installed the ABAP program on the application server. In the Designer, open the mapping and save the repository. Then install the ABAP program.
SR_17055
The time at which a file mode program was installed for this mapping is older than the time at which this mapping was saved last. The mapping name is <mapping name>, version <version number> and the program name is <program name>. Please regenerate and install the program using PowerCenter Designer for this mapping.
You saved the repository with the mapping open after you installed the ABAP program on the application server. In the Designer, open the mapping and save the repository. Then install the ABAP program.
SR_17056
Explanation:
350
User Response:
Ensure that the SAP reader code page is compatible with the SAP code page.
SR_17057
Explanation: User Response:
Unable to retrieve code page information for code page ID <code page ID>.
The pmlocale.bin file is missing or does not have the code page ID you selected in the database connection. Verify the existence of the pmlocale.bin file and the code page information.
SR_17058
Explanation: User Response:
Unable to create a locale from code page <code page> <code page ID>.
Internal error. Contact Informatica Global Customer Support.
SR_17059
Explanation: User Response:
SAP Code page: <code page ID> is not compatible with the user selected code page <code page>.
The SAP code page is not compatible with the code page you selected in the database connection. Select a code page that is compatible with the Integration Service and the SAP system.
SR_17085
Explanation: User Response:
SR_17061
Explanation: User Response:
SR_17062
Explanation: User Response:
SR_17063
Explanation: User Response:
SR_17064
Explanation: User Response:
SR_17065
Explanation:
SR Messages
351
User Response:
See the additional error message for more information. Also see the SAP trace file for more information.
SR_17067
Explanation: User Response:
SR_17068
Explanation: User Response:
SR_17069
Explanation: User Response:
SR_17073
Explanation: User Response:
SR_17090
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier name> has invalid user defined query <query> with character error at <number> location.
You entered a query containing characters that are not valid in the source database connection code page. Change the query to contain characters in the source database connection code page.
SR_17091
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier name> has invalid filter clause <filter> with character error at <number> location.
You entered a filter condition containing characters that are not valid with the source database connection code page. Change the filter condition to contain characters included in the source database connection code page.
SR_17092
Explanation: User Response:
The Application Source Qualifier <Application Source Qualifier name> has invalid join and/or filter override <join override> with character error at <number> location.
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. Change either the join, filter, or both conditions to contain characters in the source database connection code page.
352
SR_17138
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.
You defined a partition key for a port in the Application Source Qualifier that you deleted. 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
Explanation: User Response:
Error: The filter expression is missing a source or a list of sources or a source field for which this expression is specified.
You entered a wrong syntax for the filter expression. Enter the filter expression using the proper syntax.
SR_17157
Explanation: User Response:
SR_17158
Explanation: User Response:
SR_17159
Explanation: User Response:
Error: A table level filter is not allowed with a field level filter.
You specified a table level filter within a field level filter, in the filter expression. Delete the table level filter in the field level filter expression.
SR_17163
Explanation: User Response:
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.
The SAP system is Unicode data-enabled, but the Integration Service is running in ASCII data movement mode. Change the data movement mode of the Integration Service to Unicode.
SR_17171
Explanation: User Response:
SR Messages
353
CHAPTER 19
TE to TT Error Messages
This chapter includes the following topics:
TE Messages, 354 TIB Messages, 356 TM Messages, 367 TT Messages, 378
TE Messages
TE_7102
Explanation: User Response:
Initialization error. Failed to get the last saved time for mapping <mapping name>.
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. Contact Informatica Global Customer Support.
TE_7104
Explanation: User Response:
An error occurred while creating group <group number> of target <target name>.
During session initialization, the Integration Service failed to create a group object. Review the session log for related messages.
TE_7105
Explanation: User Response:
TE_7106
Explanation: User Response:
Failed to allocate or initialize the group ID <group ID> for target <target name>.
During session initialization, the Integration Service failed to create an XML group ID. Check the previous message in the session log for more information.
TE_7112
User Response:
Message recovery with non-repeatable source does not allow XML targets in the mapping.
Use a target other than an XML target or disable message recovery.
TE_7117
Explanation:
354
User Response:
TE_7122
Explanation: User Response:
The session is configured for user-defined commit, but the target <target name> is not receiving transactions from any upstream transformation.
The session is configured for user-defined commit, but the target in the mapping is not connected to an upstream effective transaction generator. Change the commit type, or connect the target to an effective transaction generator, such as a Transaction Control transformation.
TE_7127
User Response:
TE_7131
Explanation:
The transformation <transformation> is not configured to propagate transactions. The session cannot run in real time.
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. Disable flush latency, or verify that the mapping does not contain any real-time limitations.
User Response:
TE_7133
Explanation:
The master input for the unsorted Joiner transformation <transformation name> cannot be partitioned because the Joiner transformation is not a partition point.
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. 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.
User Response:
TE_7134
Explanation:
Warning. The master input for the sorted Joiner transformation <transformation name> is partitioned.
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. Verify that the partitions in the master pipeline are configured to pass sorted and grouped data to the sorted Joiner transformation.
User Response:
TE_7135
Explanation:
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>.
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. 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.
User Response:
TE Messages
355
TIB Messages
TIB_34001
Explanation: User Response:
TIB_34002
Explanation: User Response: Explanation: User Response: Explanation: User Response:
TIB_34003
Explanation: User Response:
TIB_34004
Explanation: User Response:
TIB_34010
Explanation: User Response:
TIB_34015
Explanation: User Response:
TIB_34021
Explanation: User Response:
TIB_34022
Explanation: User Response:
356
TIB_34025
Explanation: User Response:
TIB_34026
Explanation: User Response:
Data overflow happened when trying to insert value <value> into field of type <datatype>.
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. Modify the datatype for the column in the mapping.
TIB_34027
Explanation: User Response:
Invalid date.
The date value for the column is invalid. Check the data. Make sure the data contains valid values for the date.
TIB_34028
Explanation:
Data overflow.
The Integration Service could not pass all the data from one column to another. The precision of the output port might be larger than the precision of the input port. For example, the datatype of the output port is int64 and the datatype of the input port is int8. The precision of the output port is higher than the precision of the input port. As a result, the data might contain inconsistencies. The row was rejected. Modify the mapping by changing the precision or datatypes of the ports so that the precision of the output port is greater than or equal to the precision of the input port.
User Response:
TIB_34029
Explanation: User Response: Explanation: User Response:
TIB_34030
Explanation: User Response: Explanation: User Response:
Data overflow happened when trying to insert value <value> into field of type <type>.
Some connected ports in the mapping have different datatypes. The input port has a larger datatype than the output port. As a result, the Integration Service could not pass all the data. Modify the mapping so that the connected columns contain datatypes of a similar range. 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. Modify the datatype for the column in the mapping.
TIB_34031
Explanation: User Response:
TIB Messages
357
TIB_34032
Explanation: User Response:
TIB_34033
Explanation: User Response:
TIB_34034
Explanation: User Response:
TIB_34035
Explanation: User Response:
TIB_34036
Explanation: User Response:
Tibrv driver failed to set subject name <subject name> for current message: <TIBCO error message>.
The Integration Service could not set the specified subject name for the current message. See the TIBCO documentation for instructions to correct the error.
TIB_34037
Explanation: User Response:
Tibrv driver failed to send the current message: <TIBCO error message>.
The Integration Service could not send the specified message. See the TIBCO documentation for instructions to correct the error.
TIB_34038
Explanation: User Response:
TIB_35001
Explanation: User Response:
TIBCO reader cannot get connection reference for the source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
TIB_35002
Explanation: User Response:
TIBCO reader cannot get connection for the source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
358
TIB_35003
Explanation: User Response:
TIBCO reader failed to initialize connection properties for the source qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize a connection for the specified Source Qualifier transformation. The connection attributes may be invalid. Verify the connection attributes for the Source Qualifier transformation in the Connection Object Definition dialog box.
TIB_35004
Explanation: User Response:
TIBCO reader failed to initialize reader properties for the source qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize the session. Session properties for the source qualifier instance might be invalid. Check the additional error message for more information.
TIB_35005
Explanation: User Response:
TIBCO reader failed to initialize TIBCO driver for the source qualifier instance <Source Qualifier name>.
The Integration Service cannot initialize the session. Session properties for the source qualifier instance might be invalid. Check the additional error message for more information.
TIB_35006
Explanation: User Response:
TIBCO reader failed to initialize TIBCO source for the source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
TIB_35008
Explanation: User Response:
TIB_35009
Explanation: User Response:
TIB_35010
Explanation: User Response:
TIB_35011
Explanation: User Response:
TIB_35014
Explanation: User Response:
TIB Messages
359
TIB_35015
Explanation: User Response:
TIB_35016
Explanation: User Response:
Reader partition <partition> failed to truncate message cache to last serialized message: <error message>.
The Integration Service could not truncate the last message in the cache. Check the additional error message for more information.
TIB_35017
Explanation: User Response:
TIB_35018
Explanation: User Response:
TIB_35020
Explanation: User Response:
TIB_35021
Explanation: User Response: Explanation: User Response:
TIB_35022
Explanation: User Response:
TIB_35024
Explanation: User Response:
360
TIB_35025
Explanation: User Response:
Reader partition <partition> failed to close checkpoint at real-time flush point: <error message>.
The Integration Service could not commit messages to the target at the end of the Real-time Flush Latency interval. The session failed. Check the additional error message for more information.
TIB_35026
Explanation: User Response:
TIB_35027
Explanation: User Response:
TIB_35028
Explanation: User Response:
Real-time feature is not enabled for the source qualifier instance <Source Qualifier name>.
This is an informational message. You did not configure the session to run in real time. If you want to run the session in real time, you must configure the session properties for realtime data extraction.
TIB_35030
Explanation: User Response:
TIBCO reader cannot get source property <property> for the source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
TIB_35031
Explanation: User Response:
TIBCO reader cannot get the source qualifier instances from the mapping.
Internal error. Contact Informatica Global Customer Support.
TIB_35033
Explanation: User Response:
TIBCO reader failed to support recovery for the source qualifier instance <Source Qualifier name>.
Internal error. Contact Informatica Global Customer Support.
TIB_35037
Explanation: User Response:
TIB_35039
Explanation: User Response:
The source qualifier instance <Source Qualifier name> contains the datatype msg, which is incompatible with a TIB/Adapter SDK connection.
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. 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 Messages
361
TIB_35040
Explanation:
The source qualifier instance <Source Qualifier name> contains the header field Time Limit, which is incompatible with a TIB/Adapter SDK connection.
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. Remove the Time Limit field from the source definition.
User Response:
TIB_36001
Explanation: User Response: Explanation: User Response: Explanation: User Response:
TIB_36002
Explanation: User Response:
TIBCO driver failed to set default time limit for Certified Message Delivery: <TIBCO error message>.
The Integration Service cannot set a default time limit for sending certified messages. See the TIBCO documentation for instructions to correct the error.
TIB_36004
Explanation: User Response:
TIB_36005
Explanation: User Response:
TIB_36006
Explanation: User Response:
Tibrv driver failed to create a listener for receiving messages: <TIBCO error message>.
The Integration Service could not create a listener to read messages. See the TIBCO documentation for instructions to correct the error.
TIB_36009
Explanation: User Response:
Tibrv driver failed to set reply subject name <reply subject name> for the current message: <TIBCO error message>.
The Integration Service failed to set the specified reply subject name for the current message. See the TIBCO documentation for instructions to correct the error.
TIB_36010
Explanation: User Response:
Tibrv driver failed to set a time limit for the current message: <TIBCO error message>.
The Integration Service could not set a time limit for the current message. See the TIBCO documentation for instructions to correct the error.
362
TIB_36013
Explanation: User Response:
TIB_36014
Explanation: User Response:
TIB_36015
Explanation: User Response:
TIB_36016
Explanation: User Response:
Tibrv driver failed to set limit policy for message queue: <TIBCO error message>.
The Integration Service could not set a limit policy for the event queue. See the TIBCO documentation for instructions to correct the error.
TIB_36017
Explanation: User Response:
Tibrv driver failed to create message queue for advisory messages: <TIBCO error message>.
The Integration Service could not create a message queue for message events. See the TIBCO documentation for instructions to correct the error.
TIB_36018
Explanation: User Response:
Tibrv driver failed to create a listener for advisory messages: <TIBCO error message>.
The Integration Service could not create a listener for advisory messages. See the TIBCO documentation for instructions to correct the error.
TIB_36019
Explanation: User Response:
Tibrv driver failed to create a thread to dispatch advisory messages: <TIBCO error message>.
The Integration Service could not create a dispatch thread for advisory messages. See the TIBCO documentation for instructions to correct the error.
TIB_36020
Explanation: User Response:
TIB_36021
Explanation: User Response:
TIB_36022
Explanation:
Tibrv driver failed to get confirmation for the message with sequence number <number>.
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. Change the time limit policy in the session properties. Verify that the subscriber is running.
User Response:
TIB Messages
363
TIB_36023
Explanation: User Response:
TIB_36036
Explanation: User Response:
Tibrv driver failed to get message sequence number: <TIBCO error messages>.
TIB/Rendezvous cannot get the message sequence number. See the TIBCO documentation for instructions to correct the error.
TIB_36037
Explanation: User Response:
TIB_36038
Explanation: User Response:
TIB_36039
Explanation: User Response:
TIB_36040
Explanation: User Response:
TIB_36057
Explanation: User Response:
TIB_36058
Explanation: User Response:
Failed to get the number of fields in a TIB/Rendezvous message: <TIBCO error message>.
The Integration Service encountered an error while trying to determine the number of fields in the TIB/Rendezvous message. See the TIBCO documentation for information about fixing the error.
TIB_37001
Explanation: User Response:
TIB_37006
Explanation: User Response:
364
TIB_37007
Explanation: User Response:
TIB_37008
Explanation: User Response:
Tibsdk driver failed to add the listener to the subscriber: <TIBCO error message>.
The Integration Service could not initialize the session. See the TIBCO documentation for information on fixing the error.
TIB_37009
Explanation: User Response:
TIB_37011
Explanation: User Response:
Tibsdk driver failed to start adapter instance <adapter instance>: <TIBCO error message>.
The Integration Service could not start the specified adapter instance. As a result, the Integration Service could not initialize the session. See the TIBCO documentation for information on fixing the error.
TIB_37012
Explanation: User Response:
Tibsdk driver failed to pre-register a listener <pre-registered listener>: <TIBCO error message>.
The Integration Service could not initialize the session. See the TIBCO documentation for information on fixing the error.
TIB_37023
Explanation: User Response:
TIB_37024
Explanation: User Response:
TIB_37025
Explanation: User Response:
An exception occurred when Tibsdk driver initialized for advisory messages: <TIBCO error message>.
The Integration Service could not initialize the session. See the TIBCO documentation for information on fixing the error.
TIB_37026
Explanation: User Response:
TIB_37027
Explanation:
TIB Messages
365
User Response:
TIB_37028
Explanation: User Response:
TIB_38000
Explanation: User Response:
TIBCO writer failed to insert null value into field <field>, which can't take a null value.
You selected Not Null for the specified field in the target properties. From the Columns tab of the Edit Table properties for the target definition, clear the Not Null option for the field.
TIB_38001
Explanation: User Response:
TIBCO writer failed to initialize writer properties for the target instance <target>: <error message>.
The Integration Service could not initialize the writer properties for the specified target. The session failed. Check the additional error message for more information.
TIB_38002
Explanation: User Response:
TIBCO writer failed to initialize connection properties for the target instance <target>: <error message>.
An attribute in the application connection for the TIBCO target is invalid. The session failed. Check the additional error message for more information.
TIB_38003
Explanation: User Response:
TIBCO writer can't get connection information for the target instance <target>.
Internal error. Contact Informatica Global Customer Support.
TIB_38004
Explanation: User Response:
TIBCO writer initialization failed for the target instance <target>: <error message>.
The Integration Service could not initialize the target. The session failed. Check the additional error message for more information.
TIB_38007
Explanation: User Response:
TIBCO writer rejected the row because of the overflow error for field <field>.
Row error. Data overflow occurred in the specified field. Use a larger datatype for the output field. For example, use int64 instead of int32.
TIB_38008
Explanation: User Response:
TIB_38009
Explanation: User Response:
366
TIB_38010
Explanation: User Response:
SendSubject field cannot be connected when pre-registered listeners are specified for the writer.
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. 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
Explanation: User Response:
The target instance contains the datatype msg, which is incompatible with a TIB/Adapter SDK connection.
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. 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
Explanation:
Target instance contains the header field Time Limit, which is incompatible with a TIB/Adapter SDK connection.
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. Remove the link to the Time Limit port in the target definition.
User Response:
TIB_38014
Explanation:
Target instance contains the datatype ipaddr32 or ipport16, which is incompatible with a TIB/ Adapter SDK connection.
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. Use the datatype string for fields with ipaddr32 or ipport16 datatypes.
User Response:
TM Messages
TM_6004
Explanation: User Response:
TM_6018
User Response:
TM_6059
User Response: Explanation: User Response:
An error occurred updating the Sequence Generator transformation <transformation name> to the repository.
Review the Repository Service logs for more information about the error. Internal error. Contact Informatica Global Customer Support.
TM Messages
367
TM_6063
Explanation: User Response:
TM_6075
Explanation: User Response:
TM_6085
User Response:
TM_6094
Explanation:
TM_6109
Explanation: User Response:
Warning. The size of the DTM buffer allocated for each DTM is recommended not to exceed <number> bytes. The specified size of DTM buffer is <number> bytes.
The DTM buffer size exceeded the recommended size. The Integration Service started with the shared memory size you specified. If you want to change the memory size, stop the Integration Service, change the number of bytes to the specified size, and then restart the Integration Service.
TM_6154
Explanation: User Response:
TM_6157
Explanation: User Response:
TM_6159
Explanation: User Response:
368
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.
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. 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.
The stored procedure database uses a code page that is not supported by PowerCenter. 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
Explanation: User Response:
The session sort order <sort order name> is incompatible with the Integration Service code page <code page name>.
The specified sort order is incompatible with the Integration Service code page. 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
Explanation:
Cannot identify the unique relational connection or application connection that is used as $Source or $Target for a Lookup or Stored Procedure transformation.
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. In the session properties, enter a database connection for the $Source or $Target connection.
User Response:
TM_6193
Explanation:
User Response:
TM_6200
User Response:
The session log path exceeds limits of <session log path limit> characters <session log path>.
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_6202
Explanation: User Response:
DTM event. There was an error incrementing the log file number in the repository.
The repository was unable to update the log file number in the database. Verify that the database server and Repository Service are running.
TM Messages
369
TM_6223
User Response:
An internal error occurred while fetching the session log. The log attached to the post session email may be incomplete.
Contact Informatica Global Customer Support.
TM_6247
Explanation: User Response:
TM_6248
Explanation: User Response:
User <user name> does not have execute permission on the global object <object name>.
The user who started the session does not have execute permission on one of the connection objects used by the session. Verify that the user has permission on the object.
TM_6254
An error was encountered saving statistical information to the repository for the transformation <transformation name>, with group name <group> and partition ID <partition ID>.
There was an error sending statistical information to the repository. For example, the database connection may be broken. Review the Repository Service log for related messages.
TM_6255
Explanation: User Response:
An error was encountered saving statistical information to the repository for the transformation <transformation name> with partition ID <partition ID>.
There was an error sending statistical information to the repository. For example, the database connection may be broken. Review the Repository Service log for related messages.
TM_6264
Explanation: User Response:
The connection is not set in the Workflow Manager for the MQ Source Qualifier transformation <MQ Source Qualifier name> partition <partition number>.
The Integration Service cannot find the queue connection specified in the session properties. Assign a valid queue connection to the session.
TM_6279
Explanation: User Response:
The session instance <session instance name> encountered the following run-time validation error: <error message>.
The Integration Service could not run the session because it is invalid. Review the run-time error message.
TM_6288
Explanation: User Response:
TM_6289
Explanation: User Response:
370
TM_6294
Explanation:
The target load order has been changed. Revalidate the mapping <mapping name>.
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. Open the mapping and save it.
User Response:
TM_6316
Explanation: User Response: Explanation: User Response:
TM_6317
Explanation: User Response: Explanation: User Response:
The following database error occurred creating the recovery table <table name>: <database error message>.
The user name specified in the target database connection does not have table creation privileges on the target database. Grant table creation privileges to the database user name specified in the target database connection. The Integration Service could not create the recovery table due to a database error. Check the database error message to determine the cause of the error, and contact the database administrator.
TM_6318
Explanation: User Response:
The following database error occurred when preparing to fetch the target run ID from the recovery table <table name>: <database error message>.
The Integration Service could not retrieve information from the recovery table due to a database error. Check the database error message to determine the cause of the error, and contact the database administrator.
TM_6319
Explanation: User Response: Explanation: User Response:
The following database error occurred when fetching the target run ID from the recovery table <table name>: <database error message>.
The user name specified in the target database connection does not have permission to select information from the target database. Grant select privileges to the user name specified in the target database connection. The Integration Service could not retrieve information from the recovery table due to a database error. Check the database error message to determine the cause of the error, and contact the database administrator.
TM Messages
371
TM_6320
Explanation: User Response: Explanation: User Response:
The following database error occurred when inserting the target run ID into the recovery table <table name>:<database error message>.
The user name specified in the target database connection does not have permission to insert information into the PM_RECOVERY recovery table. Grant the database user name specified in the target database connection permission to insert data into the PM_RECOVERY recovery table. The Integration Service could not insert information into PM_RECOVERY due to a database error. Check the database error message for the cause of the error, and contact the database administrator.
TM_6321
Explanation: User Response:
The recovery table format is in version <version number>, while version 6.2 is expected.
The Integration Service cannot perform recovery because the recovery tables are not correctly formatted. 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
Explanation: User Response:
The following error occurred when generating a sequence ID: <database error message>.
The Integration Service could not initialize the PM_TGT_RUN_ID recovery table. 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
User Response:
The following database error occurred when committing the new sequence ID to the database: <database error message>.
Check the database error message for the cause of the error and contact the database administrator.
TM_6324
Explanation: User Response: Explanation: User Response:
The following database error occurred when preparing the UPDATE recovery statement: <database error message>.
The user specified in the target database connection does not have permission to access the recovery tables. Grant permission to access the recovery tables to the user name specified in the target database connection. The Integration Service could not access the recovery tables due to a database error. Check the database error message for the cause of the error and contact the database administrator.
TM_6325
Explanation: User Response: Explanation:
The following database error occurred when updating recovery information for the recovery table <table name>: <database error>.
The user name specified in the target database connection does not have permission to update the recovery table. Grant permission to access the recovery tables to the user name specified in the target database connection. The Integration Service could not update the recovery table due to a database error.
372
User Response:
Check the database error message for the cause of the error and contact the database administrator.
TM_6326
Explanation: User Response: Explanation: User Response:
The following database error occurred when deleting recovery information from the recovery table <table name>: <database error message>.
The user name specified in the target database connection does not have permission to delete information from the recovery table. Grant permission to delete information from the recovery tables to the user name specified in the target database connection. The Integration Service could not delete information from the recovery table due to a database error. Check the database error message for the cause of the error and contact the database administrator.
TM_6327
Explanation: User Response: Explanation: User Response:
The following database error occurred when resetting recovery information for the recovery table <table name>: <database error message>.
The user specified in the target database connection does not have permission to reset information in the recovery table. Grant permission to access, insert, and delete information in the recovery tables to the database user name specified in the target database connection. The Integration Service could not reset information in the recovery table due to a database error. Check the database error message for the cause of the error and contact the database administrator.
TM_6328
Explanation: User Response: Explanation: User Response:
The following database error occurred when fetching the partition count from the recovery table <table name>: <database error message>.
The user specified in the target database connection does not have permission to access the recovery table. Grant permission to access the recovery tables to the user name specified in the target database connection. The Integration Service could not access the recovery table due to a database error. Check the database error message for the cause of the error and contact the database administrator.
TM_6329
Explanation: User Response: Explanation: User Response:
The following database error occurred when fetching recovery information from the recovery table <table name>: <database error message>.
The user specified in the target database connection does not have permission to access the recovery table. Grant permission to access the recovery tables to the user name specified in the target database connection. The Integration Service could not access the recovery table due to a database error. Check the database error message for the cause of the error and contact the database administrator.
TM Messages
373
TM_6330
User Response:
TM_6331
User Response:
TM_6332
User Response:
An error occurred deleting information from the recovery tables for the target <target>.
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
User Response:
An error occurred initializing the recovery session because the recovery information for the target <target> was not found.
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.
TM_6341
User Response:
A database error occurred updating the recovery tables. The session updated <number of records> recovery records but expected to update one row.
Check the database error message log for possible causes of the error, and contact the database administrator.
TM_6342
User Response:
An error occurred updating information in the recovery tables for the target <target name>.
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
User Response:
Session recovery is not possible because the session is not enabled for recovery.
Enable the session for recovery. While enabled for recovery, the session must run normally and fail before you can perform recovery.
TM_6345
Explanation: User Response:
The connection object <connection name> is not a valid database partition connection type.
The Integration Service failed the session because it cannot load to the target type using database partitioning. Use pass-through partitioning for targets that do not support database partitioning.
TM_6349
User Response:
Session recovery is not possible because the session is also configured to perform a test load.
To perform recovery, disable test load in the session properties.
374
TM_6376
User Response:
TM_6687
Explanation: User Response:
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.
You tried to run a session on a 32-bit Integration Service, but the DTM buffer size is too large. Decrease the DTM buffer size or run the session on a 64-bit Integration Service.
TM_6698
Explanation: User Response:
TM_6700
Explanation: User Response:
The following error was encountered accessing the file <file name> for error logging: <error message>.
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. Review the error message, and check the permissions on the specified file.
TM_6701
User Response:
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.
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.
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. Configure the transformation instances to have the same number of partitions.
Explanation:
User Response:
TM_6713
Explanation: User Response:
Concurrent sources with the same transactional requirements must have consecutive execution order.
When a session runs in change or real-time mode, the execution of the target load order groups must be consecutive. To ensure consecutive execution of target load order groups, set the target load order in the Designer.
TM_6765
User Response:
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.
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.
Explanation:
TM Messages
375
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>.
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. 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.
Explanation:
User Response:
TM_6777
User Response:
TM_6788
Explanation:
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.
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. Verify that the PowerCenter Services user has write permission for the PowerCenter Services installation directory.
User Response:
TM_6795
User Response:
The Repository Service marked the session as impacted, and the Integration Service is not configured to run impacted sessions.
Validate the session or configure the Integration Service to run impacted sessions.
TM_6796
Explanation: User Response:
An error occurred expanding the owner name <owner name> for the transformation <transformation name>.
The Integration Service cannot expand a parameter or variable in the table owner name or table name prefix. 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 mapping variable to a text string in the parameter file. Internal error. Contact Informatica Global Customer Support.
TM_6797
User Response:
An error occurred expanding a parameter or variable in the environment SQL <SQL text> for the connection object <connection name>.
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 mapping variable to a text string in the parameter file. Internal error.
Explanation:
376
User Response:
TM_6798
User Response:
An error occurred expanding a parameter or variable in the table name prefix <prefix> for error logs.
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 mapping variable to a text string in the parameter file. Internal error. Contact Informatica Global Customer Support.
TM_6828
Explanation: User Response:
TM_6829
Explanation: User Response:
The Integration Service encountered the following error while resetting recovery table <table name>: Error <Error>.
The Integration Service could not reset a recovery table because it encountered an error. For example, the database connection may be broken. Review the session log for more information.
TM_6844
Explanation: User Response:
The variable <variable name> used in pre-session variable assignment is overridden in the parameter file. The variable assignment will be ignored.
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. 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
User Response:
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.
Verify that the variable has not been deleted or renamed.
TM_6848
User Response:
TM_6849
User Response:
Unable to resolve variable <variable name> as a mapping parameter, mapping variable, session parameter or predefined variable.
Verify that the variable has not been deleted or renamed.
TM_6850
Explanation: User Response:
An error was encountered setting the value from variable <variable name> to value for variable <variable name>.
The session contains a pre- or post-session variable assignment statement, but the Integration Service could not perform the variable assignment. Verify that the parameters or variables in the assignment statement exist and that the names are spelled correctly.
TM Messages
377
TM_6851
User Response:
TM_6956
User Response:
An error was encountered starting a new workflow instance because the number of workflow instances is at the configured limit.
Start the workflow instance after one of the instances completes running.
TM_6957
User Response:
The workflow failed because it persists the same mapping variables as another workflow instance that is running concurrently.
To persist mapping variables for concurrent workflows, configure different workflow instance names and parameters.
TM_6958
User Response:
The workflow failed to start because a workflow with the same instance name is already running.
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.
TM_6960
This session requires <number of bytes> bytes of memory to run, but with deadlock recovery and high availability off it would only need <number of bytes>. If the session fails because your computer does not have enough memory, try it again with both of these options off.
The DTM buffer size is set to Auto and Session Retry On Deadlock is enabled. The Integration Service displays the amount of memory that is required to run the session in the session log. If the session fails, disable either Session Retry On Deadlock or the high availability option.
Explanation:
User Response:
TT Messages
TT_11009
User Response:
Overflow error. The Sequence Generator transformation has reached the end of the configured end value.
Change the end value or cycle the sequence.
TT_11013
Explanation: User Response: Explanation: User Response:
TT_11014
User Response: Explanation:
378
User Response:
TT_11019
Explanation: User Response:
There is an error in the port <port name>. The default value for the port is set to: ERROR <error message>.
The named port is configured to generate the named message upon error. You can review the dropped row in the session log.
TT_11020
Explanation: User Response:
There is an error in the port <port name>. The default value for the port is set to: ABORT <error message>.
The port is configured to abort the session upon error. If you do not want to abort the session when the port contains an error, change the default value.
TT_11021
User Response:
An error occurred moving data from the transformation <transformation name> to the transformation <transformation name>. The row was dropped.
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
User Response:
An error occurred converting data in the port <port name>. The row was dropped.
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
Explanation: User Response:
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.
Change the lookup override query to contain characters included in the lookup database connection code page.
User Response:
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.
The lookup query contains one or more characters that are not encoded in the lookup database code page. 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. The lookup database uses a code page that is not supported by Informatica. Select a code page for the lookup database that is supported by Informatica and contains encoding for the lookup data character set.
TT Messages
379
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.
The stored procedure name contains one or more characters that are not encoded in the stored procedure database code page. 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. The stored procedure database uses a code page that is not supported by Informatica. 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.
The field name of a stored procedure contains one or more characters that are not encoded in the stored procedure database code page. 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. The stored procedure database uses a code page that is not supported by Informatica. 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_11090
Explanation:
The control expression of the Transaction Control transformation <transformation name> is evaluated to NULL.
The transaction control expression in a Transaction Control transformation evaluated to a null value. When the transaction control expression evaluates to any value other than continue, commit, or rollback, the Integration Service fails the session. Edit the transaction control expression so that it does not evaluate to NULL.
User Response:
TT_11091
Explanation:
The control expression of the Transaction Control transformation <transformation name> is evaluated to <evaluated value>.
The transaction control expression in a Transaction Control transformation evaluated to an invalid value. When the transaction control expression evaluates to any value other than continue, commit, or rollback, the Integration Service fails the session. Edit the transaction control expression so that it does not evaluate to an invalid value.
User Response:
TT_11100
Explanation:
The Joiner transformation <transformation name> input is not sorted. The row key value is <key value>.
The named Joiner transformation is configured to use sorted input, but the Joiner transformation received unsorted data.
380
User Response:
Configure the Joiner transformation to use unsorted input. 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
User Response:
The cache directory configured for the transformation <transformation name> is empty or not valid.
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.
The IDN license restricts the number of rows you can process in a group. Decrease the number of rows in the group or get a different license from Informatica.
TT_11134
Explanation:
The lookup cache file with the named prefix <prefix name> used by the Lookup transformation <Lookup transformation name> cannot be reused.
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
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. 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
Explanation:
The transformation <transformation name> returned a row error status on receiving an input row on group <group>.
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. 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.
User Response:
TT Messages
381
TT_11144
Explanation: User Response:
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>.
The source type for the Lookup transformation was changed after the Integration Service saved the cache. Recache the lookup source, or change the source type to the previous type.
TT_11145
Explanation: User Response:
The cache for the Lookup transformation <transformation name> indicates that the source file is <file name>, but the source file specified is <file name>.
The source file name was changed after the Integration saved the lookup cache. Recache the lookup source, or change the lookup file name to the previous name.
TT_11146
Explanation:
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.
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. Recache the lookup source, or change the lookup source file type in the session properties.
User Response:
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>.
The cache file name prefix matches for each Lookup transformation, but the lookup sources have different file names. 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.
Configure the session with the same lookup source file type for each Lookup transformation sharing the cache.
User Response:
TT_11149
Explanation: User Response:
The Lookup transformation <Lookup transformation name> has an illegal file name <file name>.
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. In the session properties, verify the file name and directory of the lookup file source.
TT_11152
Explanation: User Response:
TT_11158
Explanation:
An error occurred reading the lookup source for the Lookup transformation <transformation name>.
The Integration Service encountered errors while reading the lookup source.
382
User Response:
TT_11161
User Response:
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.
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
Explanation: User Response:
You cannot connect the transformation <transformation name> downstream from a Sequence Generator transformation.
You connected a Sequence Generator transformation upstream from a Custom transformation or a transformation developed using the Custom transformation. Update the mapping.
TT_11168
User Response:
The code page specified for transformation <transformation name> is not valid for the file <file name>.
Specify a valid code page. The code page should specify the proper locale for the lookup source file.
TT_11169
User Response:
The transformation <transformation name> code page <code page ID> is not found.
Specify a valid code page. The code page should specify the proper locale for the lookup source file.
TT_11170
Explanation: User Response:
An error occurred processing transformation <transformation name> and creating locale from the code page <code page name> for file <file name>.
The code page you specified is not valid. 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.
You can optimize performance by connecting only the NEXTVAL port in a mapping.
User Response:
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.
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. Edit the Lookup transformation and use the same precision for both ports.
Explanation:
User Response:
TT_11180
User Response:
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>.
Verify that both lookup transformations use the same multiple match policy.
TT Messages
383
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.
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. To improve performance, review the SQL and fix the SQL to retrieve data in the sort order that the Integration Service expects. The sort order settings for the database server and Integration Service do not match. To improve performance, configure a consistent sort order for the database server and the Integration Service.
Explanation:
TT_11204
User Response:
An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the cache file name prefix <prefix>.
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 mapping variable to a text string in the parameter file. Internal error. Contact Informatica Global Customer Support.
TT_11209
Explanation: User Response:
The upgrade process failed to complete. The Sequence Generator transformation has an invalid datatype.
The mapping contains a Sequence Generator transformation in which the datatype for the NEXTVAL or CURRVAL output port is not Bigint. Import the mapping again or re-create the Sequence Generator transformation.
TT_11210
Explanation: User Response:
An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the lookup table name <lookup table name>.
The session contains a mapplet variable or parameter to define a lookup table name. The Integration Service failed to expand the parameter or variable. 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.
384
CHAPTER 20
UDT Messages
UDT_50000
Explanation: User Response:
UDT_50001
Explanation:
User Response:
UDT_50002
Explanation: User Response:
UDT_50003
Explanation:
User Response:
385
UDT_50004
Explanation:
User Response:
UDT_50007
Explanation: User Response:
UDT_50008
Explanation: User Response:
UDT_50010
Explanation: User Response:
Unstructured Data transformation can only have one default output port.
The Unstructured Data transformation must have only one OutputBuffer port. 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
Explanation: User Response:
Unstructured Data transformation can only have one default input port.
The Unstructured Data transformation must have only one InputBuffer port. 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
Explanation:
There must be two default input ports in the Unstructured Data transformation.
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. 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.
User Response:
UDT_50020
Explanation: User Response:
UDT_50021
Explanation: User Response:
386
UDT_50022
Explanation: User Response:
UDT_50023
Explanation: User Response:
UDT_50024
Explanation: User Response:
UDT_50025
Explanation: User Response:
UDT_50026
Explanation:
Data Transformation port <port name> not found in the group <group>.
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. 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.
User Response:
UDT_50027
Explanation:
Data Transformation group <group> not found in the Unstructured Data transformation.
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. 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.
User Response:
UDT_50028
Explanation: User Response:
UDT Messages
387
UDT_50029
Explanation: User Response:
UDT_50030
Explanation: User Response:
UDT_50031
Explanation: User Response:
UDT_50033
Explanation:
User Response:
UDT_50034
Explanation:
'Service Name' cannot be left blank in the transformation. Enter a service name in the UDT Settings tab.
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. 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.
User Response:
UM Messages
UM_10000
Explanation: User Response:
UM_10001
Explanation:
388
User Response:
Use infasetup to restore the configuration metadata for the domain from a backup XML file.
UM_10002
Explanation: User Response:
UM_10004
Explanation: User Response:
The Service Manager could not find the user <user name> belonging to <security domain name> security domain.
The user does not exist in the security domain. Enter a valid user name for the security domain.
UM_10013
Explanation: User Response:
The group <group> belonging to <security domain name> contains a user <user name> belonging to <security domain name> that is not defined in the domain.
The user being added or removed from a group does not exist in the PowerCenter domain. Enter a valid user name to be added to or removed from the group. Or, create the user before adding it to a group.
UM_10017
Explanation: User Response:
UM_10018
Explanation: User Response:
UM_10019
Explanation: User Response:
UM_10020
Explanation: User Response:
The user <user name> belonging to <security domain name> was not associated with the node <node name>.
The user specified in the node configuration does not match the domain configuration. Either modify the user in the domain node or redefine the node with the same user as the domain node.
UM_10021
Explanation: User Response: Explanation: User Response:
The host name for node <node name> is inconsistent between node configuration and domain configuration.
The node configuration is incorrect. Redefine the node. The node is defined twice. Create a node with a different name.
UM Messages
389
UM_10022
Explanation: User Response: Explanation: User Response:
The port number for node <node name> is inconsistent between node configuration and domain configuration.
The node configuration is incorrect. Redefine the node. The node is defined twice. Create a node with a different name.
UM_10023
Explanation: User Response:
The gateway setting for node <node name> is inconsistent between node configuration and domain configuration.
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. 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
Explanation: User Response:
The Service Manager cannot encrypt the credential because the characters in the user name, password, or domain name are not UTF-8 compliant.
The user name, password, or domain name contain characters that are not UTF-8 compliant. Ensure that the user name, password, and domain name contain characters that are UTF-8 compliant.
UM_10025
Explanation: User Response:
The Service Manager could not find the group <group> belonging to <security domain name> security domain.
The group does not exist in the security domain. Enter a valid group name for the security domain.
UM_10029
Explanation: User Response: Explanation: User Response: Explanation: User Response:
UM_10032
Explanation:
The Service Manager could not load privileges from the service <service name>.
Same as UM_10029.
UM_10034
Explanation: User Response:
The Service Manager could not authenticate user <user name> in security domain <security domain name> with error <error message>.
The Service Manager could not authenticate the user. Check the additional error message for more information.
390
UM_10040
Explanation: User Response:
The privilege <privilege name> does not exist for service <service name>.
The privilege does not exist for the domain or application service. Enter a valid privilege for the domain or application service.
UM_10041
Explanation: User Response:
The security domain <security domain name> is synchronizing with the LDAP server. Wait until synchronization has completed before accessing.
The Service Manager is synchronizing the list of users and groups in the security domain with the list of users and groups in the LDAP directory service. Access the security domain when synchronization is complete.
UM_10042
Explanation: User Response:
The privilege does not exist for privilege path <privilege path>.
The privilege does not exist in the privilege path. Enter a valid privilege name and privilege path for the domain or application service.
UM_10043
Explanation: User Response:
UM_10046
Explanation: User Response:
The imported group <group> references a user <user name> in security domain <security domain name> that does not exist in the domain.
The imported XML file is invalid. Import the users and groups from a new XML file. Do not edit the XML file before importing.
UM_10053
Explanation: User Response:
Unable to create security domain <security domain name>. Security domain <security domain name> is reserved for internal use.
You cannot create an LDAP security domain named native. Enter a different name for the LDAP security domain.
UM_10059
Explanation: User Response:
UM_10060
Explanation: User Response:
Error querying users from LDAP Service with error <error message>.
The Service Manager cannot import users from the LDAP directory service. Review the error message from the LDAP directory service.
UM_10061
Explanation: User Response:
Error querying groups from LDAP Service with error <error message>.
The Service Manager cannot import groups from the LDAP directory service. Review the error message from the LDAP directory service.
UM_10082
Explanation:
The Service Manager failed to add users to service <service name> with error <error message>.
The Service Manager cannot communicate with the application service.
UM Messages
391
User Response:
UM_10083
Explanation:
The Service Manager failed to add groups to service <service name> with error <error message>.
Same as UM_10082.
UM_10084
Explanation:
The Service Manager failed to remove users from service <service name> with error <error message>.
Same as UM_10082.
UM_10085
Explanation:
The Service Manager failed to remove groups from service <service name> with error <error message>.
Same as UM_10082.
UM_10087
Explanation:
The Service Manager failed to synchronize users and groups from service <service name> with error <error message>.
Same as UM_10082.
UM_10088
Explanation: User Response:
The Service Manager failed to add users to service <service name>. The service users and groups are not synchronized with the domain.
The users and groups in the application service repository are not synchronized with the users and groups in the domain configuration database. 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
Explanation:
The Service Manager failed to add groups to service <service name>. The service users and groups are not synchronized with the domain.
Same as UM_10088.
UM_10090
Explanation:
The Service Manager failed to remove users from service <service name>. The service users and groups are not synchronized with the domain.
Same as UM_10088.
UM_10091
Explanation:
The Service Manager failed to remove groups from service <service name>. The service users and groups are not synchronized with the domain.
Same as UM_10088.
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.
Same as UM_10088.
Explanation:
UM_10093
Explanation:
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>.
Same as UM_10082.
392
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.
Same as UM_10088.
Explanation:
UM_10095
Explanation:
The Service Manager failed to update privileges for group <group> in security domain <security domain name> for service <service name> with error <error message>.
Same as UM_10082.
UM_10096
Explanation:
Unable to perform the requested operation because this would violate the maximum number of licensed Metadata Manager users: [<number of users]
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. 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.
User Response:
UM_10097
Explanation:
Unable to perform the requested operation because groups may not have Metadata Manager privileges or roles when Metadata Manager user count enforcement is enabled.
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. None.
User Response:
UM_10098
Explanation:
Unable to perform the requested operation because Reporting Service <service name> does not support value of username@securitydomain <name> greater than 80 characters.
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. 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.
User Response:
UM_10099
Explanation: User Response:
User <user name> in security domain <security domain name> cannot disable own account.
You cannot disable the own user account. Select another user account to disable. Log in as another user to disable the own user account.
UM_100100
Explanation:
The Service Manager failed to authenticate user <user name> belonging to <security domain name>. The password was not specified.
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. Log in using a password.
User Response:
UM Messages
393
UM_100101
Explanation: User Response:
The nonce value provided for user <user name> has already been used.
The nonce value provided has been used but has not yet expired. Resend the request with a new nonce value.
UM_100102
Explanation: User Response:
The created value provided for user <user name> was not used in its valid timeframe.
The request to use a created value was made too long after the value was created. A created value must be used before it expires. Resend the request with a new created value.
394
CHAPTER 21
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>.
The initial value of the mapping variable you specified in the Designer has a circular dependency when referencing another variable. 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.
VAR_27002
Explanation: User Response:
VAR_27003
Explanation: User Response:
VAR_27004
Explanation: User Response:
Internal error: aggregation operation requested for data with different datatypes.
Internal error. Contact Informatica Global Customer Support.
VAR_27005
Explanation: User Response:
Internal error: cannot perform COUNT operation on string or time datatype values.
The mapping variable COUNT value has a mismatched datatype. Contact Informatica Global Customer Support.
395
VAR_27010
Explanation: User Response:
VAR_27017
Explanation: User Response:
VAR_27018
Explanation: User Response:
Error: cannot find mapping parameter or variable of name <variable name> in transformation <transformation name>.
The Integration Service is referencing an undeclared parameter or variable in an expression. Declare the parameter or variable in the Designer.
VAR_27026
Explanation: User Response:
VAR_27030
Explanation: User Response:
VAR_27032
Explanation: User Response:
Error: initial value for count aggregate type mapping variable: <name> cannot be less than zero.
The initial value for an aggregate type mapping variable cannot be negative. Change the value to a positive integer. If the initial value is defined in a parameter file, edit the parameter file associated with the session. 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.
VAR_27033
Explanation: User Response:
VAR_27034
Explanation: User Response:
Internal Error: cannot resolve data value for server variable <name>.
Internal error. Contact Informatica Global Customer Support.
VAR_27035
Explanation: User Response:
Internal Error: cannot resolve integer numeric data value for server variable <name ($PMSession error threshold, $PMSession log count)>.
Internal error. Contact Informatica Global Customer Support.
396
VAR_27036
Explanation: User Response:
Internal Error: cannot resolve string data value for server variable <name>.
Internal error. Contact Informatica Global Customer Support.
VAR_27037
Explanation: User Response:
Internal error: copy operation requested for data with different datatypes.
Internal error. Contact Informatica Global Customer Support.
VAR_27038
Explanation: User Response:
Error: <service process variable>: <file path type>, for file or directory path, cannot reference to <variable>: <name> which is not for file or directory path.
The service process variable cannot reference another variable that does not follow a file or directory path type. Change the variable to a file or directory path type variable.
VAR_27039
Explanation: User Response:
Error: cannot reference to <variable>: <file path type> which is not for file or directory path.
The service process variable cannot reference another variable with a file or directory path. Change the variable from a file or directory path type variable to an original variable name.
VAR_27040
Explanation: User Response:
Error: failed to delete existing persisted mapping variable value(s) for session <session name> from the repository.
Internal error. The Integration Service cannot delete the mapping variable value from the repository. Contact Informatica Global Customer Support.
VAR_27041
Explanation: User Response:
Error: failed to persist mapping variable value(s) for session <session name> into the repository.
Internal error. The Integration Service cannot insert the mapping variable value from the repository. Contact Informatica Global Customer Support.
VAR_27042
Explanation: User Response:
Error in getting the final value for mapping variable <name>. Skip saving the persisted value for this variable.
Internal error. The Integration Service could not resolve the final mapping variable value to save it. Contact Informatica Global Customer Support.
VAR_27043
Explanation: User Response:
VAR_27044
Explanation:
VAR Messages
397
User Response:
Look at the data set. Make sure the mapping variable value is not null.
VAR_27046
Explanation: User Response:
Error in parsing last saved timestamp <date/time value> for mapping variable <name>. Ignoring the persisted value in repository.
Internal error. The Integration Service ignored the timestamped persisted value because the timestamp of the variable is invalid in the repository. Contact Informatica Global Customer Support.
VAR_27047
Explanation: User Response:
Error in parsing last saved timestamp <date/time value> for persisted value of mapping variable <name>. Ignore the persisted value in repository.
Internal error. The Integration Service ignored the timestamped persisted value because the timestamp of the persisted value is invalid in the repository. Contact Informatica Global Customer Support.
VAR_27053
Explanation: User Response:
VAR_27054
Explanation: User Response:
VAR_27055
Explanation: User Response:
VAR_27056
Explanation: User Response:
VAR_27057
Explanation:
398
User Response:
VAR_27061
Explanation: User Response:
Error: cannot find <workflow/worklet> variable of name <name> referenced in <workflow/ worklet> <name>.
The workflow or worklet expression contains a variable that is not declared. You may have mistyped the variable name in the expression. Check the variable name in the workflow or worklet expression.
VAR_27062
Explanation: User Response: Explanation:
Warning! Cannot find section for <workflow/worklet> <name> and folder <name> in parameter file <name>.
The parameter file does not contain a section for the named workflow or worklet. Check the parameter file. Create a section for the workflow or worklet, or correct the folder, workflow, or worklet name in the parameter file. 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. 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.
User Response:
VAR_27064
Explanation: User Response:
Error: failed to persist <workflow/worklet> variable value(s) for <name> into the repository.
Internal error. The Integration Service failed to write a persistent workflow or worklet variable value to the repository. Contact Informatica Global Customer Support.
VAR_27067
Explanation: User Response:
Error in parsing last saved timestamp <date/time value> for <workflow/worklet> variable <name>. Ignore the persisted value in the repository.
Internal error. The Integration Service failed to pass the timestamp value for the named workflow or worklet variable. Contact Informatica Global Customer Support.
VAR_27068
Explanation: User Response:
Error in parsing last saved timestamp <date/time value> for persisted value of <workflow/ worklet> variable <name>. Ignore the persisted value in the repository.
Internal error. The Integration Service failed to pass the timestamp value for the persistent value of the named workflow or worklet variable. Contact Informatica Global Customer Support.
VAR_27069
Explanation: User Response:
Error in getting the final value for workflow variable <name>. Skip updating the persisted value for this variable.
Internal error. Contact Informatica Global Customer Support.
VAR_27072
Explanation:
Error: illegal to set the override value for pre-defined workflow variable <name>.
You are trying to override the value of a pre-defined workflow variable in a parameter file. This is not allowed.
VAR Messages
399
User Response:
Either remove the variable from the parameter file or use a user-defined workflow variable in the expression.
VAR_27073
Explanation: User Response:
VAR_27075
Explanation: User Response:
Error: cannot reference to <variable/parameter type> <variable/parameter name> whose value is NULL.
Internal error. Contact Informatica Global Customer Support.
VAR_27079
Explanation: User Response:
Warning: <variable type>: <variable name>, NULL override value not valid. The override value is set to empty string.
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. Check the value of the variable in the parameter file. Set it to a value other than NULL.
VAR_27086
Explanation: User Response:
Cannot find specified parameter file <file name> for <workflow/session name>.
The Integration Service cannot find the parameter file. 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
Explanation: User Response:
Error: Failed to read line from parameter file <file name> for <workflow/session name>.
The Integration Service cannot read the parameter file. Verify that the user configured to start Informatica Services has read permission on the parameter file directory. Verify that the parameter file is valid.
400
CHAPTER 22
WEBM Messages
WEBM_1001
Explanation: User Response:
WEBM_1002
Explanation: User Response:
WEBM_1003
Explanation: User Response:
WEBM_1004
Explanation: User Response:
Preserve Client State option is set, but no client ID is given in application connection <application connection name>.
In the specified webMethods application connection, you selected the Preserve Client State option. However, you did not specify a client ID. Set a value for the client ID if you select the Preserve Client State option.
WEBM_1006
Explanation: User Response:
401
WEBM_2001
Explanation: User Response:
WEBM_2002
Explanation: User Response:
WEBM_2003
Explanation: User Response:
WEBM_2004
Explanation:
Client Group does not have the permission to subscribe to document type <document type>.
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. 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.
User Response:
WEBM_2005
Explanation:
Source <source name> is configured to receive messages, but no client ID is given in application connection <application connection name>.
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. You can configure a value for client ID in the webMethods application connection properties.
User Response:
WEBM_2010
Explanation: User Response:
Reader received and rejected a document with a mismatched document type <document type>: <document>.
The Integration Service read a document that does not match the document type in the source definition. The document is rejected. None.
WEBM_2011
Explanation: User Response:
WEBM_2012
Explanation: User Response:
402
WEBM_2013
Explanation:
The data retrieved from the recovery cache is not a valid webMethods document.
During a recovery session, the Integration Service read data from the recovery cache that is not a webMethods document. The recovery cache may have been modified. As a result, the recovery session failed. Rerun the session.
User Response:
WEBM_2014
Explanation: User Response:
WEBM_2015
Explanation: User Response:
WEBM_2016
Explanation: User Response:
WEBM_2017
Explanation: User Response:
WEBM_3001
Explanation: User Response:
WEBM_3002
Explanation: User Response:
WEBM_3003
Explanation: User Response:
WEBM_3005
Explanation:
Client Group does not have the permission to publish document type <document type>.
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. 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.
User Response:
WEBM Messages
403
WRT Messages
WRT_8000
Explanation: User Response:
WRT_8001
Explanation: User Response:
WRT_8004
Explanation: User Response: Explanation: User Response: Explanation: User Response:
WRT_8012
Explanation: User Response:
WRT_8019
Explanation: User Response:
WRT_8020
Explanation: User Response:
WRT_8023
Explanation: User Response:
404
WRT_8028
Explanation: User Response:
Error <error number> forking <loader type> external loader process for target <target name>.
The external loader process could not be forked. Look up the error code in errno.h on UNIX or winerror.h on Windows.
WRT_8031
Explanation: User Response:
WRT_8032
Explanation:
User Response:
Make sure the loader information is entered correctly. In Oracle, verify that the loader executable name entered is correct, and that the executable directory is in the path. Make sure the user name, password and connect string are correct. Make sure all fields contain a value when setting up an external loader connection. Check the permissions on the directory where the output file is to be generated.
WRT_8046
Explanation: User Response:
Error <Windows system error number> checking for completion of external loader <handle=process ID>.
The Windows system encountered an error while attempting to check for external loader completion. Look up the Windows system error code and/or check the Windows system log.
WRT_8047
Explanation: User Response:
Error: External loader process <process ID> exited with error <exit loader error number>.
The external loader process exited with an error. Look up the error code in the database external loader documentation.
WRT_8048
Explanation: User Response:
Error <Windows system error number> retrieving the termination status for completed external loader [handle=<process ID>].
The Windows system encountered an error while attempting to retrieve the exit code for the external loader. Look up the Windows system error code and/or check the Windows system log.
WRT_8049
Explanation: User Response:
Error: External loader process <process ID> exited due to receipt of signal <UNIX signal number>.
External loader on UNIX exited due to receipt of a UNIX signal. Look up the UNIX signal number in signal.h, which is in /usr/include/sys/signal.h.
WRT Messages
405
WRT_8053
Explanation: User Response:
Warning! Error executing pre-load stored procedures. Session <session name> user name <user name> Error <database error message>.
You ran a session with a pre-load stored procedure that failed to execute. Contact the database administrator.
WRT_8058
Explanation: User Response:
Error <system error number> opening session bad (reject) file <bad file name>.
During the initialization of a session, the Integration Service failed to open the reject file specified due to an operating system error. 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
Explanation: User Response:
WRT_8060
Explanation: User Response:
Writer initialization failed [Failed to get external loader information]. Writer terminating.
Internal error. You may have repository inconsistencies. Contact Informatica Global Customer Support.
WRT_8062
Explanation: User Response:
Writer initialization failed [Failed to generate external loader control file]. Writer terminating.
The session failed during generation of an external loader control file. Check preceding error messages to see the cause for the error.
WRT_8063
Explanation: User Response: Explanation: User Response:
WRT_8064
Explanation: User Response:
Error <system error number> opening session output file <output file name>.
During the initialization of a session, the Integration Service failed to open the output file specified due to an operating system error. 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.
406
WRT_8065
Explanation:
User Response:
WRT_8066
Explanation: User Response:
Error <system error message> opening session log file <log file name>.
Operating system error. Contact the system administrator.
WRT_8067
Explanation: User Response:
WRT_8068
Explanation: User Response:
WRT_8070
Explanation: User Response:
WRT_8071
Explanation: User Response:
Writer initialization failed. [Total no. of load targets from all pipelines <load targets> do not match with the no. of load targets in the mapping <mapping name>.] Writer terminating.
Internal error. Contact Informatica Global Customer Support.
WRT_8072
Explanation: User Response:
WRT_8073
Explanation: User Response:
WRT_8074
Explanation: User Response:
WRT Messages
407
WRT_8075
Explanation: User Response:
Writer initialization failed [Error creating truncate table order]. Writer terminating.
Internal error. The repository may have inconsistencies. Contact Informatica Global Customer Support.
WRT_8076
Explanation: User Response:
WRT_8077
Explanation: User Response:
WRT_8079
Explanation: User Response:
WRT_8080
Explanation: User Response:
Writer run terminated. [Error loading data and error threshold reached: no data committed].
The Integration Service has reached the error threshold configured in the session properties. Eliminate the errors in the data. Set the error threshold to zero.
WRT_8081
Explanation: User Response:
Writer run terminated. Error in loading data to target table <target instance name>.
Internal error. Check preceding error messages to see the cause for the error.
WRT_8082
Explanation: User Response:
WRT_8085
Explanation: User Response:
WRT_8086
Explanation: User Response:
WRT_8088
Explanation: User Response:
408
WRT_8091
Explanation: User Response:
WRT_8092
Explanation: User Response:
Error truncating target table <table name>. Error preparing truncate target table query: <table query>.
Database error. Contact the database administrator.
WRT_8095
Explanation: User Response: Explanation: User Response:
Error <system error number> forking isql external loader process for target <target name>.
You might be low on system resources. Contact the system administrator. You might have encountered a database configuration error. Contact the database administrator.
WRT_8096
Explanation: User Response:
WRT_8097
Explanation: User Response:
WRT_8098
Explanation: User Response:
External loader error. Error executing external loader process: [No such file or directory] errno = [2].
The Integration Service could not run the external loader because the external loader is not included in the system path. Edit the system path to include the external loader executable.
WRT_8100
Explanation: User Response:
WRT_8109
Explanation: User Response:
WRT_8110
Explanation: User Response:
BW Statement Init.
The Integration Service failed to initialize the InfoSource. Check that the Integration Service meets the minimum system requirements.
WRT Messages
409
WRT_8111
Explanation: User Response:
SAPSendDone.
The session failed to delete a line from an SAP internal table. Reschedule the SAP NetWeaver BI workflow.
WRT_8116
Explanation: User Response:
ERROR: Target table <target table name> has no keys specified. Row # <row ID> in bad file.
You attempted to perform an UPDATE or a DELETE. These commands require a primary key be defined on the target table. Go to the target definition and define a primary key. Do not use UPDATE or DELETE on the target table.
WRT_8117
Explanation: User Response:
ERROR: Target table <table name> does not allow INSERT. Row # <row ID> in bad file.
You attempted to INSERT rows into the target table. However, you might not have been granted rights to INSERT into the specified table. Contact the database administrator.
WRT_8118
Explanation: User Response:
ERROR: Target table <table name> does not allow UPDATE. Row # <row ID> in bad file.
You attempted to UPDATE rows into the target table. However, you might not have been granted rights to UPDATE into the specified table. Contact the database administrator.
WRT_8119
Explanation: User Response:
ERROR: Target table <table name> does not allow DELETE. Row # <row ID> in bad file.
You attempted to DELETE rows from the target table. However, you might not have the rights to DELETE from the specified table. Contact the database administrator.
WRT_8120
Explanation: User Response:
ERROR: Invalid row type for target table <table name>. Row # <row ID> in bad file.
Internal error. Contact Informatica Global Customer Support.
WRT_8123
Explanation: User Response:
Failed to prepare target table load. Database error: <database error number>.
Database error. Contact the database administrator.
WRT_8132
Explanation: User Response:
WRT_8136
Explanation: User Response:
WRT_8150
Explanation:
410
User Response:
WRT_8151
Explanation: User Response:
WRT_8152
Explanation: User Response:
WRT_8156
Explanation: User Response:
WRT_8157
Explanation: User Response:
Field <field name> of the output file <file name> is not wide enough to fit at least one specified NULL character.
You specified a multibyte null character and the target field does not contain enough remaining bytes for one null character. Specify a single byte null character. Increase the target column size in the Designer.
WRT_8171
Explanation: User Response:
Cannot locate CreateWrtTargetInstance function in the <library file name> shared library.
The DLL loaded for the specified target does not contain a function called CreateWrtTargetInstance. Make sure this is the correct DLL.
WRT_8172
Explanation: User Response:
WRT_8173
Explanation: User Response:
Conversion from UNICODE failed - not all the characters were converted.
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. Contact Informatica Global Customer Support.
WRT_8174
Explanation: User Response:
Error while flushing the buffer to output file <output files name>. Error message is <error message>, data buffer <buffer>.
There was an operating system input/output error trying to output into target file. Check that the output file is not locked and has the correct user permissions. Make sure the system has enough disk space.
WRT Messages
411
WRT_8175
Explanation: User Response:
Field separator string for file <file name> contains non-ASCII characters <Unicode characters>.
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. Change the Integration Service to UNICODE data movement mode or change the field separator string to be ASCII-only.
WRT_8176
Explanation: User Response:
NULL character for file <file name> is not ASCII <Unicode character>.
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. Change the Integration Service to UNICODE data movement mode or change the null character to an ASCII character.
WRT_8178
Explanation: User Response:
WRT_8179
Explanation: User Response:
Unknown error occurred while trying to close output file <file name>.
Operating system input/output error occurred when closing the output target file. Check that the file is not locked, is accessible, and has the correct permissions. Check that there is sufficient disk space.
WRT_8180
Explanation: User Response:
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.
412
WRT_8181
Explanation: User Response:
Specified locale <locale name> for the file <output file name> is not valid for NULL character <character>.
The null character you specified does not exist in the target code page. 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
Explanation: User Response:
WRT_8184
Explanation: User Response:
WARNING: The output codepage specified for the target file <target file name> is not ASCIIbased, whereas the Informatica Server is running in ASCII mode.
The Integration Service is running in ASCII data movement mode, but the code page you specified for the target is not ASCII-based. Change the Integration Service data movement mode to Unicode and run the session again.
WRT_8185
Explanation: User Response:
WRT_8186
Explanation: User Response:
WRT_8187
Explanation: User Response:
Error resolving output file <file name> for target <target name>.
Internal error. The repository may have inconsistencies. Contact Informatica Global Customer Support.
WRT_8188
Explanation: User Response:
WRT_8189
Explanation: User Response:
WRT_8197
Explanation: User Response:
WRT Messages
413
WRT_8198
Explanation: User Response:
Error opening target file <file name> during merge target file processing.
Operating system error. Contact the system administrator.
WRT_8199
Explanation: User Response:
Error reading target file <file name> during merge target file processing.
Operating system error. Contact the system administrator.
WRT_8200
Explanation: User Response:
WRT_8201
Explanation: User Response:
Error getting the merge target file name for target <target name>.
Internal error. The repository may have inconsistencies. Contact Informatica Global Customer Support.
WRT_8203
Explanation:
User Response:
WRT_8204
Explanation: User Response:
WRT_8205
Explanation: User Response:
Error: Could not find table name in catalog. This session cannot run with multiple partitions.
Internal error. The repository may have inconsistencies. Contact Informatica Global Customer Support.
WRT_8206
Explanation: User Response:
Error: The target table has been created with page level locking. The session can only run with multi partitions when the target table is created with row level locking.
You configured an Informix target table incorrectly for multiple partitions. Create the Informix target table with row-level locking.
WRT_8208
Explanation:
Error truncating target table <target table name>. The Integration Service is trying the DELETE FROM query.
The Integration Service was unable to run a truncate command on the database and tried to issue a delete command.
414
User Response:
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
Explanation: User Response:
External loader error, Teradata external loader cannot take table names greater than 24 characters. The table name <table name> has <table length> characters.
Teradata does not support external loads for table names greater than 24 characters. Use a table name of less than 24 characters.
WRT_8210
Explanation: User Response:
WRT_8211
Explanation: User Response:
See external loader log <loader log file name> for more details.
There was an error loading the table into the database using the database external loader utility. Possible errors might be that the table does not exist or there is a lock on the table. Check the external loader log file for details.
WRT_8212
Explanation: User Response:
Error: There have been too many database deadlocks. Unable to continue with the session.
You configured the Integration Service to end a session when the database encounters the maximum number of deadlocks you defined. Increase the value for deadlock retries on the Integration Service. Contact the database administrator.
WRT_8215
Explanation: User Response:
External loader error. The external loader process <process ID> exited prematurely.
This error is related to WRT_8216. The external loader exited unexpectedly, because the named pipe broke and the session failed. Check the external loader log file for details.
WRT_8216
Explanation: User Response:
WRT_8218
Explanation: User Response:
Error: Teradata external loader requires a primary key on table <table name> when using load mode <load mode>.
You did not set a primary key on the table when using load mode update, upsert, or delete. Set a primary key on the target table.
WRT_8219
Explanation: User Response:
Error: Table mismatch, target table <table name> with <number of columns> columns mismatch with physical table with <number of columns> columns.
The number of columns in the target table is different than the physical table. In the Designer, recreate the table or reload the target table from the database.
WRT Messages
415
WRT_8220
Explanation: User Response:
WRT_8226
Target Load Order Group <TLOG> is set for real-time flushing. Target based commit is switched to source based commit and target based commit interval is used as source based commit interval.
This is an informational message. You configured the session for real-time data extraction with target-based commits. The Integration Service will run the session with source-based commits. If you want to run the session in real time, you do not need to take any action. If you want to run the session with target-based commits, remove the flush latency function from the filter condition.
Explanation:
User Response:
WRT_8229
Explanation: User Response:
WRT_8244
Explanation:
Error outputting row # <row number> for output file <flat file target>. The row was rejected.
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 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
Explanation:
Error: External loader is not supported for direct flat files. Target instance <target instance name>.
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. 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.
User Response:
WRT_8247
Explanation: User Response:
Error: Cannot run in bulk mode for a test load for connection <target name>.
In the session properties, you configured the Integration Service to perform a test load and you chose bulk mode for a relational target. 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.
416
WRT_8250
Explanation: User Response:
Target (test load not supported for this target type): <target name> (Instance Name: <target instance name>).
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. None. The Integration Service only performs a test load on relational targets.
WRT_8270
Explanation: User Response:
WRT_8281
Explanation: User Response:
Error: The same character <character> is used as both field and decimal separator for the field <port name> of the target <target name>.
For the delimited flat file target definition, you chose the specified character as the decimal separator and as the field delimiter. 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
Explanation: User Response:
Error: The same character <character> is used as both field and thousand separator for the field <port name> of the target <target name>.
For the delimited flat file target definition, you chose the specified character as the thousand separator and as the field delimiter. 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
Explanation: User Response:
External loader process <loader process> exited with warning code <action file code>.
You are using an external loader warning action file. The external loader returned a non-zero warning code. 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
Explanation: User Response:
WRT_8300
Explanation:
External loader error. Error opening loader warning action file <file name> for reading. errno = <system error code>.
You configured the Integration Service to use an external loader warning action file. The Integration Service cannot read the warning action file.
WRT Messages
417
Verify that the system account that started the Integration Service has read permission for the directory the loader warning action file is located in. System error. Contact the system administrator.
WRT_8301
Explanation: User Response: Explanation:
Error loading warning codes from external loader warning action file <file name>.
The Integration Service could not load the warning codes from the external loader warning action file. Check preceding messages to see the cause of the error. 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. Specify a name and location for the external loader warning action file.
User Response:
WRT_8302
Explanation: User Response:
External loader error. Error duplicating handle to stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.
System error. Contact the system administrator.
WRT_8303
Explanation: User Response:
External loader error. Error opening DB2 EEE external loader log file for writing. System error message is <system error message>. errno = <error number>.
System error. Contact the system administrator.
WRT_8304
Explanation: User Response:
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>.
System error. Contact the system administrator.
WRT_8305
Explanation: User Response:
External loader error. Error restoring stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.
System error. Contact the system administrator.
WRT_8308
Explanation: User Response:
Error: Failed to write metadata for target table <target instance> to the output file <target file name>.
You configured the Integration Service to write flat file metadata to the target file. The Integration Service could not write to the target. Verify the Integration Service can connect to the flat file target directory and that the disk has enough space.
WRT_8309
Explanation:
External loader error. The Date Format <format> is invalid. Target instance <target instance name>.
You entered an invalid value for the Date Format option when you configured the MultiLoad external loader.
418
User Response:
Edit the MultiLoad external loader connection and enter a valid value for Date Format. Restart the session.
WRT_8310
Explanation: User Response:
External loader error. Update is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.
The MultiLoad or TPump external loader cannot run in update mode because you did not define a primary key for the target. Run the external loader in a different mode, or define a primary key for the target.
WRT_8311
Explanation: User Response:
External loader error. Update is not valid for target instance <target instance name> since no non-key field(s) is mapped to the target.
The MultiLoad or TPump external loader cannot run in update mode because you did not define any non-key columns in the target instance. Run the external loader in a different mode, or add a non-key column to the target.
WRT_8312
Explanation: User Response:
External loader error. Delete is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.
The MultiLoad or TPump external loader cannot run in delete mode because you did not define a primary key for the target. Run the external loader in a different mode, or define a primary key for the target.
WRT_8313
Explanation:
External loader error. Upsert is not valid for target instance <target instance name> since update is not valid for the target.
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.
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
Explanation: User Response:
The user-defined commit session is not supported for this type of mapping (no targets in commit groups).
Internal error. Contact Informatica Global Customer Support.
WRT_8324
Explanation:
Warning: Target Connection Group's connection doesn't support transactions. Targets <target names> may not be loaded according to specified transaction boundary rules!
You are running a source-based commit or user-defined commit session, and the named targets may not recognize transaction boundaries. This might happen with flat file targets or with bulk loading. This is an informational message for flat file targets, as flat files are commit-neutral. If you run the session in bulk mode, and you want to ensure that the targets load according to transaction boundaries, you can edit the session and run the session in normal mode.
User Response:
WRT Messages
419
WRT_8329
Explanation:
Warning. Ignoring external loader control file directory <directory> since it is all whitespace.
You configured the Integration Service LoaderControlFileDirectory option to use a directory separate from the Integration Service installation directory to create and store external loader control files, but you did not specify a directory name. Specify a directory name for LoaderControlFileDirectory.
User Response:
WRT_8343
Explanation: User Response:
Error: Target filename <file name> exceeded maximum allowable length <bytes>.
The target file name length exceeds the system limit (260 on Windows, 255 on UNIX). Reduce the length of the file name.
WRT_8371
Explanation: User Response: Explanation:
Row rejected since a rollback was issued due to errors in the transaction.
The Integration Service encountered an error in the transaction and the session is configured to roll back on error. Read other messages in the log file to find the row that caused the error. 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. Read other messages in the log file to find the row that caused the transaction control expression that evaluated to roll back.
User Response:
WRT_8372
Explanation: User Response:
WRT_8398
Explanation:
Error opening session output file <file name>. Error: <error text>.
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. 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.
User Response:
WRT_8399
Explanation: User Response:
Error closing target output file <file name>. Error: <error text>.
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. 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
Explanation:
High availability license is absent. Retry period specified for Integration Service connection to target is ignored.
The connection object properties are configured, but you do not have the high availability option. The connection retry period is ignored.
420
User Response:
None.
WRT_8419
Explanation:
Flat file target <target name> FileName port is not supported with connection or merge option.
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. Remove the FileName port from the target.
User Response:
WRT_8424
Explanation: User Response:
The Integration Service cannot read the control file template <control file template name>.
The Integration Service was unable to find the control file template. Verify that the directory and file name for the control file template are entered correctly in the session properties. Verify that the file exists in the specified directory.
WRT_8425
Explanation: User Response:
WRT_8426
Explanation: User Response:
WRT_8428
Explanation: User Response:
WRT_8430
Explanation: User Response:
The Integration Service could not create a locale for code page ID: <code page>.
The Integration Service failed to create an I18N converter object. Contact Informatica Global Customer Support.
WRT_8435
User Response:
WRT_8436
User Response:
WRT_8437
User Response:
The following error occurred writing recovery information to the recovery queue: <error message>.
Review the session log for related messages.
WRT_8438
User Response:
The following error occurred deleting recovery information from the recovery queue: <error message>.
Review the session log for related messages.
WRT Messages
421
WRT_8439
User Response:
The following error occurred reading recovering information from the recovery queue: <error message>.
Review the session log for related messages.
WRT_8442
User Response:
The Integration Service cannot recover multi-partitioned flat file targets with the concurrent merge option.
Disable recovery for the workflow.
WRT_8443
Explanation:
The Integration Service cannot repeat a multibyte NULL character in the file <file name>.
The session has a fixed width target configured to repeat null characters. The session fails because the null character is a multibyte character and the field length is not divisable by the number of bytes in the null character. Choose a single-byte null character.
User Response:
WRT_31215
Explanation: User Response:
WSC Messages
WSC_33021
Explanation: User Response:
Web Service connection <application connection name> cannot have a negative timeout value <timeout value>.
The value for the Timeout parameter in the Web Service application connection is a negative number. Set the Timeout value in the Web Service application connection equal to zero or higher.
WSC_33023
Explanation: User Response:
Encountered a problem during SOAP request conversion (DOC to RPC): <error details>.
The SOAP request for a web service source contains invalid or incomplete data. See the error details for more information. Modify the SOAP request in the Edit Tables dialog box.
WSC_33024
Explanation: User Response:
Error encountered in getting Operation Name for the table <operation name>.
Internal error. Contact Informatica Global Customer Support.
WSC_33026
Explanation: User Response:
422
WSC_33028
Explanation: User Response:
WSC_33030
Explanation: User Response:
WSC_33031
Explanation: User Response:
WSC_33032
Explanation: User Response:
WSC_33033
Explanation:
User Response:
WSC_38001
Explanation: User Response:
WSC_38002
Explanation: User Response:
WSC_38003
Explanation: User Response:
WSC_42008
Explanation: User Response: Explanation:
WSC Messages
423
Make sure the PATH settings are correct. The CLASSPATH setting is incorrect. Make sure the CLASSPATH settings are correct.
WSC_42013
Explanation: User Response: Explanation: User Response: Explanation: User Response:
WSC_42021
Explanation: User Response:
WSC_42022
Explanation: User Response: Explanation:
User Response:
WSH Messages
WSH_501
Explanation: User Response:
Service Workflow <workflow name> in repository <repository name> and folder <folder name> is invalid. This workflow cannot be accessed using the Web Services Hub.
The Web Services Hub could not access the workflow because the workflow is not configured as a web services workflow. Use a valid web services workflow.
WSH_502
Explanation: User Response:
424
WSH_505
Explanation: User Response:
WSH_516
Explanation: User Response:
Service <web service name>: Start of workflow <workflow name> located in folder <folder name> repository <repository name> failed with error <error message>.
The Web Services Hub could not start the web service workflow. See the additional error message for more information.
WSH_520
Explanation: User Response:
WSH_521
Explanation: User Response:
Workflow <workflow name> in folder <folder name> failed to complete. Workflow notification handler is invoked.
The web service workflow encountered an internal error and failed. Review the notification. Resolve the issue and restart the workflow.
WSH_522
Explanation: User Response:
Failed to fetch details of the workflow <workflow name>, in folder <folder name> while fetching data for the repository <repository name> : <error message>.
The Web Services Hub could not retrieve the details of the workflow from the repository. See the additional error message for more information.
WSH_523
Explanation: User Response:
Failed to update data cache for folder <folder name> in the repository <repository name> : <error message>
The Web Services Hub could not update the folder cache. See the additional error message for more information.
WSH_524
Explanation: User Response:
Failed to update data cache for workflow <workflow name>, in the folder <folder name> in the repository <repository name> : <error message>.
The Web Service Hub could not update the workflow cache. See the additional error message for more information.
WSH_526
Explanation: User Response:
Failed to fetch repository data for the repository <repository name> : <error message>.
The Web Services Hub could not retrieve the data for the repository. See the additional error message for more information.
WSH_530
Explanation: User Response:
Failed to update data cache for repository <repository name> : <error message>.
The Web Services Hub could not update the data cache for the repository. See the additional error message for more information.
WSH_535
Explanation:
WSH Messages
425
User Response:
WSH_547
Explanation: User Response:
WSH_553
Explanation: User Response:
Failed to find service proxy for the Service <web service name>.
The Web Services Hub could not find the web service proxy for the web service workflow. Review the workflow log for more information. Restart the web service workflow.
WSH_557
Explanation: User Response:
Service <web service name>: Failed to activate the service workflow with error <error message>.
The Web Services Hub could not activate the web service workflow. See the additional error message for more information.
WSH_567
Explanation: User Response:
Request <request instance ID>: Invocation timed out for Service <web service name>. Sending the response containing SOAP fault to the client.
The web service request has timed out. The Web Services Hub will return a SOAP fault message to the client. Review the workflow log for more information. Restart the web service workflow.
WSH_572
Explanation: User Response:
Request <request instance ID>: Client request is no longer active. Discarding the response message from the WS Writer.
The Web Services Hub discarded the response message because the client request is no longer active. Resend the web service request.
WSH_578
Explanation: User Response:
Request <request instance ID> Client IP <client IP address>: Request message for the Service <web service name> failed with error <error message>.
The Web Services Hub could not process the web service request. See the additional error message for more information. Resend the web service request.
WSH_601
Explanation: User Response:
Service <web service name>: Failed to start the workflow with error <error message>.
The Web Services Hub could not start the workflow. See the additional error message for more information. Resolve the problem and restart the web service workflow.
WSH_606
Explanation: User Response:
WSH_608
Explanation: User Response:
426
WSH_617
Explanation: User Response:
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.
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. Review the SOAP fault message. Resolve the issue and resend the web service request.
WSH_622
Explanation: User Response:
Service <web service name>: Failed to update/add service proxy in the folder <folder name> in repository <repository name>.
The Web Services Hub could not update or add the web service proxy to the folder in the repository. Review the Repository Service log for more information.
WSH_706
Explanation: User Response:
WSH_721
Explanation: User Response:
WSH_731
Explanation: User Response:
WSH_1005
Explanation: User Response:
WSH_1006
Explanation: User Response:
WSH_1007
Explanation: User Response:
WSH_1010
Explanation: User Response:
WSH Messages
427
WSH_1011
Explanation: User Response:
WSH_1012
Explanation: User Response:
WSH_1013
Explanation: User Response:
Web Services Provider source or target contains an invalid key. Expected Key: [key name].
The web service source or target contains a key column that is not valid. Review the workflow log for more information. Create the web service source and target with the correct key columns.
WSH_1014
Explanation: User Response:
Web Services Provider source or target does not contain a required key.
The web service source or target does not contain the required key. Review the workflow log for more information. Create the web service source and target with the appropriate primary or foreign key.
WSH_1016
Explanation: User Response:
The web service workflow <workflow name> does not exist or is invalid.
The Web Services Hub could not find the web service workflow in the repository. Verify that the workflow is a valid web service and restart the web service workflow.
WSH_1017
Explanation: User Response:
Invalid schema name : Schema <XML schema name> is not imported by the WSDL for the service workflow <workflow name>.
The Designer could not import the source or target from the WSDL because of a schema name that is not valid. Review the repository log for more information. Reimport the source and target from the WSDL.
WSH_1026
Explanation: User Response:
WSH_1027
Explanation: User Response:
WSH_1070
Explanation: User Response:
Request <request instance ID> ClientIP <client IP address>: Failed to read client message for Service <web service name> with payload of size <payload size>.
The Web Services Hub could not read the message from the client. Verify that the PowerCenter Integration Service is running. Resend the web service request.
428
WSH_1071
Explanation: User Response:
Request <request instance ID> ClientIP <client IP address>: Failed to decode client encoding for Service <web service name>.
The Web Services Hub could not translate the SOAP encoding of the message in the request. Verify that the encoding style is valid and that the source and target have the same encoding style.
WSH_1072
Explanation: User Response:
Request <request instance ID> ClientIP <client IP address>: Reading client message for Service <web service name> failed with error <error message>.
The Web Services Hub could not read the message in the web service request. See the additional error message for more information. Verify that the PowerCenter Integration Service is running. Resend the web service request.
WSH_1077
Explanation: User Response:
Failed to send Request <request instance ID> with ClientIP <client IP address> to the service workflow instance.
The Web Services Hub could not send the web service request. Check the connection between the Web Services Hub and the PowerCenter Integration Service. Resend the web service request.
WSH_1078
Explanation: User Response:
Request <request instance ID> ClientIP <client IP address>: Failed to send client reply for Service <web service name> with error <error message>.
The Web Services Hub could not send the response to the client. See the additional error message for more information. Resend the web service request.
WSH_1079
Explanation: User Response:
Service <web service name>: Web service source connection has been reset due to error <error message>.
The connection to the web service source was reset because of the error described in the message. 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
Explanation: User Response:
WSH_1104
Explanation: User Response:
Service statistics operation <operation name> failed with error <error message>.
The web service operation failed. See the additional error message for more information.
WSH_1124
Explanation: User Response:
Service <web service name>: Cannot find schema for namespace <namespace>.
The Web Services Hub could not find the namespace schema. Verify that the namespace included in the message is correct and resend the request.
WSH Messages
429
WSH_1126
Explanation: User Response:
Service <web service name>: Request or response with attachment is not supported for RPC encoding style.
You cannot include an attachment in a request or response message that uses the RPC SOAP binding. To include an attachment in a request or response message, use MIME binding.
WSH_1127
Explanation: User Response:
Service <web service name>: Inconsistent binding namespace between Web Service Provider source and target.
The binding style for the source and target messages must be the same. Change the binding style for the source or target so that they match.
WSH_1128
Explanation: User Response:
WSH_1129
Explanation: User Response:
WSH_1137
Explanation: User Response:
The folder <folder name> does not exist in repository <repository name>.
The folder name is not valid and cannot be found in the repository. Use a valid folder name.
WSH_1138
Explanation: User Response:
Invalid service timeout is specified for workflow <workflow name>. The default value <timeout value> is used.
The timeout value set for the workflow is not valid. The Web Services Hub will use the default timeout value. 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
Explanation: User Response:
Invalid maximum instance run per hub is specified for workflow <workflow name>. The default value <Maximum Run Count Per Hub value> is used.
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. 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
Explanation: User Response:
Invalid service time is specified for workflow <workflow name>. The default value <service time threshold value> is used.
The value set for the Service Time Threshold property of the workflow is not valid. The Web Services Hub will use the default value. 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.
430
WSH_1142
Explanation:
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.
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>. Correct the folder name to include the repository name and restart the workflow.
User Response:
WSH_1143
Explanation: User Response:
WSH_1149
Explanation: User Response:
WSH_1150
Explanation: User Response:
The nonce value provided has been used. Provide a new nonce value for this login.
The web service request uses a digested password but the password includes a nonce value that is not valid because it has been used. 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
Explanation: User Response:
WSH_1152
Explanation:
Nonce and created values must not be specified for a PasswordText request.
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. Modify the request so that the UsernameToken element in the SOAP message does not contain values for the Nonce and Created elements.
User Response:
WSH_1153
Explanation: User Response:
The password request is of an unknown type. The request must be a PasswordDigest or PasswordText request.
The password Type attribute contains an invalid value. 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.
WSH Messages
431
WSH_1154
Explanation: User Response:
WSH_95063
Explanation: User Response:
Could not log in to the repository <repository name> with the specified username and password.
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. Use a valid user name and password to log in to the repository.
WSP Messages
WSP_33002
Explanation: User Response:
WSP_33006
Explanation: User Response:
The mapping contains more than one Web Services Provider source.
You tried to run a session that contains more than one Web Services Provider source. Edit the mapping to ensure that it contains only one Web Services Provider source.
WSP_33007
Explanation: User Response:
The mapping contains more than one Web Services Provider target.
You tried to run a session that contains more than one Web Services Provider output target. 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
Explanation: User Response:
Out of memory.
The Integration Service machine is out of memory. 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
Explanation: User Response:
Valid Real-time options key is not found, unable to run this Web Service session. Please obtain a valid real-time options key.
The Real-time license is expired, or you have not applied the license key to the license file. 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
Explanation:
432
User Response:
WSP_34008
Explanation: User Response:
WSP_34010
Explanation: User Response:
WSP_34011
Explanation: User Response:
WSP_34014
Explanation: User Response:
Failed to init connection, status code <code>, error message <error message>.
The Integration Service encountered an error initializing a connection to the Web Services Hub. Check the additional error message for more information.
WSP_34015
Explanation: User Response:
Failed to deinit connection, status code <code>, error message <error message>.
The Integration Service encountered an error disconnecting from the Web Services Hub. Check the additional error message for more information.
WSP_34016
Explanation: User Response:
Failed to read data, status code <code>, error message <error message>.
The Integration Service encountered an error reading from the Web Services Hub. Check the additional error message for more information.
WSP_34017
Explanation: User Response:
Failed to write data, status code <code>, error message <error message>.
The Integration Service encountered an error writing to the Web Services Hub. Check the additional error message for more information.
WSP_34018
Explanation: User Response:
Failed to flush data, status code <code>, error message <error message>.
The Integration Service encountered an error flushing to the Web Services Hub. Check the additional error message for more information.
WSP_34019
Explanation: User Response:
WSP Messages
433
WSP_34020
Explanation: User Response:
WSP_34030
Explanation: User Response:
WSP_34034
Explanation: User Response:
WSP_35001
Explanation: User Response:
Cache folder attribute cannot be fetched for reader partition <partition number>.
Internal error. Contact Informatica Global Customer Support.
WSP_35002
Explanation: User Response:
WSP_35003
Explanation: User Response:
WSP_35005
Explanation:
User Response:
WSP_35006
Explanation: User Response:
Reader partition <partition number> failed to truncate message cache to last serialized message: <message text>.
The session failed, and the Integration Service was unable to truncate the partial message in the cache. Check the additional error message for more information.
WSP_35008
Explanation: User Response:
Reader partition <partition number> failed to flush the cache: <message text>.
The Integration Service encountered an error flushing the message cache. Check the additional error message for more information.
434
WSP_35010
Explanation: User Response:
WSP_35012
Explanation: User Response:
WSP_35013
Explanation: User Response:
WSP_35015
Explanation: User Response:
WSP_35017
Explanation: User Response:
WSP_35018
Explanation: User Response:
WSP_35019
Explanation: User Response:
WSP_35020
Explanation: User Response:
WSP_35021
Explanation:
User Response:
WSP_36002
Explanation: User Response:
Writer target <target name> partition <partition number> failed to initialize flat file generator.
The Web Services Provider Writer for flat files could not create the target flat file. Check the session log for additional messages.
WSP Messages
435
WSP_36003
Explanation: User Response:
Writer target <target name> partition <partition number> failed to initialize XML generator.
The Web Services Provider Writer for XML could not create the XML target file. Check the session log for additional messages.
WSP_36004
Explanation: User Response:
Writer target <target name> group <target group> partition <partition number> failed to process flat file messages.
The Web Services Provider Writer for flat files failed to process the flat file message. Check the session log for additional messages.
WSP_36005
Explanation: User Response:
Writer target <target name> group <target group> partition <partition number> failed to process XML messages.
The Web Services Provider Writer for XML failed to process the XML message. Check the session log for additional messages.
WSP_36006
Explanation: User Response:
Writer target <target name> group <target group> partition <partition number> failed to process end of file.
The Web Services Provider Writer for XML encountered an error processing the end of file (EOF) for the target group. Check the session log for additional messages.
WSP_36007
Explanation: User Response:
Writer target <target name> group <target group> partition <partition number> failed to process end of XML.
The Web Services Provider Writer for XML failed to send the XML message to the Web Services Hub. Check the session log for additional messages.
WSP_36008
Explanation: User Response:
Invalid cache folder in writer target partition <target name> partition <partition number>.
The XML target cache folder specified in the session properties is either invalid or it does not exist. Verify the XML cache folder name.
WSP_36010
Explanation: User Response:
436
CHAPTER 23
XMLW Messages
XMLW_31001
Explanation: User Response:
XMLW_31002
Explanation: User Response:
XMLW_31003
Explanation: User Response:
XMLW_31004
Explanation: User Response:
The field <field name> with repository ID <ID number> should not belong to XML group <group number> named <group>.
The set of fields that belong to the XML group in the message is in an incorrect group. Check the target definition in the Designer to verify the position of the fields belonging to the group. Or contact Informatica Global Customer Support.
XMLW_31005
Explanation: User Response:
437
XMLW_31006
Explanation: User Response:
There already was a row inserted into output for the topmost group. Rejecting the row# <row number>.
The topmost group must have only one row of data since the XML file can have only one root. Make sure that the data to this group is limited to one row.
XMLW_31007
Explanation: User Response:
Row# <row number> has a NULL PK value for XML group <group>.
The XML Writer received data for a primary key that is null. The primary key cannot be null. Check the data and the mapping for inconsistencies. Run the Debugger.
XMLW_31008
Explanation: User Response:
Row# <row number> has a NULL FK value for NOT TOPMOST XML group <group>.
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. Check the data and the mapping for inconsistencies. Run the Debugger.
XMLW_31009
Explanation: User Response:
XMLW_31010
Explanation: User Response:
Unexpected error occurred while trying to set the value of the element <XML element> with XML mapping <XML Map> to <value>.
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. Contact Informatica Global Customer Support.
XMLW_31011
Explanation: User Response:
An error occurred while trying to convert the data for field <field name> repository ID <ID number> of the row <row number> to text.
The XML Writer failed to convert the data into text. Check previous messages in the log for more information. Then contact Informatica Global Customer Support.
XMLW_31012
Explanation: User Response:
Cannot register XML group <group> for target <target instance> - no corresponding group definition found in the target.
Internal error. The target requested a group that does not exist. Contact Informatica Global Customer Support.
XMLW_31013
Explanation: User Response:
Unknown (or illegal) attribute value <value> for attribute <attribute name>. Check repository for possible data corruption.
Neither the first nor the last values were saved in the repository due to repository inconsistencies. Contact Informatica Global Customer Support.
438
XMLW_31014
Explanation: User Response:
Unexpected error while generating XML text for the row being removed from the DOM tree. Row's PK value is <value>.
The XML writer encountered errors while generating code for values. Run the Debugger to check the data for inconsistencies. Contact Informatica Global Customer Support.
XMLW_31016
Explanation: User Response:
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>.
At initialization time, the Integration Service found that the text in the mapping is not in the target code page. Check that the XML mapping is compatible with the target code page.
XMLW_31018
Explanation: User Response:
XMLW_31019
Explanation: User Response:
XMLW_31020
Explanation: User Response:
Cannot find an XML group for the incoming block of rows. Fatal error.
The XML Writer cannot find the appropriate group corresponding to the block of data. Run the session again. If it fails, contact Informatica Global Customer Support.
XMLW_31021
Explanation: User Response:
Error occurred while processing EOF for the XML target <target instance> group <group>.
The XML Writer encountered errors when processing the end of file (EOF) for the group. Contact Informatica Global Customer Support.
XMLW_31022
Explanation: User Response:
Fatal error while flushing to file <file name>. System error message is <error message>.
When writing to file, the XML Writer failed with the operating system message. 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
Explanation: User Response:
XMLW Messages
439
XMLW_31024
Explanation: User Response:
Error transferring staged file for XML target <target instance> using FTP.
The Integration Service could not transfer the XML file by FTP. Verify FTP permissions, directory path, network connection, and that the FTP server is running. Run the session again.
XMLW_31026
Explanation: User Response:
XMLW_31027
Explanation: User Response:
Fatal error closing XML output file <file name>. System error message is <error message>.
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. Check the operating system message for more information.
XMLW_31029
Explanation: User Response:
Cannot locate XML init/deinit functions in the DLL <.dll file name>.
The XML .dll file does not contain the initialization and deinitialization functions. Verify that the .dll file is the correct file shipped with the product. If it is incorrect, contact Informatica Global Customer Support.
XMLW_31030
Explanation: User Response: Explanation: User Response:
FK field <field name> for group <group> has to be projected, i.e. there has to be an input field for it.
The foreign key must be connected in the mapping. Check that the mapping and that the foreign key are connected. Contact Informatica Global Customer Support. The target is not defined as a flat file or XML target. It is an undefined object. Contact Informatica Global Customer Support.
XMLW_31040
Explanation: User Response:
Field <field name> of the *ROOT* XML group <group> is projected while the PK field is not.
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. Connect the PK field of the root group.
XMLW_31041
Explanation:
FK of the group <group> and PK of the parent group <group> should both either have an input field or not.
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. Validate the mapping and run the session again. Or contact Informatica Global Customer Support.
User Response:
XMLW_31043
Explanation:
440
User Response:
Edit the mapping to project additional fields into the named group.
XMLW_31047
Explanation: User Response:
XMLW_31056
Explanation: User Response:
XMLW_31059
Explanation: User Response:
Fatal error returned while closing XML document <target name> after incremental flush/ commit.
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. Check previous error messages for more information.
XMLW_31060
Explanation: User Response:
Fatal error <error number> occurred while flushing XML output <target name>.
The XML Writer failed to write data to a target file. Check file write permissions, disk space, and that the path to the file exists. Check other error messages for more information.
XMLW_31061
Explanation: User Response:
Fatal error <error number> occurred while closing XML document <target name>.
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. Check previous error messages for more information.
XMLW_31063
Explanation: User Response:
Fatal error <error number> occurred while opening file list <target>.
The XML Writer failed to open the file list. The file might not have write permissions or the path to the file is incorrect. Check the file write permissions, the directory path, disk space, or if the file exists.
XMLW_31064
Explanation: User Response:
Fatal error transferring local file <file name> into remote location <path> using FTP. The file list will not be produced.
The Integration Service could not transfer the XML file by FTP to produce a file list at the remote location. Verify FTP permissions, the directory path, network connections, and that the FTP server is running.
XMLW_31065
Explanation: User Response:
Fatal error <error number> opening an FTP connection for a file list <file name>.
The Integration Service failed to open an FTP connection for a source using a file list. Verify FTP permissions, the directory path, network connections, and that the FTP server is running. Check other error messages for more information.
XMLW Messages
441
XMLW_31066
Explanation: User Response:
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.
You are using an upgraded MQ session that uses the Output XML on Flush/Commit attribute. PowerCenter no longer supports this option. 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
Explanation: User Response:
Error: Unknown On Commit attribute value in target <target name>. Check repository for possible corruption.
You are using an upgraded XML session that uses the Output XML on Flush/Commit attribute. PowerCenter no longer supports this option. 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_31080
Explanation: User Response:
XMLW_31086
Explanation: User Response:
Row <row number> in XML group <group> has more than one non-NULL hierarchical foreign key value. This row will be dropped.
When a row has two possible parents, one of the foreign keys in the row must be NULL. None.
XMLW_31089
Explanation:
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.
The Integration Service uses a data cache to store XML row data while it generates an XML document. The cache size is the sum of all the groups in the XML target instance. The XML target cache is too large. Reduce the target cache size in the XML target properties.
User Response:
XMLW_31090
Explanation: User Response:
XMLW_31091
Explanation:
442
User Response:
Check the file write permissions, the directory path, disk space. Check previous error messages for more information.
XMLW_31092
Explanation: User Response:
XMLW_31093
Explanation: User Response:
XMLW_31108
Explanation: User Response:
Error: An appropriate start row was not found for XML root group <group> with circular reference. No output was generated.
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. Verify the source data has one row going to the root that is not a child of another group.
XMLW_31110
Explanation: User Response:
Error: Duplicate row detected for single occurring group <group>, with parent group <parent group>.
The Integration Service detected a duplicate row in a group. 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.
The session failed because the foreign key in a derived XML group has no data. Add a link to the foreign key in the mapping.
XMLW_31210
Explanation: User Response:
Fatal error transferring local file <file name> into remote location <path> using SFTP. The file list will not be produced.
The Integration Service could not transfer the XML file by SFTP to produce a file list at the remote location. Verify SFTP permissions, the directory path, network connections, and that the SFTP server is running.
XMLW_31211
Explanation: User Response:
Fatal error opening remote list file <file name> using SFTP.
The Integration Service failed to open an SFTP connection for a source using a file list. Verify SFTP permissions, the directory path, network connections, and that the SFTP server is running. Check other error messages for more information.
XMLW Messages
443
XMLR Messages
XMLR_82061
Explanation: User Response:
Error: View {XML view} column {column name} was not found and cannot be NULL. Row will not be processed.
The XML document is missing data for a required column. The column cannot be NULL in the XML instance document. Change the XML document to include the correct instance data for the schema.
XMLR_82065
Explanation: User Response:
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.
The primary key and the foreign key must be the same datatype. Set the primary key and the foreign key columns to the same datatype.
XMLR_82078
Explanation:
Fatal Error: Infinite length is set for xsd:string for group [group name] column [column name]. Change the size to an appropriate value.
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. Set the string precision to a finite value of the column in the XML source, and re-create the source qualifier.
User Response:
444