•  Preface
  •  Informatica Resources
    •  Informatica Network
    •  Informatica Knowledge Base
    •  Informatica Documentation
    •  Informatica Product Availability Matrixes
    •  Informatica Velocity
    •  Informatica Marketplace
    •  Informatica Global Customer Support
•  Client Messages
  •  PowerExchange for JMS Messages
    •  The datatype assigned to the field <field name> is invalid.
    •  Field <field name> is invalid because JMS source field does not allow “NOTNULL.”
    •  Header field <field name> is missing.
    •  The JMS body field name is invalid.
    •  The JMS property field value is invalid.
    •  Message body field is missing.
    •  The object contains an invalid message body type.
    •  The object has an invalid field category <category>.
    •  The object has an invalid header field.
    •  The object has an invalid header field map value.
    •  The object is a Bytes Message, but the body field name is invalid.
    •  The object is a Bytes Message, but the datatype for the body field is invalid.
    •  The object is a Text Message, but the body field name is invalid.
    •  The object is a Text Message, but the datatype for the body field is invalid.
    •  The precision is invalid.
    •  Unknown error happened.
  •  PowerExchange for Netezza Messages
    •  Error occurred while opening ODBC data source administrator.
    •  Failed to add menu item Import Netezza Source.
    •  Failed to add menu item Import Netezza Target.
    •  Failed to log on to the database.
    •  No output links found or no input link found for the output link.
  •  PowerExchange for PeopleSoft Messages
    •  Application source qualifier <application source qualifier name>: Error in preparing the query for effective date data extraction.
    •  Application source qualifier <application source qualifier name> has Effective Date Extract Join Order with invalid source names.
    •  Application source qualifier <application source qualifier name> has invalid Extract Date.
    •  Application source qualifier <application source qualifier name> has more than one tree attached.
    •  Application source qualifier <application source qualifier name> has projected port with no inbound link.
    •  Application Source Qualifier <application source qualifier name> has tree and Extract Override.
    •  Application source qualifier <application source qualifier name> has winter tree and other sources.
    •  Application source qualifier <application source qualifier name> is not a valid PeopleSoft SQ
    •  Application Source Qualifier <application source qualifier name> sources are not related.
    •  Application source qualifier <application source qualifier name> tree is joined with non-detail source.
    •  Error! <Source name> is not a valid PeopleSoft source.
    •  Error! Cannot find PeopleSoft metadata from source <source name>!
    •  Error! This version of PeopleSoft source <source name> is not supported!
    •  Failed to log on to PeopleSoft database server.
    •  The language code <language code> specified is either invalid or not configured on the current PeopleSoft system.
    •  The specified Language Code <language code> is either invalid or not configured on the current PeopleSoft System!
  •  PowerExchange for Salesforce.com Messages
    •  DescribeGlobal failed. Error code: <error code> Reason: <error message>.
    •  DescribeSObject <object name> failed. Error code: <error code> Reason: <error message>.
    •  Failed to add menu item for import from Salesforce.com.
    •  Failed to create table. Reason: <error message>.
    •  Login failed. Error code: <error code> Reason: <error message>.
    •  The Source <source name> is associated with more than one Source Qualifier.
    •  The Source Qualifier <Application Source Qualifier name> has more than one PowerCenter Connect for Salesforce.com source definition associated with it.
  •  PowerExchange for SAP NetWeaver Messages
    •  Generating and Installing ABAP Programs
    •  Importing and Exporting SAP Mappings
  •  PowerExchange for SAP NetWeaver BI Messages
    •  The Designer cannot import the selected objects.
    •  Hostname <hostname> unknown.
    •  The SAP BW system does not contain any activated InfoSources.
    •  The Designer is not connected to the SAP BW server.
    •  Open saprfc.ini failed: No such file or directory.
    •  Partner not reached (host <host name>, service <service number>).
  •  PowerExchange for TIBCO Messages
    •  At least two fields have the same map value <map value>.
    •  Attributes <attribute> is ignored. Another sibling attribute with the same name already exists.
    •  Conversion from TIBCO source <source> to TIBCO target failed: <error message>.
    •  Corrupted TIBCO Repository. Can't retrieve any metadata.
    •  Field <field> has invalid map value <map value> based on the source/target's metadata.
    •  For TIBCO targets, a non-header field cannot coexist with any of its direct/indirect parent groups in the TIBCO metadata tree.
    •  Libraries related to TIBCO SDK metadata retrieval weren't appropriately installed.
    •  Metadata for the TIBCO source/target is corrupt.
    •  Metadata is invalid. Non-empty TIBCO source/target must have one metadata group.
    •  The node can't be renamed. <error message>.
    •  The node <node> can't be removed. <error message>.
    •  Sender name header field is not applicable for target.
    •  Unexpected error happened when trying to retrieve metadata from TIBCO Repository.
    •  Sequence header field is not applicable for target.
  •  PowerExchange for webMethods Messages
    •  Conversion from the source to target failed.
    •  Document type <document type name> contains field <field name>, which is of an unsupported datatype.
    •  Envelope field <field name> is invalid or uses the datatype <datatype>, which does not match the data for the field.
    •  Error from the webMethods Broker: <error message>.
    •  Failed to add a menu item.
    •  Importing webMethods source from document type <document type name> failed.
    •  Importing webMethods target from document type <document type name> failed.
    •  Importing failed. PowerCenter Connect for webMethods was not installed correctly.
    •  The Map attribute value for field <field name> is empty.
    •  The Map attribute value <map value> for field <field name> already exists.
    •  There should be exactly one group.
  •  PowerExchange for Web Services Messages
    •  Encountered a problem during SOAP request conversion (DOC to RPC): <error details>.
    •  Envelope contains an element other than Header and Body.
    •  Invalid SOAP Request. Body cannot have more than one operation.
    •  Invalid SOAP Request. Either body or header or both are missing.
    •  Invalid SOAP Request. Element <element name> does not exist.
    •  Invalid SOAP Request. Failed to process at <element name>.
    •  Invalid SOAP Request. Operation cannot be found.
    •  Invalid SOAP Request. The SOAP Operation parameters in the request are inconsistent with the WSDL file.
    •  Invalid SOAP Request. The SOAP request cannot be empty.
    •  The child element <element> cannot be found or is invalid.
    •  The envelope cannot be found.
    •  The namespace for prefix <prefix> cannot be found.
    •  The operation you selected contains multiple namespaces - which is not supported. Please select another operation.
    •  The part <part> for message <message> cannot be found or is invalid.
    •  The prefix for namespace <namespace> cannot be found.
  •  PowerExchange for WebSphere MQ Messages
    •  Cannot link to MsgId port.
    •  Connections from a MQ source cannot be modified.
    •  Unable to delete links from an MQ source to an MQ Source Qualifier transformation.
    •  Unable to delete links from an MQ Source Qualifier transformation to an associated source qualifier transformation.
    •  VSAM, XML, MQ sources connect to exactly one source qualifier transformation.
  •  XML Messages
    •  <Column name> cannot be pivoted since it is a key column.
    •  Cannot change cardinality! The selected cardinality will cause groups <group names> to be invalid.
    •  Denormalized group cannot be created since XML Element/Attribute <column name> has a many to many relationship with XML Element/Attribute <column name>.
    •  Element/Attribute <element or attribute name> occurs only once and cannot be pivoted.
    •  Group <group> cannot be related to group <group>. Related groups should be under the same XML tree branch.
    •  A key <column name> already exists at this level. <column name> has a one-one correspondence with <column name>.
    •  Only leaf elements can be pivoted. <column name> refers to a non-leaf element <element name> and cannot be pivoted.
    •  Only one reference port can reference a pass-through port in an XML Generator transformation.
    •  A reference port can be created only in the XML root group.
    •  Source: <source> is not part of the Source Join Order.
    •  The XML file has fewer elements than the pivot value specified. Element <element name> appears only <number> times in the XML file.
    •  The XML metadata is invalid.
    •  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.
•  Informatica Administrator Messages
  •  Informatica Administrator Messages
    •  Correct the validation errors in <field name> and try the update again. <error message>.
    •  The Domain Service could not disable the process due to the following error: <error message>.
    •  The Domain Service could not disable the service due to the following error: <error message>.
    •  The Domain Service could not enable the process due to the following error: <error message>.
    •  The Domain Service could not enable the service due to the following error: <error message>.
    •  Enter a valid location for the shared configuration on the node <node name>.
    •  Failed to create a connection to the specified database: Reason <error message>.
    •  The following error occurred while attempting to remove the node. Error - <error message>.
    •  The following error occurred while attempting to remove the service. Error - <error message>.
    •  The following error occurred while attempting to shut down the node. Error - <error message>.
    •  The following error occurred while enabling this service. Error - <error message>.
    •  This key was already used to update the license. Please use another key for the update.
    •  The location of the shared configuration files for some of the nodes could not be determined. Verify that all nodes are running.
    •  Logs for specified query could not be exported because of the following error. Error - <error message>.
    •  Logs for specified query could not be fetched because of the following error. Error - <error message>.
    •  Logs for specified query could not be purged because of the following error. Error - <error message>.
    •  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.
    •  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.
    •  None of selected nodes are running. Select at least one node that can be connected to run the Gateway Service.
    •  You cannot remove node <node name> because it is the only gateway in the domain.
•  A Message Codes
  •  ADV Messages
    •  ADV_13226 Could not open the following dll: <dynamic link library name>.The reason is: <error message>.
  •  ALERT Messages
    •  ALERT_10000 Alerts metadata was not found in the domain configuration database.
    •  ALERT_10001 Alert service has not been enabled yet.
    •  ALERT_10002 The user <user name> is not a user defined in the domain.
    •  ALERT_10003 The user <user name> is not subscribed for alerts.
    •  ALERT_10004 Unable to send alert of type <alert type> for object <object name>, alert message <alert message>, with error <error message>.
    •  ALERT_10010 Unable to remove the user <user name> from the alert service.
  •  ATHR Messages
    •  ATHR_10000 The Service Manager is not initialized yet.
    •  ATHR_10003 The Service Manager is disabled and cannot accept authorization requests.
    •  ATHR_10006 A request was received that was missing a required parameter.
    •  ATHR_10007 A request was received with wrong <actual object type> parameter (expected: <expected object type>).
    •  ATHR_10010 The Service Manager could not find <type of object> <object name>.
    •  ATHR_10011 The Service Manager requires <expected parameter count> parameters within message but received <actual parameter count> parameters.
    •  ATHR_10012 The Service Manager denied authorization access to <type of object> <object name>.
    •  ATHR_10013 The Service Manager cannot process <type of object> authorization access object type.
    •  ATHR_10014 The Service Manager for domain <this domain> received an authorization request for another domain <other domain>.
    •  ATHR_10015 The Service Manager received an external request to execute an internal operation by <the source of the credential used>.
    •  ATHR_10017 The Service Manager received an authorization request which did not contain a credential.
    •  ATHR_10018 The Service Manager cannot process authorization <type of activity> activity type.
    •  ATHR_10019 The Service Manager denied authorization access to read-only user <user name> attempting to modify <type of object> <object name>.
    •  ATHR_10021 The Service Manager denied authorization access to user <user name> attempting to access <type of object> <object name>.
    •  ATHR_10022 The Service Manager denied authorization access for user <user name> as service\folder is wrongly specified: <service and folder>.
    •  ATHR_10023 The Service Manager denied authorization access for user <user name> as service <service name> is not found.
    •  ATHR_10024 The Service Manager denied authorization access for user <user name> as request was for the wrong type of service <service type>.
    •  ATHR_10025 The Service Manager denied authorization access for user <user name> as request was for another domain <domain name>.
    •  ATHR_10026 User <user name> does not have permission to access another user in the domain.
  •  AUTH Messages
    •  AUTH_10000 The Service Manager could not enable Authentication because authentication state is invalid.
    •  AUTH_10001 The Service Manager is not initialized yet.
    •  AUTH_10005 The Service Manager is disabled and cannot accept authentication requests.
    •  AUTH_10007 Cannot add user because <user name> already exists.
    •  AUTH_10009 Cannot remove the Administrator user.
    •  AUTH_10010 Cannot encrypt the credential because the characters in the user name, password, or domain name are not UTF-8 compliant.
    •  AUTH_10011 Failed to enable Authentication.
    •  AUTH_10014 Authentication data is invalid as it contains no users.
    •  AUTH_10015 A request for operation <operation name> required input that was not supplied.
    •  AUTH_10016 A request cannot be performed as user <user name> cannot be found.
    •  AUTH_10018 A request for operation <operation name> expected input of type <expected input type>, but was supplied with <actual input type>.
    •  AUTH_10019 The user name or password is not recognized by the system.
    •  AUTH_10022 The node <node name> not defined within the domain.
    •  AUTH_10023 Administrator user name or password is not found in the domain configuration.
    •  AUTH_10024 Message request failed because the message contained invalid credentials that were not recognized by the system.
    •  AUTH_10026 The thread was interrupted while associating node <node name> with the domain.
    •  AUTH_10027 The user <user name> associated with node <node name> was not found in the domain.
    •  AUTH_10028 The password associated with node <node name> is invalid.
    •  AUTH_10029 The node <node name> is not associated in the domain.
    •  AUTH_10030 User <user name> was not associated with node <node name>.
    •  AUTH_10031 The host name for node <node name> is inconsistent between node configuration and domain configuration.
    •  AUTH_10032 The port number for node <node name> is inconsistent between node configuration and domain configuration.
    •  AUTH_10033 The gateway setting for node <node name> is inconsistent between node configuration and domain configuration.
    •  AUTH_10036 User <user name> does not have permission on any object within the domain.
    •  AUTH_10037 Domain <domain name> for Repository Service <Repository Service name> is not linked within this domain.
    •  AUTH_10038 Repository Service <Repository Service name> is not defined or referenced within this domain.
    •  AUTH_10039 Repository Service <Repository Service name> is defined in multiple known domains <list of domains>.
  •  AUTHEN Messages
    •  AUTHEN_10001 The Service Manager failed to authenticate user <user name> in security domain <security domain name>. The user is disabled.
    •  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>.
•  B Message Codes
  •  BAPI Messages
    •  BAPI_99101 One or more connection parameters missing.
    •  BAPI_99102 None of the parameters of function <function name> has been selected as STATUS RETURN structure.
    •  BAPI_99103 Function RETURN parameter is specified. However, only <number> out of <number> required values found when parsing the property value string.
    •  BAPI_99105 STATUS or TEXT field of RETURN parameter must have ABAP type CHAR or NUMC.
    •  BAPI_99106 Could not find the STATUS field [{0}] in the RETURN structure.
    •  BAPI_99107 Could not find the TEXT field [{0}] in the RETURN structure.
    •  BAPI_99109 Could not read the internal table for the function table parameter.
    •  BAPI_99113 Exception <exception> has been raised from the RFC function call with IntegrationID <integration_ID>.
    •  BAPI_99116 The Integration Service could not create an SAP internal table for function table parameter [{0}].
    •  BAPI_99118 The Integration Service could not find field [{0}] in the RETURN structure.
    •  BAPI_99129 Commit call to SAP failed.
    •  BAPI_99133 The Integration Service could not connect to SAP.
    •  BAPI_99135 Data overflow occurred when the Integration Service applied default value <value> to function parameter <function parameter name> for Integration ID <ID number>.
    •  BAPI_99136 Data <data> overflow at port <port number> for Integration ID <ID number>.
    •  BAPI_99137 Data overflow occurred when the Integration Service applied the default value <value> to the field <field name> for the Legacy Key <legacy key value>.
    •  BAPI_99138 Data conversion error for port <port number> with data <data>.
    •  BAPI_99139 Data conversion error for port <port number>.
    •  BAPI_99140 The Integration Service could not retrieve metadata for parameter <parameter name> of RFC function <function name> from SAP.
  •  BR Messages
    •  BR_16001 Error connecting to database.
    •  BR_16002 ERROR: Initialization failed.
    •  BR_16004 ERROR: Prepare failed.
    •  BR_16009 Reader run terminated.
    •  BR_16034 ERROR: Fetch failed.
    •  BR_16036 Error finding reader initializing function in dynamically loaded library.
    •  BR_16037 Error initializing driver.
    •  BR_16038 Sanity check failed: <error message>. Reader initialization failed.
    •  BR_16045 Reader run terminating. Error threshold <maximum number of errors> reached reading data from <file name>.
    •  BR_16046 User defined query <query name> has references to mapping parameters or variable that cannot be resolved correctly.
    •  BR_16047 User defined join condition and/or source filter <condition name> has references to mapping parameters or variable that cannot be resolved correctly.
    •  BR_16048 User defined source filter condition <condition name> has references to mapping parameters or variables that cannot be resolved correctly.
    •  BR_16050 User provided string <string value> has references to mapping parameters or variables that cannot be resolved correctly.
    •  BR_16056 FTP Information in the repository is corrupt.
  •  BTree Messages
    •  BTree_90002 Error: Specified cache size is too small. It must be larger than <size>.
    •  BTree_90004 Error initializing the B-Tree.
    •  BTree_90005 Failed to open the index cache file.
    •  BTree_90006 Cannot write to index cache file.
    •  BTree_90007 Key <key name> is not in index cache.
    •  BTree_90009 Error unlocking cache block in group <group>.
    •  BTree_90010 Error locking cache block in group <group>. Increase the cache size.
    •  BTree_90011 Error inserting a row into the foreign key index for group <group>.
    •  BTree_90012 Error inserting a row into the primary key index for group <group>.
    •  BTree_90013 Error: Cannot remove duplicate row.
    •  BTree_90014 Error: Cache manager could not allocate a new block.
  •  BW Messages
    •  BW_41013 Cannot connect to Integration Service <Integration Service name> in domain <domain name>.
    •  BW_41014 The BW Server sent a request to the SAP BW Service that did not include a PowerCenter workflow name.
    •  BW_41020 Connect to SAP gateway failed.
    •  BW_41027 The Integration Service could not prepare the data in row number <row number> for the BW target <target name>.
    •  BW_41031 The SAP BW Service could not open the parameter file <parameter file> for data selection: <data selection>.
    •  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.
    •  BW_41052 The SAP BW Service could not connect to the Integration Service.
    •  BW_41058 The SAP BW Service reached the maximum number of errors trying to connect to the BW system. The SAP BW Service will be shut down.
    •  BW_41065 Workflow Start request failed with message <error message>.
    •  BW_41073 The SAP BW Service received a call to the unsupported function <function>.
    •  BW_41076 Error fetching the SAP BW Service configuration properties: <properties>.
    •  BW_41077 Error initializing service.
    •  BW_41082 The SAP BW Service could not find the Integration Service <Integration Service name> in domain <domain name>.
•  C Message Codes
  •  CFG Messages
    •  CFG_10000 The Service Manager could not enable Domain Configuration because the domain state is invalid.
    •  CFG_10001 The Service Manager is not initialized yet.
    •  CFG_10005 The Service Manager is disabled and cannot accept domain configuration requests.
    •  CFG_10008 A request was received that was missing a required parameter.
    •  CFG_10009 A request was received with wrong <actual object type> parameter (expected: <expected object type>).
    •  CFG_10012 Cannot add an existing domain option group <option group>.
    •  CFG_10013 Domain option group <option group> cannot be found.
    •  CFG_10014 Cannot create an existing folder <folder path>.
    •  CFG_10015 Cannot add an existing linked domain <linked domain name>.
    •  CFG_10017 Cannot delete domain node <node name> because it is the only gateway in the domain.
    •  CFG_10018 The folder <folder path> is not empty.
    •  CFG_10019 The root folder cannot be deleted.
    •  CFG_10020 Cannot change list of nodes associated with Integration Service <service name> while the service is enabled.
    •  CFG_10021 The Service Manager failed to read the domain configuration from <database type> database on <database host>:<database port> with error <error message>.
    •  CFG_10022 Cannot associate service <service name> with repository because: <reason of failure>.
    •  CFG_10023 Cannot unassociate service <service name> with repository because: <reason of failure>.
    •  CFG_10025 Cannot delete grid <grid name> because it is referenced by these services: <list of services>.
    •  CFG_10026 Grid <grid name> contains nodes <list of nodes> that are not defined in the domain.
    •  CFG_10027 Services <list of services> do not exist in the domain.
    •  CFG_10028 Cannot delete linked domain <linked domain name> because it is referenced by these services: <list of services>.
    •  CFG_10029 Linked domain <linked domain name> cannot be found in the domain.
    •  CFG_10030 Cannot add <object name> because the name is already in use within the domain.
    •  CFG_10031 <object name> <type of object> cannot be found in the domain.
    •  CFG_10032 Cannot delete component <component name> of the Service Manager.
    •  CFG_10033 Folder <folder path> already exists.
    •  CFG_10037 Cannot delete license <license name> because services are assigned to it.
    •  CFG_10040 Cannot add linked domain <linked domain name> because it has the same name as the domain.
    •  CFG_10041 Folder path <folder path> does not exist.
    •  CFG_10042 License serial number is already in use.
    •  CFG_10043 Failed to add a license key that expired on <expiration date>.
    •  CFG_10044 Node option group <option group> for node <node the option group belongs to> was not found.
    •  CFG_10045 Cannot add existing node option group <option group> to node <node name>.
    •  CFG_10046 Cannot add existing <type of resource> resource <resource name> to node <node name>.
    •  CFG_10047 <type of resource> resource <resource name> cannot be found on node <node name>.
    •  CFG_10048 User <name of the user> does not have permission on node <node name>.
    •  CFG_10049 Cannot associate a gateway node <node name> without specifying the log directory.
    •  CFG_10050 Cannot switch to or from a gateway node with the update operation.
    •  CFG_10051 User <user name> cannot be found.
    •  CFG_10052 Cannot unassociate node <node name> while it is running.
    •  CFG_10055 The domain configuration database is invalid because: <validation message>.
    •  CFG_10057 Unable to connect to the linked domain <domain name> because: <error message>.
    •  CFG_10059 Cannot associate node <node name> without redefining the node.
    •  CFG_10060 The administrator permissions on the root folder cannot be removed.
    •  CFG_10062 Cannot add service <service name> because license <license name> is not found in the domain.
    •  CFG_10080 The input list must contain a user name followed by at least one object name.
    •  CFG_10081 Object at full path <full path of object> cannot be found in the domain.
    •  CFG_10082 The value <option value> for option <option name> of service <service name> is not valid.
    •  CFG_10083 The operating mode of service <service name> cannot be changed to safe mode while the service is enabled.
    •  CFG_10084 Cannot move the root folder.
    •  CFG_10085 Cannot move a folder to one of its subfolders.
    •  CFG_10086 Cannot perform operation on an unassociated node <node name>.
    •  CFG_10087 Service <service name> contains references to linked domains <list of linked domains> not defined in the domain.
    •  CFG_10088 Node <node name> was modified to be a gateway node in the domain but failed to update node metadata file.
    •  CFG_10089 Node <node name> was modified to be a worker node in the domain but failed to update node metadata file.
    •  CFG_10091 The full path was not specified for object <object name>.
    •  CFG_10095 The Service Manager failed to read the domain configuration from <database type> database with connection string <database connection string> with error <error message>.
    •  CFG_10103 Cannot enable service <service name> with the same name as the domain. Rename your service.
    •  CFG_10104 Cannot add service <service name> with the same name as the domain. Rename your service.
    •  CFG_10105 The code page of an existing Repository Service <Repository Service name> cannot be changed.
    •  CFG_10106 Cannot create an OS profile with the system user name set to root because this may result in a security breach.
    •  CFG_10107 Cannot start the service upgrade process as the following services have already been upgraded to version <service version>: <list of service>
    •  CFG_10110 Cannot upgrade the services because the list of services received by the domain contains one or more services that do not depend on the Repository Service.
    •  CFG_10111 Cannot upgrade services as the list of services received by the domain does not contain one or more dependent services.
    •  CFG_10116 The version of the domain <domain name> is different from the version of the current domain. Upgrade the domain to version <domain version>.
  •  CMD Messages
    •  CMD_35197 The Value <value> for INFA_CLIENT_RESILIENCE_TIMEOUT is invalid. Using default value <value> instead.
    •  CMD_35198 Error: Cannot connect to Integration Service.
  •  CMN Messages
    •  CMN_1003 Server port not specified.
    •  CMN_1006 Failed to connect to repository.
    •  CMN_1008 Internal error.
    •  CMN_1009 Internal error: Failed to execute child process.
    •  CMN_1011 Error allocating system shared memory of <number> bytes for [DTM Buffer Pool]. Error is <system error code>: <system error message>.
    •  CMN_1012 Error: shm_malloc() failed. Unable to allocate the bytes requested.
    •  CMN_1017 Error encountered decrypting password.
    •  CMN_1021 Database driver event.
    •  CMN_1022 Database driver error.
    •  CMN_1023 Database license key not specified.
    •  CMN_1024 Invalid database license key <license key>.
    •  CMN_1026 Incorrect repository version.
    •  CMN_1028 ERROR: Illegal operation on a non-mutex.
    •  CMN_1029 ERROR: Illegal operation on a mutex.
    •  CMN_1030 ERROR: Illegal unlock operation -- mutex not locked.
    •  CMN_1035 Sybase event.
    •  CMN_1036 Sybase error.
    •  CMN_1037 Oracle event.
    •  CMN_1038 Oracle error.
    •  CMN_1040 SQL Server Error.
    •  CMN_1044 DB2 Error.
    •  CMN_1046 ODBC Error.
    •  CMN_1049 PM error.
    •  CMN_1050 PM event.
    •  CMN_1053 Error information.
    •  CMN_1054 Memory allocation error.
    •  CMN_1055 Error preparing SQL statement to fetch lookup data.
    •  CMN_1056 Error executing SQL statement to fetch lookup data.
    •  CMN_1057 Error in fetching lookup data from database.
    •  CMN_1061 ERROR: Process terminating on signal/exception.
    •  CMN_1062 Error creating lookup cache.
    •  CMN_1063 ERROR: Multiple match found in lookup.
    •  CMN_1064 Error in lookup SQL statement prepare.
    •  CMN_1065 Error in lookup SQL statement execute.
    •  CMN_1066 Error in lookup SQL statement fetch.
    •  CMN_1075 ERROR: Data overflow.
    •  CMN_1076 Error creating database connection.
    •  CMN_1077 Lookup table not found in the database.
    •  CMN_1078 Error accessing synchronization object.
    •  CMN_1079 WARNING: Lookup table contains no data.
    •  CMN_1082 ERROR: Invalid lookup condition.
    •  CMN_1083 Error encountered encrypting password.
    •  CMN_1086 <Transformation name>: Number of error exceeded threshold number.
    •  CMN_1087 ERROR: PowerMart Username not specified.
    •  CMN_1088 ERROR: PowerMart Password is not specified.
    •  CMN_1089 ERROR: Invalid lookup connect string.
    •  CMN_1093 ERROR: Invalid join condition supplied.
    •  CMN_1094 ERROR: No valid field from the master relation.
    •  CMN_1095 ERROR: Field name used in join not found in transform definition.
    •  CMN_1096 ERROR: Operator not supported in the join condition.
    •  CMN_1097 ERROR: No valid output field.
    •  CMN_1098 ERROR: Cache Directory may not exist or insufficient privilege/space in the supplied cache directory.
    •  CMN_1099 ERROR: Master and detail relations are flipped from user specification.
    •  CMN_1100 ERROR: A target load order group has at least one Source Qualifier transformation that has been used to provide master as well as detail data.
    •  CMN_1101 ERROR: Alter the mapping and place the target tables violating this constraint in different target load order groups.
    •  CMN_1102 ERROR: No ports in the join condition are connected.
    •  CMN_1103 WARNING: No row found from the master relation. Joiner will not produce any output row.
    •  CMN_1104 ERROR: The conversion from source type to target type is not supported.
    •  CMN_1105 ERROR populating index using the key value from the master relation row.
    •  CMN_1106 ERROR: Index file operation error in Joiner.
    •  CMN_1107 ERROR: Data file operation error in Joiner.
    •  CMN_1108 ERROR: PowerMart product license key not specified.
    •  CMN_1109 ERROR: Invalid PowerMart product license key <key name>.
    •  CMN_1111 Error encountered decrypting PowerMart password.
    •  CMN_1120 Error <error code> getting status of attachment file <file name>.
    •  CMN_1121 Attachment file <file name> not found.
    •  CMN_1122 Attachment file <file name> is not a regular file.
    •  CMN_1123 Error opening attachment file <file name> for read.
    •  CMN_1124 Error reading from attachment file <file name>.
    •  CMN_1125 Error opening temporary email <temporary file name> file for write.
    •  CMN_1126 Error writing to temporary email file (out of disk space?).
    •  CMN_1127 Warning: Error in deleting temporary email file.
    •  CMN_1128 Error executing shell.
    •  CMN_1129 Error sending email.
    •  CMN_1134 This PowerMart Server build does not support database type (Microsoft SQL Server).
    •  CMN_1141 ERROR: Unexpected condition at file <file name> line <line number>. Application terminating. Contact Informatica Global Customer Support for assistance.
    •  CMN_1164 Database driver error. Bulk write initialization failed (blk_init returned failure).
    •  CMN_1555 The mapping was changed after the saved disk cache file was created.
    •  CMN_1557 The precision is different from the saved disk cache.
    •  CMN_1564 The Integration Service data movement mode is different from the saved disk cache.
    •  CMN_1565 The Integration Service code page is different from the saved disk cache.
    •  CMN_1573 Error: Unknown code page <code page ID> for data source <source name>.
    •  CMN_1574 Error: Failed to create locale from code page <code page ID> for data source <source name>.
    •  CMN_1575 The Integration Service sort order is different from the saved disk cache.
    •  CMN_1576 Error: The current lookup index cache size of <number> bytes is too small. Increase the lookup index cache to at least <number> bytes.
    •  CMN_1577 Error: The current lookup index cache size of <number> bytes is too small. Increase the lookup index cache size to at least <number> bytes.
    •  CMN_1579 Input lookup precision is greater than the output lookup precision. Verify that the Lookup transformation and linked transformations have the same port precision.
    •  CMN_1625 ERROR: Joiner <Joiner transformation> has <number> inputs for the master relation. There should only be one master relation.
    •  CMN_1626 ERROR: Joiner <Joiner transformation name> has <number> inputs for the detail relation. There should only be one detail relation.
    •  CMN_1627 Internal error restoring row from cache.
    •  CMN_1628 Joiner <Joiner transformation name> initialization error creating detail input row data.
    •  CMN_1629 Joiner <Joiner transformation name> initialization error creating master input row data.
    •  CMN_1630 ERROR: Unexpected error encountered at file <file name> line <line number>.
    •  CMN_1636 Error occurred aborting row in joiner transformation <transformation name>.
    •  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.
    •  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.
    •  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.
    •  CMN_1645 Error: Failed to get shared access to cache files <cache file name>. [dat/idx] for lookup <Lookup transformation>.
    •  CMN_1646 Error: Failed to get exclusive access to cache files <cache file name>. [dat/idx] for lookup <Lookup transformation>.
    •  CMN_1647 Error: Failed to upgrade to exclusive access for cache files <cache file name> for lookup <Lookup transformation>.
    •  CMN_1650 A duplicate row was attempted to be inserted into a dynamic lookup cache <Lookup transformation name>. The dynamic lookup cache only supports unique condition keys.
    •  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>.
    •  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>.
    •  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>.
    •  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>.
    •  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>.
    •  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.
    •  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.
    •  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>.
    •  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.
    •  CMN_1664 Error: Out of sequence IDs to generate for port <port name> of Lookup <transformation name> for insertion.
    •  CMN_1665 Error: Failed to form key row for insertion in index cache file for Lookup <transformation name>.
    •  CMN_1666 Error: Failed to form data row for insertion in data cache file for Lookup <transformation name>.
    •  CMN_1667 Error: Failed to insert row for Lookup <transformation name>.
    •  CMN_1675 Cache for Lookup <Lookup transformation name> expects lookup override <SQL override> but Cache file <file name> has <SQL override>.
    •  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.
    •  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.
    •  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.
    •  CMN_1683 Error: Static Lookup <lookup> needs to delete a cache file <cache file name> that was created by a Dynamic Lookup <transformation name> in an earlier TLOG using different parameters.
    •  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.
    •  CMN_1686 Error allocating <number of bytes requested> in memory for cache transformation: <transformation name>.
    •  CMN_1687 Error: Cache not enabled for Dynamic Lookup transformation <transformation name>.
    •  CMN_1689 Failed to allocate <number> bytes from process memory for [DTM Buffer Pool].
    •  CMN_1691 Cache expects port <port name> but cache file has it in a different data type and cannot be used. A new cache file will be created.
    •  CMN_1694 Database Event Unable to set DBARITHABORT: Arithmetic exceptions from Microsoft SQL Server will not cancel query execution.
    •  CMN_1695 Database Event Unable to set options: Options cannot be set in Microsoft SQL Server.
    •  CMN_1701 Error: Data for Lookup <transformation name> fetched from the database is not sorted on the condition ports. Please check your Lookup SQL override.
    •  CMN_1702 Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number> <error message>. (UNIX only)
    •  CMN_1703 Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number>. (Windows only)
    •  CMN_1704 Error attaching to system shared memory <ID> for <Load Manager Shared Memory>. Expected to attach at address <address>, but attached at <address>.
    •  CMN_1705 Error attaching to system shared memory <ID> because it has been removed.
    •  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.
    •  CMN_1720 The persistent lookup cache was created in a format that is incompatible with this release.
    •  CMN_1764 Failed to delete file <file name>: Error Msg <error message>.
    •  CMN_1765 Failed to open file <file name>: Error Msg <error message>.
    •  CMN_1766 Failed to seek file <file name>: Error Msg <error message>.
    •  CMN_1767 Failed to ftell file <file name>: Error Msg <error message>.
    •  CMN_1768 Failed to truncate file <file name>: Error Msg <error message>.
    •  CMN_1769 Inconsistent recovery cache.
    •  CMN_1770 Recovery cache consumer is registered more than once.
    •  CMN_1771 The connection <database connection> specified is ambiguous. The connection name exists in both relational and application connections.
    •  CMN_1772 Guaranteed Message Delivery cache directory <directory name> does not exist.
    •  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.
    •  CMN_1774 Error: Logical connection <database connection> in Lookup <Lookup transformation name> is either an invalid connection or it exists in both Relational and Application type connections.
    •  CMN_1775 Recovery cache directory <directory name> is invalid.
    •  CMN_1777 The connection <database connection name> specified can not run SQL query; hence can not be used as a lookup or stored procedure connection.
    •  CMN_1778 Failed to read file <file>: Error Msg <error message>.
    •  CMN_1779 Failed to write file <file>: Error Msg <error message>.
    •  CMN_1780 Guaranteed Message Delivery timestamp was changed, message cache will be cleaned and session will continue running.
    •  CMN_1781 Error: A connection must be specified for $Target when using 3.5 LOOKUP function.
    •  CMN_1782 Error: A connection must be specified for $Source when using 3.5 LOOKUP function.
    •  CMN_1784 Connect string <connection name in Location Information property> too long. Maximum length allowed is <maximum length>.
    •  CMN_1785 Lookup SQL override <Lookup transformation> has references to mapping parameters or variables that cannot be resolved correctly.
    •  CMN_1786 Error: Failed to update row for Lookup <Lookup transformation>.
    •  CMN_1796 An error was encountered while writing prior message(s) to this log file. Those messages may be lost. Please check for available disk space.
    •  CMN_1798 Cache for Lookup <Lookup transformation name> expects <number of> partitions but Cache file <file name> has <number of> partitions.
    •  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.
    •  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.
    •  CMN_1804 Cache cannot be empty when running in recovery mode.
    •  CMN_1806 Failed to get information for file <cache file>. Error message: <error message>.
    •  CMN_1807 Cache version does not match with <version>.
    •  CMN_1808 Cache platform does not match with <platform>.
    •  CMN_1809 Partition number does not match with <number>.
    •  CMN_1813 ERROR: Some cache files with name prefix <name prefix> for Lookup <Lookup transformation name> are missing or invalid.
    •  CMN_1836 Error: Data for Lookup fetched from the file is not sorted on the condition ports.
    •  CMN_1919 External loader error. Error getting Teradata loader information.
    •  CMN_1920 External loader error. Error getting Flat-File information required for Loader.
    •  CMN_1921 External loader error. Control File will be generated for First Partition Only.
    •  CMN_1922 External loader error. Update is not valid for target instance <target definition name> since no primary key(s) is mapped to the target.
    •  CMN_1923 External loader error. Update is not valid for target instance <target definition name> since no non-key field(s) is mapped to the target.
    •  CMN_1924 External loader error. Delete is not valid for target instance <target definition name> since no primary key(s) is mapped to the target.
    •  CMN_1926 Error: Teradata external loader requires a primary key on table <target table name> when using load mode <load mode>.
    •  CMN_1927 Error: Unable to set null character.
    •  CMN_1928 External loader error. Upsert is not valid for target instance <target definition name> since update is not valid for the target.
    •  CMN_1929 External loader error <error message>.
    •  CMN_1986 Service <service name> encountered an error while communicating with Licensing Service: <error code and message>.
    •  CMN_1989 Service <service name> is not licensed to execute on node <node name>.
    •  CMN_2005 Unable to create log file <log file name>: <error message>.
    •  CMN_2006 Unable to create log file <log file name>.
    •  CMN_2018 Error: Failed to expand call text <text> for Stored Procedure transformation <transformation name>.
    •  CMN_2028 The Integration Service cannot parse user variable at position <user variable position> in file <file>.
    •  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.
    •  CMN_17800 Property <property name> is missing.
    •  CMN_17802 <Input/output port> port for <port number> not found.
    •  CMN_17804 Port <port number>: The transformation type <transformation datatype> is incompatible with SAP type <SAP datatype>.
    •  CMN_17807 Data conversion error for port <port number> with data <data>.
    •  CMN_17808 Data conversion error for port <port number>.
    •  CMN_17809 Message from SAP LastError: <error message>.
    •  CMN_17810 Property <property> is invalid.
    •  CMN_17815 Memory allocation error.
    •  CMN_17816 Error when trying to install SAP structure <structure>.
    •  CMN_17817 Connection to SAP system is lost.
    •  CMN_17818 Error in appending a line to SAP internal table.
    •  CMN_17825 The value for property <property> is not specified.
    •  CMN_17829 Failed to connect to SAP system.
    •  CMN_17831 Incorrect source file name may have been specified in the session.
    •  CMN_17833 Binary datatypes are not supported in RFC/BAPI function mappings. Disconnect port <port name> in the mapping.
    •  CMN_17838 SAP code page <code page> is not compatible with the connection code page <code page>.
    •  CMN_17839 SAP code page <code page> is not compatible with the Integration Service code page.
    •  CMN_17840 Data <data> overflow at port <port number>. See below to find the row with error.
    •  CMN_17848 The value for the property <TypeOfAEP> should be <value>.
    •  CMN_17851 Cannot get target property <property>.
    •  CMN_17853 Error threshold for the session is reached.
    •  CMN_17856 Control field <control field> cannot have length greater than the precision <value>.
    •  CMN_65011 Lookup instance <name> uses a dynamic cache. However, the workflow is configured to run concurrently with the same instance name. This combination is not supported.
    •  CMN_65013 Helper process for pmimprocess failed to initialize: <error message>.
    •  CMN_65014 Integration Service failed to spawn child process: <error message>.
    •  CMN_65015 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.
    •  CMN_65016 Child process <child process id> terminated unexpectedly.
    •  CMN_65017 The Integration Service could not use operating system profiles because pmimprocess was not configured.
    •  CMN_65018 The workflow failed because the operating system user name specified in the operating system profile is invalid.
    •  CMN_65019 Error using operating system profiles to run a workflow. Contact Informatica Global Customer Support.
    •  CMN_65020 pmimprocess failed to append library path environment variable.
    •  CMN_65025 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>.
    •  CMN_65040 Recovery file <recovery file name> is inconsistent. The size <recovery file size> is less than the minimum size of 4 bytes.
    •  CMN_65050 The Integration Service could not log in to the SMTP server.
    •  CMN_65051 The Integration Service could not send an email to the SMTP server.
    •  CMN_65052 The timeout period expired before the Integration Service could connect to the SMTP server.
    •  CMN_65057 The Integration Service could not locate the SMTP server because the server address is invalid.
    •  CMN_65070 ERROR: Update dynamic cache condition is not valid for Lookup transformation.
    •  CMN_65071 Error: Lookup transformation[{0}] and Lookup transformation [{1}] with cache file name prefix [{2}] share the same named cache but have but have incompatible match policies.
  •  CNX Messages
    •  CNX_53117 Failed processing request ID <request ID>, req opcode <request operation ID>, reply opcode <reply operation ID>. Return Status: <return status>.
    •  CNX_53119 Thread received a notification to force the closing of client connection.
  •  CONF Messages
    •  CONF_45006 Error: The Service Manager could not validate the Integration Service <Integration Service Name> because the Integration Service does not have an associated repository.
  •  CSE Messages
    •  CSE_34005 The Integration Service could not set the encryption key for encryption.
    •  CSE_34010 The Integration Service could not set the encryption key for decryption.
    •  CSE_34039 The Integration Service failed to decrypt data.
    •  CSE_34040 The Integration Service failed to encrypt data.
    •  CSE_34041 The Integration Service failed to compress data.
    •  CSE_34042 The Integration Service failed to decompress data.
  •  CTSDK Messages
    •  CTSDK_43000 Couldn't load the library <library name> for plug-in <plug-in name>.
    •  CTSDK_43001 Cannot load the library <library name>.
    •  CTSDK_43002 Couldn't find address of function <function name> for plug-in <plug-in name>.
    •  CTSDK_43003 Couldn't find address of function <function name>.
•  D Message Codes
  •  DBGR Messages
    •  DBGR_25011 No conversion to string possible.
    •  DBGR_25013 Cannot modify dependent port.
    •  DBGR_25015 Field not found.
    •  DBGR_25016 Default condition allowed on input, in/out or output ports only.
    •  DBGR_25017 Parser init failed.
    •  DBGR_25018 Invalid port condition.
    •  DBGR_25019 Breakpoint already exists.
    •  DBGR_25020 Breakpoint not found.
    •  DBGR_25021 No such target ID.
    •  DBGR_25022 Alloc Bkpt list failed.
    •  DBGR_25024 Cannot modify data for transformations at this stage of execution.
    •  DBGR_25025 Cannot modify data for transformations other than the current one.
    •  DBGR_25026 Rowtype change not allowed for this transformation.
    •  DBGR_25027 Cannot modify port.
    •  DBGR_25028 Use of port <port name> in debug condition is invalid. Maybe it is not connected.
    •  DBGR_25029 Use of port <port name> as value in debug condition is invalid. Maybe it is not connected.
    •  DBGR_25030 No such transformation in any pipeline.
    •  DBGR_25033 Error: Socket sendRequest for ident failed for reqType: <number>.
    •  DBGR_25034 Error: Socket set poll failed for reqType: <number>.
    •  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.
    •  DBGR_25036 Error: Socket open failed for reqType: <number>.
    •  DBGR_25040 Error: Invalid groupId <number> specified for modifying router transformation.
    •  DBGR_25041 Error: Invalid groupIndex <number> resulted from groupId <number> specified for modifying Router transformation.
    •  DBGR_25044 Data Type mismatch: <value> cannot be used in a condition with port <port name>.
    •  DBGR_25045 Error in breakpoint condition: Port <port name> and Port <port name> are from different groups.
    •  DBGR_25046 Error in breakpoint <number> for transformation <transformation name>. Reason is <reason>.
    •  DBGR_25047 Error in global breakpoint <number>. Reason is <reason>.
    •  DBGR_25048 Breakpoint condition cannot be specified for binary port <port> <port name>.
    •  DBGR_25049 Transformation has not received any data yet.
    •  DBGR_25050 Port <port name> used in expression is unconnected and has no default value.
    •  DBGR_25059 Failed to create a socket to listen for connections from the client <PowerCenter Client machine name>.
    •  DBGR_25060 Failed to find an available port between <DebuggerMinPort> and <DebuggerMaxPort> to listen for connections from the client <PowerCenter Client machine name>.
    •  DBGR_25061 Failed to notify client of the port we are listening on.
    •  DBGR_25062 Failed to notify client of the port we are listening on: no RepServer connection is available.
    •  DBGR_25068 Failed to get connection from the Designer. Check network/firewall settings.
  •  DMI Messages
    •  DMI_17501 Error initializing the tree builders for partition <partition>.
    •  DMI_17503 At least one field other than primary and foreign keys must be connected for each group.
    •  DMI_17504 Error creating input row for group <group>.
    •  DMI_17505 Error setting data for the field: <field>.
    •  DMI_17506 NULL data obtained for primary or foreign key fields.
    •  DMI_17507 NULL data obtained for all connected fields for the segment <segment name>.
    •  DMI_17508 Error building the tree.
    •  DMI_17509 Unknown error traversing the tree.
    •  DMI_17511 <Number> orphan rows were received by the SAP DMI Prepare transformation.
    •  DMI_17512 Orphan row <row> received in group <group> with primary key <primary key> and foreign key <foreign key>.
    •  DMI_17513 <Value> duplicate rows were received by the SAP DMI Prepare transformation.
    •  DMI_17514 Primary key received for duplicate error row <row>: <value>.
    •  DMI_17515 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>.
    •  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>.
    •  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>.
    •  DMI_17518 Data <data> overflow at port <port number>. If the error threshold is not met, the row will be sent through the ErrorDMIData port.
    •  DMI_17519 Error getting data for the field.
    •  DMI_17520 The SAP DMI Prepare transformation has an unconnected input group. All input groups must be connected for the transformation.
    •  DMI_17525 Cache folder specified for the SAP DMI Prepare transformation <transformation name> is invalid.
    •  DMI_17526 The Integration Service could not access the cache block in group <group>. Increase the cache size.
    •  DMI_17527 The SAP DMI Prepare transformation did not receive data for the DMI object.
  •  DOM Messages
    •  DOM_10009 Cannot find the specified domain <linked domain name> from domain <current domain name>.
    •  DOM_10013 Unable to disable service <service name>.
    •  DOM_10166 Unable to login node <node name> with the domain.
    •  DOM_10174 Unable to update the operating mode to <operating mode> on service <service name>.
    •  DOM_10176 Unable to queue the alert of type <alert type> for object <object name> with alert message <alert message> to the alert service.
    •  DOM_10181 Unable to communicate with node <node name> at host <host name> and port <port number> from the master node <node name>.
    •  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>.
    •  DOM_10184 The Integration Service cannot use operating system profiles on Windows node <node name> in <service name>.
    •  DOM_10185 User <user name> in security domain <security domain name> does not have the Administrator role required to shut down the domain.
    •  DOM_10188 Unable to start service <service name> of version <service version> on the node <node name>. This node is not configured to run this service version.
    •  DOM_10189 Unable to start the service <service name> of service version <service version> as the associated services <service names> belong to a different version.
  •  DS Messages
    •  DS_10008 Cannot find node <name> specified in the service lookup request in domain <name>.
    •  DS_10009 Cannot find domain <name> specified in the service lookup request.
    •  DS_10012 The disable mode specified <mode> is invalid to disable service <service name>.
    •  DS_10036 Service <name> is not available.
    •  DS_10037 Service <name> is not available on node <name>.
    •  DS_10059 The requested service <name> is not running.
  •  DSP Messages
    •  DSP_20307 Error fetching node information from Configuration Service (domain name <domain>, node name <node>). Error message: <message text>.
•  E Message Codes
  •  EB Messages
    •  EBRDR_13003 The PowerCenter Integration Service could not connect to Oracle E-Business Suite.
    •  EBRDR_13005 The PowerCenter Integration Service could not generate or parse the SQL query.
    •  EBRDR_13007 Join Type not defined.
    •  EBRDR_13009 The PowerCenter Integration Service could not execute the query.
    •  EBRDR_13037 Number of fields in the SQL Query is less than the number of ports connected from the Application Source Qualifier to the target instance.
    •  EBWRT_32006 Specified schema list is incorrectly formatted.
    •  EBWRT_32026 The PowerCenter Integration Service could not initialize Oracle Applications environment.
    •  EBWRT_32027 The PowerCenter Integration Service could not submit the concurrent program request.
    •  EBWRT_32028 The Integration Service could not determine the application ID of <application name>.
    •  EBWRT_32031 Error creating wait procedure. Wait functionality will be unavailable.
    •  EBWRT_32034 <Request ID> completed with error.
    •  EBWRT_32035 <Request ID> was terminated unexpectedly.
    •  EBWRT_32069 <partition number> The PowerCenter Integration Service could not initialize the Oracle application because no language is configured for the target instance <target name>.
    •  EBWRT_32070 <partition number> The PowerCenter Integration Service could not initialize the Oracle application because the user name is not specified for the target instance <target name>.
    •  EBWRT_32071 <partition number> The PowerCenter Integration Service could not initialize the Oracle application because the responsibility name is not specified for the target instance <target name>.
    •  EBWRT_33007 The PowerCenter Integration Service could not write data to the temporary file.
    •  EBWRT_35001 The PowerCenter Integration Service could not create hierarchy.
    •  EBWRT_35002 The sum of duplicate row count, orphan row count, and other error count exceeded the error threshold value.
    •  EBWRT_36001 The PowerCenter Integration Service could not get field list.
    •  EBWRT_36010 The PowerCenter Integration Service could not determine User ID of <user name>.
    •  EBWRT_36011 The PowerCenter Integration Service could not determine Responsibility ID of <responsibility>.
    •  EBWRT_36012 The PowerCenter Integration Service could not determine Security Group ID of <security group>.
    •  EBWRT_36013 The Integration Service could not determine Server ID of <server name>.
    •  EBWRT_36066 <Port name> port of group <group name> is not linked.
    •  EBWRT_36070 Incorrect language <language>.
    •  EBWRT_36072 The PowerCenter Integration Service could not write data for GPK__<port name> = <data> and GFK__<port name> = <data>.
    •  EBWRT_40001 The PowerCenter Integration Service could not connect to Oracle E-Business Suite.
    •  EBWRT_40003 The PowerCenter Integration Service encountered a memory allocation error.
    •  EBWRT_40005 The PowerCenter Integration Service could not execute the query.
  •  EP Messages
    •  EP_13001 Invalid conversion.
    •  EP_13002 Error freeing external module.
    •  EP_13003 Cannot prepare common external procedure information.
    •  EP_13004 Cannot prepare pipeline external procedure information.
    •  EP_13005 Cannot initialize Informatica-style external procedure.
    •  EP_13006 NULL external module name.
    •  EP_13007 Cannot create external module manager.
    •  EP_13008 Cannot load external module.
    •  EP_13010 Cannot create external module object.
    •  EP_13011 NULL external procedure name.
    •  EP_13012 Cannot get external procedure signature.
    •  EP_13013 Number of ports in transform does not match number of formal arguments.
    •  EP_13014 Multiple return ports defined for transform.
    •  EP_13015 Multiple return arguments defined for external procedure.
    •  EP_13020 External procedure has return value, but transform does not.
    •  EP_13021 Transform has return value, but external procedure does not.
    •  EP_13022 External procedure return value is not last argument.
    •  EP_13023 Transform return value is not last port.
    •  EP_13024 Port lookup failed.
    •  EP_13025 Not all input params found.
    •  EP_13026 Multiple connections to input port.
    •  EP_13027 Decimal overflow error.
    •  EP_13028 Unknown error while converting datatype.
    •  EP_13030 Exception error was thrown from external procedure <external procedure name>.
    •  EP_13033 Cannot initialize COM-style external procedure.
    •  EP_13034 Unknown COM error.
    •  EP_13035 Cannot initialize column/parameter mapping.
    •  EP_13036 Cannot find all input parameters.
    •  EP_13037 Cannot allocate memory.
    •  EP_13038 Cannot initialize external procedure.
    •  EP_13039 Buffer initialization callback failed.
    •  EP_13040 Invalid programmatic identifier.
    •  EP_13041 Programmatic identifier not found in registry.
    •  EP_13042 Cannot map programmatic identifier to CLSID.
    •  EP_13043 Cannot create string representation of CLSID.
    •  EP_13044 Cannot create instance of component object.
    •  EP_13045 Cannot get dispatch interface for component object.
    •  EP_13046 IDispatch::Invoke failed.
    •  EP_13047 Cannot open registry key HKEY_CLASSES_ROOT\\CLSID\\clsid\\Typelib.
    •  EP_13048 Cannot get registry value for HKEY_CLASSES_ROOT\\CLSID\\clsid\\Typelib.
    •  EP_13049 Cannot create CLSID from programmatic identifier.
    •  EP_13050 Cannot open registry key HKEY_CLASSES_ROOT\\TypeLib\\libid.
    •  EP_13051 Cannot open registry key HKEY_CLASSES_ROOT\\TypeLib\\libid.
    •  EP_13052 Cannot load type library.
    •  EP_13053 Cannot get type library attributes.
    •  EP_13054 Cannot open registry key HKEY_CLASSES_ROOT\\CLSID\\clsid\\server type.
    •  EP_13055 Cannot get registry value for HKEY_CLASSES_ROOT\\CLSID\\clsid\\<server type>.
    •  EP_13056 Cannot get component object type information.
    •  EP_13057 Cannot get component object type attributes.
    •  EP_13058 Cannot get reference type of interface.
    •  EP_13059 Cannot get type information of interface.
    •  EP_13060 Cannot get type attributes of interface.
    •  EP_13061 Cannot get function description.
    •  EP_13062 Cannot get names of function and its arguments.
    •  EP_13063 Cannot get IDs of function parameters.
    •  EP_13064 Cannot get function type information.
    •  EP_13065 NULL BSTR.
    •  EP_13066 Error converting COM datatype to Informatica internal datatype.
    •  EP_13067 Error converting Informatica internal datatype to COM datatype.
    •  EP_13068 Unsupported COM type.
    •  EP_13069 Cannot initialize COM.
    •  EP_13070 COM-style external procedures not supported on non-Windows platforms.
    •  EP_13071 The Informatica-style transformation has a port with an invalid datatype.
    •  EP_13072 The Informatica-style external procedure has a parameter with an invalid datatype.
    •  EP_13073 Informatica external procedure log message.
    •  EP_13074 Informatica external procedure error message.
    •  EP_13075 The version of the Informatica external module is not supported by the server.
    •  EP_13083 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.
    •  EP_13084 Data conversion error.
    •  EP_13089 Error converting initialization parameter to correct data type for constructor parameter.
    •  EP_13103 <External Procedure transformation>: Fatal error returned from external procedure <external procedure>.
    •  EP_13124 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.
    •  EP_13261 Fatal Error: It is illegal to set pass thru port when the transformation scope is not ROW or when the data access mode is ARRAY for active Custom Transformation.
    •  EP_13262 Fatal Error: It is illegal to set default row strategy to pass thru when the transformation scope is not ROW or when the data access mode is ARRAY for active Custom Transformation.
    •  EP_13263 Fatal Error: It is illegal to call INFA_CTASetInputErrorRow when the data access mode is not ARRAY.
    •  EP_13264 Fatal Error: It is illegal to call INFA_CTGetRowStrategy outside inputRowNotification.
    •  EP_13265 Fatal Error: It is illegal to call INFA_CTGetRowStrategy when the data access mode is ARRAY.
    •  EP_13266 Fatal Error: It is illegal to call INFA_CTOutputNotification outside inputRowNotification when the transformation scope is ROW.
    •  EP_13267 Fatal Error: Invalid block size is set for OutputNotification.
    •  EP_13268 Fatal Error: It is illegal to call INFA_CTASetOutputNumRowsMax at run-time.
    •  EP_13269 Fatal Error: Invalid block size is being passed to INFA_CTASetOutputNumRowsMax.
    •  EP_13270 Fatal Error: Downstream Transformations have encountered a fatal error. Please refer to session log.
  •  EB Messages
    •  ESSBASEWRT_203044 Failed to create the error log file directory.
  •  EXP Messages
    •  EXP_19007 Date function error.
    •  EXP_19108 The Integration Service failed to parse the date format <date format string>.
    •  EXP_19138 The Integration Service failed to parse the date format <unit portion of date format>.
    •  EXP_19145 Invalid date value string: <date format string>.
    •  EXP_19160 Failed to find version API <function name> in module <module name>.
    •  EXP_19161 Version API <function name> in module <module name> failed.
    •  EXP_19162 Module <module name> interface version <version number> is incompatible with framework version <version number>.
    •  EXP_19163 Failed to find module API <function name> in module <module name>.
    •  EXP_19164 Module API <function name> in module <module name> failed.
    •  EXP_19165 Module init for <function name> failed: <error message>.
    •  EXP_19166 Failed to find validation API <function name> in module <module name>.
    •  EXP_19167 Failed to find function API <function name> in module <module name>.
    •  EXP_19168 Failed to find function instance API <function name> in module <module name>.
    •  EXP_19169 Module deinit for <function name> failed: <error message>.
    •  EXP_19170 Failed to get validation interface for <function name>.
    •  EXP_19171 Failed to get function interface for <function name>.
    •  EXP_19172 Failed to get function instance interface for <function name>.
    •  EXP_19173 Failed to initialize function for <function name>: <error message>.
    •  EXP_19174 Failed to deinitialize function for <function name>: <error message>.
    •  EXP_19175 Function validation for <function name> failed: <error message>.
    •  EXP_19176 Failed to get process row API for <function name>.
    •  EXP_19177 Failed to initialize function instance for <function name>: <error message>.
    •  EXP_19178 Failed to deinitialize function instance for <function name>: <error message>.
    •  EXP_19179 Invalid datatype specified for return value.
    •  EXP_19180 Process row failed for function <function name>: <error message>.
    •  EXP_19181 Failed to get validation functions for <function name>.
    •  EXP_19182 User-defined function <user-defined function> has a cyclic dependency. Call stack is <call stack>.
    •  EXP_19183 User-defined function <user-defined function> uses an aggregator function.
    •  EXP_19185 Compilation for the user-defined function <user-defined function> failed.
    •  EXP_19186 <<Expression Fatal Error: user-defined function>> <token>: <error message>. <sub-expression>.
    •  EXP_19187 <<Expression Error: user-defined function>> <token>: <error message>. <sub-expression>.
    •  EXP_19188 <<Expression Warning: user-defined function>> <token>: <error message>. <sub-expression>.
    •  EXP_19189 Error in fetching metadata for the user-defined function <user-defined function>.
    •  EXP_19190 Error: Argument mismatch for user-defined function <user-defined function>
    •  EXP_19191 Argument name for expression must start with an x or an X.
    •  EXP_19192 Argument number is too large.
    •  EXP_19193 Cannot get argument index from argument name.
    •  EXP_19194 Argument index <index number> exceeds the expected number of arguments, <number>, in the expression.
    •  EXP_19195 Error: A non-callable user-defined function <user-defined function> is being called directly in the expression.
    •  EXP_19197 Error: The Designer cannot find function <function name>. The function name may be incorrect.
    •  EXP_20010 Integration Service failed to parse the date format <date format>. Expected format is seconds and above.
    •  EXP_20011 Date function error. Expected format is seconds and above.
  •  EXPFN Messages
    •  EXPFN_34016 Invalid number passed for conversion.
    •  EXPFN_34017 Failed to convert number to decimal base.
•  F Message Codes
  •  FEXP Messages
    •  FEXP_87001 The following system error occurred opening the file <file name>: <error number>: <error message>.
    •  FEXP_87004 Process <ID number> exited with error <FastExport error code>.
    •  FEXP_87005 Process <ID number> exited due to receipt of signal <number>.
    •  FEXP_87009 The following system error occurred spawning the process <ID number>: <error number>: <error message>.
    •  FEXP_87015 The following system error occurred reading the output file: <error number>: <error message>.
    •  FEXP_87016 Received unexpected data.
    •  FEXP_87017 Received unexpected EOF.
    •  FEXP_87018 The following system error occurred closing the file <file name>: <error number>: <error message>.
    •  FEXP_87024 Problem in line number <line number> in code page map file <file name>. Please check the file format specified in file.
    •  FEXP_87026 The following system error occurred when the Integration Service tried to get the values of session attributes: [{0}].
  •  FR Messages
    •  FR_3000 Error opening file <file name>. Operating system error message <error message>.
    •  FR_3002 Error reading file <file name>. Operating system error message <error message>.
    •  FR_3013 Error setting field delimiter string.
    •  FR_3015 Warning! Row <row ID>, field <name>: Data was truncated.
    •  FR_3016 Record length <record ID> is longer than line sequential buffer length <number> for <string>.
    •  FR_3023 Error in opening ftp connection.
    •  FR_3024 Error in transferring remote file.
    •  FR_3029 Delimited file attribute error: escape character cannot be the same as quote character.
    •  FR_3030 Delimited file attribute error: delimiters cannot contain quote character.
    •  FR_3031 Delimited file attribute error: delimiters cannot contain escape character.
    •  FR_3032 Delimited file attribute error: must specify at least one delimiter.
    •  FR_3033 Delimited file reader: Warning! Missing matching quote character in column <column name> of file <file name>. Reading till the end of line for the column.
    •  FR_3034 Delimited file reader: Warning! Skipped extra character(s) after the closing quote of column <column name> in file <file name>.
    •  FR_3035 Error opening file NULL. Operating system error message.
    •  FR_3036 Error: Escape character <escape character value> is not in Latin1 code page in ASCII data movement mode.
    •  FR_3037 Error: Field delimiter string has at least one character <delimiter value> that is not in Latin1 code page in ASCII data movement mode.
    •  FR_3038 Error: Escape character <escape character value> is invalid in current file code page <code page name> in UNICODE data movement mode.
    •  FR_3039 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.
    •  FR_3041 Error: Invalid code page <code page name> for delimited flat file.
    •  FR_3043 Error: Using EBCDIC-based Multibyte code page <code page name> in ASCII data movement mode is invalid.
    •  FR_3045 Error: Code page <code page ID> not found. Please install it first.
    •  FR_3046 Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width boundary for field <field name>.
    •  FR_3047 Error: Invalid code page <code page name> for fixed-width flat file.
    •  FR_3048 Error: Null character <null character value> is invalid in current file code page <code page name> in Unicode data movement mode.
    •  FR_3049 Error: Null character <null character value> is not in Latin1 code page in ASCII data movement mode.
    •  FR_3050 Error: Invalid code page <code page name> for fixed-width VSAM file.
    •  FR_3051 Error: Invalid binary null character <null character value>. The decimal value is not between 0 and 255.
    •  FR_3053 Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width boundary for <bytes to skip between records>. Next row/record will also be an error.
    •  FR_3054 Error! Remaining data <string data> in non-repeating, binary null field, in fixed-width file <file name> does not end at the fixed-width boundary for field <field name>.
    •  FR_3056 Error reading from file <file name>.
    •  FR_3057 Error: Insufficient data for fixed-width flat file or fixed-width VSAM file. Row data is <row data>.
    •  FR_3058 Error processing COBOL file: cannot parse the input [numeric character in <data> at position <position> has to be in the Latin1 code page].
    •  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).
    •  FR_3060 Error processing record <record name> in file <file name>: Conflicting shift states at position <position number, referring to byte offset into the row> when interpreting multiple redefines.
    •  FR_3061 Error opening WebSphere MQ queue. Operating system error message.
    •  FR_3064 Warning: Last row in file is not complete.
    •  FR_3065 Row <row number>, field <column name>: Invalid number - <column data>. The row will be skipped.
    •  FR_3066 Error: Date format string has at least one character decimal value=<number> that is not in Latin1 codepage in ASCII data movement mode.
    •  FR_3067 Row <row number>, field <column name>: Invalid date - <column data>. The row will be skipped.
    •  FR_3068 Invalid date format provided <date format>.
    •  FR_3069 Error: The character ‘<character>’ is used as a delimiter and a thousands separator for field <column name>.
    •  FR_3070 Error: The character ‘<character>’ is used as a delimiter and a decimal separator for field <column name>.
    •  FR_3072 Error: Flat file <file name> cannot be processed for reading.
    •  FR_3074 Error at row <row number>. A multibyte character spans over two fields or two lines. Record will be skipped.
    •  FR_3075 Error: Source file type cannot be indirect for an MQ associated source qualifier.
    •  FR_3077 Fatal Error: The column <column name> has corrupt formatting information. Resave the information in the repository.
    •  FR_3078 Fatal error: Cannot flush an incomplete row in real time.
    •  FR_3085 ERROR: Row <row number>: <character>-th character is a null character, which is not allowed in a text input file <file name>.
    •  FR_3107 ERROR: The character <character> is used as both a column delimiter and a row delimiter.
    •  FR_3108 ERROR: DSQ <Source Qualifier name> UCS-2 code page UTF-16BE or UTF-16LE are not supported with this type of file.
    •  FR_3110 Error in opening SFTP connection.
    •  FR_3111 Error in transferring remote files over SFTP.
    •  FR_3115 Error: Conflicting settings for NULL handling are specified for the delimited file source <source name>.
    •  FR_3116 Error: Invalid NULL replacement character is specified for the delimited file source <source name>.
    •  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.
  •  FTP Messages
    •  FTP_14002 Unable to transfer file using FTP because the TCP/IP address for the specified host could not be obtained.
    •  FTP_14003 Unable to transfer file using FTP because Integration Service could not create a socket.
    •  FTP_14004 Unable to transfer the file using FTP because socket option could not be set.
    •  FTP_14005 Unable to transfer the file using FTP because the Integration Service could not connect to the FTP server.
    •  FTP_14006 Unable to transfer the file using FTP because the Integration Service cannot read the remote file.
    •  FTP_14007 Unable to transfer the file using FTP because the format of the FTP response is not expected. The FTP server is not supported.
    •  FTP_14008 Error closing FTP connection.
    •  FTP_14009 Unable to transfer file using FTP. Could not log in due to invalid user.
    •  FTP_14010 Unable to transfer the file using FTP. Could not log in due to rejected password.
    •  FTP_14011 Unable to transfer file using FTP. Connect request rejected by the FTP server.
    •  FTP_14012 Unable to transfer file using FTP. FTP command <command name> rejected by FTP server.
    •  FTP_14017 Unable to transfer file local file <file name> using FTP.
    •  FTP_14018 Unable to transfer file using FTP. Error reading local file.
    •  FTP_14019 Unable to transfer file using FTP file. Error writing to local file.
    •  FTP_14020 Unable to delete file. FTP DELE command rejected by FTP server.
    •  FTP_14024 FTP host name <host name> has incorrect format. Specify <hostname> or <hostname>:<port> where 0 <port< 65536.
    •  FTP_14040 FTP Socket <socket number> timeout. The FTP server has not responded in time. Verify the FTP server is running, or increase the FTP timeout value.
    •  FTP_14046 Cannot reconnect to FTP server at <FTP host>: <control port number> within retry period.
    •  FTP_14047 The source file <file name> or its timestamp was changed after the previous read. Session should now terminate.
    •  FTP_14048 FTP server does not support the FTP command <FTP command>. Resilience is disabled.
    •  FTP_14049 FTP server does not support the FTP command <FTP command>. Cannot restart file transfer to FTP server.
    •  FTP_14050 DTM buffer does not contain enough data to restart file transfer. Terminating session.
    •  FTP_14055 A socket <socket number> failure is encountered: <error text>.
    •  FTP_14056 High availability license is absent. Retry period specified for Integration Service connection to the FTP server is ignored.
    •  FTP_14057 Unable to transfer files using SFTP because the Integration Service could not get the TCP/IP address for the specified host.
    •  FTP_14058 Unable to transfer files using SFTP because the Integration Service could not create a socket.
    •  FTP_14059 Unable to transfer file using SFTP because the Integration Service could not connect to SFTP server.
    •  FTP_14060 SFTP host name <host name> has incorrect format. Specify <host name>; or <host name>:<port> where 0<port<65536.
    •  FTP_14061 Unable to transfer file local file <file name> using SFTP.
    •  FTP_14062 Unable to transfer file using SFTP. Error reading local file.
    •  FTP_14063 Unable to transfer file using SFTP. Error writing to local file.
    •  FTP_14064 Unable to delete the remote file <file name> over SFTP: <system error>.
    •  FTP_14065 Failed to initialize SSH2 session (transport layer) with SFTP server: <system message>.
    •  FTP_14066 Authentication with the remote SFTP server failed: <system message>.
    •  FTP_14067 Failed to initialize SFTP subsystem: <library message>.
    •  FTP_14068 Unable to open the remote file <file name> over SFTP: <system message>.
    •  FTP_14074 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.
    •  FTP_14081 Remote SFTP server is not responding.
    •  FTP_14083 Error: The remote file name for the SFTP connection <connection name> was not specified.
    •  FTP_14084 Unable to access the private key or public key file. Verify that the correct file path was specified.
•  H Message Codes
  •  HIER Messages
    •  HIER_28004 XML Reader Error: <error text>.
    •  HIER_28020 DTM buffer block is filled, and we can't send the block yet. Need to use heap memory to hold data.
    •  HIER_28028 Fatal Error: Could not allocate memory from heap.
    •  HIER_28031 There are two fields pointing to the same XML node, but the datatypes and lengths do not match.
    •  HIER_28032 Error: There are no fields in any of the groups defined that have a reference to a node in the XML tree.
    •  HIER_28034 Could not retrieve a block from the DTM.
    •  HIER_28041 Couldn't open indirect file <file name>.
    •  HIER_28043 Reader failure: The node <element name> occurs multiple times. This node was marked in the schema as occurring one or less times.
    •  HIER_28044 Reader failure: The root node for the given XML does not match the root node in the repository.
    •  HIER_28045 Out of range error: <element name>.
    •  HIER_28051 Read invalid number <value> for XML path <path name>.
•  I Message Codes
  •  IDM Messages
    •  IDM_24007 The Data Masking transformation could not read the highgroup.txt file.
    •  IDM_24013 Failed to mask: <string>. Using default value from defaultValue.xml as output.
    •  IDM_24023 The Data Masking transformation failed to initialize the XML parser.
    •  IDM_24030 The Data Masking transformation failed to mask the date.
    •  IDM_24036 The Data Masking transformation failed to mask the number.
    •  IDM_24038 The Data Masking transformation failed to mask the string.
    •  IDM_24039 The Data Masking transformation failed to create the masking object.
    •  IDM_24045 The Data Masking transformation failed to read the data masking rules.
    •  IDM_24051 The Data Masking transformation failed to create a masking rule.
    •  IDM_24055 Seed is not between 1 and 1000. Using default value for seed.
    •  IDM_24056 Seed defined in the Data Masking default file is not between 1 and 1000. Using 725 as value for seed.
    •  IDM_24057 Failed to mask SSN: <number>. The SSN is invalid.
    •  IDM_24058 Transformation failed to evaluate expression <expression>.
    •  IDM_24059 Expression parse fatal error; Failed to parse expression <expression>. Should be: Fatal error while parsing Data Masking transformation expression.
    •  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.
    •  IDM_24061 No connection information for the relational dictionary has been specified.
    •  IDM_24062 No connection information for storage has been specified.
    •  IDM_24063 Storage table does not exist. Create the storage table before running a session.
    •  IDM_24064 Size of the dictionary is zero. Unable to select a masked value.
    •  IDM_24065 Unable to select a unique masked value from the dictionary.
    •  IDM_24066 Unable to select a masked value from the dictionary.
    •  IDM_24067 The dictionary <dictionary name> is unavailable in the connection provided.
    •  IDM_24068 The dictionary <dictionary name> is unavailable in the $PMLookupFileDir.
    •  IDM_26001 Invalid credit card number length: <number>.
    •  IDM_26002 Could not mask credit card number: <number>.
    •  IDM_26003 Failed to remove delimiter from credit card number: <number>.
    •  IDM_26004 Bounds and blurring do not generate valid range of values for <source>.
    •  IDM_26005 Invalid source date.
    •  IDM_26006 Invalid input IP address: <IP address>.
    •  IDM_26007 Invalid input SSN Format: <SSN >.
    •  IDM_26008 Invalid input URL Format: <URL >.
    •  IDM_26009 License for Data Masking transformation has not been enabled.
    •  IDM_26010 Invalid input email: <email>.
    •  IDM_26011 Invalid input phone: <phone number>.
  •  IDOC Messages
    •  IDOC_17601 Received a call to an unsupported function <function>.
    •  IDOC_17605 Invalid value specified for IDocParamType. Must be either ControlRecord or SegmentRecord.
    •  IDOC_17606 Error getting metadata for the IDoc segment <segment name>.
    •  IDOC_17607 Property <property> is invalid. Error parsing IDocs list.
    •  IDOC_17608 The number of IDoc types in the property <property> does not match the number specified in <property>.
    •  IDOC_17610 Error getting metadata for some of the IDocs in the list: <list>.
    •  IDOC_17613 Unexpected IDoc type <IDoc type> received.
    •  IDOC_17614 Input is expected only for IDoc types: <IDoc type>.
    •  IDOC_17615 Error parsing control data. Check the control data for IDoc type <IDoc type>.
    •  IDOC_17617 The segment <IDoc segment> is not allowed in the current IDoc type <type>.
    •  IDOC_17618 Control record data cannot be NULL for IDoc <IDoc>.
    •  IDOC_17619 Segment data cannot be NULL for segment <segment>.
    •  IDOC_17620 Error creating control table <control table>.
    •  IDOC_17621 Error creating data table <data table>.
    •  IDOC_17622 Error appending control record <control record>. Failed to allocate enough memory.
    •  IDOC_17623 Error appending data record <data record>. Failed to allocate enough memory.
    •  IDOC_17624 The SAPALEIDoc target definition did not receive a control record segment for IDoc type: <IDoc type>.
    •  IDOC_17625 The SAPALEIDoc target definition did not receive a control record segment. Error encountered in IDoc processing.
    •  IDOC_17626 The SAPALEIDoc target definition received an incorrect number of control record segments. Error encountered in IDoc processing.
    •  IDOC_17627 The SAPALEIDoc target definition did not receive any data segments for IDoc type <IDoc type>. Error encountered in IDoc processing.
    •  IDOC_17633 Error creating control table <table name>.
    •  IDOC_17642 Idle Time <time> must be greater than or equal to -1.
    •  IDOC_17643 Packet Count <count> must be greater than or equal to -1.
    •  IDOC_17644 Real-time Flush Latency <latency period> must be greater than or equal to 0.
    •  IDOC_17645 Reader Time Limit <time limit> must be greater than or equal to 0.
    •  IDOC_17646 Failed to get connection reference for source qualifier instance <Source Qualifier name>.
    •  IDOC_17647 Failed to get connection for source qualifier instance <Source Qualifier name>.
    •  IDOC_17648 Failed to initialize reader properties for source qualifier instance <Source Qualifier name>.
    •  IDOC_17649 Incorrect connection type specified for SAPALEIDoc source.
    •  IDOC_17652 The value for the property <TypeOfEP> should be <IDocInterpreter>.
    •  IDOC_17655 The Integration Service failed to fetch the IDoc packet.
    •  IDOC_17656 The Integration Service failed to process the IDoc packet for transaction ID = <ID>.
    •  IDOC_17658 The SAPALEIDoc source definition can have only one input group.
    •  IDOC_17659 The SAPALEIDoc source definition may contain incorrect port names.
    •  IDOC_17662 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.
    •  IDOC_17666 Failed to initialize writer properties for target instance <target>.
    •  IDOC_17668 <Connection property> not specified.
    •  IDOC_17669 Failed to get connection property <connection property>.
    •  IDOC_17670 IDoc writer cannot get connection information for the target instance <target>.
    •  IDOC_17671 Writer partition <partition> failed to register for recovery.
    •  IDOC_17672 Data <data> truncated by writer.
    •  IDOC_17675 IDoc reader failed to support recovery for the Source Qualifier instance <Source Qualifier name>.
    •  IDOC_17676 Cache folder specified for reader partition <partition> is invalid.
    •  IDOC_17677 Reader partition <partition> failed to register for recovery.
    •  IDOC_17678 Reader partition <partition> failed to cache message.
    •  IDOC_17679 Reader partition <partition> truncated last cached message from cache.
    •  IDOC_17680 Reader partition <partition> failed to truncate message cache to last serialized message: <error message>.
    •  IDOC_17681 IDoc Reader failed to cache a message: <error message>.
    •  IDOC_17682 Reader partition <partition> failed to close checkpoint at EOF: <error message>.
    •  IDOC_17684 Reader partition <partition> failed to flush the cache: <error message>.
    •  IDOC_17685 Reader partition <partition> failed to read cached message.
    •  IDOC_17690 Reader partition <partition> failed to close checkpoint at real-time flush point: <error message>.
    •  IDOC_17691 IDoc Reader failed to deserialize cache message: <error message>.
    •  IDOC_17695 Error initializing the tree builders for partition <partition>.
    •  IDOC_17696 Error creating input row for group <group>.
    •  IDOC_17697 Error setting data for the field: <field>.
    •  IDOC_17698 Unknown error encountered while traversing the tree.
    •  IDOC_17699 Error building the tree.
    •  IDOC_17700 Error getting data for the field.
    •  IDOC_17704 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>.
    •  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>.
    •  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>.
    •  IDOC_17707 NULL data obtained for primary/foreign key fields.
    •  IDOC_17708 NULL data obtained for all connected fields for the segment <segment name>.
    •  IDOC_17709 Data <data> overflow at port <port number>. If the error threshold is not met, the row will be sent through the ErrorIDocData port.
    •  IDOC_17710 <Value> orphan rows were received by the SAP/ALE IDoc Prepare transformation.
    •  IDOC_17711 <Value> duplicate rows were received by the SAP/ALE IDoc Prepare transformation.
    •  IDOC_17712 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>.
    •  IDOC_17713 Duplicate row received in group <group> with primary key: <primary key>.
    •  IDOC_17714 The following IDoc data is not of proper length: <value>.
    •  IDOC_17720 The SAP/ALE IDoc Prepare transformation has an unconnected input group. Connect all input groups for the transformation.
    •  IDOC_17721 Error encountered while setting data for group: <group>.
    •  IDOC_17722 Syntax validation failed for document number <document number> because mandatory segment is missing: <segment name>.
    •  IDOC_17723 Syntax validation failed for document number <document number> because maximum occurrence is higher than maximum limit for: <segment name>.
    •  IDOC_17724 Syntax validation failed for document number <document number> because minimum occurrence is less than the minimum limit for: <segment name>.
    •  IDOC_17725 Extended Syntax Check skipped because Error Output port is missing. Recreate the SAP/ALE IDoc Interpreter transformation.
    •  IDOC_17742 Cache folder specified for the SAP/ALE IDoc Prepare transformation <transformation name> is invalid.
    •  IDOC_17743 The Integration Service could not access the cache block in group <group>. Increase the cache size.
    •  IDOC_17744 The SAP/ALE IDoc Prepare transformation did not receive control record data for the IDoc type <IDoc type>.
    •  IDOC_17747 <Value> orphan rows were received by the SAP/ALE IDoc Interpreter transformation.
    •  IDOC_17748 The SAP/ALE IDoc Interpreter transformation received orphan row <index of the row> in group <group> with primary key <primary key>.
    •  IDOC_17749 <Value> duplicate rows were received by the SAP/ALE IDoc Interpreter transformation.
    •  IDOC_17750 Reader buffer flush failed.
    •  IDOC_17755 The type A connection to the SAP system failed.
•  J Message Codes
  •  JDE Messages
    •  JDEWRDR_50004 The PowerCenter Integration Service failed to fetch connection information from the repository.
    •  JDEWRDR_50005 The PowerCenter Integration Service failed to fetch the database type from the repository.
    •  JDEWRDR_50006 Invalid connection information.
    •  JDEWRDR_50010 Invalid value specified for the Select Distinct property at the session level.
    •  JDEWRDR_50013 The PowerCenter Integration Service failed to fetch the field attribute from the repository.
    •  JDEWRDR_50014 The PowerCenter Integration Service failed to fill the output buffer.
    •  JDEWRDR_50015 The PowerCenter Integration Service failed to flush the output buffer.
    •  JDEWRDR_50016 The PowerCenter Integration Service failed to fetch source metadata from the repository.
    •  JDEWRDR_50022 The PowerCenter Integration Service failed to get the table object.
    •  JDEWRDR_50024 The PowerCenter Integration Service could not parse the SQL query. The table alias names might have been used in the SQL query.
    •  JDEWRDR_50028 The PWX_JDEWORLDPATH environment variable is not set.
    •  JDEWRDR_50031 PowerExchange for JD Edwards World is not enabled on PowerCenter or the license has expired.
    •  JDEWRDR_50037 Mismatch in datatype or precision or both for a field.
    •  JDEWRDR_50040 The libraries specified in the JDE Library List do not contain the table <table name>.
    •  JDEWRDR_50042 Invalid value specified for the Number of Sorted Ports property at the session level.
    •  JDEWRDR_50044 The PowerCenter Integration Service failed to create locale.
    •  JDEWRDR_50047 The PowerCenter Integration Service failed to fetch the datatype, precision, and scale for a column in the JD Edwards World table.
    •  JDEWRDR_51002 PowerExchange failed to release the environment handle.
    •  JDEWRDR_51003 PowerExchange failed to allocate memory to the statement handle.
    •  JDEWRDR_51004 PowerExchange failed to disconnect from JD Edwards World.
    •  JDEWRDR_51005 PowerExchange failed to release the connection handle.
    •  JDEWRDR_51006 PowerExchange failed to release the statement handle.
    •  JDEWRDR_51007 PowerExchange failed to prepare the statement.
    •  JDEWRDR_51008 PowerExchange failed to bind the eCTYPE_CHAR datatype to a column.
    •  JDEWRDR_51009 PowerExchange failed to bind the eCTYPE_UNICHAR datatype to a column.
    •  JDEWRDR_51010 PowerExchange failed to bind the eCTYPE_DOUBLE datatype to a column.
    •  JDEWRDR_51011 PowerExchange failed to bind the eCTYPE_FLOAT datatype to a column.
    •  JDEWRDR_51012 PowerExchange failed to bind the eCTYPE_LONG datatype to a column.
    •  JDEWRDR_51013 PowerExchange failed to bind the eCTYPE_SHORT datatype to a column.
    •  JDEWRDR_51014 PowerExchange failed to bind the eCTYPE_INT32 datatype to a column.
    •  JDEWRDR_51015 PowerExchange failed to bind the eCTYPE_LONG64 datatype to a column.
    •  JDEWRDR_51016 PowerExchange failed to bind the eCTYPE_RAW datatype to a column.
    •  JDEWRDR_51017 PowerExchange failed to bind the eCTYPE_TIME datatype to a column.
    •  JDEWRDR_51018 PowerExchange failed to execute the SQL query.
    •  JDEWRDR_51019 PowerExchange failed to fetch JD Edwards World data.
    •  JDEWRDR_51020 PowerExchange failed to allocate memory to the environment handle.
    •  JDEWRDR_51021 PowerExchange failed to allocate memory to the connection handle.
    •  JDEWRDR_51023 PowerExchange failed to set connection options.
    •  JDEWRDR_51024 PowerExchange failed to connect to JD Edwards World.
    •  JDEWRDR_51025 PowerExchange failed to fetch table information from a specified library.
    •  JDEWRDR_51026 PowerExchange failed to bind a column.
  •  JMS Messages
    •  JMS_1001 Failed to connect to a JNDI provider: <error message>.
    •  JMS_1002 The object <object name> looked up from JNDI is not a Destination object.
    •  JMS_1003 Failed to set JMS exception listener: <error message>.
    •  JMS_1004 The object <object name> is not a QueueConnectionFactory object in JNDI.
    •  JMS_1005 The object <object name> is not a TopicConnectionFactory object in JNDI.
    •  JMS_1006 The destination object is not a Queue object.
    •  JMS_1007 The destination object is not a Topic object.
    •  JMS_1008 Failed to create JMS connection: <error message>.
    •  JMS_1009 Failed to create JMS session: <error message>.
    •  JMS_1010 Failed to create JMS connection consumer: <error message>.
    •  JMS_1011 Failed to start JMS connection: <error message>.
    •  JMS_1012 Failed to stop JMS connection: <error message>.
    •  JMS_1013 Failed to close JMS connection: <error message>.
    •  JMS_1014 Failed to close JNDI connection: <error message>.
    •  JMS_1015 Failed to look up object <object name> from JNDI.
    •  JMS_1018 Cannot find message type from metadata extension.
    •  JMS_1019 Cannot find JMS connection.
    •  JMS_1020 Failed to create the message consumer: <error message>.
    •  JMS_1021 Failed to create the message consumer because of conflicting JMS session and JMS connection objects.
    •  JMS_1022 Failed to get the JMS destination <destination>. Reason: <error message>.
    •  JMS_1023 Failed to get the Queue Connection Factory <queue connection factory>. Reason: <error message>.
    •  JMS_1024 Failed to get the Topic Connection Factory <topic connection factory>. Reason: <error message>.
    •  JMS_1026 The file jndi.properties is not found. No additional SSL related properties are used at runtime.
    •  JMS_2002 Error in getting the session extension information for Source Qualifier <Source Qualifier name>.
    •  JMS_2025 An error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.
    •  JMS_2026 JMS error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.
    •  JMS_2027 The data received is too large for processing the field <field name> by Source Qualifier <Source Qualifier name>. Reason: <error message>.
    •  JMS_2028 The message received by Source Qualifier <Source Qualifier name> does not match the body definition.
    •  JMS_2029 The Source Qualifier <Source Qualifier name> encountered an error in closing the consumer. Reason: <error message>.
    •  JMS_2032 Unknown error occurred while writing the data to the DTM buffer by Source Qualifier <Source Qualifier name>. Reason: <error message>.
    •  JMS_2035 The partition #<number> of Source Qualifier <Source Qualifier name> failed to get cache coordinator for recovery.
    •  JMS_2036 File cache folder is not provided. Please enter a file cache folder.
    •  JMS_2037 Failed to create storage information object for Guaranteed Message Delivery. Reason: <error message>.
    •  JMS_2038 Failed to register recovery cache. Reason: <error message>.
    •  JMS_2041 Failed to recover data from recovery cache. Reason: <error message>.
    •  JMS_2042 Unknown error encountered while recovering data from recovery cache.
    •  JMS_2043 Failed to write data to recovery cache. Reason: <error message>.
    •  JMS_2044 Source Qualifier <Source Qualifier name> encountered an error while acknowledging the message. Reason: <error message>.
    •  JMS_2046 A data conversion error happened while processing the message for field <field name> in the Source Qualifier <Source Qualifier name>.
    •  JMS_2047 Message listener cannot be set: <error message>.
    •  JMS_2048 Error closing JMS session: <error message>.
    •  JMS_2050 Source Qualifier <Source Qualifier name> encountered error while receiving the JMS message. Reason: <error message>.
    •  JMS_2051 The requested datatypes do not match the data written to the recovery cache. The cache may be corrupt.
    •  JMS_2052 The jms.jar library could not be loaded.
    •  JMS_2063 The Integration Service fails a JMS real-time session that is enabled for recovery and contains multiple partitions.
    •  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>.
    •  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>.
    •  JMS_3003 Cannot create writer connection: <error message>.
    •  JMS_3004 Cannot close connection: <error message>.
    •  JMS_3005 Cannot close JMS session: <error message>.
    •  JMS_3006 Cannot commit JMS session: <error message>.
    •  JMS_3007 Cannot roll back JMS session: <error message>.
    •  JMS_3008 Cannot create JMS message object: <error message>.
    •  JMS_3009 Cannot create message writer: <error message>.
    •  JMS_3013 Cannot create a message object because an invalid message type is given.
    •  JMS_3014 The field <field name> is not a valid JMS target field.
    •  JMS_3015 An invalid row type was encountered. JMS writer will publish a message if the row type is INSERT, UPDATE, and DELETE.
    •  JMS_3016 JMS writer encountered an unknown row type error.
    •  JMS_3017 The value provided for <property name> in the JMS connection <connection name> is invalid. Reason: <error message>.
    •  JMS_3018 JMS writer encountered a JMS exception while field <field name> was being processed: <error message>.
    •  JMS_3020 JMS writer encountered a data conversion error while field <field name> was being processed.
    •  JMS_3021 JMS writer encountered a general exception: <error message>.
    •  JMS_3022 JMS writer encountered a general error: <error message>.
    •  JMS_3023 JMS exception happened in JMS provider: <error message>.
    •  JMS_3024 Invalid datatype ID: <error message>.
    •  JMS_3025 JMS writer received NULL for the field <field name>, which is set to Not Null. The message will be rejected.
    •  JMS_3026 JMS writer encounters a JMS exception: <error message>.
    •  JMS_3027 JMS writer encountered an out of memory error.
    •  JMS_3028 JMS writer encountered an error in getting the default JMSReplyTo object <object name> from JNDI. Reason: <error message>.
    •  JMS_3029 JMS writer encountered an error in processing the data for the field <field name> in the target <target name>. Reason: <error message>.
    •  JMS_3030 The jms.jar library could not be loaded.
    •  JMS_3031 The Integration Service cannot guarantee that it will process messages only once. Some messages may be lost or duplicated.
    •  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>.
    •  JMS_3034 Field <field name> for target <target name> can be projected if IsDestinationNameDynamic is set to true in session properties.
  •  JSDK Messages
    •  JSDK_42021 Failed to load the library: <library name>.
    •  JSDK_42075 The Integration Service is trying to reset the session but the resetNotification API has not been implemented in the Java transformation <transformation>.
  •  JTX Messages
    •  JTX_1001 Failed to create partition driver. An exception occurred while loading partition driver class from byte code: <exception text>.
    •  JTX_1002 Failed to find metadata extension <metadata extension name>.
    •  JTX_1003 Failed to retrieve metadata for input/output ports: <port names>.
    •  JTX_1005 Column name <name> is not valid.
    •  JTX_1006 The number of groups is not valid. The Java transformation must have exactly one input group and one output group.
    •  JTX_1008 The row type <row type> is not valid. Valid row types for the setOutRowType API are INSERT, DELETE, and UPDATE.
    •  JTX_1009 Failed to create partition driver. The byte code for the Java transformation is not valid.
    •  JTX_1010 Transformation name cannot be null. Failed to create class loader.
    •  JTX_1011 Error thrown by Java transformation failSession API: <error text>.
    •  JTX_1013 Error message: <message text>.
    •  JTX_1014 The parameter for the Java transformation API <method name> cannot be NULL.
    •  JTX_1015 Exception thrown from Java transformation: <exception text>.
    •  JTX_1016 Cannot use Java transformation API <method name> when transformation property <name> is not selected.
    •  JTX_1017 Callable API <method name> cannot be called in a passive Java transformation.
    •  JTX_1018 Failed to set the default value for port <port name>. Error: <error>.
    •  JTX_1101 Failed to create JExpression instance.
    •  JTX_1102 The specified row type <row type> is not valid. Valid row types are: INSERT, DELETE, and UPDATE.
    •  JTX_1103 NULL result.
    •  JTX_1104 Result data type is <type>. This API call is not valid.
    •  JTX_1105 Result data type is not valid.
    •  JTX_1106 Session object is NULL.
    •  JTX_1107 Expression argument data type is not valid.
    •  JTX_1108 The expression string parameter of callable API <method name> cannot be null.
    •  JTX_1109 Too few parameters were passed to the expression <expression name>. Expected: <number> parameters. Passed: <number> parameters.
    •  JTX_1110 Too many parameters were passed to the expression <expression name>. The extra parameters are ignored.
    •  JTX_1111 The JExpression API <method name> parameter cannot be null.
    •  JTX_1114 Failed to load class <class name>: <error text>.
    •  JTX_1115 An exception occurred during the initialization of JExpression object: <name>.
    •  JTX_1117 Data was truncated for field <port name>.
    •  JTX_60000 Cannot validate Java transformation. Unable to retrieve metadata extensions from repository.
    •  JTX_60001 Cannot validate Java transformation. Unable to retrieve Java code snippets from the repository.
    •  JTX_60002 Cannot validate Java transformation. Unable to retrieve byte code from the repository.
    •  JTX_60003 Cannot validate Java transformation. Unable to retrieve CRC value from the repository.
    •  JTX_60004 Byte code for the transformation is not in the repository. Java transformation is invalid.
    •  JTX_60005 Byte code in the repository is invalid. Java transformation is invalid.
    •  JTX_60007 Cannot retrieve object class for <class name>.
    •  JTX_60008 Cannot find method <method name> in class <class name>.
    •  JTX_60009 Cannot create object of class <class name>.
    •  JTX_60010 Cannot create global reference to class <class name>.
    •  JTX_60011 Cannot use getLong API - result datatype not Time or Date.
    •  JTX_60012 Datatype of argument x <number> is invalid.
    •  JTX_60013 Cannot validate Java transformation. Unable to retrieve classpath from the repository.
    •  JTX_60014 Cannot validate Java transformation. Unable to retrieve precision mode from the repository.
•  L Message Codes
  •  LB Messages
    •  LB_47007 Submitted task <task name> was canceled by a user.
    •  LB_47008 Submitted task <task name> was canceled because no available node has the resources required by the task.
    •  LB_47010 The Integration Service failed to load the external resource manager library due to error <error text>.
    •  LB_47011 The Integration Service failed to retrieve the external resource manager interface due to error <error text>.
    •  LB_47012 The external resource manager interface failed to initialize due to error <error text>.
    •  LB_47047 The load balancer failed to detach node <node name>.
    •  LB_47050 Received final notice for request on invalid node <node name> with event code <code>.
  •  LDAP Messages
    •  LDAPRDR_1000 Failed to find the PowerExchange for LDAP license key.
    •  LDAPRDR_2037 For the LDAP directory server, the supportedControl attribute under Root DSE is missing or not accessible.
    •  LDAPRDR_2046 The PowerCenter Integration Service failed to read the change log information from the file <CDC file name>.
    •  LDAPRDR_2047 The PowerCenter Integration Service failed to write the change log information to the file <CDC file name>.
    •  LDAPRDR_2048 The PowerCenter Integration Service could not retrieve response for the Sort request control from the context. Reason: <reason>
    •  LDAPRDR_2049 The PowerCenter Integration Service could not retrieve response for PagedResultControl from the context.
    •  LDAPRDR_2050 The PowerCenter Integration Service could not retrieve the modification details for the change log entry <entry_name> due to missing values for one of the required attributes.
    •  LDAPRDR_2051 The PowerCenter Integration Service could not retrieve the entry for dn=<attribute value> from the LDAP directory server.
    •  LDAPRDR_2052 The PowerCenter Integration Service failed to expand the variable to get the Change Data Capture file location. Reason: <reason>
    •  LDAPRDR_2053 The PowerCenter Integration Service failed to propagate the modrdn change for dn=<attribute value>.
    •  LDAPRDR_2056 The PowerCenter Integration Service failed to create the Sort control.
    •  LDAPRDR_2058 The PowerCenter Integration Service failed to create the directory in which the Change Data Capture file is to be created.
    •  LDAPRDR_2059 The PowerCenter Integration Service could not retrieve the newRdn attribute for the old targetDn <attribute value> from the LDAP directory server.
    •  LDAPRDR_2062 The PowerCenter Integration Service could not find the change log entries under DN <change log DN name>.
    •  LDAPRDR_2072 The PowerCenter Integration Service failed to perform an initial check for Change Data Capture data transfer. Reason: <reason>
    •  LDAPRDR_2076 An error occurred while expanding variable to get search filter expression. Reason: <reason>
    •  LDAPRDR_2078 The PowerCenter Integration Service failed to process the referral entry <entry DN name> due to error in authenticating the user against the referenced directory server.
    •  LDAPWRT_1000 Failed to find the PowerExchange for LDAP license key.
    •  LDAPWRT_3031 Unable to <operation type> entry <entry DN name>.
    •  LDAPWRT_3032 Unable to insert the entry <entry DN name> because it already exists in the LDAP directory server.
    •  LDAPWRT_3037 The PowerCenter Integration Service failed to delete the entry <entry DN name> because it does not exist in the LDAP directory server.
    •  LDAPWRT_3043 The PowerCenter Integration Service failed to update the entry <entry DN name> as the attribute value to be updated is used in RDN.
    •  LDAPWRT_3052 Unable to <operation type> the attribute <attribute name> for the entry <entry DN name>.
  •  LDBG Messages
    •  LDBG_8316 Error. The DTM server ran out of buffer pool data blocks for Partition Point <partition point name> where <transformation name> is the transformation name.
    •  LDBG_21035 Datablock write-lock error. offset <offset value>, reason [No space left on device].
    •  LDBG_21149 ERROR determining truncate table order - could not create constraint load dependencies for target.
    •  LDBG_21178 ERROR: Self-referential constraint in target.
    •  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.
    •  LDBG_21511 TE: Fatal Transformation Error.
    •  LDBG_21604 Data block read-lock error, offset <number>, reason: <reason>.
    •  LDBG_21605 Cannot open files in the directory <directory name>.
    •  LDBG_21633 For the dynamic lookup cache for <Lookup transformation>, an input row has NULL value in condition fields. This row will not be used for update of the lookup cache.
    •  LDBG_21668 Error: The Informatica server license does not allow more than one database license to be used at a time.
  •  LGS Messages
    •  LGS_10006 The file <file name> was skipped during automatic purge.
    •  LGS_10010 Not all files are deleted in directory: <directory name>.
    •  LGS_10013 Invalid number of log events were received.
    •  LGS_10016 Failed to close the file merge stream due to the following error <error text>.
    •  LGS_10017 Error creating the directory <directory name>.
    •  LGS_10019 Failed to open the file stream <file name> due to the following error <error text>.
    •  LGS_10021 Failed to read log event from the file stream <file name> due to the following error <error text>.
    •  LGS_10024 Log request failed due to the following error <error text>.
    •  LGS_10026 The log service configuration is missing the log service directory value for the node <node name>.
    •  LGS_10028 The index file <file name> is corrupt.
    •  LGS_10034 Log request failed due to the following error <error text>. Unable to rollback changes due to the following error <error text>.
    •  LGS_10035 The timestamp index file <file name> is corrupted.
    •  LGS_10052 The Log Manager has no record of the requested session or workflow run.
    •  LGS_10060 The log fetch operation does not accept both Run ID and Run instance name as inputs.
  •  LIC Messages
    •  LIC_10000 The Service Manager is not initialized yet.
    •  LIC_10004 The Service Manager is disabled and cannot accept licensing requests.
    •  LIC_10006 A request was received that was missing a required parameter.
    •  LIC_10007 A request was received with the wrong <actual object type> parameter (expected: <expected object type>).
    •  LIC_10010 The input vector must contain license name followed by at least one service name.
    •  LIC_10011 License <license name> is not found.
    •  LIC_10013 The following services are already assigned: <list of services>
    •  LIC_10014 Request parameters must contain a license name followed by an encrypted license key.
    •  LIC_10015 Request parameters must contain source and target license names.
    •  LIC_10017 <service name> is not assigned to any license.
    •  LIC_10018 Request parameters must contain a license name followed by a description.
    •  LIC_10019 Request parameters must contain a valid service name followed by a valid node name.
    •  LIC_10020 The operating system type could not be established for node <node name>.
    •  LIC_10025 Cannot unassign from license <name of license> because services <list of services enabled> are enabled and/or services <list of services missing> were not found.
    •  LIC_10026 License <license name>/<license serial number> cannot start service <service name> as it is not licensed to execute on platform <platform name>.
    •  LIC_10027 Failed to add a license key that expired on <expiration date>.
    •  LIC_10028 Failed to add a license key that is invalid because: <reason license key is invalid>.
    •  LIC_10030 Attempted to use license <license name/<license serial number> for PowerCenter <product version> where license was purchased for <license version>.
    •  LIC_10033 License <license name>/<license serial number> cannot start service <service name> as license has expired on <expiration date>.
    •  LIC_10034 License <license name>/<license serial number> cannot start service <service name> as license does not support grid processes.
    •  LIC_10035 License <license name>/<license serial number> cannot start repository instance <repo name> as license does not have a valid repository count.
    •  LIC_10048 Failed to write license <license name>/<license serial number> new day record for logical CPUs on platform <platform>.
    •  LIC_10049 Failed to write license <license name>/<license serial number> new day record for repository instances.
    •  LIC_10050 Failed to write license <license name>/<license serial number> record for <actual CPU count for platform> logical CPUs on platform <platform>.
    •  LIC_10051 Failed to write license <license name>/<license serial number> record for <actual repo count> repository instances.
    •  LIC_10052 Change occurred to service <service name> that could not be found within domain.
    •  LIC_10053 Change occurred to node <node name> that could not be found within domain.
    •  LIC_10054 Cannot locate license with serial number <license serial number>.
    •  LIC_10055 Failed to find license for service <service name>.
    •  LIC_10056 License <license name>/<license serial number> cannot start service <service name> as license does not support backup nodes.
    •  LIC_10061 Cannot validate license usage with invalid service name <service name>.
    •  LIC_10062 Cannot validate license usage with invalid node name <node name>.
    •  LIC_10063 License <license name/license serial number> cannot start service <service name> as license does not support operating system profiles.
    •  LIC_10064 Cannot start service <service name> on node <node name> because this would exceed the number of licensed CPUs for platform <platform name>.
  •  LM Messages
    •  LM_36053 The server mode <current server mode> is invalid. Default server mode <default server mode> will be used.
    •  LM_36072 Cannot get $PMStorageDir from configuration.
    •  LM_36129 Cannot open log file <name>.
    •  LM_36133 Fail in reading log file <name>.
    •  LM_36134 Session is initializing. Session log file is temporarily unavailable.
    •  LM_36136 Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration Service.
    •  LM_36138 Cannot find workflow log name.
    •  LM_36210 Get worklet instance name from repository failed.
    •  LM_36220 Log file <name> contains no data.
    •  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).
    •  LM_36229 Request failed because the connection was broken or the client is too slow in processing replies, client <name>, connection <name>, request ID <number>.
    •  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.
    •  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.
    •  LM_36272 Failed to get gateway information from URI <universal resource identifier>.
    •  LM_36273 Failed to look up service in domain <domain>, service <service>, service process <node> from name service lookup using the URI <universal resource identifier>.
    •  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>.
    •  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.
    •  LM_36310 Workflow <name>: Cannot open log file <name>.
    •  LM_36311 Workflow <name>: Failed to expand workflow log file name <name>.
    •  LM_36312 Workflow <name>: Log path exceeds limit of <number> characters: <path>.
    •  LM36320 <Workflow or task name>: Execution failed.
    •  LM_36338 Workflow <name> Could not start execution of this workflow because the current run on this Integration Service has not completed yet.
    •  LM_36348 <Workflow, worklet, or session instance name>: Parameter file <name> not found.
    •  LM_36349 <Workflow or worklet name>: Failure to create variable manager.
    •  LM_36350 Error in binding the pre-defined variable <name>.
    •  LM_36351 <Workflow name>: Error in persisting variable values.
    •  LM_36362 Workflow <name>: The workflow log count in the repository is negative <number>.
    •  LM_36363 Workflow <name>: Cannot rename workflow log file <file name> to <file name>.
    •  LM_36364 Workflow <name>: Failed to increment the log file number in the repository.
    •  LM_36366 <Worklet name>: Failed to set the passed value for variable <name>.
    •  LM_36367 <Task instance name and path>: Suspension email has an empty user name.
    •  LM_36368 <Task instance name and path>: Failed to send suspension email.
    •  LM_36369 <Session task instance> <task instance path> Encountered task instance <task instance name> of unknown type.
    •  LM_36381 <Worklet name>: Failed to set the passed value for variable <name>. Cannot find a user-defined variable with this name.
    •  LM_36382 <Worklet name>: Failed to set the passed value for variable <name>. The variable <name> cannot be found at the parent <workflow or worklet name>.
    •  LM_36383 Error in expanding variable parameter.
    •  LM_36385 Workflow <name>: Could not acquire the execute lock for Workflow <name>.
    •  LM_36401 <Session task instance> <task instance path> Execution terminated unexpectedly.
    •  LM_36440 <Task type> task instance <task instance path>: Error in fetching persistent variable values for <workflow or worklet> <workflow or worklet name>.
    •  LM_36441 Error: Both parameter list and parameter file are specified.
    •  LM_36471 <Workflow name>: Failover of workflow schedule failed because the information in storage is inconsistent or incomplete.
    •  LM_36476 <Workflow name>: Failover of workflow execution failed because the workflow cannot be internally scheduled in recovery mode.
    •  LM_36477 <Workflow name>: Failed to save workflow information for failover.
    •  LM_36527 <Task instance name and path>: Failed to fetch session to send post session email for this session instance.
    •  LM_36528 <Task instance name and path>: Failed to expand E-mail user name <user name> for this session instance.
    •  LM_36529 <Task instance name and path>: The e-mail user name in the post session failure e-mail component for this session instance is empty.
    •  LM_36530 <Task instance name and path>: Failed to send post session failure e-mail for this session instance.
    •  LM_36538 <Session instance path>: Unable to write to temporary parameter file <parameter file name> with error <error number> <cause of error>.
    •  LM_36539 <Session instance path>: Unable to unlink temporary parameter file <parameter file name> with error <error number> <cause of error>.
    •  LM_36543 <Task name> condition expression eval error < expression >.
    •  LM_36544 <Task name>: condition expression <expression> will not evaluate to a numeric value.
    •  LM_36564 <Task name>: Invalid datatype conversion for variable <name>, expression datatype <datatype>, variable datatype <datatype>.
    •  LM_36565 <Task name>: Variable <name>: data conversion exception <value>.
    •  LM_36566 <Task name>: Unable to resolve the left-hand side variable <name> as a user-defined workflow/worklet variable.
    •  LM_36567 Unable to rollback the assignment for variable <name>.
    •  LM_36580 <Task instance name and path>. Email Username not specified.
    •  LM_36581 <Task instance name and path>. Failed to send email.
    •  LM_36601 <Timer name> Unable to schedule timer with the timer task manager.
    •  LM_36602 <Variable name> Wait for absolute time specified by variable <variable type>. The variable does not exist.
    •  LM_36603 <Variable name> Wait for absolute time specified by variable <variable type>. The variable is not of type date/time.
    •  LM_36604 <Variable name> Wait for absolute time specified by variable <variable type>. The variable value is null.
    •  LM_36648 <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>.
    •  LM_36823 Workflow <workflow ID> <session> not unscheduled because it is not scheduled.
    •  LM_44122 Errors encountered in initializing storage in directory <directory name>.
    •  LM_44124 Integration Service is missing workflow manager storage.
    •  LM_44125 Workflow manager storage is not ready for Integration Service.
    •  LM_44127 Failed to prepare the task <name>.
    •  LM_44136 Failed to release remaining execution locks as failover.
    •  LM_44180 The number of asynchronous threads for repository connections specified <number of threads> is too low, using default of <number of threads>.
    •  LM_44181 Workflow <workflow name> is impacted. The Integration Service is not configured to run sessions impacted by dependency updates.
    •  LM_44183 Scheduling workflow is not allowed because the Integration Service is running in safe mode.
    •  LM_44184 Scheduled workflow <workflow name> was not rescheduled because the Integration Service is running in safe mode.
    •  LM_44185 User <user name> does not have sufficient privilege to log on while the Integration Service is running in safe mode.
    •  LM_44188 <Task name>: Failed to expand email user <name> for this email task.
    •  LM_44189 <Workflow name>: Failed to expand email user <name> for this suspension email.
    •  LM_44190 <Command task name>: Failed to expand command <command name>, with command value <command text>.
    •  LM_44193 Integration Service <name> will not perform workflow and schedule failover or recovery when running in safe mode.
    •  LM_44205 Error using operating system profiles to run task <task name>: <error message>.
    •  LM_44207 Cannot stop or abort workflow <ID = run ID> or a task within the workflow. The specified run ID is not found on the Integration Service.
    •  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.
    •  LM_44210 Cannot wait for workflow <ID = run ID> or a task within the workflow. The run ID is not found on the Integration Service.
    •  LM_44211 Cannot wait for workflow or a task within the workflow. The Integration Service is running more than one instance of the workflow. Specify the workflow run ID to wait for.
    •  LM_44220 <Workflow or worklet name>: Failed to set the variable assignment value for variable <name>.
    •  LM_44222 Request to recover workflow <workflow name> run ID <run ID> does not match the current workflow run ID.
    •  LM_44223 The workflow <name> failed because an operating system profile was not specified and the Integration Service uses operating system profiles.
    •  LM_44224 The workflow <name> failed because the Integration Service is not enabled to use operating system profiles and an operating system profile was specified.
    •  LM_44225 The Integration Service failed to read parameter file <file name> using the operating system profile.
    •  LM_44226 The maximum number of allowed concurrent runs has been exceeded.
    •  LM_44227 The workflow contains persisted variables.
    •  LM_44228 A workflow with the same instance name is already running.
    •  LM_44254 Concurrent workflow [folder [ID = <number>], workflow [ID = <number>]] runs with the same instance name. Specify the workflow run ID for recovery.
    •  LM_44255 Failed to fetch workflow [Folder ID = <folder ID>, Workflow ID = <workflow ID>] from the repository.
    •  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.
    •  LM_44269 There is no Web Services Hub configured to run workflow [<workflow name>].
  •  LMTGT Messages
    •  LMTGT_17801 Error initializing LM-API.
    •  LMTGT_17802 All relational targets must share the same relational database connection.
    •  LMTGT_17803 Cannot create the relational database connection.
    •  LMTGT_17804 Cannot connect to database.
    •  LMTGT_17805 Cannot connect to Integration Service.
    •  LMTGT_17806 Cannot log in to Integration Service.
    •  LMTGT_17808 Key field must be connected.
    •  LMTGT_17809 Identifier port is not connected in the mapping. The port must be connected when using the Wait for Commit option.
    •  LMTGT_17810 Could not find workflow details for key <key name>.
    •  LMTGT_17811 Indicator Table <table name> not found in the mapping.
    •  LMTGT_17812 Indicator Table name is not specified in the mapping. Indicator Table name is required when using the Wait for Commit option.
    •  LMTGT_17818 The Integration Service cannot fetch workflow <workflow name> for key <key name>.
    •  LMTGT_17820 Warning: Lost server connection.
    •  LMTGT_17821 Error communicating with Integration Service.
  •  Lotus Notes Messages
    •  LNRDR_1017 Failed to load the NCSO.jar file.
    •  LNWRT_1000 Failed to find the PowerExchange for Lotus Notes license.
    •  LNWRT_1010 Failed to connect to the Domino server <servername:portnumber>. Reason: <reason>.
    •  LNWRT_1012 Unable to access the Notes database <database name>.
    •  LNWRT_1019 The PowerCenter Integration Service failed to find the agent <agent name> in the Notes database <database name>.
    •  LNWRT_1025 Internal error. The PowerCenter Integration Service received an abort or a stop request from the Data Transformation Manager (DTM) process. Terminating the session.
    •  LNWRT_1035 An error occurred while creating the error log file <file name>.
    •  LNWRT_1041 Error threshold value <threshold> reached.
•  M Message Codes
  •  MBC_EXCL Messages
    •  MBC_EXCL_E001 Failed to access OLE Excel engine.
    •  MBC_EXCL_E002 Failed to execute OLE Excel operation. Error code: <error code>. Message: <error message>
    •  MBC_EXCL_E005 Could not start Microsoft Excel API. Error code=<error code>. Message: <error message>
    •  MBC_EXCL_E0014 Cannot open file <file name>. File may be locked by another process or is protected or Vista prevents Excel API from opening a spreadsheet when called by a service.
    •  MBC_EXCL_E0015 Failed to process Excel XML spreadsheet. The XML file may be corrupted.
    •  MBC_EXCL_E0019 The MetaMap must be in XLSM format. To create one with pre-2007 Excel, install the 2007 Office Compatibility Pack.
    •  MBC_EXCL_E0043 Could not start Microsoft Excel API.
    •  MBC_EXCL_E0061 XML file could not be opened: <file name>
    •  MBC_EXCL_E0070 Cannot unpack OpenXML- it might be corrupted or in use by another program: <file name>
    •  MBC_EXCL_E0122 Cannot open file <file name>. File may be locked by another process or is protected or you must install the Office Compatibility Pack to open XLSB files.
  •  MDAdapter Messages
    •  MDAdapter_34102 File not found file_name
    •  MDAdapter_34103 Failed to parse file_name. This metadata cannot be read.
    •  MDAdapter_34105 Unable to build metadata from file_name due to errors parsing the file.
  •  MDO Messages
    •  MDO_34601 Program Logic Error: error
    •  MDO_34602 Error(s) occurred parsing control file 'control_file'
    •  MDO_34603 Error occurred parsing control file 'control_file': error_message.
    •  MDO_34605 Error occurred defining connection: connection
    •  MDO_34607 Error occurred building map data_map obtaining metadata for record 'metadata_object : message.'
    •  MDO-34608 Environment variable variable=value is invalid/missing.
    •  MDO_34609 Control file 'file_name' - file not found.
    •  MDO_34610 Error occurred creating connection: connection.
    •  MDO_34615 I/O error occurred writing to 'data_map_file', message error_message
    •  MDO_34617 An error occurred generating datamap 'data_map', message: error_message
    •  MDO_34618 Copybook definition not specified in control file for datamap data_map_name.
    •  MDO_34620 Code page 'code_page' is invalid, map data_map_name. Expected numeric ID from pmlocale.ini.
    •  MDO_34623 Error occurred building map data_map.
    •  MDO_34645 Unable to read integer values from field field_name.
    •  MDO_34647 Data file name not specified in control file for datamap data_map.
    •  MDO_34648 Unable to create cache directory 'cache_directory'
    •  MDO_34649 Unable to start cache service. Exception Error: exception_error.
    •  MDO_34650 Unable to clear cache. Exception Error: exception_error.
    •  MDO_34651 Unable to cache file properties object. Exception Error: exception_error.
    •  MDO_34652 Unable to add record record to cache. Exception Error: exception_error.
  •  MMS Messages
    •  MMS_10109 MM Agent could not be started because of port <port number> conflict.
  •  MPSVCCMN Messages
    •  MPSVCCMN_10002 The Mapping Service Module [MappingService] could not run the mapping because it could not find the correct DTM.
  •  MQ Messages
    •  MQ_29000 Cannot connect to queue manager <queue manager> reason <reason> <reason message>.
    •  MQ_29001 Cannot open queue <queue> reason <reason> <reason message>.
    •  MQ_29002 Error closing queue <queue> reason <reason> <reason message>.
    •  MQ_29003 Error disconnecting from queue manager <queue manager> reason <reason> <reason message>.
    •  MQ_29004 Filter parse error: <parse error message>.
    •  MQ_29005 Error getting message from queue <queue>:<queue manager> reason <reason> <reason message>.
    •  MQ_29006 Message data truncated reading from queue <queue>:<queue manager> reason <reason> <reason message>.
    •  MQ_29007 No message under cursor while attempting to remove message from queue <queue>:<queue manager> reason <reason> <reason message>.
    •  MQ_29008 Error putting message on queue <queue>:<queue manager> reason <reason> <reason message>.
    •  MQ_29009 Invalid RowsPerMesage value for queue <queue>:<queue manager> (<rows per message> > 0).
    •  MQ_29010 Error opening cache <cache file> for reading: <operating system error>.
    •  MQ_29011 Error opening cache <cache file> for writing: <operating system error>.
    •  MQ_29012 Error attempting to load MQ driver.
    •  MQ_29013 Delete operation for this target not enabled. Queue connection is <queue>:<queue manager>.
    •  MQ_29014 MsgId field has not been set. Queue connection is <queue>:<queue manager>.
    •  MQ_29100 Line <line>, column <column>: Unknown character '<character>' in filter.
    •  MQ_29101 Line <line>, column <column>: Invalid operator.
    •  MQ_29102 Line <line>, column <column>: Unknown identifier <identifier>.
    •  MQ_29103 Line <line>, column <column>: String literal not terminated properly.
    •  MQ_29104 Line <line>, column <column>: Syntax Error.
    •  MQ_29105 Filter Expression does not have a boolean return type.
    •  MQ_29106 Line <line>, column <column>: Left operand must be boolean.
    •  MQ_29107 Line <line>, column <column>: Right operand must be boolean.
    •  MQ_29108 Line <line>, column <column>: Incompatible types for relational operator.
    •  MQ_29109 Line <line>, column <column>: Not enough arguments. <function name> () should have argument(s).
    •  MQ_29110 Line <line>, column <column>: Too many arguments. <function name> () should have argument(s).
    •  MQ_29111 Line <line>, column <column>: Wrong type in <function name> (). Argument should be CHAR/BYTE.
    •  MQ_29112 Line <line>, column <column>: Wrong type in <function name> (). Argument should be BOOLEAN.
    •  MQ_29113 Line <line>, column <column>: Wrong type in <function name> (). Argument should be LONG.
    •  MQ_29114 Line <line>, column <column>: String literal not terminated properly.
    •  MQ_29115 Line <line>, column <column>: Bad date format in <function name> (), Argument <argument number> should be <correct date format>.
    •  MQ_29200 Projected column metadata fetch failed.
    •  MQ_29201 Cannot retrieve source filter.
    •  MQ_29202 Unable to retrieve cache file name.
    •  MQ_29203 Error opening queue <queue>:<queue manager> because <error message>.
    •  MQ_29204 Error fetching message from queue <queue>:<queue manager> because <error message>.
    •  MQ_29207 Error closing queue <queue>:<queue manager>: <error message>.
    •  MQ_29208 Error putting message on queue <queue>:<queue manager>: <error message>.
    •  MQ_29210 Error attempting to get MQ connection information.
    •  MQ_29211 Warning: Some message data was truncated reading from queue <queue>:<queue manager>.
    •  MQ_29212 Warning: Message with a total length of <length> was truncated to <length>.
    •  MQ_29213 No filter is specified for queue <queue>:<queue manager>.
    •  MQ_29214 MQ Driver initialization failure <error message>.
    •  MQ_29218 Filter Condition for MQSeries: StartTime should be prior to EndTime.
    •  MQ_29221 Partial message written into queue <queue>:<queue manager> due to commit.
    •  MQ_29222 Error committing from queue manager <queue manager>: reason <reason> <reason message>.
    •  MQ_29223 Error backing out from queue manager <queue manager>: reason <reason> <reason message>.
    •  MQ_29224 Device failed to commit: <error message>.
    •  MQ_29225 Device failed to back out: <error message>.
    •  MQ_29226 Device failed to connect to queue manager: <error message>.
    •  MQ_29231 Transactional MQ targets with the same queue manager name cannot be in different TCUs.
    •  MQ_29234 Write to recovery cached failed.
    •  MQ_29237 Failure occurred while reading messages from the queue in destructive mode.
    •  MQ_29238 Invalid recovery cache folder specified.
    •  MQ_29239 Reader partition <partition name> failed to close checkpoint at real-time flush: <additional error message>.
    •  MQ_29240 Cache folder specified for reader partition <partition name> is invalid.
    •  MQ_29241 Reader partition <partition name> failed to register recovery.
    •  MQ_29242 Consumer handle failed to initialize.
    •  MQ_29243 Reader partition failed to read cached message.
    •  MQ_29244 Reader partition <partition name> failed doing GMD flush: <additional error message>.
    •  MQ_29245 You cannot specify both Destructive Read and RemoveMsg(TRUE).
    •  MQ_29246 The mapping contains an associated source qualifer.
    •  MQ_29248 MQ queue manager <queue manager> encountered a transient connection failure.
    •  MQ_29250 Connection retry period expired. The Integration Service could not connect to MQ queue manager <queue manager>.
    •  MQ_29251 Resilience is disabled, because Destructive Read and recovery are not configured.
    •  MQ_29255 The Integration Service truncated message data while reading from queue <queue>:<queue manager> in destructive read mode.
    •  MQ_29265 The repository data for source <source name> is corrupt.
    •  MQ_29270 The Integration Service could not create a locale for code page ID: <code page>.
    •  MQ_29280 The Integration Service fails a WebSphere MQ real-time session that is enabled for recovery and contains multiple partitions.
  •  MSRdr Messages
    •  MSRdr_1007 Failed to find the PowerExchange for Email Server license key.
    •  MSRdr_1008 Failed to find the PowerExchange for Email Server license key for Real-time option.
    •  MSRdr_1016 Failed to connect to server <servername>. Reason: <reason>.
    •  MSRdr_1019 Failed to connect to server <servername>. Reason: Incorrect username or password. <reason>.
    •  MSRdr_1020 Failed to connect to server <servername>. Reason: Unknown Server Hostname.
    •  MSRdr_1021 Failed to connect to server <servername>. Reason: Valid trusted certificate not found in the cacerts keystore. <reason>.
    •  MSRdr_1050 The PowerCenter Integration Service cannot connect to the Microsoft Exchange Server <servername>. Reason: <reason>.
    •  MSRdr_1080 Failed to connect to Outlook PST file <PST filename>. Reason: Error configuring message service. Invalid password for PST File.
•  N Message Codes
  •  NODE Messages
    •  NODE_10014 <Resource type> resource <resource name> not found in node configuration.
  •  NTSERV Messages
    •  NTSERV_10000 Cannot close service main thread handle.
    •  NTSERV_10001 Cannot suspend service main thread.
    •  NTSERV_10003 Cannot resume service main thread.
    •  NTSERV_10005 Cannot set service status.
    •  NTSERV_10007 Cannot duplicate service main thread handle.
    •  NTSERV_10009 Cannot start service control dispatcher.
    •  NTSERV_10011 Cannot register service handler procedure.
    •  NTSERV_10013 Cannot open Service control manager. Access Denied.
    •  NTSERV_10024 Cannot flush registry key.
    •  NTSERV_10025 Cannot close registry key.
    •  NTSERV_10026 Cannot initialize security descriptor.
    •  NTSERV_10027 Cannot set security descriptor DACL.
    •  NTSERV_10028 Cannot create registry key.
    •  NTSERV_10029 Cannot set registry value.
    •  NTSERV_10031 Cannot delete registry key.
    •  NTSERV_10032 Cannot allocate memory.
    •  NTSERV_10033 Cannot open registry key.
    •  NTSERV_10042 Cannot create mutex.
    •  NTSERV_10043 Cannot close mutex.
    •  NTSERV_10044 Cannot create thread.
    •  NTSERV_10045 Wait for main service thread failed.
    •  NTSERV_10046 Wait for status mutex failed.
    •  NTSERV_10047 Cannot create thread to stop service.
    •  NTSERV_10065 Cannot get local computer name.
    •  NTSERV_10066 Cannot get user information.
    •  NTSERV_10067 Cannot add PowerMart user.
    •  NTSERV_10068 Cannot look up account name.
    •  NTSERV_10069 Cannot administer user rights policy.
    •  NTSERV_10070 Cannot grant user right.
    •  NTSERV_10071 Cannot convert multibyte to wide char.
    •  NTSERV_10072 Cannot convert wide char to multibyte.
    •  NTSERV_10073 Cannot delete PowerMart user.
    •  NTSERV_10080 Cannot read configuration file.
    •  NTSERV_10081 Cannot get registry value.
    •  NTSERV_10085 Key not specified.
    •  NTSERV_10086 Invalid registry value type.
    •  NTSERV_10087 Cannot enumerate registry subkeys.
    •  NTSERV_10088 Unexpected line in configuration file.
    •  NTSERV_10089 Bad usage. Consult your documentation to get correct usage.
    •  NTSERV_10091 Install failed.
    •  NTSERV_10092 Update failed.
    •  NTSERV_10093 Deinstall failed.
    •  NTSERV_10096 Cannot get registry key.
    •  NTSERV_10097 Cannot initialize message resource DLL.
    •  NTSERV_10098 Invalid drive specification.
    •  NTSERV_10099 Cannot load configuration from registry.
    •  NTSERV_10100 Wait for exit of child process failed.
    •  NTSERV_10101 Cannot find process control block.
    •  NTSERV_10102 Cannot create thread to wait for child exit event.
    •  NTSERV_10103 Cannot create thread to wait for kill event.
    •  NTSERV_10105 Cannot create process.
    •  NTSERV_10106 Cannot resume thread.
    •  NTSERV_10129 No event log configuration specified.
    •  NTSERV_10132 Registry records invalid software version.
    •  NTSERV_10133 Unknown host in TCP/IP Host Address parameter.
    •  NTSERV_10139 Unknown error converting to COM data type.
    •  NTSERV_10141 Error invoking COM external procedure.
    •  NTSERV_10143 Error looking up hostname.
    •  NTSERV_10144 Root of key is invalid.
    •  NTSERV_10145 Cannot revoke user right.
    •  NTSERV_10146 Attachment file <file name> not found.
    •  NTSERV_10147 Permissions do not allow read access of attachment <file name>.
    •  NTSERV_10148 Attachment file <file name> is not a regular file.
    •  NTSERV_10246 ERROR in attaching file.
  •  NZRDR Messages
    •  NZRDR_10015 Query generation/parsing failed.
    •  NZRDR_10017 Query execution failed.
    •  NZRDR_10109 Reading data failed.
    •  NZRDR_10013 Integration Service could not connect to Netezza Performance Server.
    •  NZRDR_10027 Create locale failed.
    •  NZRDR_10028 Failed to create pipe.
    •  NZRDR_10030 Thread creation failed.
    •  NZRDR_10034 Opening pipe failed.
    •  NZRDR_10036 Failed to create child process.
  •  NZWRT Messages
    •  NZWRT_20029 Failed to create pipe.
    •  NZWRT_20034 Failed to open pipe.
    •  NZWRT_20042 Relation <table name> does not exist in the Netezza Performance Server or no column found in the table.
    •  NZWRT_20057 Integration Service could not connect to Netezza Performance Server.
    •  NZWRT_20072 No columns linked for Update.
    •  NZWRT_20073 Primary key constraint is missing for the target.
    •  NZWRT_20075 No data available: Failed to write into pipe.
    •  NZWRT_20076 Thread creation failed.
    •  NZWRT_20126 Escape character missing.
•  O Message Codes
  •  OBJM Messages
    •  OBJM_54505 The object for which rbrowser information was requested does not exist.
    •  OBJM_54509 Rbrowser fetch: Unable to get children info. Maybe the childType is invalid. (childType = <type>).
    •  OBJM_54510 Internal Error: Unlocking a summary tree node failed.
    •  OBJM_54513 Internal: Do not have proper parent lock to access the summary tree node.
    •  OBJM_54515 Incorrect summary tree locking order.
    •  OBJM_54538 Unable to connect to the repository <repository name> on database <database name>.
    •  OBJM_54543 Database error: <database error message>.
    •  OBJM_54544 Internal Repository Service error: error number <error number>.
    •  OBJM_54545 Received fetch request with invalid rbrowser node ID <ID>.
  •  ODL Messages
    •  ODL_26001 Informatica Outer Join syntax not found.
    •  ODL_26002 Informatica Outer Join syntax error.
    •  ODL_26003 No OUTER keyword found after LEFT keyword.
    •  ODL_26004 No JOIN keyword found after OUTER keyword.
    •  ODL_26005 No OUTER keyword found after RIGHT keyword.
    •  ODL_26006 No JOIN keyword found after INNER keyword.
    •  ODL_26007 No LEFT or RIGHT keyword found before OUTER keyword.
    •  ODL_26008 More than one RIGHT OUTER JOINs are not supported.
    •  ODL_26009 No comma (,) found between table names.
    •  ODL_26012 Internal error in function <function name>. Database not in correct state.
    •  ODL_26023 Deadlock error encountered.
    •  ODL_26025 Error getting sort order from the database.
    •  ODL_26026 Driver does not support the data type.
    •  ODL_26028 File <file name> is either missing or corrupt.
    •  ODL_26035 ODBC call to SQLError failed.
    •  ODL_26036 ODBC call <ODBC call> failed.
    •  ODL_26045 Error allocating DB2 environment handle.
    •  ODL_26046 Error loading bulk API library.
    •  ODL_26047 Could not allocate a bulk API instance.
    •  ODL_26060 Fatal Error: Encountered Teradata error that aborts current transaction.
    •  ODL_26069 Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>.
    •  ODL_26071 Graphic/vargraphic partition key types are supported only on servers with UNICODE data movement enabled.
    •  ODL_26095 BigInt partition key type can be used only in high-precision mode.
    •  ODL_26111 High availability license is absent. Resilience timeout specified for database connection <connection name> is ignored.
    •  ODL_26113 Number of Bulk mode parameters=<number of parameters> exceeded the number of parameters supported <number of parameters>.
    •  ODL_26114 <Value> is not a valid parameter for the DB2BulkModeParameters custom property.
    •  ODL_26115 <Value> is not a valid key:value pair for the DB2BulkModeParameters custom property.
    •  ODL_26116 The FILETYPEMOD parameter requires single quotes at the start and end of the string value.
    •  ODL_26138 The PowerCenter Integration Service could not find the run-time OSGi bundle for the adapter [{0}] for the operating system [{1}]. Copy the adapter run-time OSGi bundle and verify that you have set the correct entry for the API in the plugin.xml file.
  •  OPT Messages
    •  OPT_63005 ERROR: Pushdown optimization failed for the session <transformation name>.
    •  OPT_63006 ERROR: Pushdown optimization could not match PowerCenter datatype <datatype> to a datatype on database <database>.
    •  OPT_63007 ERROR: Failed to expand configuration parameter [$$PushdownConfig].
    •  OPT_63008 ERROR: Configuration parameter [$$PushdownConfig] contains an invalid value.
    •  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.
    •  OPT_63014 Pushdown optimization to source stops at the transformation <transformation name> because the mapping contains too many pipeline branches.
    •  OPT_63015 Pushdown optimization to target stops at the transformation <transformation name> because the mapping contains too many pipeline branches.
    •  OPT_63021 Pushdown optimization stops at the transformation <transformation name> because it is connected to multiple targets.
    •  OPT_63022 Pushdown optimization stops at the transformation <transformation name> because no port depends on values from the upstream transformation <transformation name>.
    •  OPT_63070 Pushdown optimization to the source stops at the transformation <transformation name> because it is a partition point and the partition type is not hash auto-keys or pass-through.
    •  OPT_63072 Pushdown optimization to the source stops at the partition point <transformation name> because the source is not key-range partitioned.
    •  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.
    •  OPT_63077 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.
    •  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.
    •  OPT_63079 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.
    •  OPT_63080 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.
    •  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.
    •  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.
    •  OPT_63083 Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Joiner transformation is not properly partitioned on the join key.
    •  OPT_63102 Pushdown optimization stops at Source Qualifier transformation <transformation name> because it contains an SQL override, and view creation is not enabled.
    •  OPT_63106 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because SQL override is specified for some but not all partitions.
    •  OPT_63107 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains an SQL override with Informatica join syntax.
    •  OPT_63108 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains a user-defined join with Informatica join syntax.
    •  OPT_63120 Pushdown optimization stops at the Aggregator transformation <transformation name> because there is an upstream Aggregator transformation.
    •  OPT_63131 Pushdown optimization stops at the Joiner transformation <transformation name> because an input pipeline contains an Aggregator transformation.
    •  OPT_63133 Pushdown optimization stops at the Joiner transformation <transformation name> because it is configured for an outer join and the master source joins multiple tables.
    •  OPT_63147 Pushdown optimization stops at the Lookup transformation <transformation name> because it is downstream from an Aggregator transformation.
    •  OPT_63152 Pushdown optimization stops at the Sorter transformation <transformation name> because the distinct key <port name> is not used downstream.
    •  OPT_63157 Pushdown optimization stops at the Union transformation <transformation name> because the sources use different database connections.
    •  OPT_63170 ERROR: Pushdown optimization stops at the transformation <transformation name> because it contains an invalid expression.
    •  OPT_63175 ERROR: Pushdown optimization stops at the transformation <transformation name> because the mapping parameter <mapping parameter name> cannot be expanded.
    •  OPT_63177 Pushdown optimization stops at the transformation <transformation name> because expression <expression name> with < parameter name> parameters cannot be pushed to the database.
    •  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>.
    •  OPT_63205 Error encountered while attempting to partition session at runtime.
    •  OPT_63206 Invalid Partition Count <count>.
    •  OPT_63207 Partition Count is 1. Dynamic Partitioning has been disabled.
    •  OPT_63213 Error retrieving database partition information <database name>.
    •  OPT_63214 Error creating partitions.
    •  OPT_63215 Error partitioning session attributes.
    •  OPT_63216 Error partitioning key range for transformation <transformation name>.
    •  OPT_63217 Transformation <transformation name> uses a key range data type that cannot be partitioned.
    •  OPT_63218 Key range not closed.
    •  OPT_63219 Transformation <transformation> uses pass-through partitioning which is disallowed by dynamic partitioning.
    •  OPT_63220 Transformation <transformation name> specifies user defined SQL that will not be partitioned.
    •  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.
    •  OPT_63222 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK readers is not supported.
    •  OPT_63223 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK writers is not supported.
    •  OPT_63224 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML readers is not supported.
    •  OPT_63225 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML writers is not supported.
    •  OPT_63226 Transformation <transformation name> will not be partitioned because partitionable attribute <attribute name> has a user specified value.
    •  OPT_63227 Transformation <transformation name> is not partitionable.
    •  OPT_63229 Unable to determine count of partitions for Dynamic Partitioning because an error was encountered while expanding parameter <parameter name>.
    •  OPT_63234 Dynamic partitioning failed to detect the number of CPUs because of the following system error: <error>.
    •  OPT_63282 Source-side pushdown optimization stops at partition point <partition name>.
•  P Message Codes
  •  Parser Messages
    •  Parser_34300 Failed to parse file_name. This metadata cannot be read.
    •  Parser_34301 Error message returned by parser
  •  PCCL Messages
    •  PCCL_97001 Cannot get connection property <property name>.
    •  PCCL_97006 The Integration Service failed to support recovery for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97007 Failed to get connection reference for Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97008 Failed to get connection for Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97009 The Integration Service failed to initialize connection properties for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97010 Cannot get session property <session property name>.
    •  PCCL_97011 The Integration Service failed to initialize session properties for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97012 The Integration Service failed to initialize the driver for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97013 The Integration Service failed to initialize the source for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97014 Cache folder specified for reader partition <partition> is invalid.
    •  PCCL_97015 The Integration Service partition <partition> failed to register for recovery.
    •  PCCL_97019 Fatal error occurred while fetching messages.
    •  PCCL_97020 The Integration Service partition <partition> failed to close checkpoint at real-time flush point: <error message>.
    •  PCCL_97021 The Integration Service partition <partition> failed to close checkpoint at EOF: <error message>.
    •  PCCL_97022 The Integration Service partition <partition> failed to cache message.
    •  PCCL_97023 Failed to deserialize cache message: <error message>.
    •  PCCL_97024 The Integration Service partition <partition> truncated last cached message from cache.
    •  PCCL_97025 The Integration Service partition <partition> failed to truncate message cache to last serialized message: <error message>.
    •  PCCL_97026 The Integration Service partition <partition> failed to flush the cache: <error message>.
    •  PCCL_97027 The Integration Service failed to connect to the external data source.
    •  PCCL_97028 The Integration Service partition <partition> failed to unregister for recovery.
    •  PCCL_97029 The Integration Service partition <partition> failed to read cached message.
    •  PCCL_97030 Failed to serialize cache message: <error message>.
    •  PCCL_97031 Cache folder attribute cannot be fetched for reader partition <partition>.
    •  PCCL_97033 The Integration Service failed to initialize the metadata extension for the Source Qualifier instance <Source Qualifier name>.
    •  PCCL_97034 Error threshold for the session is reached. The number of errors encountered has exceeded the threshold value <error threshold number>.
  •  PCSF Messages
    •  PCSF_10004 Authentication for <user name> failed because <error message>.
    •  PCSF_10005 An attempt to <activity> access <object name> failed for <user name> because: <error text>.
    •  PCSF_10006 No Integration Service Ref were provided.
    •  PCSF_10007 Cannot connect to repository <repository name> because: <error text>.
    •  PCSF_10013 The file domains.infa was not defined in the system properties.
    •  PCSF_10015 Cannot process this request without domain name or host name and port number.
    •  PCSF_10017 Failed to receive response from <URL> because: <error text>.
    •  PCSF_10019 Operation <operation name> of service <service name> failed because: <error text>.
    •  PCSF_10020 Cannot write to file <domain file name>.
    •  PCSF_10024 Timed out while trying to connect to domain <domain name> to lookup service <service name>.
    •  PCSF_10025 Cannot parse message: <error text>.
    •  PCSF_10027 No gateway connectivity is found for domain <name>.
    •  PCSF_10028 Cannot respond to operation <operation name> of service <service name>: <error text>.
    •  PCSF_10039 Linked domain <linked domain name> must specify at least one gateway.
    •  PCSF_10060 Value <value> exceeded maximum length <maximum length>.
    •  PCSF_10081 Cannot deserialize <node or domain> configuration file <metadata file name>.
    •  PCSF_10095 An unexpected token was encountered during deserialization.
    •  PCSF_10131 The license key was previously applied.
    •  PCSF_10132 You cannot apply more than one original key to a license. To update an existing license, select a license file with an incremental key.
    •  PCSF_10133 The issue date for the original key must be earlier than the issue dates for the incremental keys.
    •  PCSF_10135 Cannot decrypt the license key.
    •  PCSF_10136 License is invalid. The Licensing Service encountered an invalid attribute value in the license.
    •  PCSF_10137 License is invalid. The Licensing Service encountered an invalid value <begin date value> for the Begin Date attribute.
    •  PCSF_10138 License is invalid. The Licensing Service encountered an invalid value <expiry date value> for the Expiry Date attribute.
    •  PCSF_10139 License is invalid. The Licensing Service encountered an invalid value <issue date value> for the Issue Date attribute.
    •  PCSF_10140 License is invalid. The Licensing Service encountered an invalid value <number of CPUs> for the CPUs attribute.
    •  PCSF_10141 License is invalid. The Licensing Service encountered an invalid value <number of repositories> for the repositories attribute.
    •  PCSF_10304 Cannot connect to URL <URL> to perform operation <operation name> of service <service name>.
    •  PCSF_10305 Cannot connect to gateway <node address> to look up service <service name>.
    •  PCSF_10306 Operation <operation name> of service <service name> was interrupted.
    •  PCSF_10322 The following error occurred while logging to Log Service: <error text>.
    •  PCSF_10325 Error threshold exceeded for number of failed log attempts. Disabling guaranteed messaging.
    •  PCSF_10326 The following error occurred while generating the guaranteed message file: <error text>.
    •  PCSF_10327 The following error occurred while writing to the guaranteed message file <file name>: <error text>.
    •  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.
    •  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.
    •  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.
    •  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.
    •  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.
    •  PCSF_10341 Cannot create a license with an incremental key.
    •  PCSF_10342 Exception occurred: <error message>.
    •  PCSF_10353 Error parsing upgrade configuration file: <error text>.
    •  PCSF_10354 Unable to identify the service type for configuration file <file name>. The file might be an invalid configuration file.
    •  PCSF_10355 Configuration file <file name> is missing the required option(s) <option names>.
    •  PCSF_10356 File <file name> has extension other than .cfg. Upgrade only works with .cfg file.
    •  PCSF_10357 File <file name> contains service <service name> which already exists in domain <domain name>.
    •  PCSF_10358 Upgrade configuration files directory is not found on node <node name>.
    •  PCSF_10359 File <file name> contains service <service name> which already exists in other configuration files selected for upgrade.
    •  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>.
    •  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.
    •  PCSF_10374 Failed to persist <object> with error <error message>.
    •  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.
    •  PCSF_10389 The Repository Agent configuration file <configuration file name> is located in the PCServer directory. This directory should only contain PowerCenter Server configuration files.
    •  PCSF_10391 Configuration file contains required option(s) <option names> with empty value.
    •  PCSF_10392 <error text>
    •  PCSF_10402 Unable to validate the log directory <shared disk> due to the error <error>.
    •  PCSF_10404 The log directory <shared directory> cannot be created.
    •  PCSF_10408 Failed at line #<line number> because option is missing value assignment.
    •  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.
    •  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.
    •  PCSF_10421 Error parsing upgrade configuration file at line #<line number>. The end string */ for block comment must be at the end of the line.
    •  PCSF_10422 Error parsing upgrade configuration file. The start of block comment was detected at line #<line number>; however, the end string */ for ending block comment was never found.
    •  PCSF_10423 File <file name> is a Repository Agent configuration file. Choose a PowerCenter Server configuration file or change the configuration file type.
    •  PCSF_10424 File <file name> is a PowerCenter Server configuration file. Choose a Repository Agent configuration file or change the configuration file type.
    •  PCSF_10426 Cannot find server <server name> in repository <repository name>.
    •  PCSF_10427 Option has invalid value <invalid value>.
    •  PCSF_10428 Option number <invalid value> is in an invalid format.
    •  PCSF_10429 Required option <option name> missing.
    •  PCSF_10430 Duplicate option <duplicate option name> found.
    •  PCSF_10431 Unknown option <option name> found.
    •  PCSF_10432 Option group <expected option group> misnamed as <actual option group>.
    •  PCSF_10433 Option field cannot be empty.
    •  PCSF_10434 Option specified an invalid email address of <entered email address>.
    •  PCSF_10436 Unknown value <unknown value> found.
    •  PCSF_10439 Failed to load the list of codepages: <SDK exception message from locale manager>
    •  PCSF_10440 Value <value> contains invalid spaces.
    •  PCSF_10441 Reference to linked domain <domain name> not defined.
    •  PCSF_10442 Failed to drop domain tables.
    •  PCSF_10443 CPU architecture <architecture name> is not supported.
    •  PCSF_10445 Option <option name> is greater than option <option name>.
    •  PCSF_10446 Option memory size <invalid value> must be blank or a number followed by optional K or M.
    •  PCSF_10458 Database name should not be defined with connection string.
    •  PCSF_10459 Database name should not be defined with connection string.
    •  PCSF_10460 Either database service name or connection string should be specified, but not both.
    •  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.
    •  PCSF_10507 The Integration Service cannot use operating system profiles on Windows node <node name> in <service name>.
    •  PCSF_10524 The selected database type <database type> does not support tablespaces.
    •  PCSF_10535 Cannot read PowerCenter installation directory and version from nodemeta.xml.
    •  PCSF_10536 Cannot start node because nodemeta.xml does not contain values for the PowerCenter installation directory or version.
    •  PCSF_10537 Cannot run application service <service name> of version <service version> on node <node name>.
    •  PCSF_10538 Cannot create application service <service name> of version <service version> in domain of version <domain version>.
    •  PCSF_46000 INFA_DOMAINS_FILE is not set in the environment variable.
    •  PCSF_46002 Failed to communicate with the server at <server address>.
    •  PCSF_46003 Failed to understand the response <response text> from server at <server address>: <error text>.
    •  PCSF_46006 Domain name is not specified.
    •  PCSF_46007 No gateway connectivity is provided for domain <domain name>.
    •  PCSF_46008 Cannot connect to domain <domain name> to look up service <service name>.
    •  PCSF_46009 Invalid type <object type> encountered. Failed to create an object instance.
    •  PCSF_46010 Cannot parse message: <reason for error>
    •  PCSF_46012 Cannot write to file <file name>.
    •  PCSF_46013 Cannot connect to URL < URL > to perform operation <operation name> of service <service name>.
    •  PCSF_46014 Cannot connect to gateway to look up service <service>.
    •  PCSF_46015 An unexpected token was encountered during deserialization.
  •  PETL Messages
    •  PETL_24042 The Preparer DTM has timed out after waiting <time in seconds> seconds for the Master DTM to connect.
    •  PETL_24045 The Master DTM failed to connect to the Preparer DTM.
    •  PETL_24046 The Master DTM timed out after <time in seconds> seconds while trying to connect to the Preparer DTM.
    •  PETL_24048 The Master DTM failed to fetch the prepared session from the Preparer DTM.
    •  PETL_24049 Failed to get the initialization properties from the master service process for the prepare phase <error message> with error code <error code>.
    •  PETL_24061 The Master DTM exceeded the maximum wait time while waiting for all Worker DTMs to connect.
    •  PETL_24063 The Preparer DTM encountered error <error message> with error code <error code> while notifying the Integration Service of the prepare phase status.
    •  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>.
    •  PETL_24065 Error: Thread <thread name> exceeded the maximum wait time while waiting for a reply from the Master DTM.
    •  PETL_24066 The Master DTM connection with the Worker DTM running partition group <partition group ID> was broken unexpectedly. The Master DTM will abort processing.
    •  PETL_24067 The Worker DTM connection with the Master DTM terminated unexpectedly. The Worker DTM will stop processing the session.
    •  PETL_24072 Error: Thread <thread name> failed to get a reply from the Master DTM.
    •  PETL_24074 Failed to send updates to the master service process. Session run will be terminated.
  •  PMF Messages
    •  PMF_15000 Failed to read from file <file name>.
    •  PMF_15001 Failed to write to file, there may not be enough space left on the device.
    •  PMF_15002 Failed to seek in file <file name>.
    •  PMF_15003 File <file name> is not in the correct format.
    •  PMF_15004 Unable to open file <file name>.
    •  PMF_15005 File <file name> is in an unknown state due to error from a previous run.
    •  PMF_15006 Failed to create file <file name> because file exists and contains data.
    •  PMF_15007 Failed to read file <file name> because PowerCenter/PowerMart file header is corrupt.
    •  PMF_15008 I/O requested for invalid file ID.
    •  PMF_15009 Specified file name <file name> exceeds the maximum length of 256 characters.
    •  PMF_15010 The number of files exceeds the maximum number of 256.
    •  PMF_15011 Unable to allocate memory.
    •  PMF_15012 Unable to delete file <cache file name>. System error is <error number> <error message>.
    •  PMF_15013 Unable to rename file <cache file name> to <cache file name>. System error is <error number> <error message>.
    •  PMF_15014 Unable to stat file <cache file name>. System error is <error number> <error message>.
    •  PMF_15016 Failed to get a shared lock on file <cache file name>. System error is <error number> <error message>.
    •  PMF_15017 Failed to get an exclusive lock on file <cache file name>. System error is <error number> <error message>.
    •  PMF_15018 Failed to unlock file <cache file name>. System error is <error number> <error message>.
    •  PMF_15019 Failed to open file <file name>.
  •  PMJVM Messages
    •  PMJVM_42011 The DTM process failed to close the JVM session.
  •  PR Messages
    •  PR_18001 Application Source Qualifier instance <Application Source Qualifier name> has tree source <tree source definition name> and an Extract Override. Extract override will be ignored.
    •  PR_18003 Tree <tree name> with SetId <tree setid> and Effective Date <date> was not created.
    •  PR_18004 Application Source Qualifier instance <Application Source Qualifier name> has more than one tree attached.
    •  PR_18005 Tree may only be joined with Detail record: <PeopleSoft record name>.
    •  PR_18006 Not all sources are related in Application Source Qualifier <Application Source Qualifier name>.
    •  PR_18007 Unknown error occurred in Application Source Qualifier <Application Source Qualifier name>.
    •  PR_18009 Error in converting <string> to Date. Internal Error.
    •  PR_18010 Tree <tree name> was changed after session run was started.
    •  PR_18011 Application Source Qualifier <Application Source Qualifier name> has projected port with no inbound link.
    •  PR_18012 SQL Error <SQL statement>.
    •  PR_18013 Warning: Application Source Qualifier transformation <Application Source Qualifier name> has a larger number of sorted ports than projected output ports.
    •  PR_18020 The language table <language table name>, for the base table <base table name>, does not have rows for the language <language code>.
    •  PR_18021 The Application Source Qualifier <Application Source Qualifier> has invalid user defined query <query> with character error at <number> location.
    •  PR_18022 The Application Source Qualifier <Application Source Qualifier> has invalid filter clause <filter> with character error at <number> location.
    •  PR_18023 The Application Source Qualifier <Application Source Qualifier> has invalid join and/or filter override <join override> with character error at <number> location.
    •  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.)
    •  PR_18027 Application Source Qualifier <Application Source Qualifier name>: Error in preparing the query for effective date data extraction.
    •  PR_18028 Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract Join Order with invalid source names.
    •  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.
    •  PR_18030 Application Source Qualifier <Application Source Qualifier name> cannot have Effective Date Extract Join Order when number of Effective Dated sources is one.
    •  PR_18031 Application Source Qualifier <Application Source Qualifier name> has invalid Extract Date.
    •  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.
    •  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.
    •  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.
    •  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.
    •  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.
    •  PR_18037 Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, with an invalid effective date.
    •  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.
    •  PR_18040 Application Source Qualifier <Application Source Qualifier name>: Error! The TO_EFFDT field cannot be projected if there is no primary or PeopleSoft key in the source.
  •  PWX Messages
    •  PWX-34000 Unable to stop PowerExchange Task. iSync not established.
    •  PWX-34001 Monitor thread - caught exception. Message ''message''.
    •  PWX-34002 PowerExchange Task call to set Sync URI failed - caught exception. Message ''message''.
    •  PWX-34003 Failed to connect to PowerExchange Task iSync listener (timed out).
    •  PWX-34004 Failed to connect to PowerExchange Task iSync listener.
    •  PWX-34005 Failed to send message to PowerExchange Task iSync listener.
    •  PWX-34006 Heartbeat connection to PowerExchange Task lost. Service ending.
    •  PWX-34007 Configuration option option or value value not recognised.
    •  PWX-34008 Configuration options not found.
    •  PWX-34009 Failed to launch PowerExchange process process.
    •  PWX-34010 PowerExchange service initialization failed.
    •  PWX-34011 Ending PowerExchange process process
    •  PWX-34012 Failed to send message to PowerExchange Task command handler.
    •  PWX-34013 User user does not have privilege privilege set.
    •  PWX-34504 Trying to connect to PowerExchange Task. Approx seconds seconds remaining...
  •  PWXCMD Messages
    •  PWXCMD_20000 ERROR: ''error_message''
    •  PWXCMD_20001 This command requires either the DomainName or Gateway option.
    •  PWXCMD_20002 The node [''node_name''] does not exist in the domain
    •  PWXCMD_20003 The service [''service_name'] is not a Listener Service
    •  PWXCMD_20004 The service [''service_name'] is not a Logger Service
    •  PWXCMD_20005 Error communicating with service [''service_name'']. See log for more details
    •  PWXCMD_20006 Command not applicable to service [''service_name''].
    •  PWXCMD_30084 Invalid address format. Expected format is host:port.
    •  PWXCMD_30089 Invalid port number [port_number]
    •  PWXCMD_30357 Could not connect to peer due to [service_connection_error]
    •  PWXCMD_30358 No gateway connectivity is found for domain [domain_name].
    •  PWXCMD_30359 Connection definition not found for: [connection_name].
    •  PWXCMD_30360 Definition for operation [operation_name] not found.
    •  PWXCMD_30361 Definition for field [field_name] in operation [operation_name] not found.
    •  PWXCMD_30362 Definition for field [field_name] in operation [operation_name] mismatch (details)
    •  PWXCMD_30363 General Logic Error: [error_message]
    •  PWXCMD_30364 Connection name argument invalid
    •  PWXCMD_30365 Data object name argument invalid
    •  PWXCMD_30366 Schema name argument invalid
    •  PWXCMD_30367 Model [data_model] - import warning: [validation_warning]
    •  PWXCMD_30368 Cannot load PowerExchange. Please check PWX_HOME environment variable.
    •  PWXCMD_34024 Invalid replace value 'replace_value'.
  •  PWXLog Messages
    •  PWXLog_009 Cannot load PowerExchange. Ensure PWX_HOME environment variable is set.
    •  PWXLog_34780 Invalid logger level 'logger_level'
  •  PWXNative Messages
    •  PWXNative_001 Cannot access resource "resource_name". Error: error.
    •  PWXNative_002 Error calling resource "resource_name" with API function "api_function". Error: "error_message".
    •  PWXNative_003 Invalid environment handle.
    •  PWXNative_004 Invalid connection handle.
    •  PWXNative_005 Invalid statement handle.
    •  PWXNative_006 error_message
    •  PWXNative_007 One or more characters in the password are not supported by PowerExchange.
  •  PWXPC Messages
•  R Message Codes
  •  REGEX Messages
    •  REGEX_34005 REG_MATCH function takes two arguments.
    •  REGEX_34006 The subject and pattern argument must be of the char datatype.
    •  REGEX_34007 The Integration Service failed to compile the pattern.
    •  REGEX_34008 REG_EXTRACT function requires at least two arguments.
    •  REGEX_34009 REG_EXTRACT function takes a maximum of three arguments.
    •  REGEX_34010 The Integration Service failed to validate the subject because of a perl compatible regular expression syntax error.
    •  REGEX_34011 The Integration Service failed to extract the subpattern because of a perl compatible regular expression syntax error.
    •  REGEX_34014 REG_REPLACE function takes three or four arguments.
  •  REP Messages
    •  REP_12001 Failed to log onto database server.
    •  REP_12005 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.
    •  REP_12014 An error occurred while accessing the repository.
    •  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>.
    •  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>.
    •  REP_12033 The repository being accessed is incompatible with this version.
    •  REP_12119 A repository does not exist at the specified database connection.
    •  REP_12122 Unable to unlock this folder. Please try again.
    •  REP_12123 Unable to delete this folder. Please try again.
    •  REP_12124 Unable to delete this folder. The folder is in use by another user.
    •  REP_12164 Domain-related error: <error message>.
    •  REP_12225 The value entered is not valid for memory attributes.
    •  REP_12233 Increment By must be less than or equal to 2147483647.
    •  REP_12325 Internal error. No connection callback.
    •  REP_12326 Error getting connection information for remote repository.
    •  REP_12327 Internal error. Connection callback returned an error.
    •  REP_12328 The repository at this location does not have the same name.
    •  REP_12330 Failed to fetch repository information.
    •  REP_12332 Error initializing repository object information.
    •  REP_12333 More than one GDR found.
    •  REP_12334 Repository name mismatch.
    •  REP_12335 The current repository is not a GDR.
    •  REP_12336 This repository is already registered with the GDR <global repository name>.
    •  REP_12337 This is not a local repository.
    •  REP_12338 A repository with this name has already been registered.
    •  REP_12339 Internal error. Error allocating a new repository ID.
    •  REP_12340 Error updating remote repository.
    •  REP_12341 Error updating GDR.
    •  REP_12342 The selected repository is not registered with the current Global Repository.
    •  REP_12346 Memory allocation failed.
    •  REP_12347 An error occurred while updating connection information in the repository.
    •  REP_12352 The current user does not have the privilege to perform this operation.
    •  REP_12355 The object <object name> has been modified since the time it was read.
    •  REP_12357 The object <object name> is already locked by <user name>. Do you want to reobtain the lock?
    •  REP_12363 Warning: Unable to check whether correct indices for the Teradata repository have been created. Please verify that you backup the repository and then restore it after you upgrade it.
    •  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.
    •  REP_12370 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A repository upgrade is required.
    •  REP_12371 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A product upgrade is required.
    •  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.
    •  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.
    •  REP_12381 Unable to perform the operation since an expected object was not found. Please check the repository.
    •  REP_12382 Error while updating the object information in the repository. Either no row or more than one row was updated.
    •  REP_12386 There is no database object available for the repository <repository name>. (A repository is not supported on the requested database or the appropriate database driver is not available.
    •  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.
    •  REP_12389 Unable to set database connection property <number>.
    •  REP_12390 Mapping <mapping name> contains a dependency that points to a non existent port. The mapping is assumed to be invalid.
    •  REP_12392 GID creation failed for repository <repository name>.
    •  REP_12403 Unable to retrieve locale information.
    •  REP_12404 Failed to allocate new IDs for internal sequence generator: <sequence name>.
    •  REP_12405 Failed to fetch new IDs.
    •  REP_12415 Error comparing last saved times for objects in this folder!
    •  REP_12416 Error comparing deployed times for shared folders!
    •  REP_12422 Unable to connect to GDR!
    •  REP_12449 Internal error.
    •  REP_12450 Unable to create output file <file name>.
    •  REP_12452 Failed to write to file <file name>!
    •  REP_12454 Unable to open input file <file name>!
    •  REP_12456 Failed to read from file <file name>!
    •  REP_12457 Unexpected data in file <file name>!
    •  REP_12466 Error inserting repository object information.
    •  REP_12467 Error inserting repository object attribute information.
    •  REP_12468 Error inserting server locale information.
    •  REP_12469 Error initializing object tree.
    •  REP_12470 Error updating repository information.
    •  REP_12471 Error creating first user.
    •  REP_12477 This repository contains folders which are currently in use. A repository cannot be deleted while it is in use.
    •  REP_12488 Unable to add new internal sequence generator.
    •  REP_12492 This repository contains folders which are currently in use. A repository cannot be upgraded while folders are in use.
    •  REP_12494 The Repository is newer than the version supported by this software release. Unable to do an upgrade.
    •  REP_12496 This repository is too old to be upgraded.
    •  REP_12505 Error while executing script file <file name>.
    •  REP_12581 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.
    •  REP_12589 Error occurred in locking.
    •  REP_12590 Error updating <repository name> in GDR.
    •  REP_12591 Error updating <repository name> in GDR (Repository may be left in inconsistent state).
    •  REP_12651 Memory allocation failed.
    •  REP_12654 Password is too long.
    •  REP_12678 The connection to Global DataMart Repository is unavailable for some reason.
    •  REP_12708 Unable to allocate memory.
    •  REP_12709 Unable to find database type for this source.
    •  REP_12734 The source database <source database connection> and Integration Service <Integration Service name> do not have compatible code pages (one way compatibility is required).
    •  REP_12735 The source file <file name> and Integration Service <Integration Service name> do not have compatible code pages. (One way compatibility is required.)
    •  REP_12736 The database <database name> and Integration Service <Integration Service name> do not have compatible code pages.
    •  REP_12773 The Global Repository code page (<code page name>) is not compatible with the selected code page (<code page name>).
    •  REP_12782 The repository <repository name>’s code page <code page name> and <PowerCenter Client>’s code page <code page name> are incompatible.
    •  REP_12934 Failed to fetch information for user <user name>.
    •  REP_12950 Lookup Transformation <transformation name> has INVALID lookup condition: Lookup Table Column <column name> and Transformation Port <port name> are the same.
    •  REP_12951 The lookup condition is not valid: Lookup Table Column <column name> and Transformation Port <port name> are the same. Transformation is not valid.
    •  REP_12952 Joiner Transformation <transformation name> has INVALID joiner condition: Master <port name> and Detail <port name> are the same.
    •  REP_12953 The joiner condition is not valid: Master <port name> and Detail <port name> are the same. Transformation is not valid.
    •  REP_12954 Warning: The Call Text attribute of Stored Procedure transformation <transformation name> has non-empty value when the Stored Procedure Type attribute is set to Normal.
    •  REP_12955 Warning: The Call Text attribute of Stored Procedure transformation has non-empty value when attribute Store Procedure Type is set to Normal.
    •  REP_12975 There is no existing MQ Connection to choose for <connection string> in the target repository.
    •  REP_12991 Failed to connect to <repository name> Repository Agent on host <host name> (port number: <port number>). System error message: <error message>.
    •  REP_12994 Server system error (errno = <error number>): <system error message>.
    •  REP_12995 Failed to shutdown Integration Service.
    •  REP_12996 No key is selected for Sorter transformation <transformation name>.
    •  REP_12999 No key is selected for Sorter transformation. This transformation is not valid.
    •  REP_22674 Custom Transformation <transformation name> has non-ASCII character(s) in its class name.
    •  REP_32000 Error: Could not find DSQ instance <Source Qualifier name> for <source>.
    •  REP_32001 Error: Source Reference: <source> DBD: <source> for DSQ <Source Qualifier name> not found.
    •  REP_32002 Error: There are more than one groups with the order: <number> in <group>.
    •  REP_32003 Error: Field order does not match group order.
    •  REP_32004 Error: Invalid Transformation type <type> for transformation <transformation name>.
    •  REP_32007 Folder referenced by the shortcut object does not exist, object will be created in the current folder.
    •  REP_32010 Error: Object referenced by shortcut: <shortcut>. Referring to <object> in Repository: <repository name>. Folder: <folder name> not found.
    •  REP_32011 Internal Error: Could not copy object.
    •  REP_32013 Error encountered while Parsing file.
    •  REP_32014 The DTD file name is not specified.
    •  REP_32015 Code page in file: <file name> not compatible with repository code page: <code page>.
    •  REP_32016 Error: Invalid Database Type: <database type>.
    •  REP_32018 Invalid Delimiters: <delimiter>.
    •  REP_32019 Error: Invalid table attribute: <attribute>.
    •  REP_32020 Warning: Could not link fields <field name>:<field name>:<field name>: Instance <instance> to Field: <field name> Instance <instance>.
    •  REP_32021 Error: Invalid Key Type: <key type>.
    •  REP_32022 Error: Invalid Group <group> for field <field name>.
    •  REP_32023 Error: Cannot determine ODBC Data type for field <field name>.
    •  REP_32025 Error: Invalid Field Attribute: <attribute> found for field: <field>.
    •  REP_32026 Error: Could not find field: <field> in Instance: <instance>.
    •  REP_32027 Error: Could not Resolve Foreign key dependency For Field: <field> in Source: <source>.
    •  REP_32028 Error: This source cannot have groups.
    •  REP_32029 Error: could not add group <group>.
    •  REP_32030 Database Error: while Assigning Ids for Source: <source name>.
    •  REP_32031 Error: Missing or Invalid TYPE attribute for Group: <group>.
    •  REP_32032 Error: Cannot import tables of type <TABLETYPE value>.
    •  REP_32033 Error: This target cannot have groups.
    •  REP_32034 Database Error: while Assigning Ids for Target: <target name>.
    •  REP_32035 Error: Invalid Initialization Property: <INITPROP name>.
    •  REP_32036 Error: This transformation cannot have groups.
    •  REP_32037 Database Error: while Assigning Ids for Transformation: <transformation>.
    •  REP_32038 Error: Invalid Datatype: <datatype> for field: <field name>.
    •  REP_32039 Error: Missing ATTRIBUTE <XML attribute name> for field: <SOURCEFIELD name or TRANSFORMFIELD name>.
    •  REP_32040 Error: Could not find associated source field: <SOURCEFIELD name> for <Normalizer transformation>.
    •  REP_32041 Error: Invalid Instance Type: <TYPE value>.
    •  REP_32042 Error: Invalid reference field <REF_FIELD name> for Transformation field: <TRANSFORMFIELD name>.
    •  REP_32043 Error: Missing attribute <MAPPLETGROUP> or <REF_FIELD> for Field: <mapplet name>.
    •  REP_32044 Error: Missing attribute <REF_FIELD> for Field: <TRANSFORMFIELD name>.
    •  REP_32045 Error: Invalid reference field: <REF_FIELD> for Lookup Field: <TRANSFORMFIELD name> Transformation: <transformation name>.
    •  REP_32046 Error: Invalid reference field: <REF_FIELD> for Field: <TRANSFORMFIELD name> Transformation: <TRANSFORMATION name>.
    •  REP_32047 Error: Invalid Mapplet Group <MAPPLETGROUP> for Field: <MAPPLETGROUP value> Transformation: <transformation name>.
    •  REP_32050 Error: Could not find Transformation definition for: <transformation or source or target name>.
    •  REP_32056 Error: Missing or Empty Attribute: <attribute name>.
    •  REP_32057 Error: Populating default fields for MQ Source.
    •  REP_32058 Error: Populating default fields for MQ Target.
    •  REP_32060 Error: Could not get datatype description for field: <field name>.
    •  REP_32063 Error: An Unknown target field attribute: <attribute ID> has been detected for Field: <field name>.
    •  REP_32066 Error: Could not get group for source field: <source field>.
    •  REP_32072 Invalid date in schedule info.
    •  REP_32074 Failed to export SAPFUNCPARAM:<SAP Function Parameter>.
    •  REP_32079 Failed to export SAPVariable <SAP variable>.
    •  REP_32081 Invalid schedule info.
    •  REP_32087 Error: Unable to get mapping name.
    •  REP_32088 Error: Unable to fetch database connection.
    •  REP_32089 Error: Unable to fetch registered server information for the session.
    •  REP_32090 Error: Unable to fetch session attributes.
    •  REP_32091 Error: Unable to fetch mapping DSQ related information.
    •  REP_32092 Error: Unable to fetch database connection: <database connection> associated with the data Source Qualifier transformation: <transformation name>.
    •  REP_32093 Error: Unable to fetch partitions for the session <session name>.
    •  REP_32095 Error: Invalid Mapping Name for the session <session name>.
    •  REP_32096 Error: Invalid FTP Name <FTP connection>.
    •  REP_32097 Warning: FTP connection <FTP connection> not found. Session will be imported without reference to FTP connection.
    •  REP_32098 Warning: Loader connection <external loader connection> not found. Session will be imported without reference to Loader connection.
    •  REP_32101 Error: Internal Error encountered in initializing Parser.
    •  REP_32103 Warning: Invalid Usage type: <type> for field: <field name>.
    •  REP_32105 Error: Invalid Codepage: <code page> for Flat File.
    •  REP_32111 Error: Invalid Database Type: <DATABASETYPE value> for source: <SOURCE name>.
    •  REP_32112 Error: Missing or Empty Name for: <element>.
    •  REP_32113 Error: Invalid number of fields for transformation: <Sequence transformation name>.
    •  REP_32115 Error: <object> <object name> cannot be imported as it is potentially unsafe. Importing any associated mapping/mapplet might result in an error.
    •  REP_32116 Error: The mapping: <mapping name> is potentially unsafe and cannot be imported.
    •  REP_32117 Error: <transformation type> <transformation name> is potentially unsafe and will not be available for import.
    •  REP_32118 Error: Invalid Usage Flags: <flag>.
    •  REP_32121 Warning: Removing instance <instance name>. Could not find source instance for this Source Qualifier transformation instance.
    •  REP_32122 Error: Transformation <transformation name> has an invalid reusable setting.
    •  REP_32123 Error: Rank transformation <transformation name> has an invalid first field name. It has to be RANKINDEX.
    •  REP_32124 Field <field name> has missing or invalid expression type.
    •  REP_32131 Error: Rank transformation <transformation name> has no RANK PORT. This transformation is invalid.
    •  REP_32132 Error: Transformation <transformation name> has duplicate group <group> due to the same group order.
    •  REP_32135 Error: Invalid precision: <number> specified for field: <field name>. The maximum precision is 65535.
    •  REP_32136 Error: Invalid scale: <number> specified for field: <field name>. The scale cannot be greater than the precision or the maximum scale which is 65535.
    •  REP_32137 The first field of lookup transformation <transformation name> has to be a Dynamic Lookup field when dynamic lookup cache is enabled. Transformation is not valid.
    •  REP_32138 Field <field name> for lookup transformation <transformation name> cannot be a Dynamic Lookup field when dynamic lookup cache is disabled. Transformation is not valid.
    •  REP_32139 In Lookup transformation <transformation name>, the content(s) of the generated Dynamic Lookup field <field name> has been changed. Transformation is not valid.
    •  REP_32140 In Rank transformation <transformation name>, the content(s) of the RANKINDEX field <field name> has been changed. Transformation is not valid.
    •  REP_32141 In Sequence Generator transformation <transformation name>, the content(s) of field <field name> has been changed. Transformation is not valid.
    •  REP_32144 Error: Missing or invalid attribute <attribute name> for <element name>: <attribute value>.
    •  REP_32148 Error: Invalid datatype for mapping variable <MAPPINGVARIABLE name>.
    •  REP_32149 Error: Invalid datatype for aggregate COUNT for mapping variable <MAPPINGVARIABLE name>.
    •  REP_32150 Error: Invalid aggregate type for mapping variable <MAPPINGVARIABLE name>.
    •  REP_32151 Error: No name for the imported mapping variable.
    •  REP_32167 Error: Duplicate instances of type: <instance type> name: <instance name>.
    •  REP_32171 The mapping originally assigned to this session has been changed. Cannot import the session.
    •  REP_32173 Error: Expected unsigned value for attribute: <attribute value>, found value: <value>.
    •  REP_32174 Error: Invalid value: <value>, expecting unsigned value for attribute: <attribute>, for <element>: <element name>.
    •  REP_32175 Error: Invalid target database type: <target database name> for target: <target name>.
    •  REP_32176 Two or more fields in the xml data Source Qualifier transformation: <Source Qualifier name> refer to the same field: <field name> in the source.
    •  REP_32177 Error: Invalid database type '<database type>' for target '<target name>'. A plugin required to handle this is missing. This target will not be available for import.
    •  REP_32178 Error: Invalid Database Type: <database type> for target: <target name>, or the Database Type is not installed in this repository.
    •  REP_32180 Error: Invalid Task type <task type> for task <task name>.
    •  REP_32181 Error: Invalid Extension type: <session extension type> for element <SESSIONEXTENSION element>.
    •  REP_32185 Error: The mapping <mapping name> associated with the session <session name> is invalid.
    •  REP_32186 Error: expected a timer for task <Timer task name>.
    •  REP_32188 Error: The mapping <mapping name> for session <session name> is not found in the target repository.
    •  REP_32190 Warning: session transformation instance <session transformation instance name> of type <transformation type> is not found for element <SESSIONEXTENSION>.
    •  REP_32191 Warning: missing or empty attribute <attribute name> for element <element name>.
    •  REP_32192 Error: Invalid Component Type <session component type> for element <SESSIONCOMPONENT name>.
    •  REP_32193 Error: missing or empty attribute <attribute name> for element <element name>.
    •  REP_32194 Error: Invalid partition type <PARTITIONTYPE name> for session transformation <SESSTRANSFORMATIONINST name>.
    •  REP_32195 Error: extension subType <SESSIONEXTENSION subtype> for extension type <SESSIONEXTENSION type> is invalid for element <SESSIONEXTENSION name>.
    •  REP_32196 Error: connection reference <connection reference> with connection number <number> is not found for element <SESSIONEXTENSION name> due to the following error:
    •  REP_32198 Error: Invalid connection type <connection type> for connection reference <connection reference>.
    •  REP_32199 Error: Invalid partition name <partition name> for element <element name>.
    •  REP_32202 Error: Invalid DSQ instance name < Source Qualifier transformation name> for session transformation instance <session transformation instance name>.
    •  REP_32203 Error: the number of partition <PARTITION name> is out of range [1-32] for session transformation <SESSTRANSFORMATIONINST name> in session <session name>.
    •  REP_32204 Error: building session <session name>.
    •  REP_32205 Error: Invalid DSQ <Source Qualifier name> of type <DSQINSTTYPE> for the extension in session transformation instance <SESSTRANSFORMATIONINST name>.
    •  REP_32207 Error: Invalid datatype for workflow variable <workflow variable name>.
    •  REP_32208 Error: The extension of type <SESSIONEXTENSION type> and subtype <SESSIONEXTENSION subtype> does not exist for session transformation instance <SESSTRANSFORMATIONINST name>.
    •  REP_32209 Error: Invalid suspension email <SUSPENSION_EMAIL name> for workflow <workflow name>.
    •  REP_32210 Error: Name conflict or invalid object name <object name> for element <element name>.
    •  REP_32211 Warning: missing both start and end range in key <KEYRANGE> for element <element name>.
    •  REP_32212 Warning: the session transformation <SESSTRANSFORMATIONINST name> does not exist in the mapping <mapping name> in target folder.
    •  REP_32213 Error: the session transformation <SESSTRANSFORMATIONINST name> is not partitionable and is connected to a stage with more than one partitions.
    •  REP_32214 Warning: invalid key name <KEYRANGE or HASHKEY name> for element <element name>.
    •  REP_32215 Error: Invalid DSQ type <DSQINSTTYPE> for element <SESSIONEXTENSION name>.
    •  REP_32216 Error: connection reference <CONNECTIONREFERENCE name> type <TYPE> and subtype <SUBTYPE> is not valid for the extension.
    •  REP_32217 Error: a partition name <PARTITIONNAME> is given for a non-partitionable connection reference for session transformation instance <session transformation instance name>.
    •  REP_32218 Error: Invalid task type <task type> for element <element name>.
    •  REP_32219 Warning: cannot find the referenced config object <REFOBJECTNAME>, default session config is used.
    •  REP_32220 Invalid partition type <PARTITIONTYPE> for session transformation <SESSTRANSFORMATIONINST>.
    •  REP_32222 Error: duplicate object <object name> of type <object type>.
    •  REP_32223 Error: two Schedulers of conflicting types specified for workflow <WORKFLOW name>: reusable <SCHEDULER under FOLDER> and nonreusable <SCHEDULER under WORKFLOW>.
    •  REP_32224 Error: Task <TASKNAME> is not found for instance <TASKINSTANCE name>.
    •  REP_32225 Error: Invalid value <value> for <attribute in SCHEDULER element> in Scheduler.
    •  REP_32292 Error: The transformation <transformation name> has no input groups.
    •  REP_32293 Error: The transformation <transformation name> has no output groups.
    •  REP_32294 Error: Group <group> of the transformation <transformation name> is both an input group and an output group.
    •  REP_32409 Session <session name> has a log file name which is longer than 600 characters. Session is not valid.
    •  REP_32410 Session has a log file name which is longer than 600 characters. Session is not valid.
    •  REP_32413 Session <session name> has a log directory name which is longer than 600 characters. Session is not valid.
    •  REP_32414 Session has a log directory name which is longer than 600 characters. Session is not valid.
    •  REP_32426 Session config <session configuration object name>. The number of runs to save session log on must be in the range 0 to 2147483647.
    •  REP_32427 The number of runs to save session log on must be in the range 0 to 2147483647.
    •  REP_32467 Parameter file name is too long.
    •  REP_32469 Log file name is too long.
    •  REP_32473 Log count must be in the range of 0 to 2147483647.
    •  REP_32471 Log directory name is too long.
    •  REP_32472 'Save workflow log for these runs' must be in the range of 0 to 2147483647.
    •  REP_32475 Workflow task <workflow name> parameter file name is too long.
    •  REP_32477 Workflow task <workflow name> log file name is too long.
    •  REP_32479 Workflow task <workflow name> log directory name is too long.
    •  REP_32480 Workflow task <session name> log options is invalid.
    •  REP_32481 Workflow log option is invalid.
    •  REP_32482 Workflow task <workflow name>: ‘Save workflow log for these runs’ must be in the range of 0 to 2147483647.
    •  REP_32483 ‘Save workflow log for these runs’ must be in the range of 0 to 2147483647.
    •  REP_32490 Workflow task <workflow name> log directory name must have a delimiter.
    •  REP_32491 Log directory name must have a delimiter.
    •  REP_32494 The first character in a name cannot be a number.
    •  REP_32495 Spaces are not allowed in a name.
    •  REP_32496 The first character in a name cannot be <character>.
    •  REP_32497 The character <character> is not allowed in a name.
    •  REP_32498 Name length is too large.
    •  REP_32499 This is not a valid name.
    •  REP_32523 Session <session name> has different connection subtype across partitions.
    •  REP_32524 Session has different connection subtype across partitions.
    •  REP_32532 Missing required hash key for <transformation> in session <session name>.
    •  REP_32533 Missing required hash key for <transformation name>.
    •  REP_32534 Invalid hash key <key name> for <transformation name> in session <session name>.
    •  REP_32535 Invalid hash key <key name> for instance <transformation name>.
    •  REP_32536 Hash key <key name> for instance <transformation name> in session <session name> has invalid port type.
    •  REP_32537 Hash key <key name> for instance <transformation name> in session <session name> has invalid port type.
    •  REP_32542 Empty key range for <transformation name> in session <session name>.
    •  REP_32543 Missing required hash key for <transformation name>.
    •  REP_32544 Timer task <Timer task name> uses an empty workflow variable.
    •  REP_32546 Timer task <Timer task name> uses an invalid workflow variable.
    •  REP_32548 Timer task <Timer task name> uses a workflow variable which is not Date/Time datatype.
    •  REP_32550 Key not specified for key range partition for <partition name:transformation name> in session <session name>.
    •  REP_32551 Key not specified for key range partition for <partition name:transformation>.
    •  REP_32558 Workflow task <workflow name>: ‘Save workflow log for these runs’ has an invalid Integration Service variable associated with it.
    •  REP_32559 ‘Save workflow log for these runs’ has an invalid Integration Service variable associated with it.
    •  REP_32701 Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>, session <session name>).
    •  REP_32702 Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>).
    •  REP_32705 Key not specified for Key Range partition (group <group>, instance <transformation instance name>, session <session instance name>).
    •  REP_32706 Key not specified for Key Range partition (group <group> instance <transformation instance name>).
    •  REP_32827 Syntax error: bad variable name <variable name>.
    •  REP_32828 A variable with this name, <variable name>, already exists in the mapping.
    •  REP_32898 Warning: Failed to upgrade XML source <source>.
    •  REP_32899 Warning: Failed to upgrade XML target <target>.
    •  REP_51037 Database Connection Error: <error>.
    •  REP_51042 Repository Agent connection failed. System Error (errno = <error number>) <error message>: Cannot read message header. Read <number> bytes.
    •  REP_51048 Communication failed because of network errors. [System Error (errno = <error number>): <error message>.] Please try connecting to the repository again.
    •  REP_51054 Internal error: Cannot allocate buffer of size <size> bytes to receive incoming message. The system may be out of memory.
    •  REP_51056 Unable to read from client socket. Read <number> bytes.
    •  REP_51058 Unknown TCP/IP error. Please try connecting to the repository again.
    •  REP_51059 Repository Agent connection failed, another Repository Agent on host <host name> port <port number> is already connected to this repository <repository name>.
    •  REP_51071 Invalid name: You must specify a name.
    •  REP_51072 A metadata extension named <metadata extension name> already exists in the current domain.
    •  REP_51073 <Value> is not a valid integer value. Please enter an integer value between <minimum value> and <maximum value>.
    •  REP_51074 The value's length of <length> is higher than the maximum length of <maximum length>. Please enter a value with a length smaller or equal to that maximum.
    •  REP_51075 The maximum length is too large. Please specify a value smaller than or equal to <maximum length>.
    •  REP_51112 The reserved keyword <keyword> cannot be used.
    •  REP_51115 A table with the name <table name> already exists. Please enter a unique 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.
    •  REP_51120 The column <column> cannot allow nulls.
    •  REP_51134 The absolute value of the scale cannot be larger than the length/precision.
    •  REP_51135 The scale cannot be set less than -<number>.
    •  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.
    •  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>.
    •  REP_51292 Initialization property name cannot be empty.
    •  REP_51294 Initialization property <property> doesn’t exist.
    •  REP_51295 <property> is a built-in initialization property.
    •  REP_51296 The description of a built-in initialization property cannot be modified.
    •  REP_51297 Built-in initialization property cannot be deleted.
    •  REP_51298 Initialization property name cannot have more than 80 characters.
    •  REP_51300 Error: Inconsistent repository. Repository <repository name> does not have an Administrator user. Repository initialization failed.
    •  REP_51301 Unable to send messages to the Repository Service. Initialization of repository <repository name> failed.
    •  REP_51304 Partition number <number> is not valid.
    •  REP_51343 Unable to connect to the database server. Please check the connection to the database server.
    •  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.
    •  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.
    •  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.
    •  REP_51444 “MessageSendBufferSize” value <message send buffer size> is invalid, ignoring invalid value <message send buffer size>. Using system default value.
    •  REP_51445 “MessageReceiveBufferSize” value <message receive buffer size> is invalid, ignoring invalid value <message receive buffer size>. Using system default value.
    •  REP_51447 A repository request has timed out. [System Error (errno = <error number>): <system error message>]. Please try connecting to the repository again.
    •  REP_51502 The value <number of seconds> specified for Database Pool Expiry Timeout value is invalid. The Repository Service is using the default value <number>.
    •  REP_51503 The value <number of connections> specified for Database Pool Expiry Threshold value is invalid. The Repository Service is using the default value <number>.
    •  REP_51507 Target <target name> cannot have FileName field.
    •  REP_51508 Target <target name> has existing FileName field.
    •  REP_51509 Workflow task <workflow ID> maximum automatic recovery attempts must be in the range of 0 to 2147483647.
    •  REP_51510 Maximum automatic recovery attempts must be in the range of 0 to 2147483647.
    •  REP_51814 Repository connection failed.
    •  REP_51815 Failed to read the repository connection information.
    •  REP_51832 The license key for the repagent has expired.
    •  REP_51848 Cannot enable object versioning without a team-based development license key.
    •  REP_51849 The versioned repository cannot be enabled or restored without a team-based development license key.
    •  REP_51961 The value of the environment variable <environment variable name> needs to be encrypted with the latest version of pmpasswd.
    •  REP_55035 An error occurred during deployment.
    •  REP_55036 An error occurred during folder comparison.
    •  REP_55102 Failed to connect to Repository Service <service name>.
    •  REP_57060 Login failure.
    •  REP_57064 Maximum number of connections exceeded.
    •  REP_57071 Unable to connect to the repository database. Please check the Repository Agent configuration.
    •  REP_57084 Maximum number of concurrent locks exceeded.
    •  REP_57145 No data found in the database.
    •  REP_57151 Invalid function arguments.
    •  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.
    •  REP_57201 Internal Error: Repository object is inconsistent.
    •  REP_57269 This connection has been terminated.
    •  REP_58224 Failed to connect from <PowerCenter Client tool> to repository <repository name> because the repository users and groups have not been upgraded.
    •  REP_61002 WARNING: <XML definition> contained elements or attributes whose prefixes were removed.
    •  REP_61003 Empty key range for key <key name> (group <group>, instance <transformation instance name>, session <session instance name>).
    •  REP_61004 Empty key range for key <key name> (group <group> session <session name>).
    •  REP_61010 Failed to validate transformation field <field name>.
    •  REP_61011 Cannot have cycles in transformation fields.
    •  REP_61012 Error: Field <port name> of transformation <transformation name> could not be validated.
    •  REP_61013 Invalid group encountered while validating group order.
    •  REP_61014 Error: The groups of transformation <transformation name> could not be validated.
    •  REP_61027 Unable to set database connection property.
    •  REP_61031 Failed to upgrade <XML definition> because removal of prefixes generated an invalid XPATH.
    •  REP_61032 Failed to upgrade <XML source> because removal of prefixes caused element names to conflict!
    •  REP_61059 Warning: Failed to upgrade XML source <source>, version <version>, folder <folder>.
    •  REP_61060 Warning: Failed to upgrade XML target <target>, version <version>, folder <folder>.
    •  REP_61063 An error was encountered during the upgrade.
    •  REP_62340 Transformation <source or target instance name> uses connection variable <connection variable name>, but its value is not specified.
    •  REP_62373 Lookup Transformation <transformation name> has no associated Partial Pipeline. No single group Source Qualifier of name <Lookup table name>. Transformation is not valid.
    •  REP_62377 User name variable <variable name> is not well defined.
    •  REP_62378 Password variable <variable name> is not well defined.
    •  REP_62379 Connection name <parameter value> for connection variable <variable name> is not well defined.
    •  REP_62385 Advanced recovery cannot be enabled since the session has mapping variables.
    •  REP_62386 Advanced recovery cannot be enabled for session <session name> since the session has mapping variables.
  •  REP_CORE Messages
    •  REP_CORE_59046 The high availability license is absent for the Repository Service process <process name>.
  •  RFC Messages
    •  RFC_17403 Function return parameter is specified. However, only <value> out of <value> required values found when parsing the property value string.
    •  RFC_17405 Status or text field of return parameter must have ABAP type char in the source definition.
    •  RFC_17411 Output data conversion error for row number <row number> of table parameter <parameter>. This row will be skipped.
    •  RFC_17412 Output data conversion error for Scalar Output parameter. This row will be skipped.
    •  RFC_17416 Exception <exception> has been raised from the RFC function call with IntegrationID <Integration ID>.
    •  RFC_17422 Function Name <Function name> and Sequence ID <Sequence ID> do not match. One of them is incorrect.
    •  RFC_17423 Input for function <Function name> is received while expecting input for function <Function name>.
    •  RFC_17424 Call to function <Function name> corresponding to TransactionID = <Transaction ID>, IntegrationID = <Integration ID> failed. Cannot continue transaction.
    •  RFC_17425 Commit call failed for TransactionID <Transaction ID>.
    •  RFC_17427 Error when trying to create SAP internal table for function table parameter <Parameter name>.
    •  RFC_17439 The value of all connected input indicator ports is NULL. The source file may be invalid. See the session log to find the row with the error.
  •  RR Messages
    •  RR_4004 ERROR: Failed sanity check. No primary key in source tables.
    •  RR_4006 ERROR: Failed sanity check. No key in node.
    •  RR_4025 Error executing stored procedure.
    •  RR_4032 Warning: # of sorted ports <number of ports> must be less than # of projected fields <number of connected output ports>. Ignoring sort request.
    •  RR_4033 Error parsing stored procedure call text <call text>.
    •  RR_4034 Projected column metadata fetch failed.
    •  RR_4035 SQL error.
    •  RR_4036 Error connecting to database <database name>.
    •  RR_4038 Error setting stored procedures. Session-> m_pMapping corrupt.
    •  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.
    •  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.
    •  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.
    •  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.
  •  RS Messages
    •  RS_39037 Failed to start repository <repository name>.
    •  RS_39061 Cannot start repository <repository name> as it is being shut.
    •  RS_39068 Failed to register LDR <local repository name> to GDR <global repository name>.
    •  RS_39090 Cannot complete [Register] operation because of failure to start or connect to repository <repository_name>.
    •  RS_39091 Cannot complete [UnRegister] operation because of failure to start or connect to repository <repository_name>.
    •  RS_39092 Cannot promote repository <repository_name> to be a Global repository because of failure to start or connect to the repository.
    •  RS_39107 Cannot start repository <repository name> as it has been disabled.
    •  RS_39109 Cannot enable repository <repository name> as it is not disabled.
    •  RS_39120 ERROR: This product license does not allow global repositories. Only a PowerCenter license does that.
    •  RS_39121 ERROR: This product license does not allow registering or unregistering repositories. Only a PowerCenter license does that.
    •  RS_39141 ERROR: Invalid characters in repository name <repository name>.
    •  RS_39145 Failed to copy repository <repository name> to repository <target repository name>.
    •  RS_39209 Failed to complete a call to repository <repository name>.
•  S Message Codes
  •  SAPUTIL Messages
    •  SAPUTIL_99506 Invalid usage of help option.
    •  SAPUTIL_99057 The call to receive data failed with exception - <error message>.
    •  SAPUTIL_99072 The connection to SAP system failed. <error message>.
    •  SAPUTIL_99076 The context provided is invalid.
  •  SDKC Messages
    •  SDKC_37005 Global locale could not be found for this process.
    •  SDKC_37006 Invalid code page id <ID>.
    •  SDKC_37007 Failed to create locale.
    •  SDKC_37008 Could not load message catalog.
  •  SDKS Messages
    •  SDKS_38005 Couldn’t load the library <library> for plug-in #<ID>.
    •  SDKS_38006 Plug-in #<ID>’s interface version <version> is not compatible with SDK interface version <version>.
    •  SDKS_38007 Error occurred during <phase> <reader/writer> plug-in #<ID>.
    •  SDKS_38200 Partition-level [SQ_MSMQ_SOURCE]: Plug-in #310000 failed in init().
    •  SDKS_38505 Plug-in #<ID>’s target <target> indicated that the error threshold <number> has been reached.
    •  SDKS_38605 Plug-in #<ID>’s target <target> encountered a transient failure.
  •  SDKXML Messages
    •  SDKXML_43009 Plug-in level: CT failed in <function name>().
  •  SF Messages
    •  SF_31143 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.
    •  SF_31233 Could not set up cURL to connect to the Salesforce Bulk API. Using the standard Salesforce API.
    •  SF_31234 Bulk API error received from Salesforce. Exception code <code>. Exception message <message>.
    •  SF_31235 Bulk API cURL error received. Error message <message>.
    •  SF_31242 Bulk API job ID <job ID> failed.
    •  SF_31253 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.
    •  SF_31255 Salesforce could not process batch <batch ID> of job ID <job ID> because of the following error: <message>.
    •  SF_31259 ZLib compression returned the following error: <message>.
    •  SF_31324 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.
    •  SF_31426 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.
    •  SF_31523 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.
    •  SF_34030 Client application <application>, connection <connection ID>: recv failed. System returns error code <error number>, error message <error message>.
    •  SF_34032 Closing client application <application>’s connection dues to PROTOCOL ERROR. Please contact Informatica Global Customer Support.
    •  SF_34033 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.
    •  SF_34034 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.
    •  SF_34035 PROTOCOL ERROR: Got request ID <request ID> while expecting request ID <request ID> from client application <application> on connection <connection ID>.
    •  SF_34036 PROTOCOL ERROR: Got request key <key> while expecting request key <key> from client application <application> on connection <connection ID>.
    •  SF_34037 PROTOCOL ERROR: Got request type <request type> while in state <state> from client application <application> on connection <connection ID>.
    •  SF_34062 Cannot open service control manager.
    •  SF_34063 Cannot close service control manager.
    •  SF_34064 Cannot lock service database.
    •  SF_34065 Cannot unlock service database.
    •  SF_34066 Cannot open service.
    •  SF_34067 Cannot close service.
    •  SF_34068 Cannot query service.
    •  SF_34069 Cannot control service.
    •  SF_34070 Cannot stop service.
    •  SF_34071 Cannot delete service.
    •  SF_34072 Cannot create service.
    •  SF_34094 Caught a fatal signal. Will abort this server process shortly.
    •  SF_34095 Aborting this process due to a fatal signal.
    •  SF_34096 Caught SIGFPE signal. Aborting this server process.
    •  SF_34098 Failed to allocate memory. Out of virtual memory.
    •  SF_34105 Failed to redirect standard error (stderr) messages to the file <file name>. System error is <system error number> <system error message>.
    •  SF_34106 Failed to redirect standard output (stdout) messages to the file <file name>. System error is <system error number> <system error message>.
    •  SF_34109 Failed to open file <file name> for redirecting console output (stdout/stderr) messages System error is <system error number> <system error message>.
    •  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.
    •  SF_34130 Cannot get the storage files in directory <directory name>.
    •  SF_34132 Errors encountered while reading from storage files.
    •  SF_34134 Error in writing to storage file <file name>.
    •  SF_34135 Errors encountered while writing to storage files.
    •  SF_34136 Error in removing storage file <file name>.
    •  SF_34155 Child process <process ID> terminated due to spurious abort errno <error number>.
    •  SF_34160 High availability has been disabled. Contact Informatica Global Customer Support.
  •  SFDC Messages
    •  SFDC_31101 Login failed. User <login user name>. Fault code <error code>. Reason <error message>.
    •  SFDC_31102 Query failed. User <login user name>. SOSQL <SOSQL query>. Fault code <error code>. Reason <error message>.
    •  SFDC_31103 QueryMore failed. User <login user name>. SOSQL <SOSQL query>. Query Batch Index <query batch>. Fault code <error code>. Reason <error message>.
    •  SFDC_31105 Fields mis-matched. Expected field name <field name>. Returned field name <field name>.
    •  SFDC_31106 GetServerTimestamp failed. User <login user name>. Fault code <error code>. Reason <error message>.
    •  SFDC_31107 GetDeleted failed. User <login user name>. Start Time <time>. End Time <time>. Fault code <error code>. Reason <error message>.
    •  SFDC_31112 Invalid Flush Interval value <number of seconds>. It must be set to a positive integer value.
    •  SFDC_31113 Conversion Error Occurred. Field name <field name>. Data Value <field value before conversion>.
    •  SFDC_31114 Row Errors <number of row errors> exceeded session threshold <error threshold>.
    •  SFDC_31115 Source <source name> and Application Source Qualifier <Application Source Qualifier name> have different number of fields.
    •  SFDC_31116 Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same name.
    •  SFDC_31117 Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same field position.
    •  SFDC_31118 Source field <source field name> and Application Source Qualifier field <Application Source Qualifier field name> do not have the same datatype, precision, or scale.
    •  SFDC_31201 Login failed. User <login user name>. Fault code <error code>. Reason <error message>.
    •  SFDC_31202 Error received from salesforce.com. Fields <field names>. Status code <status code>. Message <error message>.
    •  SFDC_31203 A fault is received in a create request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
    •  SFDC_31204 A fault is received in an update request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
    •  SFDC_31205 A fault is received in a delete request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
    •  SFDC_31206 A fault is received in an upsert request. Fault code <error code>. Fault subcode <error subcode>. Reason <error message>. Detail <error detail>.
    •  SFDC_31207 Upsert is turned on but external ID is missing.
    •  SFDC_31208 An update or delete row is encountered, but the ID column is not connected.
  •  SM Messages
    •  SM_7024 Transformation Parse Fatal Error: Filter clause did not evaluate to a numeric value.
    •  SM_7027 Transformation evaluation error; current row skipped. trying to delete a non-existing 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.
    •  SM_7051 Aggregate error: index file timestamp is earlier than the timestamp of the Aggregator transformation or mapping.
    •  SM_7072 Aggregate Error: Expecting keys to be descending.
    •  SM_7073 Aggregate Error: Expecting keys to be ascending.
    •  SM_7087 Aggregate Error: code page <code page> and cached code page <code page> are not two-way compatible.
    •  SM_7088 Aggregate Error: sort order <sort order> and cached sort order <sort order> mismatch.
    •  SM_7089 Aggregate error: Unknown code page <code page> in the aggregation cache.
    •  SM_7091 Transformation Parse Fatal Error: Update Strategy Expression did not evaluate to a numeric value.
    •  SM_7096 Aggregate Error: Unable to execute cache upgrade utility <utility name>.
    •  SM_7099 Fatal Error: Header from incremental aggregation files for Aggregator transformation <transformation name> has invalid data.
    •  SM_7200 Error reading from incremental aggregation files for Aggregator transformation <transformation name>.
    •  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.
    •  SM_7203 Key length for transformation <transformation name> has changed.
    •  SM_7204 Row size for transformation <transformation name> has changed.
    •  SM_7207 Incremental aggregation upgrade error.
    •  SM_7208 Mapping has been modified since the incremental aggregation files for transformation <transformation name> were last saved.
    •  SM_7209 Cache for transformation <transformation name> was created in a precision mode different from the one specified by the session.
    •  SM_7210 Number of partitions has changed since cache creation.
    •  SM_7211 The Integration Service data movement mode differs from the data movement mode used when the cache was created.
    •  SM_7217 Error: Failed to expand update override <text> for target instance <target name>.
    •  SM_7218 Aggregate functions are allowed in Aggregator transformations only.
    •  SM_7219 Fatal error parsing the Lookup transformation. Verify that the update dynamic cache condition of the Lookup transformation <transformation name> evaluates to a numeric value.
  •  SORT Messages
    •  SORT_40046 Mmap <number of bytes> bytes of /dev/zero failed: <error message>. Either increase the swap space or decrease the Cache Size in the Transformation <transformation name>.
    •  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>.
    •  SORT_40095 File or filesystem <file or file system name> could not be accessed.
    •  SORT_40096 Temp file <file name> could not be opened: <error message>.
    •  SORT_40102 This sort requires at least <value> MB of memory.
    •  SORT_40111 This sort has been cancelled.
    •  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>.
    •  SORT_40189 The sort library could not create a thread.
    •  SORT_40304 This operation appears to need <value> MB of memory; excessive paging is possible; continuing.
    •  SORT_40401 A fatal Sort error has occurred in function <function name>. Errno = <error number>.
    •  SORT_40406 In transformation <transformation name>, an error has occurred <error message>.
    •  SORT_40407 In transformation <transformation name> in partition <partition number>, an error has occurred <error message>.
    •  SORT_40409 Internal sorter error <error>.
    •  SORT_40414 Error: Total row size <row size> in transformation <transformation name> is more than the allowed maximum [8 MB].
    •  SORT_40415 Work directory <directory name> does not exist.
    •  SORT_40416 Work directory <directory> does not have read/write/execute permission.
    •  SORT_40424 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.
  •  SPC Messages
    •  SPC_10027 Cannot start process for service <service name> on node <node name>. Process is shutting down. Try again later.
    •  SPC_10039 Could not start Informatica PowerCenter Web Services Hub service on port <port number> because this port is in use.
    •  SPC_10052 The domain failed to restart the service <service name> after trying for maximum <number of restart attempts> restart attempts.
  •  SQL Messages
    •  SQL_50001 IOutputBuffer::setRowType() API has failed.
    •  SQL_50002 NULL DB Handle returned.
    •  SQL_50003 ScriptName is empty.
    •  SQL_50004 SetProperty failed.
    •  SQL_50005 Logical Connection Object Name is empty.
    •  SQL_50006 FlushOutRow failed.
    •  SQL_50007 ODL Error has occurred. Please see the pre-defined error port for detailed error message.
    •  SQL_50008 Number of columns in the select query is greater than the number of output ports in the SQL transformation.
    •  SQL_50009 Static Connection information is inappropriate to create a valid database handle.
    •  SQL_50010 Error: File handle could not be created.
    •  SQL_50011 The SQL Query entered through the Designer is empty.
    •  SQL_50013 Setting the data in target failed.
    •  SQL_50014 Getting the data from source failed.
    •  SQL_50015 Failed to connect to the database.
    •  SQL_50017 Failed to get the relational connection name attribute from repository.
    •  SQL_50018 Failed to get the connections.
    •  SQL_50070 Error threshold reached.
    •  SQL_50071 Session failed because a connection failure occurred after the SQL transformation passed some of the output rows downstream.
    •  SQL_50072 An error occurred expanding a parameter or variable in the environment SQL <connection or transaction environment SQL> for the connection object <connection name>.
  •  SR Messages
    •  SR_17000 Projected column metadata fetch failed.
    •  SR_17001 Maximum column length is zero.
    •  SR_17004 ERROR: Connect failed. SAP driver has not been loaded.
    •  SR_17005 ERROR: Connect failed: SAP error message <SAP message>.
    •  SR_17006 Unknown data transfer mode. The mode can only be staging or streaming.
    •  SR_17007 ERROR: Run failed: SAP error message <ABAP program name or staging file name or Application Source Qualifier form name> SAP <error message>.
    •  SR_17009 Error in CPIC: <error message>.
    •  SR_17010 Error in parsing filter expression: <expression>.
    •  SR_17011 Error in passing parameters to SAP system: <SAP message>.
    •  SR_17012 Could not start program in Background mode: <SAP message>.
    •  SR_17013 Could not get status information for a Background job: <SAP message>.
    •  SR_17014 ERROR: File open failed.
    •  SR_17015 Could not delete the Staging File <file name>: <SAP message>.
    •  SR_17016 The program <program name> was generated but not installed for mapping <mapping name> version <version number>.
    •  SR_17020 Memory allocation for tree <tree name> failed.
    •  SR_17021 ERROR in getting information for SetId <SetID name> and Table Name <table name>.
    •  SR_17022 No hierarchy data found for <hierarchy name>.
    •  SR_17023 Tree is inconsistent.
    •  SR_17024 Error in passing parameters to SAP system for hierarchy with SetID <setid name> and TableName <table name>.
    •  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>.
    •  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.
    •  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.
    •  SR_17056 Warning from SAP Connect:
    •  SR_17057 Unable to retrieve code page information for code page ID <code page ID>.
    •  SR_17058 Unable to create a locale from code page <code page> <code page ID>.
    •  SR_17059 SAP Code page: <code page ID> is not compatible with the user selected code page <code page>.
    •  SR_17085 SAP Extraction Version could not be verified.
    •  SR_17061 Last error encountered is:
    •  SR_17062 Error in RFC program.
    •  SR_17063 Error in network communications.
    •  SR_17064 SAP logon error.
    •  SR_17065 SAP system exception raised.
    •  SR_17067 RFC protocol error.
    •  SR_17068 RFC internal error.
    •  SR_17069 RFC registered server was cancelled.
    •  SR_17073 No program was generated as mapping contains only SAP Information Hierarchies.
    •  SR_17090 The Application Source Qualifier <Application Source Qualifier name> has invalid user defined query <query> with character error at <number> location.
    •  SR_17091 The Application Source Qualifier <Application Source Qualifier name> has invalid filter clause <filter> with character error at <number> location.
    •  SR_17092 The Application Source Qualifier <Application Source Qualifier name> has invalid join and/or filter override <join override> with character error at <number> location.
    •  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.
    •  SR_17156 Error: The filter expression is missing a source or a list of sources or a source field for which this expression is specified.
    •  SR_17157 Error: Only <word> is a valid reserved word.
    •  SR_17158 Error: Multiple field level filters not allowed.
    •  SR_17159 Error: A table level filter is not allowed with a field level filter.
    •  SR_17163 Current server data movement mode is <mode> and SAP system mode is <mode>. To extract data from Unicode enabled SAP system, server must be run in <mode> mode.
    •  SR_17171 The Integration Service could not open the SFTP connection.
•  T Message Codes
  •  TE Messages
    •  TE_7102 Initialization error. Failed to get the last saved time for mapping <mapping name>.
    •  TE_7104 An error occurred while creating group <group number> of target <target name>.
    •  TE_7105 An error occurred while creating transformation <transformation name>.
    •  TE_7106 Failed to allocate or initialize the group ID <group ID> for target <target name>.
    •  TE_7112 Message recovery with non-repeatable source does not allow XML targets in the mapping.
    •  TE_7117 A real-time session cannot have non-realtime SDK targets in the mapping.
    •  TE_7122 The session is configured for user-defined commit, but the target <target name> is not receiving transactions from any upstream transformation.
    •  TE_7127 You cannot perform a user-defined commit for a real-time session.
    •  TE_7131 The transformation <transformation> is not configured to propagate transactions. The session cannot run in real time.
    •  TE_7133 The master input for the unsorted Joiner transformation <transformation name> cannot be partitioned because the Joiner transformation is not a partition point.
    •  TE_7134 Warning. The master input for the sorted Joiner transformation <transformation name> is partitioned.
    •  TE_7135 You cannot recover a session when the target load group has multiple sources, and at least one source is a real-time source. The source names are <source names>.
  •  TIB Messages
    •  TIB_34001 Cannot get connection property <connection property>.
    •  TIB_34002 Invalid subject <subject>.
    •  TIB_34003 Cannot get source property <source property>.
    •  TIB_34004 Invalid queue limit policy <queue limit policy>.
    •  TIB_34010 Cannot get target property <property>.
    •  TIB_34015 Invalid cmName <cmName>.
    •  TIB_34021 Invalid field map <field map value>.
    •  TIB_34022 Failed to confirm certified message: <TIBCO error message>.
    •  TIB_34025 Incompatible datatype for field <field name>.
    •  TIB_34026 Data overflow happened when trying to insert value <value> into field of type <datatype>.
    •  TIB_34027 Invalid date.
    •  TIB_34028 Data overflow.
    •  TIB_34029 Invalid value or data overflow.
    •  TIB_34030 Data overflow happened when trying to insert value <value> into field of type <type>.
    •  TIB_34031 Datatype of <datatype> is expected to be msg for field <field>.
    •  TIB_34032 Extracting data for field <field> failed: <TIBCO error message>.
    •  TIB_34033 Data conversion failed for field <field>: <TIBCO error message>.
    •  TIB_34034 Failed to add a field <field> to a message: <TIBCO error message>.
    •  TIB_34035 Failed to pre-register listener <listener name>: <TIBCO error message>.
    •  TIB_34036 Tibrv driver failed to set subject name <subject name> for current message: <TIBCO error message>.
    •  TIB_34037 Tibrv driver failed to send the current message: <TIBCO error message>.
    •  TIB_34038 Failed to load library <library name>.
    •  TIB_35001 TIBCO reader cannot get connection reference for the source qualifier instance <Source Qualifier name>.
    •  TIB_35002 TIBCO reader cannot get connection for the source qualifier instance <Source Qualifier name>.
    •  TIB_35003 TIBCO reader failed to initialize connection properties for the source qualifier instance <Source Qualifier name>.
    •  TIB_35004 TIBCO reader failed to initialize reader properties for the source qualifier instance <Source Qualifier name>.
    •  TIB_35005 TIBCO reader failed to initialize TIBCO driver for the source qualifier instance <Source Qualifier name>.
    •  TIB_35006 TIBCO reader failed to initialize TIBCO source for the source qualifier instance <Source Qualifier name>.
    •  TIB_35008 Reader partition <partition> failed to get cache coordinator for recovery.
    •  TIB_35009 Cache folder attribute cannot be fetched for reader partition <partition>.
    •  TIB_35010 Cache folder specified for reader partition <partition> is invalid.
    •  TIB_35011 Reader partition <partition> failed to register for recovery.
    •  TIB_35014 Reader partition <partition> failed to cache message.
    •  TIB_35015 Reader partition <partition> truncated last cached message from cache.
    •  TIB_35016 Reader partition <partition> failed to truncate message cache to last serialized message: <error message>.
    •  TIB_35017 Reader partition <partition> failed to flush the cache: <error message>.
    •  TIB_35018 Data dispatch failed with the current message <error message>.
    •  TIB_35020 The number of row errors has reached the threshold: <number>.
    •  TIB_35021 TIBCO reader failed to connect to TIBCO.
    •  TIB_35022 Reader partition <partition> failed to close checkpoint at EOF: <error message>.
    •  TIB_35024 Fatal error occurred while fetching TIBCO messages.
    •  TIB_35025 Reader partition <partition> failed to close checkpoint at real-time flush point: <error message>.
    •  TIB_35026 Reader buffer flush failed.
    •  TIB_35027 Reader partition <partition> failed to unregister for recovery.
    •  TIB_35028 Real-time feature is not enabled for the source qualifier instance <Source Qualifier name>.
    •  TIB_35030 TIBCO reader cannot get source property <property> for the source qualifier instance <Source Qualifier name>.
    •  TIB_35031 TIBCO reader cannot get the source qualifier instances from the mapping.
    •  TIB_35033 TIBCO reader failed to support recovery for the source qualifier instance <Source Qualifier name>.
    •  TIB_35037 Reader partition <partition> failed to read cached message.
    •  TIB_35039 The source qualifier instance <Source Qualifier name> contains the datatype msg, which is incompatible with a TIB/Adapter SDK connection.
    •  TIB_35040 The source qualifier instance <Source Qualifier name> contains the header field Time Limit, which is incompatible with a TIB/Adapter SDK connection.
    •  TIB_36001 Tibrv driver failed to connect to TIB/Rendezvous.
    •  TIB_36002 TIBCO driver failed to set default time limit for Certified Message Delivery: <TIBCO error message>.
    •  TIB_36004 Tibrv driver failed to create sending interval device.
    •  TIB_36005 Tibrv driver failed to create message queue: <TIBCO error message>.
    •  TIB_36006 Tibrv driver failed to create a listener for receiving messages: <TIBCO error message>.
    •  TIB_36009 Tibrv driver failed to set reply subject name <reply subject name> for the current message: <TIBCO error message>.
    •  TIB_36010 Tibrv driver failed to set a time limit for the current message: <TIBCO error message>.
    •  TIB_36013 Tibrv driver failed to open TIB/Rendezvous environment: <TIBCO error message>.
    •  TIB_36014 Tibrv driver failed to create a TIB/Rendezvous transport: <TIBCO error message>.
    •  TIB_36015 Tibrv driver failed to initialize the listener for advisory messages.
    •  TIB_36016 Tibrv driver failed to set limit policy for message queue: <TIBCO error message>.
    •  TIB_36017 Tibrv driver failed to create message queue for advisory messages: <TIBCO error message>.
    •  TIB_36018 Tibrv driver failed to create a listener for advisory messages: <TIBCO error message>.
    •  TIB_36019 Tibrv driver failed to create a thread to dispatch advisory messages: <TIBCO error message>.
    •  TIB_36020 System is out of memory.
    •  TIB_36021 TIB/Rendezvous license will expire or has already expired on <date>.
    •  TIB_36022 Tibrv driver failed to get confirmation for the message with sequence number <number>.
    •  TIB_36023 CmName conflicts: <TIBCO error message>.
    •  TIB_36036 Tibrv driver failed to get message sequence number: <TIBCO error messages>.
    •  TIB_36037 Tibrv driver failed to serialize cache message: <error message>.
    •  TIB_36038 Tibrv driver failed to deserialize cache message: <error message>.
    •  TIB_36039 Tibrv driver tried to allocate <number> bytes memory but failed.
    •  TIB_36040 Tibrv driver failed to create a new message object.
    •  TIB_36057 Failed to create a message for field <field>: <TIBCO error message>.
    •  TIB_36058 Failed to get the number of fields in a TIB/Rendezvous message: <TIBCO error message>.
    •  TIB_37001 Tibsdk driver failed to connect.
    •  TIB_37006 Tibsdk driver failed to create the publisher: <TIBCO error message>.
    •  TIB_37007 Tibsdk driver failed to create the subscriber: <TIBCO error message>.
    •  TIB_37008 Tibsdk driver failed to add the listener to the subscriber: <TIBCO error message>.
    •  TIB_37009 Tibsdk driver failed to dispatch an event: <TIBCO error message>.
    •  TIB_37011 Tibsdk driver failed to start adapter instance <adapter instance>: <TIBCO error message>.
    •  TIB_37012 Tibsdk driver failed to pre-register a listener <pre-registered listener>: <TIBCO error message>.
    •  TIB_37023 Tibsdk driver failed to process advisory messages: <TIBCO error message>.
    •  TIB_37024 Session <session> is invalid or does not exist. It must be an RV session.
    •  TIB_37025 An exception occurred when Tibsdk driver initialized for advisory messages: <TIBCO error message>.
    •  TIB_37026 Tibsdk driver failed to cache a message: <error message>.
    •  TIB_37027 Tibsdk driver failed to read a cached message: <error message>.
    •  TIB_37028 Invalid session communication protocol. Must be either RV or RVCM.
    •  TIB_38000 TIBCO writer failed to insert null value into field <field>, which can't take a null value.
    •  TIB_38001 TIBCO writer failed to initialize writer properties for the target instance <target>: <error message>.
    •  TIB_38002 TIBCO writer failed to initialize connection properties for the target instance <target>: <error message>.
    •  TIB_38003 TIBCO writer can't get connection information for the target instance <target>.
    •  TIB_38004 TIBCO writer initialization failed for the target instance <target>: <error message>.
    •  TIB_38007 TIBCO writer rejected the row because of the overflow error for field <field>.
    •  TIB_38008 Data was truncated for field <field>.
    •  TIB_38009 TIBCO writer failed to get error threshold value.
    •  TIB_38010 SendSubject field cannot be connected when pre-registered listeners are specified for the writer.
    •  TIB_38012 The target instance contains the datatype msg, which is incompatible with a TIB/Adapter SDK connection.
    •  TIB_38013 Target instance contains the header field Time Limit, which is incompatible with a TIB/Adapter SDK connection.
    •  TIB_38014 Target instance contains the datatype ipaddr32 or ipport16, which is incompatible with a TIB/Adapter SDK connection.
  •  TM Messages
    •  TM_6004 There was an error connecting to the repository.
    •  TM_6018 The session completed with <number> row transformation errors.
    •  TM_6059 An error occurred updating the Sequence Generator transformation <transformation name> to the repository.
    •  TM_6063 An error occurred updating repository tables.
    •  TM_6075 An error occurred an error opening the file.
    •  TM_6085 A fatal transformation error occurred, and the session is terminating.
    •  TM_6094 Error creating buffer pool.
    •  TM_6109 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.
    •  TM_6154 An error occurred setting session sort order: <sort order>.
    •  TM_6157 An error occurred parsing stored procedure call text <stored procedure>.
    •  TM_6159 An error occurred executing stored procedure.
    •  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.
    •  TM_6188 The session sort order <sort order name> is incompatible with the Integration Service code page <code page name>.
    •  TM_6190 Cannot identify the unique relational connection or application connection that is used as $Source or $Target for a Lookup or Stored Procedure transformation.
    •  TM_6193 An error occurred expanding the connection parameter <parameter name>.
    •  TM_6200 The session log path exceeds limits of <session log path limit> characters <session log path>.
    •  TM_6202 DTM event. There was an error incrementing the log file number in the repository.
    •  TM_6223 An internal error occurred while fetching the session log. The log attached to the post session email may be incomplete.
    •  TM_6247 An error occurred checking global object permissions: <object>.
    •  TM_6248 User <user name> does not have execute permission on the global object <object name>.
    •  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>.
    •  TM_6255 An error was encountered saving statistical information to the repository for the transformation <transformation name> with partition ID <partition ID>.
    •  TM_6264 The connection is not set in the Workflow Manager for the MQ Source Qualifier transformation <MQ Source Qualifier name> partition <partition number>.
    •  TM_6279 The session instance <session instance name> encountered the following run-time validation error: <error message>.
    •  TM_6288 Failed to allocate memory. Out of virtual memory.
    •  TM_6289 Aborting the DTM process due to memory allocation failure.
    •  TM_6294 The target load order has been changed. Revalidate the mapping <mapping name>.
    •  TM_6316 Error: <database error message> setting up <table name> table.
    •  TM_6317 The following database error occurred creating the recovery table <table name>: <database error message>.
    •  TM_6318 The following database error occurred when preparing to fetch the target run ID from the recovery table <table name>: <database error message>.
    •  TM_6319 The following database error occurred when fetching the target run ID from the recovery table <table name>: <database error message>.
    •  TM_6320 The following database error occurred when inserting the target run ID into the recovery table <table name>:<database error message>.
    •  TM_6321 The recovery table format is in version <version number>, while version 6.2 is expected.
    •  TM_6322 The following error occurred when generating a sequence ID: <database error message>.
    •  TM_6323 The following database error occurred when committing the new sequence ID to the database: <database error message>.
    •  TM_6324 The following database error occurred when preparing the UPDATE recovery statement: <database error message>.
    •  TM_6325 The following database error occurred when updating recovery information for the recovery table <table name>: <database error>.
    •  TM_6326 The following database error occurred when deleting recovery information from the recovery table <table name>: <database error message>.
    •  TM_6327 The following database error occurred when resetting recovery information for the recovery table <table name>: <database error message>.
    •  TM_6328 The following database error occurred when fetching the partition count from the recovery table <table name>: <database error message>.
    •  TM_6329 The following database error occurred when fetching recovery information from the recovery table <table name>: <database error message>.
    •  TM_6330 An error occurred retrieving recovery information from the target database.
    •  TM_6331 An error occurred initializing recovery for target <target table>.
    •  TM_6332 An error occurred deleting information from the recovery tables for the target <target>.
    •  TM_6336 An error occurred initializing the recovery session because the recovery information for the target <target> was not found.
    •  TM_6341 A database error occurred updating the recovery tables. The session updated <number of records> recovery records but expected to update one row.
    •  TM_6342 An error occurred updating information in the recovery tables for the target <target name>.
    •  TM_6343 Session recovery is not possible because the session is not enabled for recovery.
    •  TM_6345 The connection object <connection name> is not a valid database partition connection type.
    •  TM_6349 Session recovery is not possible because the session is also configured to perform a test load.
    •  TM_6376 The Integration Service failed while processing the recovery file.
    •  TM_6687 The DTM buffer size specified <DTM buffer size> exceeds the 32-bit address space. It cannot be more than <number> on a 32-bit Integration Service.
    •  TM_6698 An error was encountered loading library: <reason for failure>.
    •  TM_6700 The following error was encountered accessing the file <file name> for error logging: <error message>.
    •  TM_6701 Warning. The flat file delimiter <delimiter> is the same as the data column delimiter for error logging. You may find it difficult to read the error log.
    •  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.
    •  TM_6713 Concurrent sources with the same transactional requirements must have consecutive execution order.
    •  TM_6765 The Debugger cannot run a session on a grid.
    •  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.
    •  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>.
    •  TM_6777 Temporary profiling sessions cannot be grid-enabled.
    •  TM_6788 Error: Unable to open temporary log file <log file name> with error <error code>. The session log will not be attached to post-session email.
    •  TM_6795 The Repository Service marked the session as impacted, and the Integration Service is not configured to run impacted sessions.
    •  TM_6796 An error occurred expanding the owner name <owner name> for the transformation <transformation name>.
    •  TM_6797 An error occurred expanding a parameter or variable in the environment SQL <SQL text> for the connection object <connection name>.
    •  TM_6798 An error occurred expanding a parameter or variable in the table name prefix <prefix> for error logs.
    •  TM_6828 An error was encountered while saving statistical information to the repository.
    •  TM_6829 The Integration Service encountered the following error while resetting recovery table <table name>: Error <Error>.
    •  TM_6844 The variable <variable name> used in pre-session variable assignment is overridden in the parameter file. The variable assignment will be ignored.
    •  TM_6845 The parent workflow or worklet variable <variable name> listed in a pre-session variable assignment statement cannot be found. The variable assignment will be ignored.
    •  TM_6848 Unable to resolve variable <variable name> as a user-defined workflow or worklet variable.
    •  TM_6849 Unable to resolve variable <variable name> as a mapping parameter, mapping variable, session parameter or predefined variable.
    •  TM_6850 An error was encountered setting the value from variable <variable name> to value for variable <variable name>.
    •  TM_6851 An error was encountered performing the post-session variable assignment.
    •  TM_6956 An error was encountered starting a new workflow instance because the number of workflow instances is at the configured limit.
    •  TM_6957 The workflow failed because it persists the same mapping variables as another workflow instance that is running concurrently.
    •  TM_6958 The workflow failed to start because a workflow with the same instance name is already running.
  •  TPTRD Messages
    •  TPTRD_11001 Plug-in failed to create the TPTLogging class object.
    •  TPTRD_11002 Plug-in failed to convert Code Page to Unicode.
    •  TPTRD_11003 Plug-in failed to convert Unicode to Code Page.
    •  TPTRD_21101 Plug-in failed to retrieve Trace level from session.
    •  TPTRD_21201 Plug-in failed to set ILog logger.
    •  TPTRD_21202 Plug-in failed to set TPTLogging logger.
    •  TPTRD_21203 Plug-in failed to set TDPID.
    •  TPTRD_21204 Plug-in failed to set User Name.
    •  TPTRD_21205 Plug-in failed to set Password.
    •  TPTRD_21206 Plug-in failed to set Working Database.
    •  TPTRD_21207 Plug-in failed to set Table Name.
    •  TPTRD_21208 Plug-in failed to set DML Statement.
    •  TPTRD_21209 Plug-in failed to create Teradata database connection object.
    •  TPTRD_21210 Plug-in failed to create Schema for Table <table name>.
    •  TPTRD_21211 Plug-in failed to Initiate Teradata database connection.
    •  TPTRD_21212 Plug-in failed to allocate memory to Connection object.
    •  TPTRD_21213 Plug-in failed to allocate memory to Schema object.
    •  TPTRD_21214 No Fields defined to read data from.
    •  TPTRD_21215 Plug-in failed to fetch data on row <row number> with status <status code>.
    •  TPTRD_21216 Plug-in failed to retrieve DSQ C-datatype.
    •  TPTRD_21217 Plug-in failed to flush all rows.
    •  TPTRD_21218 Error occurred during Export...
    •  TPTRD_21219 Unknown Error in TPTReaderPartition::run()
    •  TPTRD_21220 Invalid TDPID.
    •  TPTRD_21301 Plug-in failed to initialize Teradata PT Reader component.
    •  TPTRD_21302 Plug-in failed to retrieve Source Qualifier metadata object.
    •  TPTRD_21501 Plug-in failed to initialize Teradata PT Reader Partition Driver.
    •  TPTRD_21502 Plug-in failed to retrieve Teradata Parallel Transporter connection information.
    •  TPTRD_21503 Plug-in failed to retrieve Session-level information.
    •  TPTRD_21504 Plug-in failed to retrieve Metadata Extension information.
    •  TPTRD_21505 Plug-in failed to retrieve Source Qualifier and its field information.
    •  TPTRD_21506 Plug-in failed to build DML statement.
    •  TPTRD_21507 Plug-in failed to create TPTAPI class instance.
    •  TPTRD_21508 Plug-in failed to create connection to Teradata database.
    •  TPTRD_21509 Plug-in failed to read data from table <table name> of Teradata database.
    •  TPTRD_21510 Plug-in failed to validate Session level DML statement <DML_statement>.
    •  TPTRD_21511 Plug-in failed to validate Metadata Extension level DML statement <DML statement>.
    •  TPTRD_21512 Plug-in failed to build Default DML statement.
    •  TPTRD_21513 Multiple groups <group_ count> not supported.
    •  TPTRD_21514 Plug-in failed to retrieve Source Qualifier field list.
    •  TPTRD_21515 Plug-in failed to retrieve C-datatype of field <field name>.
    •  TPTRD_21516 Plug-in failed to retrieve datatype of field <field name>.
    •  TPTRD_21517 Plug-in failed to retrieve source extension attached with particular source qualifier.
    •  TPTRD_21518 Plug-in failed to retrieve connection reference associated with particular partition.
    •  TPTRD_21519 Plug-in failed to retrieve connection object associated with a connection reference.
    •  TPTRD_21520 Plug-in failed to retrieve TDPID.
    •  TPTRD_21521 Plug-in failed to retrieve Database Name.
    •  TPTRD_21522 Plug-in failed to retrieve Tenacity.
    •  TPTRD_21523 Plug-in failed to retrieve Max Sessions.
    •  TPTRD_21524 Plug-in failed to retrieve Sleep.
    •  TPTRD_21525 Plug-in failed to retrieve Block Size.
    •  TPTRD_21526 Plug-in failed to retrieve Encrypt Data flag.
    •  TPTRD_21527 Invalid Sql Query.
    •  TPTRD_21528 Plug-in failed to get the list of sources in the mapping.
    •  TPTRD_21529 Number of Max Sessions must be greater than 0.
    •  TPTRD_21530 Sleep must be greater than 0.
    •  TPTRD_21531 Tenacity must be greater than or equal to 0.
    •  TPTRD_21532 The minimum 256 bytes and maximum 64000 bytes Block Size is required.
    •  TPTRD_21533 No of sorted Ports more than the No of Output fields.
    •  TPTRD_35061 The following system error occurred when the PowerCenter Integration Service tried to get the values of some session attributes: <error message>.
  •  TPTWR Messages
    •  TPTWR_11001 Plug-in failed to create the TPTLogging class object.
    •  TPTWR_11002 Plug-in failed to convert Code Page to Unicode.
    •  TPTWR_11003 Plug-in failed to convert Unicode to Code Page.
    •  TPTWR_31101 Plug-in failed to retrieve Trace level from session.
    •  TPTWR_31201 Plug-in failed to set ILog logger.
    •  TPTWR_31202 Plug-in failed to set TPTLogging logger.
    •  TPTWR_31203 Plug-in failed to set System Operator.
    •  TPTWR_31204 Plug-in failed to set TDPID.
    •  TPTWR_31205 Plug-in failed to set User Name.
    •  TPTWR_31206 Plug-in failed to set Password.
    •  TPTWR_31207 Plug-in failed to set Working Database.
    •  TPTWR_31208 Plug-in failed to set Table Name.
    •  TPTWR_31209 Plug-in failed to set Error Database Name.
    •  TPTWR_31210 Plug-in failed to set Error Table 1 Name.
    •  TPTWR_31211 Plug-in failed to set Error Table 2 Name.
    •  TPTWR_31212 Plug-in failed to set Log Database Name.
    •  TPTWR_31213 Plug-in failed to set Log Table Name.
    •  TPTWR_31214 Plug-in failed to set Insert DML Statement.
    •  TPTWR_31215 Plug-in failed to set Update DML Statement.
    •  TPTWR_31216 Plug-in failed to set Delete DML Statement.
    •  TPTWR_31217 Plug-in failed to set Truncate Table DML Statement.
    •  TPTWR_31218 Plug-in failed to create Teradata database connection object.
    •  TPTWR_31219 Plug-in failed to create Schema for Table <table_name>.
    •  TPTWR_31220 Plug-in failed to create DML Group <DML group name>.
    •  TPTWR_31221 Plug-in failed to Initiate Teradata database connection.
    •  TPTWR_31222 Plug-in failed to allocate memory to Connection object.
    •  TPTWR_31223 Plug-in failed to allocate memory to Schema object.
    •  TPTWR_31224 Plug-in failed to allocate memory to DML Group <DML group name>.
    •  TPTWR_31225 Plug-in failed to commit the Connection object.
    •  TPTWR_31226 Plug-in failed in End Acquisition.
    •  TPTWR_31227 Plug-in failed to Apply rows.
    •  TPTWR_31228 Plug-in failed to set DML Group <DML group name> to connection object.
    •  TPTWR_31229 Plug-in failed to put row in Teradata database.
    •  TPTWR_31230 Plug-in failed to put buffer in Teradata database.
    •  TPTWR_31231 Plug-in failed to retrieve buffer layout for PutBuffer method.
    •  TPTWR_31232 Plug-in failed to retrieve affected rows.
    •  TPTWR_31233 Truncate Table: Plug-in failed to create Teradata database connection object.
    •  TPTWR_31234 Truncate Table: Plug-in failed to create Schema for Table <table_name>.
    •  TPTWR_31235 Truncate Table: Plug-in failed to create DML Group <DML_Group_name>.
    •  TPTWR_31236 Truncate Table: Plug-in failed to Initiate Teradata database connection.
    •  TPTWR_31237 Plug-in failed to set Update Recovery_Table DML Statement.
    •  TPTWR_31238 Plug-in failed to set Insert Recovery_Table DML Statement.
    •  TPTWR_31239 Plug-in failed to set Delete Recovery_Table DML Statement.
    •  TPTWR_31240 Unable to support multiple group.
    •  TPTWR_31301 Plug-in failed to initialize Teradata PT Writer Plug-in.
    •  TPTWR_31302 Plug-in failed to create Target Drivers.
    •  TPTWR_31303 Plug-in failed to retrieve Target Instance.
    •  TPTWR_31304 Invalid Target Index <target_index>.
    •  TPTWR_31401 Plug-in failed to initialize Teradata PT Writer Target Driver.
    •  TPTWR_31402 Plug-in failed to create Group Drivers.
    •  TPTWR_31403 Plug-in failed to retrieve Group list.
    •  TPTWR_31404 Invalid Group Index <group index>.
    •  TPTWR_31501 Plug-in failed to initialize Teradata PT Writer Group Driver.
    •  TPTWR_31502 Plug-in failed to create Partition Drivers.
    •  TPTWR_31503 Invalid Partition Index <partition_index>.
    •  TPTWR_31601 Plug-in failed to initialize Teradata PT Writer Partition Driver.
    •  TPTWR_31602 Plug-in failed to retrieve Row statistics information.
    •  TPTWR_31603 Plug-in failed to retrieve Teradata Parallel Transporter connection and session level attributes.
    •  TPTWR_31604 Plug-in failed to retrieve table information.
    •  TPTWR_31605 Plug-in failed to build DML statements on table <table name> for system operator <system operator name>.
    •  TPTWR_31606 Plug-in failed to build Truncate Table DML statement.
    •  TPTWR_31607 Plug-in failed to build INSERT DML statement.
    •  TPTWR_31608 Plug-in failed to build UPDATE DML statement.
    •  TPTWR_31609 Plug-in failed to build DELETE DML statement.
    •  TPTWR_31610 Primary Key is not defined for any of the fields of table <table_name>. Cannot build DELETE DML Statement.
    •  TPTWR_31611 Primary key is defined for all fields of table <table_name>. Cannot build UPDATE DML Statement.
    •  TPTWR_31612 Primary Key is not defined for any of the fields of table <table_name>. Cannot build UPDATE DML Statement.
    •  TPTWR_31613 Plug-in failed to retrieve Truncate Table attribute.
    •  TPTWR_31614 Plug-in failed to retrieve Update Else Insert attribute.
    •  TPTWR_31615 Plug-in failed to retrieve connection reference associated with particular partition...
    •  TPTWR_31616 Plug-in failed to retrieve connection object associated with a connection reference...
    •  TPTWR_31617 Plug-in failed to retrieve Working Database.
    •  TPTWR_31618 Plug-in failed to retrieve TDPID.
    •  TPTWR_31619 Plug-in failed to Retrieve System Operator.
    •  TPTWR_31620 Plug-in failed to retrieve Log Table Name.
    •  TPTWR_31621 Plug-in failed to retrieve Log Database Name.
    •  TPTWR_31622 Plug-in failed to retrieve Error Database Name.
    •  TPTWR_31623 Plug-in failed to retrieve Error Table 1 Name.
    •  TPTWR_31624 Plug-in failed to retrieve Error Table 2 Name.
    •  TPTWR_31625 Plug-in failed to retrieve Max Sessions.
    •  TPTWR_31626 Plug-in failed to retrieve Tenacity.
    •  TPTWR_31627 Plug-in failed to retrieve Sleep.
    •  TPTWR_31628 Plug-in failed to retrieve Base Address for each field.
    •  TPTWR_31629 Plug-in failed to retrieve commit Teradata database connection object.
    •  TPTWR_31630 Plug-in failed while Data Manipulation.
    •  TPTWR_31631 Plug-in failed to allocate Memory.
    •  TPTWR_31632 Plug-in failed to retrieve data indicator.
    •  TPTWR_31633 Update Operation is not allowed for LOAD system operator.
    •  TPTWR_31634 Delete Operation is not allowed for LOAD system operator.
    •  TPTWR_31635 Plug-in failed to truncate table.
    •  TPTWR_31636 Number of Max Sessions must be greater than 0.
    •  TPTWR_31637 Sleep must be greater than 0.
    •  TPTWR_31638 TENACITY must be greater than or equal to 0.
    •  TPTWR_31639 Block size must be greater than 0.
    •  TPTWR_31640 Failed to register TPTRecStorageFactory, recovery will not be supported.
    •  TPTWR_31641 Failed to initiate TPTRecStorageFactory, recovery will not be supported.
    •  TPTWR_31642 Failed to initiate TPTConnectionManager.
    •  TPTWR_34701 Failed to initialize TPTWriterConnection.
    •  TPTWR_34702 Failed to deinitialize TPTConnectionManager.
    •  TPTWR_34703 Failed to commit for target <name> and partition <number>.
    •  TPTWR_34704 Rollback is not supported for Teradata Parallel Transporter writer.
    •  TPTWR_34723 Initialization of TPT connection for reading recovery information failed.
    •  TPTWR_34725 Termination of TPT connection for reading recovery information failed.
    •  TPTWR_34727 Initialization of TPT connection for deleting recovery information failed.
    •  TPTWR_34729 Termination of TPT connection for deleting recovery information failed.
    •  TPTWR_34730 Selection of DML statement failed in connection for deleting recovery information.
    •  TPTWR_34731 Acquisition failed in connection for deleting recovery information.
    •  TPTWR_34732 PutRow call failed in connection for deleting recovery information.
    •  TPTWR_35001 ODBC Connection failed to create INFARecoveryTable.
    •  TPTWR_35002 ODBC Connection failed to truncate target table <name> in load mode.
    •  TPTWR_35003 ODBC Connection failed to drop error table.
    •  TPTWR_35004 ODBC Connection failed to drop log table.
    •  TPTWR_35061 The following system error occurred when the PowerCenter Integration Service tried to get the values of some session attributes: <error message>.
    •  TPTWR_36001 Connectivity license key for Teradata database is not valid.
    •  TPTWR_36002 The session uses a deprecated connection object. Replace it with a valid connection object.
  •  TT Messages
    •  TT_11009 Overflow error. The Sequence Generator transformation has reached the end of the configured end value.
    •  TT_11013 An error occurred parsing group by ports.
    •  TT_11014 An Aggregator transformation contains an expression or port that is not valid.
    •  TT_11019 There is an error in the port <port name>. The default value for the port is set to: ERROR <error message>.
    •  TT_11020 There is an error in the port <port name>. The default value for the port is set to: ABORT <error message>.
    •  TT_11021 An error occurred moving data from the transformation <transformation name> to the transformation <transformation name>. The row was dropped.
    •  TT_11023 An error occurred converting data in the port <port name>. The row was dropped.
    •  TT_11041 Failed to initialize the transformation <transformation name>.
    •  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.
    •  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.
    •  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.
    •  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.
    •  TT_11090 The control expression of the Transaction Control transformation <transformation name> is evaluated to NULL.
    •  TT_11091 The control expression of the Transaction Control transformation <transformation name> is evaluated to <evaluated value>.
    •  TT_11100 The Joiner transformation <transformation name> input is not sorted. The row key value is <key value>.
    •  TT_11118 The cache directory configured for the transformation <transformation name> is empty or not valid.
    •  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.
    •  TT_11134 The lookup cache file with the named prefix <prefix name> used by the Lookup transformation <Lookup transformation name> cannot be reused.
    •  TT_11141 The transformation <transformation name> returned a row error status on receiving an input row on group <group>.
    •  TT_11144 The cache for the Lookup transformation <transformation name> indicates that the source type is <source type>, but the source type for this transformation is <source type>.
    •  TT_11145 The cache for the Lookup transformation <transformation name> indicates that the source file is <file name>, but the source file specified is <file name>.
    •  TT_11146 The cache for the Lookup transformation <transformation name> indicates that the type of source file <source file type> does not match the one specified for the transformation.
    •  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>.
    •  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.
    •  TT_11149 The Lookup transformation <Lookup transformation name> has an illegal file name <file name>.
    •  TT_11152 An error occurred processing the Normalizer transformation <transformation name>.
    •  TT_11158 An error occurred reading the lookup source for the Lookup transformation <transformation name>.
    •  TT_11161 An error occurred reading the lookup source for the transformation <transformation name>. It fetched <number of read rows> rows and <number of error rows> error rows.
    •  TT_11166 You cannot connect the transformation <transformation name> downstream from a Sequence Generator transformation.
    •  TT_11168 The code page specified for transformation <transformation name> is not valid for the file <file name>.
    •  TT_11169 The transformation <transformation name> code page <code page ID> is not found.
    •  TT_11170 An error occurred processing transformation <transformation name> and creating locale from the code page <code page name> for file <file name>.
    •  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.
    •  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.
    •  TT_11180 The lookup cache <file name> was created with a match policy different from the multiple match policy used for the dynamic Lookup transformation <transformation name>.
    •  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.
    •  TT_11204 An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the cache file name prefix <prefix>.
    •  TT_11209 The upgrade process failed to complete. The Sequence Generator transformation has an invalid datatype.
    •  TT_11210 An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the lookup table name <lookup table name>.
•  U Message Codes
  •  UDT Messages
    •  UDT_50000 Data Transformation service <service name> not found.
    •  UDT_50001 Output file name is empty.
    •  UDT_50002 Output precision <precision> is less than output length <length>.
    •  UDT_50003 Error threshold reached.
    •  UDT_50004 Data Transformation Engine initialization failed: <status.error code> <status.description>.
    •  UDT_50007 Invalid output type: <output type>.
    •  UDT_50008 Failed to flush the output.
    •  UDT_50010 Unstructured Data transformation can only have one default output port.
    •  UDT_50011 Unstructured Data transformation can only have one default input port.
    •  UDT_50014 There must be two default input ports in the Unstructured Data transformation.
    •  UDT_50020 License for Unstructured Data Option has not been enabled.
    •  UDT_50021 Failed to set output data for row <row number>.
    •  UDT_50022 Unable to open specified file <file name>.
    •  UDT_50023 CM API If_exec_streamer() failed with status <status code>.
    •  UDT_50024 CM API If_init_streamer_C() failed with status <status code>.
    •  UDT_50025 CM API If_get_next_output_message() failed with status <status code>.
    •  UDT_50026 Data Transformation port <port name> not found in the group <group>.
    •  UDT_50027 Data Transformation group <group> not found in the Unstructured Data transformation.
    •  UDT_50028 Invalid XSD schema for service <service name>.
    •  UDT_50029 Failed to load service <service name>.
    •  UDT_50030 Unknown error code <error number> for service <service name>.
    •  UDT_50031 Input port <port name> is not connected to source.
    •  UDT_50033 Service information not found for the service <service name>.
    •  UDT_50034 'Service Name' cannot be left blank in the transformation. Enter a service name in the UDT Settings tab.
  •  UM Messages
    •  UM_10000 The Service Manager failed to load the domain privileges.
    •  UM_10001 The user management metadata is inconsistent.
    •  UM_10002 The user management service is not enabled.
    •  UM_10004 The Service Manager could not find the user <user name> belonging to <security domain name> security domain.
    •  UM_10013 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.
    •  UM_10017 The password associated with node <node name> is invalid.
    •  UM_10018 The node <node name> is not defined within the domain.
    •  UM_10019 The node <node name> is not associated in the domain.
    •  UM_10020 The user <user name> belonging to <security domain name> was not associated with the node <node name>.
    •  UM_10021 The host name for node <node name> is inconsistent between node configuration and domain configuration.
    •  UM_10022 The port number for node <node name> is inconsistent between node configuration and domain configuration.
    •  UM_10023 The gateway setting for node <node name> is inconsistent between node configuration and domain configuration.
    •  UM_10024 The Service Manager cannot encrypt the credential because the characters in the user name, password, or domain name are not UTF-8 compliant.
    •  UM_10025 The Service Manager could not find the group <group> belonging to <security domain name> security domain.
    •  UM_10029 The service <service name> is not available.
    •  UM_10032 The Service Manager could not load privileges from the service <service name>.
    •  UM_10034 The Service Manager could not authenticate user <user name> in security domain <security domain name> with error <error message>.
    •  UM_10040 The privilege <privilege name> does not exist for service <service name>.
    •  UM_10041 The security domain <security domain name> is synchronizing with the LDAP server. Wait until synchronization has completed before accessing.
    •  UM_10042 The privilege does not exist for privilege path <privilege path>.
    •  UM_10043 The service type <service type> does not exist.
    •  UM_10046 The imported group <group> references a user <user name> in security domain <security domain name> that does not exist in the domain.
    •  UM_10053 Unable to create security domain <security domain name>. Security domain <security domain name> is reserved for internal use.
    •  UM_10059 Authentication failed because the authentication token is invalid.
    •  UM_10060 Error querying users from LDAP Service with error <error message>.
    •  UM_10061 Error querying groups from LDAP Service with error <error message>.
    •  UM_10082 The Service Manager failed to add users to service <service name> with error <error message>.
    •  UM_10083 The Service Manager failed to add groups to service <service name> with error <error message>.
    •  UM_10084 The Service Manager failed to remove users from service <service name> with error <error message>.
    •  UM_10085 The Service Manager failed to remove groups from service <service name> with error <error message>.
    •  UM_10087 The Service Manager failed to synchronize users and groups from service <service name> with error <error message>.
    •  UM_10088 The Service Manager failed to add users to service <service name>. The service users and groups are not synchronized with the domain.
    •  UM_10089 The Service Manager failed to add groups to service <service name>. The service users and groups are not synchronized with the domain.
    •  UM_10090 The Service Manager failed to remove users from service <service name>. The service users and groups are not synchronized with the domain.
    •  UM_10091 The Service Manager failed to remove groups from service <service name>. The service users and groups are not synchronized with the domain.
    •  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.
    •  UM_10093 The Service Manager failed to update privileges for user <user name> in security domain <security domain name> for service <service name> with error <error message>.
    •  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.
    •  UM_10095 The Service Manager failed to update privileges for group <group> in security domain <security domain name> for service <service name> with error <error message>.
    •  UM_10096 Unable to perform the requested operation because this would violate the maximum number of licensed Metadata Manager users: [<number of users]
    •  UM_10097 Unable to perform the requested operation because groups may not have Metadata Manager privileges or roles when Metadata Manager user count enforcement is enabled.
    •  UM_10098 Unable to perform the requested operation because Reporting Service <service name> does not support value of username@securitydomain <name> greater than 80 characters.
    •  UM_10099 User <user name> in security domain <security domain name> cannot disable own account.
    •  UM_100100 The Service Manager failed to authenticate user <user name> belonging to <security domain name>. The password was not specified.
    •  UM_100102 The created value provided for user <user name> was not used within its valid timeframe.
•  V Message Codes
  •  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>.
    •  VAR_27002 Error occurred in expanding reference for <string to expand>.
    •  VAR_27003 Error occurred in expanding references for initial value of <variable name>.
    •  VAR_27004 Internal error: aggregation operation requested for data with different datatypes.
    •  VAR_27005 Internal error: cannot perform COUNT operation on string or time datatype values.
    •  VAR_27010 Internal error: <variable>: <name> is initialized for multiple times.
    •  VAR_27017 Internal error: binary datatype is not supported for <variable type>.
    •  VAR_27018 Error: cannot find mapping parameter or variable of name <variable name> in transformation <transformation name>.
    •  VAR_27026 Error: Missing initial string value for <variable>: <name>.
    •  VAR_27030 Error: count value less than zero after merge.
    •  VAR_27032 Error: initial value for count aggregate type mapping variable: <name> cannot be less than zero.
    •  VAR_27033 Internal Error: cannot resolve server variable name for <number>.
    •  VAR_27034 Internal Error: cannot resolve data value for server variable <name>.
    •  VAR_27035 Internal Error: cannot resolve integer numeric data value for server variable <name ($PMSession error threshold, $PMSession log count)>.
    •  VAR_27036 Internal Error: cannot resolve string data value for server variable <name>.
    •  VAR_27037 Internal error: copy operation requested for data with different datatypes.
    •  VAR_27038 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.
    •  VAR_27039 Error: cannot reference to <variable>: <file path type> which is not for file or directory path.
    •  VAR_27040 Error: failed to delete existing persisted mapping variable value(s) for session <session name> from the repository.
    •  VAR_27041 Error: failed to persist mapping variable value(s) for session <session name> into the repository.
    •  VAR_27042 Error in getting the final value for mapping variable <name>. Skip saving the persisted value for this variable.
    •  VAR_27043 Error: data value overflowed or too large.
    •  VAR_27044 Error: cannot have null data value.
    •  VAR_27046 Error in parsing last saved timestamp <date/time value> for mapping variable <name>. Ignoring the persisted value in repository.
    •  VAR_27047 Error in parsing last saved timestamp <date/time value> for persisted value of mapping variable <name>. Ignore the persisted value in repository.
    •  VAR_27053 Incompatible data type conversion error.
    •  VAR_27054 Error in assigning initial data value to <variable>: <name>.
    •  VAR_27055 Error <mapping variable or parameter name>: Data conversion error.
    •  VAR_27056 Data conversion error in converting <data value>.
    •  VAR_27057 Data value overflowed or too large in converting <data value>.
    •  VAR_27061 Error: cannot find <workflow/worklet> variable of name <name> referenced in <workflow/worklet> <name>.
    •  VAR_27062 Warning! Cannot find section for <workflow/worklet> <name> and folder <name> in parameter file <name>.
    •  VAR_27064 Error: failed to persist <workflow/worklet> variable value(s) for <name> into the repository.
    •  VAR_27067 Error in parsing last saved timestamp <date/time value> for <workflow/worklet> variable <name>. Ignore the persisted value in the repository.
    •  VAR_27068 Error in parsing last saved timestamp <date/time value> for persisted value of <workflow/worklet> variable <name>. Ignore the persisted value in the repository.
    •  VAR_27069 Error in getting the final value for workflow variable <name>. Skip updating the persisted value for this variable.
    •  VAR_27072 Error: illegal to set the override value for pre-defined workflow variable <name>.
    •  VAR_27073 Internal error: decimal datatype is not supported for <variable type>.
    •  VAR_27075 Error: cannot reference to <variable/parameter type> <variable/parameter name> whose value is NULL.
    •  VAR_27079 Warning: <variable type>: <variable name>, NULL override value not valid. The override value is set to empty string.
    •  VAR_27086 Cannot find specified parameter file <file name> for <workflow/session name>.
    •  VAR_27097 Error: Failed to read line from parameter file <file name> for <workflow/session name>.
•  W Message Codes
  •  WEBM Messages
    •  WEBM_1001 Failed to connect to the webMethods Broker.
    •  WEBM_1002 Failed to reconnect to the webMethods Broker.
    •  WEBM_1003 Failed to disconnect from the webMethods Broker.
    •  WEBM_1004 Preserve Client State option is set, but no client ID is given in application connection <application connection name>.
    •  WEBM_1006 Exception from the Broker: <webMethods Broker name>.
    •  WEBM_2001 Failed to get a document from the webMethods Broker.
    •  WEBM_2002 Failed to acknowledge a document to the webMethods Broker.
    •  WEBM_2003 Failed to process a received document.
    •  WEBM_2004 Client Group does not have the permission to subscribe to document type <document type>.
    •  WEBM_2005 Source <source name> is configured to receive messages, but no client ID is given in application connection <application connection name>.
    •  WEBM_2010 Reader received and rejected a document with a mismatched document type <document type>: <document>.
    •  WEBM_2011 Failed to store a document in the recovery cache: <error message>.
    •  WEBM_2012 Failed to retrieve a document from the recovery cache: <error message>.
    •  WEBM_2013 The data retrieved from the recovery cache is not a valid webMethods document.
    •  WEBM_2014 Failed to create a recovery cache to store documents: <error message>.
    •  WEBM_2015 Failed to open a recovery cache to recover documents: <error message>.
    •  WEBM_2016 There is no cache folder specified for recovery.
    •  WEBM_2017 Failed to initialize the cache folder <recovery cache> for recovery.
    •  WEBM_3001 Failed to process a row of data.
    •  WEBM_3002 Invalid data <data> for field <field name>.
    •  WEBM_3003 Data conversion error for field <field name>.
    •  WEBM_3005 Client Group does not have the permission to publish document type <document type>.
  •  WRT Messages
    •  WRT_8000 Error processing table.
    •  WRT_8001 Error connecting to database.
    •  WRT_8004 Writer initialization failed <error message>. Writer terminating.
    •  WRT_8012 Writer Run: Data out of order for targets, Terminating.
    •  WRT_8019 No column marked as primary key for table <table name>.
    •  WRT_8020 No column marked as primary key for table <table name>.
    •  WRT_8023 Error truncating target table <target name>. <database error string>.
    •  WRT_8028 Error <error number> forking <loader type> external loader process for target <target name>.
    •  WRT_8031 Error <error number> unlinking named pipe <output file name>.
    •  WRT_8032 External loader error.
    •  WRT_8046 Error <Windows system error number> checking for completion of external loader <handle=process ID>.
    •  WRT_8047 Error: External loader process <process ID> exited with error <exit loader error number>.
    •  WRT_8048 Error <Windows system error number> retrieving the termination status for completed external loader [handle=<process ID>].
    •  WRT_8049 Error: External loader process <process ID> exited due to receipt of signal <UNIX signal number>.
    •  WRT_8053 Warning! Error executing pre-load stored procedures. Session <session name> user name <user name> Error <database error message>.
    •  WRT_8058 Error <system error number> opening session bad (reject) file <bad file name>.
    •  WRT_8059 Writer initialization failed [Failed to Initialize OuputFile.] Writer terminating.
    •  WRT_8060 Writer initialization failed [Failed to get external loader information]. Writer terminating.
    •  WRT_8062 Writer initialization failed [Failed to generate external loader control file]. Writer terminating.
    •  WRT_8063 Writer initialization failed [Failed to start external loader]. Writer terminating.
    •  WRT_8064 Error <system error number> opening session output file <output file name>.
    •  WRT_8065 Writer initialization failed [Failed to Initialize IndicatorFile]. Writer terminating.
    •  WRT_8066 Error <system error message> opening session log file <log file name>.
    •  WRT_8067 Writer initialization failed [NTTrustedConn() failed]. Writer terminating.
    •  WRT_8068 Writer initialization failed. Writer terminating.
    •  WRT_8070 Writer initialization failed <Internal error:no mapping [1]>. Writer terminating.
    •  WRT_8071 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.
    •  WRT_8072 Error resolving bad file name for target <target name>.
    •  WRT_8073 Error getting output file name for target <target name>.
    •  WRT_8074 Writer initialization failed [Internal Error]. Writer terminating.
    •  WRT_8075 Writer initialization failed [Error creating truncate table order]. Writer terminating.
    •  WRT_8076 Writer run terminated. [Commit Error].
    •  WRT_8077 Writer run terminated. [Error in executing pre-load stored procedures.]
    •  WRT_8079 Writer run terminated.
    •  WRT_8080 Writer run terminated. [Error loading data and error threshold reached: no data committed].
    •  WRT_8081 Writer run terminated. Error in loading data to target table <target instance name>.
    •  WRT_8082 Writer run terminated. [Errors encountered.]
    •  WRT_8085 Writer run terminated. [Internal Error].
    •  WRT_8086 Writer run terminated. [Error in executing post-load stored procedures.]
    •  WRT_8088 Writer run terminated. [External loader error.]
    •  WRT_8091 Error truncating target table <table name>. Error forming query.
    •  WRT_8092 Error truncating target table <table name>. Error preparing truncate target table query: <table query>.
    •  WRT_8095 Error <system error number> forking isql external loader process for target <target name>.
    •  WRT_8096 External loader error. Error getting Oracle loader information.
    •  WRT_8097 External loader error. Unsupported external loader type.
    •  WRT_8098 External loader error. Error executing external loader process: [No such file or directory] errno = [2].
    •  WRT_8100 External loader error. Error getting Sybase loader information.
    •  WRT_8109 Compare Targets for InfoSource.
    •  WRT_8110 BW Statement Init.
    •  WRT_8111 SAPSendDone.
    •  WRT_8116 ERROR: Target table <target table name> has no keys specified. Row # <row ID> in bad file.
    •  WRT_8117 ERROR: Target table <table name> does not allow INSERT. Row # <row ID> in bad file.
    •  WRT_8118 ERROR: Target table <table name> does not allow UPDATE. Row # <row ID> in bad file.
    •  WRT_8119 ERROR: Target table <table name> does not allow DELETE. Row # <row ID> in bad file.
    •  WRT_8120 ERROR: Invalid row type for target table <table name>. Row # <row ID> in bad file.
    •  WRT_8123 Failed to prepare target table load. Database error: <database error number>.
    •  WRT_8132 Error executing truncate target table query.
    •  WRT_8136 Error parsing stored procedure call text.
    •  WRT_8150 Invalid code page for output file <file name>.
    •  WRT_8151 Field separator character <separator> is invalid for target's code page.
    •  WRT_8152 NULL-character <null character> is invalid for target's code page.
    •  WRT_8156 Error: External loading MBCS data to Sybase IQ 11 is not supported.
    •  WRT_8157 Field <field name> of the output file <file name> is not wide enough to fit at least one specified NULL character.
    •  WRT_8171 Cannot locate CreateWrtTargetInstance function in the <library file name> shared library.
    •  WRT_8172 Cannot create ASCII locale.
    •  WRT_8173 Conversion from UNICODE failed - not all the characters were converted.
    •  WRT_8174 Error while flushing the buffer to output file <output file name>. Error message is <error message>, data buffer <buffer>.
    •  WRT_8175 Field separator string for file <file name> contains non-ASCII characters <Unicode characters>.
    •  WRT_8176 NULL character for file <file name> is not ASCII <Unicode character>.
    •  WRT_8178 Failed to get quote option for file <file name>.
    •  WRT_8179 Unknown error occurred while trying to close output file <file name>.
    •  WRT_8180 Failed to generate indicator file name using <output file name>.
    •  WRT_8181 Specified locale <locale name> for the file <output file name> is not valid for NULL character <character>.
    •  WRT_8183 Rollback failed for the target <target instance name>.
    •  WRT_8184 WARNING: The output codepage specified for the target file <target file name> is not ASCII-based, whereas the Informatica Server is running in ASCII mode.
    •  WRT_8185 Error transferring data from target <target name> using FTP.
    •  WRT_8186 Error while finalizing load. Writer run terminated.
    •  WRT_8187 Error resolving output file <file name> for target <target name>.
    •  WRT_8188 Invalid MQ header for <target name> target.
    •  WRT_8189 Invalid field type (MQCHAR expected) for <target name> target.
    •  WRT_8197 Error opening target merge file <file name>.
    •  WRT_8198 Error opening target file <file name> during merge target file processing.
    •  WRT_8199 Error reading target file <file name> during merge target file processing.
    •  WRT_8200 Error writing to target file <file name>.
    •  WRT_8201 Error getting the merge target file name for target <target name>.
    •  WRT_8203 Bulk execute failed. Re-trying.
    •  WRT_8204 Error: Unable to set null character.
    •  WRT_8205 Error: Could not find table name in catalog. This session cannot run with multiple partitions.
    •  WRT_8206 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.
    •  WRT_8208 Error truncating target table <target table name>. The Integration Service is trying the DELETE FROM query.
    •  WRT_8209 External loader error, Teradata external loader cannot take table names greater than 24 characters. The table name <table name> has <table length> characters.
    •  WRT_8210 External loader error, Error generating Teradata loader control file.
    •  WRT_8211 See external loader log <loader log file name> for more details.
    •  WRT_8212 Error: There have been too many database deadlocks. Unable to continue with the session.
    •  WRT_8215 External loader error. The external loader process <process ID> exited prematurely.
    •  WRT_8216 External loader error. Broken Pipe.
    •  WRT_8218 Error: Teradata external loader requires a primary key on table <table name> when using load mode <load mode>.
    •  WRT_8219 Error: Table mismatch, target table <table name> with <number of columns> columns mismatch with physical table with <number of columns> columns.
    •  WRT_8220 Error: get deadlock when reading /writing database.
    •  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.
    •  WRT_8229 Database errors occurred: <database error message>.
    •  WRT_8244 Error outputting row # <row number> for output file <flat file target>. The row was rejected.
    •  WRT_8246 Error: External loader is not supported for direct flat files. Target instance <target instance name>.
    •  WRT_8247 Error: Cannot run in bulk mode for a test load for connection <target name>.
    •  WRT_8250 Target (test load not supported for this target type): <target name> (Instance Name: <target instance name>).
    •  WRT_8270 Target connection group #<group number> consists of target(s) <target name>.
    •  WRT_8281 Error: The same character <character> is used as both field and decimal separator for the field <port name> of the target <target name>.
    •  WRT_8282 Error: The same character <character> is used as both field and thousand separator for the field <port name> of the target <target name>.
    •  WRT_8297 External loader process <loader process> exited with warning code <action file code>.
    •  WRT_8299 External loader error. Cannot find loader warning action file.
    •  WRT_8300 External loader error. Error opening loader warning action file <file name> for reading. errno = <system error code>.
    •  WRT_8301 Error loading warning codes from external loader warning action file <file name>.
    •  WRT_8302 External loader error. Error duplicating handle to stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.
    •  WRT_8303 External loader error. Error opening DB2 EEE external loader log file for writing. System error message is <system error message>. errno = <error number>.
    •  WRT_8304 External loader error. Error redirecting stderr to loader log file for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.
    •  WRT_8305 External loader error. Error restoring stderr for DB2 EEE external loader. System error message is <system error message>. errno = <error number>.
    •  WRT_8308 Error: Failed to write metadata for target table <target instance> to the output file <target file name>.
    •  WRT_8309 External loader error. The Date Format <format> is invalid. Target instance <target instance name>.
    •  WRT_8310 External loader error. Update is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.
    •  WRT_8311 External loader error. Update is not valid for target instance <target instance name> since no non-key field(s) is mapped to the target.
    •  WRT_8312 External loader error. Delete is not valid for target instance <target instance name> since no primary key(s) is mapped to the target.
    •  WRT_8313 External loader error. Upsert is not valid for target instance <target instance name> since update is not valid for the target.
    •  WRT_8315 The user-defined commit session is not supported for this type of mapping (no targets in commit groups).
    •  WRT_8324 Warning: Target Connection Group's connection doesn't support transactions. Targets <target names> may not be loaded according to specified transaction boundary rules!
    •  WRT_8329 Warning. Ignoring external loader control file directory <directory> since it is all whitespace.
    •  WRT_8343 Error: Target filename <file name> exceeded maximum allowable length <bytes>.
    •  WRT_8371 Row rejected since a rollback was issued due to errors in the transaction.
    •  WRT_8372 Row rejected since a rollback was issued due to a failed commit.
    •  WRT_8398 Error opening session output file <file name>. Error: <error text>.
    •  WRT_8399 Error closing target output file <file name>. Error: <error text>.
    •  WRT_8414 High availability license is absent. Retry period specified for Integration Service connection to target is ignored.
    •  WRT_8419 Flat file target <target name> FileName port is not supported with connection or merge option.
    •  WRT_8424 The Integration Service cannot read the control file template <control file template name>.
    •  WRT_8425 ERROR: Writer execution failed.
    •  WRT_8426 ERROR: Writer preparation failed.
    •  WRT_8428 Error transferring data from target <target name> using SFTP.
    •  WRT_8430 The Integration Service could not create a locale for code page ID: <code page>.
    •  WRT_8435 Error occurred opening the recovery queue: <error message>.
    •  WRT_8436 Error occurred closing the recovery queue: <error message>.
    •  WRT_8437 The following error occurred writing recovery information to the recovery queue: <error message>.
    •  WRT_8438 The following error occurred deleting recovery information from the recovery queue: <error message>.
    •  WRT_8439 The following error occurred reading recovering information from the recovery queue: <error message>.
    •  WRT_8442 The Integration Service cannot recover multi-partitioned flat file targets with the concurrent merge option.
    •  WRT_8443 The Integration Service cannot repeat a multibyte NULL character in the file <file name>.
    •  WRT_31215 Valid PowerCenter Connect for Salesforce.com license key is not found.
  •  WSC Messages
    •  WSC_33021 Web Service connection <application connection name> cannot have a negative timeout value <timeout value>.
    •  WSC_33023 Encountered a problem during SOAP request conversion (DOC to RPC): <error details>.
    •  WSC_33024 Error encountered in getting Operation Name for the table <operation name>.
    •  WSC_33026 Cannot retrieve HTTP proxy port number.
    •  WSC_33028 Cannot retrieve HTTP proxy password.
    •  WSC_33030 Cannot retrieve NT Domain value for authentication.
    •  WSC_33031 Cannot retrieve SSL parameters for authentication.
    •  WSC_33032 Failed to set trust certificates file <trust certificates file name>.
    •  WSC_33033 Failed to set client certificate file: <certificate file name>.
    •  WSC_38001 Cannot find any SQ instances in mapping.
    •  WSC_38002 Cannot find connection reference.
    •  WSC_38003 Cannot find connection.
    •  WSC_42008 Cannot create Java VM <JVM code number>.
    •  WSC_42013 Cannot load Java class <Java class name>.
    •  WSC_42021 Failed to load the library <library name>.
    •  WSC_42022 Failed to get the address of function <library name>.
  •  WSH Messages
    •  WSH_501 Service Workflow <workflow name> in repository <repository name> and folder <folder name> is invalid. This workflow cannot be accessed using the Web Services Hub.
    •  WSH_502 Failed to initialize the repository <repository name>: <error message>.
    •  WSH_505 Failed to fetch repository data during initialization: <error message>.
    •  WSH_516 Service <web service name>: Start of workflow <workflow name> located in folder <folder name> repository <repository name> failed with error <error message>.
    •  WSH_520 Failed to wait for workflow to complete: <error message>.
    •  WSH_521 Workflow <workflow name> in folder <folder name> failed to complete. Workflow notification handler is invoked.
    •  WSH_522 Failed to fetch details of the workflow <workflow name>, in folder <folder name> while fetching data for the repository <repository name> : <error message>.
    •  WSH_523 Failed to update data cache for folder <folder name> in the repository <repository name> : <error message>
    •  WSH_524 Failed to update data cache for workflow <workflow name>, in the folder <folder name> in the repository <repository name> : <error message>.
    •  WSH_526 Failed to fetch repository data for the repository <repository name> : <error message>.
    •  WSH_530 Failed to update data cache for repository <repository name> : <error message>.
    •  WSH_535 Web Services Hub initialization failed : <error message>.
    •  WSH_547 Service <web service name>: Failed to initialize service proxy.
    •  WSH_553 Failed to find service proxy for the Service <web service name>.
    •  WSH_557 Service <web service name>: Failed to activate the service workflow with error <error message>.
    •  WSH_567 Request <request instance ID>: Invocation timed out for Service <web service name>. Sending the response containing SOAP fault to the client.
    •  WSH_572 Request <request instance ID>: Client request is no longer active. Discarding the response message from the WS Writer.
    •  WSH_578 Request <request instance ID> Client IP <client IP address>: Request message for the Service <web service name> failed with error <error message>.
    •  WSH_601 Service <web service name>: Failed to start the workflow with error <error message>.
    •  WSH_606 Failed to connect to LM Server <domain name>:<integration service name> : <error message>.
    •  WSH_608 Failed to execute task <task name> : <error message>.
    •  WSH_617 Invocation failed for <request instance ID> with client IP <client IP address> using Service <web service name> with instance id <DTM instance ID>. Sending SOAP fault in response.
    •  WSH_622 Service <web service name>: Failed to update/add service proxy in the folder <folder name> in repository <repository name>.
    •  WSH_706 Failed to connect to the repository <repository name> : <error message>.
    •  WSH_721 Failed to start workflow for <workflow name>.
    •  WSH_731 Failed to update the service proxy list: <error message>.
    •  WSH_1005 Service <web service name> is not available.
    •  WSH_1006 Content sent is invalid.
    •  WSH_1007 Caller is not authorized to invoke the service.
    •  WSH_1010 Schema for prefix <namespace prefix> could not be found.
    •  WSH_1011 Web Services Provider source or target contains incompatible versions of metadata.
    •  WSH_1012 Web Services Provider source or target contains an invalid type.
    •  WSH_1013 Web Services Provider source or target contains an invalid key. Expected Key: [key name].
    •  WSH_1014 Web Services Provider source or target does not contain a required key.
    •  WSH_1016 The web service workflow <workflow name> does not exist or is invalid.
    •  WSH_1017 Invalid schema name : Schema <XML schema name> is not imported by the WSDL for the service workflow <workflow name>.
    •  WSH_1026 Failed to read from input stream.
    •  WSH_1027 Failed to parse the MIME message.
    •  WSH_1070 Request <request instance ID> ClientIP <client IP address>: Failed to read client message for Service <web service name> with payload of size <payload size>.
    •  WSH_1071 Request <request instance ID> ClientIP <client IP address>: Failed to decode client encoding for Service <web service name>.
    •  WSH_1072 Request <request instance ID> ClientIP <client IP address>: Reading client message for Service <web service name> failed with error <error message>.
    •  WSH_1077 Failed to send Request <request instance ID> with ClientIP <client IP address> to the service workflow instance.
    •  WSH_1078 Request <request instance ID> ClientIP <client IP address>: Failed to send client reply for Service <web service name> with error <error message>.
    •  WSH_1079 Service <web service name>: Web service source connection has been reset due to error <error message>.
    •  WSH_1084 Request contains invalid encoding.
    •  WSH_1104 Service statistics operation <operation name> failed with error <error message>.
    •  WSH_1124 Service <web service name>: Cannot find schema for namespace <namespace>.
    •  WSH_1126 Service <web service name>: Request or response with attachment is not supported for RPC encoding style.
    •  WSH_1127 Service <web service name>: Inconsistent binding namespace between Web Service Provider source and target.
    •  WSH_1128 Service <web service name>: Binding namespace not set.
    •  WSH_1129 Service <web service name>: Message <message> has empty content.
    •  WSH_1137 The folder <folder name> does not exist in repository <repository name>.
    •  WSH_1138 Invalid service timeout is specified for workflow <workflow name>. The default value <timeout value> is used.
    •  WSH_1140 Invalid maximum instance run per hub is specified for workflow <workflow name>. The default value <Maximum Run Count Per Hub value> is used.
    •  WSH_1141 Invalid service time is specified for workflow <workflow name>. The default value <service time threshold value> is used.
    •  WSH_1142 Folder <folder name> is incorrectly formatted. Please use '[repository_name:]folder_name' and the repository name is required when the hub is associated with multiple repositories.
    •  WSH_1143 Repository <repository name> is not associated with Web Service hub.
    •  WSH_1149 Nonce and created values are required for a PasswordDigest request .
    •  WSH_1150 The nonce value provided has been used. Provide a new nonce value for this login.
    •  WSH_1151 The created timestamp provided has expired or has been modified.
    •  WSH_1152 Nonce and created values must not be specified for a PasswordText request.
    •  WSH_1153 The password request is of an unknown type. The request must be a PasswordDigest or PasswordText request.
    •  WSH_1154 The login information provided is not valid.
    •  WSH_95063 Could not log in to the repository <repository name> with the specified username and password.
  •  WSP Messages
    •  WSP_33002 Failed to get attribute <attribute name>.
    •  WSP_33006 The mapping contains more than one Web Services Provider source.
    •  WSP_33007 The mapping contains more than one Web Services Provider target.
    •  WSP_33008 Out of memory.
    •  WSP_33009 Valid Real-time options key is not found, unable to run this Web Service session. Please obtain a valid real-time options key.
    •  WSP_34007 Failed to build the acknowledgement message.
    •  WSP_34008 Failed to parse the message.
    •  WSP_34010 Failed to build the data message.
    •  WSP_34011 Failed to build the eof message.
    •  WSP_34014 Failed to init connection, status code <code>, error message <error message>.
    •  WSP_34015 Failed to deinit connection, status code <code>, error message <error message>.
    •  WSP_34016 Failed to read data, status code <code>, error message <error message>.
    •  WSP_34017 Failed to write data, status code <code>, error message <error message>.
    •  WSP_34018 Failed to flush data, status code <code>, error message <error message>.
    •  WSP_34019 Failed to serialize data, error message <error message>.
    •  WSP_34020 Failed to deserialize data, error message <error message>.
    •  WSP_34030 Must have workflow context to run this session.
    •  WSP_34034 Error occurred while retrieving service information from repository.
    •  WSP_35001 Cache folder attribute cannot be fetched for reader partition <partition number>.
    •  WSP_35002 Cache folder specified for reader partition <partition number> is invalid.
    •  WSP_35003 Reader partition <partition number> failed to register for recovery.
    •  WSP_35005 Reader partition <partition number> failed to cache message.
    •  WSP_35006 Reader partition <partition number> failed to truncate message cache to last serialized message: <message text>.
    •  WSP_35008 Reader partition <partition number> failed to flush the cache: <message text>.
    •  WSP_35010 Reader partition <partition number> failed to unregister for recovery.
    •  WSP_35012 Failed to close checkpoint.
    •  WSP_35013 XML parser <partition ID> initialization failed.
    •  WSP_35015 Flat file parser <partition ID> initialization failed.
    •  WSP_35017 XML parser <partition ID> parse failed.
    •  WSP_35018 File parser <partition ID> fetch failed.
    •  WSP_35019 XML parser <partition ID> deinitialization failed.
    •  WSP_35020 Error in populating message fields.
    •  WSP_35021 MsgCount cannot be greater than 1 for two-way Non-WS Aware service.
    •  WSP_36002 Writer target <target name> partition <partition number> failed to initialize flat file generator.
    •  WSP_36003 Writer target <target name> partition <partition number> failed to initialize XML generator.
    •  WSP_36004 Writer target <target name> group <target group> partition <partition number> failed to process flat file messages.
    •  WSP_36005 Writer target <target name> group <target group> partition <partition number> failed to process XML messages.
    •  WSP_36006 Writer target <target name> group <target group> partition <partition number> failed to process end of file.
    •  WSP_36007 Writer target <target name> group <target group> partition <partition number> failed to process end of XML.
    •  WSP_36008 Invalid cache folder in writer target partition <target name> partition <partition number>.
    •  WSP_36010 Get message key <key> failed.
•  X Message Codes
  •  XMLR Messages
    •  XMLR_82061 Error: View {XML view} column {column name} was not found and cannot be NULL. Row will not be processed.
    •  XMLR_82065 Error: Row in XML view [{XML view name}] is not valid because the primary key column [{column name}] and the foreign key column [{column name}] are different types.
    •  XMLR_82078 Fatal Error: Infinite length is set for xsd:string for group [group name] column [column name]. Change the size to an appropriate value.
  •  XMLW Messages
    •  XMLW_31001 An error occurred while trying to initialize XML environment.
    •  XMLW_31002 An error occurred while trying to initialize XML manager.
    •  XMLW_31003 An error occurred while trying to uninitialize XML environment.
    •  XMLW_31004 The field <field name> with repository ID <ID number> should not belong to XML group <group number> named <group>.
    •  XMLW_31005 XML group <group> does not have any fields.
    •  XMLW_31006 There already was a row inserted into output for the topmost group. Rejecting the row# <row number>.
    •  XMLW_31007 Row# <row number> has a NULL PK value for XML group <group>.
    •  XMLW_31008 Row# <row number> has a NULL FK value for NOT TOPMOST XML group <group>.
    •  XMLW_31009 Unexpected error processing schema definition <schema definition>.
    •  XMLW_31010 Unexpected error occurred while trying to set the value of the element <XML element> with XML mapping <XML Map> to <value>.
    •  XMLW_31011 An error occurred while trying to convert the data for field <field name> repository ID <ID number> of the row <row number> to text.
    •  XMLW_31012 Cannot register XML group <group> for target <target instance> - no corresponding group definition found in the target.
    •  XMLW_31013 Unknown (or illegal) attribute value <value> for attribute <attribute name>. Check repository for possible data corruption.
    •  XMLW_31014 Unexpected error while generating XML text for the row being removed from the DOM tree. Row's PK value is <value>.
    •  XMLW_31016 Unknown error generating the output XML text.
    •  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>.
    •  XMLW_31018 Unexpected error occurred while initializing the XML output generator.
    •  XMLW_31019 Error initializing output file for XML target <target name>.
    •  XMLW_31020 Cannot find an XML group for the incoming block of rows. Fatal error.
    •  XMLW_31021 Error occurred while processing EOF for the XML target <target instance> group <group>.
    •  XMLW_31022 Fatal error while flushing to file <file name>. System error message is <error message>.
    •  XMLW_31023 Error initializing XML DOM object.
    •  XMLW_31024 Error transferring staged file for XML target <target instance> using FTP.
    •  XMLW_31026 Fatal error opening file <file name> for XML output.
    •  XMLW_31027 Fatal error closing XML output file <file name>. System error message is <error message>.
    •  XMLW_31029 Cannot locate XML init/deinit functions in the DLL <.dll file name>.
    •  XMLW_31030 FK field <field name> for group <group> has to be projected, i.e. there has to be an input field for it.
    •  XMLW_31040 Field <field name> of the *ROOT* XML group <group> is projected while the PK field is not.
    •  XMLW_31041 FK of the group <group> and PK of the parent group <group> should both either have an input field or not.
    •  XMLW_31043 FK is the only projected field from group <group>.
    •  XMLW_31047 MQ error occurred while flushing XML output.
    •  XMLW_31056 Fatal error opening WebSphere MQ queue <queue> for XML output.
    •  XMLW_31059 Fatal error returned while closing XML document <target name> after incremental flush/commit.
    •  XMLW_31060 Fatal error <error number> occurred while flushing XML output <target name>.
    •  XMLW_31061 Fatal error <error number> occurred while closing XML document <target name>.
    •  XMLW_31063 Fatal error <error number> occurred while opening file list <target>.
    •  XMLW_31064 Fatal error transferring local file <file name> into remote location <path> using FTP. The file list will not be produced.
    •  XMLW_31065 Fatal error <error number> opening an FTP connection for a file list <file name>.
    •  XMLW_31066 Fatal error <error number> while generating file list.
    •  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’.
    •  XMLW_31079 Error: Unknown On Commit attribute value in target <target name>. Check repository for possible corruption.
    •  XMLW_31080 Error: Orphans were encountered.
    •  XMLW_31086 Row <row number> in XML group <group> has more than one non-NULL hierarchical foreign key value. This row will be dropped.
    •  XMLW_31089 Error: The cache size <cache size> specified for XML target <target name> exceeds the 32-bit address space. It cannot be more than <cache size> on a 32-bit server.
    •  XMLW_31090 Unable to create index file <file name>.
    •  XMLW_31091 Error: Index file operation error <error number>.
    •  XMLW_31092 Error: Encountered an error while generating the XML document.
    •  XMLW_31093 Error: Encountered an error while establishing type hierarchical relationship.
    •  XMLW_31108 Error: An appropriate start row was not found for XML root group <group> with circular reference. No output was generated.
    •  XMLW_31110 Error: Duplicate row detected for single occurring group <group>, with parent group <parent group>.
    •  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.
    •  XMLW_31210 Fatal error transferring local file <file name> into remote location <path> using SFTP. The file list will not be produced.
    •  XMLW_31211 Fatal error opening remote list file <file name> using SFTP.

Preface

XMLW Messages