![Failed to import DMI metadata from file.
Cause: Internal error.
Action: Contact Informatica Technical Support.
File does not contain DMI metadata.
Cause: You tried to import a DMI file that does not contain DMI metadata.
Action: Select a different file to import.
Found the tag <tag[s]> while expecting the tag <tag[s]>. Please use a valid DMI file.
Cause: You attempted to import an invalid DMI file.
Action: Import a valid DMI file.
Business Content Integration Messages
Error activating DataSource.
Cause: There is an unknown error activating the SAP DataSource.
Action: Check the DataSource in SAP.
Error connecting to listener. Please start the listener before activating.
Cause: You may not have started the listener workflow before activating the
DataSource.
Action: Start the listener workflow.
Error fetching list of activated DataSources.
Cause: There may be a problem communicating with SAP.
Action: Reconnect to SAP and search for DataSources.
Error getting destination for <SAP logical system>.
Cause: The destination for the SAP logical system may be invalid.
Action: Validate the destination for the SAP logical system.
Error in getting registration information. Have you completed the registration?
Cause: There is no logical system in SAP for business content integration.
Action: Create a logical system for business content integration in SAP.
The file <filename> cannot be opened for writing.
Cause: The permissions on the BCI request file directory are set to read only.
Action: Disable read only permissions on the BCI request file directory.
46 Chapter 1: Client Error Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-62-320.jpg)
![Administration Console Error Messages
Correct the validation errors in <field name> and try the update again. [error description].
Cause: A validation error occurs when data cannot be validated for some reason. For
example, if you enter text into a field that requires an integer, the data cannot
be validated because it is the wrong type of data.
Action: Read the error description and make any necessary changes. For example, if
the error description indicates that an integer value is required in the field,
enter an integer value instead of a text value. For more information, look up
the cause and action for the error code.
The Domain Service could not disable the process due to the following error: [error
description].
Cause: The Service Manager encountered a problem while disabling the service
process. The service process may have been starting up when you attempted to
enable it.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
The Domain Service could not disable the service due to the following error: [error
description].
Cause: The Service Manager encountered a problem while disabling the service. The
service may have already been disabled, or it may have been in the process of
starting up.
Action: Read the error description and make any necessary changes. For example, if
the service was in the process of being enabled when you attempted to disable
it, wait for the service to become enabled before trying to disable it. For more
information, look up the cause and action for the error code.
The Domain Service could not enable the process due to the following error: [error
description].
Cause: The Service Manager encountered a problem while enabling the service
process. The service process may have been shutting down when you
attempted to enable it, or the node where the service process runs may not be
available.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
The Domain Service could not enable the service due to the following error: [error
description].
Cause: The Service Manager could not enable the service when you clicked the Enable
button. This error may appear, for example, if the service was shutting down
when you attempted to enable it.
64 Chapter 2: Administration Console Error Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-80-320.jpg)
![Action: Read the error description and make any necessary changes. For example, if
the shutdown operation was incomplete when you attempted to enable the
service, wait until the service is completely shut down before clicking the
Enable button. For more information, look up the cause and action for the
error code.
Enter a valid location for the shared configuration on the node [node name].
Cause: No location was supplied for the shared configuration file.
Action: Enter the storage location for the shared configuration file.
The following error occurred while attempting to remove the node. Error - [error description].
Cause: The Service Manager could not remove the node from the domain. A problem
may have occurred when the Service Manager attempted to abort the processes
running on the node. The Service Manager may have encountered a problem
when shutting down the node. Also, a problem may have occurred when the
Service Manager attempted to remove the node from the domainmeta.xml file.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
The following error occurred while attempting to remove the service. Error - [error
description].
Cause: The Service Manager could not remove the service.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
The following error occurred while attempting to shut down the node. Error - [error
description].
Cause: The Service Manager could not shut down the node.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
The following error occurred while enabling this service. Error - [error description].
Cause: The Service Manager could not enable the service when you attempted to
create it. This error may appear, for example, if the node you specified to run
the service is unavailable.
Action: Read the error description and make any necessary changes. For example, if
the error description indicates that the node is unavailable, either restart the
node or configure the service to run on a different node. For more
information, look up the cause and action for the error code.
This key was already used to update the license. Please use another key for the update.
Cause: The same key cannot be used more than once to update a license.
Administration Console Error Messages 65](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-81-320.jpg)
![Action: Verify that you are using the correct key to update the license.
The location of the shared configuration files for some of the nodes could not be determined.
Verify that all nodes are running.
Cause: The Service Manager could not determine the location of shared configuration
files. This problem can occur if node is not running or if the connection to the
node fails.
Action: Verify that all the nodes in the domain are running.
Logs for specified query could not be exported because of the following error. Error - [error
description].
Cause: The Service Manager could not export logs for a query.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
Logs for specified query could not be fetched because of the following error. Error - [error
description].
Cause: The Service Manager could not fetch logs for the query.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
Logs for specified query could not be purged because of the following error. Error - [error
description].
Cause: The Service Manager could not purge logs for a query.
Action: Read the error description and make any necessary changes. For more
information, look up the cause and action for the error code.
None of selected nodes are running. Select at least one node that can be connected to run
the Gateway Service.
Cause: The nodes you designated as gateway nodes have been shut down.
Action: Start up one of the designated gateway nodes. Alternatively, configure a node
that is running to serve as a gateway.
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.
Cause: The Upgrade Wizard cannot decrypt the encrypted password in the
Repository Agent or PowerCenter Server configuration file.
Action: Use pmpasswd in the previous version of PowerCenter to encrypt the password.
Correct the password in the configuration file, revalidate the configuration
file, and upgrade the Repository Agent or PowerCenter Server configuration
file again.
66 Chapter 2: Administration Console Error Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-82-320.jpg)
![BR_16038 Sanity check failed: <message>. Reader initialization failed.
Cause: The mapping may be invalid.
Action: Validate the mapping in the Designer and run the workflow again. If the
session fails, contact Informatica Technical Support.
BR_16045 Reader run terminating. [Error threshold <maximum number of errors>
reached reading data from <file name>].
Cause: The Integration Service reached the error threshold reading data from a source
file.
Action: See the previous error in the session log.
BR_16046 User defined query <query name> has references to mapping parameters or
variable that cannot be resolved correctly.
Cause: The Integration Service encountered an error while expanding referenced
parameters and variables in the specified query.
Action: Make sure you declare the parameters and variables in the specified query and
have valid start values.
BR_16047 User defined join condition and/or source filter <condition name> has
references to mapping parameters or variable that cannot be resolved
correctly.
Cause: The Integration Service encountered an error while expanding referenced
parameters and variables in the specified join or filter condition.
Action: Make sure you declare the parameters and variables in the specified join or
filter condition and have valid start values.
BR_16048 User defined source filter condition <condition name> has references to
mapping parameters or variables that cannot be resolved correctly.
Cause: The Integration Service encountered an error while expanding parameters and
variables in the specified filter condition.
Action: Make sure you declare the parameters and variables in the specified string and
that they have valid start values.
BR_16050 User provided string <string value> has references to mapping parameters or
variables that cannot be resolved correctly.
Cause: The Integration Service encountered an error while expanding parameters and
variables in the specified string.
Action: Make sure you declare the parameters and variables in the specified string and
that they have valid start values.
BR Messages 85](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-101-320.jpg)
![CMN Messages
CMN_1003 Server port not specified.
Cause: You did not specify the Integration Service port in the Administration
Console.
Action: In the Administration Console, enter a valid value for the Integration Service
port.
CMN_1006 Failed to connect to repository.
Cause: Connection information may be missing or invalid in the Administration
Console.
Action: In the Administration Console, check all connectivity information. If related
error messages appear in the session log, fix those errors before attempting to
connect again.
CMN_1008 Internal error.
Cause: An internal error occurred. Related error messages may appear to further
diagnose the error.
Action: Contact Informatica Technical Support.
CMN_1009 Internal error: Failed to execute child process.
Cause: Internal error.
Action: Contact Informatica Technical Support.
CMN_1011 Error allocating system shared memory of <number> bytes for [DTM Buffer
Pool]. Error is <system error code>: <system error message>.
Cause: An error occurred while your system allocated shared memory.
Action: Close any unnecessary programs and restart the Integration Service before
running the session again. Check the system parameters for shared memory
allocation.
CMN_1012 Error: shm_malloc() failed. Unable to allocate the bytes requested...
Cause: Insufficient shared memory allocation.
Action: Check the session log for related error messages. If none appear, contact
Informatica Technical Support.
CMN_1017 Error encountered decrypting password...
Cause: You entered an invalid password in the Administration Console.
Action: Make sure you typed in your password correctly. Passwords may be case
sensitive. If your password is correct, contact Informatica Technical Support.
108 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-124-320.jpg)
![CMN_1645 Error: Failed to get shared access to cache files <cache file name>. [dat/idx]
for lookup <Lookup transformation>.
Cause: One session is trying to read from a cache file while another session is still
writing to it.
Action: Wait until the first session completes, then run the session.
CMN_1646 Error: Failed to get exclusive access to cache files <cache file name>. [dat/
idx] for lookup <Lookup transformation>.
Cause: One session is trying to write to a cache file while another session is reading
from it.
Action: Wait until the first session completes, then run the session.
CMN_1647 Error: Failed to upgrade to exclusive access for cache files <cache file name>
for lookup <Lookup transformation>.
Cause: A session is trying to write to a cache file while another session is reading from
the file.
Action: Wait until the first session completes, and then run the session.
CMN_1649 Error: Lookup table name <lookup table name> is too long. Maximum allowed
length is <number>.
Cause: You exceeded the length allowed for the lookup table name.
Action: Reduce the length of the lookup table name.
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.
Cause: You configured a Lookup transformation to use a dynamic lookup cache and
the lookup table contains duplicate rows.
Action: Eliminate duplicate rows in the lookup table, or use a static cache.
CMN_1655 Error: Lookup Transformations <transformation name> and <transformation
name> have the same cache file name prefix <cache file name> but have
different connect strings <connect string> vs. <connect string>.
Cause: Two Lookup transformations have different connect strings, but have the same
cache file name.
Action: Make sure the connect strings match.
CMN_1656 Error: Lookup Transformations <transformation name> and <transformation
name> have the same cache file name prefix <cache file name> but only the
latter has a query override <query>.
Cause: Two Lookup transformations have different query overrides, but have the same
cache file name.
CMN Messages 121](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-137-320.jpg)
![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.
Cause: In a previous target load order group in a mapping, a dynamic Lookup
transformation created a cache file. A static Lookup transformation uses the
same cache file name and cannot delete it.
Action: Use unique cache file names for the transformations.
CMN_1684 Error: Dynamic Lookup <transformation name> needs to delete a cache file
<cache file name> that was created by a Static Lookup <transformation
name> in an earlier TLOG using different parameters.
Cause: In a previous target load order group in a mapping, a static Lookup
transformation created a cache file. A dynamic Lookup transformation uses
the same cache file name and cannot delete it.
Action: Use unique cache file names for the transformations.
CMN_1686 Error allocating <number of bytes requested> in memory for cache
transformation: <transformation name>.
Cause: You specified a cache size larger than the system can allocate.
Action: Either reduce cache size for the transformation or increase virtual memory
available in the machine.
CMN_1687 Error: Cache not enabled for Dynamic Lookup transformation
<transformation name>.
Cause: In the session, you disabled caching for a Lookup transformation that you
configured to use as a dynamic cache.
Action: If you configure a Lookup transformation with a dynamic cache, you must
enable caching in the session.
CMN_1689 Failed to allocate <number> bytes from process memory for [DTM Buffer
Pool].
Cause: There is insufficient process memory.
Action: Reduce the DTM buffer pool size, or free system resources.
CMN_1691 Cache expects port <port name> but cache file has it in a different data type
and cannot be used. A new cache file will be created.
Cause: Two Lookup transformations are configured to share a lookup cache, but the
datatypes of the cached columns in the Lookup transformations do not match.
Action: If you are using a named cache, verify that the caching structures match. If you
are using an unnamed cache, verify that the caching structures are compatible.
CMN Messages 125](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-141-320.jpg)
![CMN_1767 Failed to ftell file <filename>: Error Msg <error message>.
Cause: Operating system error.
Action: Contact your internal technical support.
CMN_1768 Failed to truncate file <filename>: Error Msg <error message>.
Cause: The Integration Service could not truncate the specified cache file.
Action: Check the additional error message for more information.
CMN_1769 Inconsistent recovery cache.
Cause: The Integration Service cannot run the session enabled for recovery because
the recovery cache file does not contain valid data.
Action: Delete all recovery cache files associated with the session and run the session
with recovery disabled to create a new cache file. To determine which recovery
cache file is associated with the session, compare the time at which the file was
last modified with the time the session failed. If the times are the
approximately the same, you can associate the cache file with the session.
You can also refer to the cache file names to determine which files are
associated with the session. Recovery cache file names use the following
format:
pmgmd_metadata_<repository ID>_<workflow ID>_<folder ID>_<session
ID>_<transformation ID>_<partition ID>_<group ID>_<checkpoint
ID>_<sequence number>.dat
For example, in the following file name, the session ID is 102:
pmgmd_metadata_7661f424_379f_11d7_947e_f63b53abfef7_103_2_102_0_0_
0_1_1.dat
Use the REP_LOAD_SESSIONS MX View on the repository database to
determine the name of the session associated with the session ID. You can use
REP_LOAD_SESSIONS to view information about reusable sessions.
CMN_1770 Recovery cache consumer is registered more than once.
Cause: Internal error.
Action: Contact Informatica Technical Support.
CMN_1771 The connection [database connection] specified is ambiguous. The
connection name exists in both relational and application connections.
Cause: In the Location Information session property for a Lookup transformation, or
the Connection Information session property for a Stored Procedure
transformation, you specified a database connection name that exists as both a
Relational and Application database connection. When the Integration Service
runs the session, it cannot determine which connection to use.
128 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-144-320.jpg)
![This might occur when you specify the database connection name for the
transformation in the Designer and then create a session using the mapping.
Or, this might occur when you type the connection name in the session
property.
Action: In the session properties, select the correct database connection name for the
Lookup or Stored Procedure transformation.
CMN_1772 Guaranteed Message Delivery cache directory <directory name> does not
exist.
Cause: The Integration Service cannot find the cache file directory for message
recovery.
Action: Verify that the cache file directory exists. Specify the correct path to the cache
file directory in the session properties. If the cache file directory does not exist,
create a directory and specify a directory path in the session properties.
CMN_1773 Error: Logical connection [database connection] in cache header file [lookup
cache file.dat] used by Lookup [Lookup transformation name] is either an
invalid connection or it exists in both Relational and Application type
connections.
Cause: In a cached Lookup transformation in the Designer, you specified a database
connection name that exists as both a Relational and Application database
connection in the Workflow Manager. When the Integration Service runs the
session, it cannot determine which connection to use.
Action: In the session properties, select the correct database connection name for the
Lookup transformation. Or, you can enter โRelational:โ before the connection
name if it is a Relational connection, or type โApplication:โ before the
connection name if it is an Application connection.
CMN_1774 Error: Logical connection [database connection] in Lookup [Lookup
transformation name] is either an invalid connection or it exists in both
Relational and Application type connections.
Same as CMN_1773.
CMN_1775 Recovery cache directory <directory name> is invalid.
Cause: The name for the recovery cache folder is not valid.
Action: From the Properties settings on the sources tab in the session properties,
specify a valid path for the recovery cache folder.
CMN_1777 The connection [database connection name] specified can not run SQL
query; hence can not be used as a lookup or stored procedure connection.
Cause: For a Lookup or Stored Procedure transformation, you selected an Application
database connection type that is not a relational database.
CMN Messages 129](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-145-320.jpg)
![CMN_1784 Connect string [connection name in Location Information property] too long.
Maximum length allowed is <maximum length>.
Cause: In the Location Information session property for a Lookup transformation,
you specified a database connection name that is too long.
Action: Edit the database connection name in either the Relational or Application
Connection Browser.
CMN_1785 Lookup SQL override [Lookup transformation] has references to mapping
parameters or variables that cannot be resolved correctly.
Cause: You referenced a mapping parameter or variable in the lookup SQL override,
but the Integration Service could not resolve the parameter or variable to text.
Action: Edit the lookup SQL override and verify you spelled the mapping parameter
or variable correctly. Also, verify you declared the mapping parameter or
variable in the mapping.
CMN_1786 Error: Failed to update row for Lookup [Lookup transformation].
Cause: The Integration Service failed to update the row in the dynamic lookup cache.
Action: Check the session log for related error messages.
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.
Cause: The Integration Service encountered an error when writing to the server log
file, most likely because the machine that hosts the server log file ran out of
disk space. Any messages related to the task the Integration Service was
performing at the time may have been lost.
Action: Check the available space on the machine that hosts the server log file.
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.
Cause: You configured two Lookup transformations in a mapping to share a named
cache, but you configured only one transformation for cache partitioning. The
Integration Service cannot share a partitioned cache with a non-partitioned
cache.
Action: Edit the session properties and configure either both Lookup transformations
with a hash auto-keys partition point or neither with a hash auto-keys
partition point.
or
Action: Edit the mapping so that the Lookup transformations do not share a cache.
or
CMN Messages 131](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-147-320.jpg)
![Cause: You configured two Lookup transformations in separate target load order
groups to share a named cache, but you configured a different number of
partitions for the target load order groups.
Action: Edit the session properties and configure the same number of partitions for
each Lookup transformation.
or
Action: Edit the mapping so that the Lookup transformations do not share a cache.
CMN_1801 Error: Lookup <Lookup transformation name> and Lookup <Lookup
transformation name> with cache file name prefix <prefix name> are setup for
partitioned cache but have condition columns in different order.
Cause: You added hash auto-keys partition points to two Lookup transformations that
are configured to share a named cache, but the condition columns for the
transformations do not match. When you use cache partitioning with a named
cache, the condition columns in the Lookup transformations must be identical
and in the same order.
Action: Remove the hash auto-keys partition points from the Lookup transformations.
or
Action: Configure the Lookup transformations with identical condition columns.
Verify that they are in the same order.
CMN_1802 ERROR: Some cache files with name prefix [name prefix] for Lookup [Lookup
transformation name] are missing or invalid.
Cause: You ran a session with multiple partitions that uses a named persistent lookup
cache, but the Integration Service cannot access some of the cache files.
Action: Verify the Integration Service can access all cache files for each partition. Or,
remove all existing persistent named cache files and run the session again. If all
named persistent cache files do not exist, the Integration Service rebuilds the
persistent cache files.
CMN_1804 Cache cannot be empty when running in recovery mode.
Cause: You enabled recovery for a session. The session failed during the session run.
Before you started the recovery session, the cache was emptied. This is not
allowed.
Action: When a session configured for recovery fails, make sure that the cache is not
emptied before starting the recovery session.
CMN_1806 Failed to get information for file <cache file>. Error message: <error
message>.
Cause: The Integration Service could not read the recovery cache file.
Action: See the additional error message for more information.
132 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-148-320.jpg)
![CMN_1921 External loader error. Control File will be generated for First Partition Only.
Cause: You tried to override the control file for a partition other than the first
partition in the Teradata target definition. The Integration Service only uses
the control file specified in the first partition when you create multiple
partitions in a session that uses Multiload or FastLoad to load to Teradata.
Action: Verify the control file in the first partition of the session uses the attributes you
want for the session.
CMN_1922 External loader error. Update is not valid for target instance [target definition
name] since no primary key(s) is mapped to the target.
Cause: The Teradata target table does not have a primary key, so the Integration
Service cannot generate a control file and update the target.
Action: Define a primary key on the target table and run the session again.
CMN_1923 External loader error. Update is not valid for target instance [target definition
name] since no non-key field(s) is mapped to the target.
Cause: The primary key column in the Teradata target definition is not connected to
an upstream transformation in the mapping. The Integration Service cannot
generate a control file and cannot update the target.
Action: Connect the primary key column in the Teradata target definition to an
upstream port in the mapping. Run the session again.
CMN_1924 External loader error. Delete is not valid for target instance [target definition
name] since no primary key(s) is mapped to the target.
Same as CMN_1923.
CMN_1925 The server does not support delimited files with the Teradata external
loaders.
Cause: The session uses a delimited flat file target to load data to the Teradata target
using FastLoad, Multiload, or TPump.
Action: Edit the session properties and configure the Teradata target to use a fixed-
width flat file.
CMN_1926 Error: Teradata external loader requires a primary key on table [target table
name] when using load mode [load mode].
Cause: The Teradata external loader connection uses the specified load mode, such as
update or upsert, but the target table has no primary key. The target table
must have a primary key for the Integration Service to use this load mode.
Action: Define a primary key on the target table and run the session again.
134 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-150-320.jpg)
![CMN_1927 Error: Unable to set null character.
Cause: Internal error.
Action: Contact Informatica Technical Support.
CMN_1928 External loader error. Upsert is not valid for target instance [target definition
name] since update is not valid for the target.
Cause: The Integration Service cannot perform upserts on the Teradata target table.
Action: Verify the target table has a primary key and that the primary key column in
the target definition is connected to an upstream transformation.
CMN_1929 External loader error [error message].
Cause: The Integration Service cannot generate the Teradata control file because some
control file option values are missing, such as the TPDID value.
Action: Edit the external loader connection in the session and enter a value for all
options.
CMN_1986 Service <service name> encountered an error while communicating with
Licensing Service: <error code and message>.
Cause: The service encountered an error while communicating with the Licensing
Service.
Action: See the additional error message for more information.
CMN_1989 Service <service name> is not licensed to execute on node <node name>.
Cause: The service is not licensed to run on the operating system of the node.
Action: Get a license to run the service on the operating system.
or
Action: Configure the service to run on a different node that has the appropriate
license.
CMN_2005 Unable to create log file <log file name>: <error>.
Cause: The log directory is not valid or does not have enough disk space.
Action: Verify the path and the directory for $PMWorkflowLogDir and
$PMSessionLogDir in the Integration Service configuration, workflow
properties, and session properties. The user who starts the Informatica Service
on the node must have permissions to write to the directory.
or
Action: Create a small file in the log directory to ensure that you are not out of disk
space.
CMN Messages 135](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-151-320.jpg)
![CMN_2006 Unable to create log file <log file name>.
Cause: The log directory is not valid or does not have enough disk space.
Action: Verify the path and the directory for $PMWorkflowLogDir and
$PMSessionLogDir in the Integration Service configuration, workflow
properties, and session properties. The user who starts the Informatica Service
on the node must have permissions to write to the directory.
or
Action: Create a small file in the log directory to ensure that you are not out of disk
space.
CMN_2018 Error: Failed to expand call text <text> for Stored Procedure transformation
<transformation name>.
Cause: The Integration Service cannot expand a parameter or variable in the call text
of the Stored Procedure.
Action: Verify that the parameter or variable is defined properly in the parameter file
and that its value in the parameter file matches the parameter or variable
datatype. For example, you cannot set an integer mapping variable to a text
string in the parameter file.
or
Cause: The Integration Service cannot expand a parameter or variable in the call text
of the Stored Procedure due to an internal error.
Action: Contact Informatica Technical Support.
CMN_2028 The Integration Service cannot parse user variable at position <user variable
position> in file <file>.
Cause: The Integration Service cannot find a value for the user variable in the
specified position in the control file.
Action: In the connection object attributes, verify that the user variable is defined and
contains the correct syntax.
CMN_7136 Error: At Transformation [transformation name]. One of the concatenating
pipelines contains a Transaction Control Transformation. This mapping is no
longer valid since TCT is an active transformation. Please move the TCT
before or after the concatenation.
Cause: The upgraded mapping contains a pipeline branch with a Transaction Control
transformation that concatenates with another branch in the same pipeline.
This mapping is no longer valid in PowerCenter.
Action: Edit the mapping and move the Transaction Control transformation either
before or after the concatenation.
136 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-152-320.jpg)
![CMN_17838 SAP code page <code page> is not compatible with the connection code page
<code page>.
Cause: The code page specified in the SAP RFC/BAPI Interface application
connection is not compatible with the SAP server.
Action: Verify that the code page entered for the application connection is compatible
with the SAP server.
CMN_17839 SAP code page <code page> is not compatible with the Integration Service
code page.
Cause: The code page specified for the Integration Service is not compatible with the
SAP server.
Action: Verify that the Integration Service code page is compatible with the SAP
server.
CMN_17840 Data <data> overflow at port <port number>. See below to find the row with
error.
Cause: The Integration Service encountered a row error. As a result, the session failed.
Action: See the session error log to determine the row that contains the error and view
more information about the error.
CMN_17848 The value for the property [TypeOfAEP] should be <value>.
Cause: The 6.x IDoc_Writer AEP transformation contains an invalid value for the
TypeOfAEP property.
Action: Enter the specified value for the TypeOfAEP property.
CMN_17851 Cannot get target property <property>.
Cause: Internal error.
or
Cause: The PowerCenter repository contains inconsistencies.
Action: Contact Informatica Technical Support.
CMN_17853 Error threshold for the session is reached.
Cause: The Integration Service has reached the error threshold configured in the
session properties.
Action: Eliminate the errors in your data.
or
Action: Increase the error threshold.
140 Chapter 12: CMN Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-156-320.jpg)
![DS Messages
DS_10008 Cannot find node [name] specified in the service lookup request in domain
[name].
Cause: The node is not running or does not exist in the domain.
Action: Verify that the node is running. Verify that the node name was entered
correctly.
DS_10009 Cannot find domain [name] specified in the service lookup request.
Cause: The command specified a domain gateway machine name and port number, as
well as a domain name. The command line program was unable to find the
domain on the gateway host machine.
Action: Verify the domain exists on the domain gateway host machine. Verify the
domain name was entered correctly.
DS_10012 The disable mode specified [mode] is invalid to disable service [service
name].
Cause: The DisableService command was used to disable the service shown. The
mode specified is invalid.
Action: Verify the mode is either complete, stop, or abort.
DS_10036 Service [name] is not available.
Cause: The service specified in the command is not available.
Action: Verify the service exists and is running. Verify the service name was entered
correctly.
DS_10037 Service [name] is not available on node [name].
Cause: The command entered specified a service name and a node name. The service
is not available on the node.
Action: Verify the service exists and is running on the node. Verify the service name
was entered correctly.
DS_10059 The requested service [name] is not running.
Cause: The service specified in the command is not running or does not exist.
Action: Verify the service exists and is running. Verify the service name was entered
correctly.
174 Chapter 22: DS Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-190-320.jpg)
![FR_3056 Error reading from file <file name>.
Cause: An error occurred reading the source file.
Action: Check other error messages logged for more details.
FR_3057 Error: Insufficient data for fixed-width flat file or fixed-width VSAM file. Row
data is <row data>.
Cause: The non line-sequential data is too small. The data displayed is the row,
including the trailing bytes between records.
Action: Make sure the data is the correct length and the bytes between rows match the
source file options.
FR_3058 Error processing COBOL file: cannot parse the input [numeric character in
<data> at position <position> has to be in the Latin1 code page].
Cause: The reader cannot read the input field because the input field contains
characters that are not in the Latin 1 code page.
Action: Change the input field to contain Latin 1 character data.
FR_3059 Error processing record <record name> in file <file name>: Record is invalid
because at least one set of redefines is invalid (redefine is not at a perfect
character boundary or conversion error for picnum field).
Cause: In a file source, at least one of the REDEFINES statements results in a
character exceeding the field boundary.
Action: Examine and correct the row where the error occurred.
or
Cause: The definition is incorrect.
Action: Edit the REDEFINES statement.
FR_3060 Error processing record <record name> in file <file name>: Conflicting shift
states at position <position number, referring to byte offset into the row>
when interpreting multiple redefines.
Cause: In a file source, one of the REDEFINES statements leaves the row in the shift
in state while another REDEFINES statement leaves the row in the shift out
state.
Action: Examine and correct the row where the error occurred or edit the
REDEFINES statement.
FR_3061 Error opening MQSeries queue. Operating system error message.
Cause: When running a session that reads from MQSeries and flat file sources, the
queue could not be opened due to an error.
Action: Correct the error indicated in the additional error message.
208 Chapter 28: FR Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-224-320.jpg)
![FTP_14018 Unable to FTP file. Error reading local file.
Cause: The target file was written to the target staging location, but the Integration
Service encountered an error while reading the file when transferring it to the
target machine.
Action: Check the session log for further messages.
FTP_14019 Unable to FTP file. Error writing to local file.
Cause: The FTP server encountered an error when writing to the source staging file
location.
Action: Confirm the staging directory specified in the session properties.
FTP_14020 Unable to delete file. FTP DELE command rejected by FTP server.
Cause: The FTP user does not have permission to delete the staging file.
Action: Delete the file manually, and check with the administrator of the FTP system
to get permission to delete FTP files for future sessions.
FTP_14024 FTP host name <host name> has incorrect format. Specify <hostname> or
<hostname>:<port> where 0 <port< 65536.
Cause: You entered an FTP host name in the wrong format in the Host Name field in
the FTP Connection Editor dialog box.
Action: Edit the FTP connection in the Workflow Manager. Specify the host name
format as <hostname> or <hostname:port>.
FTP_14040 FTP Socket [socket number] timeout. The FTP server has not responded in
time. Verify the FTP server is running, or increase the FTP timeout value.
Cause: The Integration Service tried to accessed a file source on an FTP server, but
the FTP server did not send any data before the Integration Service timed out.
By default, the Integration Service waits 600 seconds before timing out.
Action: Verify the FTP server is still running. If you need to increase the amount of
time the Integration Service waits before timing out, contact Informatica
Technical Support.
FTP_14046 Cannot reconnect to FTP server at <FTP host>: <control port number> within
retry period.
Cause: The connection to the FTP server failed. The Integration Service could not
reconnect to the FTP server within the retry period for the FTP connection
object.
Action: Check the status of the FTP server and run the session again. If the session is
enabled for recovery, recover the session.
216 Chapter 29: FTP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-232-320.jpg)
![Action: In the session properties, edit the Real-time Flush Latency value so that it is
greater than or equal to 0.
IDOC_17645 Reader Time Limit <time limit> must be greater than or equal to 0.
Cause: The Reader Time Limit session property specified for the SAPALEIDoc source
definition contains an invalid value.
Action: In the session properties, edit the Reader Time Limit value so that it is greater
than or equal to 0.
IDOC_17646 Failed to get connection reference for source qualifier instance <Source
Qualifier>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
IDOC_17647 Failed to get connection for source qualifier instance <Source Qualifier>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
IDOC_17648 Failed to initialize reader properties for source qualifier instance <Source
Qualifier>.
Cause: The Integration Service cannot initialize the session. The session properties for
the Source Qualifier instance might be invalid.
Action: Check the additional error message for more information.
IDOC_17649 Incorrect connection type specified for SAPALEIDoc source.
Cause: In the session properties, an invalid application connection type was selected
for the SAPALEIDoc source definition. An SAPALEIDoc source definition
must use an SAP_ALE_IDoc_Reader application connection.
Action: In the session properties, select an SAP_ALE_IDoc_Reader application
connection for the SAPALEIDoc source definition.
IDOC_17652 The value for the property [TypeOfEP] should be [IDocInterpreter].
Cause: In the 6.x IDoc_Interpreter EP transformation, the TypeOfEP property is not
set to IDocInterpreter.
Action: Edit the transformation so that the TypeOfEP property is equal to
IDocInterpreter.
IDOC_17655 The Integration Service failed to fetch the IDoc packet.
Cause: The Integration Service encountered an error while reading IDocs from the
SAP system.
Action: See the additional error messages for more information.
238 Chapter 32: IDOC Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-254-320.jpg)
![Action: Use the API method only after setting the appropriate transformation
property.
JTX_1017 Cannot use Java transformation API <method name> in a passive Java
transformation.
Cause: You used the API method in a passive Java transformation, However, you
cannot use the specified API method in a passive transformation.
Action: If you want to use the API method, create a new active Java transformation.
JTX1018 Cannot set default value for port <name>. Error : <error text>.
Cause: The Integration Service failed to evaluate the default value for the port.
Action: Verify the default value for the port in the Designer.
JTX_1101 Cannot create JExpression instance.
Cause: In the Java code for the transformation, the call to defineJExpression failed.
Action: In the Designer, verify that the expression being defined is valid and run the
session again.
JTX_1102 Row type <type> for Java expression is invalid. Valid row types are: INSERT,
DELETE and UPDATE
Cause: You used an invalid row type in a Java expression. Valid row types are INSERT,
DELETE, and UPDATE.
Action: Use a valid row type.
JTX_1103 Result of Java expression is NULL.
Cause: You used a Java expression in a Java transformation that returned a NULL
value. You cannot return NULL values from a Java expression.
Action: Modify the Java expression in the Designer so it returns a non-NULL value.
JTX_1104 Invalid Java expression API call - result datatype is <type>.
Cause: You passed an invalid datatype to an API method in a Java expression.
Action: Modify the call to the API method to pass a valid datatype, or use the correct
API method.
JTX_1105 Invalid datatype returned from Java expression.
Cause: The Java expression returned an invalid datatype. Valid datatypes are Integer,
Double, String, and Byte[].
Action: Modify the Java expression to return a valid datatype.
JTX_1106 Session object is NULL.
Cause: Integration Service failed to fetch the session object from the repository.
266 Chapter 36: JTX Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-282-320.jpg)
![JTX_1113 Truncated binary data for parameter X<parameter name> in expression
<expression name>.
Cause: The length of the binary data for the expression exceeded the precision for the
binary data parameter. As a result, the Integration Service truncated the data.
Action: Increase the precision for the binary data parameter for the expression.
JTX_1114 Failed to load class [<class name>] : [<error text>].
Cause: The Integration Service could not load the Java transformation class or an
inner class in a Java transformation. This error can occur if the repository
contains inconsistent data for the byte code or the repository does not contain
the updated byte code for the transformation.
Action: Correct the error indicated in the message and run the session again. You may
need to recompile the Java code for the transformation in the Designer.
JTX_1115 Exception occurred during initialization of JExpression object <name>.
Cause: Initialization of JExpression object failed.
Action: Verify the defined expression is valid and run the session again.
JTX_1117 Data was truncated for field [port name].
Cause: The precision of the data assigned to a binary or string output port in a Java
transformation is greater than the configured precision for the port. As a
result, the Java transformation truncated the data for the port. This warning
can occur for data assigned to an output port.
Action: Make sure the precision of the port is equal to or greater than the precision of
the data assigned to the port.
JTX_60000 Cannot validate Java transformation. Unable to retrieve metadata extensions
from repository.
Cause: The Designer or Integration Service encountered an internal error when
retrieving the metadata extensions for the Java transformation.
Action: Contact Informatica Technical Support.
JTX_60001 Cannot validate Java transformation. Unable to retrieve Java code snippets
from the repository.
Cause: The Designer or Integration Service encountered an internal error when
retrieving the Java code snippets for the transformation from the repository.
Action: Contact Informatica Technical Support.
JTX_60002 Cannot validate Java transformation. Unable to retrieve byte code from the
repository.
Cause: The Designer or Integration Service encountered an internal error when
retrieving the byte code for the transformation from the repository.
268 Chapter 36: JTX Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-284-320.jpg)
![LB Messages
LB_47007 Submitted task [task name] was canceled by a user.
Cause: The Session or Command task failed because it was stopped.
Action: Restart the task.
LB_47008 Submitted task [task name] was canceled because no available node has the
resources required by the task.
Cause: The Session or Command task failed because no available node has the
resources required by the task.
Action: Verify that at least one node has the resources required to run the task. Verify
the nodes that have the required resources are running and available.
LB_47010 The Integration Service failed to load the external resource manager library
due to error [error text].
Cause: The PowerCenter administrator configured PowerCenter to work with a third-
party resource manager. The Integration Service is unable to load the resource
manager library.
Action: Verify the following:
โ The third-party resource manager library exists in the location specified in
the PATH.
โ The user account authorized to start Informatica Services has read and
execute permissions on the library file.
โ The library file is not corrupt.
LB_47011 The Integration Service failed to retrieve the external resource manager
interface due to error [error text].
Cause: The PowerCenter administrator configured PowerCenter to work with a third-
party resource manager. The Integration Service is unable to access the
resource manager interface.
Action: Contact the third-party resource manager technical support.
LB_47012 The external resource manager interface failed to initialize due to error [error
text].
Cause: The PowerCenter administrator configured PowerCenter to work with a third-
party resource manager and the resource manager failed to initialize.
Action: Contact the third-party resource manager technical support.
LB_47047 The load balancer failed to detach node [node name].
Cause: Internal error. The Load Balancer could not detach the node because there are
tasks still reserved or started on the node.
272 Chapter 37: LB Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-288-320.jpg)
![Action: Contact Informatica Technical Support.
LB_47050 Received final notice for request on invalid node [node name] with event code
[code].
Cause: Internal error. The Load Balancer received a request from a node that has shut
down.
Action: Contact Informatica Technical Support.
LB Messages 273](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-289-320.jpg)
![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.
Cause: During a user-defined commit session, the Data Transformation Manager ran
out of buffer pool data blocks, which caused the session to fail.
Action: In the session properties, increase the DTM buffer block size.
or
Action: Modify the Transaction Control expression or the Custom transformation
procedure code so that the transformation issues commits more frequently.
LDBG_21035 Datablock write-lock error. offset <offset value>, reason [No space left on
device].
Cause: The Integration Service could not write data to the disk because there is not
enough space.
Action: Increase the amount of free space on the Integration Service system disk.
Verify that the operating system does not limit the amount of disk space for
the user who starts the Integration Service.
or
Cause: This message follows CMN_1107. The Integration Service could not write to
a Joiner index or data cache file because there is not enough space on the disk.
Action: Increase the Joiner index and data cache sizes. If possible, increase the index
and data cache sizes to hold all of the data.
LDBG_21149 ERROR determining truncate table order - could not create constraint load
dependencies for target.
Cause: You are attempting to truncate target tables, but the Integration Service is
unable to determine dependencies between target tables, possibly due to errors
such as circular key relationships.
Action: Ensure the validity of dependencies between target tables.
LDBG_21178 ERROR: Self-referential constraint in target.
Cause: You have set the session for constraint-based loading, but the Integration
Service is unable to determine dependencies between target tables, possibly
due to errors such as circular key relationships.
Action: Ensure the validity of dependencies between target tables.
276 Chapter 38: LDBG Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-292-320.jpg)
![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.
Cause: The mapping writes to target tables that have a primary key-foreign key
relationship, but the targets receive data from different transaction generators,
such as a Transaction Control transformation, or active sources. The
Integration Service cannot enforce the primary key-foreign key relationship.
The session might hang depending on the source data.
Action: If the session hangs, design the mapping to enforce constraint-based loading.
Or, remove the primary key-foreign key relationship between the targets in the
target database.
LDBG_21604 Data block read-lock error, offset <number>, reason: <reason>.
Cause: Error occurred trying to read from the joiner cache.
Action: Truncate the targets and run the session again.
LDBG_21605 Cannot open files in the directory <directory name>.
Cause: Cannot open files in the joiner cache directory.
Action: Check file system permission and free space in the cache directory.
LDBG_21633 For the dynamic lookup cache for [Lookup transformation], an input row has
NULL value in condition fields. This row will not be used for update of the
lookup cache.
Cause: The Lookup transformation in the mapping uses a dynamic lookup cache, and
the source row contains a null value in a column used in the lookup condition.
Action: None. When the row exists in the lookup cache, the Integration Service does
not update the row in the cache or target table.
LDBG_21668 Error: The Informatica server license does not allow more than one database
license to be used at a time.
Cause: The Integration Service configuration contains more than one database
license.
Action: Your Informatica license does not allow you to use more than one database
license at a time. Configure the Integration Service with only one database
license. For more information, contact the Informatica Developer Network.
LDBG Messages 277](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-293-320.jpg)
![LGS Messages
LGS_10006 The file [<file name>] was skipped during automatic purge.
Cause: The day limit or size limit for log event files was reached, and the Log
Manager purged the log event files. However, the Log Manager did not delete
the file because it was in use or recently modified.
Action: None. The Log Manager will delete the file during the next log purge if the file
is not in use or recently modified.
LGS_10010 Not all files are deleted in directory: [<directory name>].
Cause: The Log Manager attempted to purge the log event files in the directory.
However, some of the log event files were recently modified or still in use by
the Log Manager.
Action: Same as LGS_10006.
LGS_10011 Failed to access index file [<file name>] due to the following error [<error
text>].
Cause: The Log Manager uses an index file in each log file directory for quick access
to log event data files. The Log Manager was unable to read from or write to
the index file. This error can occur when the permissions for an index file are
modified or because the file was removed.
Action: Correct the error indicated in the message and view log events, export log
events, or purge log events again. Make sure the user account that runs
Informatica Services has read and write permission on the file.
LGS_10013 Invalid number of log events were received.
Cause: The Log Manager attempted to retrieve log events, but the number of events is
invalid. This error can occur when you use infacmd to retrieve log events, but
you enter an invalid number of events. For example, you enter 0 for the
number of log events to retrieve.
Action: Enter a valid number of log events to retrieve.
LGS_10016 Failed to close the file merge stream due to the following error [<error text>].
Cause: The Log Manager could not close multiple file streams to the same log event
file. This error can occur because the permissions for the log event file were
modified after the Log Manager began writing or because the file was
removed.
Action: Same as LGS_10008.
LGS_10017 Error creating the directory [<directory name>].
Cause: The Log Manager could not create the directory in the shared location for log
event files. This error can occur because the Log Manager does not have
280 Chapter 39: LGS Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-296-320.jpg)
![sufficient access permissions on the shared directory location for the log event
files.
Action: Make sure the user account that runs Informatica Services has read and write
permission on the shared directory location.
LGS_10019 Failed to open the file stream [<file name>] due to the following error [<error
text>].
Cause: The Log Manager was unable to open the log event file for reading or writing.
This error can occur when the permissions for a log event file or the log event
directory are modified after the Log Manager begins reading or writing or
because the file was removed.
Action: Same as LGS_10008.
LGS_10021 Failed to read log event from the file stream [<file name>] due to the following
error [<error text>].
Cause: The Log Manager attempted to retrieve log events from the log event file.
However, the log event file contains inconsistent data.
Action: Correct the error indicated in the message.
LGS_10024 Log request failed due to the following error [<error text>].
Cause: The Log Manager attempted to retrieve log events from the shared directory
location, but the retrieval failed due to an error.
Action: Correct the error indicated in the message and view logs events again.
LGS_10026 The log service configuration is missing the log service directory value for
the node <node name>.
Cause: The Log Manager could not write to the shared directory path for the log
event files because the directory location is missing in the domain
configuration.
Action: Configure a directory for the log event files.
LGS_10028 The index file [<file name>] is corrupt.
Same as LGS_10011.
LGS_10029 Failed to flush the file stream [<file name>] due to the following error [<error
text>].
Same as LGS_10008.
LGS_10034 Log request failed due to the following error [<error text>]. Unable to rollback
changes due to the following error [<error text>].
Cause: The Log Manager wrote to log event files. However, the process was
interrupted due to an error, and the Log Manager could not roll back the
changes it made to the log event file. This error can occur if the Log Manager
LGS Messages 281](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-297-320.jpg)
![writes to a shared directory location that becomes unavailable during the write
process.
Action: Correct the errors indicated in the message and make sure the shared directory
location is available.
LGS_10035 The timestamp index file [<file name>] is corrupted.
Cause: The Log Manager uses the timestamp index file to access the log event files in
a directory. However, the timestamp index file contains inconsistent data and
the Log Manager cannot access the log event files in the directory.
Action: None.
LGS_10036 The index file in the directory [<directory name>] appears corrupted.
Cause: The Log Manager uses an index file in each log file directory for quick access
to log event data files. However, the index file contains inconsistent data and
the Log Manager cannot access the log event files in the directory.
Action: None.
LGS_10052 The Log Manager could not find the session or workflow run.
Cause: The Log Manager has no information about the session or workflow run. The
name is invalid, the run is not the latest, or the database table was purged.
Action: If you are using infacmd, verify that the workflow or session name is valid. If
you are trying to get the session or workflow log in the Workflow Monitor,
select the latest session or workflow run.
282 Chapter 39: LGS Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-298-320.jpg)
![LM Messages
LM_36053 The server mode <current server mode> is invalid. Default server mode
<default server mode> will be used.
Cause: You have modified the data movement mode in the Administration Console.
Action: Change the data movement mode to ASCII or Unicode by modifying the
Administration Console.
LM_36072 Cannot get $PMStorageDir from configuration.
Cause: A service process could not determine the storage directory used for failover
and recovery.
Action: Verify that $PMStorageDir is configured properly in the Integration Service
process properties.
LM_36129 Cannot open log file [name].
Cause: The Integration Service cannot open the named log file.
Action: Verify that the log file exists in the directory you specified in the session or
workflow properties. Also, verify that the user attempting to access the log file
has read permission for the file.
LM_36133 Fail in reading log file [name].
Cause: The Integration Service was able to open the named log file, but cannot read
it. An administrator could have deleted the log file while you were attempting
to access it.
Action: Verify that the log file exists in the directory you specified in the session or
workflow properties. Then try to access the file again.
LM_36134 Session is initializing. Session log file is temporarily unavailable.
Cause: You are trying to access a session log file while the session is still initializing.
Action: Wait and open the file when the session has finished initializing.
LM_36136 Task instance <task ID> with workflow <workflow ID> <run ID> did not run on
this Integration Service.
Cause: The specified task instance did not run.
Action: Review the workflow log to view detailed information about why the task
instance did not run.
LM_36138 Cannot find workflow log name.
Cause: You did not specify a workflow log name in the workflow properties.
Action: Enter a workflow log name in the workflow properties.
290 Chapter 41: LM Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-306-320.jpg)
![LM_36210 Get worklet instance name from repository failed.
Cause: You may have deleted the worklet from the repository.
Action: Verify that the worklet exists.
or
Cause: The database server or the Repository Service may have failed.
Action: Verify that the database server and Repository Service are running.
or
Cause: The repository may contain inconsistencies.
Action: Contact Informatica Technical Support.
LM_36220 Log file [name] contains no data.
Cause: The log file is empty, most likely because someone deleted its contents.
Action: If you need to see the log file data, rerun the session or workflow to generate
the log file again.
LM_36225 The session log file was not created for session instance [ID = <number>] in
folder [ID = <number>], workflow [ID = <number>] [run ID = <number>],
worklet [ID = <number>] (possibly because the session failed during
initialization).
Cause: The Integration Service failed to create the named session log file because the
session failed during initialization.
Action: Check the workflow or server log file to see why the session failed.
LM_36229 Request failed because the connection was broken or the client is too slow in
processing replies, client [name], connection [name], request ID [number].
Cause: The Integration Service tried to retrieve a session or workflow log file over a
network connection, but the connection was broken or timed out.
Action: Check the network connection and try to open the log file again.
LM_36269 Connection request was made from client <PowerCenter Client> on host
<host machine> for connection to service type <service type>, service name
<service>, and service process name <node>. The connection request failed
because the service process <node> is not the intended service process.
Cause: A client application attempted a connection to a service process that is not the
master service process. With pmcmd, this error occurs if you use the host name
and port number options rather than the pmcmd options -d <domain> and -sv
<service>.
Action: Verify that the node is available and attempt the connection again. If you use
pmcmd, use the options -d <domain> and -sv <service>.
LM Messages 291](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-307-320.jpg)
![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.
Cause: The Service Manager could not find the Integration Service in the domain.
Action: Verify that the Integration Service is running in the domain. Use the pmcmd
options -d <domain> and -sv <service>, rather than the host name and port
number options.
LM_36272 Failed to get gateway information from URI <universal resource identifier>.
Cause: The Integration Service could not identify the master gateway.
Action: Verify that Informatica Services is running on the gateway node. Start
Informatica Services on the gateway node.
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>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
LM_36274 Failed to look up service in domain <domain>, service <service>, service
process <service process> from name service lookup using this URI <service
process> with fault code <code>, fault message <message text>.
Cause: The Service Manager failed to provide the connectivity information for the
Integration Service for the specified reason.
Action: Verify that the domain and the Integration Service are running. Verify that you
used the correct uniform resource identifier (URI).
LM_36275 Connection request was made from client <PowerCenter Client> on host
<host machine> for connection to service type <service type>, domain name
<domain>, service name <service>, and service process name <node>. The
connection request failed because the service is not configured to redirect
connections.
Cause: The Integration Service is configured so that connections are not redirected.
Action: In the Integration Service properties, set the custom flag
EnableConnectionRedirection to Yes, which is the default value.
LM_36310 Workflow [name]: Cannot open log file [name].
Cause: The Integration Service could not open the named log file during execution of
the named workflow. The workflow failed.
292 Chapter 41: LM Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-308-320.jpg)
![Action: Verify that the workflow log file directory specified in the workflow properties
exists and that the user attempting to access the log file has write permission
for the file.
LM_36311 Workflow [name]: Failed to expand workflow log file name <name>.
Cause: The log file name for the named workflow is invalid.
Action: Check the workflow log file name in the workflow properties. If you entered
the file path directly or used server parameters to represent the file path in the
Workflow Log File Name field, verify that the file path is correct and that the
server parameters are spelled correctly.
LM_36312 Workflow [name]: Log path exceeds limit of [number] characters: [path].
Cause: The workflow log file path you specified in the workflow properties is too
long.
Action: Shorten the file path so that it is less than or equal to the displayed character
limit.
LM 36320 <Workflow or task name>: Execution failed.
Cause: Execution of workflow or task failed.
Action: Review other messages in the workflow and session log to find the cause for
failure, fix the problem, and then run the workflow again.
LM_36338 Workflow [name] Could not start execution of this workflow because the
current run on this Integration Service has not completed yet.
Cause: You may be running the specified workflow.
Action: Wait until the workflow completes to restart it.
or
Cause: You may have attempted to restart a workflow that is suspended but not
stopped.
Action: To restart a suspended workflow, choose resume to complete the workflow.
or
Cause: You made a change to a workflow that is set to run continuously.
Action: Stop or unschedule the workflow, save the workflow, and then restart or
reschedule the workflow.
LM_36348 <Workflow, worklet, or session instance name>: Parameter file [name] not
found.
Cause: The Integration Service cannot locate the parameter file for the named
workflow, worklet, or session.
LM Messages 293](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-309-320.jpg)
![LM_36385 Workflow <name>: Could not acquire the execute lock for Workflow <name>.
Cause: You started the specified workflow, but the Load Manager could not lock the
workflow before running it. This message occurs when you or another user is
currently running the workflow.
Action: Make sure that the workflow has finished running before running it again.
LM_36401 <Session task instance> <task instance path> Execution terminated
unexpectedly.
Cause: The DTM process did not stop, abort, or fail properly.
Action: Contact Informatica Technical Support.
LM_36440 <Task type> task instance <task instance path>: Error in fetching persistent
variable values for <workflow or worklet> [workflow or worklet name].
Cause: The Integration Service failed to get a persistent variable value for the
workflow or worklet.
Action: Check the Integration Service log and Repository Agent log for more
information.
LM_36441 Error: Both parameter list and parameter file are specified.
Cause: A third party application tried to start a workflow and specified both a
parameter list and a parameter file. The Integration Service needs one or the
other to run a workflow, not both.
Action: In the third party application, verify you only specify a parameter list or a
parameter file.
LM_36471 <Workflow name>: Failover of workflow schedule failed because the
information in storage is inconsistent or incomplete.
Cause: Trace message. If you have the high availability option, workflow schedule
information is written to a storage file in the storage directory,
$PMStorageDir. The Integration Service could not retrieve the information
required to start up the scheduled workflow on another node.
Action: Explicitly schedule the workflow again to run it.
LM_36476 <Workflow name>: Failover of workflow execution failed because the
workflow cannot be internally scheduled in recovery mode.
Cause: After the Integration Service failed over the workflow to another node, an
internal limit was exceeded.
Action: Try to recover the workflow manually. Also, verify the availability of the node
where the service process started the workflow.
296 Chapter 41: LM Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-312-320.jpg)
![LM_36538 <Session instance path>: Unable to write to temporary parameter file
[parameter file name] with error [error number] [cause of error].
Cause: You ran a workflow on a server grid. The master server distributed a session
that uses a parameter file to a worker server. The worker server needs to create
a temporary parameter file in its $PMTempDir directory using parameter file
information received from the master server. However, the worker server failed
to create the temporary parameter file because it does not have permission to
write to $PMTempDir, or because the directory contains a file with the same
name.
Action: Verify the worker server has the correct permissions to access $PMTempDir
and run the workflow again. Or, if $PMTempDir contains a file with the same
name as the temporary parameter file, delete it and run the workflow again.
LM_36539 <Session instance path>: Unable to unlink temporary parameter file
[parameter file name] with error [error number] [cause of error].
Cause: You ran a workflow on a server grid. The master server distributed the session
to a worker server. The worker server created a temporary parameter file in
$PMTempDir, but it failed to delete the file.
Action: Verify the worker server has the correct permissions to access $PMTempDir
and verify there is enough disk space. Or, you can manually delete the
temporary parameter file from the $PMTempDir directory.
LM_36543 <Task name> condition expression eval error < expression >.
Cause: The expression you entered may have invalid characters or cannot be
evaluated.
Action: Verify that the expression is valid in the Workflow Manager.
LM_36544 <Task name>: condition expression <expression> will not evaluate to a
numeric value.
Cause: You may have entered the wrong datatype in the expression.
Action: Review the expression in the Workflow Manager to ensure that it uses
Numeric datatypes.
LM_36564 <Task name>: Invalid datatype conversion for variable [name], expression
datatype [datatype], variable datatype [datatype].
Cause: In the Workflow Manager, you assigned a value to a variable using the
Assignment task. The Integration Service cannot convert the datatype of the
expression to the datatype of the variable.
Action: Either fix the expression in the Assignment task or change the datatype of the
variable.
LM_36565 <Task name>: Variable [name]: data conversion exception <value>.
Cause: Internal error.
298 Chapter 41: LM Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-314-320.jpg)
![Action: Contact Informatica Technical Support.
LM_36566 <Task name>: Unable to resolve the left-hand side variable [name] as a user-
defined workflow/worklet variable.
Cause: In the Workflow Manager, you assigned a value to a variable using the
Assignment task. The Integration Service does not recognize the variable as a
user-defined workflow or worklet variable.
Action: Check the variable declaration in the Assignment task and make sure it
matches the name of a user-defined workflow or worklet variable.
LM_36567 Unable to rollback the assignment for variable <name>.
Cause: Internal error. An error occurred during the assignment of a variable. The
Integration Service updated the value of the variable and could not rollback
the change.
Action: Contact Informatica Technical Support.
LM_36580 <Task instance name and path>. Email Username not specified.
Cause: The email address for the Email task is missing.
Action: Enter a valid email address in the Email User Name field for the Email task.
LM_36581 <Task instance name and path>. Failed to send email.
Cause: The Integration Service failed to send the email specified in the Email task.
This might occur if you did not specify an email profile on the machine
hosting the Integration Service, or if the machine does not have an email
client.
Action: Verify you specify an email profile on the machine hosting the Integration
Service, and that the machine has the correct email client.
LM_36601 <Timer name> Unable to schedule timer with the timer task manager.
Cause: The time specified is invalid. The range must be between 00:00:00 January 1,
1970 UTC, and 3:14:07 January 19, 2038 UTC.
Action: Specify a time within the valid range.
LM_36602 <Variable name> Wait for absolute time specified by variable <variable type>.
The variable does not exist.
Cause: The variable is not specified in the workflow.
Action: Specify the variable in the workflow properties.
LM_36603 <Variable name> Wait for absolute time specified by variable <variable type>.
The variable is not of type date/time.
Cause: The variable type entered was not the Date/Time datatype.
Action: Change the datatype to Date/Time.
LM Messages 299](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-315-320.jpg)
![LM_36604 <Variable name> Wait for absolute time specified by variable <variable type>.
The variable value is null.
Cause: The value of the variable was null.
Action: Specify a value that is not 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>].
Cause: An Event-Wait task was configured to delete the file watch indicator file when
the Integration Service detected the file. The Integration Service detected the
file but failed to delete it.
Action: Verify the user has permission to delete the file.
LM_36823 Workflow <workflow ID> <session> not unscheduled because it is not
scheduled.
Cause: You tried to remove from schedule a workflow that you have not yet
scheduled.
Action: Verify that you selected the correct workflow to remove from schedule.
LM_36824 <Workflow name>: Scheduled workflow was not rescheduled because the
schedule changed after the Integration Service last ran.
Cause: The schedule changed during failover.
Action: Reschedule the workflow.
LM_44122 Errors encountered in initializing storage in directory <directory name>.
See previous error message in log for information.
LM_44124 Integration Service is missing workflow manager storage.
Cause: Internal Error. The Integration Service could not find the state of operations.
Action: Contact Informatica Technical Support.
LM_44125 Workflow manager storage is not ready for Integration Service.
Cause: Internal Error. The Integration Service is missing the storage file that it uses to
write information about services running during failover.
Action: Contact Informatica Technical Support.
LM_44127 Failed to prepare the task [name].
Cause: The Integration Service was unable to prepare the task due to an internal
error.
Action: Contact Informatica Technical Support.
300 Chapter 41: LM Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-316-320.jpg)
![LM_44136 Failed to release remaining execution locks as failover.
Cause: A network or database issue prevented locks from being released. Resilience
mechanisms could not recover from a connection problem between the
Integration Service and the Repository Service or between the Repository
Service and the repository database.
Action: Verify that the Integration Service and Repository Service are running and
that Repository Service can connect to the repository database.
LM_44180 The number of asynchronous threads for repository connections specified
<number of threads> is too low, using default of <number of threads>.
Cause: By default, the Integration Service creates one asynchronous thread for every
10 repository connections. The number of threads specified by the
LMRepoConnAsyncThreads custom Integration Service property is less than
10. The specified number of threads is not sufficient for the number of
repository connections.
Action: To use the default number of threads, remove the
LMRepoConnAsyncThreads custom Integration property. Alternatively, you
can increase the LMRepoConnAsyncThreads value.
LM_44183 Scheduling workflow is not allowed because the Integration Service is
running in safe mode.
Cause: The Integration Service assigned to the workflow is running in safe mode. You
cannot schedule workflows when the Integration Service runs in safe mode.
Action: If you have the Admin Integration Service privilege, manually start the
workflow. You can also change the operating mode for the Integration Service
to normal.
LM_44184 Scheduled workflow {<workflow name>} was not rescheduled because the
Integration Service is running in safe mode.
Cause: The workflow runs on a schedule. However, the Integration Service does not
run scheduled workflows in safe mode.
Action: If you have the Admin Integration Service privilege, manually start the
workflow. You can also change the operating mode for the Integration Service
to normal.When you change the operating mode to normal, all scheduled
workflows will begin running.
LM_44185 User [<repository user name>] does not have sufficient privilege to log on
while the Integration Service is running in safe mode.
Cause: You must have the Admin Integration Service repository privilege to connect
to an Integration Service running in safe mode.
Action: Use a repository user account that has the Admin Integration Service privilege
to connect to the Integration Service.
LM Messages 301](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-317-320.jpg)
![MQ_29102 Line <line>, column <column>: Unknown identifier <identifier>.
Same as MQ_29100.
MQ_29103 Line <line>, column <column>: String literal not terminated properly.
Same as MQ_29100.
MQ_29104 Line <line>, column <column>: Syntax Error.
Same as MQ_29100.
MQ_29105 Filter Expression does not have a boolean return type.
Cause: The filter condition does not return a boolean TRUE/FALSE value.
Action: Edit the filter condition to return a boolean TRUE/FALSE value.
MQ_29106 Line <line>, column <column>: Left operand must be boolean.
Cause: The filter condition does not contain a boolean operand.
Action: Check the left-hand side of the logical operator in the filter condition.
MQ_29107 Line <line>, column <column>: Right operand must be boolean.
Cause: The filter condition does not contain a boolean operand.
Action: Check the right-hand side of the logical operator in the filter condition.
MQ_29108 Line <line>, column <column>: Incompatible types for relational operator.
Cause: The logical operators [=, <>, >=, <=, >, <] in the left-hand and right-hand sub-
expression have incompatible datatypes.
Action: Edit the filter condition with compatible datatypes for relational operators in
the left-hand and right-hand sub-expression.
MQ_29109 Line <line>, column <column>: Not enough arguments. <function name> ()
should have argument(s).
Cause: The function in the filter condition does not enough arguments.
Action: Apply arguments to the function in the filter condition.
MQ_29110 Line <line>, column <column>: Too many arguments. <function name> ()
should have argument(s).
Cause: There are too many arguments in a function.
Action: Use fewer arguments in a function.
MQ_29111 Line <line>, column <column>: Wrong type in <function name> (). Argument
should be CHAR/BYTE.
Cause: The function expects an argument in MQCHAR or MQBYTE type.
MQ Messages 313](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-329-320.jpg)
![queue for mappings that contain an associated source qualifier, use the
RemoveMsg(TRUE) function.
MQ_29248 MQ queue manager [<queue manager>] encountered a transient connection
failure.
Cause: The Integration Service could not connect to the MQ queue manager. The
network or the MQ server may be down. The Integration Service will attempt
to connect to the MQ queue during the retry connection period. If it does not
connect to the MQ queue during the retry connection period the session fails.
Action: Verify the MQ queue manager is running. Or, verify that the network is active.
MQ_29250 Connection retry period expired. The Integration Service could not connect to
MQ queue manager [<queue manager>].
Cause: The Integration Service could not connect to the MQ queue manager during
the retry connection period. The network or the MQ server may be down. As
a result, the session failed.
Action: Verify the MQ queue manager is running. Or, verify that the network is active.
Restart the session.
MQ_29251 Resilience is disabled, because Destructive Read and recovery are not
configured.
Cause: The Integration Service could not make multiple connection attempts to the
MQ queue manager, because Destructive Read and recovery are not
configured for the session.
Action: In the session properties, configure Destructive Read and recovery.
MQ_29255 The Integration Service truncated message data while reading from queue
<queue>:<queue manager> in destructive read mode.
Cause: The Integration Service read an MQSeries message that exceeded the precision
of the MESSAGE_DATA column in the MQSeries source definition. As a
result, the Integration Service truncated the data. Because the session is
running in destructive read mode, the session failed and the Integration
Service did not delete the message from the source queue.
Action: Increase the precision of the MESSAGE_DATA column in the MQSeries
source definition.
MQ Messages 319](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-335-320.jpg)
![NODE Messages
NODE_10014 [Resource type] resource [resource name] not found in node configuration.
Cause: The EnableNodeResource or DisableNodeResource command was used to
enable or disable a resource on a node. infacmd could not find a resource with
the name and type shown on the node.
Action: Verify the following conditions:
โ The resource shown exists on the node.
โ The resource is of the type shown.
โ The resource name was entered correctly.
324 Chapter 45: NODE Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-340-320.jpg)
![ODL_26045 Error allocating DB2 environment handle.
Cause: DB2 database error.
Action: Verify the DB2 environment is configured correctly. Also, contact your
database administrator.
ODL_26046 Error loading bulk API library.
Cause: DB2 database error.
Action: Verify the DB2 environment is configured correctly. Also, contact your
database administrator.
ODL_26047 Could not allocate a bulk API instance.
Cause: DB2 database error.
Action: Verify the DB2 environment is configured correctly. Also, contact your
database administrator.
ODL_26060 Fatal Error: Encountered Teradata error that aborts current transaction.
Cause: The Integration Service encountered one of the following Teradata errors that
aborted the current transaction:
โ 2801 Duplicate unique prime key error.
โ 2802 Duplicate row error.
โ 2803 Secondary index uniqueness violation.
โ 3604 Cannot place a null value in a NOT NULL field.
Action: Remove the row that caused the Teradata error and restart the session.
ODL_26069 Failed to create and initialize SQL OLE DB instance.
Reason <error code>: <system error>.
Cause: The Repository Service or Integration Service failed to connect to the
Microsoft SQL Server database because one or more Microsoft SQL Server
API function calls failed.
Action: Verify that all specified Microsoft SQL Server classes are properly registered in
the registry. Then re-register oledb32.dll. [Regsvr32 Program FilesCommon
FilesSystemOle DBoledb32.dll]. Use the returned error code and error
message to determine the cause of this error.
ODL_26071 Graphic/vargraphic partition key types are supported only on servers with
UNICODE data movement enabled.
Cause: You ran a session using database partitioning on an Integration Service
running in ASCII mode and the IBM DB2 target table uses a partitioning key
with either a Graphic or Vargraphic column.
Action: Run the session on an Integration Service in Unicode mode.
340 Chapter 48: ODL Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-356-320.jpg)
![OPT Messages
OPT_63005 ERROR: Pushdown optimization failed for the session <transformation
name>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
OPT_63007 ERROR: Failed to expand configuration parameter [$$PushdownConfig].
Cause: The Integration Service could not expand the $$PushdownConfig
configuration parameter because it could not locate the parameter file or could
not locate the specified parameter within the parameter file.
Action: Verify that the parameter file contains the correct path, and a value for the
$$PushdownConfig parameter is specified within the file.
OPT_63008 ERROR: Configuration parameter [$$PushdownConfig] contains an invalid
value.
Cause: The Integration Service could not expand the $$PushdownConfig
configuration parameter because the parameter files specifies an invalid value
for the $$PushdownConfig parameter.
Action: Verify that the parameter file specifies a valid value for the $$PushdownConfig
configuration parameter.
OPT_63014 Pushdown optimization to source stops at the transformation
<transformation name> because the mapping contains too many pipeline
branches.
Cause: The mapping contains more than 64 two-way branches, 43 three-way
branches, or 32 four-way branches. The Integration Service cannot generate
SQL to push all the branches of the mapping to the database.
Action: None.
OPT_63015 Pushdown optimization to target stops at the transformation <transformation
name> because the mapping contains too many pipeline branches.
Cause: The mapping contains more than 64 two-way branches, 43 three-way
branches, or 32 four-way branches. The Integration Service cannot generate
SQL to push all the branches of the mapping to the database.
Action: None.
OPT_63021 Pushdown optimization stops at the transformation <transformation name>
because it is connected to multiple targets.
Cause: You attempted to push a transformation to multiple targets for target-side
partial pushdown optimization. The Integration Service cannot generate the
SQL to push the transformation to both targets.
344 Chapter 49: OPT Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-360-320.jpg)
![PCSF Messages
PCSF_10004 Authentication for <user name> failed because <error message>.
Cause: The authentication failed for the specified user.
Action: Resolve the issue using the details provided in the error message.
PCSF_10005 An attempt to [activity] access [object name] failed for [user name] because:
[error text].
Cause: A user attempted to run a command that accesses the object specified. The
command could not be executed because the command line program cannot
access the object.
Action: Verify that the user specified in the command has permission on the object.
PCSF_10006 No Integration Service Ref were provided.
Cause: Validation failed for an SAP BW Service because no Integration Service
references were found.
Action: Configure the Integration Service for the an SAP BW Service.
PCSF_10007 Cannot connect to repository <repository name> because: <reason for
failure>.
Cause: A problem was encountered when you attempted to connect to the repository.
Action: Resolve the issue using the details provided in the message.
PCSF_10013 The file domains.infa was not defined in the system properties.
Cause: The system was unable to locate the domains.infa file required to
communicate with the domain.
Action: Internal error. Attempt to start Informatica Services again. If the problem
persists, contact Informatica Technical Support.
PCSF_10015 A message was being sent without specify either the domain name or host/
port.
Cause: The command requires that the domain name or host name and port number
be entered as a command option. No domain name or host and port number
was entered.
Action: Enter the domain name or host name and port number as a command option.
PCSF_10017 Failed to receive response from [<URL>] because: [<error text>].
Cause: The PowerCenter Client did not receive a response from a service at the URL.
Action: Correct the error indicated in the message.
354 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-370-320.jpg)
![PCSF_10019 Operation [<operation name>] of service [<service name>] failed because:
[<error text>].
Cause: The Service Manager attempted an operation. However, operation failed
because of an error.
Action: Correct the error indicated in the message and retry the operation.
PCSF_10020 Cannot write to file [<domain file name>].
Cause: The domains.infa file is read-only, or there is not enough disk space available.
Action: Make sure the domains.infa file is not read-only and that there is enough disk
space available.
PCSF_10024 Timed out while trying to connect to domain [<domain name>] to lookup
service [<service name>].
Cause: The PowerCenter Client could not connect the domain within the resilience
timeout period.
Action: Verify that the domain is running and reconnect to the domain. If the domain
is not running, ask the domain administrator to start PowerCenter Services.
PCSF_10025 Cannot parse message: [<error text>].
Cause: The Service Manager received a response with inconsistent message content.
As a result, the operation failed.
Action: Correct the error indicated in the message.
PCSF_10027 No gateway connectivity is found for domain [name].
Cause: The command line program was unable to find the domain specified in the
command.
Action: Verify that the domain exists and that the domain name was entered correctly.
PCSF_10028 Cannot respond to operation [<operation name>] of service [<service name>]:
[<error text>].
Cause: The Service Manager attempted an operation. However, the operation failed
because of an error.
Action: Correct the error indicated in the message and retry the operation.
PCSF_10039 Linked domain <linked domain name> must specify at least one gateway.
Cause: Validation for a linked domain failed as no gateways were specified.
Action: Make sure you specify at least one gateway.
PCSF_10040 Logging service [PurgeLogsOlderLimit] value <entered value> is invalid.
Cause: The Service Manager validation failed due to an invalid value.
Action: Ensure that all the values you enter are within valid ranges.
PCSF Messages 355](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-371-320.jpg)
![PCSF_10041 Logging Service [MaximumLogSize] value <entered value> is invalid.
Cause: The Service Manager validation failed due to an invalid value.
Action: Ensure that all the values you enter are within valid ranges.
PCSF_10042 Logging service [LogServiceDirectory] value <entered value> is invalid.
Cause: The Service Manager validation failed due to an invalid value.
Action: Ensure that all the values you enter are within valid ranges.
PCSF_10060 Value <value> exceeded maximum length <maximum length>.
Cause: A value length exceeds the maximum.
Action: Shorten the value to be less than the maximum length.
PCSF_10081 Cannot deserialize <node or domain> configuration file <metadata file name>.
Cause: The Service Manager has inconsistent data.
Action: Contact Informatica Technical Support.
PCSF_10083 Failed to open backup configuration file <metadata file name>.
Cause: The disk that stores the metadata file is not accessible.
Action: Verify that the metadata file is in an accessible location.
PCSF_10085 Failed to read the configuration file from <metadata file name> or <backup
metadata file name>.
Cause: The disk that stores the metadata file is not accessible.
Action: Verify that the metadata file is in an accessible location.
PCSF_10095 An unexpected token was encountered during deserialization.
Cause: Internal Error. An unexpected token was encountered while reading an object.
Action: If problem persists, contact Informatica Technical Support.
PCSF_10131 The license key was previously applied.
Cause: You tried to add an incremental key that has already been added.
Action: To enable additional options, use a different incremental key.
PCSF_10132 You cannot apply more than one original key to a license. To update an
existing license, select a license file with an incremental key.
Cause: Each license requires one original key. You cannot apply more than one
original key to the same license. You must use an incremental key to update an
existing license. You use an original key to create a new license.
Action: Apply the incremental key to the existing license to update the license.
or
356 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-372-320.jpg)
![Action: Create a new license using the original key.
PCSF_10133 The issue date for the original key must be earlier than the issue dates for the
incremental keys.
Cause: Each incremental key must be issued after the original key.
Action: Contact Informatica Technical Support to get a valid incremental key.
PCSF_10135 Validating license failed because cannot be read properly.
Cause: The license key file is unreadable.
Action: Contact Informatica Technical Support to get a new license key file.
PCSF_10136 License is invalid. The Licensing Service encountered an invalid attribute
value in the license.
Cause: The key provided was not validated as having proper encryption.
Action: Please acquire a new license key file from Technical Support.
PCSF_10137 License is invalid. The Licensing Service encountered an invalid value [begin
date value] for the Begin Date attribute.
Cause: The license is invalid. The Begin Date attribute encountered in the license file
is invalid.
Action: Contact Informatica Technical Support to get a valid license key file.
PCSF_10138 License is invalid. The Licensing Service encountered an invalid value [expiry
date value] for the Expiry Date attribute.
Cause: The Expiry Date attribute in the license file is invalid.
Action: Contact Informatica Technical Support to get a valid license key file.
PCSF_10139 License is invalid. The Licensing Service encountered an invalid value [issue
date value] for the Issue Date attribute.
Cause: The Issue Date attribute in the license file is invalid.
Action: Contact Informatica Technical Support to get a valid license key file.
PCSF_10140 Invalid number of CPUs <number of CPUs> encountered.
Cause: The CPUs attribute in the license file is invalid.
Action: Contact Informatica Technical Support to get a valid license key file.
PCSF_10141 License is invalid. The Licensing Service encountered an invalid value
<number of repositories> for the repositories attribute.
Cause: The Service Manager failed to validate the license because the number of
repositories is invalid.
Action: Contact Informatica Technical Support to get a valid license key file.
PCSF Messages 357](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-373-320.jpg)
![PCSF_10304 Cannot connect to URL [< URL >] to perform operation [<operation name>] of
service [<service name>].
Cause: A client or service attempted to connect to the URL to perform an operation.
However, the operation failed because the client or service could not connect
to the URL within the resilience timeout.
Action: Verify that the host name and port number for the URL and retry the
operation.
PCSF_10305 Cannot connect to gateway [<node address>] to look up service [<service
name>].
Cause: The PowerCenter component could not connect to the Service Manager on
the gateway node to look up a service within the resilience timeout for the
domain.
Action: Verify that the gateway node is running.
PCSF_10306 Operation [<operation name>] of service [<service name>] was interrupted.
Cause: The service could not complete the operation. This error can occur because
the Service Manager is in the process of shutting down.
Action: Restart the node.
PCSF_10322 The following error occurred while logging to Log Service: [<error text>].
Cause: The Log Manager cannot process log events because of the operating system
error shown. For example, the network file system may be unavailable.
Action: Fix the errors listed in the node.log file. The node.log file is located in the
servertomcatlogs directory.
PCSF_10325 Error threshold exceeded for number of failed log attempts. Disabling
guaranteed messaging.
Cause: Too many errors occurred while the Log Manager was processing log events.
Action: Fix the errors listed in the node.log file. The node.log file is located in the
servertomcatlogs directory.
PCSF_10326 The following error occurred while generating the guaranteed message file:
[<error text>].
Cause: An application service process could not create the Guaranteed Message
Delivery file because of the operating system error shown. For example, the
network file system may be unavailable.
Action: Try to fix the operating system error.
358 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-374-320.jpg)
![PCSF_10327 The following error occurred while writing to the guaranteed message file
[<file name>]: [<error text>].
Cause: An application service process could not write log events to the Guaranteed
Message Delivery file because of the operating system error shown. For
example, the network file system may be unavailable.
Action: Try to fix the operating system error.
PCSF_10336 Incremental key is of a different deployment type than the original key. To
update a license, use an incremental key that has same deployment type as
the original key that was used to create the license.
Cause: The incremental key has a different deployment type than the original key that
was used to create the license.
Action: Get an incremental license key from Informatica with the correct deployment
type.
PCSF_10337 Incremental key is for a different distributor than the original key. To update a
license, use an incremental key that has same distributor as the original key
that was used to create the license.
Cause: The incremental key is for a different distributor than the original key that was
used to create the license. The distributor is the organization that issued the
PowerCenter product.
Action: Get an incremental license key from Informatica with the correct distributor.
PCSF_10338 Incremental key is for a different PowerCenter edition than the original key. To
update a license, use an incremental key that has the same PowerCenter
edition as the original key that was used to create the license.
Cause: The incremental key is for a different PowerCenter edition than the original
key that was used to create the license.
Action: Get an incremental license key from Informatica with the correct PowerCenter
edition.
PCSF_10339 Incremental key has a different serial number than the original key. To update
a license, use an incremental key that has same serial number as the original
key that was used to create the license.
Cause: The incremental key uses a different serial number than the original key that
was used to create the license.
Action: Get an incremental license key from Informatica with the correct serial
number.
PCSF Messages 359](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-375-320.jpg)
![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.
Cause: The incremental key is for a different PowerCenter version than the original
key that was used to create the license.
Action: Get an incremental license key from Informatica with the correct PowerCenter
version.
PCSF_10341 Cannot create a license with an incremental key.
Cause: You tried to create a license using an incremental key.
Action: You must use an original key to create a license.
PCSF_10352 Upgrade configuration file [<file name>] is not found. Error: <error text>
Cause: You selected a single Repository Agent or PowerCenter Server configuration
file in the Upgrade Wizard, but the file you selected does not exist.
Action: Verify that the file exists and open the file again.
PCSF_10353 Error parsing upgrade configuration file: <error text>
Cause: The Upgrade Wizard encountered an error in a Repository Agent to
PowerCenter Server configuration file and could not validate the file.
Action: Correct the error indicated in the message and validate the file again.
PCSF_10354 Unable to identify the service type for configuration file [<file name>]. The file
might be an invalid configuration file.
Cause: The Upgrade Wizard could not determine if the configuration file is a
Repository Agent or PowerCenter Server configuration file. A Repository
Agent configuration file must contain the [RepositoryName] property. A
PowerCenter Server configuration file must contain the [ServerName]
property.
Action: Correct the contents of the configuration file and validate the file again. If you
created the PowerCenter Server configuration file with the pmserverexportreg
utility, the registry for the machine running the PowerCenter Server may
contain inconsistent data.
PCSF_10355 Configuration file [<file name>] is missing the required option(s) <option
names>.
Cause: The Upgrade Wizard could not validate the Repository Agent or PowerCenter
Server configuration file because the file is missing one or more of the required
properties.
Action: Add the required property or properties to the configuration file and validate
the file again.
360 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-376-320.jpg)
![PCSF_10356 File [<file name>] has extension other than .cfg. Upgrade only works with .cfg
file.
Cause: You placed a file in the global_repo, local_repo, or PCServer directory in the
server/upgrade/cfgfiles directory on a node. However, you can only upgrade
Repository Agent or PowerCenter configuration files with the .cfg extension.
The Upgrade Wizard cannot validate or upgrade the file.
Action: If the file is a Repository Agent or PowerCenter Server configuration file,
rename the file with the correct extension. If the file is not a configuration file,
remove the file from the upgrade directory or ignore the error.
PCSF_10357 File [<file name>] contains service [<service name>] which already exists in
domain [<domain name>].
Cause: The [RepositoryName] or [ServerName] property in the Repository Agent or
PowerCenter Server configuration file matches a Repository Service or
Integration Service name in the domain. As a result, the Upgrade Wizard
cannot upgrade the configuration file.
Action: If you already upgraded the Repository Agent or PowerCenter Server
configuration file, ignore the error and do not upgrade the configuration file.
If you want to upgrade the configuration file again, remove the service from
the domain and upgrade the file again.
PCSF_10358 Upgrade configuration files directory is not found on node <node name>.
Cause: You selected a node that contains Repository Agent and PowerCenter Server
configuration files to upgrade in the Upgrade Wizard. However, the server/
upgrade/cfgfiles directory does not exist on the node. The directory was
removed after installation.
Action: Create the directory and place Repository Agent and PowerCenter Server
configuration files in the appropriate global_repo, local_repo, and PCServer
directories under the server/upgrade/cfgfiles directory on the node, and then
validate the files again.
PCSF_10359 File [<file name>] contains service [<service name>] which already exists in
other configuration files selected for upgrade.
Cause: The value for the [RepositoryName] or [ServerName] property in the
Repository Agent or PowerCenter Server configuration file matches the same
property in another configuration file under the server/upgrade/cfgfiles
directory on the node. All configuration files you want to upgrade must
contain different values for the [RepositoryName] or [ServerName] properties.
There may be duplicate configuration files in the upgrade directory.
Action: Make sure the configuration file have unique values for the [RepositoryName]
or [ServerName] properties and validate the files again.
PCSF Messages 361](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-377-320.jpg)
![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>].
Cause: The PowerCenter Server configuration file contains an associated repository
that does not have a corresponding Repository Service in the domain. The
Upgrade Wizard requires information from the repository to upgrade the
PowerCenter Server. As a result, the Upgrade Wizard cannot upgrade the
Powercenter Server.
Action: Upgrade the Repository Agent for the associated repository before you
upgrade the PowerCenter Server.
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.
Cause: The PowerCenter Server configuration file contains an associated repository
that does not have a corresponding Repository Service in the domain or in any
of the Repository Agent configuration files you want to upgrade. The Upgrade
Wizard will not be able to upgrade the PowerCenter configuration file without
an upgraded Repository Service for the associated repository.
Action: Make sure the domain has an upgraded Repository Service for the associated
repository or that the upgrade directory has a Repository Agent configuration
file for the associated repository. Otherwise, remove the PowerCenter Server
configuration file from the upgrade directory.
PCSF_10374 Failed to persist [object] with error [message].
Cause: PowerCenter could not create the object because of the database error shown.
Action: Correct the database error.
or
Cause: The infasetup DefineDomain command was used to create a domain on IBM
DB2 and the primary tablespace default page size is too small.
Action: If the domain configuration database type is IBM DB2, make sure that the
primary tablespace default page size is at least 16K.
PCSF_10386 Unable to decrypt the password for option [<option name>]. It's possible that
the password is corrupted. Please use previous installation of PowerCenter
to re-generate the password and try again.
Cause: The Upgrade Wizard cannot decrypt the encrypted password in the
Repository Agent or PowerCenter Server configuration file.
Action: Use pmpasswd in the previous version of PowerCenter to encrypt the password.
Correct the password in the configuration file, revalidate the configuration
362 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-378-320.jpg)
![file, and upgrade the Repository Agent or PowerCenter Server configuration
file again.
PCSF_10389 The selected configuration file [<file name>] is a Repository Agent
configuration file. The PCServer directory should only contain PowerCenter
Server configuration files. Move [<file name>] to the global_repo or
local_repo directory.
Cause: You placed a Repository Agent configuration file in the PCServer directory
under the server/upgrade/cfgfiles directory on a node. However, the PCServer
directory can only contain PowerCenter Server configuration files.
Action: Move the Repository Agent to the global_repo or local_repo directory under
the server/upgrade/cfgfiles directory on the node and validate the
configuration files again.
PCSF_10391 Configuration file contains required option(s) <option names> with empty
value.
Cause: A property or properties in a Repository Agent or PowerCenter Server
configuration files does not have a corresponding value.
Action: Add a value for the property in the configuration file and validate and upgrade
the configuration file again.
PCSF_10392 <error text>
Cause: The Repository Agent or PowerCenter Server configuration contains an error
and the Upgrade Wizard cannot upgrade the configuration file.
Action: Correct the error indicated in the message and validate and upgrade the
configuration file again.
PCSF_10402 Unable to validate the log directory <shared disk> due to the error <error>.
Cause: The permissions of the shared disk was not validated.
Action: Verify the path and directory. The user that starts Informatica Services on the
node must have permissions to write to the directory.
PCSF_10404 The log directory [<shared directory>} cannot be created.
Cause: The shared directory cannot be created because it is not valid or user does not
have permission.
Action: Verify the path and directory. The user that starts Informatica Services on the
node must have permissions to write to the directory.
PCSF_10407 Cannot find server [<server name>] in repository [<repository name>]
Cause: The PowerCenter Server is not registered to the associated repository in the
PowerCenter Server configuration file.
PCSF Messages 363](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-379-320.jpg)
![Action: Register the PowerCenter Server to the associated repository in the previous
version of PowerCenter. Move the configuration file to the server/upgrade/
cfgfiles/PCServer directory on the node and validate and upgrade the
PowerCenter Server again.
PCSF_10408 Failed at line #<line number> because option is missing value assignment
Cause: The Repository Agent or PowerCenter Server configuration file contains a
property without an associated value at a specific line number.
Action: Correct the value for the property at the line number in the configuration file
and validate and upgrade the Repository Agent or PowerCenter Server
configuration file again.
PCSF_10410 The selected configuration file [<file name>] is a PowerCenter Server
configuration file. The global_repo or local_repo directory should only
contain Repository Agent configuration files. Move [<file name>] to the
PCServer directory.
Cause: You placed a PowerCenter Server configuration file in the global_repo or
local_repo directory under the server/upgrade/cfgfiles directory on a node.
However, the global_repo or local_repo directory can only contain Repository
Agent configuration files.
Action: Move the PowerCenter Server configuration file to the PCServer directory
under the server/upgrade/cfgfiles directory on the node and validate the
configuration files again.
PCSF_10414 <error text> Please 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.
Cause: The [RepositoryName] property in the Repository Agent contains a tab
character, a trailing space, or one of the following characters: ? " : < > * / | .
Action: Back up the repository, restore it using a name that does not contain these
characters, and the upgrade the Repository Agent configuration file again.
PCSF_10421 Error parsing upgrade configuration file at line #<line number>. The end
string */ for block comment must be at the end of the line.
Cause: In a Repository Agent or PowerCenter Server configuration file, the end block
comment string '*/' occurs in the middle of a line, but can only appear at the
end of a line.
Action: Correct the configuration file and place the end comment string at the end of
the line. Then validate and upgrade the configuration file again.
364 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-380-320.jpg)
![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.
Cause: You started a comment block that was not ended in a Repository Agent or
PowerCenter Server configuration file.
Action: Correct the configuration file and place the end comment string in the file.
Then validate and upgrade the configuration file again.
PCSF_10423 File [<file name>] is a Repository Agent configuration file. Choose a
PowerCenter Server configuration file or change the configuration file type.
Cause: In the Upgrade Wizard, you chose a Repository Agent configuration file, but
selected a PowerCenter Server file type.
Action: Choose a PowerCenter Server configuration file or change the file type.
PCSF_10424 File [<file name>] is a PowerCenter Server configuration file. Choose a
Repository Agent configuration file or change the configuration file type.
Cause: In the Upgrade Wizard, you chose a PowerCenter Server configuration file,
but selected a Repository Agent file type.
Action: Choose a Repository Agent configuration file or change the file type.
PCSF_10426 Cannot find server [<server name>] in repository [<repository name>].
Cause: The PowerCenter Server is not registered to the associated repository in the
PowerCenter Server configuration file.
Action: Register the PowerCenter Server to the associated repository in the previous
version of PowerCenter. Move the configuration file to the server/upgrade/
cfgfiles/PCServer directory on the node and validate and upgrade the
PowerCenter Server again.
PCSF_10427 Option has invalid value <invalid value>.
Cause: Option contains an invalid value.
Action: Use the default value.
PCSF_10428 Option number <invalid value> is in an invalid format.
Cause: A number option contained invalid numeric format.
Action: Use the default value.
PCSF_10429 Required option <option name> missing.
Cause: Domain metadata is invalid with missing required option.
Action: Back up the domain, correct the backup (XML) file, and restore the domain.
PCSF Messages 365](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-381-320.jpg)
![Action: Make sure the database is running.
PCSF_10443 CPU architecture <architecture name> is not supported.
Cause: The node is starting on an unsupported platform.
Action: Run PowerCenter only on supported platforms.
PCSF_10445 Option <option name> is greater than option <option name>.
Cause: A minimum option value is greater than a maximum option value.
Action: Make sure the minimum value is less than or equal to the maximum.
PCSF_10446 Option memory size <invalid value> must be blank or a number followed by
optional K or M.
Cause: A number option contained invalid memory size format.
Action: Enter a valid memory size format.
PCSF_46000 INFA_DOMAINS_FILE is not set in the environment variable.
Cause: You can use the environment variable INFA_DOMAINS_FILE to store the
domains.infa path. You will receive an error if the environment variable
INFA_DOMAINS_FILE is not set.
Action: Add the environment variable INFA_DOMAINS_FILE, and set the path to
the domains.infa file. By default, the domains.infa file resides in the
infa_home directory.
PCSF_46002 Failed to communicate with the server at <server address>.
Cause: The request exceeded the timeout period due to an invalid connection or
domain not running.
Action: Ping the domain using infacmd ping and provide the gateway address. If the
connection is invalid, infacmd ping adds or updates domains.infa file. If the
domain is not running, ask the domain administrator to start Informatica
Services.
PCSF_46003 Failed to understand the response [<response text>] from server at [<server
address>]: <error text>.
Cause: A PowerCenter component failed to understand the response from a
PowerCenter service due to an error.
Action: Correct the error indicated in the message.
PCSF_46006 Domain name is not specified.
Cause: The command line programs require the domain name, which you provide as
an option at the command prompt. If you incorrectly type this information,
you will receive an error.
PCSF Messages 367](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-383-320.jpg)
![Action: Verify that you typed the domain name at the command prompt correctly.
Optionally, you can store the domain name as the environment variable
INFA_DEFAULT_DOMAIN. If you have more than one domain, choose a
default domain.
PCSF_46007 No gateway connectivity is provided for domain [<domain name>].
Cause: The domains.infa file does not contain the information necessary to connect
to the domain or the domains.infa does not exist.
Action: Ping the domain using infacmd ping and provide the gateway address. If the
connection is invalid, infacmd ping adds or updates domains.infa. If the
domain is not running, ask the domain administrator to start Informatica
Services.
Action: If you attempted to connect to a repository with the PowerCenter Client,
remove the repository in the Navigator and add the repository again.
PCSF_46008 Failed to look up service.
Cause: The Service Manager on the gateway is not running, and cannot accept the
request.
Action: Use the infacmd ping to verify that the domain is running and the connection
parameters are configured correctly. If the domain is running, infacmd displays
the host name and port number of the domain. If the domain is stopped or
unavailable, ask the domain administrator to start Informatica Services.
Contact Informatica Technical Support if the domain is running and you
continue to receive an error.
PCSF_46009 Invalid type <object type> encountered. Failed to create an object instance.
Same as PCSF_46002.
PCSF_46010 Cannot parse message: <reason for error>
Cause: You specified the incorrect domain name, gateway host name, or port number
from a PowerCenter client application, such as pmcmd or the Designer.
Action: Verify that you use the correct gateway information. If the gateway
information is correct, and you continue to receive this error, contact
Informatica Technical Support.
or
Cause: The Domain Service could not parse the SOAP message received from a
remote client, such as an FTP server.
Action: Review the log for related messages to find out more information.
or
Action: Contact Informatica Technical Support.
368 Chapter 50: PCSF Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-384-320.jpg)
![REP Messages
REP_12001 Failed to log onto database server.
Cause: The Integration Service failed to connect to the database server. You may have
logged in incorrectly.
Action: Log in with the correct information. User names and passwords may be case-
sensitive.
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.
Cause: The Integration Service cannot locate a necessary SQL script file.
Action: In the win.ini file, make sure the HOME entry in the Informatica PowerMart
entry points to the directory where the SQL script is located. If the HOME
entry is correct, contact Informatica Technical Support.
REP_12014 An error occurred while accessing the repository.
Cause: The Repository Service encountered an error while accessing the repository.
Action: Check preceding messages to see the cause of the error. This error message may
be preceded by REP_51056.
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].
Cause: The Service Manager was unable to connect to a local repository from the
global repository.
Action: Verify that the local repository is registered with the global repository. Also,
verify that the Repository Services for both repositories are running. In
addition verify that the connectivity information for the local repository is up
to date.
REP_12022 Failed to connect to global repository [global repository name] in domain
[PowerCenter domain of global repository] from local repository [local
repository name] in [PowerCenter domain of local repository].
Cause: The Service Manager was unable to connect to the global repository from a
local repository.
Action: Verify that the local repository is registered with the global repository. Also,
verify that the Repository Services for both repositories are running. In
addition, verify that the connectivity information for the global repository is
up to date.
390 Chapter 55: REP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-406-320.jpg)
![REP_12033 The repository being accessed is incompatible with this version...
Cause: The repository version does not match the client and/or server version.
Action: If the repository is older, upgrade the repository. If the software is older,
upgrade the software.
REP_12119 A repository does not exist at the specified database connection.
Cause: The Integration Service failed to connect to the database. You may have logged
in incorrectly.
Action: Log in with the correct information. User names and passwords may be case
sensitive.
or
Cause: You do not have the appropriate database privilege to view repository tables.
Action: Have the database administrator review your database privileges.
REP_12122 Unable to unlock this folder. Please try again.
Cause: This is a database error.
Action: Check the server event or error log for related database error messages. If
necessary, consult the database manual for appropriate action.
REP_12123 Unable to delete this folder. Please try again.
Same as REP_12122.
REP_12124 Unable to delete this folder. The folder is in use by another user.
Cause: You tried to delete a folder while other users are logged in to the folder. Even if
there are no users connected, the folder could contain residual locks.
Action: Ask all users to close all client tools. Use the Repository Manager to view
locks. If necessary, remove old locks. Then perform the operation again.
Warning: Removing valid locks can cause repository inconsistencies.
REP_12164 Domain-related error: [error description].
Cause: The Service Manager could not complete the requested operation.
Action: Read the error description and make any necessary changes to the domain
connectivity. For more information, look up the cause and action for the error
code.
REP_12225 The value entered is not valid for memory attributes.
Cause: The value for the memory attribute is invalid.
Action: Enter a valid value. The value must be a non-negative integer, a non-negative
integer followed by KB, MB, or GB. Or, you can enter auto to allow the
Integration Service to determine the value at run time.
REP Messages 391](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-407-320.jpg)
![Action: Edit the XML file, and verify the DSQINSTNAME attribute matches the
SESSTRANSFORMATIONINST element name. Or, export the object again
and then import it.
REP_32203 Error: the number of partition <PARTITION name> is out of range [1-32] for
session transformation <SESSTRANSFORMATIONINST name> in session
<session name>.
Cause: The number of PARTITIONs under SESSTRANSFORMATIONINST is
invalid.
Action: Remove, as appropriate, the PARTITIONs from under the
SESSTRANSFORMATIONINST so that the number of PARTITIONs is less
than or equal to 32.
REP_32204 Error: building session <session name>.
Cause: The SESSION element or some of its sub-elements are invalid.
Action: View the Output window for more information. Export the object again and
then import it.
REP_32205 Error: Invalid DSQ <Source Qualifier transformation> of type
<DSQINSTTYPE> for the extension in session transformation instance
<SESSTRANSFORMATIONINST name>.
Cause: In the XML file, you specified a DSQINSTNAME and DSQINSTTYPE
attribute in a SESSIONEXTENSION element that references a non-existent
SESSTRANSFORMATIONINST element or a
SESSTRANSFORMATIONINST element that does not match the name and
type specified in the SESSIONEXTENSION element.
Action: Edit the XML file, and verify the DSQINSTNAME and DSQINSTTYPE
attributes match the SESSTRANSFORMATIONINST element name and
type. Or, export the object again and then import it.
REP_32207 Error: Invalid datatype for workflow variable <workflow variable name>
Cause: In the XML file, you specified an invalid DATATYPE attribute for the
WORKFLOWVARIABLE element.
Action: Edit the XML file, and specify a valid DATATYPE attribute for the
WORKFLOWVARIABLE element. Or, export the object again and then
import it.
REP_32208 Error: The extension of type <SESSIONEXTENSION type> and subtype
<SESSIONEXTENSION subtype> does not exist for session transformation
instance <SESSTRANSFORMATIONINST name>.
Cause: In the XML file, the TYPE and SUBTYPE attributes for the
SESSIONEXTENSION element are not supported for the
SESSTRANSFORMATIONINST element.
424 Chapter 55: REP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-440-320.jpg)
![REP_32225 Error: Invalid value <value> for <attribute in SCHEDULER element> in
Scheduler.
Cause: In the XML file, you specified a invalid value for the specified attribute in the
SCHEDULER element.
Action: Edit the XML file, and enter a valid value. Or, export the object again and
then import it.
REP_32292 Error: The transformation [transformation name] has no input groups.
Cause: You imported a Custom transformation defined with no input groups.
Action: Edit the XML file and define at least one input group. Or, export the object
and import it again.
REP_32293 Error: The transformation [transformation name] has no output groups.
Cause: You imported a Custom transformation defined with no output groups.
Action: Edit the XML file and define at least one output group. Or, export the object
and import it again.
REP_32294 Error: Group [group name] of the transformation [transformation name] is
both an input group and an output group.
Cause: You imported a Custom transformation with a group defined as both an
output and input group.
Action: Edit the XML file and define the group as either an input, output, or input/
output group. Or, export the object and import it again.
REP_32409 Session <name> has a log file name which is longer than 600 characters.
Session is not valid.
Cause: The session log file name is too long.
Action: On the session Properties tab, specify a session log file name of 600 characters
or fewer, including the file extension.
REP_32410 Session has a log file name which is longer than 600 characters. Session is
not valid.
Cause: The session log file name is too long.
Action: On the session Properties tab, specify a session log file name of 600 characters
or fewer, including the file extension.
REP_32413 Session <name> has a log directory name which is longer than 600
characters. Session is not valid.
Cause: The session log file directory name is too long.
Action: On the session Properties tab, specify a session log file directory name of 600
characters or fewer, including delimiters.
428 Chapter 55: REP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-444-320.jpg)
![REP_51048 Communication failed because of network errors. [System Error (errno =
<error number>): <error message>.] Please try connecting to the repository
again.
Cause: The PowerCenter Client or the Integration Service cannot connect to the
Repository Agent.
Action: Read the operating system error referenced in this message and make any
necessary changes. There might be network problems.
REP_51054 Internal error: Cannot allocate buffer of size <size> bytes to receive incoming
message. The system may be out of memory.
Cause: The system is low on resources.
Action: Free some system resources.
or
Cause: Internal error.
Action: Contact Informatica Technical Support.
REP_50156 Repository Agent connection failed. [Unable to read from client socket. Read
<number> bytes.]
Cause: The repository client application lost connectivity to the Repository Agent
process.
Action: Verify that the Repository Agent process is running. If the Repository Agent is
not running, restart it. Also, verify the repository database is running.
REP_51058 Unknown TCP/IP error. Please try connecting to the repository again.
Cause: The PowerCenter Client or the Integration Service cannot connect to the
Repository Agent due to a network problem. This might happen if the
Repository Agent machine was disconnected from the network, or if it lost
power.
Action: Verify the PowerCenter Client and Integration Service machines can connect
to the Repository Agent machine and try to connect again.
REP_51059 Repository Agent connection failed, another Repository Agent on host <host
name> port <port number> is already connected to this repository
<repository name>.
Cause: There is another Repository Agent process already running for the repository.
Action: Connect to the running Repository Agent, or wait for it to shut down before
connecting again.
REP_51071 Invalid name: You must specify a name.
Cause: You tried to create a metadata extension, but left the metadata extension name
blank.
436 Chapter 55: REP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-452-320.jpg)
![Action: Enter Relational: or Application: before the connection name for $Target
Connection Value on the Properties tab of the session properties.
REP_51444 โMessageSendBufferSizeโ value <message send buffer size> is invalid,
ignoring invalid value <message send buffer size>. Using system default
value.
Cause: The repository is on a Windows machine and the repository configuration file
specifies an invalid value for the MessageSendBufferSize parameter. The
Repository Agent uses the default message send buffer size.
Action: Edit the repository configuration file and verify the MessageSendBufferSize
size is greater than or equal to zero. When you specify zero, the Repository
Agent ignores the MessageSendBufferSize parameter.
REP_51445 โMessageReceiveBufferSizeโ value <message receive buffer size> is invalid,
ignoring invalid value <message receive buffer size>. Using system default
value.
Cause: The repository is on a Windows machine and the repository configuration file
specifies an invalid value for the MessageReceiveBufferSize parameter. The
Repository Agent uses the default message receive buffer size.
Action: Edit the repository configuration file and verify the MessageReceiveBufferSize
size is greater than or equal to zero. When you specify zero, the Repository
Agent ignores the MessageReceiveBufferSize parameter.
REP_51447 Repository agent connection failed. A repository request has timed out.
[System Error <error number>]. Please try connecting to the repository again.
Cause: The timeout values of the Repository Agent requests are too small. Or, you
made a request for a large repository object, which decreased network
performance.
Action: Increase the MessageReceiveTimeout value and MessageSendTimeout value
from the repository configuration.
or
Cause: Repository Agent timed out due to a slow network.
Action: Verify that the network is running properly.
or
Cause: The repository is stopped.
Action: Start the repository.
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>.
Cause: The value specified for Database Pool Expiry Timeout is invalid. For example,
it may be less than the minimum, or it may be a negative number or a letter.
442 Chapter 55: REP Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-458-320.jpg)
![RS Messages
RS_39037 Failed to start repository <repository name>.
Cause: The Repository Service failed to start a Repository Agent process for the
repository.
Action: Check preceding error messages in the Repository Service log file to see the
cause of the error. Verify that the repository database is running. Verify that
the repository configuration information is correct. Verify that another
Repository Service is not running a Repository Agent for the repository.
RS_39061 Cannot start repository <repository name> as it is being shut.
Cause: You cannot start the repository because it is in the process of being shut down.
Action: If you want to start the repository, wait until it is shut down before trying to
start it. Verify that the system administrator is not shutting down the
repository for maintenance purposes.
RS_39068 Failed to register LDR <local repository name> to GDR <global repository
name>.
Cause: The Repository Service could not register the local repository to the global
repository because you specified incorrect connectivity information for either
the local or global repository. Message RS_39090 or message RS_39091 may
precede this message.
Action: Check preceding messages for more information.
RS_39090 Cannot complete [Register] operation because of failure to start or connect to
repository [repository_name].
Cause: The Repository Service could not register a local repository to a global
repository because it could not start the Repository Agent process for one of
the repositories.
Action: Check preceding messages to see the cause of the error. Also, verify that the
local and global repository databases are running, and that you entered correct
connectivity information.
RS_39091 Cannot complete [UnRegister] operation because of failure to start or connect
to repository [repository_name].
Cause: The Repository Service could not unregister a local repository from a global
repository because it could not start the Repository Agent process for one of
the repositories.
Action: Check preceding error messages in the Repository Service log file to see the
cause of the error. Verify that the repository database is running. Verify that
the repository configuration information is correct. Verify that another
Repository Service is not running a Repository Agent for the repository.
460 Chapter 59: RS Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-476-320.jpg)
![RS_39092 Cannot promote repository [repository_name] to be a Global repository
because of failure to start or connect to the repository.
Cause: The Repository Service could not promote a local repository to a global
repository because it could not start a Repository Agent process for the
repository.
Action: Check preceding error messages in the Repository Service log file to see the
cause of the error. Verify that the repository database is running. Verify that
the repository configuration information is correct. Verify that another
Repository Service is not running a Repository Agent for the repository.
RS_39107 Cannot start repository <repository name> as it has been disabled.
Cause: The Repository Service cannot start the repository because it is disabled.
Action: Enable the repository. If you cannot enable it, a repository administrator may
have disabled the repository for maintenance.
RS_39109 Cannot enable repository <repository name> as it is not disabled.
Cause: The Repository Service cannot enable the repository because it is already
enabled.
Action: None.
RS_39120 ERROR: This product license does not allow global repositories. Only a
PowerCenter license does that.
Cause: You cannot create global repositories or promote a local repository to a global
repository with your current license.
Action: If you want to create global repositories, you need to purchase the Team-based
Development option.
RS_39121 ERROR: This product license does not allow registering or unregistering
repositories. Only a PowerCenter license does that.
Cause: You cannot register a local repository with or unregister a local repository from
a global repository with your current license.
Action: If you want to register or unregister repositories in a repository domain, you
need to purchase the Team-based Development option.
RS_39141 ERROR: Invalid characters in repository name <repository name>.
Cause: The repository name contains invalid characters.
Action: Create a new repository configuration. Include only valid characters when you
specify the repository name.
RS Messages 461](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-477-320.jpg)
![SDKS Messages
SDKS_38005 Couldn't load the library <library> for plug-in #<ID>.
Cause: PowerCenter could not load the specified library for the repository plug-in.
The library or dependent libraries may not be in the proper directory.
Action: Verify that the library and any dependent libraries are in the proper
directories.
SDKS_38006 Plug-in #<ID>'s interface version <version> is not compatible with SDK
interface version <version>.
Cause: The version of the plug-in and the SDK version are not compatible.
Action: Update the plug-in version to an SDK-compatible version.
SDKS_38007 Error occurred during <phase> <reader/writer> plug-in #<ID>.
Cause: There was an error during plug-in initialization or deinitialization.
Action: See additional error messages for more information.
SDKS_38200 Partition-level [SQ_MSMQ_SOURCE]: Plug-in #310000 failed in init().
Cause: Internal error.
Action: Contact Informatica Technical Support.
SDKS_38505 Plug-in #<ID>'s target <target> indicated that the error threshold
<number> has been reached.
Cause: The Integration Service reached the maximum number of errors for the
session. The session failed.
Action: If you want to increase the number of allowable errors per session, increase
the session error threshold.
SDKS_38605 Plug-in #<ID>'s target <target> encountered a transient failure.
Cause: The Integration Service was unable to write data to the target because of a
connection failure.
Action: Verify that a connection to the target can be established.
SDKS Messages 465](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-481-320.jpg)
![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.
Cause: During a transient failure, the Integration Service could not access the
$PMStorageDir to store the request for recovery.
Action: Verify that the Integration Service can access $PMStorageDir. If the directory
does not exist or cannot be written to, the request cannot be persisted.
SF_34130 Cannot get the storage files in directory <directory name>.
Cause: The storage directory does not exist or there are no storage files in this
directory.
Action: Make sure the $PMStorageDir directory path is set to directory that exists, and
you have proper write permissions to the directory.
SF_34132 Errors encountered while reading from storage files.
Cause: You do not have write permission, or the disk is full.
Action: Make sure you have write permission, and the disk has enough room for the
storage file.
SF_34134 Error in writing to storage file <file name>.
Cause: You do not have write permission, or the disk is full.
Action: Make sure you have write permission, and the disk has enough room for the
storage file.
SF_34135 Errors encountered while writing to storage files.
Cause: The Integration Service does not have write permission on the directory to
write the state of operations.
Action: Verify that the user configured to start Informatica Services has write
permission, and the disk has enough room for the storage file.
SF_34136 Error in removing storage file <file name>.
Cause: The storage file is in use, or you do not have write permissions on the storage
file.
Action: Make sure you have write permission, and the disk has enough room for the
storage file.
SF_34155 Child process [process ID] terminated due to spurious abort errno [error
number].
Cause: The Session or Command task exited unexpectedly and the machine running
the Integration Service process generated an error.
Action: Use the error number to determine the cause of the error. If it indicates an out-
of-memory error, increase the swap space or reduce the maximum processes
SF Messages 475](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-491-320.jpg)
![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].
Cause: The Integration Service could not allocate memory for the Sorter or Lookup
transformation because there is not enough available memory.
Action: Free memory resources or increase the swap space on the Integration Service
system. You can also reduce the cache size to match the amount of available
memory.
SORT_40090 There are only <amount of available memory> megabytes of <total memory>
available. Either increase the swap space or decrease the Cache Size in the
Transformation [transformation name].
Cause: You ran the session on a UNIX Integration Service and the necessary cache size
of the specified transformation exceeds the maximum memory allowed for
processes that run on the UNIX machine.
Action: Increase the memory limit for processes on the UNIX machine.
or
Same as SORT_40046.
SORT_40095 File or filesystem <file or file system name> could not be accessed.
Cause: The Integration Service could not access the specified file.
Action: Verify you have read permission for the specified file.
SORT_40096 Temp file <file name> could not be opened: <error message>.
Cause: The Integration Service could not open a temporary file for the Sorter
transformation.
Action: Verify the user who started the Integration Service has read, write, and execute
permissions for the Sorter transformation work directory.
SORT_40102 This sort requires at least <value> MB of memory.
Cause: You specified too small a value for the Sorter transformation cache size. The
Integration Service cannot perform the sort operation.
Action: Increase the Sorter transformation cache size.
SORT_40111 This sort has been cancelled.
Cause: The Integration Service cancelled the sort operation.
Action: Check preceding messages to see the cause of the error.
484 Chapter 64: SORT Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-500-320.jpg)
![SORT_40179 Insufficient space to map <amount of memory> MB of memory: <error
message>. Either increase the swap space or decrease the Cache Size in the
Transformation [transformation name].
Same as SORT_40046.
SORT_40189 The sort library could not create a thread.
Cause: The Integration Service system does not have enough resources to run the sort
operation.
Action: Free Integration Service system resources by closing applications. After you
free system resources, restart the workflow.
SORT_40304 This operation appears to need <value> MB of memory; excessive paging is
possible; continuing.
Cause: You specified a Sorter cache size above the minimum required cache size, but
the Sorter cache size is small compared to the size of the incoming data. The
Integration Service can proceed with the sort operation, but the session will
have decreased performance.
Action: To increase session performance, increase the Sorter transformation cache size.
SORT_40401 A fatal Sort error has occurred in function <function name>. Errno = <error
number>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
SORT_40406 In transformation [transformation name], an error has occurred [error
message].
Cause: The Integration Service encountered an error at the specified Sorter or Lookup
transformation.
Action: Read the error message displayed in this error message and other messages in
the session log for more information.
SORT_40407 In transformation [transformation name] in partition [partition number], an
error has occurred [error message].
Cause: The Integration Service encountered an error when it processed a row in the
specified partition and transformation.
Action: Read the error message displayed in this error message and other messages in
the session log for more information.
SORT_40409 Internal sorter error <error>.
Cause: Internal error.
Action: Contact Informatica Technical Support.
SORT Messages 485](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-501-320.jpg)
![SORT_40414 Error: Total row size [row size] in transformation [transformation name] is
more than the allowed maximum [8 MB].
Cause: The sum of all port sizes in the specified Sorter or Lookup transformation
exceeds 8 MB.
Action: Disconnect any port that you do not need in your mapping. Consider
redesigning the mapping to reduce the number of ports in the specified
transformation. Or, reduce the precision of large string or binary ports.
SORT_40415 Work directory <directory name> does not exist.
Cause: The directory name specified for the Sorter transformation work directory
does not exist.
Action: Verify the Work Directory option in the Sorter transformation properties
specifies an existing directory.
SORT_40416 Work directory <directory> does not have read/write/execute permission.
Cause: The user who started the Integration Service does not have read, write, and
execute permissions on the Sorter transformation work directory.
Action: Grant read, write, and execute permissions for the Sorter transformation work
directory to the user who starts the Integration Service.
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.
Cause: The Sorter transformation cache size is too large.
Action: Reduce the Sorter transformation cache size in the session properties.
486 Chapter 64: SORT Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-502-320.jpg)
![TE_7114 Error: Guaranteed Message Delivery does not allow a dynamic lookup cache
in the mapping.
Cause: The session contains a dynamic lookup cache. When you enable message
recovery for a session, you cannot use a dynamic lookup cache in the mapping.
Action: Use a static lookup cache in a mapping for the session.
or
Action: Do not use message recovery for the session. To remove message recovery for
the session, clear the Enable Recovery option in the session properties.
TE_7115 Error: The source configured for Guaranteed Message Delivery cannot be a
Joiner transformation master source.
Cause: The session contains a mapping with a JMS source that is a Joiner master
source. When you enable message recovery for the session, the source cannot
be the Joiner master source.
Action: Do not use message recovery for the session. To remove message recovery for
the session, clear the Enable Recovery option in the session properties.
TE_7116 Error: Guaranteed Message Delivery does not allow partition types other than
pass-through for each partitioning point.
Cause: You enabled message recovery and selected a partition type other than pass-
through for a partition point.
Action: When you enable message recovery, you must select pass-through partitioning
at all partition points in the session properties.
or
Action: Do not use message recovery for the session. To remove message recovery for
the session, clear the Enable Recovery option in the session properties.
TE_7117 Error: RealTime commit does not allow non-realtime SDK targets in the
mapping.
Cause: You configured a session using Real-time Flush Latency as a session condition.
However, the mapping contains an SDK target definition that you cannot use
with real-time sessions.
Action: Enter 0 for the Real-time Flush Latency session condition.
TE_7122 Error: Session is running in UDC mode; however, the target [target name] is
not receiving transactions from any upstream transformations.
Cause: You ran a user-defined commit session, but you did not connect the specified
target to an upstream effective transaction generator.
Action: Connect an effective transaction generator, such as a Transaction Control
transformation, to the target.
504 Chapter 68: TE Messages](https://image.slidesharecdn.com/pc811troubleshootingguide-130220121329-phpapp02/85/Pc-811-troubleshooting_guide-520-320.jpg)
Ad
More Related Content
What's hot (20)
Viewers also liked (6)
Ad
Similar to Pc 811 troubleshooting_guide (20)
Ad
Recently uploaded (20)
Pc 811 troubleshooting_guide
- 2. Informatica PowerCenter Troubleshooting Guide Version 8.1.1 January 2007 Copyright (c) 1998โ2007 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data Quality and Informatica Data Explorer are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies, 1999-2002. All rights reserved. Copyright ยฉ Sun Microsystems. All Rights Reserved. Copyright ยฉ RSA Security Inc. All Rights Reserved. Copyright ยฉ Ordinal Technology Corp. All Rights Reserved. Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved. Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, โas-isโ, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integrationยฎ is a registered trademark of Meta Integration Technology, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2005 The Apache Software Foundation. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved. The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler. The Curl license provided with this Software is Copyright 1996-2004, Daniel Stenberg, <[email protected]>. All Rights Reserved. The PCRE library included with this software is Copyright (c) 1997-2001 University of Cambridge Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel. The source for this library may be found at ftp://ftp.csx.cam.ac.uk/pub/software/programming/ pcre. InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved. Portions of the Software are Copyright (c) 1998-2005 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License, available at http://www.openldap.org/software/release/license.html. This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775 and other U.S. Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation โas isโ without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.
- 3. Table of Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . xv Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . xv Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Chapter 1: Client Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Business Components Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Data Profiling Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Java Transformation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerCenter Connect for IBM MQSeries Messages . . . . . . . . . . . . . . . . . . . 16 PowerCenter Connect for JMS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 PowerCenter Connect for PeopleSoft Messages . . . . . . . . . . . . . . . . . . . . . . 21 PowerCenter Connect for Salesforce.com Messages . . . . . . . . . . . . . . . . . . . 26 PowerCenter Connect for SAP NetWeaver BW Option Messages . . . . . . . . . 28 PowerCenter Connect for SAP NetWeaver mySAP Option Messages . . . . . . . 30 Importing Source Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Validating the Filter Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Validating the Join Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Validating SAP Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Creating ABAP Program Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Cleaning ABAP Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Generating and Installing ABAP Programs . . . . . . . . . . . . . . . . . . . . . . 37 Validating SAP Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Importing and Exporting SAP Mappings . . . . . . . . . . . . . . . . . . . . . . . 42 Working with IDocs Using ALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Data Migration Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Business Content Integration Messages . . . . . . . . . . . . . . . . . . . . . . . . . 46 PowerCenter Connect for Siebel Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 48 PowerCenter Connect for TIBCO Messages . . . . . . . . . . . . . . . . . . . . . . . . 52 iii
- 4. PowerCenter Connect for webMethods Messages . . . . . . . . . . . . . . . . . . . . . 55 PowerCenter Connect for Web Services Messages . . . . . . . . . . . . . . . . . . . . . 57 XML Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Chapter 2: Administration Console Error Messages . . . . . . . . . . . . . 63 Administration Console Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Chapter 3: ADV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 ADV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Chapter 4: ALERT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 ALERT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Chapter 5: ATHR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ATHR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 6: AUTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 AUTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Chapter 7: BR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 BR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Chapter 8: BTree Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 BTree Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Chapter 9: BW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 BW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Chapter 10: CFG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 CFG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Chapter 11: CMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 CMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 iv Table of Contents
- 5. Chapter 12: CMN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 CMN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Chapter 13: CNF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 CNF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Chapter 14: CNX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 CNX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Chapter 15: CSE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 CSE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Chapter 16: CTSDK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 CTSDK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Chapter 17: DBGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 DBGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Chapter 18: DCF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 DCF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Chapter 19: DMI Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 DMI Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Chapter 20: DOM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 DOM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Chapter 21: DP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 DP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Chapter 22: DS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 DS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Table of Contents v
- 6. Chapter 23: DSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 DSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Chapter 24: EP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 EP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Chapter 25: EXP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 EXP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Chapter 26: EXPFN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 EXPFN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Chapter 27: FEXP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 FEXP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Chapter 28: FR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 FR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Chapter 29: FTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 FTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Chapter 30: HIER Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 HIER Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Chapter 31: ICMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 ICMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Chapter 32: IDOC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 IDOC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Chapter 33: ISTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 ISTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 vi Table of Contents
- 7. Chapter 34: JMS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 JMS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Chapter 35: JSDK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 JSDK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Chapter 36: JTX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 JTX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Chapter 37: LB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 LB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Chapter 38: LDBG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 LDBG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Chapter 39: LGS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 LGS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Chapter 40: LIC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 LIC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Chapter 41: LM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 LM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Chapter 42: LMTGT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 LMTGT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Chapter 43: MQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 MQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Chapter 44: MXR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 MXR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Table of Contents vii
- 8. Chapter 45: NODE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 NODE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Chapter 46: NTSERV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 NTSERV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Chapter 47: OBJM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 OBJM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Chapter 48: ODL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 ODL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Chapter 49: OPT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 OPT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Chapter 50: PCSF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 PCSF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Chapter 51: PETL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 PETL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Chapter 52: PMF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 PMF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Chapter 53: PR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 PR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Chapter 54: REGEX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 REGEX Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Chapter 55: REP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 REP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 viii Table of Contents
- 9. Chapter 56: REP_CORE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 449 REP_CORE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Chapter 57: RFC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 RFC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 Chapter 58: RR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 RR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Chapter 59: RS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 RS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Chapter 60: SDK_ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 SDKC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 SDKS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 SDKXML Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Chapter 61: SEBL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 SEBL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 Chapter 62: SF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 SF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Chapter 63: SM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 SM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 Chapter 64: SORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483 SORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Chapter 65: SPC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 SPC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Chapter 66: SQL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 SQL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Table of Contents ix
- 10. Chapter 67: SR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 SR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Chapter 68: TE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 TE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 Chapter 69: TIB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 TIB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 Chapter 70: TM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 TM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Chapter 71: TT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 TT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Chapter 72: VAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 VAR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Chapter 73: WEBM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 WEBM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Chapter 74: WRT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 WRT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Chapter 75: WSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 WSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600 Chapter 76: WSH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603 WSH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604 Chapter 77: WSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611 WSP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612 x Table of Contents
- 11. Chapter 78: XML Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 XML Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 Chapter 79: XMLR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621 XMLR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 Chapter 80: XMLW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 XMLW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Table of Contents xi
- 12. xii Table of Contents
- 13. Preface Welcome to PowerCenter, the Informatica software product that delivers an open, scalable data integration solution addressing the complete life cycle for all data integration projects including data warehouses, data migration, data synchronization, and information hubs. PowerCenter combines the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely, usable, and efficient manner. The PowerCenter repository coordinates and drives a variety of core functions, including extracting, transforming, loading, and managing data. The Integration Service can extract large volumes of data from multiple platforms, handle complex transformations on the data, and support high-speed loads. PowerCenter can simplify and accelerate the process of building a comprehensive data warehouse from disparate data sources. xiii
- 14. About This Book The Troubleshooting Guide is written for all PowerCenter users. It contains troubleshooting information for all aspects of data warehouse development, including source analysis, transformation development, mapping development, and running sessions. This guide assumes you have knowledge about your operating systems, relational database concepts, and the interface requirements for your supporting applications. The material in this book is also available online. Document Conventions This guide uses the following formatting conventions: If you seeโฆ It meansโฆ italicized text The word or set of words are especially emphasized. boldfaced text Emphasized subjects. italicized monospaced text This is the variable name for a value you enter as part of an operating system command. This is generic text that should be replaced with user-supplied values. Note: The following paragraph provides additional facts. Tip: The following paragraph provides suggested uses. Warning: The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure. monospaced text This is a code example. bold monospaced text This is an operating system command you enter from a prompt to run a task. xiv Preface
- 15. Other Informatica Resources In addition to the product manuals, Informatica provides these other resources: โฆ Informatica Customer Portal โฆ Informatica web site โฆ Informatica Knowledge Base โฆ Informatica Technical Support Visiting Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community. Visiting the Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Visiting the Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. Obtaining Technical Support There are many ways to access Informatica Technical Support. You can contact a Technical Support Center by using the telephone numbers listed the following table, you can send email, or you can use the WebSupport Service. Use the following email addresses to contact Informatica Technical Support: โฆ [email protected] for technical inquiries โฆ [email protected] for general customer service requests Preface xv
- 16. WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com. North America / South America Europe / Middle East / Africa Asia / Australia Informatica Corporation Informatica Software Ltd. Informatica Business Solutions Headquarters 6 Waltham Park Pvt. Ltd. 100 Cardinal Way Waltham Road, White Waltham Diamond District Redwood City, California Maidenhead, Berkshire Tower B, 3rd Floor 94063 SL6 3TN 150 Airport Road United States United Kingdom Bangalore 560 008 India Toll Free Toll Free Toll Free 877 463 2435 00 800 4632 4357 Australia: 00 11 800 4632 4357 Singapore: 001 800 4632 4357 Standard Rate Standard Rate Standard Rate United States: 650 385 5800 Belgium: +32 15 281 702 India: +91 80 4112 5738 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445 xvi Preface
- 17. Chapter 1 Client Error Messages This chapter includes the following topics: โฆ Overview, 2 โฆ Business Components Messages, 3 โฆ Data Profiling Messages, 4 โฆ Java Transformation Messages, 11 โฆ PowerCenter Connect for IBM MQSeries Messages, 16 โฆ PowerCenter Connect for JMS Messages, 17 โฆ PowerCenter Connect for PeopleSoft Messages, 21 โฆ PowerCenter Connect for Salesforce.com Messages, 26 โฆ PowerCenter Connect for SAP NetWeaver BW Option Messages, 28 โฆ PowerCenter Connect for SAP NetWeaver mySAP Option Messages, 30 โฆ PowerCenter Connect for Siebel Messages, 48 โฆ PowerCenter Connect for TIBCO Messages, 52 โฆ PowerCenter Connect for webMethods Messages, 55 โฆ PowerCenter Connect for Web Services Messages, 57 โฆ XML Messages, 60 1
- 18. Overview The PowerCenter Client tools display messages in the status bar as you perform tasks such as opening or copying objects. The Designer displays error messages when you perform tasks that are not permitted, such as importing an invalid XML file. 2 Chapter 1: Client Error Messages
- 19. Business Components Messages Cannot copy/move directory: The destination directory is a subdirectory of the source directory. Cause: You tried to move a directory into a subdirectory. Action: Check the directory structure before moving directories. Cannot create a business component at the root level: please select a directory to use. Cause: You tried to put an object directly in a business components node. Action: You can put an object in a directory in the business components node, but not directly in the business components node. Only Sources and Mapplets can be placed in Business Components. Cause: You tried to place a transformation, cube, mapping, or target in a business components directory. Action: Business component directories support sources and mapplets only. <Object name> already exists in <directory name>. Cause: You tried to have two sources or mapplets with identical names in the same directory. Action: Sources or mapplets must have unique names in the same directory. Rename one of the sources or mapplets. Select a directory under Business Components. Cause: You tried to move an object into the business components node. Action: You can put an object in a directory in the business components node, but not directly in the business components node. The source folder <folder name> is not open. Use Repository - Open to open it. Cause: You dragged an object from one folder into a closed folder. Action: Open the source folder in the Navigator before you drag an object into the destination folder. This is not a valid move/copy. Cause: You tried to copy, move, drag, or drop an object that cannot be copied, moved, dragged, or dropped into a directory. Action: Check the directory structure before moving an object into it. Business Components Messages 3
- 20. Data Profiling Messages At least one join condition is needed. Cause: The Join Complexity function requires at least one join condition. Action: Edit the profile session to include at least one join condition in the Join Complexity function. At most, 6 join conditions are supported. Cause: The Join Complexity function supports up to six join conditions for each function. Action: If you need more join conditions, create another Join Complexity function using the same sources and enter the remaining join conditions. Cannot access session log file <log file name>. Cause: The log file might have been deleted. Action: Rerun the session to create a session log. Cannot regenerate mapping for the profile since it is running. Cause: The Designer cannot regenerate a mapping for this data profile because a session for the mapping is running. Action: Wait for the session to complete before you regenerate the profile mapping. Datatype 'number' of port <port name> and datatype 'character' of port <port name> are not the same. Cause: The Join Complexity Evaluation function requires the selected ports to have the same datatype. Action: Select ports with the same datatype for the Join Complexity Evaluation function. Datatype <datatype> of port <port name> and datatype <datatype> of domain lookup column <lookup column name> are not the same. Cause: The original column datatype and domain lookup column datatype do not match. Action: Select a port with a matching datatype to the domain lookup column datatype. Failed to add plug-in menu. Cause: Internal error. Action: Contact Informatica Technical Support. Failed to launch the Profile Wizard. Cause: Internal error. 4 Chapter 1: Client Error Messages
- 21. Action: Contact Informatica Technical Support. Failed to load the mapping. Cause: The mapping was deleted. Action: Regenerate the mapping or recreate the data profile. Failed to load the mapplet. Cause: The mapplet was deleted. Action: Recreate the data profile. Failed to retrieve connection info of any Integration Service. Cause: There is no Integration Service registered for the Data Profile repository. Action: Confirm that an Integration Service is registered and running for the Data Profile repository. Failed to retrieve Integration Service properties. Cause: The Integration Service is not responding. Action: Confirm that the Integration Service is running. Failed to validate Integration Service connection: <Integration Service name>. Cause: The selected Integration Service is not running. Action: Confirm that an Integration Service is running for the Data Profile repository. <File name> file is not a valid domain definition file. Reason: <error message>. Cause: The domain definition file that you specified for the List of Values domain is empty or contains a value longer than 200 characters. The domain definition file must contain entries of 200 or fewer characters. Action: Make sure that the domain definition file contains valid content before you import it. or Action: See the additional error message for more information. Intersource Structure Analysis is not allowed on more than <number> sources. Cause: The number of sources you selected for the function exceeds the limit for that function. Action: Edit the function to remove some sources. You can use mapplets in the profile to analyze additional sources. Mapping <mapping name> representing this profile is not valid. This profile cannot be run in interactive mode. Cause: The mapping is invalid because it has been modified. Data Profiling Messages 5
- 22. Action: Regenerate the profile mapping. or Action: If this is the first time that you generated the mapping, and you did not modify it, contact Informatica Technical Support. No Integration Service is registered in the repository to run this profile. Cause: An Integration Service is not configured to run against the data profiling repository. Action: Configure an Integration Service for the data profiling repository. No report is available for the profile <data profile>. Cause: The Integration Service has not generated a report for the selected data profile because a profile session has not been run for the data profile or the data profile has been edited. Action: You must run a profile session before you can view a report. No session log was created for this session. Cause: The session failed. Action: Check the workflow log or the Event Viewer for a message that indicates the reason for the failure. Correct the error and rerun the session. None of the columns from source <source name> can be used in Intersource Structure Analysis. Cause: The Intersource Structure Analysis function included a source with no columns that meet the defined values for allowed precision. Action: Edit the data profile to remove this source. or Action: Adjust the precision definitions to bring this source within the allowable range. Not connected to the warehouse. Cause: An incorrect ODBC database connection was specified for viewing reports. Action: Enter the correct ODBC database connection in the Profile Manager. Make sure that the target warehouse connection for viewing reports matches the relational database connection you specified when you ran the profile session. Referential Integrity Analysis is not valid for groups in the same source. Cause: More than one group from the same source was specified while adding or editing an Referential Integrity Analysis function. Action: Move groups back to the Available Sources field, leaving one group from each source in the Selected Sources field. 6 Chapter 1: Client Error Messages
- 23. Port <port name> cannot be used in a Join Complexity Evaluation function, because it is of the datatype โbinaryโ. Cause: A port with a Binary datatype was specified while adding or editing a Join Complexity Evaluation function. Action: Specify a port with a datatype other than Binary. Profile information does not exist in the target warehouse. Cause: The profile session did not run against the Data Profiling warehouse for which you are trying to view reports. or Cause: The profile was modified, and no profile session ran after the profile was modified. Action: Run a profile session against the Data Profiling warehouse for which you are trying to view reports. Profile was created successfully but mapping <mapping name> representing this profile is not valid. This profile cannot be run in interactive mode. Cause: Internal error. Action: Contact Informatica Technical Support. Profile was successfully created but no Integration Service is registered to run the profile. Cause: Data Profiling successfully created the profile but could not run the session because an Integration Service is not registered for the data profiling repository. Action: Register an Integration Service for the data profiling repository. Profile was updated successfully but mapping <mapping name> representing this profile is not valid. This profile cannot be run in interactive mode. Cause: Internal error. Action: Contact Informatica Technical Support. Profiling for this source is not supported. Cause: Internal error. Action: Contact Informatica Technical Support. Regular expression is invalid. Cause: An invalid regular expression was specified. Action: Make sure that the regular expression contains valid characters. Data Profiling Messages 7
- 24. Regular expression validation failed at character position <position>: <error message>. Cause: The Designer could not validate the regular expression. Action: Check the additional error message for more information. Some fields in source <source file name> group <group name> cannot be found. The source might be corrupt. Cause: The source has been modified since you last edited the data profile. Action: Create a new data profile for the modified source. Source <source name> cannot be chosen as a lookup source in column lookup domain validation functions as it has already been chosen as a non lookup source in other profiling function(s). Cause: The specified source in a column lookup function was used as a non-lookup source. The same source was also used in another column lookup function as a lookup source. Action: A source cannot be used as both a non-lookup and lookup source within the same function. Edit the data profile to use the indicated source as either a lookup or a non-lookup. Source <source name> has to be chosen as a lookup source in column lookup domain validation functions as it has already been chosen as a lookup source in other profiling function(s). Cause: The specified source in a column lookup function was used as a lookup source. The same source was also used in another column lookup function as a non- lookup source. Action: A source cannot be used as both a non-lookup and lookup source within the same function. Edit the data profile to use the indicated source as only a lookup source as already defined. Target warehouse does not exist. Cause: The Data Profiling warehouse connection that you specified for viewing reports does not match the relational database connection that you specified for the session target. Action: In the Profile Manager, modify the connection for viewing reports to match the relational database connection that you specified for the session target. or Cause: The database does not contain Data Profiling warehouse tables. Action: Rerun the Data Profiling warehouse script in the PowerCenter Client directory. Commit the SQL script after you run it. Rerun the profile session and try to view the report again. 8 Chapter 1: Client Error Messages
- 25. The domain used by the function is invalid. Please use a valid domain. Cause: The selected domain is invalid. A lookup column domain could be invalid if the name of the lookup column has been changed or deleted, or the lookup source is deleted. Action: Select a valid domain for the function. The mapping corresponding to this profile cannot be found. The repository might be corrupt. Cause: The mapping corresponding to this data profile might have been deleted. Action: Delete the data profile and create a new one. The profile was modified successfully but no Integration Service is registered to run the profile. Cause: Data Profiling successfully modified the data profile but could not run the session because an Integration Service is not configured to run against the data profiling repository. Action: Register an Integration Service for the data profiling repository. The session log editor could not be invoked. Cause: The path entered for the session log editor is invalid. Action: In the Profile Manager, enter a valid path for the session log editor. The target warehouse does not contain profile results for repository <repository name>. Cause: The Data Profiling warehouse connection specified for viewing reports does not match the relational database connection specified for the session target. Action: In the Profile Manager, modify the connection for viewing reports to match the relational database connection that you specified for the session target. There are no relational connections in this repository. Cause: The Connection Browser does not contain any relational database connections for the selected repository. Action: Import a relational database connection from another repository, or create a relational database connections in the selected repository. This is already used for repository <repository name>. Cause: The Data Profiling warehouse specified for the profile session has been used for a different repository. A Data Profiling warehouse can contain information for only one repository. Action: Specify the correct Data Profiling warehouse for the profile session that you are trying to run. This mapplet is not valid. Invalid mapplet cannot be profiled. Cause: The mapplet used to create an auto profile is invalid. Data Profiling Messages 9
- 26. Action: Open the mapplet in the Mapplet Designer, and click Mapplet > Validate to view the mapplet error. The error appears in the Output window. Correct the error and try to create the auto profile again. Unable to load the profile. Cause: The Designer cannot load the data profile. Action: See the additional error message for more information. You cannot profile a mapplet with transformations that generate transaction controls. Cause: A mapplet with a transformation that generates a transaction was used in creating a data profile. For example, you tried to create a data profile for a mapplet with a Custom transformation configured to generate a transaction. Action: Make sure the transformations in the mapping are not configured to generate transactions. 10 Chapter 1: Client Error Messages
- 27. Java Transformation Messages Java code snippets disabled for the transformation. Cause: The Java transformation is read-only. This can occur when you open a reusable transformation in the Mapping Designer. or Cause: The Designer cannot locate the JAR files for the Java Development Kit (JDK) or the Designer cannot locate javac.exe for compiling the Java code. Action: If the transformation is a reusable transformation, no action is required. Otherwise, contact Informatica Technical Support. You cannot edit the Java transformation - some common utilities are not available. Cause: An internal error occurred when loading common utilities for the Java Development Kit (JDK). As a result, you cannot edit the transformation. Action: Contact Informatica Technical Support. Unable to locate JDK in PowerCenter installation directory. Cause: The Designer cannot find the location of the Java Development Kit (JDK). Action: Verify that the JDK is located in the <PowerCenter installation directory>java. Unable to locate the PowerCenter Client installation directory. Cause: The plug-in for the Java transformation is unable to locate the installation directory for the PowerCenter Client. Action: Contact Informatica Technical Support. Unable to locate java.ini - cannot perform syntax highlighting. Cause: The Java transformation plug-in cannot locate java.ini in the PowerCenter Client installation directory. java.ini is required to perform syntax highlighting the Designer. Action: Make sure java.ini is located in the PowerCenter Client installation directory. Unable to create default input and output groups. Cause: An internal error occurred when the Designer attempted to create default input and output groups. Action: Contact Informatica Technical Support. Unable to save the Java code snippets to the repository. Cause: The Designer attempted to save the Java code snippets to the repository. However, an internal error occurred and the code snippets could not be saved to the repository. Java Transformation Messages 11
- 28. Action: Contact Informatica Technical Support. Unable to save byte code, byte code length, and CRC to the repository. Cause: After compiling the byte code for the Java transformation, the Designer attempted to save the byte code, byte code length, and cyclic redundancy check (CRC) for the transformation to the repository. However, an internal error occurred and the data could not be saved to the repository. Action: Contact Informatica Technical Support. Unable to retrieve Java code snippets from the repository. Cause: An internal error occurred when the Designer attempted to retrieve the Java code snippets for the Java transformation from the repository. Action: Contact Informatica Technical Support. Unable to read the byte code file. Cause: The Designer could not read the compiled byte code file for the transformation when opening the transformation. This error can occur when the byte code for the transformation in the repository contains inconsistencies. Action: Contact Informatica Technical Support. Unable to locate javakeywords.txt - cannot validate port names. Cause: The Java transformation plug-in cannot locate javakeywords.txt in the PowerCenter Client installation directory. javakeywords.txt is required to validate port names to make sure they do not conflict with reserved Java keywords. Action: Make sure javakeywords.txt is located in the PowerCenter Client installation directory. Compilation of Java code failed - transformation invalid. Cause: The compilation of the Java code for the transformation failed. As a result, the transformation is invalid. Action: Fix the errors in the Java code snippets for the transformation and compile the Java code again. Unable to open byte code file. Cause: The Designer generated the Java byte code file for the transformation, but was unable to open it. Action: Contact Informatica Technical Support. Unable to delete temporary file <name>. Cause: When you compile a Java transformation, the Designer creates a temporary Java source file in a temporary directory in the PowerCenter Client installation directory. The Java compiler compiles the Java source file, generates a byte 12 Chapter 1: Client Error Messages
- 29. code file, and deletes the temporary file and directory. The PowerCenter Client could not delete the temporary file. This error can occur if you move the temporary file or change it to a read-only file. Action: None. The compilation is not affected. Unable to create the Java source file. Cause: When you compile a Java transformation, the Designer creates a temporary Java source file in a temporary directory in the PowerCenter Client installation directory. The Java compiler compiles the Java source file, generates a byte code file, and deletes the temporary file and directory. The Designer could not create the Java source file for the generated code. This error can occur when the PowerCenter Client directory is read-only. Action: Make sure the PowerCenter Client directory is not read-only. Unable to delete temporary directory. Cause: When you compile a Java transformation, the Designer creates a temporary Java source file in a temporary directory in the PowerCenter Client installation directory. The Java compiler compiles the Java source file, generates a byte code file, and deletes the temporary file and directory. The Designer could not delete the temporary directory. Action: None. The compilation is not affected. No ports have been added. Cause: You clicked the Java Code tab in the Java transformation, but did not add any ports on the Ports tab. Action: None. You can enter Java code in the Java Code tab, and then add the ports in the Ports tab. Unable to generate Java code. Cause: An internal error occurred when the Designer attempted to generate the Java class for the transformation. The Designer generates the class code for the transformation before compiling the Java code for the transformation. Action: Contact Informatica Technical Support. Unable to compile Java code. Cause: An internal error occurred when the Designer called the Java compiler to compile the generated Java class for the transformation. Action: Contact Informatica Technical Support. Port name(s) conflict with Java reserved keyword. Cause: One or more of the ports in the Java transformation conflict with a reserved Java keyword. Action: Rename the port. Java Transformation Messages 13
- 30. A valid Java transformation can have only one input group and one output group. Cause: You added an additional input or output group to the Java transformation. A valid Java transformation can have only one input group and one output group. Action: In the Designer, delete any extra input groups or output groups. The default input group was deleted. Creating an input group. Cause: You removed the default input group for the Java transformation. A Java transformation must have at least one input group. As a result, the Designer created another input group. Action: None. The default output group was deleted. Creating an output group. Cause: You removed the default output group for the Java transformation. A Java transformation must have at least one output group. As a result, the Designer created another output group. Action: None. Unable to locate javac.exe, which is required for compiling Java code. Cause: The Designer could not locate javac.exe. The Designer requires javac.exe to compile the Java code for the transformation. Action: Make sure javac.exe is located in <PowerCenter installation directory>/java/ bin. Unable to locate the following JAR files : <JAR file name(s)>. Cause: The Java compiler requires the JAR files to compile the Java code for the transformation. However, the required JAR files are not located in the <PowerCenter Client installation directory> directory. Action: Make sure the JAR files are located in the correct directory. Unable to locate error in Java code. Cause: You attempted to locate the source of an error in the Output window on the Java Code tab. However, an internal error occurred and the Designer could not locate the error in the Java code for the transformation. Action: Contact Informatica Technical Support. Expression name <name> is a reserved Java keyword. Cause: The Java expression name is a reserved Java keyword. Action: Change the name for the Java expression. Expression name <name> is not a valid Java identifier. Cause: The name of the Java expression must be a valid Java identifier. A valid Java identifier can start with any alphanumeric character, number sign ($), or 14 Chapter 1: Client Error Messages
- 31. underscore (_). All other characters in the expression name must be alphanumeric. Action: Change the name for the Java expression. Parameter name <name> is a reserved Java keyword. Cause: The parameter name is a reserved Java keyword. Action: Change the name for the parameter. Unable to generate Java code for the expression. Cause: An internal error occurred when the Designer attempted to generate the code that invokes the expression. Action: Contact Informatica Technical Support. Java Transformation Messages 15
- 32. PowerCenter Connect for IBM MQSeries Messages Connections from a MQ source cannot be modified. Cause: You tried to modify the connections from the MQSeries source to the MQ Source Qualifier. Action: None. You cannot modify the connections from the MQSeries source to the MQ Source Qualifier. VSAM, XML, MQ sources connect to exactly one source qualifier transformation. Cause: You tried to connect an MQSeries, VSAM, or XML source definition to more than one Source Qualifier or Normalizer transformation. This action is not allowed. Action: Do not connect an MQSeries, VSAM, or XML source definition to more than one Source Qualifier or Normalizer transformation. Unable to delete links from an MQ source to an MQ Source Qualifier transformation. Cause: You tried to delete the link between the MQSeries source definition and the MQ Source Qualifier. Action: None. You cannot delete links between the MQSeries source definition and the MQ Source Qualifier. Unable to delete links from an MQ Source Qualifier transformation to an associated source qualifier transformation. Cause: You tried to delete the link between MQ Source Qualifier and the associated source qualifier. Action: To delete the link, remove the association between the MQ Source Qualifier and the associated source qualifier in the Edit Transformation dialog box of the MQ Source Qualifier. Cannot link to MsgId port. Cause: You tried to link a non-MsgId port to a MsgId port. Action: None. You cannot link a non-MsgId port to a MsgId port. 16 Chapter 1: Client Error Messages
- 33. PowerCenter Connect for JMS Messages The datatype assigned to the field <field name> is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the datatype for the specified field in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. Field <field name> is invalid because JMS source field does not allow โNOTNULL.โ Cause: You wanted to import a repository object that represents a JMS source definition from an XML file. However, the specified field in the XML file is set to Not Null. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. Header field <field name> is missing. Cause: You wanted to import a repository object that represents a JMS source definition from an XML file. However, you attempted to import an XML file that represents a JMS target. Action: If an XML file represents a JMS source definition, you must import it as a JMS source definition. or Cause: You wanted to import a repository object that represents a JMS target definition from an XML file. However, you attempted to import an XML file that represents a JMS source. Action: If an XML file represents a JMS target definition, you must import it as a JMS target definition. or Cause: A header field is missing. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The JMS body field name is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, a JMS body field name is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. PowerCenter Connect for JMS Messages 17
- 34. The JMS property field value is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the value for a JMS property field is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. Message body field is missing. Cause: You wanted to import a repository object that represents a JMS source or target definition in Bytes message, Text message, or Map message format from an XML file. However, the XML file contains no body fields. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object contains an invalid message body type. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid message body type. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object has an invalid field category <category>. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, there is an invalid category for a message field in the XML file. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object has an invalid header field. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid header field. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object has an invalid header field map value. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid map value for a header field. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. 18 Chapter 1: Client Error Messages
- 35. The object is a Bytes Message, but the body field name is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition in Bytes message format from an XML file. However, the body field name in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object is a Bytes Message, but the datatype for the body field is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition in Bytes message format from an XML file. However, the datatype for the body field in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object is a Text Message, but the body field name is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition in Text message format from an XML file. However, the body field name in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The object is a Text Message, but the datatype for the body field is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition in Text message format from an XML file. However, the datatype for the body field in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The precision is invalid. Cause: You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the precision for a field is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. Unknown error happened. Cause: The Designer encountered an unknown error. The Repository Service might not be running. Action: Make sure the Repository Service is running. If necessary, start the Repository Service. PowerCenter Connect for JMS Messages 19
- 36. or Cause: Your repository may contain inconsistencies. Action: Contact Informatica Technical Support. 20 Chapter 1: Client Error Messages
- 37. PowerCenter Connect for PeopleSoft Messages 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. Cause: You have defined this application source qualifier to connect a TO_EFFDT field from a source that has no primary keys or PeopleSoft keys defined. Action: Disconnect the link between the TO_EFFDT field in the source and the application source qualifier. Application source qualifier <application source qualifier name>: Error in preparing the query for effective date data extraction. Cause: You have defined this application source qualifier to extract current rows from an effective dated record that has no primary keys or PeopleSoft keys defined. Action: Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer. or Cause: You have specified an effective date join order in this application source qualifier, and at least one of the effective dated records has no primary keys or PeopleSoft keys defined. Action: Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer. Application source qualifier <application source qualifier name> has Effective Date Extract Join Order with invalid number of source names. This should be equal to the number of effective dated records in the DSQ. Cause: In the Effective Date Join Order field, you entered too few or too many PeopleSoft record names. Action: Edit the Effective Date Join Order field so the number of records you enter equals the number of records associated with the application source qualifier. Verify that you separated each PeopleSoft record name with a comma. Application source qualifier <application source qualifier name> has Effective Date Extract Join Order with invalid source names. Cause: In the Effective Date Join Order field, you typed a PeopleSoft record name that is not connected to the application source qualifier. Action: Edit the Effective Date Join Order field so that each PeopleSoft record name is spelled correctly. The record names you enter in the Effective Date Join Order field must match the records associated with the application source qualifier. Separate each record name with a comma. Application source qualifier <application source qualifier name> has invalid Extract Date. Cause: You entered the Extract Date in the wrong date format. PowerCenter Connect for PeopleSoft Messages 21
- 38. Action: Enter the Extract Date in the following format: MM/DD/YYYY HH24:MI:SS. Application source qualifier <application source qualifier name> has more than one tree attached. Cause: The listed application source qualifier is associated or connected to more than one imported PeopleSoft tree source definition. You can associate or connect only one imported tree source definition to a single application source qualifier. Action: Disconnect one of the tree source definitions from the application source qualifier. Or, remove one of the associated tree source definitions. To use more than one tree in a single mapping, create an application source qualifier for each tree you want to use. Use a Joiner transformation to join two related trees. Application source qualifier <application source qualifier name> has projected port with no inbound link. Cause: The listed application source qualifier has a connected output port, and the corresponding input port is not connected. Action: Connect the necessary input port or disconnect the connected output port. Application Source Qualifier <application source qualifier name> has tree and Extract Override. Cause: The listed application source qualifier uses a user-defined extract override for a PeopleSoft tree source definition. You cannot use extract overrides for tree sources. Action: Edit the application source qualifier to remove the extract override and save the mapping. Application source qualifier <application source qualifier name> has tree source definition with no PeopleSoft tree attributes assigned. The session will fail if you do not provide values for tree name and effective date at session level. Cause: This message is a warning. You used a created tree source definition in the mapping, but you did not import tree attributes into the source definition in the Mapping Designer. Action: Before you run a session using this mapping, you must import tree attributes into this created tree source definition. You can import the tree attributes in either the source definition in the Mapping Designer in the session properties. Application source qualifier <application source qualifier name> has vertical tree source definition <created tree source definition name> and other sources. For vertical tree flattening, tree cannot be joined with any source. Cause: You have connected a created tree source definition and other sources to this application source qualifier. You cannot connect other sources to an application source qualifier of a created tree source definition. 22 Chapter 1: Client Error Messages
- 39. Action: Use separate application source qualifiers for PeopleSoft sources and separate Source Qualifiers for relational sources. If you need to join a created tree source definition with other sources, use a Joiner transformation. Application source qualifier <application source qualifier name> has winter tree and other sources. Cause: The listed application source qualifier is connected to an imported winter tree source definition and other source definitions. You cannot join a winter tree with other PeopleSoft sources. Action: Disconnect either the winter tree or the other sources from the application source qualifier. Application source qualifier <application source qualifier name> is not a valid PeopleSoft SQ. Cause: The listed application source qualifier is invalid. Action: See related error messages for more information. Application Source Qualifier <application source qualifier name> sources are not related. Cause: You tried to connect or associate two unrelated sources in the listed application source qualifier. Action: Disconnect one of the unrelated sources. Or, remove one of the associated source definitions. You can only connect or associate related sources in an application source qualifier. Application source qualifier <application source qualifier name> tree is joined with non-detail source. Cause: You connected or associated an imported tree and a record in an application source qualifier, and the record is not the detail record for the tree. Action: You can connect or associate an imported tree with a non-detail record if the non-detail record is related to the detail record and you connect or associate the detail record with the application source qualifier. or Action: You can connect the tree and non-detail record to separate application source qualifiers and join them with a Joiner transformation. To determine which record provides detail data for an imported tree, open the tree source definition in the Mapping Designer and click on the Attributes tab. Error! <Source name> is not a valid PeopleSoft source. Cause: You tried to import a non-PeopleSoft object in the Import from PeopleSoft dialog box. Action: Import only PeopleSoft sources with the Import from PeopleSoft dialog box. or PowerCenter Connect for PeopleSoft Messages 23
- 40. Cause: In the Import from PeopleSoft dialog box, you entered a database user name that does not have SELECT permission on PeopleSoft metadata tables. Action: Use a different user name or have the PeopleSoft administrator grant the user name the necessary permissions. Error! Cannot find PeopleSoft metadata from source <source name>! Cause: In the Import from PeopleSoft dialog box, you entered a database user name that does not have SELECT permission on PeopleSoft metadata tables. Action: Use a different user name or have the PeopleSoft administrator grant the user the appropriate permissions. or Cause: The user name entered in the Import from PeopleSoft dialog box does not have permission to log in to the database. Action: Use a different user name or have the database administrator grant the user the appropriate permissions. Error! This version of PeopleSoft source <source name> is not supported! Cause: You tried to import a PeopleSoft source definition from a version of PeopleSoft that is not supported by this version of PowerCenter Connect for PeopleSoft. Action: Only import source definitions or extract source data from supported versions of PeopleSoft. Failed to log on to PeopleSoft database server. Cause: The Designer was unable to access the PeopleSoft system database server. The network or the database server might not be running properly. Action: Make sure the network and database are running before trying again. The language code <language code> specified is either invalid or not configured on the current PeopleSoft system. Cause: When importing a PeopleSoft source definition, you entered an invalid PeopleSoft language code. The code is either not a valid PeopleSoft language code or not configured on the PeopleSoft system you accessed. Action: Enter a PeopleSoft language code that is configured for the PeopleSoft system you want to access. The specified Language Code <language code> is either invalid or not configured on the current PeopleSoft System! Cause: The language code you entered in the Import from PeopleSoft dialog box is not a valid PeopleSoft language code or is not registered with the PeopleSoft system. Action: Enter a valid PeopleSoft language code. 24 Chapter 1: Client Error Messages
- 41. Warning: Application Source Qualifier transformation <application source qualifier name> has a larger number of sorted ports than projected output ports. Ignoring number of sorted ports. Cause: In an application source qualifier, the Number of Sorted Ports option on the Properties tab has a higher value than the number of connected output ports. Action: Either lower the Number of Sorted Ports value or increase the number of connected output ports in the application source qualifier. PowerCenter Connect for PeopleSoft Messages 25
- 42. PowerCenter Connect for Salesforce.com Messages DescribeGlobal failed. Error code: <error code> Reason: <error description>. Cause: The Designer could not retrieve a list of available objects for the data of the organization. Action: See the additional error message for more information. DescribeSObject <object name> failed. Error code: <error code> Reason: <error description>. Cause: The Designer could not retrieve the field list and object properties for the object. Action: See the additional error message for more information. Failed to add menu item for import from Salesforce.com. Cause: The Import from Salesforce.com menu item was not added to the Source Analyzer or the Target Designer tool in the Designer. Action: Shut down and restart the machine running the Designer. If the problem persists, contact Informatica Technical Support. Failed to create table. Reason: <error description>. Cause: The Designer could not create a source or target definition based on an object imported from Salesforce.com. Action: See the additional error message for more information. Login failed. Error code: <error code> Reason: <error description>. Cause: The Designer could not connect to Salesforce.com. Action: See the additional error message for more information. The Source <source name> is associated with more than one Source Qualifier. Cause: A source in the mapping is associated with multiple Application Source Qualifier transformations. Each Salesforce source definition must be associated with exactly one Application Source Qualifier transformation. Action: If a source definition is associated with multiple Application Source Qualifier transformations, remove the extra transformations and associate the source definition with a single Application Source Qualifier. The Source Qualifier <Application Source Qualifier name> has more than one PowerCenter Connect for Salesforce.com source definition associated with it. Cause: An Application Source Qualifier transformation in the mapping is associated with multiple source definitions. To extract data from multiple Salesforce 26 Chapter 1: Client Error Messages
- 43. sources, you must have an Application Source Qualifier for each source definition in the mapping. Action: Associate each source definition in the mapping with a single Application Source Qualifier transformation. PowerCenter Connect for Salesforce.com Messages 27
- 44. PowerCenter Connect for SAP NetWeaver BW Option Messages The Designer cannot import the selected objects. Cause: A transfer structure that is not an InfoSource was selected in the Import SAP BW Metadata dialog box. Only InfoSources can be imported. Action: Select InfoSources only and then click Add to Import List. Hostname <hostname> unknown. Cause: The SAP BW Service cannot connect to the host specified in the saprfc.ini file (as the GWHOST entry) and cannot connect to the BW system. This error originates in Common Program Interface-Communications (TCP/IP) on the local host. Action: Change the GWHOST entry in the saprfc.ini file to point to the host on which the BW system is running. The SAP BW system does not contain any activated InfoSources. Cause: The SAP BW system does not contain any activated InfoSources. InfoSources must be activated before they can be imported into PowerCenter. Action: In the SAP BW system, create and activate the InfoSources you want to import into PowerCenter. The Designer cannot import all of the selected items. <Number of items> items were selected. However, only <number of items> items were added to the import list. Cause: InfoSources that are not correctly created and activated in the SAP BW system were selected in the Import SAP BW Metadata dialog box. Action: In the SAP BW system, verify that the InfoSources you want to import into PowerCenter are properly created and activated. The Designer is not connected to the SAP BW server. Cause: In the Import SAP BW Metadata dialog box, Add to Import List was clicked before a connection was made to the SAP BW system. Action: Connect to the SAP BW system by entering the appropriate Connect to SAP values and clicking Connect. Select the InfoSources you want to import and click Add to Import List. Open saprfc.ini failed: No such file or directory. Cause: The Designer, Integration Service, or SAP BW Service could not locate the saprfc.ini file. Either the file does not exist or the RFC_INI environment variable is not set correctly. 28 Chapter 1: Client Error Messages
- 45. Action: Verify that the saprfc.ini file exists. Also verify that the RFC_INI environment variable is equal to the full path of the saprfc.ini file. You must stop and restart the Service Manager for the environment variables to take effect. Partner not reached (host <host name>, service <service number>). Cause: The SAP BW Service is unable to connect to the BW system specified as GWSERV in the saprfc.ini file. This error originates in Common Program Interface-Communications (TCP/IP) on the local host. Action: Change the GWSERV entry in the saprfc.ini file to point to the server on which the BW system is running. PowerCenter Connect for SAP NetWeaver BW Option Messages 29
- 46. PowerCenter Connect for SAP NetWeaver mySAP Option Messages Messages for PowerCenter Connect for SAP NetWeaver mySAP Option can originate from the PowerCenter Designer or from the SAP system. The messages that originate from SAP are often from RFC or CPI-C errors and display in conjunction with PowerCenter messages. They most often appear in PowerCenter Client dialog boxes and session logs. The Designer displays messages in the output window, status bar, or a message box. This section lists messages alphabetically for the following tasks: โฆ Importing source definitions โฆ Validating a filter condition โฆ Validating a join condition โฆ Validating SAP functions โฆ Creating ABAP program variables โฆ Cleaning ABAP programs โฆ Generating and installing ABAP programs โฆ Validating SAP mappings โฆ Importing and exporting SAP mappings โฆ Working with IDocs Using ALE โฆ Data migration messages โฆ Business content integration messages Importing Source Definitions A data source name must be selected or specified. Cause: You tried to connect to the SAP system without entering a connect string. Action: Select a connect string. Also verify that you have correctly configured the saprfc.ini file and set the RFC_INI environment variable. A password must be specified. Cause: You tried to connect to the SAP system without specifying a password. Action: Enter the user name and password. Then connect. A user name must be specified. Cause: You tried to connect to the SAP system without specifying a user name. Action: Enter the user name and password. Then connect. 30 Chapter 1: Client Error Messages
- 47. Cannot import selected object(s). Cause: Internal error. Action: Contact Informatica Technical Support. Error! Not all the selected items have been imported. <quantity> item(s) have been selected. However, only <quantity> item(s) were added to the import list. Cause: You tried to import a hierarchy definition that is empty. The hierarchy has no nodes. Action: Import a hierarchy definition that contains nodes. or Cause: You selected to import some SAP functions that you have already imported in the repository. Action: Select SAP functions that you have not already imported in the repository. IDoc filter supports only US-ASCII character set, showing all IDocs. Cause: You entered non-US-ASCII characters in the filter when you tried to import IDocs. Action: Use US-ASCII characters in filter conditions when you import IDocs. No item is selected to delete. Cause: You clicked the Delete button in the Import List with no definition selected. Action: Select the items you want to remove from the Import List and click Delete. The import list is empty. There is nothing to import. Cause: You clicked OK to import source definitions or SAP functions without first adding them to the Import List. Action: Select the definitions or SAP functions you want to import into the Designer and click Add to Import List. Then you can click OK to import the definitions or functions. There is no filter criterion specified. Continue connecting to SAP server without filter? Cause: You did not enter filter criterion before you connected to the SAP system to import sources. Action: You can enter filter criterion, or you can leave the filter field blank to instruct the SAP system to return all tables and hierarchies. Validating the Filter Condition <Filter condition>: <operator> is not a legal relational operator. Cause: The Designer does not recognize the relational operator used in the condition. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 31
- 48. Action: Use a valid operator and verify spacing around the operator. In the Application Source Qualifier <Application Source Qualifier name> the variable <variable name> is not defined. Cause: You tried to use an undefined ABAP program variable in a static filter condition. Action: Define the variable by clicking the Variables button in the ABAP Program Flow dialog box. In Application Source Qualifier <Application Source Qualifier name>, local variable <variable name> cannot be a part of the Dynamic Filter. Cause: You used an ABAP program variable in a dynamic filter condition. Action: You cannot use ABAP program variables in a dynamic filter condition. In filter expression for <Application Source Qualifier name>: <filter condition>; <value> following <operator> is not a constant or literal. Cause: The value on the right side of a filter condition must be a string or a numeric literal and it must be enclosed in single quotes. Action: Either change the filter condition to reflect proper syntax or remove the condition. In filter expression for <Application Source Qualifier name>: <filter condition>; <table-field> is a reference to a field not part of this source for which this filter expression is specified. Cause: The source table specified to the left of the condition is not part of the condition. Action: Edit the condition so that the source table specified to the left of the condition is also specified in the condition. or Cause: You have an invalid source table name or field name in the filter condition. Action: Verify all source table and field names. In filter expression for <Application Source Qualifier name>: <filter condition>; <token>: constant or literal has to follow an operator. Cause: You cannot have a space in an operator, such as < =. Action: Edit the filter expression and remove the space from the operator. <Source>: Source is not part of the Application SQ. Cause: The Designer does not recognize the source to the left of your filter condition. Action: Verify that the source to the left of the filter condition is a source in the Application Source Qualifier. 32 Chapter 1: Client Error Messages
- 49. You cannot specify filters for SAP Info Hierarchies. Cause: You created a filter condition using a hierarchy. Action: Remove the hierarchy from the filter condition. Validating the Join Condition <Hierarchy>: Source is an SAP InfoHierarchy and cannot be used in Join Override. Cause: You included a hierarchy in the join override in the Application Source Qualifier. Action: Remove the hierarchy from the join override condition. In Application Source Qualifier <Application Source Qualifier name> no join exists between tables <sourceX> and <sourceY>. Cause: You specified a join condition for two source tables but you did not specify the join type between the two tables. Action: Specify the join type between the two tables in the Join Type tab. In Join Condition expression for <Application Source Qualifier name>: <condition>; <table name> can only appear on the value side or right side of a relational operator for source table join order <table join order>. Cause: The qualifying table in the join condition is not selected before all other tables in the condition are selected. For example, with a join order S1, S2 you may have entered a join condition S1 = S2. Action: Make sure that the qualifying table appears in the join order before all other tables in the condition. For example, if the join order is S1, S2 the override must be S2 = S1. In join condition for <Application Source Qualifier name>: <join condition>; <token>: constant or literal has to follow an operator. Cause: You cannot have a space in an operator, such as < =. Action: Edit the join condition and remove the space from the operator. In join condition for <Application Source Qualifier name>: <join condition >; <sourceX> refers to a source table which follows <sourceY> in a source table join order of <join order>. Cause: The outer most table in the join condition is not used as the qualifying table. Action: Either change the order of the join condition or change the qualifying table so that the outer most table in the join condition is used as the qualifying table. For example, if the join order is S1, S2, S3, you can have a join override S3 = S3 = S2 = S1 or S2 = S2 = S1. No condition exists between tables <sourceX> and <sourceY>. Cause: You tried to join two source tables that have no key relationship. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 33
- 50. Action: Specify a key relationship between the two tables in the Join Condition tab. Source: <source name> is not part of the Source Join Order. All source(s) coming into the Application SQ have to be part of the Source Join Order. Cause: You entered a join order override in the Application Source Qualifier and did not include all source tables in the override condition. Action: Include all tables in the join order override. Source: <hierarchy> is an SAP InfoHierarchy and cannot be used in Source Join Order list. Cause: You included a hierarchy in the join order override in the Application Source Qualifier. Action: Remove the hierarchy from the join order override. Source: <source> is not part of the Source Join Order. Cause: The Designer does not recognize the sources for your source join order. Action: Verify that all the sources in your join order override are valid sources in your Application Source Qualifier. or Action: If you entered a join order override and join condition override, verify that you have placed a semi-colon between the order override and the condition override. Warning: Join Override for the first source <source> will be ignored. No syntax error detected. Cause: The qualifying table is not the outer most table of the join order. Action: Use the outer most table as the qualifying table in the join condition. For example, if the join order is S1, S2, the override must be S2 = S2 = S1. Validating SAP Functions All the table fields projected from the Application Source Qualifier must belong to a single table in the function <SAP function name>. Before projecting ports from this table <table name>, remove the ports projected from all other tables in this function. Cause: You tried to create output ports from two different table parameters. You can only create output ports from fields in the same table parameter. Action: Clear the SQ Port option for all other table parameters in the function before you create output ports from a table parameter. In the function <SAP function name> the parameter <function parameter name> is assigned the variable <variable name> that is not compatible in datatype, precision, or scale. Please specify a valid variable. Cause: You assigned a variable to a function parameter with an incompatible datatype, precision, or scale. 34 Chapter 1: Client Error Messages
- 51. Action: Assign a variable with compatible datatype, precision, or scale. In the function <SAP function name> the parameter <parameter name> is assigned the variable <variable name> that is not compatible either in definition or in datatype, precision, or scale. Please specify a valid variable. Cause: You assigned a variable to a function parameter with an incompatible definition, datatype, precision, or scale. Action: Assign a variable with compatible definition, datatype, precision, or scale. In the function <SAP function name> the parameter <parameter name> is a required parameter. It cannot be a None type. Please specify a value. Cause: You did not specify a type and value for a required parameter of the SAP function. Action: Specify the Type field for required parameters of the SAP function. In the function <SAP function name>, parameter <parameter name> is specified as a variable type but the value is None. Please assign a variable to this parameter. Cause: You did not specify a variable for a variable type function parameter. Action: Specify a variable for the function parameter. In the function <SAP function name>, parameter <parameter name> is specified as const type but the assigned value has length exceeding the type precision definition. Please specify a valid constant value. Cause: The value you specified for the export parameter is longer than the precision of the parameter. Action: Specify a value within the precision of the parameter. In the function <SAP function name> the parameter <parameter name> is specified as source field type but the value is missing. Please specify a valid source field. Cause: You specified that an SAP function parameter is a source field, but you did not specify a valid source field in the Value field of the parameter. Action: Specify a valid source field in the Value field of the function parameter. In the function <SAP function name> the parameter <parameter name> is specified as source field type with value <source name-field name> but the source <source name> must precede this function call. Cause: When you assigned a source field to a function parameter, you selected a source field from a source table that the ABAP program has not selected. Action: Select a source field from source tables above the SAP function in the ABAP program flow. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 35
- 52. In the function <SAP function name> the value of the variable <variable name> does not match with the function parameter <parameter name>. Cause: After you assigned a variable to the function parameter, you modified the variable value. The value of the variable no longer matches the function parameter. Action: Click the Variables button in the ABAP program flow and modify the variable value to match the function parameter. In the function <SAP function name> the parameter <parameter name> is specified as variable type but the assigned variable <variable name> is not defined. Cause: You removed the variable that you assigned to the function parameter. Action: Click the Variable button in the ABAP program flow and define the variable again. In the function <SAP function> the assigned field <field name> does not match with any field in the structure <structure name>. Please specify a valid field name. Cause: After you assigned a source field to a function parameter, you modified the source field name in the Source Analyzer. The source field name in the SAP function does not match the modified source field name. Action: Assign the modified source field to the function parameter in the ABAP Program Flow dialog box. Creating ABAP Program Variables Initial value specified is invalid. Please enter a valid integer. Cause: You specified an invalid initial value for the variable. Action: Specify a value that matches the datatype of the variable. Please enter a valid integer. Cause: You specified an invalid initial value for the variable. Action: Specify a valid integer for the initial value. Scale should be less than precision. Cause: The value you specified for scale is greater than the precision. Action: Specify a value less than the precision. Reserved keyword <key word> cannot be used. Cause: You specified a variable name that contains a reserved key word. Variable names cannot contain SAP datatype names, table, structure, or structure field names, or any ABAP key word. Action: Specify a variable name that does not contain a reserved key word. 36 Chapter 1: Client Error Messages
- 53. Variable definition is not valid. Cause: You specified an invalid variable definition, such as an invalid structure name. Action: Specify a valid variable definition. Cleaning ABAP Programs Message Box Messages There is no program information in the deleted folder. Cause: There are no orphan or shared ABAP programs in the deleted folder. Action: You do not need to clean ABAP program information in this folder. Output Window Messages Not connected to any SAP system. Please make the connection and choose uninstall. Cause: You did not connect to any SAP system. Action: Connect to an SAP system and choose uninstall again. Not connected to SAP system <system name>. Please make the connection and choose uninstall. Cause: You did not connect to the correct SAP system for the ABAP program. Action: Connect to the correct SAP system where the ABAP program exists. Generating and Installing ABAP Programs Message Box Messages Cannot generate further program name. Cause: The sequence number in YPMPRGSEQ has reached 99999. Action: Have the SAP administrator truncate YPMPRGSEQ and repopulate it using a different prefix. Cannot install ABAP program for mapping <mapping name>. Mapping <mapping name> is either modified or new. Please save the mapping first. Cause: You tried to generate or install an ABAP program for a mapping that is not saved in the repository. Action: Close the Generate and Install dialog box and click Repository > Save. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 37
- 54. Error obtaining program name from destination <connect string> for mapping <mapping name>. Cause: RFC error. Action: Contact your SAP administrator. Error opening selected ABAP file with associated file viewer or Notepad.exe. Cause: You do not have the file type associated with a viewer. Action: Associate the file type.ab4 with the Wordpad or Notepad viewer. In Application Source Qualifier <Application Source Qualifier name>, for ABAP join syntax, source <source name> cannot be outer joined multiple sources. Cause: You joined multiple sources using outer join. Action: Edit the ABAP program flow so that you only join two sources with outer join. LRAW field cannot be the first field in the source. Code generation for mapping <mapping name> failed. Cause: The first field in your source definition is an LRAW field. Action: Import the source definition from SAP again and verify that the LRAW field is the last field of the definition. LRAW field should be preceded by a field type of INT2. Code generation for mapping <mapping name> failed. Cause: You have an LRAW field in the source definition that is not directly preceded by an INT2 field. Action: Import the source definition from SAP again and verify that the LRAW field is preceded by an INT2 field. Mapping <mapping name> is invalid. Continue to install ABAP program for this mapping? Cause: You are installing an ABAP program for an invalid mapping. Action: Close the Generate and Install dialog box. Correct the source of errors in the mapping and save the repository. No Program Info has been selected to delete. Cause: You clicked Uninstall in the View Programs dialog box without any programs selected. Action: If you want to uninstall a program, select the program and click Uninstall. No rows found in table ZERPPRGSEQ for <program name> generation. Cause: SAP cannot assign sequence numbers to the generated programs because the SAP administrator did not run the YPMPRGSEQ program. Action: Have the SAP administrator run the YPMPRGSEQ program. 38 Chapter 1: Client Error Messages
- 55. Select a program mode first. Cause: Internal error. Action: Contact Informatica Technical Support. Output Window Messages Binary datatypes are not supported by code generation. Please do not project binary columns from an Application SQ. Code generation for mapping <mapping name> failed. Cause: You have connected binary datatype columns outside the Application Source Qualifier. Action: Make all binary datatype columns in the Application Source Qualifier input ports only. Do not connect them to other transformations or targets. Can not override existing program. Override option disabled for mapping <mapping name>. Cause: You cannot override the ABAP program name for an existing ABAP program. You can only override the program name if you are generating or installing an ABAP program for the first time. Action: Clear the Enable Override option or uninstall the existing ABAP program. Code generation for mapping <mapping name> failed. WARNING: No program was generated as mapping contains only SAP Info Hierarchies. Cause: You tried to generate an ABAP program for a mapping containing a hierarchy only. You do not need to generate an ABAP program for mappings with hierarchies only. Action: You can run the session without an ABAP program. Code generation is not allowed for a shortcut to a mapping. Code generation for mapping <mapping name> failed. Cause: You tried to generate or install an ABAP program from a shortcut mapping. Action: Generate the ABAP program from the original instance of the mapping, or make a copy of the mapping to your folder. Extraction of Info Hierarchies is not allowed in Stream Mode. Code Generation for mapping <mapping name> failed. Cause: You tried to generate a stream mode ABAP program for a mapping that contains a hierarchy and a table. Action: You can only use file mode for mappings that contain hierarchies and tables. Generate the ABAP program using file mode. For Application SQ <Application Source Qualifier name>, Select Single option is ignored as code generation mode is Exec SQL. Cause: You cannot use the Select Single option and generate the ABAP program using Exec SQL or ABAP join syntax. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 39
- 56. Action: Clear the Select Single option and generate the ABAP program again. For Application SQ <Application Source Qualifier name>, Select Single option is ignored as all the sources donโt have select single option in ABAP join mode. Cause: You cannot use the Select Single option and generate the ABAP program using Exec SQL or ABAP join syntax. Action: Clear the Select Single option and generate the ABAP program again. For Application SQ <Application Source Qualifier name>, Select Distinct option is ignored as all the sources donโt have Select Distinct option in ABAP join mode. Cause: You did not choose Select Distinct for all the sources connected to the Application Source Qualifier. Action: Choose Select Distinct for each source connected to the Application Source Qualifier. Generate the ABAP program again. For Application SQ <Application Source Qualifier name>, Select Distinct option is ignored as all the sources donโt have Select Distinct option in Exec SQL mode. Cause: You did not choose Select Distinct for all the sources connected to the Application Source Qualifier. Action: Choose Select Distinct for each source connected to the Application Source Qualifier. Generate the ABAP program again. In the Application Source Qualifier <Application Source Qualifier name>, as Exec SQL option is selected Outer Joins are not allowed. Cause: You joined sources with an outer join and selected to generate the ABAP program using exec SQL. Action: Choose inner join to generate the ABAP program with exec SQL. When you generate the ABAP program with exec SQL, the ABAP program joins sources using inner join. In Application Source Qualifier <Application Source Qualifier name>, as connected to SAP system 3.x, Outer Joins are not allowed. Cause: You selected the Outer Join option in the ABAP program flow and connected to an SAP 3.x system to generate the ABAP program. Action: In the Properties tab of the Application Source Qualifier, select Force Nested Loop or Exec SQL if you have only transparent tables in the mapping. Select Force Nested Loop if you have pool or cluster tables, or hierarchies and related detail tables. or Action: Connect to an SAP 4.x system when you generate the ABAP program. 40 Chapter 1: Client Error Messages
- 57. In Application Source Qualifier <Application Source Qualifier name>, as reverted to Nested Loop Outer Joins are not allowed. Cause: You selected the Outer Join option in the ABAP program flow when your mapping contains pool or cluster tables. Action: Select Force Nested Loop in the Properties tab in the Application Source Qualifier. Invalid entry. ABAP Program name should start with โYโ or โZ.โ Operation canceled. No code generated for mapping <mapping name>. Cause: You entered an ABAP program name that does not start with 'Y' or 'Z.' Action: Generate or install the ABAP program again and enter a program name that starts with 'Y' or 'Z.' Only variable ports are projected from an Application SQ. Code generation requires that at least one source field to be projected out. Cause: You have only variable ports in your Application Source Qualifier. Action: Create at least one output field in the Application Source Qualifier. The ABAP program name is empty. No code generated for mapping <mapping name>. Cause: You did not enter a program name. Action: Generate or install the ABAP program again and enter the program name in the ABAP Program Name dialog box. The source <source name> does not have a join condition with any of the sources above it. Cause: You did not select a table you want to join using ABAP join syntax. Action: Select the table you want to join in the Source(s) To Join To section of the ABAP Program Flow dialog box. There are no Application SQ's present in mapping <mapping name>. Cause: You tried to generate or install an ABAP program for a mapping that does not contain an Application Source Qualifier. Action: Select a mapping with an Application Source Qualifier. Then generate an ABAP program. There are no fields projected out from an Application SQ for which code generation is required in mapping <mapping name>. Cause: You tried to generate or install an ABAP program for a mapping with an Application Source Qualifier that is not connected to other transformations. Action: Connect the output ports in your Application Source Qualifier to another transformation or target instance. Then generate an ABAP program. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 41
- 58. There is no program generation information for program found in the repository. This program may be generated from other repository. Cause: You tried to install an ABAP program from an invalid file or a file that was generated from another repository. Action: Verify that you are installing a valid ABAP file and that you are connected to the repository from which the ABAP program was generated. You cannot have more than one Info Hierarchy coming into an Application SQ. Code generation for mapping <mapping name> failed. Cause: You tried to generate an ABAP program for a mapping that contains more than one hierarchy definition in a single Application Source Qualifier. Action: Edit the mapping to connect each hierarchy to an individual Application Source Qualifier. You can have one and only one IDoc coming into an Application SQ. Join with other IDoc is not supported. Code generation for mapping <mapping name> failed. Cause: You tried to join two IDocs in one Application Source Qualifier. Action: Remove other IDocs in the Application Source Qualifier. Validating SAP Mappings Code blocks, functions, and variables cannot exist in the program flow when a hierarchy is the only source in the Application Source Qualifier. Cause: You removed sources from the ABAP program flow so that the only source left in the program flow is a hierarchy. Action: Delete code blocks, functions, and variables from the ABAP Program Flow dialog box and validate the mapping again. Importing and Exporting SAP Mappings Exporting SAP Mappings Error: Missing source instance for program flow object. Cause: You deleted a source in the Source Analyzer. The mapping you want to export still uses that source. Action: Reimport the source in the Source Analyzer. Error: Missing function instance for program flow object. Cause: You deleted an SAP function used in the mapping. Action: Reimport the SAP function. 42 Chapter 1: Client Error Messages
- 59. Error: Missing SAP code block for program flow object. Cause: You deleted the code block used in the mapping. Action: Recreate the code block and add it to the ABAP program flow. SAP function is no longer in the repository. Cause: You deleted an SAP function used in an Application Source Qualifier. Action: Reimport the SAP function in the Source Analyzer. Importing SAP Mappings Error: Associated Application SQ instance is missing. Cause: You edited the XML file and changed the Application Source Qualifier name. Action: Check that there is a valid Application Source Qualifier name in the XML file. Or, re-export the SAP mapping and import it again. Error: Invalid datatype for SAP function parameter <parameter name>. Cause: You edited the XML file after exporting the SAP function and changed a datatype in the file. The datatype is no longer valid. Action: Make sure the datatype is a valid datatype. Or, re-export the SAP mapping and import it again. Error: Invalid datatype for SAP variable. Cause: You edited the XML file and changed the datatype for an ABAP program variable. Action: Check that you have valid datatypes in the XML file. Or, re-export the SAP mapping and import it again. Error: Missing SAP function information. Cause: You edited the XML file and changed information about SAP functions. Action: Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping and import it again. Error: No name for the imported SAP table parameter. Cause: You edited the XML file and deleted a name for the imported SAP table parameter. Action: Check that there are no empty object names in the XML file. Or, re-export the SAP mapping and import it again. Error: No name for the imported SAP function instance parameter field. Cause: You edited the XML file and deleted a function name or other function information. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 43
- 60. Action: Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping and import it again. Error: No name for the import SAP function instance parameter. Cause: You edited the XML file and deleted information about SAP functions. Action: Do not modify the SAP function information in the XML file. Or, re-export the SAP mapping and import it again. Error: No name for the import SAP table instance parameter. Cause: You edited the XML file and deleted a table instance. Action: Check that there are no empty object names. Or, re-export the SAP mapping and import it again. Error: No name for the imported SAP variable. Cause: You edited the XML file and deleted an ABAP program variable. Action: Check that there are no empty object names. Or, re-export the SAP mapping and import it again. Error: No name for the imported SAP code block. Cause: You edited the XML file and deleted the name for an ABAP code block. Action: Check that there are no empty object names. Or, re-export the SAP mapping and import it again. SAP program flow objectโs associated source instance is invalid. Cause: You edited the XML file and deleted a source instance name in the file. Action: Check that the XML file has a valid source instance name. Or, re-export the SAP mapping and import it again. Working with IDocs Using ALE BEGIN_CONTROL_RECORD not found. Need to get metadata for the control record. Cause: You tried to import an IDoc from file. However, the file does not contain the control record BEGIN_CONTROL_RECORD. Action: Select a different file to import. Error encountered while reading the IDoc metadata file. Cause: The Designer could not import IDoc metadata for an SAP/ALE IDoc Interpreter transformation or SAP/ALE IDoc Prepare transformation from the specified file. Action: Verify that your IDoc metadata is valid before you create an SAP/ALE IDoc Interpreter transformation or SAP/ALE IDoc Prepare transformation. 44 Chapter 1: Client Error Messages
- 61. Failed to import IDoc metadata from file. Cause: Internal error. Action: Contact Informatica Technical Support. File does not contain IDoc metadata. Cause: You tried to import an IDoc from file. However, the file does not contain IDoc metadata. Action: Select a different file to import. The SAP version is incorrect. Cause: You attempted to connect to an SAP system that PowerCenter does not support. Action: Connect to SAP version 3.x or later. The SAP code page <code page> is not compatible with the Designer's code page. Cause: The SAP code page and Designer code page are not compatible. Action: Connect to an SAP system with a code page that is compatible with the Designer code page. Unable to fetch IDoc. Cause: The Designer cannot retrieve the IDoc metadata from the SAP system. The metadata for the IDoc is not consistent Action: Validate the IDoc metadata. or Cause: SAP fetch error. Action: Contact your internal technical support. Data Migration Messages Error encountered while reading the DMI metadata file. Cause: The Designer could not import DMI metadata from the specified file. The DMI metadata may be invalid. Action: Verify that your DMI metadata is valid before you import a DMI file. Error fetching metadata for object. Cause: The metadata for a DMI Prepare transformation is inconsistent in the DMI file. Action: Correct the data in the DMI file. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 45
- 62. Failed to import DMI metadata from file. Cause: Internal error. Action: Contact Informatica Technical Support. File does not contain DMI metadata. Cause: You tried to import a DMI file that does not contain DMI metadata. Action: Select a different file to import. Found the tag <tag[s]> while expecting the tag <tag[s]>. Please use a valid DMI file. Cause: You attempted to import an invalid DMI file. Action: Import a valid DMI file. Business Content Integration Messages Error activating DataSource. Cause: There is an unknown error activating the SAP DataSource. Action: Check the DataSource in SAP. Error connecting to listener. Please start the listener before activating. Cause: You may not have started the listener workflow before activating the DataSource. Action: Start the listener workflow. Error fetching list of activated DataSources. Cause: There may be a problem communicating with SAP. Action: Reconnect to SAP and search for DataSources. Error getting destination for <SAP logical system>. Cause: The destination for the SAP logical system may be invalid. Action: Validate the destination for the SAP logical system. Error in getting registration information. Have you completed the registration? Cause: There is no logical system in SAP for business content integration. Action: Create a logical system for business content integration in SAP. The file <filename> cannot be opened for writing. Cause: The permissions on the BCI request file directory are set to read only. Action: Disable read only permissions on the BCI request file directory. 46 Chapter 1: Client Error Messages
- 63. Request file not found. Request file will be created. Cause: You attempted to revert to a request file that does not exist in the directory you specified. Action: Change the directory to the request file location. or Action: Create a new request file in the currently specified directory. No hierarchy catalog in the source system. Cause: While creating a processing mapping, you clicked Send Request before selecting a hierarchy DataSource in the Generate Mapping for BCI Wizard. Action: Select a hierarchy DataSource before clicking Send Request to send the request to the SAP system. Registration is not complete. Please complete the registration before continuing. Cause: There is no logical system in SAP for business content integration. Action: Create a logical system for business content integration in SAP. PowerCenter Connect for SAP NetWeaver mySAP Option Messages 47
- 64. PowerCenter Connect for Siebel Messages Application source qualifier <application source qualifier name> has business component and other sources. Cause: The listed application source qualifier is connected to a Siebel business component source definition and other source definitions. You cannot join a Siebel business component with other Siebel sources. Action: Use a separate application source qualifier for each Siebel source definition. Application source qualifier <application source qualifier name> has filter clause which uses one or more fields that were not selected. Cause: The listed application source qualifier has a filter clause which uses one or more fields that you did not select from the business component. Action: In the filter clause, only use the fields that you select from the business component. Application source qualifier <application source qualifier name> has join override clause which uses one or more fields that were not selected. Cause: The listed application source qualifier has a join override clause which uses one or more fields that you did not select from the business component. Action: In the join override clause, only use the fields that you select from the business component. Application source qualifier <application source qualifier name> has more than one business component attached. Cause: The listed application source qualifier is associated or connected to more than one Siebel business component source definition. You can associate or connect one business component source definition to a single application source qualifier. Action: Disconnect one of the business component source definitions from the application source qualifier or remove one of the associated business component source definitions from the mapping. or Action: To use more than one business component in a single mapping, create an application source qualifier for each business component you want to use. Use a Joiner transformation to join two related business components. Application source qualifier <application source qualifier name> has one or more calculated fields projected out. NULL data would be produced for such fields. Generate a mapplet for this business component before using calculated fields. Cause: An application source qualifier contains one or more fields with calculated expressions connected to a target or another transformation. You cannot 48 Chapter 1: Client Error Messages
- 65. connect Siebel business component fields with calculated expressions from an application source qualifier to a target or another transformation. Action: Disconnect any ports that connect fields with calculated expressions from the application source qualifier to the target or transformation. Generate a Siebel business component mapplet to interpret the calculated expressions in the business component. Connect the fields with calculated expressions from the application source qualifier to the Siebel business component mapplet. Application source qualifier <application source qualifier name> has partitions with key names that use one or more fields that were not selected. Cause: The listed application source qualifier has partitions with key names that use one or more fields that you did not select from the business component. Action: For key names in partitions, only use the fields that you select from the business component. Application source qualifier <application source qualifier name> sources are not related. Cause: You tried to connect or associate two unrelated table source definitions in the listed application source qualifier. You can only connect or associate related table source definitions in an application source qualifier. Action: Disconnect one of the unrelated sources. Or remove one of the associated source definitions. Warning: Application source qualifier transformation <application source qualifier name> has a larger number of sorted ports than projected output ports. Ignoring number of sorted ports. Cause: In the application source qualifier, the Number of Sorted Ports option on the Properties tab has a higher value than the number of connected output ports. Action: In the application source qualifier, use a lower value for the Sorted Ports option or increase the number of connected output ports. Error! Cannot find Siebel metadata from source <source name>. Cause: In the Import from Siebel dialog box, you entered a database user name that does not have SELECT permission on Siebel metadata tables. Action: Use a different user name or have the Siebel administrator grant the user name the necessary permissions. or Cause: You tried to import a non-Siebel object in the Import from Siebel dialog box. Action: Only import Siebel sources with the Import from Siebel dialog box. Error! This version of Siebel source <source name> is not supported! Cause: You tried to import a Siebel source definition from a version of Siebel that is not supported by this version of PowerCenter Connect for Siebel. PowerCenter Connect for Siebel Messages 49
- 66. Action: Only import source definitions or extract source data from supported versions of Siebel. Failed to log on to Siebel database server. Cause: The Designer was unable to access the Siebel system database server. The network or the database server might not be running properly. Action: Make sure the network and database are running before trying again. Invalid Siebel Metadata: Siebel Join <Join name> used by one or more projected fields is not found in the repository. Cause: The listed Siebel Join does not exist or is not found in the Siebel system. Action: Disconnect transformations and targets from any application source qualifier port that uses the listed Siebel Join. You can view the fields that use the listed Join on the Attributes tab of a business component in the Source Analyzer properties. Invalid Siebel Metadata: Siebel Link <Link name> used by one or more projected fields is not found in the repository. Cause: The listed Siebel Link does not exist or is not found in the Siebel system. Action: Disconnect transformations and targets from any application source qualifier port that uses the listed Siebel Link. You must query the database underlying the Siebel system for the Multi Value Links that use the listed Destination Link. You can view the fields that use these Multi Value Links on the Attributes tab of a business component in the Source Analyzer properties. Invalid Siebel Metadata: There is no physical column name for non-calculated field <field name>. Cause: You created a port in the Siebel business component that is not based on a database column. Action: Disconnect transformations and targets from any application source qualifier port that uses the listed port. or Action: Delete the listed Siebel business component port from the source definition. Search specification contains unsupported terms. Cause: Search specification contains expressions using PositionID, RepositoryID, LoginID, IfNull, Iif, or GetProfileAttr. Action: Siebel search specifications do not allow expression suing PositionID, RepositoryID, IfNull, Iif, or GetProfileAttr. Modify the search specifications. Search specification is invalid. Cause: All filed names in the search specification are not enclosed in brackets. Action: Enclose all field names in search specifications in brackets. 50 Chapter 1: Client Error Messages
- 67. Search specification contains non-projected fields. The search specification will not be processed. Cause: Search specification has a field that is part of the source but not connected in the mapping to an output port. Action: Project all fields that are part of the search specification. Search specification contains calculated fields. The search specification will not be processed. Cause: Search specification includes calculated fields. Action: Remove all calculated fields from specifications. Search specifications cannot include calculated fields. PowerCenter Connect for Siebel Messages 51
- 68. PowerCenter Connect for TIBCO Messages At least two fields have the same map value <map value>. Cause: You wanted to import a TIBCO source or target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Action: Import the TIBCO source or target definition from a new XML object. Attribute <attribute> has primitive datatype of <datatype>, which is not supported. Cause: This is an informational message. You connected to a TIB/Repository instance to display metadata to import a TIBCO source or target definition. The PowerCenter Designer did not display the specified attribute because it contains a datatype that PowerCenter does not support. Action: None. For a list of TIBCO datatypes that PowerCenter supports, see โTIBCO Datatype Referenceโ in the PowerCenter Connect for TIBCO User and Administrator Guide. Attributes <attribute> is ignored. Another sibling attribute with the same name already exists. Cause: This is an informational message. You connected to a TIB/Repository instance to display metadata to import a TIBCO source or target definition. The PowerCenter Designer ignored the specified attribute from the TIB/ Repository instance because the PowerCenter Designer found an identical attribute in the TIB/Repository instance. For example, the class ADDRESS in the TIB/Repository instance contained two attributes with the name STREET. The PowerCenter Designer displays only one of these attributes when you view the list of attributes in the Import TIBCO Metadata dialog box. Action: None. Conversion from TIBCO source <source> to TIBCO target failed: <error message>. Cause: You tried to drag the specified TIBCO source definition to the Target Designer. The source definition may contain both a subgroup and a field from the subgroup as columns in the source definition. This is not allowed for target definitions. Action: Remove one of the fields in the source definition before dragging it to the Target Designer. Corrupted TIBCO Repository. Can't retrieve any metadata. Cause: The TIB/Repository is corrupt. Action: Consult the TIBCO documentation for information about fixing the error. 52 Chapter 1: Client Error Messages
- 69. Field <field> has invalid map value <map value> based on the source/target's metadata. Cause: You wanted to import a TIBCO source or target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Action: Import the TIBCO source or target definition from a new XML object. The filter only allows % as the first or last character. Cause: You entered one or more wildcard characters in the filter condition for importing a TIBCO source or target definition from a TIB/Repository instance. However, at least one of the wildcard characters was not the first or last character of the string. For example, you entered A%A. Action: When you enter wildcard characters in a filter condition for importing a TIBCO source or target definition from a TIB/Repository instance, the wildcard characters must be the first and/or last character in the string. For example, you can enter %A, A%, or %AA%. For TIBCO targets, a non-header field cannot coexist with any of its direct/indirect parent groups in the TIBCO metadata tree. Cause: When editing a TIBCO target definition, you wanted to add a group from the TIBCO metadata tree as a column in the target definition. You also wanted to add fields from the group as columns in the target definition. This is not allowed. Action: If you want to add a group to a target definition, do not add any fields from the group to the target definition. Libraries related to TIBCO SDK metadata retrieval weren't appropriately installed. Cause: TIB/Adapter SDK might not be properly installed. Action: Verify that TIB/Adapter SDK is properly installed. Metadata for the TIBCO source/target is corrupt. Cause: The PowerCenter repository may contain inconsistencies. Action: Contact Informatica Technical Support. Metadata is invalid. Non-empty TIBCO source/target must have one metadata group. Cause: You wanted to import a TIBCO source or target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Action: Import the TIBCO source or target definition from a new XML object. The node can't be renamed. <error message>. Cause: You tried to rename a group or field in the TIBCO metadata tree. However, a column in the source or target definition already contains the group or field in its map value. For example, the TIBCO metadata tree contains the group PowerCenter Connect for TIBCO Messages 53
- 70. GROUP1. GROUP1 contains a field FIELD1. FIELD1 is already a column in the source definition. In the metadata tree, you want to change the name of GROUP1 to GROUP2. Because FIELD1 is already a column in the source definition, the change is not allowed. Action: To change the field or group name in the TIBCO metadata tree, remove any columns in the source or target definition that contain the group or field name in their map value. Then, you can edit the group or field in the metadata tree. The node <node> can't be removed. <error message>. Cause: You tried to delete a field from the TIBCO metadata tree. However, the field is already a column in the source or target definition. You cannot delete the field from the TIBCO metadata tree. Action: If you want to remove the field from the TIBCO metadata tree, remove the corresponding column from the source or target definition. Then, remove the field from the TIBCO metadata tree. PowerCenter Connect for TIBCO plugin metadata is not registered in the repository. Please open Repository Manager and register plugin metadata. Cause: You tried to import a TIBCO source or target definition. However, the PowerCenter Connect for TIBCO repository plug-in is not registered in the PowerCenter repository. Action: Register the PowerCenter Connect for TIBCO repository plug-in. Sender name header field is not applicable for target. Cause: You wanted to import a TIBCO target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Action: Import the TIBCO source or target definition from a new XML object. Unexpected error happened when trying to retrieve metadata from TIBCO Repository. Cause: Internal error. Action: Contact Informatica Technical Support. Sequence header field is not applicable for target. Cause: You wanted to import a TIBCO target definition from an XML object. However, the XML file is corrupt. You might have attempted to change the XML file. Action: Import the TIBCO source or target definition from a new XML object. 54 Chapter 1: Client Error Messages
- 71. PowerCenter Connect for webMethods Messages Conversion from the source to target failed. Cause: The Designer could not convert the source definition to a target definition. Action: See the additional error message for more information. Document type <document type name> contains field <field name>, which is of an unsupported datatype. Cause: You tried to import a document type as a webMethods source or target definition. However, the document type contains a field, which uses an unsupported datatype. As a result, the Designer could not import the source or target definition. Action: Make sure that any document types you want to import as webMethods source or target definitions contain fields that use datatypes that PowerCenter supports. Envelope field <field name> is invalid or uses the datatype <datatype>, which does not match the data for the field. Cause: You wanted to import a repository object that represents a webMethods source or target definition from an XML file. However, the datatype for an envelope field is invalid in the XML file. The XML file may have been modified. or Cause: The envelope field is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. Error from the webMethods Broker: <error message>. Cause: The Designer encountered an error from the webMethods Broker. Action: See the additional error message for more information. Failed to add a menu item. Cause: Internal error. Action: Contact Informatica Technical Support. Importing webMethods source from document type <document type name> failed. Cause: The Designer could not import the webMethods source definition. Action: See the additional error message for more information. Importing webMethods target from document type <document type name> failed. Cause: The Designer could not import the webMethods target definition. Action: See the additional error message for more information. PowerCenter Connect for webMethods Messages 55
- 72. Importing failed. PowerCenter Connect for webMethods was not installed correctly. Cause: The Designer could not import the source or target definition, because PowerCenter Connect for webMethods is not properly installed. Action: Reinstall PowerCenter Connect for webMethods. The Map attribute value for field <field name> is empty. Cause: You wanted to import a repository object that represents a webMethods source or target definition from an XML file. However, the Map attribute value for a field in the XML file is invalid. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. The Map attribute value <map value> for field <field name> already exists. Cause: You wanted to import a repository object that represents a webMethods source or target definition from an XML file. However, the Map attribute value for a field is duplicated. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. There should be exactly one group. Cause: You wanted to import a repository object that represents a webMethods source or target definition from an XML file. However, there is more than one group in the XML file. The XML file may have been modified. Action: Import the repository object from a new XML file. Avoid editing the XML file before importing. 56 Chapter 1: Client Error Messages
- 73. PowerCenter Connect for Web Services Messages Encountered a problem during SOAP request conversion (DOC to RPC): <error details>. Cause: The SOAP request for a web service source contains invalid or incomplete data. The <error details> specifies the invalid or missing data. Action: Modify the SOAP request in the Edit Tables dialog box. Envelope contains an element other than Header and Body. Cause: The SOAP request envelope contains an element other than Header and Body. Action: Reimport the web service operation. Invalid SOAP Request. Body cannot have more than one operation. Cause: The SOAP request contains a request for more than one web service operation. Action: Reimport the web service operation and run the session again. or Action: Use a third-party SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. Either body or header or both are missing. Cause: The SOAP request contains elements that the SOAP server does not recognize. Action: Reimport the web service operation and run the session again. or Action: Use a third-party SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. Element <element name> does not exist. Cause: The SOAP request is missing an element. Action: Reimport the web service operation and run the session again. or Action: Use a SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. Failed to process at <element name>. Cause: The SOAP request contains an invalid element. Action: Reimport the web service operation and run the session again. or PowerCenter Connect for Web Services Messages 57
- 74. Action: Use a third-party SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. Operation cannot be found. Cause: The SOAP request does not specify a web service operation. Action: Use PowerCenter Connect for Web Services to reimport the web service operation and run the session again. or Action: Use a SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. The SOAP Operation parameters in the request are inconsistent with the WSDL file. Cause: The SOAP request contains parameters for the web service operation that you want to import that the WSDL file does not describe. Action: Use PowerCenter Connect for Web Services to reimport the web service operation and run the session again. or Action: Use a SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. Invalid SOAP Request. The SOAP request cannot be empty. Cause: The SOAP request does not contain any elements. Action: Use PowerCenter Connect for Web Services to reimport the web service operation and run the session again. or Action: Use a SOAP development tool to generate a SOAP request from the WSDL file. You can replace the current SOAP request with the one that you generate. The child element <element> cannot be found or is invalid. Cause: The SOAP request is missing a child element, or it contains an invalid child element. Action: Reimport the web service operation. The envelope cannot be found. Cause: The SOAP request does not contain an envelope element. Action: Reimport the web service operation. The namespace for prefix <prefix> cannot be found. Cause: The SOAP request contains an invalid namespace. 58 Chapter 1: Client Error Messages
- 75. Action: Reimport the web service operation. The operation you selected contains multiple namespaces - which is not supported. Please select another operation. Cause: You tried to import a web service operation from a WSDL file that specifies RPC encoding and a namespace that differs from the target namespace. If the WSDL file specifies RPC encoding, the namespace that the SOAP body specifies must match the target namespace. Action: Choose another web service operation to import. The part <part> for message <message> cannot be found or is invalid. Cause: The SOAP request contains an invalid part. Action: Reimport the web service operation. The prefix for namespace <namespace> cannot be found. Cause: The SOAP request contains an invalid prefix. Action: Reimport the web service operation. PowerCenter Connect for Web Services Messages 59
- 76. XML Messages Cannot change cardinality! The selected cardinality will cause groups <group names> to be invalid. Cause: You tried to change the cardinality of an element that invalidates the group. Action: You cannot change the cardinality of an element if it violates the structure defined in the associated DTD or XML schema. <Column name> cannot be pivoted since it is a key column. Cause: You tried to pivot a column designated as a primary key. Action: Select another column to pivot. You cannot pivot a column that is designated as a primary key. Column cannot be added since it will make the group invalid. If you add this element/attribute, the multiple occurring parent for this group will move down to <column name>. Remove the primary key <column name> before adding this element/attribute. Cause: You tried to add a column to the group that can turn the primary key in the group into a multiple-occurring column and invalidate the group. Action: Remove the primary key before adding the column. When you have completed modifying your group, set an appropriate column as a key. Column cannot be pivoted. All columns under the same multiple occurring parent should be either pivoted or unpivoted. Column <column name> is pivoted while column <column name> is not. Cause: You have a pivoted and an unpivoted column under the same multiple occurring parent. Action: This is a warning. If you pivot an element, you must also pivot all its sibling elements included in the group. You may get this warning if you are pivoting several elements or attributes in a group. You can proceed with the action if you are sure you want to pivot the element or attribute. Column cannot be unpivoted. All columns under the same multiple occurring parent should be either pivoted or unpivoted. Column <column name> and column <column name> are pivoted. Cause: You have a pivoted and an unpivoted column under the same multiple occurring parent. Action: This is a warning. You may get this warning if you are pivoting several elements or attributes in a group. You can proceed with the action if you are sure you want to pivot the element or attribute. Denormalized group cannot be created since XML Element/Attribute <column name> has a many to many relationship with XML Element/Attribute <column name>. Cause: You have at least two multiple-occurring element in the group with a many-to- many relationship. 60 Chapter 1: Client Error Messages
- 77. Action: You cannot put more than one multiple-occurring element with a many-to- many relationship in the same group. The multiple-occurring elements in a denormalized group must have a one-to-many relationship. Element/Attribute <element or attribute name> occurs only once and cannot be pivoted. Cause: You tried to pivot an element that occurs only once. Action: This is a warning. It is not necessary to pivot a column that occurs only once. You can proceed with the action if you are sure you want to pivot the column. Group <group name> cannot be related to group <group name>. Related groups should be under the same XML tree branch. Cause: You tried to set a foreign key to relate to the primary key of a group that is lower on the parent chain than the current group. Action: Relate to another primary key. You can only set a foreign key to relate to the primary key of a group that is higher in the parent chain than the current group. A key <column name> already exists at this level. <column name> has a one-one correspondence with <column name>. Cause: You tried to add a key to a hierarchy level that already has a key. Action: You cannot have more than one key for one hierarchy level. Only leaf elements can be pivoted. <column name> refers to a non-leaf element <element name> and cannot be pivoted. Cause: You tried to pivot a column that points to an element that is not a leaf element. Action: Select another column to pivot. You can pivot only attributes and leaf elements. Source file name has to be less than 80 characters long for DBD <file name>. Cause: You changed the XML file so that the DBD FILENAME attribute is greater or equal to 80 characters. Action: Make sure the FILENAME attribute is less than 80 characters. The XML file has fewer elements than the pivot value specified. Element <element name> appears only <number> times in the XML file. Cause: The pivot value you set is larger than the number of times the element appears in the XML file you are importing from. Action: This is a warning. You can proceed with the action if you know that the pivot value will match the number of times the element appears in the source XML file when you run the session. XML Messages 61
- 78. 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. Cause: You have a pivoted and an unpivoted column in one group pointing to the same element. Action: This is a warning. You may get this warning if you are pivoting the same element into several columns in a group. You can proceed with the action if you are sure you want to pivot the column. You cannot have two multiple occurring elements in the same group. XML Element/Attribute <column name> has a many to many relationship with XML Element/Attribute <column name>. Cause: You have at least two multiple-occurring elements in the group with a many- to-many relationship. Action: You cannot put more than one multiple-occurring elements with a many-to- many relationship in the same group. The multiple-occurring elements in a denormalized group must have a one-to-many relationship. A reference port can be created only in the XML root group. Cause: A non-root group in an XML Generator transformation contains a reference port. Action: Remove the invalid reference port. Only one reference port can reference a pass-through port in an XML Generator transformation. Cause: More than one reference port is referencing the same pass-through port. Action: Remove the duplicate reference ports. The XML metadata is invalid. Cause: The XML definition contains inconsistencies. Action: The XML definition is unusable. You must recreate it. 62 Chapter 1: Client Error Messages
- 79. Chapter 2 Administration Console Error Messages This chapter includes the following topic: โฆ Administration Console Error Messages, 64 Messages listed alphabetically. 63
- 80. Administration Console Error Messages Correct the validation errors in <field name> and try the update again. [error description]. Cause: A validation error occurs when data cannot be validated for some reason. For example, if you enter text into a field that requires an integer, the data cannot be validated because it is the wrong type of data. Action: Read the error description and make any necessary changes. For example, if the error description indicates that an integer value is required in the field, enter an integer value instead of a text value. For more information, look up the cause and action for the error code. The Domain Service could not disable the process due to the following error: [error description]. Cause: The Service Manager encountered a problem while disabling the service process. The service process may have been starting up when you attempted to enable it. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. The Domain Service could not disable the service due to the following error: [error description]. Cause: The Service Manager encountered a problem while disabling the service. The service may have already been disabled, or it may have been in the process of starting up. Action: Read the error description and make any necessary changes. For example, if the service was in the process of being enabled when you attempted to disable it, wait for the service to become enabled before trying to disable it. For more information, look up the cause and action for the error code. The Domain Service could not enable the process due to the following error: [error description]. Cause: The Service Manager encountered a problem while enabling the service process. The service process may have been shutting down when you attempted to enable it, or the node where the service process runs may not be available. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. The Domain Service could not enable the service due to the following error: [error description]. Cause: The Service Manager could not enable the service when you clicked the Enable button. This error may appear, for example, if the service was shutting down when you attempted to enable it. 64 Chapter 2: Administration Console Error Messages
- 81. Action: Read the error description and make any necessary changes. For example, if the shutdown operation was incomplete when you attempted to enable the service, wait until the service is completely shut down before clicking the Enable button. For more information, look up the cause and action for the error code. Enter a valid location for the shared configuration on the node [node name]. Cause: No location was supplied for the shared configuration file. Action: Enter the storage location for the shared configuration file. The following error occurred while attempting to remove the node. Error - [error description]. Cause: The Service Manager could not remove the node from the domain. A problem may have occurred when the Service Manager attempted to abort the processes running on the node. The Service Manager may have encountered a problem when shutting down the node. Also, a problem may have occurred when the Service Manager attempted to remove the node from the domainmeta.xml file. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. The following error occurred while attempting to remove the service. Error - [error description]. Cause: The Service Manager could not remove the service. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. The following error occurred while attempting to shut down the node. Error - [error description]. Cause: The Service Manager could not shut down the node. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. The following error occurred while enabling this service. Error - [error description]. Cause: The Service Manager could not enable the service when you attempted to create it. This error may appear, for example, if the node you specified to run the service is unavailable. Action: Read the error description and make any necessary changes. For example, if the error description indicates that the node is unavailable, either restart the node or configure the service to run on a different node. For more information, look up the cause and action for the error code. This key was already used to update the license. Please use another key for the update. Cause: The same key cannot be used more than once to update a license. Administration Console Error Messages 65
- 82. Action: Verify that you are using the correct key to update the license. The location of the shared configuration files for some of the nodes could not be determined. Verify that all nodes are running. Cause: The Service Manager could not determine the location of shared configuration files. This problem can occur if node is not running or if the connection to the node fails. Action: Verify that all the nodes in the domain are running. Logs for specified query could not be exported because of the following error. Error - [error description]. Cause: The Service Manager could not export logs for a query. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. Logs for specified query could not be fetched because of the following error. Error - [error description]. Cause: The Service Manager could not fetch logs for the query. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. Logs for specified query could not be purged because of the following error. Error - [error description]. Cause: The Service Manager could not purge logs for a query. Action: Read the error description and make any necessary changes. For more information, look up the cause and action for the error code. None of selected nodes are running. Select at least one node that can be connected to run the Gateway Service. Cause: The nodes you designated as gateway nodes have been shut down. Action: Start up one of the designated gateway nodes. Alternatively, configure a node that is running to serve as a gateway. 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. Cause: The Upgrade Wizard cannot decrypt the encrypted password in the Repository Agent or PowerCenter Server configuration file. Action: Use pmpasswd in the previous version of PowerCenter to encrypt the password. Correct the password in the configuration file, revalidate the configuration file, and upgrade the Repository Agent or PowerCenter Server configuration file again. 66 Chapter 2: Administration Console Error Messages
- 83. You cannot remove node <node name> because it is the only gateway in the domain. Cause: All domains require at least one gateway node. You cannot remove a gateway node if it is the only gateway in the domain. Action: If you have the high availability option, create another gateway node for the domain before removing this gateway. Administration Console Error Messages 67
- 84. 68 Chapter 2: Administration Console Error Messages
- 85. Chapter 3 ADV Messages This chapter includes the following topic: โฆ ADV Messages, 70 Error messages listed numerically. 69
- 86. ADV Messages ADV_13226 Could not open the following dll: <dynamic link library name>.The reason is: <error message>. Cause: The Integration Service cannot load an external Custom transformation library that is dependent on other libraries. Action: See the additional error message for more information. 70 Chapter 3: ADV Messages
- 87. Chapter 4 ALERT Messages This chapter includes the following topic: โฆ ALERT Messages, 72 Error messages listed numerically. 71
- 88. ALERT Messages ALERT_10000 Alerts metadata was not found in the domain configuration database. Cause: The domain metadata is invalid. Action: Restore the domain configuration database with the latest backup file. Before you restore the domain configuration database from the latest backup file, back up the corrupted domain configuration database to another file to help Informatica Technical Support troubleshoot the problem, if necessary. ALERT_10001 Alert service has not been enabled yet. Cause: The domain has not enabled alerts. Action: Wait for the master gateway to initialize before sending another request. ALERT_10002 The user <user name> is not a user defined in the domain. Cause: The user specified cannot be found in the domain. Action: Check the domain Administration tab to be sure the specified user is valid. ALERT_10003 The user <user name> is not subscribed for alerts. Cause: The user specified to be removed from receiving alerts is not subscribed. Action: The user may have unsubscribed previously. Verify if the user being removed is no longer receiving alerts. ALERT_10004 Unable to send alert of type <alert type> for object <object name>, alert message <alert message>, with error <error>. Cause: Unable to send the referenced alert. Action: Verify that the SMTP connectivity and user email information are correct in the domain. ALERT_10010 Unable to remove the user <user name> from the alert service. Cause: Unable to remove the alert user. Action: Verify that the master gateway node is running on the domain. 72 Chapter 4: ALERT Messages
- 89. Chapter 5 ATHR Messages This chapter includes the following topic: โฆ ATHR Messages, 74 Error messages listed numerically. 73
- 90. ATHR Messages ATHR_10000 The Service Manager is not initialized yet. Cause: The Tomcat servlet container has not initialized the Service Manager. Action: The Service Manager is still initializing. If the Service Manager is not initialized within five minutes, contact Informatica Technical Support. ATHR_10003 The Service Manager is disabled and cannot accept authorization requests. Cause: The Service Manager on the master gateway experienced a problem and disabled itself. Action: Wait for a new master gateway node to be elected. The new master gateway node will enable its Service Manager. If a new master gateway node does not come up automatically, manually recycle this node. ATHR_10006 A request was received that was missing a required parameter. Cause: A request was received that was missing a required parameter. Action: If problem persists, contact Informatica Technical Support. ATHR_10007 A request was received with wrong <actual object type> parameter (expected: <expected object type>). Cause: A request was received that had the wrong type of parameter. Action: If problem persists, contact Informatica Technical Support. ATHR_10010 The Service Manager could not find <type of object> <object name>. Cause: A request was received to authorize access to an object that could not be located. Action: If problem persists, contact Informatica Technical Support. ATHR_10011 The Service Manager requires <expected parameter count> parameters within message but received <actual parameter count> parameters. Cause: A request was received with the wrong number of parameters. Action: If problem persists, contact Informatica Technical Support. ATHR_10012 The Service Manager denied authorization access to <type of object> <object name>. Cause: User was trying to access an object without proper permissions. Action: User should only access objects where permission was granted. ATHR_10013 The Service Manager cannot process <type of object> authorization access object type. Cause: A request was received on an unknown type of object. 74 Chapter 5: ATHR Messages
- 91. Action: If problem persists, contact Informatica Technical Support. ATHR_10014 The Service Manager for domain <this domain> received an authorization request for another domain <other domain>. Cause: This domain received a request to authorize an object on another domain. Action: If problem persists, contact Informatica Technical Support. ATHR_10015 The Service Manager received an external request to execute an internal operation by <the source of the credential used>. Cause: An internal request was received by an unauthorized sender. Action: Verify that the domain is secure from unauthorized users. ATHR_10017 The Service Manager received an authorization request which did not contain a credential. Cause: A request was received that did not have credential. Action: Log in again or wait until after master elections are finished. ATHR_10018 The Service Manager cannot process authorization <type of activity> activity type. Cause: A request was received for an unknown activity type. Action: If problem persists, contact Informatica Technical Support. ATHR_10019 The Service Manager denied authorization access to read-only user <user name> attempting to modify <type of object> <object name>. Cause: User was trying to modify an object without proper permissions. Action: User can read objects where permission was granted. ATHR_10021 The Service Manager denied authorization access to repository user <user name> attempting to access <type of object> <object name>. Cause: A repository user was trying to access an object outside of the repository logs. Action: Repository users can only access objects with reference to the repository they logged in to. ATHR_10022 The Service Manager denied authorization access for repository user <user name> as servicefolder is wrongly specified: <service and folder>. Cause: A repository user was trying to access a service and folder that was not specified correctly. Action: If problem persists, contact Informatica Technical Support. ATHR Messages 75
- 92. ATHR_10023 The Service Manager denied authorization access for repository user <user name> as service <service name> is not found. Cause: A repository user was trying to access a service not referenced in this domain. Action: Make sure that no changes have occurred with services in this domain. ATHR_10024 The Service Manager denied authorization access for repository user <user name> as request was for the wrong type of service <service type>. Cause: A repository user was trying to access an invalid service type. Action: If problem persists, contact Informatica Technical Support. ATHR_10025 The Service Manager denied authorization access for repository user <user name> as request was for another domain <domain name>. Cause: A repository user was trying to access another domain. Action: If problem persists, contact Informatica Technical Support. ATHR_10026 User <user name> does not have permission to access another user in the domain. Cause: User trying to access another user does not have adequate permission. Action: User should ask a root user to perform desired request. 76 Chapter 5: ATHR Messages
- 93. Chapter 6 AUTH Messages This chapter includes the following topic: โฆ AUTH Messages, 78 Error messages listed numerically. 77
- 94. AUTH Messages AUTH_10000 The Service Manager could not enable Authentication because authentication state is invalid. Cause: The network shared disk that stores the domain configuration data is not accessible. Action: Ensure access to the shared disk that stores the domain configuration database. or Cause: Node configuration is not synchronized with the domain configuration. Action: Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix the node configuration with infacmd. or Cause: Authentication configuration has invalid data. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. AUTH_10001 The Service Manager is not initialized yet. Cause: The Tomcat servlet container has not initialized the Service Manager. Action: The Service Manager is still initializing. If the Service Manager is not initialized within five minutes, contact Informatica Technical Support. AUTH_10005 The Service Manager is disabled and cannot accept authentication requests. Cause: The Service Manager on the master gateway node experienced a problem and disabled itself. Action: Wait for a new master gateway node to be elected. The new master gateway node will enable its Service Manager. If a new master gateway node does not come up automatically, manually recycle this node. AUTH_10007 Cannot add user because <user name> already exists. Cause: Cannot create a user with the same name as an existing user. Action: Use a different user name to create a new user. AUTH_10009 Cannot remove the Administrator user. Cause: The Administrator user cannot be removed. This operation is not allowed. Action: Do not attempt to remove the Administrator user. 78 Chapter 6: AUTH Messages
- 95. AUTH_10010 Cannot encrypt the credential because the characters in the user name, password, or domain name are not UTF-8 compliant. Cause: User name, password, or domain name contain characters that are not UTF-8 compliant. Action: Ensure that the user name, password, and domain name contain characters that are UTF-8 compliant. AUTH_10011 Failed to enable Authentication. Cause: The network shared disk that stores the domain configuration database is not accessible. Action: Ensure access to the shared disk that stores the domain configuration data. or Cause: Node configuration is not synchronized with the domain configuration. Action: Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix the node configuration with infacmd. or Cause: The authentication data is missing or invalid within the domain configuration database. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. AUTH_10014 Authentication data is invalid as it contains no users. Cause: The authentication data is invalid within the domain configuration database. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. AUTH_10015 A request for operation <operation name> required input that was not supplied. Cause: The input required by the operation was not provided. Action: Contact Informatica Technical Support to troubleshoot the problem. AUTH_10016 A request cannot be performed as user <user name> cannot be found. Cause: An attempt was made to update user data, but the Service Manager could not authenticate the user specified in the request. Action: If the error displays because of a user request, resubmit the request with a valid user name. It might be necessary to recreate the user. AUTH Messages 79
- 96. AUTH_10018 A request for operation <operation name> expected input of type <expected input type>, but was supplied with <actual input type>. Cause: Authentication did not receive the required input. Action: Contact Informatica Technical Support to troubleshoot the problem. AUTH_10019 The user name or password is not recognized by the system. Cause: The login user name and password combination is not valid. User cannot be authenticated. Action: Enter a valid user name and password to log in. AUTH_10022 The node <node name> not defined within the domain. Cause: The node is not defined in the domain. Action: Either change the node configuration or add the node to the domain. AUTH_10023 Administrator user name or password is not found in the domain configuration. Cause: The authentication data is invalid within the domain configuration database. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. AUTH_10024 Message request failed because the message contained invalid credentials that were not recognized by the system. Cause: The message request contained invalid credentials. Action: If error displays because of a user request, the user must log in again and resubmit the request to get a valid credential. Otherwise, contact Informatica Technical Support. AUTH_10026 The thread was interrupted while associating node <node name> with the domain. Cause: A problem occurred with threads while associating a node. Action: Try again. If problem persists, then contact Informatica Technical Support. AUTH_10027 The user <user name> associated with node <node name> was not found in the domain. Cause: The user specified in the node was not found in the domain. Action: Either add the user in the domain or redefine node with a domain user. 80 Chapter 6: AUTH Messages
- 97. AUTH_10028 The password associated with node <node name> is invalid. Cause: The user password provided with the node did not match the password in the domain configuration database. Action: Redefine the node with the correct password. AUTH_10029 The node <node name> is not associated in the domain. Cause: The node is not associated. Action: Redefine the node. AUTH_10030 User <user name> was not associated with node <node name>. Cause: The user specified in the node configuration does not match the domain configuration. Action: Either modify the user in the domain node or redefine node with the same user as the domain node. AUTH_10031 The host name for node <node name> is inconsistent between node configuration and domain configuration. Cause: The node configuration is incorrect. Action: Redefine the node. or Cause: The node is defined twice. Action: Create a new node with a different name. AUTH_10032 The port number for node <node name> is inconsistent between node configuration and domain configuration. Cause: The node configuration is incorrect. Action: Redefine the node. or Cause: The node is defined twice. Action: Create a new node with a different name. AUTH_10033 The gateway setting for node <node name> is inconsistent between node configuration and domain configuration. Cause: One definition is set as gateway and the other definition is set as worker. Action: Make sure they are consistent by updating domain node or redefining node configuration. AUTH_10036 User <user name> does not have permission on any object within the domain. Cause: The user trying to log in does not have any permission within the domain. AUTH Messages 81
- 98. Action: Root user can add permissions for the user or remove the user. AUTH_10037 Domain <domain name> for Repository Service <Repository Service name> is not linked within this domain. Cause: The user trying to log in through this domain for service not used within this domain. Action: User should log directly in to the Repository Service domain or define the link. AUTH_10038 Repository Service <Repository Service name> is not defined or referenced within this domain. Cause: The requested service is not known within this domain. Action: User should select a Repository Service known to this domain. AUTH_10039 Repository Service <Repository Service name> is defined in multiple known domains <list of domains>. Cause: Repository services with the same name exist in multiple domains. Action: User must also specify the requested domain. 82 Chapter 6: AUTH Messages
- 99. Chapter 7 BR Messages This chapter includes the following topic: โฆ BR Messages, 84 Error messages listed numerically. 83
- 100. BR Messages BR_16001 Error connecting to database... Cause: The Integration Service failed to connect to the database. You may have logged in incorrectly. Action: Log in with the correct information. User names and passwords may be case- sensitive. BR_16002 ERROR: Initialization failed. Cause: The Integration Service failed to initialize the reader. Action: Check the session log for related error messages. If no other messages appear, contact Informatica Technical Support. BR_16004 ERROR: Prepare failed. Cause: The Integration Service failed to prepare the SQL query for the Source Qualifier transformation. Action: Validate the mapping in the Designer. or Cause: Either you terminated the session during the reader process, or the Integration Service terminated the reader process because of internal errors. Action: Check the session log for related error messages. BR_16009 Reader run terminated. Cause: Either you terminated the session during the reader process, or the Integration Service terminated the reader process because of internal errors. Action: Check the session log for related error messages. BR_16034 ERROR: Fetch failed. Cause: An error occurred fetching information from the relational source database. Action: Check for additional database errors in the session log. If none exist, contact Informatica Technical Support. BR_16036 Error finding reader initializing function in dynamically loaded library. Cause: Internal error. Action: Contact Informatica Technical Support. BR_16037 Error initializing driver. Cause: Internal error. Action: Contact Informatica Technical Support. 84 Chapter 7: BR Messages
- 101. BR_16038 Sanity check failed: <message>. Reader initialization failed. Cause: The mapping may be invalid. Action: Validate the mapping in the Designer and run the workflow again. If the session fails, contact Informatica Technical Support. BR_16045 Reader run terminating. [Error threshold <maximum number of errors> reached reading data from <file name>]. Cause: The Integration Service reached the error threshold reading data from a source file. Action: See the previous error in the session log. BR_16046 User defined query <query name> has references to mapping parameters or variable that cannot be resolved correctly. Cause: The Integration Service encountered an error while expanding referenced parameters and variables in the specified query. Action: Make sure you declare the parameters and variables in the specified query and have valid start values. BR_16047 User defined join condition and/or source filter <condition name> has references to mapping parameters or variable that cannot be resolved correctly. Cause: The Integration Service encountered an error while expanding referenced parameters and variables in the specified join or filter condition. Action: Make sure you declare the parameters and variables in the specified join or filter condition and have valid start values. BR_16048 User defined source filter condition <condition name> has references to mapping parameters or variables that cannot be resolved correctly. Cause: The Integration Service encountered an error while expanding parameters and variables in the specified filter condition. Action: Make sure you declare the parameters and variables in the specified string and that they have valid start values. BR_16050 User provided string <string value> has references to mapping parameters or variables that cannot be resolved correctly. Cause: The Integration Service encountered an error while expanding parameters and variables in the specified string. Action: Make sure you declare the parameters and variables in the specified string and that they have valid start values. BR Messages 85
- 102. BR_16056 FTP Information in the repository is corrupt. Cause: The repository contains inconsistent FTP information. Action: Contact Informatica Technical Support. 86 Chapter 7: BR Messages
- 103. Chapter 8 BTree Messages This chapter includes the following topic: โฆ BTree Messages, 88 Error messages listed numerically. 87
- 104. BTree Messages BTree_90002 Error: Specified cache size is too small. It must be larger than <size>. Cause: The session failed because the cache size specified for the transformation is insufficient. Action: In the session properties, increase the cache size. BTree_90004 Error initializing the B-Tree. Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. or Cause: The amount of memory is inadequate to process the transformation. Action: Verify that the machine running the Integration Service has enough memory to process the transformation. BTree_90005 Failed to open the index cache file. Cause: The Integration Service does not have read permission on the cache directory. Action: Verify that the user configured to start Informatica Services has read permission on the cache directory. BTree_90006 Cannot write to index cache file. Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. BTree_90007 Key <key name> is not in index cache. Cause: The Integration Service could not find the primary key or foreign key in the index cache because the cache files may have been modified or deleted. Action: Run the session again. BTree_90009 Error unlocking cache block in group <group name>. Cause: The cache directory has inadequate disk space. Action: Check the disk for free space. BTree_90010 Error locking cache block in group <group name>. Increase the cache size. Cause: The session failed because the cache size specified for the transformation is insufficient. Action: In the session properties, increase the cache size. 88 Chapter 8: BTree Messages
- 105. or Cause: The cache directory has inadequate disk space. Action: Check the disk for free space. BTree_90011 Error inserting a row into the foreign key index for group <group>. Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. or Cause: The cache directory has inadequate disk space. Action: Check the disk for free space. BTree_90012 Error inserting a row into the primary key index for group <group>. Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. or Cause: The cache directory has inadequate disk space. Action: Check the disk for free space. BTree_90013 Error: Cannot remove duplicate row. Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. or Cause: The cache directory has inadequate disk space. Action: Check the disk for free space. BTree_90014 Error: Cache manager could not allocate a new block. Cause: The session failed because the cache size specified for the transformation is insufficient. Action: In the session properties, increase the cache size. or Cause: The Integration Service does not have write permission on the cache directory. Action: Verify that the user configured to start Informatica Services has write permission on the cache directory. BTree Messages 89
- 106. or Cause: The amount of memory is inadequate to process the transformation. Action: Verify that the machine running the Integration Service has enough memory to process the transformation. 90 Chapter 8: BTree Messages
- 107. Chapter 9 BW Messages This chapter includes the following topic: โฆ BW Messages, 92 Error messages listed numerically. 91
- 108. BW Messages BW_41013 Cannot connect to Integration Service <Integration Service name> in domain <domain name>. Cause: The connection setting for the Integration Service is incorrect. Action: Verify that the Integration Service is running. Check the user name, password, hostname, and port number settings for the Integration Service. BW_41014 The BW Server sent a request to the SAP BW Service that did not include a PowerCenter workflow name. Cause: The 3rd Party Selection tab of the BW InfoPackage does not include a PowerCenter workflow name. Action: Specify a PowerCenter workflow name in the 3rd Party Selection tab of the BW InfoPackage. BW_41020 Connect to SAP gateway failed. Cause: The RFC destination or the destination entry in saprfc.ini is incorrect. Action: Change the RFC destination or the destination entry in saprfc.ini. BW_41027 The Integration Service could not prepare the data in row number <row number> for the BW target <BW target name>. Cause: The source data contains invalid data for the row. Action: Correct the source data so that it matches the datatype, scale, and precision for the fields in the BW target definition. BW_41031 The SAP BW Service could not open the parameter file <parameter file> for data selection: <data selection>. Cause: The Parameter File Directory property for the SAP BW Service contains a directory that does not exist or that does not have read and write permissions enabled. Action: In the Administration Console, verify that the Parameter File Directory property contains a valid directory on the node where the SAP BW Service process runs. Also verify that the directory has read and write permissions enabled. BW_41044 Data selection was specified in the SAP BW InfoPackage but input value in 3rd party selection is not of the form Folder:Workflow:Session. The workflow name will be used as the session name in the parameter file header. Cause: The BW Server sent a request to the SAP BW Service that contains a data selection entry, but does not specify the workflow name on the 3rd Party Selection tab in the correct format. 92 Chapter 9: BW Messages
- 109. Action: Enter the workflow name in the 3rd Party Selections tab in the BW InfoPackage using the format <PowerCenter folder name>:<PowerCenter workflow name>:<PowerCenter session name>. BW_41052 The SAP BW Service could not connect to the Integration Service. Cause: The Integration Service may not be running. Or the SAP BW Service contains incorrect connection information for the associated Integration Service. Action: Verify that the Integration Service is running. Or in the Administration Console, verify that the SAP BW Service contains correct connection information for the Integration Service. BW_41058 The SAP BW Service reached the maximum number of errors trying to connect to the BW system. The SAP BW Service will be shut down. Cause: The SAP BW Service tried to connect to the BW system five times without succeeding. Action: Verify that the saprfc.ini file is configured correctly. BW_41065 Workflow Start request failed with message <message>. Cause: The Integration Service could not start the BW workflow for the reason specified in the message. Action: Correct the problem specified in the message and restart the workflow. BW_41073 The SAP BW Service received a call to the unsupported function <function>. Cause: The SAP BW Service received an RFC call from the BW system for a function that is not registered to the SAP BW Service. Action: Use the RFC Destination created for the SAP BW Service in the BW system for data loading purposes only. BW_41076 Error fetching the SAP BW Service configuration properties: <properties>. Cause: The SAP BW Service could not be started because the service contains properties with invalid values. Action: In the Administration Console, verify that the SAP BW Service properties are configured correctly. BW_41077 Error initializing service. Cause: The SAP BW Service could not initialize the LMAPI service because it could not connect to the Integration Service. Action: Verify that the Integration Service is running. Or in the Administration Console, verify that the SAP BW Service contains correct connection information for the Integration Service. BW Messages 93
- 110. BW_41082 The SAP BW Service could not find the Integration Service <Integration Service name> in domain <domain name>. Cause: The SAP BW Service could not find the Integration Service in the domain specified in the 3rd Party Selection tab of the BW InfoPackage. The values for the domain and Integration Service name properties might be invalid. Action: In the BW system, verify that the domain and Integration Service name entered in the 3rd Party Selection tab are valid. or Cause: The Integration Service might not be enabled. Action: Verify that the Integration Service is enabled. 94 Chapter 9: BW Messages
- 111. Chapter 10 CFG Messages This chapter includes the following topic: โฆ CFG Messages, 96 Error messages listed numerically. 95
- 112. CFG Messages CFG_10000 The Service Manager could not enable Domain Configuration because the domain state is invalid. Cause: The network shared disk that stores the domain configuration database is not accessible. Action: Ensure access to the shared disk that holds the domain configuration database. or Cause: Node configuration is not synchronized with the domain configuration. Action: Shutdown this gateway to force a master gateway election. If the problem is resolved, then fix the node configuration with infacmd. or Cause: Domain configuration database has invalid data. Action: Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. CFG_10001 The Service Manager is not initialized yet. Cause: The Tomcat servlet container has not initialized the Service Manager. Action: Wait a few minutes. The Service Manager is still initializing. If the Service Manager is not initialized within five minutes, contact Informatica Technical Support. CFG_10005 The Service Manager is disabled and cannot accept domain configuration requests. Cause: The Service Manager on the master gateway node experienced a problem and disabled itself. Action: Wait for a new master gateway node to be elected. The new master gateway node will enable its Service Manager. If a new master gateway node does not come up automatically, manually recycle this node. CFG_10008 A request was received that was missing a required parameter. Cause: A request was received that was missing a required parameter. Action: If problem persists, contact Informatica Technical Support. CFG_10009 A request was received with wrong <actual object type> parameter (expected: <expected object type>). Cause: A request was received that had the wrong type of parameter. Action: If problem persists, contact Informatica Technical Support. 96 Chapter 10: CFG Messages
- 113. CFG_10012 Cannot add an existing domain option group <option group name>. Cause: A request was received to add an existing option group. Action: Select an option group name that is not in use. CFG_10013 Domain option group <option group name> cannot be found. Cause: A request was received to access an option group that could not be found. Action: Verify the name of the option group or create the option group. CFG_10014 Cannot create an existing folder <folder path>. Cause: A request was received to create an existing folder. Action: Select a folder name that is not in use. CFG_10015 Cannot add an existing linked domain <linked domain name>. Cause: A request was received to add an existing linked domain. Action: Select a linked domain name that is not in use. CFG_10017 Cannot delete domain node <node name> because it is the only gateway in the domain. Cause: A request was received to delete the last gateway in the domain. Action: Select or create another node to be a gateway before continuing. CFG_10018 The folder <folder path> is not empty. Cause: A request was received to delete a folder that is in use. Action: Move or delete contents of the folder before continuing. CFG_10019 The root folder cannot be deleted. Cause: A request was received to delete the root folder. Action: Do not attempt to do this operation as it is protected. CFG_10020 Cannot change list of nodes associated with Integration Service <service name> while the service is enabled. Cause: A request was received to change nodes to grid, grid to nodes, or one grid to another grid on an enabled Integration Service. Action: Disable the service prior to making this type of change. CFG_10021 The Service Manager failed to read the domain configuration from <database type> database on <database host>:<database port> with error <error message>. Cause: The Service Manager failed to read the domain configuration from the database. CFG Messages 97
- 114. Action: Ensure the database connectivity information specified for the domain is correct. or Cause: Domain configuration database has invalid data. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. CFG_10022 Cannot associate service <service name> with repository because: <reason of failure>. Cause: An attempt to associate a service with a repository failed. Action: Fix the listed error before attempting again. CFG_10023 Cannot unassociate service <service name> with repository because: <reason of failure>. Cause: An attempt to unassociate a service with a repository failed. Action: Fix the listed error before attempting again. CFG_10025 Cannot delete grid <grid name> because it is referenced by these services: <list of services>. Cause: A request was received to delete a grid that is referenced by services. Action: Assign the listed services to other grids or nodes before continuing. CFG_10026 Grid <grid name> contains nodes <list of nodes> that are not defined in the domain. Cause: A request was received to include nodes in a grid that do not exist. Action: Use only existing nodes while modifying the grid. CFG_10027 Services <list of services> do not exist in the domain. Cause: The listed services do not exist in the domain. Action: Use only existing services within the requested operation. CFG_10028 Cannot delete linked domain <linked domain name> because it is referenced by these services: <list of services>. Cause: A request was received to delete a linked domain that is referenced. Action: Move the listed services to another domain. CFG_10029 Linked domain <linked domain name> cannot be found in the domain. Cause: A request was received to access a linked domain that could not be found. 98 Chapter 10: CFG Messages
- 115. Action: Link the domain. CFG_10030 Cannot add <object name> because the name is already in use within the domain. Cause: A request was received to add an object whose name is in use. Action: Select an object name that is not in use. CFG_10031 <object name> <type of object> cannot be found in the domain. Cause: The named object was deleted or never created in the domain. Action: Select an object that is defined in the domain. CFG_10032 Cannot delete component <component name> of the Service Manager. Cause: A request was received to delete a component of the Service Manager. Action: None. You cannot perform this protected operation. CFG_10033 Folder <folder path> already exists. Cause: A request was received to move a folder to parent folder with same name. Action: Select a different parent folder or change one of the names. CFG_10037 Cannot delete license <license name> because services are assigned to it. Cause: A request was received to delete a license that has services assigned to it. Action: Move the assigned services to another license. CFG_10040 Cannot add linked domain <linked domain name> because it has the same name as the domain. Cause: A request was received to add a linked domain with name already in use. Action: Select a different name for one of the domains. CFG_10041 Folder path <folder path> does not exist. Cause: The provided folder path does not exist in the domain. Action: Provide an existing folder path or verify the provided folder path. CFG_10042 License serial number is already in use. Cause: A request was received to add a license with same serial number as another license serial number. Each license must contain a unique serial number. When you create the license, the original license key provides a serial number for the license. Action: Use a different original key to create the license. Contact your Informatica sales representative to get another license. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request. CFG Messages 99
- 116. CFG_10043 Failed to add a license key that expired on <expiration date>. Cause: A request was received to add a license key that has already expired. Action: Contact your Informatica sales representative to extend your license. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request. CFG_10044 Node option group <option group name> for node <node the option group belongs to> was not found. Cause: A request was received to access an option group that cannot be found. Action: Use infacmd listNodeOptions to list the available option groups. CFG_10045 Cannot add existing node option group <option group name> to node <node name>. Cause: A request was received to add an existing option group for the node. Action: Update the individual options in the option group or choose another name. CFG_10046 Cannot add existing <type of resource> resource <resource name> to node <node name>. Cause: A request was received to add an existing node resource. Action: Provide a different resource name or a different resource type. CFG_10047 <type of resource> resource <resource name> cannot be found on node <node name>. Cause: A request was received to act on a non-existing node resource. Action: Provide the resource name before continuing. CFG_10048 User <name of the user> does not have permission on node <node name>. Cause: A request was received to add or update a node with an invalid login user. Action: Either assign permission to that user to access the node or choose a user who has node permission. CFG_10049 Cannot associate a gateway node <node name> without specifying the log directory. Cause: A request was received to associate a gateway node without the log directory being specified. Action: Verify that the log directory is specified. CFG_10050 Cannot switch to or from a gateway node with the update operation. Cause: A request was received to switch gateway status for a node. Action: Use the switchToGatewayNode or the switchToWorkerNode commands, or change the gateway status in the Administration Console. 100 Chapter 10: CFG Messages
- 117. CFG_10051 User <user name> cannot be found. Cause: A request was received to update a node with a login user that is not defined in the domain. Action: Choose a user who has node permission. CFG_10052 Cannot unassociate node <node name> while it is running. Cause: An attempt was made to unassociate a running node. Action: Shutdown the node first. CFG_10055 The domain configuration database is invalid because: <validation message>. Cause: The domain configuration database is invalid. Action: Contact Informatica Technical Support. Before restoring the domain configuration database from last known good backup file, first back up the invalid domain configuration database to another file to help Informatica Technical Support troubleshoot the problem. CFG_10057 Unable to connect to the linked domain <domain name> because: <error message>. Cause: The domain cannot communicate with the linked domain specified. Action: Verify that the Service Manager on the linked domain is running and that its gateway host:port address is correct. CFG_10059 Cannot associate node <node name> without redefining the node. Cause: A request was received to associate a node that was probably unassociated and has not been redefined. Action: Use infacmd defineGatewayNode or defineWorkerNode command to redefine the node. CFG_10060 The administrator permissions on the root folder cannot be removed. Cause: A request was received to remove administrator from the root folder. Action: None. You cannot perform this protected operation. CFG_10062 Cannot add service <service name> because license <license name> is not found in the domain. Cause: A request was received to add a service using a non-existing license. Action: Specify a valid license to assign the service to. CFG_10080 The input list must contain a user name followed by at least one object name. Cause: A request was received with invalid parameters. Action: Provide the user name followed by at least one object name. CFG Messages 101
- 118. CFG_10081 Object at full path <full path of object> cannot be found in the domain. Cause: A request was received for an object that cannot be found. Action: Verify that the object path and the object name are correct. CFG_10082 The value <option value> for option <option name> of service <service name> is not valid. Cause: The option value specified for the service is not valid. Action: Check to make sure option specified is valid. CFG_10083 The operating mode of service <service name> cannot be changed to safe mode while the service is enabled. Cause: The operating mode cannot be changed to safe while the service is enabled. Action: Disable the service first. CFG_10084 Cannot move the root folder. Cause: A request was received to move the root folder. Action: None. You cannot perform this protected operation. CFG_10085 Cannot move a folder to one of its subfolders. Cause: A request was received to move folder to one of its subfolders. Action: Select a different target location. CFG_10086 Cannot perform operation on an unassociated node <node name>. Cause: An attempt was made to perform an operation on an unassociated node. Action: Associate the node first. CFG_10087 Service <service name> contains references to linked domains <list of linked domains> not defined in the domain. Cause: A request was received to add a service referencing undefined linked domains. Action: Link the domains. CFG_10088 Node <node name> was modified to be a gateway node in the domain but failed to update node metadata file. Cause: A problem was encountered communicating with the node that did not update its metadata file. Action: Go to the node and run infacmd defineGatewayNode to match domain definition. 102 Chapter 10: CFG Messages
- 119. CFG_10089 Node <node name> was modified to be a worker node in the domain but failed to update node metadata file. Cause: A problem was encountered communicating with the node that did not update its metadata file. Action: Go to the node and run infacmd defineWorkerNode to match the domain definition. CFG_10091 The full path was not specified for object <object name>. Cause: A request was received for an object requiring the full path. Action: Provide the object full path. CFG Messages 103
- 120. 104 Chapter 10: CFG Messages
- 121. Chapter 11 CMD Messages This chapter includes the following topic: โฆ CMD Messages, 106 Error messages listed numerically. 105
- 122. CMD Messages CMD_35197 The Value <value> for INFA_CLIENT_RESILIENCE_TIMEOUT is invalid. Using default value <value> instead. Cause: The environment variable INFA_CLIENT_RESILIENCE_TIMEOUT is set to an invalid value. Action: Change the value to 0 or any positive integer. CMD_35198 Error: Cannot connect to Integration Service. Cause: You can use the environment variable INFA_DOMAINS_FILE to store the domains.infa path. You will receive an error if the environment variable INFA_DOMAINS_FILE is not set. Action: Add the environment variable, INFA_DOMAINS_FILE, and set the path to the domains.infa file. By default, the domains.infa file resides in the PowerCenter directory. 106 Chapter 11: CMD Messages
- 123. Chapter 12 CMN Messages This chapter includes the following topic: โฆ CMN Messages, 108 Error messages listed numerically. 107
- 124. CMN Messages CMN_1003 Server port not specified. Cause: You did not specify the Integration Service port in the Administration Console. Action: In the Administration Console, enter a valid value for the Integration Service port. CMN_1006 Failed to connect to repository. Cause: Connection information may be missing or invalid in the Administration Console. Action: In the Administration Console, check all connectivity information. If related error messages appear in the session log, fix those errors before attempting to connect again. CMN_1008 Internal error. Cause: An internal error occurred. Related error messages may appear to further diagnose the error. Action: Contact Informatica Technical Support. CMN_1009 Internal error: Failed to execute child process. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1011 Error allocating system shared memory of <number> bytes for [DTM Buffer Pool]. Error is <system error code>: <system error message>. Cause: An error occurred while your system allocated shared memory. Action: Close any unnecessary programs and restart the Integration Service before running the session again. Check the system parameters for shared memory allocation. CMN_1012 Error: shm_malloc() failed. Unable to allocate the bytes requested... Cause: Insufficient shared memory allocation. Action: Check the session log for related error messages. If none appear, contact Informatica Technical Support. CMN_1017 Error encountered decrypting password... Cause: You entered an invalid password in the Administration Console. Action: Make sure you typed in your password correctly. Passwords may be case sensitive. If your password is correct, contact Informatica Technical Support. 108 Chapter 12: CMN Messages
- 125. CMN_1021 Database driver event... Cause: A database driver event occurred. Action: Check your session log for a related database driver error message. If necessary, check your database manual for an action. CMN_1023 Database license key not specified. Cause: You did not specify the database license key in the Administration Console. Action: In the Administration Console, enter a valid database license key. CMN_1024 Invalid database license key <license key>. Cause: You entered an invalid license key in the Administration Console. Action: In the Administration Console, specify a valid database license key. CMN_1026 Incorrect repository version... Cause: The repository and software versions do not match. One has been updated, while the other has not been updated. Action: If your repository is older, upgrade your repository. If your software is older, upgrade your software. CMN_1028 ERROR: Illegal operation on a non-mutex. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1029 ERROR: Illegal operation on a mutex. Same as CMN_1028. CMN_1030 ERROR: Illegal unlock operation -- mutex not locked. Same as CMN_1028. CMN_1035 Sybase event. Cause: A Sybase event has occurred. Action: Check the session log for a related Sybase event. If necessary, check your Sybase manual for action. CMN_1036 Sybase error. Cause: A Sybase error has occurred. Action: Check the session log for a related Sybase error message. If necessary, check your Sybase manual for action. CMN_1037 Oracle event. Cause: An Oracle event has occurred. CMN Messages 109
- 126. Action: Check the session log for a related Oracle event. If necessary, check your Oracle manual for action. CMN_1038 Oracle error. Cause: An Oracle error has occurred. Action: Check the session log for a related Oracle error message. If necessary, check your Oracle manual for action. CMN_1040 SQL Server Error. Cause: A Microsoft SQL Server error has occurred. Action: Check the session log for a related Microsoft SQL Server error message. If necessary, check your Microsoft SQL Server manual for action. CMN_1044 DB2 Error. Cause: A DB2 error has occurred. Action: Check the session log for a related DB2 error message. If necessary, check your DB2 manual for action. CMN_1046 ODBC Error. Cause: You created an ODBC data source, but no longer have the underlying native connectivity software or environment. Action: Reconfigure the native connectivity environment and then run the session. or Cause: A session with DB2 UDB EEE sources or targets failed when the Integration Service ran on AIX and used both the DataDirect ODBC driver manager and the DB2 UDB EEE CAE ODBC driver. This problem occurred because the DataDirect ODBC driver manager and the DB2 UDB EEE CAE ODBC driver are not compatible. Action: Do not use an ODBC connection. Be sure to only use a native DB2 CAE connection to a DB2 database. CMN_1049 PM error. Cause: This is a generic error. Action: Check the session log for related error messages. CMN_1050 PM event. Cause: This is a generic error. Action: Check the session log for related error messages. CMN_1053 Error information. Cause: This is a generic error. 110 Chapter 12: CMN Messages
- 127. Action: This message varies depending on the error. Check the session log for more specific messages. CMN_1054 Memory allocation error. Cause: Error in memory allocation. Your system resources may be low. Action: Close any unnecessary applications and restart the system. If the problem persists, you may need to add RAM to your system. CMN_1055 Error preparing SQL statement to fetch lookup data. Cause: A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly. Action: This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping. or Cause: The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly. Action: Log in with the correct information. user names and passwords may be case- sensitive. or Cause: The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down. Action: Make sure the database is up before running the session again. CMN_1056 Error executing SQL statement to fetch lookup data. Same as CMN_1055. CMN_1057 Error in fetching lookup data from database. Same as CMN_1055. CMN_1061 ERROR: Process terminating on signal/exception. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1062 Error creating lookup cache. Cause: An error occurred while creating the lookup cache. Action: Check the session log for related error messages. CMN Messages 111
- 128. CMN_1063 ERROR: Multiple match found in lookup. Cause: In a Lookup transformation, you specified the Lookup Policy on Multiple Match option to return this error message when encountering multiple occurrences of data. Action: If you do not want an error message when multiple matches occur in the lookup table, change the Lookup Policy on Multiple Match option. CMN_1064 Error in lookup SQL statement prepare. Same as CMN_1055. CMN_1065 Error in lookup SQL statement execute. Same as CMN_1055. CMN_1066 Error in lookup SQL statement fetch. Same as CMN_1055. CMN_1075 ERROR: Data overflow. Cause: A numeric data overflow occurred. One of the rows exceeded the declared precision in the target column. The Integration Service writes that row to the session reject file, and sometimes to the session log, depending on the session tracing level. If you enabled row error logging, the Integration Service writes the row to the error log. Action: Check the session reject file or error log to find the row. If this is a recurring error, you may want to change the precision of the target transformation column. CMN_1076 Error creating database connection. Cause: The configuration parameters for the database may be incorrect. Action: Check the database connection defined in the Workflow Manager. or Cause: The database or network may be down. Action: Make sure they are both up before running the session again. CMN_1077 Lookup table not found in the database. Cause: The lookup table may have been deleted or renamed since the mapping was last saved. Action: Check the name of the lookup table in the mapping and in the database. Make sure the names match. CMN_1078 Error accessing synchronization object. Cause: Internal error. 112 Chapter 12: CMN Messages
- 129. Action: Contact Informatica Technical Support. CMN_1079 WARNING: Lookup table contains no data. Cause: The lookup table specified in your mapping contains no data because you specified an invalid lookup table. Action: Make sure your mapping contains the correct name of the lookup table. or Cause: The lookup table specified in your mapping is empty. Action: Import or enter the correct data for your lookup table. CMN_1082 ERROR: Invalid lookup condition. Cause: In a Lookup transformation, the lookup condition is invalid or blank. Action: Correct the invalid lookup condition. CMN_1083 Error encountered encrypting password... Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1086 <Transformation name>: Number of error exceeded threshold number. Cause: The specified transformation reached the error threshold. Action: Examine the incoming data and the transformation configuration to locate the problem, then correct the problem. Or increase the error threshold. CMN_1087 ERROR: PowerMart Username not specified. Cause: You did not specify a user name in the Administration Console. Action: Enter a valid value for user name. CMN_1088 ERROR: PowerMart Password is not specified. Cause: You did not specify a password in the Administration Console. Action: In the Administration Console, enter a valid value for Password. Passwords must be in 7-bit ASCII. CMN_1089 ERROR: Invalid lookup connect string. Cause: A Lookup transformation contains an invalid location for its lookup table. Action: Check the location of the lookup table, and then enter the correct location in the Lookup transformation. CMN_1093 ERROR: Invalid join condition supplied. Cause: A Joiner transformation in your mapping specifies an invalid join condition. CMN Messages 113
- 130. Action: Make sure the condition for each Joiner transformation in the session contains at least one valid join. or Cause: If each Joiner transformation uses valid conditions, you may have repository inconsistencies. Action: Contact Informatica Technical Support. CMN_1094 ERROR: No valid field from the master relation. Cause: One of the Joiner transformations in the mapping has a master port that is not used in the join condition or the output port. Action: Make sure to use the master ports as required. or Cause: If there are no extraneous input ports connected to the Joiner transformations, you may have repository inconsistencies. Action: Contact Informatica Technical Support. CMN_1095 ERROR: Field name used in join not found in transform definition. Cause: The Integration Service could not locate a port specified in the Joiner transformation. You may have repository inconsistencies. Action: Contact Informatica Technical Support. CMN_1096 ERROR: Operator not supported in the join condition. Cause: The join condition for a Joiner transformation contains an operator that is not supported. The equal sign (=) is the only operator supported in a Joiner transformation. Action: Edit the join condition in the session properties, using an equal sign (=) as an operator. CMN_1097 ERROR: No valid output field. Cause: A Joiner transformation has no output links. Each Joiner transformation needs to have at least one output link. Action: Make sure each Joiner transformation has at least one linked output port. CMN_1098 ERROR: Cache Directory may not exist or insufficient privilege/space in the supplied cache directory. Cause: The directory specified for the index and data caches has run out of memory. Action: Free up disk space in the cache directory. or Cause: You do not have the appropriate privileges to access that directory. 114 Chapter 12: CMN Messages
- 131. Action: Have the system administrator check your file system privileges. CMN_1099 ERROR: Master and detail relations are flipped from user specification. Cause: In the mapping, one Source Qualifier transformation has been linked to two Joiner transformations in the same target load order group, and has been specified as the master source in one Joiner transformation and the detail source in the other. Action: Edit the Joiner transformations so the same Source Qualifier transformation is the master source in both Joiner transformations in the same target load order group. or Action: If you need to keep the Source Qualifier transformation as the master source in one Joiner transformation and the detail source in the other, create a separate target load order group and place one of the Joiner transformations in that second group. CMN_1100 ERROR: A target load order group has at least one Source Qualifier transformation that has been used to provide master as well as detail data. Same as CMN_1099. CMN_1101 ERROR: Alter the mapping and place the target tables violating this constraint in different target load order groups. Same as CMN_1099. CMN_1102 ERROR: No ports in the join condition are connected. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1103 WARNING: No row found from the master relation. Joiner will not produce any output row. Cause: The master source contained no rows. Since the data from the master source is read before the detail source data can load, the Joiner transformation is unable to produce data when the master source contains no data. Action: Make sure the correct source tables are named in the mapping and those tables contain data. CMN_1104 ERROR: The conversion from source type to target type is not supported. Cause: The mapping contains an invalid datatype conversion. Action: In the Designer, validate the mapping to locate the invalid conversion. CMN Messages 115
- 132. CMN_1105 ERROR populating index using the key value from the master relation row. Cause: The index cache ran out of memory, causing the Integration Service to use the index file at a local directory that ran out of disk space as well. Action: This message is preceded by a file error. Correct the file error before running the session again. CMN_1106 ERROR: Index file operation error in Joiner. Cause: This is a file error. It is followed by another message naming the Joiner and the specific file error. Action: Correct the file error before running the session again. CMN_1107 ERROR: Data file operation error in Joiner. Same as CMN_1106. CMN_1108 ERROR: PowerMart product license key not specified. Cause: You did not specify the PowerCenter product license key in the Administration Console. Action: Specify a valid product license key in the Administration Console. CMN_1109 ERROR: Invalid PowerMart product license key <key name>. Cause: The specified PowerCenter product license key listed in the Administration Console is invalid. Action: In the Administration Console, enter a valid Informatica product license key. If the license key is accurate, contact Informatica Technical Support. CMN_1111 Error encountered decrypting PowerMart password. Cause: The Integration Service encountered an invalid password in the Administration Console. Action: Check the password in the Administration Console. CMN_1120 Error <error code> getting status of attachment file <file name>. Cause: You configured a session for post-session email with an attached file. The Integration Service account on UNIX does not have read permission for one (or more) of the directory components for the attachment file directory. Action: Ensure the Integration Service account on UNIX has read permission for the attachment file path. CMN_1121 Attachment file <file name> not found. Cause: You configured a session for post-session email with an attached file. The Integration Service on UNIX could not locate specified file. 116 Chapter 12: CMN Messages
- 133. Action: Verify the directory and file name for the attachment file are entered correctly in the session properties. Verify the file exists in the specified directory. CMN_1122 Attachment file <file name> is not a regular file. Cause: You configured a session for post-session email with an attached file. The attachment file you have specified is not a regular UNIX file. It might be a directory name or some other type of file. Action: Specify a regular attachment file in the session for post-session email. CMN_1123 Error opening attachment file <file name> for read. Cause: You configured a session for post-session email with an attached file. The Integration Service account on UNIX may not have read permissions on the attachment file. Action: Enable read permissions on the Integration Service on UNIX for the attachment file. CMN_1124 Error reading from attachment file <file name>. Cause: A system error, such as disk corruption, occurred while a Integration Service on UNIX tried to attach a file to a post-session email. Action: Resolve the system error condition. CMN_1125 Error opening temporary email <temporary file name> file for write. Cause: An Integration Service on UNIX encountered an error trying to create post- session email. The directory from where the Integration Service was started does not have write permissions for the Integration Service account. Action: Make sure the directory has write permissions. CMN_1126 Error writing to temporary email file (out of disk space?). Cause: The Integration Service on UNIX encountered an error creating post-session email, possibly due to lack of disk space. Action: Make sure there is sufficient disk space on the machine hosting the Integration Service. CMN_1127 Warning: Error in deleting temporary email file. Cause: The Integration Service on UNIX could not delete a temporary file name used to create post-session email. Action: The Integration Service reuses the temporary file when creating post-session email, so you do not need to take action upon receiving this message. CMN_1128 Error executing shell... Cause: An error occurred while the Integration Service on UNIX tried to execute a shell command. The listed error code is a UNIX error code. CMN Messages 117
- 134. Action: If running a Integration Service on UNIX, check the session log for the related UNIX error number. Then locate the error in the /usr/include/sys/errno.h file. Check the UNIX documentation for explanation of the error. CMN_1129 Error sending email... Cause: The rmail UNIX command used to send email returned an error. The listed error code is a UNIX error code. Action: Check the rmail documentation. CMN_1134 This PowerMart Server build does not support database type (Microsoft SQL Server). Cause: The Integration Service on UNIX tried to load Microsoft SQL Server as a target database using native drivers. The Integration Service on UNIX does not support Microsoft SQL Server database type. Action: Use the DataDirect ODBC SQL Server driver for UNIX to load Microsoft SQL Server. CMN_1141 ERROR: Unexpected condition at file; <file name> line <line number>. Application terminating. Contact Informatica Technical Support for assistance. Cause: An application error occurred. Action: Note the file name and line number and contact Informatica Technical Support. CMN_1164 Database driver error... Bulk write initialization failed (blk_init returned failure). Cause: Your session failed because you loaded to Sybase 11 and configured the Table Name Prefix option in the mapping target instance or in the session properties. Action: If you load to multiple Sybase 11 tables with different owners, create views of all the target tables in one database. Ensure that the owner of the views has all required permissions on the target tables. Create the database connection in the Workflow Manager using the target owner as the user in the connection. Or, if the target tables have the same owner, make sure the user in the database connection is the owner of the targets. CMN_1573 Error: Unknown code page <code page ID> for data source <source name>. Cause: The system could not find a code page for the source. The pmlocale.bin file might be corrupt or incomplete. Action: Install a complete pmlocale.bin file from the installation CD. 118 Chapter 12: CMN Messages
- 135. CMN_1574 Error: Failed to create locale from code page <code page ID> for data source <source name>. Cause: The system could not locate locale information for the source. The pmlocale.bin file that contains the locale information might be corrupt or incomplete. Action: Install pmlocale.bin file from the installation CD. 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. Cause: In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value. Action: Increase the lookup index cache size to the value recommended in the error message. CMN_1577 Error: The current lookup index cache size of <number> bytes is too small. Increase the lookup index cache size to at least <number> bytes. Cause: In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value. Action: Increase the lookup index cache size to the value recommended in the error message. CMN_1579 Input lookup precision is greater than the output lookup precision. Verify that the Lookup transformation and linked transformations have the same port precisions. Cause: The lookup input and output port precisions are not identical. Action: In the lookup condition, verify that the ports in the Lookup Table Column and the Transformation Port have the same precision. CMN_1625 ERROR: Joiner <Joiner transformation> has <number> inputs for the master relation. There should only be one master relation. Cause: The mapping is invalid and you cannot run the session. Action: Check the mapping, make changes, and revalidate it. CMN_1626 ERROR: Joiner <Joiner transformation name> has <number> inputs for the detail relation. There should only be one detail relation. Cause: The mapping is invalid and you cannot run the session. Action: Check the mapping, make changes, and revalidate it. CMN_1627 Internal error restoring row from cache. Cause: Internal error, or there may be problems with the joiner cache files. Action: Truncate the targets and run the session again. CMN Messages 119
- 136. CMN_1628 Joiner <Joiner transformation name> initialization error creating detail input row data. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1629 Joiner <Joiner transformation name> initialization error creating master input row data. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1630 ERROR: Unexpected error encountered at file <file name> line <line number>. Cause: Unexpected error. Action: Review error messages preceding this message. Otherwise, note the file name and line number and contact Informatica Technical Support. CMN_1636 Error occurred aborting row in joiner transformation <transformation name>. Cause: An error occurred while aborting a row in the Joiner transformation instance. Action: Check other error messages preceding this error message in the log. CMN_1642 Error: Static Lookup Transformation <transformation name> has the same cache file name prefix <cache file name> as a Dynamic Lookup Transformation <transformation name> in same TLOG. Cause: You cannot share static and dynamic lookups in the same target load order group. Action: Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group. CMN_1643 Error: Dynamic Lookup Transformation <transformation name> has the same cache file name prefix <cache file name> as a Dynamic Lookup Transformation <transformation name> in same TLOG. Cause: You cannot share two dynamic lookups in the same target load order group. Action: Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group. CMN_1644 Error: Dynamic Lookup Transformation <transformation name> has the same cache file name prefix <cache file name> as a Static Lookup Transformation <transformation name> in same TLOG. Cause: You cannot share static and dynamic or two dynamic lookups in the same target load order group. Action: Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group. 120 Chapter 12: CMN Messages
- 137. CMN_1645 Error: Failed to get shared access to cache files <cache file name>. [dat/idx] for lookup <Lookup transformation>. Cause: One session is trying to read from a cache file while another session is still writing to it. Action: Wait until the first session completes, then run the session. CMN_1646 Error: Failed to get exclusive access to cache files <cache file name>. [dat/ idx] for lookup <Lookup transformation>. Cause: One session is trying to write to a cache file while another session is reading from it. Action: Wait until the first session completes, then run the session. CMN_1647 Error: Failed to upgrade to exclusive access for cache files <cache file name> for lookup <Lookup transformation>. Cause: A session is trying to write to a cache file while another session is reading from the file. Action: Wait until the first session completes, and then run the session. CMN_1649 Error: Lookup table name <lookup table name> is too long. Maximum allowed length is <number>. Cause: You exceeded the length allowed for the lookup table name. Action: Reduce the length of the lookup table name. 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. Cause: You configured a Lookup transformation to use a dynamic lookup cache and the lookup table contains duplicate rows. Action: Eliminate duplicate rows in the lookup table, or use a static cache. CMN_1655 Error: Lookup Transformations <transformation name> and <transformation name> have the same cache file name prefix <cache file name> but have different connect strings <connect string> vs. <connect string>. Cause: Two Lookup transformations have different connect strings, but have the same cache file name. Action: Make sure the connect strings match. CMN_1656 Error: Lookup Transformations <transformation name> and <transformation name> have the same cache file name prefix <cache file name> but only the latter has a query override <query>. Cause: Two Lookup transformations have different query overrides, but have the same cache file name. CMN Messages 121
- 138. Action: If you want to share the cache, use the same query override. If you do not want to share the cache, change the cache file name for one of the Lookup transformations. CMN_1657 Error: Lookup Transformations <transformation name> and <transformation name> have the same cache file name prefix <cache file name> but have different override strings <override string> vs. <override string>. Cause: Two Lookup transformations have different query overrides, but have the same cache file name. Action: If you want to share the cache, use the same query override. If you do not want to share the cache, change the cache file name for one of the Lookup transformations. CMN_1658 Error: Lookup Transformations <transformation name> and <transformation name> have the same cache file name prefix <cache file name> but correspond to different tables <table name> vs. <table name>. Cause: Two Lookup transformations use different lookup tables, but have the same cache file name. Action: If you want to share the cache, the lookup table names must match. If you do not want to share the cache, change the cache file name for one of the Lookup transformations. CMN_1659 Error: Condition column <column name> of Lookup <transformation name> (with existing cache) was not found in Lookup <transformation name> (that is trying to find one to share) even though they have the same cache file name prefix <cache file name>. Cause: When you have multiple Lookup transformations in a mapping, the first lookup creates a cache file. The second lookup tries to use the same cache file, but cannot because the condition does not match. Because both lookups use the same cache file name, the second lookup cannot create a new cache file. Action: If you do not want to share the cache, change the cache file name for one of the lookups. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions. CMN_1660 Error: The number <number> of condition columns of Lookup <transformation name> is different from <number> Lookup <transformation name> even though they have the same cache file name prefix <prefix name> and <cache file name> needs to be refreshed / updated. Cause: The second Lookup transformation uses a subset of condition columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of condition columns must be the same. 122 Chapter 12: CMN Messages
- 139. Action: If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions. CMN_1661 Error: Output column <column name> of Lookup <transformation name> (that is trying to find one to share) was not found in Lookup <transformation name> (with existing cache) even though they have the same cache file name prefix <cache file name> and <cache file name> needs to be refreshed / updated. Cause: The second Lookup transformation uses a subset of condition columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of condition columns must be the same. Action: If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions. CMN_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>. Cause: The second Lookup transformation uses a subset of output columns of the first Lookup transformation. However, the second Lookup transformation needs to update the cache. The number of output columns must be the same. Action: If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions. CMN_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. Cause: The second Lookup transformation uses a subset of output columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of output columns must be the same. Action: If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions. CMN_1664 Error: Out of sequence IDs to generate for port <port name> of Lookup <transformation name> for insertion. Cause: You reached the limit of unique sequence IDs that can be generated for inserting rows in the dynamic lookup cache. CMN Messages 123
- 140. Action: Check the value of this port in the rows that are used to initialize the lookup cache. Try to modify the value. CMN_1665 Error: Failed to form key row for insertion in index cache file for Lookup <transformation name>. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1666 Error: Failed to form data row for insertion in data cache file for Lookup <transformation name>. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1667 Error: Failed to insert row for Lookup <transformation name>. Cause: Internal error. Action: Contact Informatica Technical Support. 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. Cause: Another session with a named lookup cache in the mapping may be running that is using this cache file. Action: Use unique cache file names for the named Lookup transformation. CMN_1678 Error: Cache file <cache file name> needed by named Lookup Transformation <transformation name> in this mapping appears to be created by an unnamed cache lookup transformation. Cause: Another session with an unnamed Lookup transformation in the mapping may be running that is using this cache file. Action: Use unique cache file names for the named Lookup transformation. CMN_1679 Warning: A cache file name prefix <prefix> has been specified for the Lookup Transformation <transformation name> but it is not marked as persistent. The cache file name prefix will be ignored. Cause: The Lookup transformation has been configured to use a cache file name prefix, but it has not been configured for a persistent lookup cache. You can use a cache filename prefix only with a persistent lookup cache. Action: Change the Lookup properties to either remove the cache filename prefix or use a persistent cache. For more information, see โLookup Cachesโ in the Transformation Guide. 124 Chapter 12: CMN Messages
- 141. 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. Cause: In a previous target load order group in a mapping, a dynamic Lookup transformation created a cache file. A static Lookup transformation uses the same cache file name and cannot delete it. Action: Use unique cache file names for the transformations. CMN_1684 Error: Dynamic Lookup <transformation name> needs to delete a cache file <cache file name> that was created by a Static Lookup <transformation name> in an earlier TLOG using different parameters. Cause: In a previous target load order group in a mapping, a static Lookup transformation created a cache file. A dynamic Lookup transformation uses the same cache file name and cannot delete it. Action: Use unique cache file names for the transformations. CMN_1686 Error allocating <number of bytes requested> in memory for cache transformation: <transformation name>. Cause: You specified a cache size larger than the system can allocate. Action: Either reduce cache size for the transformation or increase virtual memory available in the machine. CMN_1687 Error: Cache not enabled for Dynamic Lookup transformation <transformation name>. Cause: In the session, you disabled caching for a Lookup transformation that you configured to use as a dynamic cache. Action: If you configure a Lookup transformation with a dynamic cache, you must enable caching in the session. CMN_1689 Failed to allocate <number> bytes from process memory for [DTM Buffer Pool]. Cause: There is insufficient process memory. Action: Reduce the DTM buffer pool size, or free system resources. CMN_1691 Cache expects port <port name> but cache file has it in a different data type and cannot be used. A new cache file will be created. Cause: Two Lookup transformations are configured to share a lookup cache, but the datatypes of the cached columns in the Lookup transformations do not match. Action: If you are using a named cache, verify that the caching structures match. If you are using an unnamed cache, verify that the caching structures are compatible. CMN Messages 125
- 142. CMN_1694 Database Event Unable to set DBARITHABORT: Arithmetic exceptions from Microsoft SQL Server will not cancel query execution. Cause: The Integration Service failed to set database option DBARITHABORT for a database connection to Microsoft SQL Server. Action: Make sure Microsoft SQL Server is running and check Microsoft SQL Server network settings so that the Integration Service can connect to the database and set the DBARITHABORT option. CMN_1695 Database Event Unable to set options: Options cannot be set in Microsoft SQL Server. Cause: The Integration Service failed to set any database option for a database connection to Microsoft SQL Server. Action: Make sure Microsoft SQL Server is running and you can set the database connection and database connection options. CMN_1701 Error: Data for Lookup <transformation name> fetched from the database is not sorted on the condition ports. Please check your Lookup SQL override. Cause: You specified a SQL override for this Lookup transformation and specified the ORDER BY clause incorrectly. Action: When you override the lookup query ORDER BY clause, you must put the condition ports first. CMN_1702 Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number> <error message>. (UNIX only) Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1703 Error attaching to system shared memory <ID> for <Load Manager Shared Memory> at address <address>. System error is <error number>. (Windows only) Cause: The address you specified in the Shared Memory Base Address is already in use. Action: Change the address in the Integration Service configuration. CMN_1704 Error attaching to system shared memory <ID> for <Load Manager Shared Memory>. Expected to attach at address <address>, but attached at <address>. Cause: Internal error. Action: Contact Informatica Technical Support. 126 Chapter 12: CMN Messages
- 143. CMN_1705 Error attaching to system shared memory <ID> because it has been removed. Cause: The Load Manager terminated unexpectedly. Or the system shared memory was manually removed using the ipcrm command. Action: Restart the Integration Service. CMN_1715 The lookup query <Lookup transformation> contains character(s) that is(are) not valid in the codepage of the database connection. The invalid character starts at position <character position> of the query. Cause: The lookup query contains one or more characters that are not encoded in character set of the lookup database code page. Action: Identify the invalid character referenced in the session log. Edit the lookup query so that it contains characters encoded in the character sets of both the Integration Service code page and the lookup database code page. You can also configure the lookup database to use a code page that contains encoding for the lookup data character set and is compatible with the Integration Service code page. or Cause: The lookup database uses a code page that is not supported by PowerCenter. Action: Select a code page for the lookup database that is supported by PowerCenter and contains encoding for the lookup data character set. CMN_1720 The persistent lookup cache was created in a format that is incompatible with this release. Cause: You upgraded a session using a persistent lookup cache and the Integration Service ran it for the first time since the upgrade. Action: None. The Integration Service rebuilds the cache from the lookup table. CMN_1764 Failed to delete file <filename>: Error Msg <error message>. Cause: The Integration Service could not delete the specified cache file. Action: Check the additional error message for more information. CMN_1765 Failed to open file <filename>: Error Msg <error message>. Cause: The Integration Service could not open the specified cache file. Action: Check the additional error message for more information. CMN_1766 Failed to seek file <filename>: Error Msg <error message>. Cause: Operating system error. Action: Contact your internal technical support. CMN Messages 127
- 144. CMN_1767 Failed to ftell file <filename>: Error Msg <error message>. Cause: Operating system error. Action: Contact your internal technical support. CMN_1768 Failed to truncate file <filename>: Error Msg <error message>. Cause: The Integration Service could not truncate the specified cache file. Action: Check the additional error message for more information. CMN_1769 Inconsistent recovery cache. Cause: The Integration Service cannot run the session enabled for recovery because the recovery cache file does not contain valid data. Action: Delete all recovery cache files associated with the session and run the session with recovery disabled to create a new cache file. To determine which recovery cache file is associated with the session, compare the time at which the file was last modified with the time the session failed. If the times are the approximately the same, you can associate the cache file with the session. You can also refer to the cache file names to determine which files are associated with the session. Recovery cache file names use the following format: pmgmd_metadata_<repository ID>_<workflow ID>_<folder ID>_<session ID>_<transformation ID>_<partition ID>_<group ID>_<checkpoint ID>_<sequence number>.dat For example, in the following file name, the session ID is 102: pmgmd_metadata_7661f424_379f_11d7_947e_f63b53abfef7_103_2_102_0_0_ 0_1_1.dat Use the REP_LOAD_SESSIONS MX View on the repository database to determine the name of the session associated with the session ID. You can use REP_LOAD_SESSIONS to view information about reusable sessions. CMN_1770 Recovery cache consumer is registered more than once. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1771 The connection [database connection] specified is ambiguous. The connection name exists in both relational and application connections. Cause: In the Location Information session property for a Lookup transformation, or the Connection Information session property for a Stored Procedure transformation, you specified a database connection name that exists as both a Relational and Application database connection. When the Integration Service runs the session, it cannot determine which connection to use. 128 Chapter 12: CMN Messages
- 145. This might occur when you specify the database connection name for the transformation in the Designer and then create a session using the mapping. Or, this might occur when you type the connection name in the session property. Action: In the session properties, select the correct database connection name for the Lookup or Stored Procedure transformation. CMN_1772 Guaranteed Message Delivery cache directory <directory name> does not exist. Cause: The Integration Service cannot find the cache file directory for message recovery. Action: Verify that the cache file directory exists. Specify the correct path to the cache file directory in the session properties. If the cache file directory does not exist, create a directory and specify a directory path in the session properties. CMN_1773 Error: Logical connection [database connection] in cache header file [lookup cache file.dat] used by Lookup [Lookup transformation name] is either an invalid connection or it exists in both Relational and Application type connections. Cause: In a cached Lookup transformation in the Designer, you specified a database connection name that exists as both a Relational and Application database connection in the Workflow Manager. When the Integration Service runs the session, it cannot determine which connection to use. Action: In the session properties, select the correct database connection name for the Lookup transformation. Or, you can enter โRelational:โ before the connection name if it is a Relational connection, or type โApplication:โ before the connection name if it is an Application connection. CMN_1774 Error: Logical connection [database connection] in Lookup [Lookup transformation name] is either an invalid connection or it exists in both Relational and Application type connections. Same as CMN_1773. CMN_1775 Recovery cache directory <directory name> is invalid. Cause: The name for the recovery cache folder is not valid. Action: From the Properties settings on the sources tab in the session properties, specify a valid path for the recovery cache folder. CMN_1777 The connection [database connection name] specified can not run SQL query; hence can not be used as a lookup or stored procedure connection. Cause: For a Lookup or Stored Procedure transformation, you selected an Application database connection type that is not a relational database. CMN Messages 129
- 146. Action: Select a Relational database connection, or select an Application database connection based on a relational database, such as a PeopleSoft connection. CMN_1778 Failed to read file <file>: Error Msg <error message>. Cause: The Integration Service failed to read data from the specified cache file. Action: Check the additional error message for more information. CMN_1779 Failed to write file <file>: Error Msg <error message>. Cause: The Integration Service failed to write data to the specified cache file. Action: Check the additional error message for more information. CMN_1780 Guaranteed Message Delivery timestamp was changed, message cache will be cleaned and session will continue running. Cause: This is an informational message. The mapping or the session properties in the Task Developer have changed since the last session run. The message recovery cache will be deleted and the session will continue to run. Action: None. CMN_1781 Error: A connection must be specified for $Target when using 3.5 LOOKUP function. Cause: An expression in the mapping uses the LOOKUP function and you did not specify a database connection for the $Target Connection Value session property. Action: On the General Options settings of the Properties tab in the session properties, enter a database connection for the $Target Connection Value property. When you create a session based on a mapping that uses the LOOKUP function, you must specify the database connection for either the $Source Connection Value or $Target Connection Value in the session properties. CMN_1782 Error: A connection must be specified for $Source when using 3.5 LOOKUP function. Cause: An expression in the mapping uses the LOOKUP function and you did not specify a database connection for the $Source Connection Value session property. Action: On the General Options settings of the Properties tab in the session properties, enter a database connection for the $Source Connection Value property. When you create a session based on a mapping that uses the LOOKUP function, you must specify the database connection for either the $Source Connection Value or $Target Connection Value in the session properties. 130 Chapter 12: CMN Messages
- 147. CMN_1784 Connect string [connection name in Location Information property] too long. Maximum length allowed is <maximum length>. Cause: In the Location Information session property for a Lookup transformation, you specified a database connection name that is too long. Action: Edit the database connection name in either the Relational or Application Connection Browser. CMN_1785 Lookup SQL override [Lookup transformation] has references to mapping parameters or variables that cannot be resolved correctly. Cause: You referenced a mapping parameter or variable in the lookup SQL override, but the Integration Service could not resolve the parameter or variable to text. Action: Edit the lookup SQL override and verify you spelled the mapping parameter or variable correctly. Also, verify you declared the mapping parameter or variable in the mapping. CMN_1786 Error: Failed to update row for Lookup [Lookup transformation]. Cause: The Integration Service failed to update the row in the dynamic lookup cache. Action: Check the session log for related error messages. 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. Cause: The Integration Service encountered an error when writing to the server log file, most likely because the machine that hosts the server log file ran out of disk space. Any messages related to the task the Integration Service was performing at the time may have been lost. Action: Check the available space on the machine that hosts the server log file. 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. Cause: You configured two Lookup transformations in a mapping to share a named cache, but you configured only one transformation for cache partitioning. The Integration Service cannot share a partitioned cache with a non-partitioned cache. Action: Edit the session properties and configure either both Lookup transformations with a hash auto-keys partition point or neither with a hash auto-keys partition point. or Action: Edit the mapping so that the Lookup transformations do not share a cache. or CMN Messages 131
- 148. Cause: You configured two Lookup transformations in separate target load order groups to share a named cache, but you configured a different number of partitions for the target load order groups. Action: Edit the session properties and configure the same number of partitions for each Lookup transformation. or Action: Edit the mapping so that the Lookup transformations do not share a cache. CMN_1801 Error: Lookup <Lookup transformation name> and Lookup <Lookup transformation name> with cache file name prefix <prefix name> are setup for partitioned cache but have condition columns in different order. Cause: You added hash auto-keys partition points to two Lookup transformations that are configured to share a named cache, but the condition columns for the transformations do not match. When you use cache partitioning with a named cache, the condition columns in the Lookup transformations must be identical and in the same order. Action: Remove the hash auto-keys partition points from the Lookup transformations. or Action: Configure the Lookup transformations with identical condition columns. Verify that they are in the same order. CMN_1802 ERROR: Some cache files with name prefix [name prefix] for Lookup [Lookup transformation name] are missing or invalid. Cause: You ran a session with multiple partitions that uses a named persistent lookup cache, but the Integration Service cannot access some of the cache files. Action: Verify the Integration Service can access all cache files for each partition. Or, remove all existing persistent named cache files and run the session again. If all named persistent cache files do not exist, the Integration Service rebuilds the persistent cache files. CMN_1804 Cache cannot be empty when running in recovery mode. Cause: You enabled recovery for a session. The session failed during the session run. Before you started the recovery session, the cache was emptied. This is not allowed. Action: When a session configured for recovery fails, make sure that the cache is not emptied before starting the recovery session. CMN_1806 Failed to get information for file <cache file>. Error message: <error message>. Cause: The Integration Service could not read the recovery cache file. Action: See the additional error message for more information. 132 Chapter 12: CMN Messages
- 149. CMN_1807 Cache version does not match with <version>. Cause: You enabled recovery for a session. The session failed during the session run. Before you started the recovery session, the cache folder was modified. This is not allowed. Action: When a session configured for recovery fails, make sure that the cache file is not modified before starting the recovery session. CMN_1808 Cache platform does not match with <platform>. Cause: You enabled recovery for a session. The session failed during the session run. Before you started the recovery session, the recovery cache was moved to a different platform. For example, you ran a session on Windows to read messages from a TIBCO source. After the session failed, the recovery cache was moved to a UNIX platform. You tried to run the session in recovery mode on UNIX. This is not allowed. Action: Run sessions in recovery mode on the same platform as the initial session. CMN_1809 Partition number does not match with <number>. Cause: You enabled recovery for a session. The session failed during the session run. Before you started the recovery session, the number of partitions for the session changed. This is not allowed. Action: When a session configured for recovery fails, make sure that the number of partitions does not change before starting the recovery session. CMN_1836 Error: Data for Lookup fetched from the file is not sorted on the condition ports. Cause: You ran a flat file lookup session configured for sorted input, but the data for the condition columns is not grouped. Action: Clear the sorted input option in the Lookup transformation. or Action: Ensure that data in the condition columns are grouped. CMN_1919 External loader error. Error getting Teradata loader information. Cause: The Integration Service could not fetch information from the repository to build the Teradata control file. Action: Verify the Integration Service machine can connect to the Repository Service machine and that the Repository Service machine can connect to the repository. Verify the repository machine is plugged in and connected to the network. CMN_1920 External loader error. Error getting Flat-File information required for Loader. Same as CMN_1919. CMN Messages 133
- 150. CMN_1921 External loader error. Control File will be generated for First Partition Only. Cause: You tried to override the control file for a partition other than the first partition in the Teradata target definition. The Integration Service only uses the control file specified in the first partition when you create multiple partitions in a session that uses Multiload or FastLoad to load to Teradata. Action: Verify the control file in the first partition of the session uses the attributes you want for the session. CMN_1922 External loader error. Update is not valid for target instance [target definition name] since no primary key(s) is mapped to the target. Cause: The Teradata target table does not have a primary key, so the Integration Service cannot generate a control file and update the target. Action: Define a primary key on the target table and run the session again. CMN_1923 External loader error. Update is not valid for target instance [target definition name] since no non-key field(s) is mapped to the target. Cause: The primary key column in the Teradata target definition is not connected to an upstream transformation in the mapping. The Integration Service cannot generate a control file and cannot update the target. Action: Connect the primary key column in the Teradata target definition to an upstream port in the mapping. Run the session again. CMN_1924 External loader error. Delete is not valid for target instance [target definition name] since no primary key(s) is mapped to the target. Same as CMN_1923. CMN_1925 The server does not support delimited files with the Teradata external loaders. Cause: The session uses a delimited flat file target to load data to the Teradata target using FastLoad, Multiload, or TPump. Action: Edit the session properties and configure the Teradata target to use a fixed- width flat file. CMN_1926 Error: Teradata external loader requires a primary key on table [target table name] when using load mode [load mode]. Cause: The Teradata external loader connection uses the specified load mode, such as update or upsert, but the target table has no primary key. The target table must have a primary key for the Integration Service to use this load mode. Action: Define a primary key on the target table and run the session again. 134 Chapter 12: CMN Messages
- 151. CMN_1927 Error: Unable to set null character. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_1928 External loader error. Upsert is not valid for target instance [target definition name] since update is not valid for the target. Cause: The Integration Service cannot perform upserts on the Teradata target table. Action: Verify the target table has a primary key and that the primary key column in the target definition is connected to an upstream transformation. CMN_1929 External loader error [error message]. Cause: The Integration Service cannot generate the Teradata control file because some control file option values are missing, such as the TPDID value. Action: Edit the external loader connection in the session and enter a value for all options. CMN_1986 Service <service name> encountered an error while communicating with Licensing Service: <error code and message>. Cause: The service encountered an error while communicating with the Licensing Service. Action: See the additional error message for more information. CMN_1989 Service <service name> is not licensed to execute on node <node name>. Cause: The service is not licensed to run on the operating system of the node. Action: Get a license to run the service on the operating system. or Action: Configure the service to run on a different node that has the appropriate license. CMN_2005 Unable to create log file <log file name>: <error>. Cause: The log directory is not valid or does not have enough disk space. Action: Verify the path and the directory for $PMWorkflowLogDir and $PMSessionLogDir in the Integration Service configuration, workflow properties, and session properties. The user who starts the Informatica Service on the node must have permissions to write to the directory. or Action: Create a small file in the log directory to ensure that you are not out of disk space. CMN Messages 135
- 152. CMN_2006 Unable to create log file <log file name>. Cause: The log directory is not valid or does not have enough disk space. Action: Verify the path and the directory for $PMWorkflowLogDir and $PMSessionLogDir in the Integration Service configuration, workflow properties, and session properties. The user who starts the Informatica Service on the node must have permissions to write to the directory. or Action: Create a small file in the log directory to ensure that you are not out of disk space. CMN_2018 Error: Failed to expand call text <text> for Stored Procedure transformation <transformation name>. Cause: The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure. Action: Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. or Cause: The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure due to an internal error. Action: Contact Informatica Technical Support. CMN_2028 The Integration Service cannot parse user variable at position <user variable position> in file <file>. Cause: The Integration Service cannot find a value for the user variable in the specified position in the control file. Action: In the connection object attributes, verify that the user variable is defined and contains the correct syntax. CMN_7136 Error: At Transformation [transformation name]. One of the concatenating pipelines contains a Transaction Control Transformation. This mapping is no longer valid since TCT is an active transformation. Please move the TCT before or after the concatenation. Cause: The upgraded mapping contains a pipeline branch with a Transaction Control transformation that concatenates with another branch in the same pipeline. This mapping is no longer valid in PowerCenter. Action: Edit the mapping and move the Transaction Control transformation either before or after the concatenation. 136 Chapter 12: CMN Messages
- 153. CMN_17800 Property <property name> is missing. Cause: A required property for a Custom transformation does not exist. You may have modified the transformation. Action: If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again. or Action: If you received this error for an RFC/BAPI function mapping, regenerate the mapping. CMN_17802 <Input/output port> port for <port number> not found. Cause: The Integration Service cannot find a column in a Custom transformation. You may have modified the transformation. Action: If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again. or Action: If you received this error for an RFC/BAPI function mapping, regenerate the mapping. CMN_17804 Port <port number>: The transformation type <transformation datatype> is incompatible with SAP type <SAP datatype>. Cause: The transformation datatype and SAP datatype are not compatible for the specified transformation. You may have modified the transformation. Action: If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again. or Action: If you received this error for an RFC/BAPI function mapping, regenerate the mapping. CMN_17807 Data conversion error for port <port number> with data <data>. Cause: The Integration Service received data from the SAP system. The SAP system may have sent data with a precision or scale that is too large. Action: Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port. or Cause: The data contains inconsistencies. Action: Contact Informatica Technical Support. CMN Messages 137
- 154. CMN_17808 Data conversion error for port <port number>. Cause: The Integration Service received data from the SAP system. The SAP system may have sent data with a precision or scale that is too large. Action: Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port. or Cause: The data contains inconsistencies. Action: Contact Informatica Technical Support. CMN_17809 Message from SAP LastError: <error message>. Cause: SAP error. Action: See the additional error message for more information. CMN_17810 Property <property> is invalid. Cause: The SequenceID or the Function Name property in the Custom transformation is invalid. Action: If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again. or Action: If you received this error for an RFC/BAPI function mapping, regenerate the mapping. CMN_17815 Memory allocation error. Cause: Out of memory error. Action: Contact your internal technical support. CMN_17816 Error when trying to install SAP structure <structure>. Cause: Internal error. Action: Contact Informatica Technical Support. CMN_17817 Connection to SAP system is lost. Cause: Due to the length of the PowerCenter session, the SAP connection may have timed out. Action: Restart the session. CMN_17818 Error in appending a line to SAP internal table. Cause: Internal error. Action: Contact Informatica Technical Support. 138 Chapter 12: CMN Messages
- 155. CMN_17825 The value for property <property> is not specified. Cause: There is no value for the specified property. Action: If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again. or Action: If you received this error for an SAP/ALE IDoc Prepare transformation, view the transformation properties to see if it has the required value for the specified property. Or, create the transformation again. or Action: If you received this error for an RFC/BAPI function mapping, regenerate the mapping. CMN_17826 Failed to get connection information from the mapping parameter with name <mapping parameter name>. Cause: The $$SAPCONNECTION mapping parameter in the RFC/BAPI function mapping contains an invalid value. The parameter refers to an RFC/BAPI Interface application connection that does not exist in the repository. Action: Create an RFC/BAPI Interface application connection using the name provided in the mapping parameter. CMN_17829 Failed to connect to SAP system. Cause: The Integration Service could not connect to the SAP system because the SAP RFC/BAPI Interface or SAP_ALE_IDoc_Writer application connection contains invalid values for several connection attributes. Action: Verify that the application connection contains valid values for the User Name, Password, and Connect String attributes. CMN_17831 Incorrect source file name may have been specified in the session. Cause: The source file name specified for the 6.x IDoc_Writer AEP transformation may be incorrect. Action: Verify that the source file name is correct. CMN_17833 Binary datatypes are not supported in RFC/BAPI function mappings. Disconnect port <port name> in the mapping. Cause: The binary datatypes PREC and LRAW are not supported in RFC/BAPI function mappings. If a port uses these datatypes, you cannot connect it in the mapping. Action: Disconnect the specified port. CMN Messages 139
- 156. CMN_17838 SAP code page <code page> is not compatible with the connection code page <code page>. Cause: The code page specified in the SAP RFC/BAPI Interface application connection is not compatible with the SAP server. Action: Verify that the code page entered for the application connection is compatible with the SAP server. CMN_17839 SAP code page <code page> is not compatible with the Integration Service code page. Cause: The code page specified for the Integration Service is not compatible with the SAP server. Action: Verify that the Integration Service code page is compatible with the SAP server. CMN_17840 Data <data> overflow at port <port number>. See below to find the row with error. Cause: The Integration Service encountered a row error. As a result, the session failed. Action: See the session error log to determine the row that contains the error and view more information about the error. CMN_17848 The value for the property [TypeOfAEP] should be <value>. Cause: The 6.x IDoc_Writer AEP transformation contains an invalid value for the TypeOfAEP property. Action: Enter the specified value for the TypeOfAEP property. CMN_17851 Cannot get target property <property>. Cause: Internal error. or Cause: The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. CMN_17853 Error threshold for the session is reached. Cause: The Integration Service has reached the error threshold configured in the session properties. Action: Eliminate the errors in your data. or Action: Increase the error threshold. 140 Chapter 12: CMN Messages
- 157. CMN_17856 Control field <control field> cannot have length greater than the precision <value>. Cause: The length of the control field exceeds the precision set for it. Action: Eliminate the error in your data. or Action: Increase the precision for the control field. CMN Messages 141
- 158. 142 Chapter 12: CMN Messages
- 159. Chapter 13 CNF Messages This chapter includes the following topic: โฆ CNF Messages, 144 Error messages listed numerically. 143
- 160. CNF Messages Information forthcoming. 144 Chapter 13: CNF Messages
- 161. Chapter 14 CNX Messages This chapter includes the following topic: โฆ CNX Messages, 146 Error messages listed numerically. 145
- 162. CNX Messages CNX_53119 Thread received a notification to force the closing of client connection. Cause: A repository connection ended because a repository or domain administrator terminated the repository connection. Action: Verify that the administrator does not need to have all users disconnected from the repository for maintenance or other purposes. Then retry the operation in the PowerCenter Client. 146 Chapter 14: CNX Messages
- 163. Chapter 15 CSE Messages This chapter includes the following topic: โฆ CSE Messages, 148 Error messages listed numerically. 147
- 164. CSE Messages CSE_34005 The Integration Service could not set the encryption key for encryption. Cause: The Integration Service could not set the encryption key for AES_ENCRYPT. An error occurred in the Advanced Encryption Standard (AES) algorithm. The error may occur because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to encrypt. CSE_34010 The Integration Service could not set the encryption key for decryption. Cause: The Integration Service could not set the encryption key for AES_DECRYPT. An error occurred in the Advanced Encryption Standard (AES) algorithm. The error may occur because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to decrypt. CSE_34039 The Integration Service failed to decrypt data. Cause: The Integration Service could not decrypt the data because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to decrypt. CSE_34040 The Integration Service failed to encrypt data. Cause: The Integration Service could not encrypt the data because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to encrypt. CSE_34041 The Integration Service failed to compress data. Cause: The Integration Service could not compress the data because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to compress. CSE_34042 The Integration Service failed to decompress data. Cause: The Integration Service could not decompress the data because of low system resources or an out of memory error. Action: Run the session again. If the error persists, contact Informatica Technical Support and provide the data you are trying to decompress. 148 Chapter 15: CSE Messages
- 165. Chapter 16 CTSDK Messages This chapter includes the following topic: โฆ CTSDK Messages, 150 Error messages listed numerically. 149
- 166. CTSDK Messages CTSDK_43000 Couldn't load the library <library name> for plug-in <plug-in name>. Cause: The plug-in has been installed incorrectly or is not compatible with the PowerCenter version. Action: Reinstall the plug-in. CTSDK_43001 Couldn't load the library <library name>. Cause: PowerCenter could not load the specified library for the Custom transformation. The library or dependent libraries may not be in the proper directory. Action: Verify that the library and any dependent library is in the proper directory. CTSDK_43002 Couldn't find address of function <function name> for plug-in <plug-in name>. Cause: The function for the plug-in is not defined or is incorrectly defined. Action: Reinstall the plug-in. CTSDK_43003 Couldn't find address of function <function name>. Cause: PowerCenter could not load the specified function for the Custom transformation. Action: Verify that the library and any dependent library is in the proper directory. or Action: Rebuild the library. 150 Chapter 16: CTSDK Messages
- 167. Chapter 17 DBGR Messages This chapter includes the following topic: โฆ DBGR Messages, 152 Error messages listed numerically. 151
- 168. DBGR Messages DBGR_25011 No conversion to string possible. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25013 Cannot modify dependent port. Cause: You tried to modify a generated key or other dependent ports. Action: Contact Informatica Technical Support. DBGR_25015 Field not found. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25016 Default condition allowed on input, in/out or output ports only. Cause: IsDefault conditional breakpoint is not allowed on other ports, such as variable ports. Action: Use the IsDefault breakpoint condition on input, input/output, and output ports only. DBGR_25017 Parser init failed. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25018 Invalid port condition. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25019 Breakpoint already exists. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25020 Breakpoint not found. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25021 No such target ID. Cause: Internal error. Action: Contact Informatica Technical Support. 152 Chapter 17: DBGR Messages
- 169. DBGR_25022 Alloc Bkpt list failed. Cause: Out of memory. Action: Check memory usage of the machine. Other processes may be using too much memory. You might want to increase swap space. DBGR_25024 Cannot modify data for transformations at this stage of execution. Cause: Internal error. You tried to modify a port during an error breakpoint. Action: Contact Informatica Technical Support. DBGR_25025 Cannot modify data for transformations other than the current one. Same as DBGR_25024. DBGR_25026 Rowtype change not allowed for this transformation. Cause: You tried to change the row type for this transformation to something other than Filter, Data Driven, or Router. Action: You can only change the row type for Filter, Router, and Update Strategy transformations. DBGR_25027 Cannot modify port. Cause: You tried to modify a read-only port. Action: You cannot modify a read-only port. DBGR_25028 Use of port <port name> in debug condition is invalid. Maybe it is not connected. Cause: You specified an unconnected port in the port column of the condition for a breakpoint. Action: An unconnected port either has a default value if it is specified, or it always has a null value. Do not specify the value in a debug condition. Either make a connection to that port or choose a connected port. DBGR_25029 Use of port <port name> as value in debug condition is invalid. Maybe it is not connected. Cause: You specified an unconnected port in the value column of the condition for a breakpoint when the type column is port. Action: An unconnected port either has a default value if it is specified, or it always has a null value. Do not specify the value in a debug condition. Either make a connection to that port or choose a connected port. DBGR_25030 No such transformation in any pipeline. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR Messages 153
- 170. DBGR_25033 Error: Socket sendRequest for ident failed for reqType: <number>. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25034 Error: Socket set poll failed for reqType: <number>. Cause: Internal error. Action: Contact Informatica Technical Support. 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. Cause: The DTM could not connect to the Designer due to the Integration Service timeout. Action: Increase the timeout value for the Integration Service connection in the Workflow Manager and run session again. DBGR_25036 Error: Socket open failed for reqType: <number>. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25040 Error: Invalid groupId <number> specified for modifying router transformation. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25041 Error: Invalid groupIndex <number> resulted from groupId <number> specified for modifying Router transformation. Cause: Internal error. Action: Contact Informatica Technical Support. DBGR_25044 Data Type mismatch: <value> cannot be used in a condition with port <port name>. Cause: You entered an invalid value for the port datatype for a conditional breakpoint. Action: Make sure the value is in the correct format: MM/DD/YYYY hh:mm:ss. DBGR_25045 Error in breakpoint condition: Port <port name> and Port <port name> are from different groups. Cause: You used ports from different groups when setting a conditional breakpoint using two ports. A Normalizer or an XML Source Qualifier transformation 154 Chapter 17: DBGR Messages
- 171. have ports organized in different groups. The Integration Service reads data from these ports one group at a time. Action: Do not use ports from different groups to set the conditional breakpoint. DBGR_25046 Error in breakpoint <number> for transformation <transformation name>. Reason is <reason>. Cause: Error in setting global breakpoint. Action: Check the reason for details. DBGR_25047 Error in global breakpoint <number>. Reason is <reason>. Cause: Error in setting global breakpoint. Action: Check the reason for details. DBGR_25048 Breakpoint condition cannot be specified for binary port <port> <port name>. Cause: You tried to specify a conditional breakpoint using a binary port. Action: Do not specify a conditional breakpoint for a binary port. DBGR_25049 Transformation has not received any data yet. Cause: You tried to evaluate an expression before the Integration Service received data. Action: Wait for a row of data to move into the transformation before evaluating an expression. DBGR_25050 Port <port name> used in expression is unconnected and has no default value. Cause: You tried to evaluate an expression using a port that is unconnected and has no default value. An expression port never receives a value. Action: Check to see if a port connection was deleted. Do not use this port in any expression evaluation. Or, pass a value to the port through a valid connection. DBGR_25059 Failed to create a socket to listen for connections from the client <PowerCenter Client machine name>. Cause: The Integration Service could not create a socket for Debugger connections. The PowerCenter Client machine may have failed during the connection. Action: Restart the Debugger session. DBGR_25060 Failed to find an available port between <DebuggerMinPort> and <DebuggerMaxPort> to listen for connections from the client <PowerCenter Client machine name>. Cause: The Integration Service could not find an available port for Debugger connections. DBGR Messages 155
- 172. Action: Stop other Debugger sessions or wait for those sessions to complete before you restart the current Debugger session. or Action: Increase the DebuggerMaxPort value to provide additional ports for Debugging on the Integration Service. DBGR_25061 Failed to notify client of the port we are listening on. Cause: The Integration Service could not connect to the PowerCenter Client machine. Action: Restart the Debugger session. DBGR_25062 Failed to notify client of the port we are listening on: no RepServer connection is available. Cause: The Integration Service could not connect to the Repository Server or lost the connection to the PowerCenter Client machine. Action: Restart the Debugger session. DBGR_25068 Failed to get connection from the Designer. Check network/firewall settings. Cause: The Integration Service timed out while waiting for the connection from the PowerCenter Client. Action: Check your network and firewall settings. Increase the timeout value for the Integration Service connection and restart the Debugger session. 156 Chapter 17: DBGR Messages
- 173. Chapter 18 DCF Messages This chapter includes the following topic: โฆ DCF Messages, 158 Error messages listed numerically. 157
- 174. DCF Messages Information forthcoming. 158 Chapter 18: DCF Messages
- 175. Chapter 19 DMI Messages This chapter includes the following topic: โฆ DMI Messages, 160 Error messages listed numerically. 159
- 176. DMI Messages DMI_17501 Error initializing the tree builders for partition <partition>. Cause: The metadata file used to create the SAP DMI Prepare transformation may be invalid. Action: Recreate the SAP DMI Prepare transformation. DMI_17503 At least one field other than primary and foreign keys must be connected for each group. Cause: Only primary and foreign keys are connected. At least one other port must be connected. Action: Connect at least one port per group other than the primary and foreign keys. DMI_17504 Error creating input row for group <group>. Cause: There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP DMI Prepare transformation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. DMI_17505 Error setting data for the field: <field>. Same as DMI_17504. DMI_17506 NULL data obtained for primary or foreign key fields. Cause: The data for the primary or foreign key is missing. Action: Make sure the data contains primary and foreign key values. DMI_17507 NULL data obtained for all connected fields for the segment <segment name>. Cause: The data for all connected fields is missing for the named segment. Action: Make sure the data exists for all connected fields for the named segment. DMI_17508 Error building the tree. Same as DMI_17504. DMI_17509 Unknown error traversing the tree. Same as DMI_17504. DMI_17511 <Number> orphan rows were received by the SAP DMI Prepare transformation. Cause: The SAP DMI Prepare transformation received orphan rows. Action: Make sure that all child rows have parent rows. 160 Chapter 19: DMI Messages
- 177. DMI_17512 Orphan row <row> received in group <group> with primary key <primary key> and foreign key <foreign key>. Cause: The SAP DMI Prepare transformation received orphan rows. Action: Make sure that all child rows have parent rows. DMI_17513 <Value> duplicate rows were received by the SAP DMI Prepare transformation. Cause: The DMI Prepare transformation received duplicate rows. Action: Eliminate the duplicate rows in your data. DMI_17514 Primary key received for duplicate error row <row>: <value>. Cause: The DMI Prepare transformation received duplicate rows. Action: Eliminate the duplicate rows in your data. DMI_17515 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>. Cause: You configured the session to validate DMI documents before writing them to the SAP system. During the session, the Integration Service determined that a value for the mandatory segment in the DMI document is missing. Action: Verify that the SAP DMI Prepare transformation for the DMI document contains values for the mandatory segment. 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>. Cause: You configured the session to validate DMI documents before writing them to the SAP system. During the session, the Integration Service determined that the segment contains more than the maximum number of records allowed. Action: Correct the source data so that the number of records for the segment does not exceed the maximum number of records allowed. DMI_17517 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because minimum occurrence is less than the minimum limit for: <value>. Cause: You configured the session to validate DMI documents before writing them to the SAP system. During the session, the Integration Service determined that the segment contains less than the minimum number of records allowed. Action: Correct the source data, so that the number of records for the segment meet at least the minimum number of records allowed. DMI Messages 161
- 178. 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. Cause: The SAP DMI Prepare transformation received data that is larger than the precision for the row. Action: Correct the source data so that the value matches the precision for the row. DMI_17519 Error getting data for the field. Same as DMI_17504. DMI_17520 The SAP DMI Prepare transformation has an unconnected input group. All input groups must be connected for the transformation. Cause: An input group does not have any connected ports. Action: Make sure that at least one port for each input group is connected. DMI_17525 Cache folder specified for the SAP DMI Prepare transformation <transformation name> is invalid. Cause: The cache directory specified for the SAP DMI Prepare transformation does not exist. Action: In the session properties, enter a valid directory for the Cache Directory property. DMI_17526 The Integration Service could not access the cache block in group <group>. Increase the cache size. Cause: The cache size specified for the SAP DMI Prepare transformation is inadequate. Action: In the session properties, increase the cache size. DMI_17527 The SAP DMI Prepare transformation did not receive data for the DMI object. Cause: The source in the DMI mapping does not contain valid data for the DMI object. Action: Verify that the source data is valid. 162 Chapter 19: DMI Messages
- 179. Chapter 20 DOM Messages This chapter includes the following topic: โฆ DOM Messages, 164 Error messages listed numerically. 163
- 180. DOM Messages DOM_10009 Cannot find the specified domain <linked domain name> from domain <current domain name>. Cause: The Service Manager cannot find the domain name that is specified in the lookup request. The domain information may be out of date, or the requested domain may not be running. Action: Verify that the domain information in the domain is up to date. Also, verify that the linked domain in the lookup request is running. DOM_10166 Unable to login node <node name> with the domain. Cause: The node failed to log in to the domain. Action: Fix the problem described in the subsequent message and restart the node. DOM_10174 Unable to update the operating mode to <operating mode> on service <service name>. Cause: The domain failed to up date the service configuration. Action: Make sure the service configuration is valid in the domain. DOM_10176 Unable to queue the alert of type <alert type> for object <object name> with alert message <alert message> to the alert service. Cause: The domain failed to connect to the alert service. Action: Restart the master gateway node. DOM_10181 Unable to communicate with node <node name> at host <host name> and port <port number> from the master node <node name>. Cause: The master node cannot communicate with the node in the domain. The node may be behind a fire wall that is not accessible from the master gateway node. Action: Reconfigure network so the node is accessible from the master gateway node. DOM_10182 The runtime state change from <original runtime state> to <requested runtime state> is invalid for service <service name> on service process <node the service process is running on>. Cause: An invalid value has been entered for the run-time state. Action: Shut down the domain, and then start Informatica Services on the gateway nodes and worker nodes. 164 Chapter 20: DOM Messages
- 181. Chapter 21 DP Messages This chapter includes the following topic: โฆ DP Messages, 166 Error messages listed numerically. 165
- 182. DP Messages DP_90001 Invalid target type. Profile mapping targets should either be relational or null. Cause: The profile mapping contains target definitions that are not relational or null. The targets in the profile mapping might have been modified. Action: Recreate the profile. DP_90002 All the targets in a profiling mapping should use the same connection and have the same connection attributes. Cause: There are two or more relational database connections configured for targets in the profile mapping. Action: Make sure you use the same relational database connection for all targets in a profiling mapping. DP_90003 Create server database connection failed. Cause: The database driver might not be set up correctly. Action: Check the database driver configuration. DP_90004 Connection to the database using user <user name>, connect string <database connect string> failed. Reason: <error message>. Cause: The user name or connect string is invalid. Action: Verify that the user name and connect string values are valid. or Action: See the additional error message for more information. DP_90005 Cannot find the profile object for this mapping. Cause: You ran a session with a copied or deployed mapping that contains reusable domains. You cannot run a session with a copied or deployed profile mapping that contains reusable domains. Action: Run a profile session with the original profile mapping. DP_90007 Profile metadata deserialization failed with error <error message>. Cause: The Data Profiling Client or Integration Service installation might be missing a DTD file. The file may have been moved from the PowerCenter Client or Integration Service installation directory. Action: If the PowerCenter Client or Integration Service installation directory does not contain the DTD file, reinstall the Integration Service or Client. If the problem persists, contact Informatica Technical Support. or Cause: The DTD file does not have read permission. 166 Chapter 21: DP Messages
- 183. Action: Verify that you have read permission on the DTD file. DP_90008 Commit to the database failed with error <database error>. Cause: A database error prevents the Integration Service from loading data into Data Profiling warehouse tables. Action: Fix the database error indicated in the message and run the session again. If Data Profiling warehouse tables are incomplete, recreate the Data Profiling warehouse. DP_90009 SQL Prepare failed for statement <SQL statement> with error <database error>. Cause: The SQL query failed. Action: Fix the database error indicated in the message, and rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. DP_90010 SQL Bind failed for statement <SQL statement> with error <database error>. Cause: The Data Profiling warehouse tables are invalid. Action: Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. DP_90011 SQL Execute failed for statement <SQL statement> with error <database error>. Cause: The Data Profiling warehouse tables are invalid. Action: Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. DP_90012 SQL Fetch failed for statement <SQL statement> with error <database error>. Cause: The Data Profiling warehouse tables are invalid. Action: Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. DP_90013 Fetching the key for type <key number> failed. Cause: A Data Profiling warehouse table is missing surrogate keys. The following surrogate keys correspond to these key types in error messages: โ 0 - Profile run key โ 1 - Column key โ 2 - Source function key โ 3 - Column function key โ 4 - Referential Integrity Analysis function key โ 5 - Join Complexity Evaluation function key DP Messages 167
- 184. Action: Rerun the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. or Cause: You attempted to run an existing profile session in an upgraded PowerCenter repository against a new Data Profiling warehouse. Action: Regenerate the profile mapping and run the profile session again. DP_90014 There must be one input group and one output group for this transformation. Cause: The Custom transformation in the profile mapping has been modified and is invalid. Action: Regenerate the profile mapping. DP_90015 The output port <port name> datatype should be long. Cause: The Custom transformation in the profile mapping has been modified and is invalid. Action: Regenerate the profile mapping. DP_90016 The target warehouse is already used for repository <repository name> with GUID <global unique identifier>. Either drop the warehouse tables or use a different one. Cause: You tried to use two repositories for the same Data Profiling warehouse. Action: Create a second Data Profiling warehouse. Also, create a new relational database connection to the second Data Profiling warehouse in the Workflow Manager. DP_90017 The profile warehouse tables are not present in the target database connection. Please check the target connection information. Cause: The Data Profiling warehouse tables are not in the target database. Action: Run the Data Profiling warehouse script in the Data Profiling installation directory. Commit the SQL script after you run it. DP_90019 Failed to get the folder information from repository. Cause: Internal error. Action: Contact Informatica Technical Support. DP_90020 Failed to get the metadata extension <metadata extension> for the mapping. Cause: You copied a profile mapping without copying the metadata extensions. Action: Copy the metadata extensions from the original profile mapping to the copied mapping and run the session again. or 168 Chapter 21: DP Messages
- 185. Cause: You are running a session with an original profile mapping that corresponds to a data profile, but the metadata extensions are deleted. Action: Regenerate the profile mapping. DP_90022 Profile has some invalid functions. Session run failed. Cause: You tried to run a profile session for a data profile. The data profile contains invalid functions. Action: Edit the data profile to modify or remove the invalid functions. DP_90023 Warehouse table PMDP_WH_VERSION is missing. The target warehouse version is incorrect. You may need to upgrade the warehouse. Cause: The version of the Data Profiling warehouse does not match the version of PowerCenter. Action: Upgrade the Data Profiling warehouse using the upgrade script for the database type. DP_90024 The target warehouse uses schema version <version> and data version <version>. You may need to upgrade the warehouse. Cause: The version of the Data Profiling warehouse does not match the version of PowerCenter. Action: Upgrade the Data Profiling warehouse using the upgrade script for the database type. DP_90026 Warehouse table PMDP_WH_VERSION is missing or column SCHEMA_VERSION/DATA_VERSION/DATABASE_TYPE is missing. You need to upgrade the warehouse. Cause: The version of the Data Profiling warehouse does not match the version of PowerCenter. Action: Upgrade the Data Profiling warehouse using the upgrade script for the database type. DP_90029 Source index of mapping parameter <mapping parameter> is invalid. Cause: The profile mapping is modified. Action: Regenerate the profile mapping. DP_90030 Missing mapping parameter(s) for source with index <index>. Cause: The profile mapping is modified. Action: Regenerate the profile mapping. DP_90031 Source Qualifier transformation <transformation> was not found in this mapping. Cause: The profile mapping is modified. DP Messages 169
- 186. Action: Regenerate the profile mapping. DP_90401 Failed to load List of Values from the file <file name>. Cause: You tried to load a domain definition file for a List of Values domain type. However, the file path might be incorrect. Action: Verify the domain definition file path. or Cause: The file does not exist in the specified location. Action: Make sure that the file exists in the specified location. or Cause: The file is empty. Action: Make sure that the domain definition file contains valid entries. DP_90403 List of Values domain cannot be empty. Cause: You tried to load a domain definition file for a List of Values domain type. However, the file might be empty. Action: Make sure that the domain definition file contains valid content. DP_90404 Failed to expand List of Values file <file path>. Cause: You tried to load a domain definition file for a List of Values domain type. However, the domain definition file path contains an unrecognized variable. Action: Check the domain definition file path that you entered. DP_90405 Failed to open Domain definition file <expanded file path>. Cause: You tried to load a domain definition file for a List of Values domain type. However, the domain definition file does not exist in the specified location. Action: Make sure that you place the domain definition file in the file path location that you enter. DP_90406 Fetching Custom transportation input group failed. Cause: Internal error. Action: Contact Informatica Technical Support. DP_90407 Fetching Custom transformation output group(s) failed. Cause: Internal error. Action: Contact Informatica Technical Support. 170 Chapter 21: DP Messages
- 187. DP_90408 Unexpected number of input/output groups received. Cause: You tried to run a session with a copied or deployed profile mapping that contains reusable domains. Action: You must use the original profile mapping. or Cause: You copied a profile transformation to use in another mapping. Action: You must use the original profile mapping. DP_90409 Could not fetch output port <port number>. Cause: You tried to run a session with a copied or deployed profile mapping that contains reusable domains. Action: You must use the original profile mapping. or Cause: You copied a profile transformation to use in another mapping. Action: You must use the original profile mapping. DP_90410 Unexpected number of input/output ports received. Cause: You tried to run a session with a copied or deployed profile mapping that contains reusable domains. Action: You must run a profile session with the original profile mapping if the mapping contains reusable domains. or Cause: You copied a profile transformation to use in another mapping. Action: You must run a profile session with the original profile mapping. DP_90411 Corrupt input received. Cause: You tried to run a session with a copied or deployed profile mapping that contains reusable domains. Action: You must run a profile session with the original profile mapping if the mapping contains reusable domains. or Cause: You copied a profile transformation to use in another mapping. Action: You must run a profile session with the original profile mapping. DP_90603 Regular expression is invalid. Cause: The regular expression is not valid. As a result, the session failed. DP Messages 171
- 188. Action: Edit the Regular Expression function in the data profile and verify the expression against the source data. DP_90604 Unexpected condition encountered. Cause: Internal error. Action: Contact Informatica Technical Support. DP_90802 No input port(s) found for output port <port>. Cause: The profile mapping is modified. Action: Regenerate the profile mapping. DP_90803 Invalid number of input port(s) associated with output port <port>. Cause: The profile mapping is modified. Action: Regenerate the profile mapping. DP_90804 There are input port(s) with no corresponding output port. Cause: The profile mapping is modified. Action: Regenerate the profile mapping. 172 Chapter 21: DP Messages
- 189. Chapter 22 DS Messages This chapter includes the following topic: โฆ DS Messages, 174 Error messages listed numerically. 173
- 190. DS Messages DS_10008 Cannot find node [name] specified in the service lookup request in domain [name]. Cause: The node is not running or does not exist in the domain. Action: Verify that the node is running. Verify that the node name was entered correctly. DS_10009 Cannot find domain [name] specified in the service lookup request. Cause: The command specified a domain gateway machine name and port number, as well as a domain name. The command line program was unable to find the domain on the gateway host machine. Action: Verify the domain exists on the domain gateway host machine. Verify the domain name was entered correctly. DS_10012 The disable mode specified [mode] is invalid to disable service [service name]. Cause: The DisableService command was used to disable the service shown. The mode specified is invalid. Action: Verify the mode is either complete, stop, or abort. DS_10036 Service [name] is not available. Cause: The service specified in the command is not available. Action: Verify the service exists and is running. Verify the service name was entered correctly. DS_10037 Service [name] is not available on node [name]. Cause: The command entered specified a service name and a node name. The service is not available on the node. Action: Verify the service exists and is running on the node. Verify the service name was entered correctly. DS_10059 The requested service [name] is not running. Cause: The service specified in the command is not running or does not exist. Action: Verify the service exists and is running. Verify the service name was entered correctly. 174 Chapter 22: DS Messages
- 191. Chapter 23 DSP Messages This chapter includes the following topic: โฆ DSP Messages, 176 Error messages listed numerically. 175
- 192. DSP Messages DSP_20307 Error fetching node information from Configuration Service (domain name <domain>, node name <node>). Error message: <message text>. Cause: The Integration Service could not fetch node metadata from the Service Manager. Action: Start Informatica Services on the referenced node. Check the error message text for more information about the cause of the failure. 176 Chapter 23: DSP Messages
- 193. Chapter 24 EP Messages This chapter includes the following topic: โฆ EP Messages, 178 Error messages listed numerically. 177
- 194. EP Messages EP_13001 Invalid conversion. Cause: In an external procedure, the Integration Service cannot convert the datatype of the port to the datatype of the corresponding parameter, or vice versa. For example, the port may have a Date/Time datatype, while the parameter has an Integer datatype. The Integration Service cannot convert a Date/Time datatype to an Integer datatype. Action: Either change the external procedure datatype or the port datatype before running the session again. EP_13002 Error freeing external module. Cause: The Integration Service encountered an error while closing a DLL or shared object. Action: This error does not adversely affect the session run. If the message recurs, however, contact Informatica Technical Support. EP_13003 Cannot prepare common external procedure information. Cause: The Integration Service cannot initialize the external procedure. Action: This is a general error message. Check the session log for related error messages. EP_13004 Cannot prepare pipeline external procedure information. Same as EP_13003. EP_13005 Cannot initialize Informatica-style external procedure. Same as EP_13003. EP_13006 NULL external module name. Cause: The entry for the Module/Programmatic Identifier property for the External Procedure transformation is empty. Action: Enter a valid entry for the Module/Programmatic Identifier property. EP_13007 Cannot create external module manager. Cause: The Integration Service cannot create the External Module Manager. Action: This is a general message. Check the session log for related error messages. EP_13008 Cannot load external module. Cause: The Integration Service cannot locate the DLL or considers the DLL invalid. Action: Verify the name, the location of the DLL, and the Module/Programmatic Identifier property before running the session again. 178 Chapter 24: EP Messages
- 195. EP_13010 Cannot create external module object. Cause: The class factory function CreateExternalModuleObject failed to create an external module object in the Informatica external module. Action: Examine the CreateExternalModuleObject function and the constructor for the external module object called within it. EP_13011 NULL external procedure name. Cause: You did not enter the procedure name in the External Procedure transformation. Action: Enter a valid name for the procedure. EP_13012 Cannot get external procedure signature. Cause: A call to the TINFExternal Module Impl::GetProcSignature function failed. Action: Examine this function in the file infemimp.cpp. Also, make sure that the INFEMProcSignatures and the p*ParamVector data structures in the module_nameEM.CPP file have not been altered. EP_13013 Number of ports in transform does not match number of formal arguments. Cause: The Integration Service cannot match the number of ports in an External Procedure transformation with the number of formal arguments in the external procedure. Action: Correct either the number of arguments in the external procedure or the number of ports in the External Procedure transformation before running the session again. EP_13014 Multiple return ports defined for transform. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13015 Multiple return arguments defined for external procedure. Same as EP_13014. EP_13020 External procedure has return value, but transform does not. Cause: The external procedure has a return value, but the External Procedure transformation does not. Action: Either add a return value to the External Procedure transformation or remove it from the external procedure code. EP_13021 Transform has return value, but external procedure does not. Cause: The External Procedure transformation has a return value, but the external procedure does not. EP Messages 179
- 196. Action: Either add a return value to the external procedure code or remove it from the External Procedure transformation. EP_13022 External procedure return value is not last argument. Cause: The external procedure code has a return value, but it is not the last parameter. Action: Make sure the return value of the external procedure code is the last parameter. EP_13023 Transform return value is not last port. Cause: The External Procedure transformation has a return value, but it is not the last port. Action: Make sure the return value of the External Procedure transformation is the last port. EP_13024 Port lookup failed. Cause: An External Procedure transformation port name does not match the corresponding external procedure argument. Action: Change the external procedure argument or the External Procedure transformation port name before running the session again. EP_13025 Not all input params found. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13026 Multiple connections to input port. Same as EP_13025. EP_13027 Decimal overflow error. Cause: The Integration Service encountered an error converting decimal numbers on input to or output from an external procedure. Action: Evaluate the external procedure to see if the Decimal datatype is necessary. If possible, change the Decimal datatype to Double. EP_13028 Unknown error while converting datatype. Cause: This may be an internal error. Action: Send the external procedure to Informatica Technical Support with a description of the error. EP_13030 Exception error was thrown from external procedure <external procedure name>. Cause: The Integration Service encountered a serious exception while running the external procedure. 180 Chapter 24: EP Messages
- 197. Action: Debug the external procedure code before running the session again. EP_13033 Cannot initialize COM-style external procedure. Cause: The Integration Service encountered an error initializing a COM-style external procedure. Action: This is a general error. Check the session log for related error messages. EP_13034 Unknown COM error. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13035 Cannot initialize column/parameter mapping. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13036 Cannot find all input parameters. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13037 Cannot allocate memory. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13038 Cannot initialize external procedure. Cause: The Integration Service encountered an error initializing an external procedure. Action: This is a general error. Check the session log for related error messages. EP_13039 Buffer initialization callback failed. Cause: The Integration Service encountered an error creating buffers. Action: This is a general error. Check the session log for related error messages. EP_13040 Invalid programmatic identifier. Cause: The Integration Service found an invalid programmatic identifier in the registry. Action: Correct the programmatic identifier key in the registry. The key must appear in a two-dot format, such as abc.def. For more information, see your COM documentation. EP Messages 181
- 198. EP_13041 Programmatic identifier not found in registry. Cause: The Integration Service cannot match the programmatic identifier module with its corresponding key in the registry. Action: Either change and compile the module or register the COM.dll in the registry. For more information, see your COM documentation. EP_13042 Cannot map programmatic identifier to CLSID. Cause: In the registry, the programmatic ID does not map to the CLSID. Action: Check the programmatic ID in the registry. For more information, see your COM documentation. EP_13043 Cannot create string representation of CLSID. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13044 Cannot create instance of component object. Cause: The Integration Service call to the CoCreateInstance file failed. Action: Check the CoCreateInstance documentation for action. EP_13045 Cannot get dispatch interface for component object. Cause: The Integration Service encountered an error accessing a COM type library. Action: Contact Informatica Technical Support. EP_13046 IDispatch::Invoke failed. Cause: The Integration Service encountered a major exception in a COM-style external procedure. Action: Debug the external procedure code. EP_13047 Cannot open registry key HKEY_CLASSES_ROOTCLSIDclsidTypelib. Cause: The Integration Service could not find the named key in the registry. Action: In the registry, enter a valid library ID. For more information, see your COM documentation. EP_13048 Cannot get registry value for HKEY_CLASSES_ROOTCLSIDclsidTypelib. Cause: The named key has a registry location, but that location is empty. Action: Enter a valid key at that location. For more information, see your COM documentation. EP_13049 Cannot create CLSID from programmatic identifier. Cause: Internal error. 182 Chapter 24: EP Messages
- 199. Action: Contact Informatica Technical Support. EP_13050 Cannot open registry key HKEY_CLASSES_ROOTTypeLiblibid. Cause: The Integration Service could not find the named key in the registry. Action: In the registry, enter a valid library ID. For more information, see your COM documentation. EP_13051 Cannot open registry key HKEY_CLASSES_ROOTTypeLiblibid. Cause: The Integration Service could not open the named key because it is invalid or not at that location. Action: In the registry, make sure the named key exists at the right location and is a valid key. For more information, see your COM documentation. EP_13052 Cannot load type library. Cause: The Integration Service cannot load the type library because it is not there or because the file is invalid. Action: In the registry, make sure the type library is valid and in the correct location. For more information, see your COM documentation. EP_13053 Cannot get type library attributes. Cause: The Integration Service encountered an error accessing a COM type library. Action: Contact Informatica Technical Support. EP_13054 Cannot open registry key HKEY_CLASSES_ROOTCLSIDclsidserver type. Cause: The Integration Service could not open the named key because it is invalid or not at that location. Action: In the registry, make sure the named key exists at the right location and is a valid key. For more information, see your COM documentation. EP_13055 Cannot get registry value for HKEY_CLASSES_ROOTCLSIDclsid<server type>. Cause: The named key has a registry location, but that location is empty. Action: Enter a valid key at that location. For more information, see your COM documentation. EP_13056 Cannot get component object type information. Cause: The Integration Service encountered an error accessing a COM type library. Action: Contact Informatica Technical Support. EP_13057 Cannot get component object type attributes. Same as EP_13056. EP Messages 183
- 200. EP_13058 Cannot get reference type of interface. Same as EP_13056. EP_13059 Cannot get type information of interface. Same as EP_13056. EP_13060 Cannot get type attributes of interface. Same as EP_13056. EP_13061 Cannot get function description. Same as EP_13056. EP_13062 Cannot get names of function and its arguments. Same as EP_13056. EP_13063 Cannot get IDs of function parameters. Same as EP_13056. EP_13064 Cannot get function type information. Same as EP_13056. EP_13065 NULL BSTR. Cause: A COM external procedure did not allocate memory for a B-String in a COM- style procedure. Action: Allocate more memory for the B-String. EP_13066 Error converting COM datatype to Informatica internal datatype. Cause: The Integration Service encountered an error converting between a COM and Informatica datatype. Either the external procedure attempted an invalid conversion, or a data overflow occurred. Action: Check the session log for messages related to data overflow or invalid datatype conversions. If data overflowed, change your external procedure or mapping to accommodate the data. Otherwise, make sure the external procedure uses valid datatype conversions. EP_13067 Error converting Informatica internal datatype to COM datatype. Same as EP_13066. EP_13068 Unsupported COM type. Cause: The external procedures uses a COM datatype that is not supported. Action: Check the supported COM datatypes and make the appropriate changes to the external procedure. 184 Chapter 24: EP Messages
- 201. EP_13069 Cannot initialize COM. Cause: The Integration Service call to CoInitialize failed. Action: Check the CoInitialize documentation for action. EP_13070 COM-style external procedures not supported on non-Windows platforms. Cause: You tried to run a COM external procedure on a UNIX server. COM-style external procedures only run on Windows platforms. Action: If possible, move the session to a Windows server before running the session again. Otherwise, create an Informatica style external procedure to replace the COM-style procedure. EP_13071 The Informatica-style transformation has a port with an invalid datatype. Cause: Internal error. Action: Contact Informatica Technical Support. EP_13072 The Informatica-style external procedure has a parameter with an invalid datatype. Cause: The Integration Service encountered a parameter with an invalid datatype in the Informatica-style external procedure. Action: Change the datatype to a supported type before running the session again. EP_13073 Informatica external procedure log message. Cause: This message appears when the external procedure creates a log message. Action: If necessary, examine the external procedure for the cause of the message. EP_13074 Informatica external procedure error message. Cause: A session configured with an external procedure has encountered an error. Action: Examine the external procedure for the cause of the message. EP_13075 The version of the Informatica external module is not supported by the server. Cause: The Integration Service encountered an external procedure that is not supported. Action: Do not use unsupported external procedure modules. EP_13083 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>. Cause: The Init or InitParams method in the specified external procedure returned a fatal error. Action: Check the code for the Init or InitParams method in the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure. EP Messages 185
- 202. EP_13084 Data conversion error. Cause: The Integration Service cannot convert a String port from the External Procedure transformation to a Date/Time input port in the external procedure. The string is not in the default date format (MM/DD/YYYY HH24:MI:SS). Action: Use TO_DATE with the appropriate format string to convert a string to a date. or Cause: The Integration Service cannot convert data from an external procedure Date/ Time output port to a String port in the External Procedure transformation. Action: Change the External Procedure transformation port to Date/Time. EP_13089 Error converting initialization parameter to correct data type for constructor parameter. Cause: In the initialization properties for the External Procedure transformation, you specified a parameter that the Integration Service cannot convert to the COM datatype for the constructor in the external procedure. Before the Integration Service calls the constructor in the external procedure, it tries to convert the initialization parameters in the External Procedure transformation to the required COM datatypes. Action: Edit the parameters in the Initialization Properties tab of the External Procedure transformation. Enter values that the Integration Service can convert to the required COM datatypes for the constructor. EP_13103 <External Procedure transformation>: Fatal error returned from external procedure <external procedure>. Cause: The specified external procedure returned a fatal error. Action: Check the code for the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure. EP_13124 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>. Cause: The Init or InitParams method in the specified external procedure returned a fatal error. Action: Check the code for the Init or InitParams method in the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure. 186 Chapter 24: EP Messages
- 203. 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. Cause: The Custom transformation procedure code uses the INFA_CTSetPassThruPort() function when the transformation scope is transaction or all input and the data access mode is row-based. Action: Change the transformation scope to row. or Cause: The procedure code for an active Custom transformation uses the INFA_CTSetPassThruPort() function and the data access mode is array-based. Action: Edit the procedure code and use the array-based mode data handling functions to set the data for all output ports. Do not use the INFA_CTSetPassThruPort() function. EP_13262 Fatal Error: It is illegal to set default row strategy to pass thru when the transformation scope is not ROW or when the data access mode is ARRAY for active Custom Transformation. Cause: The Custom transformation procedure code uses the INFA_CTSetRowStrategy() function to define the default row strategy to pass through when the transformation scope is transaction or all input and the data access mode is row-based. Action: Change the transformation scope to row. or Cause: The procedure code for an active Custom transformation uses the INFA_CTSetRowStrategy() function to define the default row strategy to pass through and the data access mode is array-based. Action: Edit the procedure code and use the INFA_CTASetRowStrategy() function to define the default row strategy to pass through. EP_13263 Fatal Error: It is illegal to call INFA_CTASetInputErrorRow when the data access mode is not ARRAY. Cause: The Custom transformation procedure code uses the INFA_CTASetInputErrorRowM() or INFA_CTASetInputErrorRowU() function and the data access mode is row-based. Action: Edit the procedure code and remove the INFA_CTASetInputErrorRowM() or INFA_CTASetInputErrorRowU() function. Instead, you can return INFA_ROWERROR in the input row notification function to notify the Integration Service that a particular input row has an error. EP Messages 187
- 204. EP_13264 Fatal Error: It is illegal to call INFA_CTGetRowStrategy outside inputRowNotification. Cause: The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function inside a function other than the p_<proc_name>_inputRowNotification() function. Action: Edit the procedure code and only use the INFA_CTGetRowStrategy() function inside the p_<proc_name>_inputRowNotification() function. EP_13265 Fatal Error: It is illegal to call INFA_CTGetRowStrategy when the data access mode is ARRAY. Cause: The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function when the data access mode is array- based. Action: Edit the procedure code and use the INFA_CTAGetRowStrategy() function to get the default row strategy. EP_13266 Fatal Error: It is illegal to call INFA_CTOutputNotification outside inputRowNotification when the transformation scope is ROW. Cause: The Custom transformation procedure code uses the INFA_CTOutputNotification() function inside a function other than the p_<proc_name>_inputRowNotification() function when the transformation scope is row. Action: Change the transformation scope to transaction or all input. EP_13267 Fatal Error: Invalid block size is set for OutputNotification. Cause: The Custom transformation procedure code uses the INFA_CTASetNumRowsInBlock() function to set the number of rows in a block. However, the number of rows is invalid. Action: Edit the procedure code and verify the value for the nRows argument in the INFA_CTASetNumRowsInBlock() function is greater than 0 and less than or equal to the value returned by the INFA_CTAGetOutputRowMax() function. EP_13268 Fatal Error: It is illegal to call INFA_CTASetOutputNumRowsMax at run-time. Cause: The Custom transformation procedure code contains the INFA_CTASetOutputNumRowMax() function in a notification function. Action: Edit the procedure code and only use the INFA_CTASetOutputNumRowMax() function in an initialization function. EP_13269 Fatal Error: Invalid block size is being passed to INFA_CTASetOutputNumRowsMax. Cause: The Custom transformation procedure code uses the INFA_CTASetOutputNumRowMax() function, but the nRowsMax argument is an invalid number. 188 Chapter 24: EP Messages
- 205. Action: Edit the procedure code and verify nRowsMax is a positive number. EP_13270 Fatal Error: Downstream Transformations have encountered a fatal error. Please refer to session log. Cause: A transformation downstream from a Custom transformation encountered a fatal error. Action: Read the session log for other error messages. EP Messages 189
- 206. 190 Chapter 24: EP Messages
- 207. Chapter 25 EXP Messages This chapter includes the following topic: โฆ EXP Messages, 192 Error messages listed numerically. 191
- 208. EXP Messages EXP_19160 Failed to find version API <function name> in module <module name>. Cause: The custom function developer did not implement the INFA_EXPR_GetPluginVersion function. Action: The custom function developer needs to implement the function in the implementation file. EXP_19161 Version API <function name> in module <module name> failed. Cause: The custom function developer configured INFA_EXPR_GetPluginVersion to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The custom function developer did not configure the plug-in version to be compatible with the Custom Function API version. The Custom Function API version includes major release number, minor release number, and patch number, such as 8.0.0. Action: The custom function developer needs to configure the plug-in version in INFA_EXPR_GetPluginVersion to be compatible with the Custom Function API version. EXP_19162 Module <module name> interface version <version number> is incompatible with framework version <version number>. Cause: The custom function developer did not configure the plug-in version to be compatible with the Custom Function API version. The Custom Function API version includes major release number, minor release number, and patch number, such as 8.0.0. Action: The custom function developer needs to configure the plug-in version in INFA_EXPR_GetPluginVersion to be compatible with the Custom Function API version. EXP_19163 Failed to find module API <function name> in module <module name>. Cause: The custom function developer did not implement the INFA_EXPR_ModuleGetUserInterface function. Action: The custom function developer needs to implement the function in the implementation file. EXP_19164 Module API <function name> in module <module name> failed. Cause: The custom function developer configured the INFA_EXPR_GetPluginVersion function to return INFA_FAILURE. 192 Chapter 25: EXP Messages
- 209. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. EXP_19165 Module init for <function name> failed: <error message>. Cause: The custom function developer configure module_init to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP_19166 Failed to find validation API <function name> in module <module name>. Cause: The custom function developer did not implement INFA_EXPR_ValidateGetUserInterface. Action: The custom function developer needs to implement the function in the implementation file. EXP_19167 Failed to find function API <function name> in module <module name>. Cause: The custom function developer did not implement INFA_EXPR_FunctionGetUserInterface. Action: The custom function developer needs to implement the function in the implementation file. EXP_19168 Failed to find function instance API <function name> in module <module name>. Cause: The custom function developer did not implement INFA_EXPR_FunctionInstanceGetUserInterface. Action: The custom function developer needs to implement the function in the implementation file. EXP_19169 Module deinit for <function name> failed: <error message>. Cause: The custom function developer configured module_deinit to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP Messages 193
- 210. EXP_19170 Failed to get validation interface for <function name>. Cause: The custom function developer configured INFA_EXPR_ValidateGetUserInterface to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. EXP_19171 Failed to get function interface for <function name>. Cause: The custom function developer configured INFA_EXPR_FunctionGetUserInterface to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. EXP_19172 Failed to get function instance interface for <function name>. Cause: The custom function developer configured INFA_EXPR_FunctionInstanceGetUserInterface to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. EXP_19173 Failed to initialize function for <function name>: <error message>. Cause: The custom function developer configured function_init to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP_19174 Failed to deinitialize function for <function name>: <error message>. Cause: The custom function developer configured function_deinit to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP_19175 Function validation for <function name> failed: <error message>. Cause: The custom function developer configured the validation API to return INFA_FAILURE. 194 Chapter 25: EXP Messages
- 211. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The custom function developer specified an invalid return datatype for the custom function. Action: The custom function developer needs to specify a valid return datatype for the custom function. EXP_19176 Failed to get process row API for <function name>. Cause: The custom function developer did not set a pointer to processRow in INFA_EXPR_FunctionInstanceGetUserInterface. Action: The custom function developer needs to set a pointer to processRow in INFA_EXPR_FunctionInstanceGetUserInterface. or Cause: The custom function developer did not implement processRow. Action: The custom function developer needs to implement the function in the implementation file. EXP_19177 Failed to initialize function instance for <function name>: <error message>. Cause: The custom function developer configured fnInstance_init to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP_19178 Failed to deinitialize function instance for <function name>: <error message>. Cause: The custom function developer configured fnInstance_deinit to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP Messages 195
- 212. EXP_19179 Invalid datatype specified for return value. Cause: The custom function developer specified an invalid return datatype for the custom function. Action: The custom function developer needs to specify a valid return datatype for the custom function. EXP_19180 Process row failed for function <function name>: <error message>. Cause: The custom function developer configured processRow to return INFA_FAILURE. Action: The custom function developer needs to configure the function to return INFA_SUCCESS. or Cause: The function failed for the reason specified in the additional error message. Action: The custom function developer may need to correct the function syntax. EXP_19181 Failed to get validation functions for <function name>. Cause: The custom function developer did not implement one ore more of the following functions: validateFunction, getFunctionDescription, getFunctionPrototype, and DestroyString. Action: The custom function developer needs to verify that these functions are implemented. EXP_19182 User-defined function <user-defined function> has a cyclic dependency. Call stack is <call stack>. Cause: The specified user-defined function contains a reference to itself in the expression syntax. Or, it contains another user-defined function which refers to it. Action: Modify the user-defined function so that it does not refer to itself or to another user-defined function that refers to the user-defined function specified in the error message. EXP_19183 User-defined function <user-defined function> uses an aggregator function. Cause: The specified user-defined function contains an aggregator function in the syntax. This is not allowed. Action: Remove the aggregator function from the function syntax. EXP_19185 Compilation for the user-defined function <user-defined function> failed. Cause: The Integration Service could not validate the user-defined function. Action: Edit the user-defined function and make sure the function syntax is valid. or 196 Chapter 25: EXP Messages
- 213. Action: Check the additional error message for more information. EXP_19186 <<Expression Fatal Error: user-defined function>> <token>: <error message>. <sub-expression>. Cause: The Integration Service encountered an error while evaluating the expression in the user-defined function. For example, the Integration Service is calling a stored procedure but cannot access the database. Action: See the additional error message for more information. EXP_19187 <<Expression Error: user-defined function>> <token>: <error message>. <sub-expression>. Cause: The Integration Service truncated an operand value because the precision is too low. The error message may provide more information about this error. Action: Increase the precision. or Cause: Data overflow occurred for an integer value. Action: Check the data values for the overflow. The error message may provide more information about this error. EXP_19188 <<Expression Warning: user-defined function>> <token>: <error message>. <sub-expression>. Same as EXP_19187. EXP_19189 Error in fetching metadata for the user-defined function <user-defined function>. Cause: The Integration Service or PowerCenter Client cannot fetch metadata for the specified user-defined function. Action: Close the repository connection and reconnect. Run the session again. or Action: Verify that you are not trying to use a user-defined function that does not exist. EXP_19190 Error: Argument mismatch for user-defined function <user-defined function> Cause: The number of arguments in the user-defined function does not match the number of required arguments. The user-defined function may contain too many or too few arguments. Action: Edit the user-defined function syntax to include the correct number of arguments. EXP Messages 197
- 214. EXP_19191 Argument name for expression must start with an x or an X. Cause: The argument for the expression in not named correctly. The name of an argument for a Java expression must start with an x or X. Action: Rename the argument. EXP_19192 Argument number is too large. Cause: The number in the argument name is too large. The number is larger than can be stored by an integer value. Action: Reduce the number of arguments for the expression. EXP_19193 Cannot get argument index from argument name. Cause: You created a argument name or names for an expression, but did not correctly name the argument. Argument names for expressions must start with an x or X, followed by an integer (index) starting from 1. All arguments for an expression must be indexed in sequential order, such as x1, x2, x3. Action: Rename the argument. EXP_19194 Argument index <index number> exceeds the expected number of arguments, <number>, in the expression. Cause: The expression contains an argument having an index greater then the expected number of arguments for the expression. For example, you created an expression that takes two arguments, but used an argument name x3 inside the expression. Instead, your expression should use x1 and x2. Action: Use the correct number of arguments for the expression when you invoke the expression. EXP_19195 Error: A non-callable user-defined function <user-defined function> is being called directly in the expression. Cause: An expression contains a non-callable user-defined function. You may have manually entered the user-defined function in the expression syntax. Or, the expression contains a user-defined function which you modified to be non- callable. Action: Edit the user-defined function to be callable. Or, remove the user-defined function from the expression. EXP_19197 Error: The Designer cannot find function <function name>. The function name may be incorrect. Cause: An expression contains a function that has an incorrect function name. Action: Ensure that the function name is correct. 198 Chapter 25: EXP Messages
- 215. Chapter 26 EXPFN Messages This chapter includes the following topic: โฆ EXPFN Messages, 200 Error messages listed numerically. 199
- 216. EXPFN Messages EXPFN_34016 Invalid number passed for conversion. Cause: The value of the number you want to convert with CONVERT_BASE cannot be represented by the source base value. For example, the source base value is 2, and the input values is 123. The input value can only contain 0s or 1s. Action: Verify that the input values can be represented by the source base. EXPFN_34017 Failed to convert number to decimal base. Cause: The input value for CONVERT_BASE was larger than the maximum allowed to convert the value to base 10. Action: Verify that all input values can be converted to base 10. 200 Chapter 26: EXPFN Messages
- 217. Chapter 27 FEXP Messages This chapter includes the following topic: โฆ FEXP Messages, 202 Error messages listed numerically. 201
- 218. FEXP Messages Information forthcoming. 202 Chapter 27: FEXP Messages
- 219. Chapter 28 FR Messages This chapter includes the following topic: โฆ FR Messages, 204 Error messages listed numerically. 203
- 220. FR Messages FR_3000 Error opening file <file name>. Operating system error message <error>. Cause: A file name specified in the session properties is incorrect. The operating system error displays when the file does not exist. Action: In the Workflow Manager, correct the file name in the session properties. FR_3002 Error reading file <file name>. Operating system error message <error>. Cause: This is an operating system error. Action: An operating system error number appears with this message. If necessary, check your operating system manual for action. FR_3013 Error setting field delimiter string... Cause: The Integration Service failed to identify a field separator. You may have repository inconsistencies. Action: Contact Informatica Technical Support. FR_3015 Warning! Row <row ID>, field <name>: Data was truncated. Cause: Data is larger than field length (delimited files only), forcing the Integration Service to truncate data. Action: To avoid truncating data, increase the field length accordingly. FR_3016 Record length <record ID> is longer than line sequential buffer length <number> for <string>. Cause: Insufficient buffer length. Action: In the session properties, increase the setting for Line Sequential Buffer Length. The record length may not be the size to which the Line Sequential Buffer Length should be increased. Check your source data file. FR_3023 Error in opening ftp connection. Cause: You specified an incorrect FTP connection in a session. You might have used the wrong user name or password. Or the FTP server may be down. Action: Verify the correct FTP connection is specified in the session properties and manually test that FTP connection. FR_3024 Error in transferring remote file. Cause: You attempted to use FTP to transfer a file that does not exist. Action: Verify that the file exists and that you used the correct spelling. or Cause: You do not have permission to access the remote file. 204 Chapter 28: FR Messages
- 221. Action: Contact the FTP system administrator. FR_3029 Delimited file attribute error: escape character cannot be the same as quote character. Cause: You specified the same quote mark for the escape character and the optional quotes character in a delimited flat file source. Action: Specify a different escape or quote character. FR_3030 Delimited file attribute error: delimiters cannot contain quote character. Cause: One of the delimiters is the selected quote character. Action: Specify a delimiter other than the quote character. FR_3031 Delimited file attribute error: delimiters cannot contain escape character. Cause: One of the delimiters is the specified escape character. Action: Specify a delimiter other than the escape character. FR_3032 Delimited file attribute error: must specify at least one delimiter. Cause: You have not specified a delimiter. Action: Specify a delimiter. FR_3033 Delimited file reader: Warning! Missing matching quote character in column <column name> of file <file name>. Reading till the end of line for the column. Cause: There is a missing closing quote in the specified column. Action: Review the file and add a closing quote character where appropriate. FR_3034 Delimited file reader: Warning! Skipped extra character(s) after the closing quote of column <column name> in file <file name>. Cause: There are additional characters after the closing quote delimiter in the specified column. The Integration Service did not read the extra characters. Action: Look in the source file to verify if the skipped characters are intended to be a part of the column. If so, import the file into the Source Analyzer again. FR_3035 Error opening file NULL. Operating system error message. Cause: Internal error while reading from a source file. Action: Contact Informatica Technical Support. FR_3036 Error: Escape character <escape character value> is not in Latin1 code page in ASCII data movement mode. Cause: You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected an escape character for the file source that is not valid in the Latin1 code page. FR Messages 205
- 222. Action: Select an escape character that is valid in the Latin1 code page. 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. Cause: You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected a delimiter for the file source that is not valid in the Latin1 code page. Action: Select a delimiter that is valid in the Latin1 code page. FR_3038 Error: Escape character <escape character value> is invalid in current file code page <code page name> in UNICODE data movement mode. Cause: You configured the Integration Service to run in Unicode mode, and you selected an escape character for the file source that is not valid for the file source code page. Action: Select an escape character that is valid in the source code page. 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. Cause: You configured the Integration Service to run in Unicode mode, and you selected a delimiter for the file source that is not valid for the file source code page. Action: Select a delimiter that is valid in the source code page. FR_3041 Error: Invalid code page <code page name> for delimited flat file. Cause: The code page you selected is not valid for delimited flat file formats. Action: Select a code page that is valid for delimited flat files. FR_3043 Error: Using EBCDIC-based Multibyte code page <code page name> in ASCII data movement mode is invalid. Cause: You configured the Integration Service to run in ASCII mode and selected an EBCDIC-based multibyte code page for a file source. Action: If data requires an EBCDIC-based multibyte code page, run the Integration Service in Unicode mode. Otherwise, select a valid code page for the source. FR_3045 Error: Code page <code page ID> not found. Please install it first. Cause: The Integration Service could not find the code page you specified. Action: Install the correct code page. FR_3046 Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width boundary for field <field name>. Cause: Multibyte data does not fit into the fixed-width boundary for this column. 206 Chapter 28: FR Messages
- 223. Action: Change the field width or pad the column with blanks so that fields fit correctly. FR_3047 Error: Invalid code page <code page name> for fixed-width flat file. Cause: The code page you selected is not valid for fixed-width files. Action: Select a code page that is valid for fixed-width files. FR_3048 Error: Null character <null character value> is invalid in current file code page <code page name> in Unicode data movement mode. Cause: The null character you specified is invalid in the source flat file code page. Action: Use a null character that is valid in the source flat file code page. FR_3049 Error: Null character <null character value> is not in Latin1 code page in ASCII data movement mode. Cause: You configured the Integration Service to run in ASCII mode and specified a null character that is not valid in the Latin1 code page. Action: Specify a null character that is valid in the Latin1 code page. FR_3050 Error: Invalid code page <code page name> for fixed-width VSAM file. Cause: The code page you selected is not valid for VSAM files. Action: Select a code page that is valid for VSAM files. FR_3051 Error: Invalid binary null character <null character value>. The decimal value is not between 0 and 255. Cause: You entered an invalid null character value. Action: Specify a null character value between 0 and 255. FR_3053 Error! Data <string data> in fixed-width file <file name> does not end at the fixed-width boundary for <bytes to skip between records>. Next row/record will also be an error. Cause: The number of bytes to skip between records is greater than 0. If the number of bytes to skip between records is greater than 0, then there is an alignment error in these bytes. The record data does not end at the fixed-width boundary for these skipped bytes. Action: Fix the data and the number of bytes to skip between rows/records setting. FR_3054 Error! Remaining data <string data> in non-repeating, binary null field, in fixed-width file <file name> does not end at the fixed-width boundary for field <field name>. Cause: Remaining data in a non-repeating, binary null field does not end at the fixed- width boundary for that field. Action: Fix the data and/or the fixed-width settings. FR Messages 207
- 224. FR_3056 Error reading from file <file name>. Cause: An error occurred reading the source file. Action: Check other error messages logged for more details. FR_3057 Error: Insufficient data for fixed-width flat file or fixed-width VSAM file. Row data is <row data>. Cause: The non line-sequential data is too small. The data displayed is the row, including the trailing bytes between records. Action: Make sure the data is the correct length and the bytes between rows match the source file options. FR_3058 Error processing COBOL file: cannot parse the input [numeric character in <data> at position <position> has to be in the Latin1 code page]. Cause: The reader cannot read the input field because the input field contains characters that are not in the Latin 1 code page. Action: Change the input field to contain Latin 1 character data. FR_3059 Error processing record <record name> in file <file name>: Record is invalid because at least one set of redefines is invalid (redefine is not at a perfect character boundary or conversion error for picnum field). Cause: In a file source, at least one of the REDEFINES statements results in a character exceeding the field boundary. Action: Examine and correct the row where the error occurred. or Cause: The definition is incorrect. Action: Edit the REDEFINES statement. FR_3060 Error processing record <record name> in file <file name>: Conflicting shift states at position <position number, referring to byte offset into the row> when interpreting multiple redefines. Cause: In a file source, one of the REDEFINES statements leaves the row in the shift in state while another REDEFINES statement leaves the row in the shift out state. Action: Examine and correct the row where the error occurred or edit the REDEFINES statement. FR_3061 Error opening MQSeries queue. Operating system error message. Cause: When running a session that reads from MQSeries and flat file sources, the queue could not be opened due to an error. Action: Correct the error indicated in the additional error message. 208 Chapter 28: FR Messages
- 225. FR_3064 Warning: Last row in file is not complete. Cause: The last row in the fixed-width file contains empty columns. The Integration Service skips the last row. Action: Verify the last row in the source file contains valid data. FR_3065 Row <row number>, field <column name>: Invalid number - <column data>. The row will be skipped. Cause: The source file contains string data in a numeric column. The Integration Service skips the row. Action: Verify the row in the source file contains valid data. 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. Cause: The date format string for a datetime column contains a character that is not in 7-bit ASCII. Action: In the Designer, edit the flat file source definition using 7-bit ASCII characters for the datetime column format string. FR_3067 Row <row number>, field <column name>: Invalid date - <column data>. The row will be skipped. Cause: The source file contains invalid data in a datetime column. The Integration Service skips the row. Action: Verify the row in the source file contains valid data. FR_3068 Invalid date format provided <date format>. Cause: Internal error. Action: Contact Informatica Technical Support. FR_3069 Error: The character '<character>' is used as a delimiter and a thousands separator for field <column name>. Cause: In the Designer, you specified the same character as both the file delimiter and as the thousands separator for the specified numeric column. Action: Verify the source file contains different characters for the thousands separators and column delimiters. Edit the source definition in the Source Analyzer, or import it again. FR_3070 Error: The character '<character>' is used as a delimiter and a decimal separator for field <column name>. Cause: In the Designer, you specified the same character as both the file delimiter and as the decimal separator for the specified numeric column. FR Messages 209
- 226. Action: Verify the source file contains different characters for the decimal separator and column delimiter. Edit the source definition in the Source Analyzer, or import it again. FR_3072 Error: Flat file <file name> cannot be processed for reading. Cause: The Integration Service cannot access the source file. Action: Verify the Integration Service can access the machine hosting the file. or Action: Verify the user who started the Integration Service has read permission on the directory where the file is located. FR_3074 Error at row <row number>. A multibyte character spans over two fields or two lines. Record will be skipped. Cause: In the fixed-width file source, a multibyte character in a column spans over two columns. The Integration Service skips the row. Action: Verify that the row in the source file contains valid data. Also, verify that the data in the source file matches the source definition. FR_3075 Error: Source file type cannot be indirect for an MQ associated source qualifier. Cause: You selected Indirect for the Source file type. When the mapping contains an associated source qualifier, the source file type must be direct. Action: Select Direct as the source file type. FR_3077 Fatal Error: The column <column name> has corrupt formatting information. Resave the information in the repository. Cause: Internal error. Action: Contact Informatica Technical Support. FR_3078 Fatal error: Cannot flush an incomplete row in real time. Cause: During a real-time session, the Integration Service issued a commit while processing a record. As a result, the session failed. Action: Make sure that all message fields in the MQSeries source are complete before running the session. FR_3085 ERROR: Row <row number>: <character>-th character is a null character, which is not allowed in a text input file <file name>. Cause: The Integration Service cannot read the input field because it contains a null character. Action: Verify that the source does not have null values. 210 Chapter 28: FR Messages
- 227. FR_3107 ERROR: The character <character> is used as both a column delimiter and a row delimiter. Cause: The session failed because the line break character is the same character as the column delimiter in the flat file. Action: Configure different characters for the flat file line break character and column delimiter character. FR_3108 ERROR: DSQ <Source Qualifier> UCS-2 code page UTF-16BE or UTF-16LE are not supported with this type of file. Cause: The session failed because the UTF-16BE or UTF-16LE code page is not supported for fixed-width flat files. Action: You can use these code pages with delimited flat files. FR_3111 Error: Conflicting settings for NULL handling are specified for the delimited file source <source name>. Cause: The FileRdrTruncateStringNull and the FileRdrTreatNullCharAs custom properties are enabled at the same time. The FileRdrTruncateStringNull and the FileRdrTreatNullCharAs custom properties determine how the Integration Service handles null characters in the flat file source. Action: Disable one of the properties. FR_3112 Error: Invalid NULL replacement character is specified for the delimited file source <source name>. Cause: When you enable the FileRdrTreatNullCharAs custom property, the Integration Service sets null characters in a source file to the character you define. The character format is invalid. Action: Define a valid octal character, such as 040. FR Messages 211
- 228. 212 Chapter 28: FR Messages
- 229. Chapter 29 FTP Messages This chapter includes the following topic: โฆ FTP Messages, 214 Error messages listed numerically. 213
- 230. FTP Messages FTP_14002 Unable to FTP file because the TCP/IP address for the specified host could not be obtained. Cause: The host machine of the file is not defined on the machine hosting the Integration Service. Action: Define the remote machine on the Integration Service in a file, such as in the hosts file. FTP_14003 Unable to FTP file because socket could not be created. Cause: The Integration Service could not create the socket due to insufficient resources (such as file descriptors, memory, or permissions) on the FTP server. Action: Contact the FTP system administrator. FTP_14004 Unable to FTP file because socket option could not be set. Cause: Internal error. Action: Contact the FTP system administrator. FTP_14005 Unable to FTP file because could not connect to FTP server. Cause: The Integration Service could not connect to the FTP server, possibly because the network is down. Action: Contact the network administrator. or Cause: The FTP server is not properly configured on the remote machine. Action: Contact the FTP system administrator. FTP_14006 Unable to FTP file because read from FTP server failed (recv()). Cause: The network connection went down after the Integration Service connected to the FTP server. Action: Check with the network administrator, the FTP system administrator, and the Informatica system administrator. FTP_14007 Unable to FTP file because format of FTP response is not expected. The FTP server is not supported. Cause: The Integration Service does not recognize the FTP protocol. Action: Contact Informatica Technical Support. 214 Chapter 29: FTP Messages
- 231. FTP_14008 Error closing FTP connection. Cause: The Integration Service lost connection with the FTP server. Action: Contact the FTP administrator. FTP_14009 Unable to FTP file. Could not log in due to invalid user. Cause: The user name in the FTP Connection Editor dialog box is incorrect. Action: Verify the FTP user name in the Workflow Manager. FTP_14010 Unable to FTP file. Could not login due to rejected password. Cause: The password in the FTP Connection Editor dialog box is incorrect. Action: Verify the FTP password in the Workflow Manager. FTP_14011 Unable to FTP file. Connect request rejected by FTP server. Cause: The FTP server denied connection from the Integration Service. Action: Contact the FTP system administrator. FTP_14012 Unable to FTP file. FTP command rejected by FTP server. Cause: The FTP user in the Workflow Manager FTP Connection Editor dialog box does not have read permissions. Action: For Windows, verify that the FTP user accessing the file has standard read permissions on the directory of the staged file. For UNIX, prepare the staging directory so that the FTP user who accesses the file also owns the directory. Run the following UNIX command from the directory where you want to generate the file: % chmod g+s or Cause: This is an informational message. The Integration Service checks the existence of a file when you run a file persist session. The first time you run a file persist session, the file does not exist. When the Integration Service does not find the file, it logs this message in the session log. Action: None. FTP_14017 Unable to FTP file - Local File <file name> System Error <system message>. Cause: The Integration Service could not open the local staging file you specified in the session properties. Action: Check the session log for further messages. FTP Messages 215
- 232. FTP_14018 Unable to FTP file. Error reading local file. Cause: The target file was written to the target staging location, but the Integration Service encountered an error while reading the file when transferring it to the target machine. Action: Check the session log for further messages. FTP_14019 Unable to FTP file. Error writing to local file. Cause: The FTP server encountered an error when writing to the source staging file location. Action: Confirm the staging directory specified in the session properties. FTP_14020 Unable to delete file. FTP DELE command rejected by FTP server. Cause: The FTP user does not have permission to delete the staging file. Action: Delete the file manually, and check with the administrator of the FTP system to get permission to delete FTP files for future sessions. FTP_14024 FTP host name <host name> has incorrect format. Specify <hostname> or <hostname>:<port> where 0 <port< 65536. Cause: You entered an FTP host name in the wrong format in the Host Name field in the FTP Connection Editor dialog box. Action: Edit the FTP connection in the Workflow Manager. Specify the host name format as <hostname> or <hostname:port>. FTP_14040 FTP Socket [socket number] timeout. The FTP server has not responded in time. Verify the FTP server is running, or increase the FTP timeout value. Cause: The Integration Service tried to accessed a file source on an FTP server, but the FTP server did not send any data before the Integration Service timed out. By default, the Integration Service waits 600 seconds before timing out. Action: Verify the FTP server is still running. If you need to increase the amount of time the Integration Service waits before timing out, contact Informatica Technical Support. FTP_14046 Cannot reconnect to FTP server at <FTP host>: <control port number> within retry period. Cause: The connection to the FTP server failed. The Integration Service could not reconnect to the FTP server within the retry period for the FTP connection object. Action: Check the status of the FTP server and run the session again. If the session is enabled for recovery, recover the session. 216 Chapter 29: FTP Messages
- 233. FTP_14047 The source file <file name> or its timestamp was changed after the previous read. Session should now terminate. Cause: The connection to the FTP server for the session failed and the Integration Service reconnected to the FTP server. However, the source file for the session changed since the last time the Integration Service read from the file, and the session failed. Action: Run the session again. If the session is enabled for recovery, recover the session. FTP_14048 FTP server does not support the FTP command <FTP command>. Resilience is disabled. Cause: The connection to the FTP server failed. The Integration Service reconnected to the FTP server and attempted to restart the file transfer. However, the FTP server does not support the REST, MDTM, or SIZE FTP commands, which are necessary to restart the file transfer. As a result, the session failed. Action: For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP commands. FTP_14049 FTP server does not support the FTP command <FTP command>. Cannot restart file transfer to FTP server. Same as 14048. FTP_14050 DTM buffer does not contain enough data to restart file transfer. Terminating session. Cause: The Integration Service transferred some target data to the remote FTP server and the connection failed. Some of the target data was not written to the remote file by the FTP server, and target data no longer exists in the buffer for the DTM process. As a result, data was lost and the Integration Service cannot restart file transfer after reconnecting to the FTP server. Action: Run the session again. FTP_14055 A socket <socket number> failure is encountered: <error text>. Cause: The Integration Service encountered an error for the socket. As a result, the session failed. Action: Correct the error and run the session again. FTP_14056 High availability license is absent. Retry period specified for Integration Service connection to the FTP server is ignored. Cause: The retry period is configured in the FTP connection object, but you do not have the high availability option. The retry period is ignored. Action: None. FTP Messages 217
- 234. 218 Chapter 29: FTP Messages
- 235. Chapter 30 HIER Messages This chapter includes the following topic: โฆ HIER Messages, 220 Error messages listed numerically. 219
- 236. HIER Messages HIER_28004 XML Reader Error: <error text>. Cause: This is a generic error. Action: Check the session log for related error messages. HIER_28020 DTM buffer block is filled, and we can't send the block yet. Need to use heap memory to hold data. Cause: In the XML file, leaf elements appear after multiple-occurring enclosure elements of a parent element. The memory block for the multiple-occurring enclosure elements is filled. Action: Restructure the file so that all of the leaf elements of a parent element appear before the multiple-occurring enclosure elements. HIER_28028 Fatal Error: Could not allocate memory from heap. Cause: In the XML file, leaf elements appear after multiple-occurring enclosure elements of a parent element. The Integration Service has now run out of heap memory. Action: Restructure the file so that all of the leaf elements of a parent element appear before the multiple-occurring enclosure elements. HIER_28031 There are two fields pointing to the same XML node, but the datatypes and lengths do not match. Cause: The Source Qualifier transformation contains different ports based on the same XML element. The datatypes or lengths for these ports are different. Action: Check the Source Qualifier transformation and make sure the datatypes and lengths for all occurrences of the element match. HIER_28032 Error: There are no fields in any of the groups defined that have a reference to a node in the XML tree. Cause: The XML map for an element in the XML file is blank. Action: Contact Informatica Technical Support. HIER_28034 Could not retrieve a block from the DTM. Cause: The reader thread could not retrieve a block of memory from the DTM buffer pool. Action: Contact Informatica Technical Support. HIER_28041 Couldn't open indirect file <file name>. Cause: You set up the session to read from a file list. The Integration Service could not open the specified file list. 220 Chapter 30: HIER Messages
- 237. Action: Make sure the file exists in the specified directory, check the permissions on the file and directory, and then rerun the session. HIER_28043 Reader failure: The node <element name> occurs multiple times. This node was marked in the schema as occurring one or less times. Cause: You imported a source in the Designer based on an XML file. In the source qualifier, the Designer marked one of the elements as a single-occurring element. When you used this source in a mapping, the imported XML file contained the element multiple times. Action: Recreate the XML Source Qualifier transformation using a more accurate XML file. HIER_28044 Reader failure: The root node for the given XML does not match the root node in the repository. Cause: You imported a source in the Designer based on an XML file. The Designer determined the root element based on this file and stored it in the repository. When you used this source in a mapping, the imported XML file contained a different root element. Action: Check the XML file and then import it again. HIER_28045 Out of range error: <element name>. Cause: The element stored in the repository is a decimal number with a specific precision and range. The precision for the element in the XML file does not match the precision stored in the repository. Action: Check the precision for the element, and then import the XML file again. HIER_28051 Read invalid number <value> for XML path <path name>. Cause: The Integration Service failed to read a value from an XML file because the datatype defined in the XML source definition does not match the datatype in the XML file. Action: Verify that the datatype defined in the XML source definition matches the datatype in the XML file. HIER Messages 221
- 238. 222 Chapter 30: HIER Messages
- 239. Chapter 31 ICMD Messages This chapter includes the following topic: โฆ ICMD Messages, 224 Error messages listed numerically. 223
- 240. ICMD Messages ICMD_10000 Cannot find command <invalid command name>. Cause: The command does not exist. Action: Use infacmd help for available commands. ICMD_10001 Command <command name> encountered an internal error. Cause: The command was not able to load the options. Action: If the problem persists, contact Informatica Technical Support. ICMD_10002 Cannot find command <invalid command name>. Cause: The command does not exist. Action: Use infacmd help for available commands. ICMD_10003 Invalid command option: <option name>. Cause: The command option specified is not available for this command. Action: Use infacmd help for available command options. ICMD_10006 The command option <option name> takes one value. Cause: The command option was entered with more than one argument. The option takes only one argument. Action: Verify that the command entered specifies only one argument for the option. If the command takes several options, make sure that all options are preceded with a hyphen. On UNIX, escape quotation marks and other non- alphanumeric characters using a backslash. ICMD_10007 Missing required command option: <option>. Cause: The command is missing a required command option. Action: Specify the command option for the command. ICMD_10011 The specified service is not a Repository Service. Cause: The service specified must be a Repository Service. Action: Specify a Repository Service. ICMD_10014 The specified service does not have a process defined on the specified node. Cause: The node is not defined for the service. Action: Verify the command values. ICMD_10015 Service options not found: <service option names>. Cause: Service option specified does not exist. 224 Chapter 31: ICMD Messages
- 241. Action: Use infacmd help for available service options. ICMD_10016 Invalid resource type. Cause: The resource type specified in the argument is invalid. Action: Use one of the following resource types: connection, custom, or โfile directoryโ. ICMD_10018 XML element <element name> not found in configuration file. Cause: Resource element not found during batch import of tomcat/bin/ nodeoptions.xml file. Action: Add resource back to tomcat/bin/nodeoptions.xml file and retry. or Cause: Server port element may be invalid of tomcat/conf/server.xml file. Action: Add server port back to tomcat/conf/server.xml file and retry. ICMD_10019 Service <service name> not found in tomcat/conf/server.xml file. Cause: HTTP service or Web Services Hub not specified in tomcat/conf/server.xml or Tomcat server setting may be invalid. Action: Rerun infasetup define node command, or correct tomcat/conf/server.xml file. ICMD_10020 HTTP connector not found in tomcat/conf/server.xml file. Cause: HTTP Connector not specified in tomcat/conf/server.xml or Tomcat server setting may be invalid. Action: Rerun infasetup define node command, or correct tomcat/conf/server.xml file. ICMD_10021 HTTP port not found in tomcat/conf/server.xml file. Cause: HTTP connector port not specified in tomcat/conf/server.xml or Tomcat server setting may be invalid. Action: Rerun infasetup define node command, or correct tomcat/conf/server.xml file. ICMD_10022 Invalid port number specified. Cause: The port value specified for the argument to an infasetup command is invalid. For example, if the argument name shows โdomain_gateway_host:portโ, then the port number for the domain gateway host machine is invalid. Action: Verify the port number for the argument. ICMD_10023 XML transformer configuration error occurred. Cause: Error occurred while writing tomcat/conf/server.xml. Action: Refer to stack trace for more details. Contact Informatica Technical Support. ICMD Messages 225
- 242. ICMD_10024 XML transformer error occurred. Cause: Error occurred while writing tomcat/conf/server.xml. Action: Refer to stack trace for more details. Contact Informatica Technical Support. ICMD_10029 Invalid port range specified. Cause: Port number range specified is invalid. Action: Rerun command with valid port numbers. ICMD_10030 Server/config/nodemeta.xml file not found. Cause: Server/config/nodemeta.xml file cannot be found. Action: Define the node with infasetup define node command. ICMD_10031 Domain metadata file not found. Cause: Domain metadata file cannot be found. Action: Specify or restore the domain metadata file. ICMD_10035 Invalid option syntax. Cause: โOPTION_NAME=option_valueโ is in invalid format. Action: Use infacmd help for valid syntax. ICMD_10036 Domain name not consistent with domain. Cause: Invalid domain name entered. Action: Enter the correct domain name. ICMD_10038 HTTP port is used twice in tomcat/conf/server.xml file. Cause: HTTP port defined in both HTTP connection and protocol. Action: Rerun infasetup define node command or contact Informatica Technical Support to correct tomcat/conf/server.xml file. ICMD_10039 Server port not found in tomcat/conf/server.xml file. Cause: Server port element not defined in tomcat/conf/server.xml file. Action: Rerun infasetup define node command or contact Informatica Technical Support to correct tomcat/conf/server.xml file. ICMD_10040 SSL port not found in tomcat/conf/server.xml file. Cause: SSL port element not defined in tomcat/conf/server.xml file. Action: Rerun infasetup define node command or contact Informatica Technical Support to correct tomcat/conf/server.xml file. 226 Chapter 31: ICMD Messages
- 243. ICMD_10041 Proxied connector port not found in tomcat/conf/server.xml file. Cause: Proxied connector port element not defined in tomcat/conf/server.xml file. Action: Rerun infasetup define node command or contact Informatica Technical Support to correct tomcat/conf/server.xml file. ICMD_10042 AJP port not found in tomcat/conf/server.xml file. Cause: AJP port element not defined in tomcat/conf/server.xml file. Action: Rerun infasetup define node command or contact Informatica Technical Support to correct tomcat/conf/server.xml file. ICMD_10043 Service type <service type> is invalid. Cause: Service type specified is invalid. Action: Use infacmd help for available service types. ICMD_10045 Cannot perform operation on running domain <domain name>. Cause: Domain is currently running. Action: Shut down the domain. ICMD_10046 Cannot perform operation on a running node. Cause: Node is currently running. Action: Shut down the node. ICMD_10047 Cannot perform operation on running domain <domain name>. Cause: Domain is currently running. Action: Shut down the domain. ICMD_10048 Cannot remove enabled service. Cause: Service is enabled. Action: Disable the service. ICMD_10050 The specified service is not an Integration Service. Cause: Service specified to update is not an Integration Service. Action: Specify an Integration Service. ICMD_10051 Cannot remove running node. Cause: Node is currently running. Action: Shut down the node. ICMD_10053 <Objects that were pinged> has failed to ping back. Cause: The object being pinged was not running. ICMD Messages 227
- 244. Action: Make sure that the domain and other objects are running. or Cause: Domain specified does not exist. Action: Check the domain name, host, and port. ICMD_10058 Internal error: This command has two options with the same name <option >. Cause: Two identical options exist in infacmd parsing. Action: Contact Informatica Technical Support. ICMD_10061 Binary export must specify a file name. Cause: User asked to export log in binary format without specifying file name. Action: Change the format type or specify a file name using -OutputFile command option. ICMD_10064 Invalid output format type: <Format type>. Cause: Invalid format type specified. Action: Use infacmd help for available format types. ICMD_10065 Invalid message count option: <count of messages>. Cause: Invalid count of messages specified. Action: Specify a valid number greater than 0. ICMD_10066 Cannot find input file <input file name> because: <reason>. Cause: Input file cannot be accessed. Action: Specify a valid input file name. ICMD_10067 Input data contains non-log events: <object type>. Cause: Input data contains an object that cannot be imported by Log Manager. Action: Verify that input data contains only log events. ICMD_10068 Failed to parse import data because: <reason>. Cause: An error occurred parsing the input data. Action: Verify file contains exported log events. If the problem persists, contact Informatica Technical Support. ICMD_10069 Failed to import log events because: <reason>. Cause: Import operation failed. Action: Review detail of failure and try to correct stated problem. 228 Chapter 31: ICMD Messages
- 245. ICMD_10070 Invalid process ID: <process ID>. Cause: Invalid process ID specified. Action: Process ID must be a valid number. ICMD_10071 Invalid message severity: <message severity level>. Cause: Invalid message severity level specified. Action: Use infacmd help for available message severity levels. ICMD_10072 Invalid date format: <date>. Expected date formats are MM/dd/yyyy or yyyy- MM-dd optionally followed by HH:mm:ss. Cause: Invalid date specified. Action: Specify date in format MM/dd/yyyy or yyyy-MM-dd optionally followed by HH:mm:ss. ICMD_10073 Invalid block size: <block size>. Cause: Invalid block size specified. Action: Specify block size as a positive integer. ICMD_10082 Cannot disable Service Manager component <service name>. Cause: Cannot disable a component of the Service Manager. Action: Select an application service. ICMD_10084 Invalid node address format. Expected format is host:port. Cause: Invalid node address specified. Action: Specify node address with host:port format. ICMD_10085 Invalid resilience timeout value. Cause: Invalid timeout value specified. Action: Specify timeout value with a positive integer. ICMD_10086 The node <node name> does not exist in the domain. Cause: Node name does not exist in the domain. Action: Enter a valid node name. ICMD_10089 Invalid port number <port number> for command option <command option>. Cause: Invalid port number specified. Action: Enter a valid port number. ICMD_10090 Invalid Resource Type. Use one of the following: <types>. Cause: The resource type specified in the argument is invalid. ICMD Messages 229
- 246. Action: Use one of the resource types shown in the message for the command: either connection, custom, or โfile directory.โ ICMD_10091 The resource provision <value> is not valid. Cause: The resource provision threshold specified in the argument is invalid. Action: Specify the resource provision threshold in the format resource_provision_threshold=value. For example, to set the Maximum Processes threshold to 15, enter -rp MaxProcesses=15. ICMD_10092 The error severity level is not valid. Cause: The error severity specified in the argument is invalid. Action: Verify that the severity type specified is one of the following: fatal, error, warning, info, trace, or debug. ICMD_10093 There are no licenses in this domain. Cause: The ListLicenses command was used to list licenses in the domain. infacmd was unable to find any licenses in the domain. Action: Add a license to the domain. ICMD_10099 Multiple values provided for mutually exclusive options. Cause: The command contains an option that cannot be specified with another option. For example, in some commands, you can specify either a node name or a grid name, but not both. Action: Specify one of the options, but not both. ICMD_10101 Backup nodes defined without a primary. Cause: The command requires arguments that specify primary and backup node names. Backup nodes were specified, but a primary node was not. Action: Specify both the primary and backup nodes. ICMD_10104 Duplicate node specified in list. Cause: The command takes arguments that specify a list of nodes. The same node was specified more than once. Action: Specify each node once. ICMD_10145 Unable to add node <node> to the requested domain <domain> with error <error message>. Cause: Unable to add the domain node to the domain. Action: Check the error message and address it accordingly. 230 Chapter 31: ICMD Messages
- 247. ICMD_10146 Metadata is up to date. Cause: You are attempting to upgrade an object that has been upgraded already. Action: None. ICMD_10147 No attributes were defined for update. Update will not be done. Cause: You did not define any attributes for update. Action: Define update attributes. ICMD_10148 The file specified does not exist: <file name> Cause: File specified in infacmd could not be found. Action: Check the file specified in infacmd and correct any errors. ICMD_10149 The command contains an unended quotes argument. Cause: The command contains an argument with only an open quote. Action: Correct the command input. ICMD_10152 The folder path must begin with the rootpath '/ '. Cause: You did not specify a folder path starting with '/'. Action: Correct the folder path and retry the command. ICMD_10155 The specified object type <object type> is invalid, please see help for valid types. Cause: You did not specify the right object type. Action: Correct the object type and try again. ICMD_10194 The input <value> does not conform to the required name=value format. Cause: The input does not match the required format. Action: Reenter the data with name=value without spacing. ICMD_10195 Repository Service requires service name, user name, and user password if any are specified. Cause: Not all required Repository Service fields were entered. Action: Make sure that all required fields are entered and try again. ICMD_10199 Cannot perform this command on core service <core service name>. Cause: A core service was specified for a command for installed services only. Action: Select a different installed service for this command. ICMD Messages 231
- 248. 232 Chapter 31: ICMD Messages
- 249. Chapter 32 IDOC Messages This chapter includes the following topic: โฆ IDOC Messages, 234 Error messages listed numerically. 233
- 250. IDOC Messages IDOC_17601 Received a call to an unsupported function <function>. Cause: The Integration Service received an RFC call from SAP for a function that is not registered to the Integration Service. Action: Use the RFC Destination created for the Integration Service in SAP to send outbound IDocs only. IDOC_17605 Invalid value specified for IDocParamType. Must be either ControlRecord or SegmentRecord. Cause: The 6.x IDoc_Prepare AEP transformation contains an invalid value for the IDocParamType property. Action: Edit the transformation and select either ControlRecord or SegmentRecord for this property. IDOC_17606 Error getting metadata for the IDoc segment <segment name>. Cause: The Integration Service failed to retrieve the IDoc metadata for a 6.x IDoc mapping. Action: Verify that the Informatica transports were correctly installed or upgraded. or Action: Verify that the saprfc.ini file is configured according to the instructions in the PowerCenter Installation and Configuration Guide. Also, verify that the RFC Destination created in the SAP system for the Integration Service is valid. IDOC_17607 Property <property> is invalid. Error parsing IDocs list. Cause: The 6.x IDoc_Writer AEP transformation contains a list of values for the IDocTypeList property that are not separated with the correct delimiter. Action: Edit the transformation and use a semicolon (;) to separate the list of IDoc types. IDOC_17608 The number of IDoc types in the property <property> does not match the number specified in <property>. Cause: The number of IDoc types listed in the IDocTypeList property does not match the number specified in the NumberOfIDocTypes property for the 6.x IDoc_Writer AEP transformation. Action: Edit the transformation so that the value for the NumberOfIDocTypes property matches the number of IDoc types listed in the IDocTypeList property. 234 Chapter 32: IDOC Messages
- 251. IDOC_17610 Error getting metadata for some of the IDocs in the list: <list>. Cause: The Integration Service failed to retrieve the metadata for the IDoc_Writer AEP transformation in a 6.x inbound IDoc mapping. Action: Verify that the Informatica transports were correctly installed or upgraded. or Action: Verify that the saprfc.ini file is configured according to the instructions in the PowerCenter Installation and Configuration Guide. Also, verify that the RFC Destination created in the SAP system for the Integration Service is valid. IDOC_17613 Unexpected IDoc type <IDoc type> received. Cause: The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. Action: Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. IDOC_17614 Input is expected only for IDoc types: <IDoc type>. Cause: The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. Action: Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. IDOC_17615 Error parsing control data. Check the control data for IDoc type <IDoc type>. Cause: The Integration Service failed to parse the IDoc control record data received by the 6.x IDoc_Writer AEP transformation. Action: Correct the source data so that it contains valid control record data. IDOC_17617 The segment <IDoc segment> is not allowed in the current IDoc type <type>. Cause: The 6.x IDoc_Writer AEP transformation received data for an invalid segment for the IDoc type. Action: Correct the source data so that it contains only valid segment data as defined by the metadata for the IDoc type. IDOC_17618 Control record data cannot be NULL for IDoc <IDoc>. Cause: The 6.x IDoc_Writer AEP transformation received a null value for the control record. Action: Correct the source data so that the IDoc control record data does not contain null values. IDOC_17619 Segment data cannot be NULL for segment <segment>. Cause: The 6.x IDoc_Writer AEP transformation received a null value for the segment record. IDOC Messages 235
- 252. Action: Correct the source data so that the IDoc segment record data does not contain null values. IDOC_17620 Error creating control table <control table>. Cause: There is not enough memory on the node where the Integration Service process runs to perform the desired operation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. IDOC_17621 Error creating data table <data table>. Cause: There is not enough memory on the node where the Integration Service process runs to perform the desired operation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. IDOC_17622 Error appending control record <control record>. Failed to allocate enough memory. Cause: There is not enough memory on the node where the Integration Service process runs to perform the desired operation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. IDOC_17623 Error appending data record <data record>. Failed to allocate enough memory. Same as IDOC_17622. IDOC_17624 The SAPALEIDoc target definition did not receive a control record segment for IDoc type: <IDoc type>. Cause: The SAPALEIDoc target definition received several data segments but no control record segment (EDIDC) for the specified IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid IDoc data. Action: Verify that valid IDoc data is passed to the SAPALEIDoc target definition. IDOC_17625 The SAPALEIDoc target definition did not receive a control record segment. Error encountered in IDoc processing. Cause: The SAPALEIDoc target definition received several data segments but no control record segment (EDIDC) for an IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target 236 Chapter 32: IDOC Messages
- 253. definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. Action: Verify that valid IDoc data is passed to the SAPALEIDoc target definition. IDOC_17626 The SAPALEIDoc target definition received an incorrect number of control record segments. Error encountered in IDoc processing. Cause: The number of control record segments that the SAPALEIDoc target definition received does not match the total number of IDocs received. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. Action: Verify that valid IDoc data is passed to the SAPALEIDoc target definition. IDOC_17627 The SAPALEIDoc target definition did not receive any data segments for IDoc type <IDoc type>. Error encountered in IDoc processing. Cause: The SAPALEIDoc target definition received a control record segment but no data segments for the specified IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. Action: Verify that valid IDoc data is passed to the SAPALEIDoc target definition. IDOC_17633 Error creating control table <table>. Same as IDOC_17622. IDOC_17642 Idle Time <time> must be greater than or equal to -1. Cause: The Idle Time session property specified for the SAPALEIDoc source definition contains an invalid value. Action: In the session properties, edit the Idle Time value so that it is greater than or equal to -1. IDOC_17643 Packet Count <count> must be greater than or equal to -1. Cause: The Packet Count session property specified for the SAPALEIDoc source definition contains an invalid value. Action: In the session properties, edit the Packet Count value so that it is greater than or equal to -1. IDOC_17644 Real-time Flush Latency <latency period> must be greater than or equal to 0. Cause: The Real-time Flush Latency session property specified for the SAPALEIDoc source definition contains an invalid value. IDOC Messages 237
- 254. Action: In the session properties, edit the Real-time Flush Latency value so that it is greater than or equal to 0. IDOC_17645 Reader Time Limit <time limit> must be greater than or equal to 0. Cause: The Reader Time Limit session property specified for the SAPALEIDoc source definition contains an invalid value. Action: In the session properties, edit the Reader Time Limit value so that it is greater than or equal to 0. IDOC_17646 Failed to get connection reference for source qualifier instance <Source Qualifier>. Cause: Internal error. Action: Contact Informatica Technical Support. IDOC_17647 Failed to get connection for source qualifier instance <Source Qualifier>. Cause: Internal error. Action: Contact Informatica Technical Support. IDOC_17648 Failed to initialize reader properties for source qualifier instance <Source Qualifier>. Cause: The Integration Service cannot initialize the session. The session properties for the Source Qualifier instance might be invalid. Action: Check the additional error message for more information. IDOC_17649 Incorrect connection type specified for SAPALEIDoc source. Cause: In the session properties, an invalid application connection type was selected for the SAPALEIDoc source definition. An SAPALEIDoc source definition must use an SAP_ALE_IDoc_Reader application connection. Action: In the session properties, select an SAP_ALE_IDoc_Reader application connection for the SAPALEIDoc source definition. IDOC_17652 The value for the property [TypeOfEP] should be [IDocInterpreter]. Cause: In the 6.x IDoc_Interpreter EP transformation, the TypeOfEP property is not set to IDocInterpreter. Action: Edit the transformation so that the TypeOfEP property is equal to IDocInterpreter. IDOC_17655 The Integration Service failed to fetch the IDoc packet. Cause: The Integration Service encountered an error while reading IDocs from the SAP system. Action: See the additional error messages for more information. 238 Chapter 32: IDOC Messages
- 255. IDOC_17656 The Integration Service failed to process the IDoc packet for transaction ID = <ID>. Cause: The RFC Destination created in the SAP system for the Integration Service may be invalid. Action: Verify that the RFC Destination is valid. IDOC_17658 The SAPALEIDoc source definition can have only one input group. Cause: The SAPALEIDoc source definition contains more than one input group. Action: Recreate the SAPALEIDoc source definition. IDOC_17659 The SAPALEIDoc source definition may contain incorrect port names. Cause: The SAPALEIDoc source definition may contain incorrect port names. Action: Recreate the SAPALEIDoc source definition. 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. Cause: The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. Action: Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. IDOC_17666 Failed to initialize writer properties for target instance <target>. Cause: The Integration Service could not initialize the writer properties for the specified target. The session failed. Action: Check the additional error message for more information. IDOC_17668 <Connection property> not specified. Cause: The Integration Service could not find a value for the specified connection property. Action: Check the additional error message for more information. IDOC_17669 Failed to get connection property <connection property>. Cause: Internal error. or Cause: The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. IDOC Messages 239
- 256. IDOC_17670 IDoc writer cannot get connection information for the target instance <target>. Cause: Internal error. Action: Contact Informatica Technical Support. IDOC_17671 Writer partition <partition> failed to register for recovery. Cause: The Integration Service could not configure recovery for the session. Action: Check the additional error message for more information. IDOC_17672 Data <data> truncated by writer. Cause: This is a warning message. The data for the segment exceeds the maximum length. The data was truncated. Action: Check the data for the segment specified in the message. Correct the length of the data for the next session run. IDOC_17675 IDoc reader failed to support recovery for the Source Qualifier instance <Source Qualifier name>. Cause: Internal error. Action: Contact Informatica Technical Support. IDOC_17676 Cache folder specified for reader partition <partition> is invalid. Cause: The recovery cache folder in the session properties is invalid. Action: In the session properties, specify a recovery cache folder. IDOC_17677 Reader partition <partition> failed to register for recovery. Cause: The Integration Service could not configure recovery for the session. Action: Check the additional error message for more information. IDOC_17678 Reader partition <partition> failed to cache message. Cause: The Integration Service failed to cache the SAP IDoc. The Integration Service might have written only part of the IDoc to the recovery cache before the session failed. Action: Check the additional error message for more information. IDOC_17679 Reader partition <partition> truncated last cached message from cache. Cause: This is an informational message. The Integration Service truncated the last IDoc in the cache. Action: None. 240 Chapter 32: IDOC Messages
- 257. IDOC_17680 Reader partition <partition> failed to truncate message cache to last serialized message: <error message>. Cause: The Integration Service could not truncate the last IDoc in the cache. Action: Check the additional error message for more information. IDOC_17681 IDoc Reader failed to cache a message: <error message>. Cause: The Integration Service could not cache an IDoc during the session. Action: Check the additional error message for more information. IDOC_17682 Reader partition <partition> failed to close checkpoint at EOF: <error message>. Cause: The Integration Service could not commit IDocs to the target when it reached the session condition(s) you specified in the session properties. The session failed. Action: Check the additional error message for more information. IDOC_17684 Reader partition <partition> failed to flush the cache: <error message>. Cause: The Integration Service could not flush the cache. Action: Check the additional error message for more information. IDOC_17685 Reader partition <partition> failed to read cached message. Cause: The Integration Service could not read the cached IDoc. The cache might contain inconsistencies. Action: Check the additional error message for more information. IDOC_17690 Reader partition <partition> failed to close checkpoint at real-time flush point: <error message>. Cause: The Integration Service could not commit IDocs to the target at the end of the Real-time Flush Latency interval. The session failed. Action: Check the additional error message for more information. IDOC_17691 IDoc Reader failed to deserialize cache message: <error message>. Cause: The Integration Service could not read the message from the recovery cache. Action: Check the additional error message for more information. IDOC_17692 Recovery is not supported for old versions of SAP outbound IDoc mappings. Cause: This is an informational message. The Integration Service cannot support recovery for outbound IDoc mappings you created in PowerCenter Connect for SAP R/3 7.0 or earlier. Action: If you want to run a session to read outbound IDocs from SAP using ALE, create a new outbound IDoc mapping. IDOC Messages 241
- 258. IDOC_17695 Error initializing the tree builders for partition <partition>. Cause: The metadata file used to create the SAP/ALE IDoc Interpreter transformation may be invalid. Action: Recreate the SAP/ALE IDoc Interpreter transformation. IDOC_17696 Error creating input row for group <group>. Cause: There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. IDOC_17697 Error setting data for the field: <field>. Same as IDOC_17696. IDOC_17698 Unknown error encountered while traversing the tree. Same as IDOC_17696. IDOC_17699 Error building the tree. Same as IDOC_17696. IDOC_17700 Error getting data for the field. Same as IDOC_17696. IDOC_17704 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because mandatory segment is missing: <segment name>. Cause: You configured the session to validate inbound IDocs before writing them to the SAP system. During the session, the Integration Service determined that a value for the mandatory segment in the IDoc is missing. Action: Verify that the SAP/ALE IDoc Prepare transformation for the inbound IDoc contains values for the mandatory segment. IDOC_17705 Syntax validation failed for primary key <primary key> and corresponding generated document number <document number> because maximum occurrence is higher than maximum limit for: <segment name>. Cause: You configured the session to validate inbound IDocs before writing them to the SAP system. During the session, the Integration Service determined that the segment contains more than the allowed number of records. Action: Correct the source data so that the number of records for the segment do not exceed the maximum number allowed. 242 Chapter 32: IDOC Messages
- 259. 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>. Cause: You configured the session to validate inbound IDocs before writing them to the SAP system. During the session, the Integration Service determined that the segment contains less than the minimum number of records allowed. Action: Correct the source data so that the number of records for the segment meet the minimum number of records allowed. IDOC_17707 NULL data obtained for primary/foreign key fields. Cause: Data for the primary or foreign key fields is missing. Action: Make sure your data contains primary and foreign keys. IDOC_17708 NULL data obtained for all connected fields for the segment <segment name>. Cause: Data for the connected fields in the named segment is missing. Action: Make sure the data exists for the connected fields in the named segment. IDOC_17709 Data <data> overflow at port <port number>. If the error threshold is not met, the row will be sent through the ErrorIDocData port. Cause: The SAP/ALE IDoc Prepare transformation received data that is larger than the precision for the row. Action: Correct the source data so that the value matches the precision for the row. IDOC_17710 <Value> orphan rows were received by the SAP/ALE IDoc Prepare transformation. Cause: The SAP/ALE IDoc Prepare transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. Action: Verify that all child rows have parent rows. IDOC_17711 <Value> duplicate rows were received by the SAP/ALE IDoc Prepare transformation. Cause: The SAP/ALE IDoc Prepare transformation received duplicate rows. Action: Eliminate the duplicate rows in your data. 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>. Cause: The SAP/ALE IDoc Prepare transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. Action: Verify that all child rows have parent rows. IDOC Messages 243
- 260. IDOC_17713 Duplicate row received in group <group> with primary key: <primary key>. Cause: The SAP/ALE IDoc Prepare transformation received duplicate rows. Action: Eliminate the duplicate rows in your data. IDOC_17714 The following IDoc data is not of proper length: <value>. Cause: The SAP/ALE IDoc Interpreter transformation received IDoc data that is less than the fixed length of 1063 characters for each segment. Action: Correct the source data so that it equals 1063 characters for each segment. IDOC_17720 The SAP/ALE IDoc Prepare transformation has an unconnected input group. Connect all input groups for the transformation. Cause: One or more input groups in the SAP/ALE IDoc Prepare transformation are not connected. Action: Make sure that all input groups are connected. IDOC_17721 Error encountered while setting data for group: <group name>. Cause: There is not enough disk space to perform the desired operation. Action: Check the disk for free space. IDOC_17722 Syntax validation failed for document number <document number> because mandatory segment is missing: <segment name>. Cause: The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. During the session, the Integration Service determined that a value for the mandatory segment in the IDoc is missing. Action: Correct the source data so that the mandatory segment contains values. IDOC_17723 Syntax validation failed for document number <document number> because maximum occurrence is higher than maximum limit for: <segment name>. Cause: The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. During the session, the Integration Service determined that the segment contains more than the allowed number of records. Action: Correct the source data so that the number of records for the segment do not exceed the maximum number allowed. IDOC_17724 Syntax validation failed for document number <document number> because minimum occurrence is less than the minimum limit for: <segment name>. Cause: The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. During the session, the Integration Service determined that the segment contains less than the minimum number of records allowed. 244 Chapter 32: IDOC Messages
- 261. Action: Correct the source data so that the number of records for the segment meet the minimum number of records allowed. IDOC_17725 Extended Syntax Check skipped because Error Output port is missing. Recreate the SAP/ALE IDoc Interpreter transformation. Cause: The outbound IDoc session contains an SAP/ALE IDoc Interpreter transformation created in version 7.x. The Extended Syntax Check session property is selected. However, the Integration Service cannot validate outbound IDocs for an SAP/ALE IDoc Interpreter transformation created in earlier versions because the transformation does not contain an Error Output port. Action: Recreate the SAP/ALE IDoc Interpreter transformation. IDOC_17742 Cache folder specified for the SAP/ALE IDoc Prepare transformation <transformation name> is invalid. Cause: The cache directory specified for the SAP/ALE IDoc Prepare transformation does not exist. Action: In the session properties, enter a valid directory for the Cache Directory property. IDOC_17743 The Integration Service could not access the cache block in group <group>. Increase the cache size. Cause: The cache size specified for the SAP/ALE IDoc Prepare transformation is inadequate. Action: In the session properties, increase the cache size. IDOC_17744 The SAP/ALE IDoc Prepare transformation did not receive control record data for the IDoc type <IDoc type>. Cause: The source in the inbound IDoc mapping does not contain valid data for the IDoc control record. Action: Verify that the source data contains valid control record data. IDOC_17747 <Value> orphan rows were received by the SAP/ALE IDoc Interpreter transformation. Cause: The SAP/ALE IDoc Interpreter transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. Action: Verify that all child rows have parent rows. IDOC Messages 245
- 262. IDOC_17748 The SAP/ALE IDoc Interpreter transformation received orphan row <index of the row> in group <group> with primary key <primary key>. Cause: The SAP/ALE IDoc Interpreter transformation received an orphan row. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. Action: Verify that all child rows have parent rows. IDOC_17749 <Value> duplicate rows were received by the SAP/ALE IDoc Interpreter transformation. Cause: The SAP/ALE IDoc Interpreter transformation received duplicate rows. The transformation uses the segment number as the primary key to detect duplicate rows. The segment number is part of the header data for each segment data row that the transformation receives for the IDoc message. Action: Verify that each segment in the IDoc message has a unique segment number. IDOC_17750 Reader buffer flush failed. Cause: Internal error. Action: Contact Informatica Technical Support. 246 Chapter 32: IDOC Messages
- 263. Chapter 33 ISTP Messages This chapter includes the following topic: โฆ ISTP Messages, 248 Error messages listed numerically. 247
- 264. ISTP Messages Information forthcoming. 248 Chapter 33: ISTP Messages
- 265. Chapter 34 JMS Messages This chapter includes the following topic: โฆ JMS Messages, 250 Error messages listed numerically. 249
- 266. JMS Messages JMS_1001 Failed to connect to a JNDI provider: <error message>. Cause: The Integration Service could not connect to a JNDI provider. Action: Check the additional error message for more information. JMS_1002 The object <object name> looked up from JNDI is not a Destination object. Cause: The value for JMS Destination in the JMS application connection is not valid. Action: Enter a valid value for JMS Destination. Use a value that exists in your JNDI configuration. JMS_1003 Failed to set JMS exception listener: <error message>. Cause: The Integration Service cannot set a listener for JMS exceptions. Action: Check the additional error message for more information. JMS_1004 The object <object name> is not a QueueConnectionFactory object in JNDI. Cause: The value for JMS Connection Factory Name in the JMS application connection is not valid. The name of the connection factory is not a queue connection factory name in your JNDI configuration. Action: Enter a valid queue connection factory name for the JMS Connection Factory Name attribute in the application connection. JMS_1005 The object <object name> is not a TopicConnectionFactory object in JNDI. Cause: The value for JMS Connection Factory Name in the JMS application connection is not valid. The name of the connection factory is not a topic connection factory name in your JNDI configuration. Action: Enter a valid topic connection factory name for the JMS Connection Factory Name attribute in the application connection. JMS_1006 The destination object is not a Queue object. Cause: The value for the JMS Destination attribute in the JMS application connection is not a valid queue name. However, the value for JMS Destination Type in the application connection is QUEUE. Action: Provide a valid queue name for the JMS Destination attribute. Make sure the queue name exists in your JNDI configuration. or Action: Change the Destination Type to TOPIC if the value for the JMS Destination attribute is a topic. 250 Chapter 34: JMS Messages
- 267. JMS_1007 The destination object is not a Topic object. Cause: The value for the JMS Destination attribute in the JMS application connection is not a valid topic. However, the value for JMS Destination Type in the application connection is TOPIC. Action: Provide a valid topic for the JMS Destination attribute. Make sure the topic exists in your JNDI configuration. or Action: Change the JMS Destination Type to QUEUE if the value for the JMS Destination attribute is a queue. JMS_1008 Failed to create JMS connection: <error message>. Cause: The Integration Service cannot connect to JMS. As a result, the PowerCenter session failed. Action: Check the additional error message for more information. JMS_1009 Failed to create JMS session: <error message>. Cause: The Integration Service cannot start a JMS session. As a result, the PowerCenter session failed. Action: Check the additional error message for more information. JMS_1010 Failed to create JMS connection consumer: <error message>. Cause: The Integration Service cannot create a JMS connection consumer. As a result, the PowerCenter session failed. Action: Check the additional error message for more information. JMS_1011 Failed to start JMS connection: <error message>. Cause: The Integration Service could not initialize a JMS connection. As a result, the PowerCenter session failed. Action: Check the additional error message for more information. JMS_1012 Failed to stop JMS connection: <error message>. Cause: The Integration Service could not stop the JMS connection. Action: Check the additional error message for more information. JMS_1013 Failed to close JMS connection: <error message>. Cause: The Integration Service could not close the JMS connection. Action: Check the additional error message for more information. JMS_1014 Failed to close JNDI connection: <error message>. Cause: The Integration Service could not close the JNDI connection. JMS Messages 251
- 268. Action: Check the additional error message for more information. JMS_1015 Failed to look up object <object name> from JNDI. Cause: The specified value in the JMS application connection is not valid. As a result, the session failed. Action: Make sure the attribute value in the JMS application is valid. Make sure the value exists in your JNDI configuration. or Cause: The JNDI server may not be running. Action: Verify that the JNDI server is running. If necessary, start the server. JMS_1018 Cannot find message type from metadata extension. Cause: JMS cannot find the message type represented in the source or target definition. The repository may contain inconsistencies. Action: Contact Informatica Technical Support. JMS_1019 Cannot find JMS connection. Cause: There may be no application connection specified for the Source Qualifier or target in the session properties. Action: Specify a value for the application connection in the session properties. or Cause: The repository may contain inconsistencies. Action: Contact Informatica Technical Support. JMS_1020 Failed to create the message consumer: <error message>. Cause: JMS could not create the message consumer. The PowerCenter session failed. Action: Check the additional error message for more information. JMS_1021 Failed to create the message consumer because of conflicting JMS session and JMS connection objects. Cause: Internal error. Action: Contact Informatica Technical Support. JMS_1022 Failed to get the JMS destination <destination>. Reason: <error message>. Cause: The specified value for the JMS Destination attribute in the JMS application connection does not exist in your JNDI configuration. Action: Configure JNDI to include the value. Or, use a value that exists in your JNDI configuration. 252 Chapter 34: JMS Messages
- 269. JMS_1023 Failed to get the Queue Connection Factory <queue connection factory>. Reason: <error message>. Cause: The Integration Service cannot retrieve the queue connection factory from JNDI to connect to JMS. The value for the JMS Connection Factory Name attribute may not be valid. Action: Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in your JNDI configuration. or Cause: The JNDI server may not be running. Action: Verify that the JNDI server is running. If necessary, start the JNDI server. JMS_1024 Failed to get the Topic Connection Factory <topic connection factory>. Reason: <error message>. Cause: The Integration Service cannot retrieve the topic connection factory from JNDI to connect to JMS. The value for the JMS Connection Factory Name attribute may not be valid. Action: Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in your JNDI configuration. or Cause: The JNDI server may not be running. Action: Verify that the JNDI server is running. If necessary, start the JNDI server. JMS_2002 Error in getting the session extension information for Source Qualifier <Source Qualifier name>. Cause: The Integration Service cannot read the session properties. The repository may contain inconsistencies. Action: Contact Informatica Technical Support. JMS_2025 An error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>. Cause: The Integration Service could not process a message. Action: Check the additional error message for more information. JMS_2026 JMS error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>. Cause: The Integration Service encountered a JMS error while processing a message. Action: Check the additional error message for more information. JMS Messages 253
- 270. JMS_2027 The data received is too large for processing the field <field name> by Source Qualifier <Source Qualifier name>. Reason: <error message>. Cause: The Integration Service cannot process data for the specified field. The data is too large. Action: Check the additional error message for more information. JMS_2028 The message received by Source Qualifier <Source Qualifier name> does not match the body definition. Cause: The Integration Service received a message whose body fields do not match the source definition. The Integration Service rejected the message. Action: Make sure the body fields of the messages the Integration Service reads from the source match the format of the source definition. Otherwise, the Integration Service rejects the messages. JMS_2029 The Source Qualifier <Source Qualifier name> encountered an error in closing the consumer. Reason: <error message>. Cause: The Integration Service could not close the JMS consumer. Action: Check the additional error message for more information. JMS_2032 Unknown error occurred while writing the data to the DTM buffer by Source Qualifier <Source Qualifier name>. Reason: <error message>. Cause: The Integration Service encountered an unknown error during the session. Action: Check the additional error message for more information. JMS_2035 The partition #<number> of Source Qualifier <Source Qualifier name> failed to get cache coordinator for recovery. Cause: Internal error. Action: Contact Informatica Technical Support. JMS_2036 File cache folder is not provided. Please enter a file cache folder. Cause: You enabled message recovery for the session, but did not specify a file cache folder. Action: In the session properties, enter a file cache folder. JMS_2037 Failed to create storage information object for Guaranteed Message Delivery. Reason: <error message>. Cause: You ran a session with message recovery enabled for the session. However, the session failed when the Integration Service tried to write data to the recovery cache. Action: Check the additional error message for more information. 254 Chapter 34: JMS Messages
- 271. JMS_2038 Failed to register recovery cache. Reason: <error message>. Cause: The Integration Service could not register the session for message recovery. Action: Check the additional error message for more information. JMS_2041 Failed to recover data from recovery cache. Reason: <error message>. Cause: During a recovery session, the Integration Service could not read messages from the recovery cache. As a result, the session failed. Action: Check the additional error message for more information. JMS_2042 Unknown error encountered while recovering data from recovery cache. Cause: During a recovery session, the Integration Service encountered an unknown error. The cache might be corrupt. Action: Remove the cache file. Run the session again. JMS_2043 Failed to write data to recovery cache. Reason: <error message>. Cause: During a recovery session, the Integration Service could not write data to the recovery cache. Action: Check the additional error message for more information. JMS_2044 Source Qualifier <Source Qualifier name> encountered an error while acknowledging the message. Reason: <error message>. Cause: During a session to read messages from a JMS source, the Integration Service encountered an error acknowledging a source message. As a result, the session failed. Action: Check the additional error message for more information. JMS_2046 A data conversion error happened while processing the message for field <field name> in the Source Qualifier <Source Qualifier name>. Cause: During a session to read messages from a JMS source, the Integration Service could not process the specified field because of a data conversion error. The datatype for the field is not compatible with the datatype for the corresponding field in the source definition. Action: Make sure that the datatype for the field in the JMS source messages is compatible with the datatype in the source definition. JMS_2047 Message listener cannot be set: <error message>. Cause: The Integration Service cannot set the JMS message listener. As a result, the session failed. Action: Verify that your JMS settings are correct. Check the additional error message for more information. JMS Messages 255
- 272. JMS_2048 Error closing JMS session: <error message>. Cause: The JMS session cannot close. Action: Check the additional error message for more information. JMS_2050 Source Qualifier <Source Qualifier name> encountered error while receiving the JMS message. Reason: <error message>. Cause: During a session to read messages from a JMS source, the Integration Service encountered a JMS error. Action: Check the additional error message for more information. JMS_2051 The requested datatypes do not match the data written to the recovery cache. The cache may be corrupt. Cause: The message recovery cache file may contain inconsistencies. The session failed. Action: Manually delete the corrupted cache file. JMS_2052 The jms.jar library could not be loaded. Cause: The Integration Service could not start the session because it could not load the jms.jar file. Action: Verify that the jms.jar file is in the Integration Service /bin/javlib directory. JMS_3003 Cannot create writer connection: <error message>. Cause: The Integration Service cannot connect to JMS to write target messages. Action: Check the additional error message for more information. JMS_3004 Cannot close connection: <error message>. Cause: The Integration Service cannot close the JMS connection. Action: Check the additional error message for more information. JMS_3005 Cannot close JMS session: <error message>. Cause: The JMS session cannot close. Action: Check the additional error message for more information. JMS_3006 Cannot commit JMS session: <error message>. Cause: The Integration Service cannot commit messages to the JMS target. Action: Check the additional error message for more information. JMS_3007 Cannot roll back JMS session: <error message>. Cause: The Integration Service could not roll back messages from the target. Action: Check the additional error message for more information. 256 Chapter 34: JMS Messages
- 273. JMS_3008 Cannot create JMS message object: <error message>. Cause: Internal error. or Cause: Out of memory error. Action: Check the additional error message for more information. or Action: Contact Informatica Technical Support. JMS_3009 Cannot create message writer: <error message>. Cause: Internal error. or Cause: Out of memory error. Action: Check the additional error message for more information. or Action: Contact Informatica Technical Support. JMS_3013 Cannot create a message object because an invalid message type is given. Cause: Internal error. Action: Contact Informatica Technical Support. JMS_3014 The field <field name> is not a valid JMS target field. Cause: The repository may contain inconsistencies. Action: Contact Informatica Technical Support. JMS_3015 An invalid row type was encountered. JMS writer will publish a message if the row type is INSERT, UPDATE, and DELETE only. Cause: The row type for the source rows is Data Driven, but must be Insert, Update, or Delete. Action: From the Properties tab in the session properties, set the value for the Treat Source Rows As property to Insert, Update, or Delete. JMS_3016 JMS writer encountered an unknown row type error. Cause: Your repository may contain inconsistencies. Action: Contact Informatica Technical Support. JMS_3017 The value provided for <property name> in the JMS connection <connection name> is invalid. Reason: <error message>. Cause: The value for the specified property is not valid. JMS Messages 257
- 274. Action: Provide a valid value for the property in the session properties. JMS_3018 JMS writer encountered a JMS exception while field <field name> was being processed: <error message>. Cause: The Integration Service encountered a JMS exception while processing the specified field. The Integration Service increased the error threshold as a result of the error. Action: Check the additional error message for more information. JMS_3020 JMS writer encountered a data conversion error while field <field name> was being processed. Cause: The Integration Service could not convert the data for the specified field when writing messages to the JMS target. The field contains incompatible datatypes. The Integration Service rejected the field. Action: Make sure the datatypes in the target definition are compatible with JMS datatypes. JMS_3021 JMS writer encountered a general exception: <error message>. Cause: The JMS writer encountered an error. As a result, the session failed. Action: Check the additional error message for more information. JMS_3022 JMS writer encountered a general error: <error message>. Cause: The JMS writer encountered an error. As a result, the session failed. Action: Check the additional error message for more information. JMS_3023 JMS exception happened in JMS provider: <error message>. Cause: The target JMS provider encountered an error. As a result, the session failed. Action: Check the additional error message for more information. JMS_3024 Invalid datatype ID: <error message>. Cause: Internal error. Action: Contact Informatica Technical Support. JMS_3025 JMS writer received NULL for the field <field name>, which is set to Not Null. The message will be rejected. Cause: The specified field is set to Not Null in the target definition for the mapping. Action: Edit the target definition in the Designer, and clear the Not Null option for the field to prevent messages with a NULL value from being rejected. 258 Chapter 34: JMS Messages
- 275. JMS_3026 JMS writer encounters a JMS exception: <error message>. Cause: The Integration Service encountered a JMS error when writing messages to the target. As a result, the session failed. Action: Check the additional error message for more information. If the additional error message is an MQSeries JMS message regarding an invalid value for the JMSTimeToLive field in the target, it prints the value for field multiplied by 1,000. For example, if the JMSTimeToLive value in the target is -1, the MQSeries JMS message prints -1,000. JMS_3027 JMS writer encountered an out of memory error. Cause: JVM is out of memory. As a result, the PowerCenter session failed. Action: Increase the memory for JVM. Then restart the session. JMS_3028 JMS writer encountered an error in getting the default JMSReplyTo object <object name> from JNDI. Reason: <error message>. Cause: The Integration Service could not obtain a value for JMSReplyTo from JNDI. Action: Check the additional error message for more information. JMS_3029 JMS writer encountered an error in processing the data for the field <field name> in the target <target name>. Reason: <error message>. Cause: The Integration Service could not process data for the specified field in the target. Action: Check the additional error message for more information. JMS Messages 259
- 276. 260 Chapter 34: JMS Messages
- 277. Chapter 35 JSDK Messages This chapter includes the following topic: โฆ JSDK Messages, 262 Error messages listed numerically. 261
- 278. JSDK Messages JSDK_42021 Failed to load the library: <library name>. Cause: You attempted to run a session to read messages from a JMS source or write messages to a JMS target. Or, you attempted run a session to read documents form a webMethods source or write documents to a webMethods target. However, the JVM library is not properly set on the machine hosting the Integration Service. Action: If the Integration Service runs on Windows, verify that the path to the jvm.dll file is properly set. You can do this from the Environment tab in the Systems settings on the Control Panel. or Action: If the Integration Service runs on UNIX or Linux, make sure the library path for the JVM library is properly set. 262 Chapter 35: JSDK Messages
- 279. Chapter 36 JTX Messages This chapter includes the following topic: โฆ JTX Messages, 264 Error messages listed numerically. 263
- 280. JTX Messages JTX_1001 Failed to create partition driver. Exception occurred while loading partition driver class from byte code : <exception text>. Cause: The Integration Service failed to create the partition driver for the Java transformation class. This error can occur due to inconsistent byte code in the repository. Action: Use the Designer to recompile the byte code for the Java transformation, and run the session again. JTX_1002 Failed to find metadata extension <metadata extension name>. Cause: The repository stores the code for the Java transformation in metadata extensions for the Java transformation. The Integration Service could not find the metadata extensions that correspond to the code for the Java transformation in the repository. This error can occur due to inconsistent metadata in the repository. Action: Use the Designer to save the Java transformation to the repository, and run the session again. Otherwise, contact Informatica Technical Support. JTX_1003 Failed to retrieve metadata for input/output ports : <port names>. Cause: The Integration Service could not retrieve the metadata for the input and output ports in the Java transformation from the repository. This error can occur due to inconsistent metadata in the repository. Action: Use the Designer to save the Java transformation to the repository, and run the session again. Otherwise, you need to recreate the repository. JTX_1005 Column name <name> is invalid. Cause: The Integration Service could not retrieve the metadata for the Java transformation because the column name is invalid. Action: None. JTX_1006 Invalid number of groups. Java Transformation should have exactly one input and one output group. Cause: The Java transformation contains more than one input group or output group. Action: Edit the Java transformation in the Designer and remove the extra group or groups. JTX_1008 Row type <row type> is invalid. Valid row types for setOutRowType API are INSERT, DELETE, and UPDATE. Cause: You used the setOutRowType API to set the output row type for the Java transformation. However, the row type is invalid. Valid row types are INSERT, DELETE, and UPDATE. 264 Chapter 36: JTX Messages
- 281. Action: Change the row type for the setOutRowType API to a valid type. JTX_1009 Failed to create partition driver. Invalid byte code for Java transformation. Cause: The Integration Service failed to create the partition driver for the Java transformation class. This error can occur due to inconsistent byte code in the repository. Action: Use the Designer to recompile the byte code for the Java transformation, and run the session again. JTX_1010 Transformation name cannot be null. Failed to create class loader. Cause: The Integration Service failed to create the class loader for a particular Java transformation because it could not retrieve the transformation name from the repository. Action: None. JTX_1011 Error thrown by Java transformation failSession API : <error text>. Cause: You used failSession to throw a fatal error in the Java transformation. Action: None. JTX_1013 Error message: <message text>. Cause: You used logError to add an error message to the session log for a Java transformation. Action: None. JTX_1014 Parameter for Java transformation API <method name> cannot be NULL. Cause: You passed a parameter with a value of NULL to an API method in a Java transformation. However, parameters for APIs in a Java transformation cannot be NULL. Action: Modify the code for the Java transformation to pass a non-NULL parameter to the API method. JTX_1015 Exception thrown from Java transformation : <exception text>. Cause: The code in a Java transformation threw an error. This message only occurs when the code to throws an SDKException. Action: None. JTX_1016 Cannot use Java transformation API <method name> when transformation property <name> is not selected. Cause: You used the API method in an active Java transformation. However, the transformation property was not selected. You must select the transformation property to use the API method in an active Java transformation. JTX Messages 265
- 282. Action: Use the API method only after setting the appropriate transformation property. JTX_1017 Cannot use Java transformation API <method name> in a passive Java transformation. Cause: You used the API method in a passive Java transformation, However, you cannot use the specified API method in a passive transformation. Action: If you want to use the API method, create a new active Java transformation. JTX1018 Cannot set default value for port <name>. Error : <error text>. Cause: The Integration Service failed to evaluate the default value for the port. Action: Verify the default value for the port in the Designer. JTX_1101 Cannot create JExpression instance. Cause: In the Java code for the transformation, the call to defineJExpression failed. Action: In the Designer, verify that the expression being defined is valid and run the session again. JTX_1102 Row type <type> for Java expression is invalid. Valid row types are: INSERT, DELETE and UPDATE Cause: You used an invalid row type in a Java expression. Valid row types are INSERT, DELETE, and UPDATE. Action: Use a valid row type. JTX_1103 Result of Java expression is NULL. Cause: You used a Java expression in a Java transformation that returned a NULL value. You cannot return NULL values from a Java expression. Action: Modify the Java expression in the Designer so it returns a non-NULL value. JTX_1104 Invalid Java expression API call - result datatype is <type>. Cause: You passed an invalid datatype to an API method in a Java expression. Action: Modify the call to the API method to pass a valid datatype, or use the correct API method. JTX_1105 Invalid datatype returned from Java expression. Cause: The Java expression returned an invalid datatype. Valid datatypes are Integer, Double, String, and Byte[]. Action: Modify the Java expression to return a valid datatype. JTX_1106 Session object is NULL. Cause: Integration Service failed to fetch the session object from the repository. 266 Chapter 36: JTX Messages
- 283. Action: Contact Informatica Technical Support. JTX_1107 Invalid argument datatype for expression. Cause: You passed an invalid datatype to an expression in a Java transformation. The argument for the expression is a different type than the one you passed to the expression. Action: Pass the correct datatype to the expression. JTX_1108 String parameter of Java expression API method <method name> cannot be NULL. Cause: You passed a NULL value for the String parameter of a Java expression API method. The String parameter cannot take a NULL value. Action: Modify the call the Java expression API method to pass a non-NULL value to the String parameter. JTX_1109 Incorrect number of parameters passed to expression <expression name>. <number> parameters passed, expression requires <number>. Cause: You did not pass the required number of parameters to an expression in a Java transformation. Action: Edit the Java code for the transformation and pass the correct number of parameters to the expression. JTX_1110 Ignored extra parameters for expression <expression name>. Cause: You passed more parameters to the expression in a Java transformation than the expression requires. The Integration Service ignored the extra parameters. Action: None. If you do not want the Integration Service to ignore the extra parameters, modify the definition for the Java expression. JTX_1111 Cannot use NULL value for parameter in Java expression API method <method name>. Cause: You passed a NULL value to a parameter in a Java expression API method. However, you cannot pass NULL values for Java expression API method parameters. Action: Pass a non-NULL value for the Java expression API method. JTX_1112 Truncated string data <data> for parameter X<parameter name> in expression <expression name>. Cause: The length of the string data for the expression exceeded the precision for the string parameter. As a result, the Integration Service truncated the data for the parameter. Action: Increase the precision of the parameter for the expression. JTX Messages 267
- 284. JTX_1113 Truncated binary data for parameter X<parameter name> in expression <expression name>. Cause: The length of the binary data for the expression exceeded the precision for the binary data parameter. As a result, the Integration Service truncated the data. Action: Increase the precision for the binary data parameter for the expression. JTX_1114 Failed to load class [<class name>] : [<error text>]. Cause: The Integration Service could not load the Java transformation class or an inner class in a Java transformation. This error can occur if the repository contains inconsistent data for the byte code or the repository does not contain the updated byte code for the transformation. Action: Correct the error indicated in the message and run the session again. You may need to recompile the Java code for the transformation in the Designer. JTX_1115 Exception occurred during initialization of JExpression object <name>. Cause: Initialization of JExpression object failed. Action: Verify the defined expression is valid and run the session again. JTX_1117 Data was truncated for field [port name]. Cause: The precision of the data assigned to a binary or string output port in a Java transformation is greater than the configured precision for the port. As a result, the Java transformation truncated the data for the port. This warning can occur for data assigned to an output port. Action: Make sure the precision of the port is equal to or greater than the precision of the data assigned to the port. JTX_60000 Cannot validate Java transformation. Unable to retrieve metadata extensions from repository. Cause: The Designer or Integration Service encountered an internal error when retrieving the metadata extensions for the Java transformation. Action: Contact Informatica Technical Support. JTX_60001 Cannot validate Java transformation. Unable to retrieve Java code snippets from the repository. Cause: The Designer or Integration Service encountered an internal error when retrieving the Java code snippets for the transformation from the repository. Action: Contact Informatica Technical Support. JTX_60002 Cannot validate Java transformation. Unable to retrieve byte code from the repository. Cause: The Designer or Integration Service encountered an internal error when retrieving the byte code for the transformation from the repository. 268 Chapter 36: JTX Messages
- 285. Action: Contact Informatica Technical Support. JTX_60003 Cannot validate Java transformation. Unable to retrieve CRC value from the repository. Cause: The Designer or Integration Service encountered an internal error when retrieving the CRC value for the transformation from the repository. The Designer or Integration Service compares the current CRC value for the byte code to the CRC value stored in the repository to verify the byte code for the transformation. Action: Contact Informatica Technical Support. JTX_60004 Byte code for the transformation is not in the repository. Java transformation is invalid. Cause: The byte code for the transformation is not in the repository. Action: Compile the Java code for the transformation, and validate the transformation or mapping. JTX_60005 Byte code in the repository is invalid. Java transformation is invalid. Cause: The CRC value for the byte code retrieved from the repository does not match the CRC value stored in the repository. As a result, the transformation is not valid. Action: Compile the Java code for the transformation, and validate the transformation or mapping. JTX_60007 Cannot retrieve object class for <class name>. Cause: The Java Runtime Environment cannot retrieve the object class for the class name in the byte code. This error can occur when the pmjtx.jar file in the server/bin/javalib directory contains inconsistent data. Action: Contact Informatica Technical Support. JTX_60008 Cannot find method <method name> in class <class name>. Cause: The Java Runtime Environment cannot find the Java method in the byte code for the transformation. This error can occur when the pmjtx.jar file in the server/bin/javalib directory contains inconsistent data. Action: Contact Informatica Technical Support. JTX_60009 Cannot create object of class <class name>. Cause: The Java Runtime Environment could not create an object for a Java transformation class. This error can occur when there is not enough memory available to the JRE when it runs the byte code for a Java transformation. Action: Make sure there is enough memory available and run the session again. JTX Messages 269
- 286. JTX_60010 Cannot create global reference to class <class name>. Cause: The Java Runtime Environment could not create a global reference to a Java transformation class. This error can occur when there is not enough memory available to the JRE when it runs the byte code for a Java transformation. Action: Make sure there is enough memory available and run the session again. JTX_60011 Cannot use getLong API - result datatype not Time or Date. Cause: A Java expression created with the advanced interface uses the getLong API to get the result of an expression that does not return a Date or Time value. You can only use getLong to get the result of an expression with a Date or Time return value. Action: Use the getInt or getDouble API with the expression. JTX_60012 Datatype of argument x<number> is invalid. Cause: The datatype of the argument passed to a Java expression is invalid. Action: Contact Informatica Technical Support. JTX_60013 Cannot validate Java transformation. Unable to retrieve classpath from the repository. Cause: The Designer or Integration Service could not retrieve the value of the classpath for the Java transformation from the repository. This error can occur due to inconsistent data in the repository. Action: Contact Informatica Technical Support. JTX_60014 Cannot validate Java transformation. Unable to retrieve precision mode from the repository. Cause: The Designer or Integration Service could not retrieve the value of the precision mode for the Java transformation from the repository. This error can occur due to inconsistent data in the repository. Action: Contact Informatica Technical Support. 270 Chapter 36: JTX Messages
- 287. Chapter 37 LB Messages This chapter includes the following topic: โฆ LB Messages, 272 Error messages listed numerically. 271
- 288. LB Messages LB_47007 Submitted task [task name] was canceled by a user. Cause: The Session or Command task failed because it was stopped. Action: Restart the task. LB_47008 Submitted task [task name] was canceled because no available node has the resources required by the task. Cause: The Session or Command task failed because no available node has the resources required by the task. Action: Verify that at least one node has the resources required to run the task. Verify the nodes that have the required resources are running and available. LB_47010 The Integration Service failed to load the external resource manager library due to error [error text]. Cause: The PowerCenter administrator configured PowerCenter to work with a third- party resource manager. The Integration Service is unable to load the resource manager library. Action: Verify the following: โ The third-party resource manager library exists in the location specified in the PATH. โ The user account authorized to start Informatica Services has read and execute permissions on the library file. โ The library file is not corrupt. LB_47011 The Integration Service failed to retrieve the external resource manager interface due to error [error text]. Cause: The PowerCenter administrator configured PowerCenter to work with a third- party resource manager. The Integration Service is unable to access the resource manager interface. Action: Contact the third-party resource manager technical support. LB_47012 The external resource manager interface failed to initialize due to error [error text]. Cause: The PowerCenter administrator configured PowerCenter to work with a third- party resource manager and the resource manager failed to initialize. Action: Contact the third-party resource manager technical support. LB_47047 The load balancer failed to detach node [node name]. Cause: Internal error. The Load Balancer could not detach the node because there are tasks still reserved or started on the node. 272 Chapter 37: LB Messages
- 289. Action: Contact Informatica Technical Support. LB_47050 Received final notice for request on invalid node [node name] with event code [code]. Cause: Internal error. The Load Balancer received a request from a node that has shut down. Action: Contact Informatica Technical Support. LB Messages 273
- 290. 274 Chapter 37: LB Messages
- 291. Chapter 38 LDBG Messages This chapter includes the following topic: โฆ LDBG Messages, 276 Error messages listed numerically. 275
- 292. 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. Cause: During a user-defined commit session, the Data Transformation Manager ran out of buffer pool data blocks, which caused the session to fail. Action: In the session properties, increase the DTM buffer block size. or Action: Modify the Transaction Control expression or the Custom transformation procedure code so that the transformation issues commits more frequently. LDBG_21035 Datablock write-lock error. offset <offset value>, reason [No space left on device]. Cause: The Integration Service could not write data to the disk because there is not enough space. Action: Increase the amount of free space on the Integration Service system disk. Verify that the operating system does not limit the amount of disk space for the user who starts the Integration Service. or Cause: This message follows CMN_1107. The Integration Service could not write to a Joiner index or data cache file because there is not enough space on the disk. Action: Increase the Joiner index and data cache sizes. If possible, increase the index and data cache sizes to hold all of the data. LDBG_21149 ERROR determining truncate table order - could not create constraint load dependencies for target. Cause: You are attempting to truncate target tables, but the Integration Service is unable to determine dependencies between target tables, possibly due to errors such as circular key relationships. Action: Ensure the validity of dependencies between target tables. LDBG_21178 ERROR: Self-referential constraint in target. Cause: You have set the session for constraint-based loading, but the Integration Service is unable to determine dependencies between target tables, possibly due to errors such as circular key relationships. Action: Ensure the validity of dependencies between target tables. 276 Chapter 38: LDBG Messages
- 293. 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. Cause: The mapping writes to target tables that have a primary key-foreign key relationship, but the targets receive data from different transaction generators, such as a Transaction Control transformation, or active sources. The Integration Service cannot enforce the primary key-foreign key relationship. The session might hang depending on the source data. Action: If the session hangs, design the mapping to enforce constraint-based loading. Or, remove the primary key-foreign key relationship between the targets in the target database. LDBG_21604 Data block read-lock error, offset <number>, reason: <reason>. Cause: Error occurred trying to read from the joiner cache. Action: Truncate the targets and run the session again. LDBG_21605 Cannot open files in the directory <directory name>. Cause: Cannot open files in the joiner cache directory. Action: Check file system permission and free space in the cache directory. LDBG_21633 For the dynamic lookup cache for [Lookup transformation], an input row has NULL value in condition fields. This row will not be used for update of the lookup cache. Cause: The Lookup transformation in the mapping uses a dynamic lookup cache, and the source row contains a null value in a column used in the lookup condition. Action: None. When the row exists in the lookup cache, the Integration Service does not update the row in the cache or target table. LDBG_21668 Error: The Informatica server license does not allow more than one database license to be used at a time. Cause: The Integration Service configuration contains more than one database license. Action: Your Informatica license does not allow you to use more than one database license at a time. Configure the Integration Service with only one database license. For more information, contact the Informatica Developer Network. LDBG Messages 277
- 294. 278 Chapter 38: LDBG Messages
- 295. Chapter 39 LGS Messages This chapter includes the following topics: โฆ LGS Messages, 280 Error messages listed numerically. 279
- 296. LGS Messages LGS_10006 The file [<file name>] was skipped during automatic purge. Cause: The day limit or size limit for log event files was reached, and the Log Manager purged the log event files. However, the Log Manager did not delete the file because it was in use or recently modified. Action: None. The Log Manager will delete the file during the next log purge if the file is not in use or recently modified. LGS_10010 Not all files are deleted in directory: [<directory name>]. Cause: The Log Manager attempted to purge the log event files in the directory. However, some of the log event files were recently modified or still in use by the Log Manager. Action: Same as LGS_10006. LGS_10011 Failed to access index file [<file name>] due to the following error [<error text>]. Cause: The Log Manager uses an index file in each log file directory for quick access to log event data files. The Log Manager was unable to read from or write to the index file. This error can occur when the permissions for an index file are modified or because the file was removed. Action: Correct the error indicated in the message and view log events, export log events, or purge log events again. Make sure the user account that runs Informatica Services has read and write permission on the file. LGS_10013 Invalid number of log events were received. Cause: The Log Manager attempted to retrieve log events, but the number of events is invalid. This error can occur when you use infacmd to retrieve log events, but you enter an invalid number of events. For example, you enter 0 for the number of log events to retrieve. Action: Enter a valid number of log events to retrieve. LGS_10016 Failed to close the file merge stream due to the following error [<error text>]. Cause: The Log Manager could not close multiple file streams to the same log event file. This error can occur because the permissions for the log event file were modified after the Log Manager began writing or because the file was removed. Action: Same as LGS_10008. LGS_10017 Error creating the directory [<directory name>]. Cause: The Log Manager could not create the directory in the shared location for log event files. This error can occur because the Log Manager does not have 280 Chapter 39: LGS Messages
- 297. sufficient access permissions on the shared directory location for the log event files. Action: Make sure the user account that runs Informatica Services has read and write permission on the shared directory location. LGS_10019 Failed to open the file stream [<file name>] due to the following error [<error text>]. Cause: The Log Manager was unable to open the log event file for reading or writing. This error can occur when the permissions for a log event file or the log event directory are modified after the Log Manager begins reading or writing or because the file was removed. Action: Same as LGS_10008. LGS_10021 Failed to read log event from the file stream [<file name>] due to the following error [<error text>]. Cause: The Log Manager attempted to retrieve log events from the log event file. However, the log event file contains inconsistent data. Action: Correct the error indicated in the message. LGS_10024 Log request failed due to the following error [<error text>]. Cause: The Log Manager attempted to retrieve log events from the shared directory location, but the retrieval failed due to an error. Action: Correct the error indicated in the message and view logs events again. LGS_10026 The log service configuration is missing the log service directory value for the node <node name>. Cause: The Log Manager could not write to the shared directory path for the log event files because the directory location is missing in the domain configuration. Action: Configure a directory for the log event files. LGS_10028 The index file [<file name>] is corrupt. Same as LGS_10011. LGS_10029 Failed to flush the file stream [<file name>] due to the following error [<error text>]. Same as LGS_10008. LGS_10034 Log request failed due to the following error [<error text>]. Unable to rollback changes due to the following error [<error text>]. Cause: The Log Manager wrote to log event files. However, the process was interrupted due to an error, and the Log Manager could not roll back the changes it made to the log event file. This error can occur if the Log Manager LGS Messages 281
- 298. writes to a shared directory location that becomes unavailable during the write process. Action: Correct the errors indicated in the message and make sure the shared directory location is available. LGS_10035 The timestamp index file [<file name>] is corrupted. Cause: The Log Manager uses the timestamp index file to access the log event files in a directory. However, the timestamp index file contains inconsistent data and the Log Manager cannot access the log event files in the directory. Action: None. LGS_10036 The index file in the directory [<directory name>] appears corrupted. Cause: The Log Manager uses an index file in each log file directory for quick access to log event data files. However, the index file contains inconsistent data and the Log Manager cannot access the log event files in the directory. Action: None. LGS_10052 The Log Manager could not find the session or workflow run. Cause: The Log Manager has no information about the session or workflow run. The name is invalid, the run is not the latest, or the database table was purged. Action: If you are using infacmd, verify that the workflow or session name is valid. If you are trying to get the session or workflow log in the Workflow Monitor, select the latest session or workflow run. 282 Chapter 39: LGS Messages
- 299. Chapter 40 LIC Messages Chapter 40 This chapter includes the following topic: โฆ LIC Messages, 284 Error messages listed numerically. 283
- 300. LIC Messages LIC_10000 The Service Manager is not initialized yet. Cause: The Tomcat servlet container has not initialized the Service Manager. Action: The Service Manager is still initializing. If the Service Manager is not initialized within five minutes, contact Informatica Technical Support. LIC_10004 The Service Manager is disabled and cannot accept licensing requests. Cause: The Service Manager on the master gateway experienced a problem and disabled itself. Action: Wait for a new master gateway to be elected. The new master gateway will enable its Service Manager. If a new master gateway does not come up automatically, manually recycle this node. LIC_10006 A request was received that was missing a required parameter. Cause: A request was received that was missing a required parameter. Action: If problem persists, contact Informatica Technical Support. LIC_10007 A request was received with the wrong <actual object type> parameter (expected: <expected object type>). Cause: A request was received that had the wrong type of parameter. Action: If problem persists, contact Informatica Technical Support. LIC_10010 The input vector must contain license name followed by at least one service name. Cause: A request was received with invalid parameters. Action: If problem persists, contact Informatica Technical Support. LIC_10011 License <license name> is not found. Cause: A request was received to process a license that could not be located. Action: Verify that the license is defined in domain. LIC_10013 The following services are already assigned: <list of services> Cause: A request was received to assign services to a license that were already assigned to another license. Action: Unassign these services before you assign them to another license. LIC_10014 Request parameters must contain a license name followed by an encrypted license key. Cause: A request was received with the wrong number of parameters. 284 Chapter 40: LIC Messages
- 301. Action: If problem persists, contact Informatica Technical Support. LIC_10015 Request parameters must contain source and target license names. Cause: A request was received with the wrong number of parameters. Action: If problem persists, contact Informatica Technical Support. LIC_10017 <service name> is not assigned to any license. Cause: A service was attempting to start that was not assigned to any license. Action: Assign the service to a license, and then enable or start the service. LIC_10018 Request parameters must contain a license name followed by a description. Cause: A request was received with the wrong number of parameters. Action: If problem persists, contact Informatica Technical Support. LIC_10019 Request parameters must contain a valid service name followed by a valid node name. Cause: A request was received with the wrong number of parameters. Action: If problem persists, contact Informatica Technical Support. LIC_10020 The operating system type could not be established for node <node name>. Cause: A service was attempting to start on a node where the platform could not be established. Action: If problem persists, contact Informatica Technical Support. LIC_10025 Cannot unassign from license <name of license> because services <list of services enabled> are enabled and/or services <list of services missing> were not found. Cause: A request was received to unassign enabled services. Action: Disable services before continuing. or Cause: A request was received to unassign an unknown service. Action: Verify the service names and resubmit. LIC_10026 License <license name>/<license serial number> cannot start service <service name> as it is not licensed to execute on platform <platform name>. Cause: A service was attempting to start on an unlicensed platform. Action: Contact your Informatica sales representative to update your license for specified platform. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request. LIC Messages 285
- 302. LIC_10027 Failed to add a license key that expired on <expiration date>. Cause: A request was received to add a license key that has already expired. Action: Contact your Informatica sales representative to extend your license. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request. LIC_10028 Failed to add a license key that is invalid because: <reason license key is invalid>. Cause: A request was received to add a license key that is invalid. Action: Verify that the license key being used is correct. LIC_10030 Attempted to use license <license name/<license serial number> for PowerCenter <product version> where license was purchased for <license version>. Cause: A service was assigned to a license for a different version. Action: Assign the service to a license for this version. LIC_10033 License <license name>/<license serial number> cannot start service <service name> as license has expired on <expiration date>. Cause: A service is assigned to an expired license. Action: Contact your Informatica sales representative to extend your license. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request. LIC_10034 License <license name>/<license serial number> cannot start service <service name> as license does not support grid processes. Cause: A service with a grid is assigned to a license that does not support grids. Action: Either assign service to a license that supports a grid or remove the grid from service. LIC_10035 License <license name>/<license serial number> cannot start repository instance <repo name> as license does not have a valid repository count. Cause: A Repository Service is assigned to a license that does not allocate Repository Services. Action: Assign the Repository Service to a license that supports Repository Services. LIC_10048 Failed to write license <license name>/<license serial number> new day record for logical CPUs on platform <platform>. Cause: A database write request failed to update records. Action: Verify that the domain configuration database is running. 286 Chapter 40: LIC Messages
- 303. LIC_10049 Failed to write license <license name>/<license serial number> new day record for repository instances. Cause: A database write request failed to update records. Action: Verify that the domain configuration database is running. LIC_10050 Failed to write license <license name>/<license serial number> record for <actual CPU count for platform> logical CPUs on platform <platform>. Cause: A database write request failed to update records. Action: Verify that the domain configuration database is running. LIC_10051 Failed to write license <license name>/<license serial number> record for <actual repo count> repository instances. Cause: A database write request failed to update records. Action: Verify that the domain configuration database is running. LIC_10052 Change occurred to service <service name> that could not be found within domain. Cause: The service must have been just deleted. Action: If problem persists, contact Informatica Technical Support. LIC_10053 Change occurred to node <node name> that could not be found within domain. Cause: The node must have been just deleted. Action: If problem persists, contact Informatica Technical Support. LIC_10054 Cannot locate license with serial number <license serial number>. Cause: The license must have been just deleted. Action: If problem persists, contact Informatica Technical Support. LIC_10055 Failed to find license for service <service name>. Cause: The service being processed is not assigned to a license. Action: Assign the service to a license. LIC_10056 License <license name>/<license serial number> cannot start service <service name> as license does not support backup nodes. Cause: A service with a backup node is assigned to a license that does not support high availability. Action: Either assign service to a license that supports high availability or remove backup nodes from service. LIC Messages 287
- 304. LIC_10061 Cannot validate license usage with invalid service name <service name>. Cause: License authorization was requested for a missing or invalid service name. Action: If problem persists, contact Informatica Technical Support. LIC_10062 Cannot validate license usage with invalid node name <node name>. Cause: License authorization was requested for a missing or invalid node name. Action: If problem persists, contact Informatica Technical Support. 288 Chapter 40: LIC Messages
- 305. Chapter 41 LM Messages This chapter includes the following topic: โฆ LM Messages, 290 Error messages listed numerically. 289
- 306. LM Messages LM_36053 The server mode <current server mode> is invalid. Default server mode <default server mode> will be used. Cause: You have modified the data movement mode in the Administration Console. Action: Change the data movement mode to ASCII or Unicode by modifying the Administration Console. LM_36072 Cannot get $PMStorageDir from configuration. Cause: A service process could not determine the storage directory used for failover and recovery. Action: Verify that $PMStorageDir is configured properly in the Integration Service process properties. LM_36129 Cannot open log file [name]. Cause: The Integration Service cannot open the named log file. Action: Verify that the log file exists in the directory you specified in the session or workflow properties. Also, verify that the user attempting to access the log file has read permission for the file. LM_36133 Fail in reading log file [name]. Cause: The Integration Service was able to open the named log file, but cannot read it. An administrator could have deleted the log file while you were attempting to access it. Action: Verify that the log file exists in the directory you specified in the session or workflow properties. Then try to access the file again. LM_36134 Session is initializing. Session log file is temporarily unavailable. Cause: You are trying to access a session log file while the session is still initializing. Action: Wait and open the file when the session has finished initializing. LM_36136 Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration Service. Cause: The specified task instance did not run. Action: Review the workflow log to view detailed information about why the task instance did not run. LM_36138 Cannot find workflow log name. Cause: You did not specify a workflow log name in the workflow properties. Action: Enter a workflow log name in the workflow properties. 290 Chapter 41: LM Messages
- 307. LM_36210 Get worklet instance name from repository failed. Cause: You may have deleted the worklet from the repository. Action: Verify that the worklet exists. or Cause: The database server or the Repository Service may have failed. Action: Verify that the database server and Repository Service are running. or Cause: The repository may contain inconsistencies. Action: Contact Informatica Technical Support. LM_36220 Log file [name] contains no data. Cause: The log file is empty, most likely because someone deleted its contents. Action: If you need to see the log file data, rerun the session or workflow to generate the log file again. LM_36225 The session log file was not created for session instance [ID = <number>] in folder [ID = <number>], workflow [ID = <number>] [run ID = <number>], worklet [ID = <number>] (possibly because the session failed during initialization). Cause: The Integration Service failed to create the named session log file because the session failed during initialization. Action: Check the workflow or server log file to see why the session failed. LM_36229 Request failed because the connection was broken or the client is too slow in processing replies, client [name], connection [name], request ID [number]. Cause: The Integration Service tried to retrieve a session or workflow log file over a network connection, but the connection was broken or timed out. Action: Check the network connection and try to open the log file again. LM_36269 Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, service name <service>, and service process name <node>. The connection request failed because the service process <node> is not the intended service process. Cause: A client application attempted a connection to a service process that is not the master service process. With pmcmd, this error occurs if you use the host name and port number options rather than the pmcmd options -d <domain> and -sv <service>. Action: Verify that the node is available and attempt the connection again. If you use pmcmd, use the options -d <domain> and -sv <service>. LM Messages 291
- 308. 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. Cause: The Service Manager could not find the Integration Service in the domain. Action: Verify that the Integration Service is running in the domain. Use the pmcmd options -d <domain> and -sv <service>, rather than the host name and port number options. LM_36272 Failed to get gateway information from URI <universal resource identifier>. Cause: The Integration Service could not identify the master gateway. Action: Verify that Informatica Services is running on the gateway node. Start Informatica Services on the gateway node. 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>. Cause: Internal error. Action: Contact Informatica Technical Support. LM_36274 Failed to look up service in domain <domain>, service <service>, service process <service process> from name service lookup using this URI <service process> with fault code <code>, fault message <message text>. Cause: The Service Manager failed to provide the connectivity information for the Integration Service for the specified reason. Action: Verify that the domain and the Integration Service are running. Verify that you used the correct uniform resource identifier (URI). LM_36275 Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the service is not configured to redirect connections. Cause: The Integration Service is configured so that connections are not redirected. Action: In the Integration Service properties, set the custom flag EnableConnectionRedirection to Yes, which is the default value. LM_36310 Workflow [name]: Cannot open log file [name]. Cause: The Integration Service could not open the named log file during execution of the named workflow. The workflow failed. 292 Chapter 41: LM Messages
- 309. Action: Verify that the workflow log file directory specified in the workflow properties exists and that the user attempting to access the log file has write permission for the file. LM_36311 Workflow [name]: Failed to expand workflow log file name <name>. Cause: The log file name for the named workflow is invalid. Action: Check the workflow log file name in the workflow properties. If you entered the file path directly or used server parameters to represent the file path in the Workflow Log File Name field, verify that the file path is correct and that the server parameters are spelled correctly. LM_36312 Workflow [name]: Log path exceeds limit of [number] characters: [path]. Cause: The workflow log file path you specified in the workflow properties is too long. Action: Shorten the file path so that it is less than or equal to the displayed character limit. LM 36320 <Workflow or task name>: Execution failed. Cause: Execution of workflow or task failed. Action: Review other messages in the workflow and session log to find the cause for failure, fix the problem, and then run the workflow again. LM_36338 Workflow [name] Could not start execution of this workflow because the current run on this Integration Service has not completed yet. Cause: You may be running the specified workflow. Action: Wait until the workflow completes to restart it. or Cause: You may have attempted to restart a workflow that is suspended but not stopped. Action: To restart a suspended workflow, choose resume to complete the workflow. or Cause: You made a change to a workflow that is set to run continuously. Action: Stop or unschedule the workflow, save the workflow, and then restart or reschedule the workflow. LM_36348 <Workflow, worklet, or session instance name>: Parameter file [name] not found. Cause: The Integration Service cannot locate the parameter file for the named workflow, worklet, or session. LM Messages 293
- 310. Action: Check the workflow or session properties to make sure the named parameter file exists in the specified directory. Also, check to make sure the user accessing the file has read permission for the file. LM_36349 <Workflow or worklet name>: Failure to create variable manager. Cause: Internal error. Action: Contact Informatica Technical Support. LM_36350 Error in binding the pre-defined variable <name>. Cause: Internal error. Action: Contact Informatica Technical Support. LM_36351 <Workflow name>: Error in persisting variable values. Cause: Internal error. The Integration Service failed to write the persistent variable value to the repository. Action: Contact Informatica Technical Support. LM_36362 Workflow <name>: The workflow log count in the repository is negative <number>. Cause: Internal error. Action: Contact Informatica Technical Support. LM_36363 Workflow <name>: Cannot rename workflow log file <file name> to <file name>. Cause: You saved the workflow logs for the named workflow by number of runs. The Integration Service encountered an error when it tried to rename an existing log file. The disk on which the log files are located might be out of space. Action: Check the disk and directory where the log file is located. Make sure the disk is not out of space. LM_36364 Workflow <name>: Failed to increment the log file number in the repository. Cause: Internal error. Action: Contact Informatica Technical Support. LM_36366 <Worklet name>: Failed to set the passed value for variable <name>. Cause: Internal error. The Integration Service failed to pass the initial value of the named variable to the named worklet. Action: Contact Informatica Technical Support. 294 Chapter 41: LM Messages
- 311. LM_36367 <Task instance name and path>: Suspension email has an empty user name. Cause: You configured the workflow to send a suspension email, but the email address for the suspension email is missing. Action: Enter an email address in the Email User Name field for the suspension Email task. LM_36368 <Task instance name and path>: Failed to send suspension email. Cause: You configured the workflow to send a suspension email, but the Integration Service failed to send the suspension email. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client. Action: Verify you specified an email profile on the machine hosting the Integration Service, and that the machine has the correct email client. LM_36369 <Session task instance> <task instance path> Encountered task instance <task instance name> of unknown type. Cause: The Integration Service has encountered a task type that it cannot recognize because the version of the Integration Service and repository are inconsistent. You have upgraded the repository but not the Integration Service. Action: Upgrade the Integration Service. LM_36381 <Worklet name>: Failed to set the passed value for variable <name>. Cannot find a user-defined variable with this name. Cause: The Integration Service attempted to override the initial value of the named variable in the named worklet, but it could not locate the named worklet variable. Action: Make sure you defined the named variable in the worklet. 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>. Cause: The Integration Service attempted to override the initial value of the named variable in the named worklet. It could not do this because it could not locate the named parent workflow or worklet variable. Action: Make sure you defined the named variable in the parent workflow or worklet. LM_36383 Error in expanding variable parameter. Cause: Internal error. Action: Contact Informatica Technical Support. LM Messages 295
- 312. LM_36385 Workflow <name>: Could not acquire the execute lock for Workflow <name>. Cause: You started the specified workflow, but the Load Manager could not lock the workflow before running it. This message occurs when you or another user is currently running the workflow. Action: Make sure that the workflow has finished running before running it again. LM_36401 <Session task instance> <task instance path> Execution terminated unexpectedly. Cause: The DTM process did not stop, abort, or fail properly. Action: Contact Informatica Technical Support. LM_36440 <Task type> task instance <task instance path>: Error in fetching persistent variable values for <workflow or worklet> [workflow or worklet name]. Cause: The Integration Service failed to get a persistent variable value for the workflow or worklet. Action: Check the Integration Service log and Repository Agent log for more information. LM_36441 Error: Both parameter list and parameter file are specified. Cause: A third party application tried to start a workflow and specified both a parameter list and a parameter file. The Integration Service needs one or the other to run a workflow, not both. Action: In the third party application, verify you only specify a parameter list or a parameter file. LM_36471 <Workflow name>: Failover of workflow schedule failed because the information in storage is inconsistent or incomplete. Cause: Trace message. If you have the high availability option, workflow schedule information is written to a storage file in the storage directory, $PMStorageDir. The Integration Service could not retrieve the information required to start up the scheduled workflow on another node. Action: Explicitly schedule the workflow again to run it. LM_36476 <Workflow name>: Failover of workflow execution failed because the workflow cannot be internally scheduled in recovery mode. Cause: After the Integration Service failed over the workflow to another node, an internal limit was exceeded. Action: Try to recover the workflow manually. Also, verify the availability of the node where the service process started the workflow. 296 Chapter 41: LM Messages
- 313. LM_36477 <Workflow name>: Failed to save workflow information for failover. Cause: The Integration Service was unable to write the workflow data to a storage file to enable failover. Action: Verify that the Integration Service can access the storage directory $PMStorageDir. To access the storage directory, the directory must be properly mapped or mounted, and the Integration Service must have the necessary security permissions. If the directory does not exist or cannot be written to, the requests cannot be stored for persistence. Verify that the directory is not full. LM_36527 <Task instance name and path>: Failed to fetch session to send post session email for this session instance. Cause: The repository containing the session object is not running. Action: Start the repository. or Cause: Internal error. Action: Contact Informatica Technical Support. LM_36528 <Task instance name and path>: Failed to expand E-mail user name <user name> for this session instance. Cause: Internal error. Action: Contact Informatica Technical Support. 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. Cause: You selected the On Failure Email option for the session, but the email address for the post-session email is missing. Action: Enter an email address in the Email User Name field for the post-session Email task. LM_36530 <Task instance name and path>: Failed to send post session failure e-mail for this session instance. Cause: You selected the On Failure Email option for the session, but the Integration Service failed to send the post-session email. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client. Action: Verify you specify an email profile on the machine hosting the Integration Service, and that the machine has the correct email client. LM Messages 297
- 314. LM_36538 <Session instance path>: Unable to write to temporary parameter file [parameter file name] with error [error number] [cause of error]. Cause: You ran a workflow on a server grid. The master server distributed a session that uses a parameter file to a worker server. The worker server needs to create a temporary parameter file in its $PMTempDir directory using parameter file information received from the master server. However, the worker server failed to create the temporary parameter file because it does not have permission to write to $PMTempDir, or because the directory contains a file with the same name. Action: Verify the worker server has the correct permissions to access $PMTempDir and run the workflow again. Or, if $PMTempDir contains a file with the same name as the temporary parameter file, delete it and run the workflow again. LM_36539 <Session instance path>: Unable to unlink temporary parameter file [parameter file name] with error [error number] [cause of error]. Cause: You ran a workflow on a server grid. The master server distributed the session to a worker server. The worker server created a temporary parameter file in $PMTempDir, but it failed to delete the file. Action: Verify the worker server has the correct permissions to access $PMTempDir and verify there is enough disk space. Or, you can manually delete the temporary parameter file from the $PMTempDir directory. LM_36543 <Task name> condition expression eval error < expression >. Cause: The expression you entered may have invalid characters or cannot be evaluated. Action: Verify that the expression is valid in the Workflow Manager. LM_36544 <Task name>: condition expression <expression> will not evaluate to a numeric value. Cause: You may have entered the wrong datatype in the expression. Action: Review the expression in the Workflow Manager to ensure that it uses Numeric datatypes. LM_36564 <Task name>: Invalid datatype conversion for variable [name], expression datatype [datatype], variable datatype [datatype]. Cause: In the Workflow Manager, you assigned a value to a variable using the Assignment task. The Integration Service cannot convert the datatype of the expression to the datatype of the variable. Action: Either fix the expression in the Assignment task or change the datatype of the variable. LM_36565 <Task name>: Variable [name]: data conversion exception <value>. Cause: Internal error. 298 Chapter 41: LM Messages
- 315. Action: Contact Informatica Technical Support. LM_36566 <Task name>: Unable to resolve the left-hand side variable [name] as a user- defined workflow/worklet variable. Cause: In the Workflow Manager, you assigned a value to a variable using the Assignment task. The Integration Service does not recognize the variable as a user-defined workflow or worklet variable. Action: Check the variable declaration in the Assignment task and make sure it matches the name of a user-defined workflow or worklet variable. LM_36567 Unable to rollback the assignment for variable <name>. Cause: Internal error. An error occurred during the assignment of a variable. The Integration Service updated the value of the variable and could not rollback the change. Action: Contact Informatica Technical Support. LM_36580 <Task instance name and path>. Email Username not specified. Cause: The email address for the Email task is missing. Action: Enter a valid email address in the Email User Name field for the Email task. LM_36581 <Task instance name and path>. Failed to send email. Cause: The Integration Service failed to send the email specified in the Email task. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client. Action: Verify you specify an email profile on the machine hosting the Integration Service, and that the machine has the correct email client. LM_36601 <Timer name> Unable to schedule timer with the timer task manager. Cause: The time specified is invalid. The range must be between 00:00:00 January 1, 1970 UTC, and 3:14:07 January 19, 2038 UTC. Action: Specify a time within the valid range. LM_36602 <Variable name> Wait for absolute time specified by variable <variable type>. The variable does not exist. Cause: The variable is not specified in the workflow. Action: Specify the variable in the workflow properties. LM_36603 <Variable name> Wait for absolute time specified by variable <variable type>. The variable is not of type date/time. Cause: The variable type entered was not the Date/Time datatype. Action: Change the datatype to Date/Time. LM Messages 299
- 316. LM_36604 <Variable name> Wait for absolute time specified by variable <variable type>. The variable value is null. Cause: The value of the variable was null. Action: Specify a value that is not 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>]. Cause: An Event-Wait task was configured to delete the file watch indicator file when the Integration Service detected the file. The Integration Service detected the file but failed to delete it. Action: Verify the user has permission to delete the file. LM_36823 Workflow <workflow ID> <session> not unscheduled because it is not scheduled. Cause: You tried to remove from schedule a workflow that you have not yet scheduled. Action: Verify that you selected the correct workflow to remove from schedule. LM_36824 <Workflow name>: Scheduled workflow was not rescheduled because the schedule changed after the Integration Service last ran. Cause: The schedule changed during failover. Action: Reschedule the workflow. LM_44122 Errors encountered in initializing storage in directory <directory name>. See previous error message in log for information. LM_44124 Integration Service is missing workflow manager storage. Cause: Internal Error. The Integration Service could not find the state of operations. Action: Contact Informatica Technical Support. LM_44125 Workflow manager storage is not ready for Integration Service. Cause: Internal Error. The Integration Service is missing the storage file that it uses to write information about services running during failover. Action: Contact Informatica Technical Support. LM_44127 Failed to prepare the task [name]. Cause: The Integration Service was unable to prepare the task due to an internal error. Action: Contact Informatica Technical Support. 300 Chapter 41: LM Messages
- 317. LM_44136 Failed to release remaining execution locks as failover. Cause: A network or database issue prevented locks from being released. Resilience mechanisms could not recover from a connection problem between the Integration Service and the Repository Service or between the Repository Service and the repository database. Action: Verify that the Integration Service and Repository Service are running and that Repository Service can connect to the repository database. LM_44180 The number of asynchronous threads for repository connections specified <number of threads> is too low, using default of <number of threads>. Cause: By default, the Integration Service creates one asynchronous thread for every 10 repository connections. The number of threads specified by the LMRepoConnAsyncThreads custom Integration Service property is less than 10. The specified number of threads is not sufficient for the number of repository connections. Action: To use the default number of threads, remove the LMRepoConnAsyncThreads custom Integration property. Alternatively, you can increase the LMRepoConnAsyncThreads value. LM_44183 Scheduling workflow is not allowed because the Integration Service is running in safe mode. Cause: The Integration Service assigned to the workflow is running in safe mode. You cannot schedule workflows when the Integration Service runs in safe mode. Action: If you have the Admin Integration Service privilege, manually start the workflow. You can also change the operating mode for the Integration Service to normal. LM_44184 Scheduled workflow {<workflow name>} was not rescheduled because the Integration Service is running in safe mode. Cause: The workflow runs on a schedule. However, the Integration Service does not run scheduled workflows in safe mode. Action: If you have the Admin Integration Service privilege, manually start the workflow. You can also change the operating mode for the Integration Service to normal.When you change the operating mode to normal, all scheduled workflows will begin running. LM_44185 User [<repository user name>] does not have sufficient privilege to log on while the Integration Service is running in safe mode. Cause: You must have the Admin Integration Service repository privilege to connect to an Integration Service running in safe mode. Action: Use a repository user account that has the Admin Integration Service privilege to connect to the Integration Service. LM Messages 301
- 318. LM_44188 <Task name>: Failed to expand email user <name> for this email task. Cause: The Integration Service cannot expand a parameter or variable in the email user name. Action: Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file. or Cause: The Integration Service cannot expand the parameter or variable in the email user name due to an internal error. Action: Contact Informatica Technical Support. LM_44189 <Workflow name>: Failed to expand email user <name> for this suspension email. Cause: The Integration Service cannot expand a parameter or variable in the email user name. Action: Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file. or Cause: The Integration Service cannot expand the parameter or variable in the email user name due to an internal error. Action: Contact Informatica Technical Support. LM_44190 <Command task name>: Failed to expand command <command name>, with command value <command text>. Cause: The Integration Service cannot expand a parameter or variable in the command text. Action: Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file. or Cause: The Integration Service cannot expand a parameter or variable in the command text due to an internal error. Action: Contact Informatica Technical Support. 302 Chapter 41: LM Messages
- 319. LM_44193 Integration Service <Integration Service process name> will not perform workflow and schedule failover or recovery when running in safe mode. Cause: The workflow is assigned to an Integration Service running in safe mode. The Integration Service will perform workflow and schedule failover and workflow recovery when you change the Integration Service operating mode to normal. Action: Change the Integration Service operating mode to normal. LM Messages 303
- 320. 304 Chapter 41: LM Messages
- 321. Chapter 42 LMTGT Messages This chapter includes the following topic: โฆ LMTGT Messages, 306 Error messages listed numerically. 305
- 322. LMTGT Messages LMTGT_17801 Error initializing LM-API. Cause: The LMAPI target could not initialize the PowerCenter LMAPI service because the Integration Service is not running. Action: Verify that the Integration Service is running. Also verify that the LMAPITarget application connection is configured correctly. LMTGT_17802 All relational targets must share the same relational database connection. Cause: The relational targets in the mapping do not use the same relational database connection. Action: Edit the session properties so that each relational target uses the same relational connection. LMTGT_17803 Cannot create the relational database connection. Cause: There is not enough memory on the node where the Integration Service process runs to create the database connection objects the Integration Service uses to connect to the relational database. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. LMTGT_17804 Cannot connect to database. Cause: The Integration Service could not connect to a relational database. The relational database connection used for all relational targets in the mapping contains inaccurate information for the connection parameters. Action: Verify that the relational database connection is configured correctly. LMTGT_17805 Cannot connect to Integration Service. Cause: The LMAPI target could not connect to the Integration Service. Action: Verify that the Integration Service is running. Also verify that the LMAPITarget application connection is configured correctly. LMTGT_17806 Cannot log in to Integration Service. Cause: The LMAPI target could not log in to the Integration Service after connecting to the service. Action: Verify that the LMAPITarget application connection contains correct information for the Domain Name and Integration Service Name fields. LMTGT_17808 Key field must be connected. Cause: The UKey port in the LMAPI target is not connected. 306 Chapter 42: LMTGT Messages
- 323. Action: Connect the UKey port in the mapping. The LMAPI target starts the workflows scheduled in the Scheduling Information tab based on the data it receives from this port. LMTGT_17809 Identifier port is not connected in the mapping. The port must be connected when using the Wait for Commit option. Cause: The Identifier port in the LMAPI target is not connected. However, the Wait for Commit option is selected in the session properties. Action: Connect the Identifier port in the mapping when you select Wait for Commit in the session properties. LMTGT_17810 Could not find workflow details for key <key name>. Cause: The LMAPI target received data for a key which does not exist on the Scheduling Information tab of the LMAPI target properties. Action: Enter a key in the Scheduling Information tab for each value that the LMAPI target will receive in the UKey port. LMTGT_17811 Indicator Table <table name> not found in the mapping. Cause: The mapping containing the LMAPI target does not include the indicator table. However, an indicator table name is specified on the Scheduling Information tab of the LMAPI target properties. Action: Verify that the table entered for the Indicator Table field exists in the mapping. The table must contain the fields UKey, Identifier, and Status. LMTGT_17812 Indicator Table name is not specified in the mapping. Indicator Table name is required when using the Wait for Commit option. Cause: The Indicator Table field on the Scheduling Information tab of the LMAPI target properties does not contain a value. However, the Wait for Commit option is selected in the session properties. Action: Enter the name of the indicator table in the Indicator Table field when you select Wait for Commit in the session properties. LMTGT_17818 The Integration Service cannot fetch workflow <workflow name> for key <key name>. Cause: The Integration Service cannot start the workflow because it does not exist or because it does not have a unique name in the repository. Action: Verify that all workflows scheduled in the LMAPI target exist in the repository and have unique names in the repository. LMTGT_17820 Warning: Lost server connection. Cause: The LMAPI target lost its connection to the Integration Service. Action: Verify that the Integration Service is running. LMTGT Messages 307
- 324. LMTGT_17821 Error communicating with Integration Service. Cause: The LMAPI target failed to communicate with the Integration Service. Action: Verify that the Integration Service is running. 308 Chapter 42: LMTGT Messages
- 325. Chapter 43 MQ Messages This chapter includes the following topic: โฆ MQ Messages, 310 Error messages listed numerically. 309
- 326. MQ Messages MQ_29000 Cannot connect to queue manager <queue manager> reason <reason> <reason message>. Cause: The queue manager name is inaccurate. Action: Check the queue manager name. or Cause: You might not have proper permission to connect to the queue manager. Action: Verify your privileges to connect to the queue manager. MQ_29001 Cannot open queue <queue> reason <reason> <reason message>. Cause: The queue name is inaccurate. Action: Check the queue name. or Cause: You might not have proper permission to connect to the queue. Action: Verify your privileges to connect to the queue. MQ_29002 Error closing queue <queue> reason <reason> <reason message>. Cause: The Integration Service could not close the message queue due to the reason code stated in the message. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29003 Error disconnecting from queue manager <queue manager> reason <reason> <reason message>. Cause: The Integration Service could not disconnect from the queue manager due to the reason code stated in the message. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29004 Filter parse error: <parse error message>. Cause: The filter condition in the MQ Source Qualifier is invalid. Action: Correct the error stated in the parse error message. MQ_29005 Error getting message from queue <queue>:<queue manager> reason <reason> <reason message>. Cause: The Integration Service failed to get a message from the queue due to the reason code stated in the message. 310 Chapter 43: MQ Messages
- 327. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29006 Message data truncated reading from queue <queue>:<queue manager> reason <reason> <reason message>. Cause: The message size is too large for the Integration Service to read. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29007 No message under cursor while attempting to remove message from queue <queue>:<queue manager> reason <reason> <reason message>. Cause: You might not have the permission to remove the message from the queue. or Cause: The message was removed by another process. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29008 Error putting message on queue <queue>:<queue manager> reason <reason> <reason message>. Cause: The Integration Service could not put message on the queue due to reason code stated in message. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29009 Invalid RowsPerMesage value for queue <queue>:<queue manager> (<rows per message> > 0). Cause: The Rows Per Message parameter in the session properties is incorrect. Action: Specify a value greater than 0 for the Rows Per Message in the session properties. MQ_29010 Error opening cache <cache file> for reading: <operating system error>. Cause: You might not have permission to read from the cache file. or Cause: The $PMCacheDir variable is incorrect. Action: Fix the operating system error stated in the message. MQ_29011 Error opening cache <cache file> for writing: <operating system error>. Cause: You might not have permission to write to the cache file. or Cause: The hard disk is full. MQ Messages 311
- 328. or Cause: The $PMCacheDir variable is incorrect. Action: Fix the operating system error stated in the message. Look in the directory $PMCacheDir. MQ_29012 Error attempting to load MQ driver. Cause: PowerCenter could not load the MQ driver shared library because the file does not exist. Action: Verify the search path for the MQ driver shared library. Depending on your platform, look for the driver file in the appropriate location: โ Windows - pmmqdrvc.dll โ Solaris - libpmmqdrvc.so โ Linux - libpmmqdrvc.so โ AIX - libpmmqdrvc.a โ HP - libpmmqdrvc.sl or Cause: PowerCenter could not load the MQ driver shared library due to insufficient permissions. Action: Make sure the permissions for the MQ driver file are correct. MQ_29013 Delete operation for this target not enabled. Queue connection is <queue>:<queue manager>. Cause: The MQSeries target received a row with the delete flag set to TRUE. However, the Integration Service does not have delete permission for the queue. Action: Enable delete permission for the Integration Service on the target queue. MQ_29014 MsgId field has not been set. Queue connection is <queue>:<queue manager>. Cause: There may be no port projected to the MsgId column in the dynamic MQSeries target. The Integration Service cannot delete messages from the queue. Action: Project a port to the MsgId column of the dynamic MQSeries target. MQ_29100 Line <line>, column <column>: Unknown character '<character>' in filter. Cause: A filter condition has a general parsing error. Action: Check the syntax of the expression. MQ_29101 Line <line>, column <column>: Invalid operator. Same as MQ_29100. 312 Chapter 43: MQ Messages
- 329. MQ_29102 Line <line>, column <column>: Unknown identifier <identifier>. Same as MQ_29100. MQ_29103 Line <line>, column <column>: String literal not terminated properly. Same as MQ_29100. MQ_29104 Line <line>, column <column>: Syntax Error. Same as MQ_29100. MQ_29105 Filter Expression does not have a boolean return type. Cause: The filter condition does not return a boolean TRUE/FALSE value. Action: Edit the filter condition to return a boolean TRUE/FALSE value. MQ_29106 Line <line>, column <column>: Left operand must be boolean. Cause: The filter condition does not contain a boolean operand. Action: Check the left-hand side of the logical operator in the filter condition. MQ_29107 Line <line>, column <column>: Right operand must be boolean. Cause: The filter condition does not contain a boolean operand. Action: Check the right-hand side of the logical operator in the filter condition. MQ_29108 Line <line>, column <column>: Incompatible types for relational operator. Cause: The logical operators [=, <>, >=, <=, >, <] in the left-hand and right-hand sub- expression have incompatible datatypes. Action: Edit the filter condition with compatible datatypes for relational operators in the left-hand and right-hand sub-expression. MQ_29109 Line <line>, column <column>: Not enough arguments. <function name> () should have argument(s). Cause: The function in the filter condition does not enough arguments. Action: Apply arguments to the function in the filter condition. MQ_29110 Line <line>, column <column>: Too many arguments. <function name> () should have argument(s). Cause: There are too many arguments in a function. Action: Use fewer arguments in a function. MQ_29111 Line <line>, column <column>: Wrong type in <function name> (). Argument should be CHAR/BYTE. Cause: The function expects an argument in MQCHAR or MQBYTE type. MQ Messages 313
- 330. Action: Make sure argument is of MQCHAR or MQBYTE type in the filter expression. MQ_29112 Line <line>, column <column>: Wrong type in <function name> (). Argument should be BOOLEAN. Cause: The function expects an argument in boolean type. Action: Make sure argument is of boolean type in the filter condition. MQ_29113 Line <line>, column <column>: Wrong type in <function name> (). Argument should be LONG. Cause: The function expects an argument in MQLONG type. Action: Make sure argument is of MQLONG type in the filter condition. MQ_29114 Line <line>, column <column>: String literal not terminated properly. Cause: The string literals must be in double quotes. Action: Use double quotes to enclose string literals in the filter condition. MQ_29115 Line <line>, column <column>: Bad date format in <function name> (), Argument <argument number> should be <correct date format>. Cause: The argument in the function does not contain the correct date format. Action: Use the <correct date format> for the argument in the filter condition. MQ_29200 Projected column metadata fetch failed. Cause: Internal error. Action: Contact Informatica Technical Support. MQ_29201 Cannot retrieve source filter. Cause: Internal error. Action: Contact Informatica Technical Support. MQ_29202 Unable to retrieve cache file name. Cause: Internal error. Action: Contact Informatica Technical Support. MQ_29203 Error opening queue <queue>:<queue manager> because <error message>. Cause: The Integration Service could not open the queue due to the reason code stated in message. You may have selected to install the MQSeries server driver during installation. However, the MQSeries server is not installed on the machine hosting the Integration Service. Action: Reinstall the PowerCenter Connect for IBM MQSeries server. Make sure to select the MQSeries client driver during installation. 314 Chapter 43: MQ Messages
- 331. or Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29204 Error fetching message from queue <queue>:<queue manager> because <error message>. Cause: The Integration Service could not fetch message from the queue due to the error. Action: Correct the error indicated in the error message. MQ_29207 Error closing queue <queue>:<queue manager>: <error message>. Cause: The Integration Service could not close the queue due to the error stated in the message. Action: Correct the error indicated in the error message. MQ_29208 Error putting message on queue <queue>:<queue manager>: <error message>. Cause: The Integration Service could not put the message on the queue due to the error stated in the message. Action: Correct the error indicated in the error message. MQ_29210 Error attempting to get MQ connection information. Cause: Internal error. Action: Contact Informatica Technical Support. MQ_29211 Warning: Some message data was truncated reading from queue <queue>:<queue manager>. Cause: This is only a warning. The MQ reader truncated one or more MESSAGE_DATA columns because the size of the message exceeded the maximum size for the MESSAGE_DATA port in the MQ Source Qualifier. Action: However, you can increase the size of the MESSAGE_DATA column in the MQ Source Qualifier. MQ_29212 Warning: Message with a total length of <length> was truncated to <length>. Cause: This is only a warning. This is a more detailed warning that appears when Tracing is set to โVERBOSE RUN.โ The message number is given as MSGNO. Action: However, you can increase the size of the MESSAGE_DATA column in the MQ Source Qualifier. MQ Messages 315
- 332. MQ_29213 No filter is specified for queue <queue>:<queue manager>. Cause: This is an informational message. It indicates that there is no filter set for reading messages from the queue. Action: None. You can enter a filter condition in the MQ Source Qualifier or in the session properties. MQ_29214 MQ Driver initialization failure <message>. Cause: An error occurred during the initialization of the MQ driver. Action: Check the additional error message for more information. MQ_29218 Filter Condition for MQSeries: StartTime should be prior to EndTime. Cause: This is an informational message. The value for StartTime in the filter condition is equal to or greater than the value entered for EndTime. Action: Make sure the StartTime value is less than the EndTime value. MQ_29221 Partial message written into queue <queue>:<queue manager> due to commit. Cause: This is an informational message. The Integration Service did not commit all rows in a message to the target. This might occur when the Integration Service reaches the end of a commit interval or a short FlushLatency interval. It commits the remaining rows at the next commit interval. Action: None. MQ_29222 Error committing from queue manager <queue manager>: reason <reason> <reason message>. Cause: The Integration Service could not commit messages to the target. The MQSeries system may not contain enough log space. Action: Verify that your MQSeries system contains enough log space. or Action: Check the additional error message for more information. MQ_29223 Error backing out from queue manager <queue manager>: reason <reason> <reason message>. Cause: The Integration Service could not roll back messages from the target. Action: Check the additional error message for more information. MQ_29224 Device failed to commit: <error message>. Cause: The Integration Service could not commit messages to the target. Action: Check the additional error message for more information. 316 Chapter 43: MQ Messages
- 333. MQ_29225 Device failed to back out: <error message>. Cause: The Integration Service could not roll back messages from the target. Action: Check the additional error message for more information. MQ_29226 Device failed to connect to queue manager: <error message>. Cause: The Integration Service could not connect to the queue manager. The session failed to initialize. Action: Check the additional error message for more information. MQ_ 29231 Transactional MQ targets with the same queue manager name cannot be in different TCUs. Cause: The MQSeries targets have the same queue connection but belong to different transaction control units. As a result, the session failed. Action: Make sure that all MQSeries targets with the same queue connection belong to the same transaction control unit. MQ_29234 Write to recovery cached failed. Cause: Recovery cache folder is not available. Action: Check that the recovery cache folder exists and has write permission. or Cause: The target may have insufficient disk space. Action: Verify that enough disk space is available in the target. MQ_29237 Failure occurred while reading messages from the queue in destructive mode. Cause: The IBM MQSeries installation may not allow deleting messages from the queue. Action: Look up the reason code in the IBM MQSeries documentation for instructions to correct the error. MQ_29238 Invalid recovery cache folder specified. Cause: The recovery cache folder is invalid. Action: From the properties settings on the Mapping tab (Sources node) in the session properties, specify a valid recovery cache folder. MQ_29239 Reader partition <partition name> failed to close checkpoint at real-time flush: <additional error message>. Cause: There may be insufficient disk space when the Integration Service commits messages to the target after the Real-time Flush Latency period expires. Action: Verify that enough disk space is available in the target. MQ Messages 317
- 334. MQ_29240 Cache folder specified for reader partition <partition name> is invalid. Cause: The operating system cannot find the recovery cache folder. Action: Verify the recovery cache folder specified in the session properties exists. MQ_29241 Reader partition <partition name> failed to register recovery. Cause: The operating system may be low on memory. Action: Verify the system has sufficient memory. MQ_29242 Consumer handle failed to initialize. Cause: The name of the recovery cache folder may be incorrect. Action: Verify the recovery cache folder name specified in the session properties. or Action: Contact the system administrator. MQ_29243 Reader partition failed to read cached message. Cause: The recovery cache file may be deleted. Action: Verify that the cache file and directory exist. Specify the correct path to the cache file directory in the properties settings on the Mapping tab (Sources node) in the session properties. MQ_29244 Reader partition <partition name> failed doing GMD flush: <additional error message>. Cause: The recovery cache folder may have insufficient memory. Action: Verify the recovery cache folder has sufficient memory for large files. or Cause: The recovery cache folder may not have write permission. Action: Verify the recovery cache folder has write permission. MQ_29245 You cannot specify both Destructive Read and RemoveMsg(TRUE). Cause: You selected the Destructive Read option and specified the RemoveMsg(TRUE) function as a filter condition. Action: You must set the RemoveMsg(TRUE) function to RemoveMsg(FALSE) in the filter condition or remove the function from the filter condition. MQ_29246 The mapping contains an associated source qualifer. Cause: You specify the Destructive Read option in a mapping with an associated source qualifier. Action: The Integration Service ignores the Destructive Read option if the mapping contains an associated source qualifier. To remove messages from the source 318 Chapter 43: MQ Messages
- 335. queue for mappings that contain an associated source qualifier, use the RemoveMsg(TRUE) function. MQ_29248 MQ queue manager [<queue manager>] encountered a transient connection failure. Cause: The Integration Service could not connect to the MQ queue manager. The network or the MQ server may be down. The Integration Service will attempt to connect to the MQ queue during the retry connection period. If it does not connect to the MQ queue during the retry connection period the session fails. Action: Verify the MQ queue manager is running. Or, verify that the network is active. MQ_29250 Connection retry period expired. The Integration Service could not connect to MQ queue manager [<queue manager>]. Cause: The Integration Service could not connect to the MQ queue manager during the retry connection period. The network or the MQ server may be down. As a result, the session failed. Action: Verify the MQ queue manager is running. Or, verify that the network is active. Restart the session. MQ_29251 Resilience is disabled, because Destructive Read and recovery are not configured. Cause: The Integration Service could not make multiple connection attempts to the MQ queue manager, because Destructive Read and recovery are not configured for the session. Action: In the session properties, configure Destructive Read and recovery. MQ_29255 The Integration Service truncated message data while reading from queue <queue>:<queue manager> in destructive read mode. Cause: The Integration Service read an MQSeries message that exceeded the precision of the MESSAGE_DATA column in the MQSeries source definition. As a result, the Integration Service truncated the data. Because the session is running in destructive read mode, the session failed and the Integration Service did not delete the message from the source queue. Action: Increase the precision of the MESSAGE_DATA column in the MQSeries source definition. MQ Messages 319
- 336. 320 Chapter 43: MQ Messages
- 337. Chapter 44 MXR Messages This chapter includes the following topic: โฆ MXR Messages, 322 Error messages listed numerically. 321
- 338. MXR Messages Information forthcoming. 322 Chapter 44: MXR Messages
- 339. Chapter 45 NODE Messages This chapter includes the following topic: โฆ NODE Messages, 324 Error messages listed numerically. 323
- 340. NODE Messages NODE_10014 [Resource type] resource [resource name] not found in node configuration. Cause: The EnableNodeResource or DisableNodeResource command was used to enable or disable a resource on a node. infacmd could not find a resource with the name and type shown on the node. Action: Verify the following conditions: โ The resource shown exists on the node. โ The resource is of the type shown. โ The resource name was entered correctly. 324 Chapter 45: NODE Messages
- 341. Chapter 46 NTSERV Messages This chapter includes the following topic: โฆ NTSERV Messages, 326 Error messages listed numerically. 325
- 342. NTSERV Messages NTSERV_10000 Cannot close service main thread handle. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10001 Cannot suspend service main thread. Cause: Internal error. You attempted to pause the service for the Integration Service on Windows. Action: Try the operation again. If it fails, contact your system administrator. NTSERV_10003 Cannot resume service main thread. Cause: Operating system error. You attempted to resume the service for the Integration Service on Windows. Action: Try the operation again. If it fails, contact your system administrator. NTSERV_10005 Cannot set service status. Cause: Operating system error. Action: See the previous error message and contact your system administrator. NTSERV_10007 Cannot duplicate service main thread handle. Same as NTSERV_10000. NTSERV_10009 Cannot start service control dispatcher. Same as NTSERV_10000. NTSERV_10011 Cannot register service handler procedure. Same as NTSERV_10000. NTSERV_10013 Cannot open Service control manager. Access Denied. Cause: Operating system error. You attempted to configure or start a service but do not have the right permissions. Action: Contact your system administrator to gain privileges to configure or start a service. NTSERV_10024 Cannot flush registry key. Cause: The Integration Service failed to read a value from the registry. You may not have the privileges to access that portion of the registry. Action: Contact your system administrator to gain privileges access to the registry. If that does not resolve the problem, contact Informatica Technical Support. 326 Chapter 46: NTSERV Messages
- 343. NTSERV_10025 Cannot close registry key. Same as NTSERV_10024. NTSERV_10026 Cannot initialize security descriptor. Same as NTSERV_10024. NTSERV_10027 Cannot set security descriptor DACL. Same as NTSERV_10024. NTSERV_10028 Cannot create registry key. Same as NTSERV_10024. NTSERV_10029 Cannot set registry value. Same as NTSERV_10024. NTSERV_10031 Cannot delete registry key. Cause: The Integration Service failed to read a value from the registry. You may not have the privileges to access that portion of the registry. Action: Contact your system administrator to gain privileges to access the registry. If that does not resolve the problem, contact Informatica Technical Support. NTSERV_10032 Cannot allocate memory. Cause: Operating system error. You might be low on resources. Action: Contact your system administrator. NTSERV_10033 Cannot open registry key. Same as NTSERV_10024. NTSERV_10042 Cannot create mutex. Same as NTSERV_10032. NTSERV_10043 Cannot close mutex. Same as NTSERV_10032. NTSERV_10044 Cannot create thread. Same as NTSERV_10032. NTSERV_10045 Wait for main service thread failed. Same as NTSERV_10032. NTSERV_10046 Wait for status mutex failed. Same as NTSERV_10032. NTSERV Messages 327
- 344. NTSERV_10047 Cannot create thread to stop service. Same as NTSERV_10032. NTSERV_10065 Cannot get local computer name. Cause: Operating system error. The machine hosting the Integration Service might be low on resources. Action: Contact your system administrator, or free system resources. NTSERV_10066 Cannot get user information. Same as NTSERV_10065. NTSERV_10067 Cannot add PowerMart user. Same as NTSERV_10065. NTSERV_10068 Cannot look up account name. Same as NTSERV_10065. NTSERV_10069 Cannot administer user rights policy. Same as NTSERV_10065. NTSERV_10070 Cannot grant user right. Same as NTSERV_10065. NTSERV_10071 Cannot convert multibyte to wide char. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV_10072 Cannot convert wide char to multibyte. Same as NTSERV_10071. NTSERV_10073 Cannot delete PowerMart user. Same as NTSERV_10071. NTSERV_10080 Cannot read configuration file. Cause: The Integration Service could not locate or read a configuration file. Action: Contact Informatica Technical Support. NTSERV_10081 Cannot get registry value. Cause: Internal error. Action: Contact Informatica Technical Support. 328 Chapter 46: NTSERV Messages
- 345. NTSERV_10085 Key not specified. Same as NTSERV_10081. NTSERV_10086 Invalid registry value type. Same as NTSERV_10081. NTSERV_10087 Cannot enumerate registry subkeys. Same as NTSERV_10081. NTSERV_10088 Unexpected line in configuration file. Cause: An install file contains an invalid line. Action: Contact Informatica Technical Support. NTSERV_10089 Bad usage. Consult your documentation to get correct usage. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV_10091 Install failed. Cause: The Informatica installation failed. Action: Check the .mif file in the Windows directory for related error messages. NTSERV_10092 Update failed. Same as NTSERV_10091. NTSERV_10093 Deinstall failed. Cause: Windows failed to install the Integration Service. Action: Contact Informatica Technical Support. NTSERV_10096 Cannot get registry key. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV_10097 Cannot initialize message resource DLL. Cause: The pmmsg.dll file is missing or the registry key is pointing to the wrong location. Action: Contact Informatica Technical Support. NTSERV_10098 Invalid drive specification. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV Messages 329
- 346. NTSERV_10099 Cannot load configuration from registry. Same as NTSERV_10098. NTSERV_10100 Wait for exit of child process failed. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10101 Cannot find process control block. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10102 Cannot create thread to wait for child exit event. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10103 Cannot create thread to wait for kill event. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10105 Cannot create process. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10106 Cannot resume thread. Cause: Operating system error. Action: Contact your system administrator. NTSERV_10129 No event log configuration specified. Cause: A configuration file does not contain a valid event log configuration. Action: Contact Informatica Technical Support. NTSERV_10132 Registry records invalid software version. Cause: Error in the Informatica registry services. Action: Contact Informatica Technical Support. NTSERV_10133 Unknown host in TCP/IP Host Address parameter. Cause: In the Integration Service Setup, the TCP/IP host address cannot be found. Action: Enter a valid TCP/IP host address in the Integration Service Setup. 330 Chapter 46: NTSERV Messages
- 347. NTSERV_10139 Unknown error converting to COM data type. Cause: You attempted to convert data and the conversion failed. This might be due to data overflow. Action: Determine which data caused the error and then correct that data. NTSERV_10141 Error invoking COM external procedure... Cause: You specified a COM object that is invalid or does not exist. Action: Verify that you spelled the COM object correctly and verify that it is not corrupt or invalid. NTSERV_10143 Error looking up hostname... Cause: In the Integration Service Setup, the host listed in the TCP/IP Host Address field is incorrect. Action: Enter a valid TCP/IP host address in the Administration Console. NTSERV_10144 Root of key is invalid. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV_10145 Cannot revoke user right. Cause: Internal error. Action: Contact Informatica Technical Support. NTSERV_10146 Attachment file <file name> not found. Cause: You configured a session to send a post-session email with an attached file. The Integration Service on Windows could not locate the specified attached file. Action: Verify the directory and file name for the attachment file are entered correctly in the session properties. Verify the file exists in the specified directory. NTSERV_10147 Permissions do not allow read access of attachment <file name>. Cause: You configured a session to send a post-session email with an attached file. The Integration Service on Windows could not access the specified file. Action: Verify that you have privileges to read the file. NTSERV_10148 Attachment file <file name> is not a regular file. Cause: You configured a session to send a post-session email with an attached file. The attachment file you have specified is not a regular Windows file. It might be a directory name, a service name, or a device name. Action: Specify a regular attachment file in the session for post-session email. NTSERV Messages 331
- 348. NTSERV_10246 ERROR in attaching file. Cause: You configured a session to send a post-session email with an attached file. Action: Check preceding error messages to see the cause for the error. 332 Chapter 46: NTSERV Messages
- 349. Chapter 47 OBJM Messages This chapter includes the following topic: โฆ OBJM Messages, 334 Error messages listed numerically. 333
- 350. OBJM Messages OBJM_54505 The object for which rbrowser information was requested does not exist. Cause: The Repository Agent process could not retrieve object properties from the repository because the object does not exist. Action: The object may be deleted. Refresh the Navigator windows. Check for other error messages in the Repository Service log. OBJM_54509 Rbrowser fetch: Unable to get children info. Maybe the childType is invalid. (childType = <type>) Cause: Internal error. Action: Contact Informatica Technical Support. OBJM_54510 Internal Error: Unlocking a summary tree node failed. Cause: Internal error. Action: Contact Informatica Technical Support. OBJM_54513 Internal: Do not have proper parent lock to access the summary tree node. Cause: Internal error. Action: Contact Informatica Technical Support. OBJM_54515 Incorrect summary tree locking order. Cause: Internal error. Action: Contact Informatica Technical Support. OBJM_54538 Unable to connect to the repository <repository name> on database <database name>. Cause: The Repository Agent process could not connect to the repository. Action: Verify that the repository database is running. Check preceding error messages to see the cause of the error. OBJM_54543 Database error: <database error message>. Cause: Database error. Action: Check the session log for related messages. Also, contact your database administrator. OBJM_54544 Internal Repository Service error: error number <error number>. Cause: Internal error. Action: Contact Informatica Technical Support. 334 Chapter 47: OBJM Messages
- 351. OBJM_54545 Received fetch request with invalid rbrowser node ID <ID>. Cause: Internal error. Action: Contact Informatica Technical Support. OBJM Messages 335
- 352. 336 Chapter 47: OBJM Messages
- 353. Chapter 48 ODL Messages This chapter includes the following topic: โฆ ODL Messages, 338 Error messages listed numerically. 337
- 354. ODL Messages ODL_26001 Informatica Outer Join syntax not found. Cause: You entered braces ( { } ) in a Source Qualifier join override or extract override without using Informatica join syntax within the braces. Action: Either remove the braces and use database-specific join syntax or use Informatica join syntax within the braces. ODL_26002 Informatica Outer Join syntax error. Cause: The Integration Service found an error in the outer join syntax in the Source Qualifier transformation. Action: Correct the error before running the session again. Look for related messages in the session log. ODL_26003 No OUTER keyword found after LEFT keyword. Cause: You omitted the OUTER keyword from the join syntax for a left outer join. Action: Correct the join syntax in the Source Qualifier. To create a left outer join, use the keywords LEFT OUTER JOIN. ODL_26004 No JOIN keyword found after OUTER keyword. Cause: You omitted the JOIN keyword from the syntax for an outer join. Action: Correct the join syntax in the Source Qualifier. ODL_26005 No OUTER keyword found after RIGHT keyword. Cause: You omitted the OUTER keyword from the join syntax for a right outer join. Action: Correct the join syntax in the Source Qualifier. To create a right outer join, use the keywords RIGHT OUTER JOIN. ODL_26006 No JOIN keyword found after INNER keyword. Cause: You omitted the JOIN keyword from the syntax for an inner join. Action: Correct the join syntax in the Source Qualifier. To create an inner join, use the keywords INNER JOIN. ODL_26007 No LEFT or RIGHT keyword found before OUTER keyword. Cause: You omitted the LEFT or RIGHT keyword from the join syntax for an outer join. Action: Correct the join syntax in the Source Qualifier. To create a left outer join, use the keywords LEFT OUTER JOIN. To create a right outer join, use the keywords RIGHT OUTER JOIN. 338 Chapter 48: ODL Messages
- 355. ODL_26008 More than one RIGHT OUTER JOINs are not supported. Cause: You combined two right outer joins in the same join syntax. Use only one right outer join in a single Source Qualifier. Action: Correct the join syntax in the Source Qualifier. If appropriate, change the right outer joins to left outer joins. You can use multiple left outer joins in a single Source Qualifier. ODL_26009 No comma (,) found between table names. Cause: You omitted a comma between table names in the FROM clause of the outer join syntax. Action: Correct the join syntax in the Source Qualifier. Place commas between table names in the FROM clause. ODL_26012 Internal error in function <function name>. Database not in correct state. Cause: Internal error. Action: Contact Informatica Technical Support. ODL_26023 Deadlock error encountered. Cause: The database has deadlocked. Action: Contact your database administrator. ODL_26025 Error getting sort order from the database. Cause: Internal error. Action: Contact Informatica Technical Support. ODL_26026 Driver does not support the data type. Cause: You selected an unsupported datatype for the database. Action: Select a datatype that is supported by the database. ODL_26028 File <file name> is either missing or corrupt. Cause: Internal error. Action: Contact Informatica Technical Support. ODL_26035 ODBC call to SQLError failed. Cause: Internal error. Action: Contact Informatica Technical Support. ODL_26036 ODBC call <ODBC call> failed. Cause: Internal error. Action: Contact Informatica Technical Support. ODL Messages 339
- 356. ODL_26045 Error allocating DB2 environment handle. Cause: DB2 database error. Action: Verify the DB2 environment is configured correctly. Also, contact your database administrator. ODL_26046 Error loading bulk API library. Cause: DB2 database error. Action: Verify the DB2 environment is configured correctly. Also, contact your database administrator. ODL_26047 Could not allocate a bulk API instance. Cause: DB2 database error. Action: Verify the DB2 environment is configured correctly. Also, contact your database administrator. ODL_26060 Fatal Error: Encountered Teradata error that aborts current transaction. Cause: The Integration Service encountered one of the following Teradata errors that aborted the current transaction: โ 2801 Duplicate unique prime key error. โ 2802 Duplicate row error. โ 2803 Secondary index uniqueness violation. โ 3604 Cannot place a null value in a NOT NULL field. Action: Remove the row that caused the Teradata error and restart the session. ODL_26069 Failed to create and initialize SQL OLE DB instance. Reason <error code>: <system error>. Cause: The Repository Service or Integration Service failed to connect to the Microsoft SQL Server database because one or more Microsoft SQL Server API function calls failed. Action: Verify that all specified Microsoft SQL Server classes are properly registered in the registry. Then re-register oledb32.dll. [Regsvr32 Program FilesCommon FilesSystemOle DBoledb32.dll]. Use the returned error code and error message to determine the cause of this error. ODL_26071 Graphic/vargraphic partition key types are supported only on servers with UNICODE data movement enabled. Cause: You ran a session using database partitioning on an Integration Service running in ASCII mode and the IBM DB2 target table uses a partitioning key with either a Graphic or Vargraphic column. Action: Run the session on an Integration Service in Unicode mode. 340 Chapter 48: ODL Messages
- 357. ODL_26095 BigInt partition key type can be used only in high-precision mode. Cause: You configured a DB2 session with Bigint columns for database partitioning, but you did not configure the session for high precision mode. Action: Specify high precision mode when you configure a DB2 session with Bigint columns for database partitioning. ODL_26111 High availability license is absent. Resilience timeout specified for database connection <connection name> is ignored. Cause: The connection retry period is configured in the database connection object, but you do not have the high availability option. The retry period is ignored. Action: None. ODL Messages 341
- 358. 342 Chapter 48: ODL Messages
- 359. Chapter 49 OPT Messages This chapter includes the following topic: โฆ OPT Messages, 344 Error messages listed numerically. 343
- 360. OPT Messages OPT_63005 ERROR: Pushdown optimization failed for the session <transformation name>. Cause: Internal error. Action: Contact Informatica Technical Support. OPT_63007 ERROR: Failed to expand configuration parameter [$$PushdownConfig]. Cause: The Integration Service could not expand the $$PushdownConfig configuration parameter because it could not locate the parameter file or could not locate the specified parameter within the parameter file. Action: Verify that the parameter file contains the correct path, and a value for the $$PushdownConfig parameter is specified within the file. OPT_63008 ERROR: Configuration parameter [$$PushdownConfig] contains an invalid value. Cause: The Integration Service could not expand the $$PushdownConfig configuration parameter because the parameter files specifies an invalid value for the $$PushdownConfig parameter. Action: Verify that the parameter file specifies a valid value for the $$PushdownConfig configuration parameter. OPT_63014 Pushdown optimization to source stops at the transformation <transformation name> because the mapping contains too many pipeline branches. Cause: The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 four-way branches. The Integration Service cannot generate SQL to push all the branches of the mapping to the database. Action: None. OPT_63015 Pushdown optimization to target stops at the transformation <transformation name> because the mapping contains too many pipeline branches. Cause: The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 four-way branches. The Integration Service cannot generate SQL to push all the branches of the mapping to the database. Action: None. OPT_63021 Pushdown optimization stops at the transformation <transformation name> because it is connected to multiple targets. Cause: You attempted to push a transformation to multiple targets for target-side partial pushdown optimization. The Integration Service cannot generate the SQL to push the transformation to both targets. 344 Chapter 49: OPT Messages
- 361. Action: None. OPT_63022 Pushdown optimization stops at the transformation <transformation name> because no port depends on values from the upstream transformation <transformation name>. Cause: You created an expression that does not use upstream output port values. The Integration Service cannot generate an SQL statement for an expression that does not use output ports from upstream transformations because it cannot determine the values to use. Action: None. OPT_63070 Pushdown optimization to the source stops at the transformation <transformation name> because it is a repartition point and the partition type is not hash auto-keys or pass-through. Cause: To push transformation logic for a partitioned transformation to the database, the partition type must be hash auto-keys or pass-through. If the partition type is hash auto-keys, the source must be key-range partitioned, and the key ranges cannot gap or overlap. Action: Change the partition type for the transformation to hash auto-keys or pass- through. OPT_63072 Pushdown optimization to the source stops at the repartition point <transformation name> because the source is not key-range partitioned. Cause: The transformation uses a hash auto-keys partition, and the source is not key- range partitioned. When the partition is hash auto-keys, you must also configure the source for key-range partitioning. Action: Configure the source for key-range partitioning. OPT_63076 Pushdown optimization to the source stops at the repartition point <transformation name> because the source has a partition with an end key- range different from the start key range of the next partition. Cause: You configured the source for key range partitioning, but you did not ensure that the end key range for a partition matches the start range for the next partition. The end key range for each partition must equal the start range for the next partition, and it cannot overlap with the next partition. Action: Modify the start or end key-range to ensure that the end key range for the partition equals the start range for the next partition. OPT_63077 Pushdown optimization to the source stops at the repartition point <transformation name> because the source contains a user-defined filter on a per-partition basis. Cause: You added a user-defined distinct filter condition at the Source Qualifier transformation. Two or more partitions use a different filter condition. The OPT Messages 345
- 362. Integration Service cannot push transformation logic to the source when you use a distinct user-defined filter. Action: None. OPT_63078 Pushdown optimization to the source stops at the repartition point <transformation name> because an upstream Aggregator transformation is not properly partitioned on the aggregate key. Cause: You configured a group by port for the upstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match. Action: Configure the group by port and partition key to match. OPT_63079 Pushdown optimization to the source stops at the repartition point <transformation name> because an upstream Sorter transformation is not properly partitioned on the distinct sort key. Cause: You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match. Action: Configure the sort key and partition key to match. OPT_63080 Pushdown optimization to the source stops at the repartition point <transformation name> because an upstream Joiner transformation is not properly partitioned on the join key. Cause: You configured a join condition for the upstream Joiner transformation that is different from the partition key specified for the key-range partition. The join condition and partition key must match. Action: Configure the join condition and the partition key to match. OPT_63081 Pushdown optimization to the source stops at the repartition point <transformation name> because a downstream Aggregator transformation is not properly partitioned on the aggregate key. Cause: You configured a group by port for the downstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match. Action: Configure the group by port and partition key to match. OPT_63082 Pushdown optimization to the source stops at the repartition point <transformation name> because a downstream Sorter transformation is not properly partitioned on the distinct sort key. Cause: You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match. Action: Configure the sort key and partition key to match. 346 Chapter 49: OPT Messages
- 363. OPT_63083 Pushdown optimization to the source stops at the repartition point <transformation name> because a downstream Joiner transformation is not properly partitioned on the join key. Cause: You configured a join condition for the upstream Joiner transformation that is different from the partition key specified for the key-range partition. The join condition and partition key must match. Action: Configure the join condition and the key-range partition to match. OPT_63102 Pushdown optimization stops at Source Qualifier transformation <transformation name> because it contains an SQL override, and view creation is not enabled. Cause: You configured a session that contains an SQL override for pushdown optimization, but you did not configure the session to create a view. Action: When you configure the session containing an SQL override for pushdown optimization, ensure that you configure the session to create a view. You configure this setting on the Properties tab of the session properties. OPT_63106 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because SQL override is specified for some but not all partitions. Cause: When you configure a session that contains an SQL override for pushdown optimization, you must configure the SQL override for all partitions in the session. Action: Configure an SQL override for all partitions in the session. OPT_63107 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains an SQL override with Informatica join syntax. Cause: The SQL override contains Informatica join syntax. Because the Integration Service creates a view to process the SQL override, the syntax must be compatible with the source database. Action: Use source database syntax when you write the SQL override. OPT_63108 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains a user-defined join with Informatica join syntax. Cause: The user-defined join contains Informatica join syntax. Because the Integration Service pushes the transformation logic for the join to the source database, the syntax must be compatible with the source database. Action: Use source database syntax when you write the user-defined join. OPT Messages 347
- 364. OPT_63120 Pushdown optimization stops at the Aggregator transformation <transformation name> because there is an upstream Aggregator transformation. Cause: The Aggregator transformation is the second Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for more than one Aggregator transformation in a pipeline. This occurs because the SQL generated for two consecutive Aggregator transformations results in a nested Aggregator function, which cannot be processed on the database. Action: None. OPT_63131 Pushdown optimization stops at the Joiner transformation <transformation name> because an input pipeline contains an Aggregator transformation. Cause: An Aggregator transformation exists in an input pipeline. The database must perform join operations before aggregation operations, so the Integration Service cannot generate an SQL statement for a Joiner transformation that is downstream from an Aggregator transformation. Action: None. 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. Cause: The master source joins multiple tables. The Integration Service cannot generate SQL to join multiple tables with an outer join. Action: None. OPT_63147 Pushdown optimization stops at the Lookup transformation <transformation name> because it is downstream from an Aggregator transformation. Cause: The Lookup transformation is downstream from an Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for a Lookup transformation downstream from an Aggregator transformation. Action: None. OPT_63152 Pushdown optimization stops at the Sorter transformation <transformation name> because the distinct key <port name> is not used downstream. Cause: The Integration Service cannot generate SQL for a Sorter transformation configured for a distinct sort when the distinct key is not used downstream. Action: None. OPT_63157 Pushdown optimization stops at the Union transformation <transformation name> because the sources use different database connections. Cause: The Union transformations joins sources that are from different databases or that use different database connections. 348 Chapter 49: OPT Messages
- 365. Action: If the Union transformation joins sources from the same database, ensure that you specify the same database connection in the session properties. OPT_63170 ERROR: Pushdown optimization stops at the transformation <transformation name> because it contains an invalid expression. Cause: Internal error. Action: Contact Informatica Technical Support. OPT_63175 ERROR: Pushdown optimization stops at the transformation <transformation name> because the mapping parameter <mapping parameter name> cannot be expanded. Cause: The transformation contains a mapping parameter that cannot be expanded. The parameter file may be corrupt, the path to the parameter file may be incorrect, or the parameter file name may be incorrect. Action: Modify the parameter file, the path to the parameter file, or the parameter file name. OPT_63177 Pushdown optimization stops at the transformation <transformation name> because expression <expression name> with < parameter name> parameters cannot be pushed to the database. Cause: The expression uses a parameter that represents a datatype that is unsupported on the database. Action: None. OPT_63193 Pushdown optimization to target stops at the transformation <transformation name> because the expression <expression name> uses a boolean expression for parameter <parameter name>. Cause: The numeric expression contains a boolean subexpression. Numeric and boolean values are not compatible in SQL. To covert a boolean expression to a numeric expression, the database requires a case statement, which cannot be performed with target-side pushdown optimization. Action: None. OPT_63205 Error encountered while attempting to partition session at runtime. Cause: The Integration Service could not dynamically partition the session. Action: Review previous messages in the session log to determine the cause. OPT_63206 Invalid Partition Count <count>. Cause: You set dynamic partitioning based on the number of partitions but the attribute does not contain a valid value. Action: Set the Number of Partitions to the $DynamicPartitionCount session parameter or enter a number greater than 1. OPT Messages 349
- 366. OPT_63207 Partition Count is 1. Dynamic Partitioning has been disabled. Cause: The Number of Partitions session attribute is 1. The session runs in one partition. Action: Set the number of partitions to a number greater than 1, or change the method of partitioning. OPT_63213 Error retrieving database partition information <database name>. Cause: When you use database partitioning, the Integration Service generates SQL queries to access data in each database partition. The Integration Service queries of the database system catalog failed. Action: Review previous messages to determine why the database is inaccessible. OPT_63214 Error retrieving partitions. Cause: The Integration Service is using database partitioning, but it cannot retrieve partition IDs or partition names. Action: Review previous messages to determine why the partitions are inaccessible. OPT_63215 Error partitioning session attributes. Cause: The Integration Service could not create partition-level attributes for dynamic partitions. Action: Verify that you enter valid values for the session parameters that the Integration Service uses to create dynamic partition attributes. Partition-level attributes include source, target, and reject file names and locations. OPT_63216 Error partitioning key range for transformation <transformation name>. Cause: You are using key range partitioning and the Integration Service cannot partition the key ranges you defined for a transformation. Action: Verify the key ranges do not have gaps or overlapping ranges. OPT_63217 Transformation <transformation name> uses a key range data type that cannot be partitioned. Cause: The key range partition key must be a number or a date for a dynamic partitioned session. Action: Disable dynamic partitioning or change the key type to a number or date. OPT_63218 Key range not closed. Cause: You cannot enable dynamic partitioning for a transformation that uses an open range of partition key numbers. Action: Disable dynamic partitioning or change the key range to a closed range of numbers. 350 Chapter 49: OPT Messages
- 367. OPT_63219 Transformation <transformation> uses pass-through partitioning which is disallowed by dynamic partitioning. Cause: You cannot enable dynamic partitioning for a relational source using a pass- through partition type. The session runs in one partition by default. Action: Disable dynamic partitioning or use a database partition type. OPT_63220 Transformation <transformation name> specifies user defined SQL that will not be partitioned. Cause: You enabled dynamic partitioning for a session with a transformation that has user-defined SQL. The session runs in one partition by default. Action: Disable dynamic partitioning or remove the user-defined SQL. 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. Cause: The number of partitions must be consistent across a pipeline in a mapping. If the Integration Service cannot dynamically partition a transformation in a pipeline, it does not partition the pipeline. The session runs in one partition by default. Action: Disable dynamic partitioning. OPT_63222 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK readers is not supported. Cause: You enabled dynamic partitioning in a session containing an SDK source. You cannot enable dynamic partitioning for SDK and PowerCenter Connect sources and targets. The session runs in one partition by default. Action: Disable dynamic partitioning. OPT_63223 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK writers is not supported. Cause: You enabled dynamic partitioning in a session containing an SDK target. You cannot enable dynamic partitioning for SDK and PowerCenter Connect sources and targets. The session runs in one partition by default. Action: Disable dynamic partitioning. OPT_63224 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML readers is not supported. Cause: You enabled dynamic partitioning for a pipeline that contains an XML source transformation. The session runs in one partition by default. Action: Disable dynamic partitioning. OPT Messages 351
- 368. OPT_63225 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML writers is not supported. Cause: You enabled dynamic partitioning for a pipeline that contains an XML target transformation. The session runs in one partition by default. Action: Disable dynamic partitioning. OPT_63226 Transformation <transformation name> will not be partitioned because partitionable attribute <attribute name> has a user specified value. Cause: The Integration Service does not partition a transformation when you enter a value for a partition-level attribute. Action: To use dynamic partitioning with a Custom transformation, clear the referenced attribute. For other transformations, set the cache directory to the default, $PMCacheDir. OPT_63227 Transformation <transformation name> is not partitionable. Cause: You enabled dynamic partitioning for a session that contains a transformation that is not partitionable. The session runs in one partition by default. Action: Disable dynamic partitioning or change the transformation that is not partitionable. OPT_63229 Unable to determine dynamic partition count because an error was encountered while expanding parameter <parameter name>. Cause: The Integration Service could not determine the number of partitions to create. Action: Verify that the $DynamicPartitionCount session parameter contains a number greater than 1. 352 Chapter 49: OPT Messages
- 369. Chapter 50 PCSF Messages This chapter includes the following topic: โฆ PCSF Messages, 354 Error messages listed numerically. 353
- 370. PCSF Messages PCSF_10004 Authentication for <user name> failed because <error message>. Cause: The authentication failed for the specified user. Action: Resolve the issue using the details provided in the error message. PCSF_10005 An attempt to [activity] access [object name] failed for [user name] because: [error text]. Cause: A user attempted to run a command that accesses the object specified. The command could not be executed because the command line program cannot access the object. Action: Verify that the user specified in the command has permission on the object. PCSF_10006 No Integration Service Ref were provided. Cause: Validation failed for an SAP BW Service because no Integration Service references were found. Action: Configure the Integration Service for the an SAP BW Service. PCSF_10007 Cannot connect to repository <repository name> because: <reason for failure>. Cause: A problem was encountered when you attempted to connect to the repository. Action: Resolve the issue using the details provided in the message. PCSF_10013 The file domains.infa was not defined in the system properties. Cause: The system was unable to locate the domains.infa file required to communicate with the domain. Action: Internal error. Attempt to start Informatica Services again. If the problem persists, contact Informatica Technical Support. PCSF_10015 A message was being sent without specify either the domain name or host/ port. Cause: The command requires that the domain name or host name and port number be entered as a command option. No domain name or host and port number was entered. Action: Enter the domain name or host name and port number as a command option. PCSF_10017 Failed to receive response from [<URL>] because: [<error text>]. Cause: The PowerCenter Client did not receive a response from a service at the URL. Action: Correct the error indicated in the message. 354 Chapter 50: PCSF Messages
- 371. PCSF_10019 Operation [<operation name>] of service [<service name>] failed because: [<error text>]. Cause: The Service Manager attempted an operation. However, operation failed because of an error. Action: Correct the error indicated in the message and retry the operation. PCSF_10020 Cannot write to file [<domain file name>]. Cause: The domains.infa file is read-only, or there is not enough disk space available. Action: Make sure the domains.infa file is not read-only and that there is enough disk space available. PCSF_10024 Timed out while trying to connect to domain [<domain name>] to lookup service [<service name>]. Cause: The PowerCenter Client could not connect the domain within the resilience timeout period. Action: Verify that the domain is running and reconnect to the domain. If the domain is not running, ask the domain administrator to start PowerCenter Services. PCSF_10025 Cannot parse message: [<error text>]. Cause: The Service Manager received a response with inconsistent message content. As a result, the operation failed. Action: Correct the error indicated in the message. PCSF_10027 No gateway connectivity is found for domain [name]. Cause: The command line program was unable to find the domain specified in the command. Action: Verify that the domain exists and that the domain name was entered correctly. PCSF_10028 Cannot respond to operation [<operation name>] of service [<service name>]: [<error text>]. Cause: The Service Manager attempted an operation. However, the operation failed because of an error. Action: Correct the error indicated in the message and retry the operation. PCSF_10039 Linked domain <linked domain name> must specify at least one gateway. Cause: Validation for a linked domain failed as no gateways were specified. Action: Make sure you specify at least one gateway. PCSF_10040 Logging service [PurgeLogsOlderLimit] value <entered value> is invalid. Cause: The Service Manager validation failed due to an invalid value. Action: Ensure that all the values you enter are within valid ranges. PCSF Messages 355
- 372. PCSF_10041 Logging Service [MaximumLogSize] value <entered value> is invalid. Cause: The Service Manager validation failed due to an invalid value. Action: Ensure that all the values you enter are within valid ranges. PCSF_10042 Logging service [LogServiceDirectory] value <entered value> is invalid. Cause: The Service Manager validation failed due to an invalid value. Action: Ensure that all the values you enter are within valid ranges. PCSF_10060 Value <value> exceeded maximum length <maximum length>. Cause: A value length exceeds the maximum. Action: Shorten the value to be less than the maximum length. PCSF_10081 Cannot deserialize <node or domain> configuration file <metadata file name>. Cause: The Service Manager has inconsistent data. Action: Contact Informatica Technical Support. PCSF_10083 Failed to open backup configuration file <metadata file name>. Cause: The disk that stores the metadata file is not accessible. Action: Verify that the metadata file is in an accessible location. PCSF_10085 Failed to read the configuration file from <metadata file name> or <backup metadata file name>. Cause: The disk that stores the metadata file is not accessible. Action: Verify that the metadata file is in an accessible location. PCSF_10095 An unexpected token was encountered during deserialization. Cause: Internal Error. An unexpected token was encountered while reading an object. Action: If problem persists, contact Informatica Technical Support. PCSF_10131 The license key was previously applied. Cause: You tried to add an incremental key that has already been added. Action: To enable additional options, use a different incremental key. PCSF_10132 You cannot apply more than one original key to a license. To update an existing license, select a license file with an incremental key. Cause: Each license requires one original key. You cannot apply more than one original key to the same license. You must use an incremental key to update an existing license. You use an original key to create a new license. Action: Apply the incremental key to the existing license to update the license. or 356 Chapter 50: PCSF Messages
- 373. Action: Create a new license using the original key. PCSF_10133 The issue date for the original key must be earlier than the issue dates for the incremental keys. Cause: Each incremental key must be issued after the original key. Action: Contact Informatica Technical Support to get a valid incremental key. PCSF_10135 Validating license failed because cannot be read properly. Cause: The license key file is unreadable. Action: Contact Informatica Technical Support to get a new license key file. PCSF_10136 License is invalid. The Licensing Service encountered an invalid attribute value in the license. Cause: The key provided was not validated as having proper encryption. Action: Please acquire a new license key file from Technical Support. PCSF_10137 License is invalid. The Licensing Service encountered an invalid value [begin date value] for the Begin Date attribute. Cause: The license is invalid. The Begin Date attribute encountered in the license file is invalid. Action: Contact Informatica Technical Support to get a valid license key file. PCSF_10138 License is invalid. The Licensing Service encountered an invalid value [expiry date value] for the Expiry Date attribute. Cause: The Expiry Date attribute in the license file is invalid. Action: Contact Informatica Technical Support to get a valid license key file. PCSF_10139 License is invalid. The Licensing Service encountered an invalid value [issue date value] for the Issue Date attribute. Cause: The Issue Date attribute in the license file is invalid. Action: Contact Informatica Technical Support to get a valid license key file. PCSF_10140 Invalid number of CPUs <number of CPUs> encountered. Cause: The CPUs attribute in the license file is invalid. Action: Contact Informatica Technical Support to get a valid license key file. PCSF_10141 License is invalid. The Licensing Service encountered an invalid value <number of repositories> for the repositories attribute. Cause: The Service Manager failed to validate the license because the number of repositories is invalid. Action: Contact Informatica Technical Support to get a valid license key file. PCSF Messages 357
- 374. PCSF_10304 Cannot connect to URL [< URL >] to perform operation [<operation name>] of service [<service name>]. Cause: A client or service attempted to connect to the URL to perform an operation. However, the operation failed because the client or service could not connect to the URL within the resilience timeout. Action: Verify that the host name and port number for the URL and retry the operation. PCSF_10305 Cannot connect to gateway [<node address>] to look up service [<service name>]. Cause: The PowerCenter component could not connect to the Service Manager on the gateway node to look up a service within the resilience timeout for the domain. Action: Verify that the gateway node is running. PCSF_10306 Operation [<operation name>] of service [<service name>] was interrupted. Cause: The service could not complete the operation. This error can occur because the Service Manager is in the process of shutting down. Action: Restart the node. PCSF_10322 The following error occurred while logging to Log Service: [<error text>]. Cause: The Log Manager cannot process log events because of the operating system error shown. For example, the network file system may be unavailable. Action: Fix the errors listed in the node.log file. The node.log file is located in the servertomcatlogs directory. PCSF_10325 Error threshold exceeded for number of failed log attempts. Disabling guaranteed messaging. Cause: Too many errors occurred while the Log Manager was processing log events. Action: Fix the errors listed in the node.log file. The node.log file is located in the servertomcatlogs directory. PCSF_10326 The following error occurred while generating the guaranteed message file: [<error text>]. Cause: An application service process could not create the Guaranteed Message Delivery file because of the operating system error shown. For example, the network file system may be unavailable. Action: Try to fix the operating system error. 358 Chapter 50: PCSF Messages
- 375. PCSF_10327 The following error occurred while writing to the guaranteed message file [<file name>]: [<error text>]. Cause: An application service process could not write log events to the Guaranteed Message Delivery file because of the operating system error shown. For example, the network file system may be unavailable. Action: Try to fix the operating system error. PCSF_10336 Incremental key is of a different deployment type than the original key. To update a license, use an incremental key that has same deployment type as the original key that was used to create the license. Cause: The incremental key has a different deployment type than the original key that was used to create the license. Action: Get an incremental license key from Informatica with the correct deployment type. PCSF_10337 Incremental key is for a different distributor than the original key. To update a license, use an incremental key that has same distributor as the original key that was used to create the license. Cause: The incremental key is for a different distributor than the original key that was used to create the license. The distributor is the organization that issued the PowerCenter product. Action: Get an incremental license key from Informatica with the correct distributor. PCSF_10338 Incremental key is for a different PowerCenter edition than the original key. To update a license, use an incremental key that has the same PowerCenter edition as the original key that was used to create the license. Cause: The incremental key is for a different PowerCenter edition than the original key that was used to create the license. Action: Get an incremental license key from Informatica with the correct PowerCenter edition. PCSF_10339 Incremental key has a different serial number than the original key. To update a license, use an incremental key that has same serial number as the original key that was used to create the license. Cause: The incremental key uses a different serial number than the original key that was used to create the license. Action: Get an incremental license key from Informatica with the correct serial number. PCSF Messages 359
- 376. 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. Cause: The incremental key is for a different PowerCenter version than the original key that was used to create the license. Action: Get an incremental license key from Informatica with the correct PowerCenter version. PCSF_10341 Cannot create a license with an incremental key. Cause: You tried to create a license using an incremental key. Action: You must use an original key to create a license. PCSF_10352 Upgrade configuration file [<file name>] is not found. Error: <error text> Cause: You selected a single Repository Agent or PowerCenter Server configuration file in the Upgrade Wizard, but the file you selected does not exist. Action: Verify that the file exists and open the file again. PCSF_10353 Error parsing upgrade configuration file: <error text> Cause: The Upgrade Wizard encountered an error in a Repository Agent to PowerCenter Server configuration file and could not validate the file. Action: Correct the error indicated in the message and validate the file again. PCSF_10354 Unable to identify the service type for configuration file [<file name>]. The file might be an invalid configuration file. Cause: The Upgrade Wizard could not determine if the configuration file is a Repository Agent or PowerCenter Server configuration file. A Repository Agent configuration file must contain the [RepositoryName] property. A PowerCenter Server configuration file must contain the [ServerName] property. Action: Correct the contents of the configuration file and validate the file again. If you created the PowerCenter Server configuration file with the pmserverexportreg utility, the registry for the machine running the PowerCenter Server may contain inconsistent data. PCSF_10355 Configuration file [<file name>] is missing the required option(s) <option names>. Cause: The Upgrade Wizard could not validate the Repository Agent or PowerCenter Server configuration file because the file is missing one or more of the required properties. Action: Add the required property or properties to the configuration file and validate the file again. 360 Chapter 50: PCSF Messages
- 377. PCSF_10356 File [<file name>] has extension other than .cfg. Upgrade only works with .cfg file. Cause: You placed a file in the global_repo, local_repo, or PCServer directory in the server/upgrade/cfgfiles directory on a node. However, you can only upgrade Repository Agent or PowerCenter configuration files with the .cfg extension. The Upgrade Wizard cannot validate or upgrade the file. Action: If the file is a Repository Agent or PowerCenter Server configuration file, rename the file with the correct extension. If the file is not a configuration file, remove the file from the upgrade directory or ignore the error. PCSF_10357 File [<file name>] contains service [<service name>] which already exists in domain [<domain name>]. Cause: The [RepositoryName] or [ServerName] property in the Repository Agent or PowerCenter Server configuration file matches a Repository Service or Integration Service name in the domain. As a result, the Upgrade Wizard cannot upgrade the configuration file. Action: If you already upgraded the Repository Agent or PowerCenter Server configuration file, ignore the error and do not upgrade the configuration file. If you want to upgrade the configuration file again, remove the service from the domain and upgrade the file again. PCSF_10358 Upgrade configuration files directory is not found on node <node name>. Cause: You selected a node that contains Repository Agent and PowerCenter Server configuration files to upgrade in the Upgrade Wizard. However, the server/ upgrade/cfgfiles directory does not exist on the node. The directory was removed after installation. Action: Create the directory and place Repository Agent and PowerCenter Server configuration files in the appropriate global_repo, local_repo, and PCServer directories under the server/upgrade/cfgfiles directory on the node, and then validate the files again. PCSF_10359 File [<file name>] contains service [<service name>] which already exists in other configuration files selected for upgrade. Cause: The value for the [RepositoryName] or [ServerName] property in the Repository Agent or PowerCenter Server configuration file matches the same property in another configuration file under the server/upgrade/cfgfiles directory on the node. All configuration files you want to upgrade must contain different values for the [RepositoryName] or [ServerName] properties. There may be duplicate configuration files in the upgrade directory. Action: Make sure the configuration file have unique values for the [RepositoryName] or [ServerName] properties and validate the files again. PCSF Messages 361
- 378. 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>]. Cause: The PowerCenter Server configuration file contains an associated repository that does not have a corresponding Repository Service in the domain. The Upgrade Wizard requires information from the repository to upgrade the PowerCenter Server. As a result, the Upgrade Wizard cannot upgrade the Powercenter Server. Action: Upgrade the Repository Agent for the associated repository before you upgrade the PowerCenter Server. 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. Cause: The PowerCenter Server configuration file contains an associated repository that does not have a corresponding Repository Service in the domain or in any of the Repository Agent configuration files you want to upgrade. The Upgrade Wizard will not be able to upgrade the PowerCenter configuration file without an upgraded Repository Service for the associated repository. Action: Make sure the domain has an upgraded Repository Service for the associated repository or that the upgrade directory has a Repository Agent configuration file for the associated repository. Otherwise, remove the PowerCenter Server configuration file from the upgrade directory. PCSF_10374 Failed to persist [object] with error [message]. Cause: PowerCenter could not create the object because of the database error shown. Action: Correct the database error. or Cause: The infasetup DefineDomain command was used to create a domain on IBM DB2 and the primary tablespace default page size is too small. Action: If the domain configuration database type is IBM DB2, make sure that the primary tablespace default page size is at least 16K. PCSF_10386 Unable to decrypt the password for option [<option name>]. It's possible that the password is corrupted. Please use previous installation of PowerCenter to re-generate the password and try again. Cause: The Upgrade Wizard cannot decrypt the encrypted password in the Repository Agent or PowerCenter Server configuration file. Action: Use pmpasswd in the previous version of PowerCenter to encrypt the password. Correct the password in the configuration file, revalidate the configuration 362 Chapter 50: PCSF Messages
- 379. file, and upgrade the Repository Agent or PowerCenter Server configuration file again. PCSF_10389 The selected configuration file [<file name>] is a Repository Agent configuration file. The PCServer directory should only contain PowerCenter Server configuration files. Move [<file name>] to the global_repo or local_repo directory. Cause: You placed a Repository Agent configuration file in the PCServer directory under the server/upgrade/cfgfiles directory on a node. However, the PCServer directory can only contain PowerCenter Server configuration files. Action: Move the Repository Agent to the global_repo or local_repo directory under the server/upgrade/cfgfiles directory on the node and validate the configuration files again. PCSF_10391 Configuration file contains required option(s) <option names> with empty value. Cause: A property or properties in a Repository Agent or PowerCenter Server configuration files does not have a corresponding value. Action: Add a value for the property in the configuration file and validate and upgrade the configuration file again. PCSF_10392 <error text> Cause: The Repository Agent or PowerCenter Server configuration contains an error and the Upgrade Wizard cannot upgrade the configuration file. Action: Correct the error indicated in the message and validate and upgrade the configuration file again. PCSF_10402 Unable to validate the log directory <shared disk> due to the error <error>. Cause: The permissions of the shared disk was not validated. Action: Verify the path and directory. The user that starts Informatica Services on the node must have permissions to write to the directory. PCSF_10404 The log directory [<shared directory>} cannot be created. Cause: The shared directory cannot be created because it is not valid or user does not have permission. Action: Verify the path and directory. The user that starts Informatica Services on the node must have permissions to write to the directory. PCSF_10407 Cannot find server [<server name>] in repository [<repository name>] Cause: The PowerCenter Server is not registered to the associated repository in the PowerCenter Server configuration file. PCSF Messages 363
- 380. Action: Register the PowerCenter Server to the associated repository in the previous version of PowerCenter. Move the configuration file to the server/upgrade/ cfgfiles/PCServer directory on the node and validate and upgrade the PowerCenter Server again. PCSF_10408 Failed at line #<line number> because option is missing value assignment Cause: The Repository Agent or PowerCenter Server configuration file contains a property without an associated value at a specific line number. Action: Correct the value for the property at the line number in the configuration file and validate and upgrade the Repository Agent or PowerCenter Server configuration file again. PCSF_10410 The selected configuration file [<file name>] is a PowerCenter Server configuration file. The global_repo or local_repo directory should only contain Repository Agent configuration files. Move [<file name>] to the PCServer directory. Cause: You placed a PowerCenter Server configuration file in the global_repo or local_repo directory under the server/upgrade/cfgfiles directory on a node. However, the global_repo or local_repo directory can only contain Repository Agent configuration files. Action: Move the PowerCenter Server configuration file to the PCServer directory under the server/upgrade/cfgfiles directory on the node and validate the configuration files again. PCSF_10414 <error text> Please 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. Cause: The [RepositoryName] property in the Repository Agent contains a tab character, a trailing space, or one of the following characters: ? " : < > * / | . Action: Back up the repository, restore it using a name that does not contain these characters, and the upgrade the Repository Agent configuration file again. PCSF_10421 Error parsing upgrade configuration file at line #<line number>. The end string */ for block comment must be at the end of the line. Cause: In a Repository Agent or PowerCenter Server configuration file, the end block comment string '*/' occurs in the middle of a line, but can only appear at the end of a line. Action: Correct the configuration file and place the end comment string at the end of the line. Then validate and upgrade the configuration file again. 364 Chapter 50: PCSF Messages
- 381. 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. Cause: You started a comment block that was not ended in a Repository Agent or PowerCenter Server configuration file. Action: Correct the configuration file and place the end comment string in the file. Then validate and upgrade the configuration file again. PCSF_10423 File [<file name>] is a Repository Agent configuration file. Choose a PowerCenter Server configuration file or change the configuration file type. Cause: In the Upgrade Wizard, you chose a Repository Agent configuration file, but selected a PowerCenter Server file type. Action: Choose a PowerCenter Server configuration file or change the file type. PCSF_10424 File [<file name>] is a PowerCenter Server configuration file. Choose a Repository Agent configuration file or change the configuration file type. Cause: In the Upgrade Wizard, you chose a PowerCenter Server configuration file, but selected a Repository Agent file type. Action: Choose a Repository Agent configuration file or change the file type. PCSF_10426 Cannot find server [<server name>] in repository [<repository name>]. Cause: The PowerCenter Server is not registered to the associated repository in the PowerCenter Server configuration file. Action: Register the PowerCenter Server to the associated repository in the previous version of PowerCenter. Move the configuration file to the server/upgrade/ cfgfiles/PCServer directory on the node and validate and upgrade the PowerCenter Server again. PCSF_10427 Option has invalid value <invalid value>. Cause: Option contains an invalid value. Action: Use the default value. PCSF_10428 Option number <invalid value> is in an invalid format. Cause: A number option contained invalid numeric format. Action: Use the default value. PCSF_10429 Required option <option name> missing. Cause: Domain metadata is invalid with missing required option. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF Messages 365
- 382. PCSF_10430 Duplicate option <duplicate option name> found. Cause: Domain metadata is invalid with duplicate option. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF_10431 Unknown option <option name> found. Cause: Domain metadata is invalid with an unknown option. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF_10432 Option group <expected option group name> misnamed as <actual option group name>. Cause: Domain metadata is invalid with wrong option group name. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF_10433 Option field cannot be empty. Cause: Domain metadata is invalid with empty option. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF_10434 Option specified an invalid email address of <entered email address>. Cause: Domain metadata is invalid with invalid email address. Action: Back up the domain, correct the backup (XML) file, and restore the domain. PCSF_10436 Unknown value <unknown value> found. Cause: An unknown value was encountered in an object. Action: If problem persists, please contact Informatica Technical Support. PCSF_10439 Failed to load the list of codepages: <SDK exception message from locale manager> Cause: Loading the list of codepages failed when fetching from locale manager. Action: If problem persists, contact Informatica Technical Support PCSF_10440 Value <value> contains invalid spaces. Cause: A value contains invalid spaces. Action: Remove all spaces from the value. PCSF_10441 Reference to linked domain <domain name> not defined. Cause: Attempting to communicate with a linked domain not in domain metadata. Action: Add appropriate linked domain then try again. PCSF_10442 Failed to drop domain tables. Cause: Database connection could not delete the domain. 366 Chapter 50: PCSF Messages
- 383. Action: Make sure the database is running. PCSF_10443 CPU architecture <architecture name> is not supported. Cause: The node is starting on an unsupported platform. Action: Run PowerCenter only on supported platforms. PCSF_10445 Option <option name> is greater than option <option name>. Cause: A minimum option value is greater than a maximum option value. Action: Make sure the minimum value is less than or equal to the maximum. PCSF_10446 Option memory size <invalid value> must be blank or a number followed by optional K or M. Cause: A number option contained invalid memory size format. Action: Enter a valid memory size format. PCSF_46000 INFA_DOMAINS_FILE is not set in the environment variable. Cause: You can use the environment variable INFA_DOMAINS_FILE to store the domains.infa path. You will receive an error if the environment variable INFA_DOMAINS_FILE is not set. Action: Add the environment variable INFA_DOMAINS_FILE, and set the path to the domains.infa file. By default, the domains.infa file resides in the infa_home directory. PCSF_46002 Failed to communicate with the server at <server address>. Cause: The request exceeded the timeout period due to an invalid connection or domain not running. Action: Ping the domain using infacmd ping and provide the gateway address. If the connection is invalid, infacmd ping adds or updates domains.infa file. If the domain is not running, ask the domain administrator to start Informatica Services. PCSF_46003 Failed to understand the response [<response text>] from server at [<server address>]: <error text>. Cause: A PowerCenter component failed to understand the response from a PowerCenter service due to an error. Action: Correct the error indicated in the message. PCSF_46006 Domain name is not specified. Cause: The command line programs require the domain name, which you provide as an option at the command prompt. If you incorrectly type this information, you will receive an error. PCSF Messages 367
- 384. Action: Verify that you typed the domain name at the command prompt correctly. Optionally, you can store the domain name as the environment variable INFA_DEFAULT_DOMAIN. If you have more than one domain, choose a default domain. PCSF_46007 No gateway connectivity is provided for domain [<domain name>]. Cause: The domains.infa file does not contain the information necessary to connect to the domain or the domains.infa does not exist. Action: Ping the domain using infacmd ping and provide the gateway address. If the connection is invalid, infacmd ping adds or updates domains.infa. If the domain is not running, ask the domain administrator to start Informatica Services. Action: If you attempted to connect to a repository with the PowerCenter Client, remove the repository in the Navigator and add the repository again. PCSF_46008 Failed to look up service. Cause: The Service Manager on the gateway is not running, and cannot accept the request. Action: Use the infacmd ping to verify that the domain is running and the connection parameters are configured correctly. If the domain is running, infacmd displays the host name and port number of the domain. If the domain is stopped or unavailable, ask the domain administrator to start Informatica Services. Contact Informatica Technical Support if the domain is running and you continue to receive an error. PCSF_46009 Invalid type <object type> encountered. Failed to create an object instance. Same as PCSF_46002. PCSF_46010 Cannot parse message: <reason for error> Cause: You specified the incorrect domain name, gateway host name, or port number from a PowerCenter client application, such as pmcmd or the Designer. Action: Verify that you use the correct gateway information. If the gateway information is correct, and you continue to receive this error, contact Informatica Technical Support. or Cause: The Domain Service could not parse the SOAP message received from a remote client, such as an FTP server. Action: Review the log for related messages to find out more information. or Action: Contact Informatica Technical Support. 368 Chapter 50: PCSF Messages
- 385. PCSF_46012 Cannot write to file <file name>. Same as PCSF_10020. PCSF_46013 Cannot connect to URL < URL > to perform operation <operation name> of service <service name>. Same as PCSF_10304. PCSF_46014 Cannot connect to gateway to look up service <service>. Same as PCSF_10305. PCSF_46015 An unexpected token was encountered during deserialization. Same as PCSF_10095. PCSF Messages 369
- 386. 370 Chapter 50: PCSF Messages
- 387. Chapter 51 PETL Messages This chapter includes the following topic: โฆ PETL Messages, 372 Error messages listed numerically. 371
- 388. PETL Messages PETL_24042 The Preparer DTM has timed out after waiting <time in seconds> seconds for the Master DTM to connect. Cause: The master DTM process was unable to connect with the preparer DTM process. The master DTM process may have shut down unexpectedly. The master DTM process may be on another node and there may be a network failure. Action: View the workflow log to see if the DTM process started on the node. If the DTM process started and shut down unexpectedly, the error is internal. If the error is not internal, check with the Network Administrator to verify that the network does not have connectivity issues. Check with the domain Administrator to verify that the Integration Service is running. Run the session again. PETL_24045 The Master DTM failed to connect to the Preparer DTM. Cause: The master DTM process failed to connect to the preparer DTM process. There may be a network failure and the master DTM and preparer DTM processes are running on different nodes. The preparer DTM process may have shut down unexpectedly. Action: Same as PETL_24042. PETL_24046 The Master DTM timed out after <time in seconds> seconds while trying to connect to the Preparer DTM. Cause: The master DTM process timed out attempting to connect with the preparer DTM process. The master DTM and the preparer DTM processes may be running on separate nodes and there is a network failure. The preparer DTM process may have shut down unexpectedly. Action: Same as PETL_24042. PETL_24048 The Master DTM failed to fetch the prepared session from the Preparer DTM. Cause: The master DTM process was unable to connect with the preparer DTM process. The master DTM and preparer DTM processes may be on separate nodes and there may be a network failure. The preparer DTM process may have shut down unexpectedly. Action: Same as PETL_24042. PETL_24049 Failed to get the initialization properties from the master service process for the prepare phase <error message> with error code <error code>. Cause: The preparer DTM process was unable to retrieve run time properties from the Integration Service due to an error. Action: Use the returned error code error message to determine the cause of this error. 372 Chapter 51: PETL Messages
- 389. PETL_24061 The Master DTM exceeded the maximum wait time while waiting for all Worker DTMs to connect. Cause: The master DTM process waited longer than the maximum amount of time allotted to wait for worker DTM processes to connect. The node running the worker DTM process may have failed, or connectivity to the worker DTM process may have failed. Or, the worker DTM process may have shut down unexpectedly. Action: Same as PETL_24042. PETL_24063 The Preparer DTM encountered error <error message> with error code <error code> while notifying the Integration Service of the prepare phase status. Cause: An error prevented the preparer DTM process from connecting to the Integration Service. Action: Use the returned error code message to determine the cause of this error. PETL_24064 Thread <thread ID> waited for <time in seconds> seconds for a message. The current number of attempts is <attempt number> and the maximum number of attempts is <maximum number of attempts>. Cause: An error prevented the preparer DTM process from connecting to the Integration Service. Action: Use the returned error code message to determine the cause of this error. PETL_24065 Error: Thread <thread name> exceeded the maximum wait time while waiting for a reply from the Master DTM. Cause: A worker DTM process waited longer than the maximum amount of time allotted to wait for a reply from the master DTM process. Action: Same as PETL_24042. 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. Cause: The master DTM process detected that a worker DTM process failed unexpectedly. Action: Same as PETL_24042. PETL_24067 The Worker DTM connection with the Master DTM terminated unexpectedly. The Worker DTM will stop processing the session. Cause: The worker DTM process detected that a connection to the master DTM process failed. The master DTM process and worker DTM process may be on different nodes and there may be a network failure. Action: Same as PETL_24042. PETL Messages 373
- 390. PETL_24074 Failed to send updates to the master service process. Session run will be terminated. Cause: The master DTM process was unable to send updates to the master service process. Action: Same as PETL_24042. 374 Chapter 51: PETL Messages
- 391. Chapter 52 PMF Messages This chapter includes the following topic: โฆ PMF Messages, 376 Error messages listed numerically. 375
- 392. PMF Messages PMF_15000 Failed to read from file <file name>. Cause: The Integration Service failed to read the file. The file might be already open, or the disk might be corrupt. Action: Check the session log for related errors. PMF_15001 Failed to write to file, there may not be enough space left on the device. Cause: The hard disk is full. Action: Check the disk for free space, and check the session log for related errors. PMF_15002 Failed to seek in file <file name>. Cause: The file pointer failed to locate the file. You might have deleted or moved the file, or the hard disk might be corrupt. Action: Check the session log for related errors. PMF_15003 File <file name> is not in the correct format. Cause: You might have altered the format of the file. For example, you copied another file to the file. Action: Use a previous copy of the file that has the correct format. or Cause: Internal error. Action: Contact Informatica Technical Support. PMF_15004 Unable to open file <file name>. Cause: You might not have the correct write file permissions. Action: Make sure you have the proper write permissions. or Cause: You provided an incorrect file name or cache directory that the Integration Service cannot locate. Action: Provide the correct file name and aggregation cache directory in the Workflow Manager. PMF_15005 File <file name> is in an unknown state due to error from a previous run. Cause: The system shut down unexpectedly during the previous run. Action: Use the backup file (filename.bak). 376 Chapter 52: PMF Messages
- 393. PMF_15006 Failed to create file <file name> because file exists and contains data. Cause: The Integration Service failed to remove the previous file and detected a file containing data and failed to overwrite it. Action: Check the file and manually delete it or rename it. Run the session again. PMF_15007 Failed to read file <file name> because PowerCenter/PowerMart file header is corrupt. Cause: The file might be corrupt due to a system crash on a previous session run. Action: Use the backup file (filename.bak), if available, and run the session again. or Cause: Internal error. Action: Contact Informatica Technical Support. PMF_15008 I/O requested for invalid file ID. Cause: Internal error. Action: Use the backup file filename.bak. or Action: Contact Informatica Technical Support. PMF_15009 Specified file name <file name> exceeds the maximum length of 256 characters. Cause: Internal error. You may have repository inconsistencies. Action: Contact Informatica Technical Support. PMF_15010 The number of files exceeds the maximum number of 256. Cause: The cache exceeded half a terabyte. Action: Contact Informatica Technical Support. PMF_15011 Unable to allocate memory. Cause: Error in heap memory allocation. Your system resources may be low. Action: Free existing resources. or Action: Increase the swap space. You may need to add RAM to your system. PMF_15012 Unable to delete file <cache file name>. System error is <error number> <error message>. Cause: This file might be in use. Action: Check the session that is running. See the system error for more information. PMF Messages 377
- 394. PMF_15013 Unable to rename file <cache file name> to <cache file name>. System error is <error number> <error message>. Cause: This file might be in use. Action: Check the session that is running. See the system error for more information. PMF_15014 Unable to stat file <cache file name>. System error is <error number> <error message>. Cause: The call to get cache file properties failed. Action: Contact Informatica Technical Support. PMF_15016 Failed to get a shared lock on file <cache file name>. System error is <error number> <error message>. Cause: The file might be in use. A session could be writing to the file. Action: Check the session that is running. See the system error for more information. PMF_15017 Failed to get an exclusive lock on file <cache file name>. System error is <error number> <error message>. Cause: The file might be in use. A session could be writing to the file. Action: Check the session that is running. See the system error for more information. PMF_15018 Failed to unlock file <cache file name>. System error is <error number> <error message>. Cause: The file might be in use. A session could be reading or writing to the file. Action: Check the session that is running. See the system error for more information. PMF_15019 Failed to open file <file name>. Cause: The file may be in use. Some other session that uses this file may be running. Action: Wait until the session completes. 378 Chapter 52: PMF Messages
- 395. Chapter 53 PR Messages This chapter contains information on the following topic: โฆ PR Messages, 380 Errors listed numerically. 379
- 396. 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. Cause: The listed Application Source Qualifier is connected to an imported PeopleSoft tree source definition and has an extract override. You cannot use extract overrides for imported tree sources. Action: During the session, the Integration Service ignores the extract override. If you want to perform an extract override on records connected to the Application Source Qualifier, connect the tree source definition to a different Application Source Qualifier. or Action: To keep this message from appearing again, remove the extract override from the session properties. PR_18003 Tree <tree name> with SetId <tree setid> and Effective Date <date> was not created. Cause: The listed tree does not exist in the PeopleSoft source system or has unexpected conditions. Action: Check the tree in the PeopleSoft source system for problems. If necessary, contact PeopleSoft technical support. or Cause: The listed tree has no ports connected to an Application Source Qualifier. Action: If you do not need the tree in the mapping, delete the tree source definition. Otherwise, connect the necessary ports to an Application Source Qualifier. PR_18004 Application Source Qualifier instance <Application Source Qualifier name> has more than one tree attached. Cause: The listed Application Source Qualifier is associated or connected to more than one imported PeopleSoft tree source definition. You can associate or connect only one imported tree source definition to a single Application Source Qualifier. Action: Disconnect one of the tree source definitions from the Application Source Qualifier. Or, remove one of the associated tree source definitions. or Action: To use more than one imported tree source in a single mapping, create an Application Source Qualifier for each imported tree source you want to use. Use a Joiner transformation to join two related tree sources. 380 Chapter 53: PR Messages
- 397. PR_18005 Tree may only be joined with Detail record: <PeopleSoft record name>. Cause: You connected or associated an imported tree and a record in an Application Source Qualifier, and the record is not the detail record for the tree. Action: You can connect or associate an imported tree with a non-detail record if the non-detail record is related to the detail record and you connect or associate the detail record with the Application Source Qualifier. or Action: You can connect the tree and non-detail record to separate Application Source Qualifiers and join them with a Joiner transformation. To determine which record provides detail data for a tree, open the tree source definition in the Mapping Designer and click the Attributes tab. PR_18006 Not all sources are related in Application Source Qualifier <Application Source Qualifier name>. Cause: You tried to connect or associate two unrelated sources in the listed Application Source Qualifier. You can only connect or associate related sources in an Application Source Qualifier. Action: Disconnect one of the unrelated sources. or Action: Remove one of the associated source definitions. PR_18007 Unknown error occurred in Application Source Qualifier <Application Source Qualifier name>. Cause: Internal error. Action: Contact Informatica Technical Support. PR_18009 Error in converting <string> to Date. Internal Error. Cause: Internal conversion error. Action: Contact Informatica Technical Support. PR_18010 Tree <tree name> was changed after session run was started. Cause: The listed tree changed in the PeopleSoft system after the Integration Service started the session. Action: The Integration Service completes the session with version of the tree as it was at the beginning of the session. If this is not the version you want, correct the session targets and run the session again. PR Messages 381
- 398. PR_18011 Application Source Qualifier <Application Source Qualifier name> has projected port with no inbound link. Cause: The listed Application Source Qualifier has a connected output port, and the corresponding input port is not connected. Action: Connect the necessary input port, or disconnect the connected output port. PR_18012 SQL Error <SQL statement>. Cause: Internal error. The Integration Service encountered an error in the listed SQL statement. Action: Contact Informatica Technical Support. PR_18013 Warning: Application Source Qualifier transformation <Application Source Qualifier name> has a larger number of sorted ports than projected output ports. Cause: In an Application Source Qualifier, the number of sorted ports option on the Properties tab has a higher value than the number of connected output ports. Action: Either lower the Number of Sorted Ports value or increase the number of connected output ports in the Application Source Qualifier. PR_18020 The language table <language table name>, for the base table <base table name>, does not have rows for the language <language code>. Cause: The application connection for the session specifies a PeopleSoft language code, and the source table listed in the error message does not have related data for the language you specified. When there is no data for the specified language, the Integration Service returns data from the base source table. Action: If you require data in the specified language, that data must be entered into the PeopleSoft system. If you want data in a different language, you can edit the application connection or create a new connection for a different language code. PR_18021 The Application Source Qualifier <Application Source Qualifier> has invalid user defined query <query> with character error at <number> location. Cause: You entered a query containing characters that are not valid in the source application connection code page. Action: Edit the query so all characters are valid in the source database connection code page. PR_18022 The Application Source Qualifier <Application Source Qualifier> has invalid filter clause <filter> with character error at <number> location. Cause: You entered a filter condition containing characters that are not valid in the application connection code page. 382 Chapter 53: PR Messages
- 399. Action: Edit the filter condition so all characters are valid in the application connection code page. PR_18023 The Application Source Qualifier <Application Source Qualifier> has invalid join and/or filter override <join override> with character error at <number> location. Cause: You entered a join condition and/or a source filter condition that contains characters that are not valid in the application connection code page. Action: Edit the join and/or filter conditions so all characters are valid in the application connection code page. 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.) Cause: You did not import PeopleSoft tree attributes into the created tree source definition. Action: Import tree attributes in the created tree source definition. You can import the tree attributes in either the source definition in the Mapping Designer or in the session properties. You must enter at least the PeopleSoft tree name and its effective date. PR_18027 Application Source Qualifier <Application Source Qualifier name>: Error in preparing the query for effective date data extraction. Cause: You have defined this Application Source Qualifier to extract current rows from an effective dated record that has no primary keys or PeopleSoft keys defined. Action: Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer. or Cause: You have specified an effective date join order in this Application Source Qualifier, and at least one of the effective dated records has no primary keys or PeopleSoft keys defined. Action: Either reimport and replace the PeopleSoft record or define a primary or PeopleSoft key in the Source Analyzer. PR_18028 Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract Join Order with invalid source names. Cause: In the Effective Date Join Order field, you typed a PeopleSoft record name that is not connected to the Application Source Qualifier. Action: Edit the Effective Date Join Order field so that each PeopleSoft record name is spelled correctly. The record names you enter in the Effective Date Join Order PR Messages 383
- 400. field must match the records associated with the Application Source Qualifier. Separate each record name with a comma. PR_18029 Application Source Qualifier <Application Source Qualifier name> has Effective Date Extract Join Order with invalid number of source names. This should be equal to the number of effective dated records in the DSQ. Cause: In the Effective Date Join Order field, you entered too few or too many PeopleSoft record names. Action: Edit the Effective Date Join Order field so the number of records you enter equals the number of records associated with the Application Source Qualifier. Verify that you separated each PeopleSoft record name with a comma. PR_18030 Application Source Qualifier <Application Source Qualifier name> cannot have Effective Date Extract Join Order when number of Effective Dated sources is one. Cause: You entered an effective date join order in the session properties, but there is only one effective dated record connected to the Application Source Qualifier. Action: Delete the text from the Effective Date Join Order field in the session properties. PR_18031 Application Source Qualifier <Application Source Qualifier name> has invalid Extract Date. Cause: You entered the Extract Date in the wrong date format. Action: Enter the Extract Date in the following format: MM/DD/YYYY HH24:MI:SS. 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. Cause: You entered a mapping parameter or variable for the Extract Date transformation option that does not exist in the mapping parameter file for the session. Action: Specify the correct mapping parameter file for the session. Make sure the parameter file contains a value for the mapping parameter or variable that you entered for the extract date. or Cause: You entered an invalid value in the parameter file for the extract date mapping parameter or variable. Action: Verify that the value you entered in the mapping parameter file for the extract date mapping parameter or variable is in the correct datatype format. Enter the value in Informatica default date format: MM/DD/YYYY HH24:MI:SS. 384 Chapter 53: PR Messages
- 401. 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. Cause: You entered a mapping parameter or variable for the PeopleSoft tree name that does not exist in the mapping parameter file for the session. Action: Specify the correct mapping parameter file for the session. Verify that the parameter file contains a value for the mapping parameter or variable that you entered for the PeopleSoft tree name. or Cause: You entered an invalid value in the parameter file for the PeopleSoft tree name mapping parameter or variable. Action: Verify that the value you entered in the mapping parameter file for the PeopleSoft tree name mapping parameter or variable is in the correct datatype format. PR_18034 Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, whose effective date through a mapping variable cannot be expanded or resolved correctly. Cause: You entered a mapping parameter or variable for the Effective Date option that does not exist in the mapping parameter file for the session. Action: Specify the correct mapping parameter file for the session. Verify that the parameter file contains a value for the mapping parameter or variable that you entered for the Effective Date option. or Cause: You entered an invalid value in the parameter file for the Effective Date option mapping parameter or variable. Action: Verify that the value you entered in the mapping parameter file for the Effective Date option mapping parameter or variable is in the correct datatype format. PR_18035 Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, whose Set Id through a mapping variable cannot be expanded or resolved correctly. Cause: You entered a mapping parameter or variable for the Set ID option that does not exist in the mapping parameter file for the session. Action: Specify the correct mapping parameter file for the session. Verify that the parameter file contains a value for the mapping parameter or variable that you entered for the Set ID option. or Cause: You entered an invalid value in the parameter file for the Set ID option mapping parameter or variable. PR Messages 385
- 402. Action: Verify that the value you entered in the mapping parameter file for the Set ID option mapping parameter or variable is in the correct datatype format. PR_18036 Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, whose Set Control Value through a mapping variable cannot be expanded or resolved correctly. Cause: You entered a mapping parameter or variable for the Set Control Value option that does not exist in the mapping parameter file for the session. Action: Specify the correct mapping parameter file for the session. Verify that the parameter file contains a value for the mapping parameter or variable that you entered for the Set Control Value option. or Cause: You entered an invalid value in the parameter file for the Set Control Value option mapping parameter or variable. Action: Verify that the value you entered in the mapping parameter file for the Set Control Value option mapping parameter or variable is in the correct datatype format. PR_18037 Application Source Qualifier <Application Source Qualifier name> has a tree instance <created tree source definition name>, with an invalid effective date. Cause: You entered an invalid value in the Effective Date option in the created tree source definition in the Mapping Designer or in the session properties. Action: Verify that the date you entered for the Effective Date is in the Informatica default date format: MM/DD/YYYY HH24:MI:SS. PR_18038 ERROR: One or more fields used to partition source(s) of Source Qualifier <Application Source Qualifier name> have been deleted. Please edit and save the session to correct the partitioning information. Cause: You defined a partition key for a port in the Application Source Qualifier that you deleted. Action: Edit the session to remove the partition key from the Application Source Qualifier. Then save the new partition information in the session and run it again. PR_18040 Application Source Qualifier <Application Source Qualifier name>: Error! The TO_EFFDT field cannot be projected if there is no primary or PeopleSoft key in the source. Cause: You have defined this Application Source Qualifier to connect a TO_EFFDT field from a source that has no primary keys or PeopleSoft keys defined. Action: Disconnect the link between the TO_EFFDT field in the source and the Application Source Qualifier. 386 Chapter 53: PR Messages
- 403. Chapter 54 REGEX Messages This chapter includes the following topic: โฆ REGEX Messages, 388 Error messages listed numerically. 387
- 404. REGEX Messages REGEX_34010 Failed to validate the subject. Cause: The Integration Service could not validate the value for the subject argument, because there was a perl compatible regular expression syntax error. There might not be enough system memory. Or, the value of the subject argument may contain invalid syntax. Action: Verify that the system contains enough memory. or Action: Verify the syntax of the expression. Use perl compatible regular expression syntax. REGEX_34011 Failed to extract the sub-pattern. Cause: The Integration Service could not extract the subpattern, because there was a perl compatible regular expression syntax error. There might not be enough system memory. Or, the subpattern may contain invalid syntax. Action: Verify that the system contains enough memory. or Action: Verify the syntax of the expression. Use perl compatible regular expression syntax. 388 Chapter 54: REGEX Messages
- 405. Chapter 55 REP Messages This chapter includes the following topic: โฆ REP Messages, 390 Error messages listed numerically. 389
- 406. REP Messages REP_12001 Failed to log onto database server. Cause: The Integration Service failed to connect to the database server. You may have logged in incorrectly. Action: Log in with the correct information. User names and passwords may be case- sensitive. 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. Cause: The Integration Service cannot locate a necessary SQL script file. Action: In the win.ini file, make sure the HOME entry in the Informatica PowerMart entry points to the directory where the SQL script is located. If the HOME entry is correct, contact Informatica Technical Support. REP_12014 An error occurred while accessing the repository. Cause: The Repository Service encountered an error while accessing the repository. Action: Check preceding messages to see the cause of the error. This error message may be preceded by REP_51056. 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]. Cause: The Service Manager was unable to connect to a local repository from the global repository. Action: Verify that the local repository is registered with the global repository. Also, verify that the Repository Services for both repositories are running. In addition verify that the connectivity information for the local repository is up to date. REP_12022 Failed to connect to global repository [global repository name] in domain [PowerCenter domain of global repository] from local repository [local repository name] in [PowerCenter domain of local repository]. Cause: The Service Manager was unable to connect to the global repository from a local repository. Action: Verify that the local repository is registered with the global repository. Also, verify that the Repository Services for both repositories are running. In addition, verify that the connectivity information for the global repository is up to date. 390 Chapter 55: REP Messages
- 407. REP_12033 The repository being accessed is incompatible with this version... Cause: The repository version does not match the client and/or server version. Action: If the repository is older, upgrade the repository. If the software is older, upgrade the software. REP_12119 A repository does not exist at the specified database connection. Cause: The Integration Service failed to connect to the database. You may have logged in incorrectly. Action: Log in with the correct information. User names and passwords may be case sensitive. or Cause: You do not have the appropriate database privilege to view repository tables. Action: Have the database administrator review your database privileges. REP_12122 Unable to unlock this folder. Please try again. Cause: This is a database error. Action: Check the server event or error log for related database error messages. If necessary, consult the database manual for appropriate action. REP_12123 Unable to delete this folder. Please try again. Same as REP_12122. REP_12124 Unable to delete this folder. The folder is in use by another user. Cause: You tried to delete a folder while other users are logged in to the folder. Even if there are no users connected, the folder could contain residual locks. Action: Ask all users to close all client tools. Use the Repository Manager to view locks. If necessary, remove old locks. Then perform the operation again. Warning: Removing valid locks can cause repository inconsistencies. REP_12164 Domain-related error: [error description]. Cause: The Service Manager could not complete the requested operation. Action: Read the error description and make any necessary changes to the domain connectivity. For more information, look up the cause and action for the error code. REP_12225 The value entered is not valid for memory attributes. Cause: The value for the memory attribute is invalid. Action: Enter a valid value. The value must be a non-negative integer, a non-negative integer followed by KB, MB, or GB. Or, you can enter auto to allow the Integration Service to determine the value at run time. REP Messages 391
- 408. REP_12325 Internal error. No connection callback. Cause: Internal error. Action: Contact Informatica Technical Support. REP_12326 Error getting connection information for remote repository. Cause: The global repository is missing required configuration parameters to connect to another repository. Action: Connect to the registered repository and correct the configuration parameters. REP_12327 Internal error. Connection callback returned an error. Cause: Internal error. Action: Contact Informatica Technical Support. REP_12328 The repository at this location does not have the same name. Cause: Either the database connection or the repository name entered is incorrect. Action: The status bar displays the correct repository name. Correct the inaccurate information. or Cause: You tried to connect to a repository on the network, but there was a network failure during the connect process. Action: Verify that the PowerCenter Client and the repository are connected to the network. When you connect to the repository again, enter the host name and port number of the repository in the Connect to Repository dialog box. REP_12330 Failed to fetch repository information. Cause: This is a database error. Action: Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Technical Support. REP_12332 Error initializing repository object information. Cause: You are low or out of memory. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to your system. or Cause: This is a database error. Action: Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Technical Support. 392 Chapter 55: REP Messages
- 409. REP_12333 More than one GDR found. Cause: The Integration Service found inconsistent repository information. Action: Contact Informatica Technical Support. REP_12334 Repository name mismatch. Cause: A global repository and a repository registered with it have the same name. Action: Unregister the local repository. Copy it to another location with a new name, and then re-register the repository. REP_12335 The current repository is not a GDR. Cause: You tried a global repository operation, such as registering a repository, when you were not connected to a global repository. Action: If desired, promote the repository to a global repository. Warning: Once a repository becomes a global repository, you cannot change it to a local repository. REP_12336 This repository is already registered with the GDR <global repository name>. Cause: You tried to register a repository to a global repository that is registered with a different global repository. Action: If the repository should be registered with the new global repository, unregister the repository from the original global repository. Register with the new global repository. REP_12337 This is not a local repository. Cause: You tried to register a dependent repository with a global repository. Only independent repositories can be registered with a global repository. Action: If the repository should be registered with a new global repository, unregister the repository from the original global repository. Then register with the new global repository. REP_12338 A repository with this name has already been registered. Cause: You tried to register a local repository when a local repository of the same name exists in the global repository. Action: Unregister the repository. Copy the repository to another location with a new name, then re-register the repository. REP_12339 Internal error. Error allocating a new repository ID. Cause: Database error. Action: Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Technical Support. REP Messages 393
- 410. REP_12340 Error updating remote repository. Same as REP_12339. REP_12341 Error updating GDR. Same as REP_12339. REP_12342 The selected repository is not registered with the current Global Repository. Cause: You tried to unregister a repository that is not registered with the current global repository. Action: You can only unregister repositories registered with a global repository. REP_12346 Memory allocation failed. Cause: Insufficient memory allocation. Action: Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to your system. REP_12347 An error occurred while updating connection information in the repository. Cause: A database error occurred while updating connection information during repository registration or while editing connection information. Action: Check the Repository Service event or error log for a related database error message. If no database error is reported, contact Informatica Technical Support. REP_12352 The current user does not have the privilege to perform this operation. Cause: You tried to perform an operation without the appropriate privileges. Action: Have your database administrator review your privileges. REP_12355 The object <object name> has been modified since the time it was read. Cause: You tried to edit a repository object that has been modified and saved by another user since you opened the object. Action: Close the object and open it again to view the edited object. REP_12357 The object <object name> is already locked by <user name>. Do you want to reobtain the lock? Cause: You tried to edit an object that has been locked by your user name. Either someone used your user name and password to access this object, or the client shut down while you were working on the object. Action: If someone is using your user name and password, click No, then ask that person to close the object and log out. If the PowerCenter Client shut down while you were working on the object, and you are sure that no one else has the object open, click Yes. 394 Chapter 55: REP Messages
- 411. Warning: Choosing Yes when someone else is working on the object may cause permanent damage to your repository. REP_12361 The user <user name> does not exist in the repository <repository name>. Cause: You tried to connect to a local repository from a global repository, or vice versa, and the specified user name does not exist in that second repository. Action: Use a valid user name or ask the administrator to add your user name to the repository. REP_12362 The password for user <user name> is incorrect for repository <repository name>. Cause: You have a different password for your user name at two different repositories. You tried to connect from one repository to another, and the password used to connect to the first repository is not valid in the second repository. Action: To connect to the second repository you must disconnect from the original repository, then connect to the second repository with the proper user name and password combination. To prevent this error from recurring, change one of the passwords to match the other. 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. Cause: The database user starting the repository does not have permission to query the Teradata dictionary. The Repository Service needs to query the Teradata dictionary to verify whether the Teradata repository tables have the correct primary indexes. Action: After you upgrade a Teradata repository, verify you back it up and restore it before starting it. This causes the Repository Service to create new primary indexes for the repository tables. You must back up and restore a Teradata repository before you can start it. REP_12364 For Teradata upgrade process to be complete, please take a backup of the repository (repository_name), delete existing repository and restore from the backup file. Then start the repository. Cause: You upgraded the Teradata repository and tried to start it without backing it up and restoring it. Action: Back up the repository and restore it. This causes the Repository Service to create new primary indexes for the repository tables. You must back up and restore the repository before you can start it. REP Messages 395
- 412. 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. Use the Repository Manager to upgrade. Cause: The repository needs to be upgraded to the current version expected by the product. Action: Use the Administration Console to upgrade your repository. REP_12371 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A product upgrade is required. Cause: The repository has been upgraded to a newer version of the product. Action: Upgrade the PowerCenter Client, Repository Service, and the Integration Service to the newer version. 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. Cause: The repository has been upgraded to a newer version of the product. Action: Upgrade the PowerCenter Client, Repository Service, and the Integration Service to the newer version. 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. Cause: The repository needs to be upgraded to the current version expected by the product. Action: Use the Administration Console to upgrade your repository. REP_12381 Unable to perform the operation since an expected object was not found. Please check the repository. Cause: Internal error. Your repository may contain inconsistencies. Action: Contact Informatica Technical Support. REP_12382 Error while updating the object information in the repository. Either no row or more than one row was updated. Cause: Internal error. Your repository may contain inconsistencies. Action: Contact Informatica Technical Support. 396 Chapter 55: REP Messages
- 413. 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. Cause: A repository is not supported on the database type specified in the configuration file. Action: Check the Integration Service Setup and correct the database type of the repository. REP_12387 The attempt to get a <save/fetch> lock on the <object type> <object name> timed out due to the following conflicting lock: User <user name> on the computer <hostname> running the <application> obtained a <save/fetch> lock on the <object type> <object name> at <time>. Please try again. Cause: You tried to access or save a repository object, and the repository could not create the necessary fetch or save lock to allow you to perform your task. This occurred because another user has the object locked. Action: Try again the operation again. If the problem persists, use the information provided to determine if the listed user is accessing the object. If you can verify the object is not being used or accessed, ask the administrator to unlock the object as necessary. REP_12389 Unable to set database connection property <number>. Cause: A database error prevented the repository connection from setting required database connection parameters. Action: Make sure the repository database server is up and running. If there is no problem in the database, try connecting to the repository again. If the problem persists, contact Informatica Technical Support. REP_12390 Mapping <mapping name> contains a dependency that points to a non existent port. The mapping is assumed to be invalid. Cause: You started a session that uses a mapplet, and information about the mapping is inconsistent in the repository. Action: Open the mapping in the Designer, validate the mapping and save it again. If the problem persists, the inconsistency is in the mapplet used by the mapping. Open the mapplet, validate, and save it. Then validate and save the mapping again. REP_12392 GID creation failed for repository <repository name>. Cause: Internal error. This might be caused by hardware failure. Action: Contact Informatica Technical Support. REP_12403 Unable to retrieve locale information. Cause: The repository cannot find or read the pmlocale.bin file. REP Messages 397
- 414. Action: Make sure that the pmlocale.bin file is in the installation directory and has not been corrupted by a disk failure. REP_12404 Failed to allocate new IDs for internal sequence generator: <sequence name>. Cause: A repository database error occurred causing the internal ID generation to fail. Action: If a repository database error occurred, try again after correcting the database problem. or Cause: The repository has inconsistent data. Action: Contact Informatica Technical Support. REP_12405 Failed to fetch new IDs. Same as REP_12404. REP_12415 Error comparing last saved times for objects in this folder! Cause: The repository database server could not provide the time or is not running properly. A previous problem with the database might have caused some data inconsistencies. Action: Try the operation again. Check the database server log for a possible cause to the problem. If there is no database error, contact Informatica Technical Support. REP_12416 Error comparing deployed times for shared folders! Same as REP_12415. REP_12422 Unable to connect to GDR! Cause: The database hosting the global repository (GDR) is not available or the connectivity information for the global repository is incorrect. Action: Verify that the connectivity information is the same on all client systems. If the connection is a secondary connection, make sure the connectivity information for the global repository did not change after the local repository was registered. If you moved the global repository to a different Repository Service, or edited the configuration information for the global repository, the connectivity information may have changed. To update the connectivity information in the repository domain, propagate the connectivity information for the global repository to the local repository. REP_12449 Internal error. Cause: Internal error. Action: Contact Informatica Technical Support. 398 Chapter 55: REP Messages
- 415. REP_12450 Unable to create output file <file name>. Cause: You tried to back up the repository and the Repository Manager could not create the backup file. The hard disk may be full or damaged. Action: Make sure there is enough disk space and there is no problem with the hard disk. REP_12452 Failed to write to file <file name>! Cause: You tried to back up the repository and the Administration Console could not write to the backup file. The hard disk may be full or damaged. Action: Make sure enough disk space exists and there is no problem with the hard disk. REP_12454 Unable to open input file <file name>! Cause: You tried to restore the repository and the Repository Service could not read from the backup file. The backup file might be corrupt or the hard disk might have bad sectors. Action: Check the hard disk for possible problems. You might have to restore the backup file from an older backup. Contact Informatica Technical Support for help. REP_12456 Failed to read from file <file name>! Same as REP_12454. REP_12457 Unexpected data in file <file name>! Cause: The repository backup file has data inconsistencies. Action: Check the hard disk for possible problems. You might have to restore the backup files from an older backup. Contact Informatica Technical Support for help. REP_12466 Error inserting repository object information. Cause: A repository database error caused the repository creation or upgrade to fail. Action: Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Technical Support. REP_12467 Error inserting repository object attribute information. Cause: A repository database error caused the repository creation or upgrade to fail. Action: Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Technical Support. REP_12468 Error inserting server locale information. Same as REP_12467. REP Messages 399
- 416. REP_12469 Error initializing object tree. Cause: A repository was not created, upgraded, or restored correctly. If the problem occurs in a repository that is in use, the database may have inconsistencies. Action: Contact Informatica Technical Support. REP_12470 Error updating repository information. Same as REP_12467. REP_12471 Error creating first user. Cause: A repository database error caused the repository creation to fail. Action: Try to create the repository again after fixing the database error. If the problem persists contact Informatica Technical Support. REP_12477 This repository contains folders which are currently in use. A repository cannot be deleted while it is in use. Cause: You tried to delete a repository while other users are logged in to the repository. Even if there are no users connected, the repository could contain residual locks. Action: Ask all users to close all client tools. Use the Repository Manager to view locks. If necessary, remove old locks. Then perform the operation again. Warning: Removing valid locks can cause repository inconsistencies. REP_12488 Unable to add new internal sequence generator. Same as REP_12467. REP_12492 This repository contains folders which are currently in use. A repository cannot be upgraded while folders are in use. Cause: You tried to upgrade a repository when other users are logged in to the repository. If there are no users connected, the repository might contain residual locks. Action: Ask all users to close all client tools. Use the Repository Manager to view locks. If necessary, remove old locks. Then perform the operation again. Warning: Removing valid locks can cause repository inconsistencies. REP_12494 The Repository is newer than the version supported by this software release. Unable to do an upgrade. Cause: The product version is older than the repository version. Action: Release all old locks in the repository. Upgrade the PowerCenter Client to the latest version, then upgrade the repository. 400 Chapter 55: REP Messages
- 417. REP_12496 This repository is too old to be upgraded. Cause: You tried to upgrade a repository with a newer release of the Repository Manager that does not support upgrading that repository version. Action: Contact Informatica Technical Support. REP_12505 Error while executing script file <file name>. Cause: A database error or a problem occurred in the script. Action: Correct the database error and try the operation again. If there is no database error, contact Informatica Technical Support. REP_12581 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance. Cause: The script file cannot be found in the PowerCenter Client installation directory or the file is corrupt. Action: Install the PowerCenter Client again to get the correct scripts. If the problem persists, contact Informatica Technical Support. REP_12589 Error occurred in locking. Cause: An internal error occurred due to a database error or inconsistent data in the repository. This error might be accompanied by a more descriptive error message or a database error message. Action: Abort the operation and try again. If the problem persists and there is no database error, contact Informatica Technical Support. REP_12590 Error updating <repository name> in GDR. Cause: A database error occurred while registering or unregistering a repository. Action: If a database error occurred, correct the database error and try again. Otherwise, contact Informatica Technical Support. REP_12591 Error updating <repository name> in GDR (Repository may be left in inconsistent state). Cause: A repository database error occurred when you tried to register or unregister a repository. Action: If a repository database error occurred, correct the database error and try again. If the operation succeeds then the inconsistency in the repository will have been corrected. Otherwise, contact Informatica Technical Support. REP_12651 Memory allocation failed. Cause: The Integration Service machine is out of memory. Action: Increase virtual memory or close other applications. REP Messages 401
- 418. REP_12654 Password is too long. Cause: You entered a password that exceeded the limit of 76 characters. Action: Use a shorter password. REP_12678 The connection to Global DataMart Repository is unavailable for some reason. Cause: The global repository connection failed while trying to fetch a shortcut. The connection information for the global repository might have changed or the repository database server is down. Action: Check the database error message for more information and correct the problem. Update connection information in the administration console if it has changed. REP_12708 Unable to allocate memory. Cause: The Integration Service machine is out of memory. Action: Increase virtual memory or close other applications. REP_12709 Unable to find database type for this source. Cause: Internal error. Action: Contact Informatica Technical Support. 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). Cause: Validation error. The code page of the source database connection is not a subset of the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode. Action: If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions: โ Choose a different source database connection for the session. โ Choose a different Integration Service to run the workflow. โ Correct the code page configured for the source database connection. โ Correct the code page registered for the Integration Service. REP_12735 The source file <file name> and Integration Service <Integration Service name> do not have compatible code pages. (One way compatibility is required.) Cause: Validation error. The code page of the source file is not a subset of the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode. 402 Chapter 55: REP Messages
- 419. Action: If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions: โ Choose a different source file and code page for the session. โ Choose a different Integration Service to run the workflow. โ Correct the code page registered for the Integration Service. REP_12736 The database <database name> and Integration Service <Integration Service name> do not have compatible code pages. Cause: Validation error. The session contains a Lookup or Stored Procedure transformation and the code page for the lookup or stored procedure database is not compatible with the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode. Action: If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions: โ Choose a different Integration Service to run the workflow. โ Correct the configured code page for the database in the Workflow Manager. โ Choose a different lookup or stored procedure database in the session properties. โ Correct the code page registered for the Integration Service. REP_12773 The Global Repository code page (<code page name>) is not compatible with the selected code page (<code page name>). Cause: While upgrading a local repository, the local repository code page must be a superset of the global repository code page. Action: Choose an appropriate code page. REP_12782 The repository <repository name>'s code page <code page name> and <PowerCenter Client>'s code page <code page name> are incompatible. Cause: The PowerCenter Client code page is not compatible with the code page of the repository to which you are trying to connect. The PowerCenter Client and repository code pages must be compatible. Their code pages must also be compatible with the Integration Service code page. Action: Change the code page for the PowerCenter Client to one that is compatible with the repository code page. Or, if you need to change the repository code page, you can copy the repository to a new location or backup and restore it. Both actions allow you to configure a different code page for the repository. REP Messages 403
- 420. REP_12934 Failed to fetch information for user <repository user name>. Cause: This is a database error. Action: Read the accompanying database error message for more details. or Cause: The computer running the PowerCenter Client is out of memory. Action: Close other applications. REP_12950 Lookup Transformation <transformation name> has INVALID lookup condition: Lookup Table Column <column name> and Transformation Port <port name> are the same. Cause: You entered an incorrect expression value for the lookup condition in the XML file. The lookup table column is the same as the transformation port. Action: Edit the XML file and make sure the lookup table column is different from the transformation port. Or, export the object again and then import it. REP_12951 The lookup condition is not valid: Lookup Table Column <column name> and Transformation Port <port name> are the same. Transformation is not valid. Cause: You entered an incorrect expression value for the lookup condition in the XML file. The lookup table column is the same as the transformation port. Action: Edit the XML file and make sure the lookup table column is different from the transformation port. Or, export the object again and then import it. REP_12952 Joiner Transformation <transformation name> has INVALID joiner condition: Master <port name> and Detail <port name> are the same. Cause: You entered an incorrect expression value for the join condition in the XML file. The master port is the same as the detail port. Action: Edit the XML file and make sure the master port is different from the detail port. Or, export the object again and then import it. REP_12953 The joiner condition is not valid: Master <port name> and Detail <port name> are the same. Transformation is not valid. Cause: You entered an incorrect expression value for the join condition. The master port is the same as the detail port. Action: Edit the XML file and make sure the master port is different from the detail port. Or, export the object again and then import it. REP_12954 Warning: The Call Text attribute of Stored Procedure transformation <transformation name> has non-empty value when the Stored Procedure Type attribute is set to Normal. Cause: The call text attribute for the stored procedure contains a value when you defined the stored procedure type attribute as Normal in the XML file. 404 Chapter 55: REP Messages
- 421. Action: Edit the XML file and make sure the call text attribute value is empty when you define the stored procedure type attribute as Normal. Or, export the object again and then import it. REP_12955 Warning: The Call Text attribute of Stored Procedure transformation has non- empty value when attribute Store Procedure Type is set to Normal. Cause: The call text attribute contains a value when you defined the stored procedure type attribute as Normal in the XML file. Action: Edit the XML file and make sure the call text attribute value is empty when you define the stored procedure type attribute as Normal. Or, export the object again and then import it. REP_12975 There is no existing MQ Connection to choose for <connection string> in the target repository. Cause: This is an informational message. You tried to copy an MQSeries session to a target repository that has no defined queue connections. Action: Create at least one queue connection in the target repository. REP_12991 Failed to connect to <repository name> Repository Agent on host <host name> (port number: <port number>). System error message: <error message>. Cause: A repository client application could not connect to a Repository Agent process. The Repository Agent host name or port number may be incorrect. Action: Verify that the host name and port number specified in the repository client connection information is the same as the information specified in the Repository Agent configuration. REP_12994 Server system error (errno = <error number>): <system error message>. Cause: An error occurred on the Repository Service system. Action: For Repository Service on Windows, check the system event log for related error messages. See Windows help and look up the specified system error number. or Action: For Repository Service on UNIX, locate the error in the /usr/include/sys/ errno.h file. Check the UNIX documentation for explanation of the error. REP_12995 Failed to shutdown Integration Service. Cause: The server would not shut down. Action: Check preceding messages to see the cause of the error. REP_12996 No key is selected for Sorter transformation <transformation name>. Cause: You did not configure a sort key for the Sorter transformation. REP Messages 405
- 422. Action: Edit the Sorter transformation and select one or more ports to use as a sort key. REP_12999 No key is selected for Sorter transformation. This transformation is not valid. Cause: You did not configure a sort key for the Sorter transformation. Action: Edit the Sorter transformation and select one or more ports to use as a sort key. REP_22674 Custom Transformation <transformation name> has non-ASCII character(s) in its class name. Cause: The Custom transformation class name contains non 7-bit ASCII characters. Action: Edit the transformation properties and enter 7-bit ASCII characters for the class name. REP_32000 Error: Could not find DSQ instance <Source Qualifier transformation> for <source>. Cause: The Source Qualifier transformation associated with the source is missing in the XML file. Action: Edit the XML file and verify that it has a valid entry for the Source Qualifier transformation. Or, export the object again and then import it. REP_32001 Error: Source Reference: <source> DBD: <source> for DSQ <Source Qualifier transformation> not found. Cause: The source associated with a specified Source Qualifier transformation is missing in the XML file. Action: Edit the XML file and verify it has a valid source for the specified Source Qualifier transformation. Or, export the object again and then import it. REP_32002 Error: There are more than one groups with the order: <number> in <group>. Cause: The XML file specifies more than one group with the same order for that particular source, target, or transformation. Action: Check the ORDER entry under the GROUP node for that specified source, target, or transformation in the XML file. Or, export the object again and then import it. REP_32003 Error: Field order does not match group order. Cause: The field order does not match the group order in the XML file. Action: Edit the XML file and make sure the field order matches the group order. Or, export the object again and then import it. 406 Chapter 55: REP Messages
- 423. REP_32004 Error: Invalid Transformation type <type> for transformation <transformation name>. Cause: In the XML file, you defined the TYPE Attribute in the TRANSFORMATION element as an incorrect value. Action: Edit the XML file and enter a legal transformation type for the attribute TYPE. Or, export the object again and then import it. REP_32007 Folder referenced by the shortcut object does not exist, object will be created in the current folder. Cause: The shortcut to an object does not contain folder information. You might have renamed or deleted the folder. Action: Restore the folder in the target repository. Otherwise the object is imported as the actual object the shortcut references, as defined by the metadata in the XML file, under the current folder. REP_32010 Error: Object referenced by shortcut: <shortcut>. Referring to <object> in Repository: <repository name>. Folder: <folder name> not found. Cause: You deleted or renamed a folder that contains a shortcut in the specified repository. Action: Restore the folder or re-create the shortcut to the object in the folder. REP_32011 Internal Error: Could not copy object. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32013 Error encountered while Parsing file. Cause: The XML file from which you tried to import is invalid or does not follow the powrmart.dtd file. Action: Edit the XML file and make sure it is valid against the powrmart.dtd file. REP_32014 The DTD file name is not specified. Cause: The XML file does not contain the DTD file name. Action: Edit the XML file header with the DTD file name, powrmart.dtd. REP_32015 Code page in file: <file name> not compatible with repository code page: <code page>. Cause: The repository code page specified in the XML file is not compatible with the target repository code page. Action: Cannot import the XML file. Edit the XML file and make sure the code pages are compatible. REP Messages 407
- 424. REP_32016 Error: Invalid Database Type: <database type>. Cause: The database name in the XML file for that object is not supported or invalid. Action: Edit the XML file and verify the database type. Or, export the object again and then import it. REP_32018 Invalid Delimiters: <delimiter>. Cause: You defined invalid delimiters for a flat file source in the XML file. Action: Edit the XML file under the FLAT FILE node. Or, export the object again and then import it. REP_32019 Error: Invalid table attribute: <attribute>. Cause: You defined a table attribute type in the XML that is not supported. Action: Edit the XML file for that attribute. Or, export the object again and then import it. REP_32020 Warning: Could not link fields <field name>:<field name>:<field name>: Instance <instance> to Field: <field name> Instance <instance>. Cause: An invalid connector node exists for a mapping or mapplet in the XML file. Action: Fix the CONNECTOR node under the mapping or mapplet. Or, export the object again and then import it. REP_32021 Error: Invalid Key Type: <key type>. Cause: You defined a key type for a source object in the XML file that is not supported. Action: Edit the key type node in the XML file. Or, export the object again and then import it. REP_32022 Error: Invalid Group <group> for field <field name>. Cause: You defined a group in the XML file that does not exist for that table field. Action: Edit the group name in the XML file. Or, export the object again and then import it. REP_32023 Error: Cannot determine ODBC Data type for field <field name>. Cause: You defined an invalid ODBC type for a table field in the XML file. Action: Edit the XML file for the ODBC data type for that particular field. REP_32025 Error: Invalid Field Attribute: <attribute> found for field: <field>. Cause: You defined an invalid field attribute for a table field in the XML file. Action: Edit the XML file for that particular attribute. Or, export the object again and then import it. 408 Chapter 55: REP Messages
- 425. REP_32026 Error: Could not find field: <field> in Instance: <instance>. Cause: You specified a Foreign Key field name does not exist in the referenced source. Action: Edit the referenced field name in the XML file. Or, export the object again and then import it. REP_32027 Error: Could not Resolve Foreign key dependency For Field: <field> in Source: <source>. Cause: The DBD or source for a specified foreign key field name is missing in the XML file. Action: Edit the XML file. Or, export the object again and then import it. REP_32028 Error: This source cannot have groups. Cause: You defined a group node for a source that does not support groups in the XML file. Action: Edit the XML file and remove the group node. Or, export the object again and then import it. REP_32029 Error: could not add group <group>. Cause: Unable to add group information. Action: Check that the group exists in the XML file. Or, export the object again and then import it. REP_32030 Database Error: while Assigning Ids for Source: <source name>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32031 Error: Missing or Invalid TYPE attribute for Group: <group>. Cause: You defined a group type in the XML file that is missing or invalid. Action: Edit the group type node in the XML file. REP_32032 Error: Cannot import tables of type <TABLETYPE value>. Cause: You entered an invalid value for the TABLETYPE attribute in the TARGET element in the XML file. Action: Edit the XML file and enter NONE for the TABLETYPE attribute. Or, export the object again and then import it. REP_32033 Error: This target cannot have groups. Cause: You specified a target in the XML file that does not support groups. Action: Edit the XML file and remove the group node. Or, export the object again and then import it. REP Messages 409
- 426. REP_32034 Database Error: while Assigning Ids for Target: <target name>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32035 Error: Invalid Initialization Property: <INITPROP name>. Cause: You entered NO for the USERDEFINED attribute and entered an invalid value for the NAME attribute for the INITPROP element in the XML file. Action: If the INITPROP element represents a user-defined initialization property in the transformation, edit the XML file and enter YES for the USERDEFINED attribute. Otherwise, export the object again and then import it. REP_32036 Error: This transformation cannot have groups. Cause: In the XML file, you entered a GROUP element for a transformation that does not support groups. Action: Edit the XML file to remove the GROUP element from the transformation that does not support groups. Or, export the object again and then import it. REP_32037 Database Error: while Assigning Ids for Transformation: <transformation>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32038 Error: Invalid Datatype: <datatype> for field: <field name>. Cause: You entered an invalid datatype for the field in the XML file. Action: Edit the XML file to specify a supported datatype. Or, export the object again and then import it. REP_32039 Error: Missing ATTRIBUTE <XML attribute name> for field: <SOURCEFIELD name or TRANSFORMFIELD name>. Cause: The specified attribute is missing or empty in the specified element in the XML file. Action: Edit the XML file and enter the necessary attribute in the specified element or add a value for the specified attribute. Or, export the object again and then import it. REP_32040 Error: Could not find associated source field: <SOURCEFIELD name> for <Normalizer transformation>. Cause: In the XML file, the specified REF_SOURCEFIELD attribute in the TRANSFORMFIELD element in the specified Normalizer transformation does not match the name of a SOURCEFIELD element. Action: Edit the XML field and verify the REF_SOURCEFIELD attribute matches the name of a SOURCEFIELD element in the XML file. Or, export the object again and then import it. 410 Chapter 55: REP Messages
- 427. REP_32041 Error: Invalid Instance Type: <TYPE value>. Cause: You specified an invalid entry for the TYPE attribute in the INSTANCE element for a transformation. Action: Edit the XML file and enter a valid instance type for the TYPE attribute. Or, export the object again and then import it. REP_32042 Error: Invalid reference field <REF_FIELD name> for Transformation field: <TRANSFORMFIELD name>. Cause: In the XML file, a TRANSFORMFIELD element contains a value for the REF_FIELD attribute that does not match a SOURCEFIELD element. Action: Edit the XML file and verify the REF_FIELD attribute matches the name of the SOURCEFIELD element. Or, export the object again and then import it. REP_32043 Error: Missing attribute <MAPPLETGROUP> or <REF_FIELD> for Field: <mapplet name>. Cause: In the XML file, either the REF_FIELD or MAPPLETGROUP attribute is missing from a TRANSFORMFIELD element inside a TRANSFORMATION element for a mapplet. Action: Edit the XML file and enter the necessary attribute. Or, export the object again and then import it. REP_32044 Error: Missing attribute <REF_FIELD> for Field: <TRANSFORMFIELD name>. Cause: The specified TRANSFORMFIELD element in a Router transformation is missing a REF_FIELD attribute or contains a value for the REF_FIELD attribute that does not match a TRANSFORMFIELD element in the XML file. Action: Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the name of a TRANSFORMFIELD element. Or, export the object again and then import it. REP_32045 Error: Invalid reference field: <REF_FIELD> for Lookup Field: <TRANSFORMFIELD name> Transformation: <transformation name>. Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file. Action: Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, export the object again and then import it. or Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD REP Messages 411
- 428. attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name. Action: Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it. REP_32046 Error: Invalid reference field: <REF_FIELD> for Field: <TRANSFORMFIELD name> Transformation: <TRANSFORMATION name>. Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file. Action: Edit the XML file and enter a REF_FIELD attribute. Make sure the REF_FIELD attribute matches the spelling of the TRANSFORMFIELD element it references. Or, export the object again and then import it. or Cause: The specified TRANSFORMFIELD element in the specified Lookup transformation contains a value for the REF_FIELD attribute that does not match another TRANSFORMFIELD element. Either the REF_FIELD attribute references a TRANSFORMFIELD that does not exist, or the spelling does not match the TRANSFORMFIELD name. Action: Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it. REP_32047 Error: Invalid Mapplet Group <MAPPLETGROUP> for Field: <MAPPLETGROUP value> Transformation: <transformation name>. Cause: In the XML file, the MAPPLETGROUP attribute value does not match the name of the GROUP element for the mapplet. Action: Edit the XML file and verify the MAPPLETGROUP attribute matches the GROUP name for the mapplet. Or, export the object again and then import it. REP_32050 Error: Could not find Transformation definition for: <transformation or source or target name>. Cause: The TRANSFORMATION_NAME attribute in the INSTANCE element does not match a TRANSFORMATION element name in the XML file. Action: Edit the XML file and verify the TRANSFORMATION_NAME attribute matches a TRANSFORMATION element name. Or, export the object again and then import it. REP_32056 Error: Missing or Empty Attribute: <attribute name>. Cause: You did not enter the specified attribute in either a SOURCE, SOURCEFIELD, or TARGETFIELD element in the XML file. 412 Chapter 55: REP Messages
- 429. Action: Edit the XML file and enter the necessary attribute. Or, export the object again and then import it. REP_32057 Error: Populating default fields for MQ Source. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32058 Error: Populating default fields for MQ Target. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32060 Error: Could not get datatype description for field: <field name>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32063 Error: An Unknown target field attribute: <attribute ID> has been detected for Field: <field name>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32066 Error: Could not get group for source field: <source field>. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32072 Invalid date in schedule info. Cause: You defined an invalid date in the XML file for a session start and end time in the schedule information node. Action: Edit the XML file for the session. Or, export the object again and then import it. REP_32074 Failed to export SAPFUNCPARAM:<SAP Function Parameter>. Cause: Internal Error. This REP message is specific to sessions with SAP R/3 sources. Action: Contact Informatica Technical Support. REP_32079 Failed to export SAPVariable <SAP variable>. Cause: Internal Error. This REP message is specific to sessions with SAP R/3 sources. Action: Contact Informatica Technical Support. REP_32081 Invalid schedule info. Cause: You set invalid schedule information for the session in the XML file. REP Messages 413
- 430. Action: Edit the schedule information node in the XML file. Or, export the object again and then import it. REP_32087 Error: Unable to get mapping name. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32088 Error: Unable to fetch database connection. Cause: The database connection specified for the session in the XML file does not exist in the target repository. Action: Create a new database connection in the target repository with the name defined in the XML file, or select an existing database connection from the Workflow Manager. REP_32089 Error: Unable to fetch registered server information for the session. Cause: The Integration Service specified for the session in the XML file does not exist in the target repository. Action: Create an Integration Service in the target repository with the name specified in the XML file, or select an existing one using the Workflow Manager. REP_32090 Error: Unable to fetch session attributes. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32091 Error: Unable to fetch mapping DSQ related information. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32092 Error: Unable to fetch database connection: <database connection> associated with the data Source Qualifier transformation: <transformation name>. Cause: The database connection specified for the session in the XML file does not exist in the target repository. Action: Create a new database connection in the target repository with the name defined in the XML file, or select an existing database connection from the Workflow Manager. REP_32093 Error: Unable to fetch partitions for the session <session name>. Cause: Internal error. Action: Contact Informatica Technical Support. 414 Chapter 55: REP Messages
- 431. REP_32095 Error: Invalid Mapping Name for the session <session name>. Cause: You defined an invalid mapping name associated with the session in the XML file. Action: Edit the XML file for the mapping name attribute in the session. Or, export the object again and then import it. REP_32096 Error: Invalid FTP Name <FTP connection>. Cause: Unable to retrieve the connection object defined in the XML file for that session. Action: Create a new connection object or select an existing one using the Workflow Manager. REP_32097 Warning: FTP connection <FTP connection> not found. Session will be imported without reference to FTP connection. Cause: Unable to retrieve the connection object defined in the XML file for that session. Action: Create a new connection object or select an existing one using the Workflow Manager. REP_32098 Warning: Loader connection <external loader connection> not found. Session will be imported without reference to Loader connection. Cause: Unable to retrieve the connection object defined in the XML file for that session. Action: Create a new connection object or select an existing one using the Workflow Manager. REP_32101 Error: Internal Error encountered in initializing Parser. Cause: Internal error. Action: Contact Informatica Technical Support. REP_32103 Warning: Invalid Usage type: <type> for field: <field name>. Cause: You defined an invalid usage type description under the flat file node in the XML file. Action: Edit the XML file. Or, export the object again and then import it. REP_32105 Error: Invalid Codepage: <code page> for Flat File. Cause: You defined a code page for the flat file object in the XML file that is not compatible with the repository code page information. Action: Cannot import the source. REP Messages 415
- 432. REP_32111 Error: Invalid Database Type: <DATABASETYPE value> for source: <SOURCE name>. Cause: You entered an invalid database type in the DATABASETYPE attribute in the SOURCE element for the specified source. Action: Edit the XML file and correct the DATABASETYPE attribute in the SOURCE element. Or, export the object again and then import it. REP_32112 Error: Missing or Empty Name for: <element>. Cause: You did not enter a NAME attribute for the specified element. Action: Edit the XML file and add a NAME attribute in the specified element. Or, export the object again and then import it. REP_32113 Error: Invalid number of fields for transformation: <Sequence transformation name>. Cause: In the XML file, you included more than two TRANSFORMFIELD elements in the specified TRANSFORMATION element for a Sequence Generator transformation. Action: Edit the XML file and make sure the Sequence Generator transformation has exactly two TRANSFORMFIELD elements. Or, export the object again and then import it. REP_32115 Error: <object> <object name> cannot be imported as it is potentially unsafe. Importing any associated mapping/mapplet might result in an error. Cause: You created or modified an object in the XML file that cannot be created or modified. Action: Export the object again and then import it. REP_32116 Error: The mapping: <mapping name> is potentially unsafe and cannot be imported. Cause: In the XML file, you modified an object that contains a CRCVALUE code. The object is a part of the specified mapping. Action: Export the object again and then import it. REP_32117 Error: <transformation type> <transformation name> is potentially unsafe and will not be available for import. Cause: In the XML file, you modified either a source, target, or transformation that contains a CRCVALUE code. Action: Export the object again and then import it. REP_32118 Error: Invalid Usage Flags: <flag>. Cause: You specified an invalid usage flag in the XML file. Action: Edit the XML file. Or, export the object again and then import it. 416 Chapter 55: REP Messages
- 433. REP_32121 Warning: Removing instance <instance name>. Could not find source instance for this Source Qualifier transformation instance. Cause: You defined a Source Qualifier transformation in the XML file that is not associated with a source. Action: Edit the XML file. Or, export the object again and then import it. REP_32122 Error: Transformation <transformation name> has an invalid reusable setting. Cause: You defined a non-reusable transformation as reusable in the XML file. Action: Edit the XML file. Or, export the object again and then import it. REP_32123 Error: Rank transformation <transformation name> has an invalid first field name. It has to be RANKINDEX. Cause: You deleted or renamed the first field for the Rank transformation in the XML file. Action: Edit the XML file and make sure the first field name for the Rank transformation is RANKINDEX. Or, export the object again and then import it. REP_32124 Field <field name> has missing or invalid expression type. Cause: You did not define an expression type for the transformation in the XML file, or you defined an invalid expression type. Action: Edit the XML file and define a valid expression type for the transformation. Or, export the object again and then import it. REP_32131 Error: Rank transformation <transformation name> has no RANK PORT. This transformation is invalid. Cause: You did not define a Rank port type for the Rank transformation in the XML file. Action: Edit the XML file and make sure there is only one field which has the port type as Rank. Or, export the object again and then import it. REP_32132 Error: Transformation <transformation name> has duplicate group <group name> due to the same group order. Cause: You defined duplicated groups in the group order in the XML file. Action: Edit the XML file and make sure the group order has different groups. Or, export the object again and then import it. REP_32135 Error: Invalid precision: <number> specified for field: <field name>. The maximum precision is 65535. Cause: You defined the field precision in the XML file greater than the maximum of 65,535. REP Messages 417
- 434. Action: Edit the XML file and make sure the precision is less than or equal to the maximum precision, which is 65,535. REP_32136 Error: Invalid scale: <number> specified for field: <field name>. The scale cannot be greater than the precision or the maximum scale which is 65535. Cause: You defined the scale for a field in the XML file with an invalid number. The scale is either greater than the corresponding precision or greater than the maximum scale allowed, which is 65,535. Action: Edit the XML file and make sure the scale for the field is less than or equal to the precision for the field. 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. Cause: In the XML file, you defined the dynamic lookup cache attribute to YES, but you did not define the first lookup port as NewLookupRow. Action: When the dynamic lookup cache attribute is set to YES, the first field has to be NewLookupRow. Edit the XML file, or export the object again and then import it. REP_32138 Field <field name> for lookup transformation <transformation name> cannot be a Dynamic Lookup field when dynamic lookup cache is disabled. Transformation is not valid. Cause: In the XML file, you defined a lookup port as NewLookupRow, but you defined the dynamic lookup cache as NO. Action: You cannot have the NewLookupRow when the dynamic lookup cache attribute is set to NO. Edit the XML file, or export the object again and then import it. REP_32139 In Lookup transformation <transformation name>, the content(s) of the generated Dynamic Lookup field <field name> has been changed. Transformation is not valid. Cause: You modified the definition of the NewLookupRow port in the XML file. Action: Do not change the NewLookupRow port in the XML file. Export the object again and then import it. REP_32140 In Rank transformation <transformation name>, the content(s) of the RANKINDEX field <field name> has been changed. Transformation is not valid. Cause: You modified the contents of the RANKINDEX field in the Rank transformation in the XML file. Action: Do not modify the RANKINDEX field in the XML file. Export the object again and then import it. 418 Chapter 55: REP Messages
- 435. REP_32141 In Sequence Generator transformation <transformation name>, the content(s) of field <field name> has been changed. Transformation is not valid. Cause: You modified the definitions of the NEXTVAL and CURRVAL fields in the Sequence Generator transformation in the XML file. Action: Do not modify these fields in the XML file. Export the object again and then import it. REP_32144 Error: Missing or invalid attribute <attribute name> for <element name>: <attribute value>. Cause: In the XML file, you entered an invalid value or no value for the specified attribute in the specified element. Action: Edit the XML file and define a valid value for the specified attribute. Or, export the object again and then import it. REP_32148 Error: Invalid datatype for mapping variable <MAPPINGVARIABLE name>. Cause: You entered an invalid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element in the XML file. Action: Edit the XML file and define a valid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element. Or, export the object again and then import it. REP_32149 Error: Invalid datatype for aggregate COUNT for mapping variable <MAPPINGVARIABLE name>. Cause: In the XML file, you specified COUNT for the AGGFUNCTION attribute, and you entered an invalid value for the DATATYPE attribute for the specified MAPPINGVARIABLE element. Action: Edit the XML file and enter either LONG or SHORT for the DATATYPE attribute for the MAPPINGVARIABLE element. Or, export the object again and then import it. REP_32150 Error: Invalid aggregate type for mapping variable <MAPPINGVARIABLE name>. Cause: In the XML file, you specified NO for the ISPARAM attribute, and you entered an invalid value for the AGGFUNCTION attribute for the specified MAPPINGVARIABLE element. Action: Edit the XML file and enter COUNT, MIN, or MAX for the AGGFUNCTION attribute for the MAPPINGVARIABLE element. Or, export the object again and then import it. REP Messages 419
- 436. REP_32151 Error: No name for the imported mapping variable. Cause: In the XML file, the NAME attribute is missing from the MAPPINGVARIABLE element. Action: Edit the XML file and add a NAME attribute to the MAPPINGVARIABLE element. Or, export the object again and then import it. REP_32167 Error: Duplicate instances of type: <instance type> name: <instance name>. Cause: In the XML file, you defined two instances of the same type with the same instance name. Action: Edit the XML file and rename one of the transformation instance names. Also, rename any references to it in the mapping or mapplet. Import the object again. REP_32171 The mapping originally assigned to this session has been changed. Cannot import the session. Cause: You copied a mapping to a repository, but the mapping was modified, deleted or renamed. Action: Copy or import the original mapping to the target repository again. REP_32173 Error: Expected unsigned value for attribute: <attribute value>, found value: <value>. Cause: You provided a negative or invalid value for an unsigned number in the XML file. Action: Correct the value in the XML file. Or, export the object again and then import it. REP_32174 Error: Invalid value: <value>, expecting unsigned value for attribute: <attribute>, for <element>: <element name>. Cause: You provided a negative or invalid value for an unsigned number in the XML file. Action: Edit the XML file and define a valid value for the attribute OCCURS. Or, export the object again and then import it. REP_32175 Error: Invalid target database type: <target database name> for target: <target name>. Cause: You defined an invalid database type in the XML file, or the database type is not valid for a target. Action: Edit the XML file and define the correct database type for the DATABASETYPE attribute in the TARGET element. Or, export the object again and then import it. 420 Chapter 55: REP Messages
- 437. REP_32176 Two or more fields in the xml data Source Qualifier transformation: <Source Qualifier transformation> refer to the same field: <field name> in the source. Cause: In the XML file, you defined two transformation fields for the XML Source Qualifier transformation with the same value for the REF_SOURCEFIELD attribute. Action: Edit the XML file and provide the correct value. Or, export the object again and then import it. REP_32177 Error: Invalid database type '<database type>' for target '<target name>'. ...A plugin required to handle this is missing. ...This target will not be available for import. Cause: In the XML file, you defined a plugin database type for the target, but you did not register the plugin in the PowerCenter Client. Action: Register the plugin the PowerCenter Client before importing the file. Or, edit the XML file and specify an existing database type. REP_32178 Error: Invalid Database Type: <database type> for target: <target name>, or the Database Type is not installed in this repository. Cause: In the XML file, you defined a plugin database type for the target, but you did not install the plugin in the repository. Action: Install the plugin in the repository before importing the file. Or, edit the XML file and specify an existing database type. REP_32180 Error: Invalid Task type <task type> for task <task name>. Cause: In the XML file, you specified an invalid TYPE attribute for the TASK element. Action: Edit the XML file, and specify a valid TYPE for the TASK. Or, export the object again and then import it. REP_32181 Error: Invalid Extension type: <session extension type> for element <SESSIONEXTENSION element>. Cause: In the XML file, you specified an invalid TYPE attribute for the SESSIONEXTENSION element. Action: Edit the XML file, and specify a valid TYPE for the SESSIONEXTENSION. Or, export the object again and then import it. REP_32185 Error: The mapping <mapping name> associated with the session <session name> is invalid. Cause: In the XML file, you specified a mapping that is invalid. Action: In the Designer, validate the mapping before importing the session. Or, choose a different valid mapping for the session. REP Messages 421
- 438. REP_32186 Error: expected a timer for task <Timer task name>. Cause: In the XML file, you did not specify a TIMER element for the Timer TASK. Action: Export the object again and then import it. REP_32188 Error: The mapping <mapping name> for session <session name> is not found in the target repository. Cause: The XML file references a mapping that does not exist in the repository. Action: Create a valid mapping in the Designer before importing, or choose a different mapping for the session. REP_32190 Warning: session transformation instance <session transformation instance name> of type <transformation type> is not found for element <SESSIONEXTENSION>. Cause: In the XML file, the type of the SESSIONEXTENSION element does not match a SESSTRANSFORMATIONINST element. Action: Edit the XML file, and verify the type of the SESSIONEXTENSION element matches a SESSTRANSFORMATIONINST element. Or, export the object again and then import it. REP_32191 Warning: missing or empty attribute <attribute name> for element <element name>. Cause: The XML file contains an empty or missing attribute. Action: Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it. REP_32192 Error: Invalid Component Type <session component type> for element <SESSIONCOMPONENT name>. Cause: In the XML file, you specified an invalid TYPE attribute for the SESSIONCOMPONENT element. Action: Edit the XML file, and specify a valid TYPE attribute for the SESSIONCOMPONENT element. Or, export the object again and then import it. REP_32193 Error: missing or empty attribute <attribute name> for element <element name>. Cause: The XML file contains an empty attribute, or the attribute is missing. Action: Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it. 422 Chapter 55: REP Messages
- 439. REP_32194 Error: Invalid partition type <PARTITIONTYPE name> for session transformation <SESSTRANSFORMATIONINST name>. Cause: In the XML file, you specified an invalid PARTITIONTYPE attribute for the SESSTRANSFORMATIONINST element. Action: Edit the XML file, and specify a valid PARTITIONTYPE. Or, export the object again and then import it. REP_32195 Error: extension subType <SESSIONEXTENSION subtype> for extension type <SESSIONEXTENSION type> is invalid for element <SESSIONEXTENSION name>. Cause: In the XML file, you specified an invalid SUBTYPE attribute for the SESSIONEXTENSION element with the specified TYPE attribute. The SUBTYPE attribute must be compatible with the TYPE attribute. Action: Edit the XML file, and specify a valid SUBTYPE. Or, export the object again and then import it. REP_32196 Error: connection reference <connection reference> with connection number <number> is not found for element <SESSIONEXTENSION name> due to the following error: Cause: In the SESSIONEXTENSION element, the referenced CONNECTIONREFERENCE element does not exist. Action: Edit the XML file, and specify a valid CONNECTIONREFERENCE. Or, export the object again and then import it. REP_32198 Error: Invalid connection type <connection type> for connection reference <connection reference>. Cause: In the XML file, you specified an invalid CONNECTIONTYPE attribute for the CONNECTIONREFERENCE element. Action: Edit the XML file, and specify a valid CONNECTIONTYPE attribute. Or, export the object again and then import it. REP_32199 Error: Invalid partition name <partition name> for element <element name>. Cause: In the XML file, you specified an invalid PARTITIONNAME attribute for the specified element. Action: Edit the XML file, and specify a valid PARTITIONNAME attribute. Or, export the object again and then import it. REP_32202 Error: Invalid DSQ instance name < Source Qualifier transformation name> for session transformation instance <session transformation instance name>. Cause: In the XML file, you specified a DSQINSTNAME attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element. REP Messages 423
- 440. Action: Edit the XML file, and verify the DSQINSTNAME attribute matches the SESSTRANSFORMATIONINST element name. Or, export the object again and then import it. REP_32203 Error: the number of partition <PARTITION name> is out of range [1-32] for session transformation <SESSTRANSFORMATIONINST name> in session <session name>. Cause: The number of PARTITIONs under SESSTRANSFORMATIONINST is invalid. Action: Remove, as appropriate, the PARTITIONs from under the SESSTRANSFORMATIONINST so that the number of PARTITIONs is less than or equal to 32. REP_32204 Error: building session <session name>. Cause: The SESSION element or some of its sub-elements are invalid. Action: View the Output window for more information. Export the object again and then import it. REP_32205 Error: Invalid DSQ <Source Qualifier transformation> of type <DSQINSTTYPE> for the extension in session transformation instance <SESSTRANSFORMATIONINST name>. Cause: In the XML file, you specified a DSQINSTNAME and DSQINSTTYPE attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element or a SESSTRANSFORMATIONINST element that does not match the name and type specified in the SESSIONEXTENSION element. Action: Edit the XML file, and verify the DSQINSTNAME and DSQINSTTYPE attributes match the SESSTRANSFORMATIONINST element name and type. Or, export the object again and then import it. REP_32207 Error: Invalid datatype for workflow variable <workflow variable name> Cause: In the XML file, you specified an invalid DATATYPE attribute for the WORKFLOWVARIABLE element. Action: Edit the XML file, and specify a valid DATATYPE attribute for the WORKFLOWVARIABLE element. Or, export the object again and then import it. REP_32208 Error: The extension of type <SESSIONEXTENSION type> and subtype <SESSIONEXTENSION subtype> does not exist for session transformation instance <SESSTRANSFORMATIONINST name>. Cause: In the XML file, the TYPE and SUBTYPE attributes for the SESSIONEXTENSION element are not supported for the SESSTRANSFORMATIONINST element. 424 Chapter 55: REP Messages
- 441. Action: Edit the XML file, and specify TYPE and SUBTYPE attributes in the SESSIONEXTENSION element that the SESSTRANSFORMATIONINST element supports. REP_32209 Error: Invalid suspension email <SUSPENSION_EMAIL name> for workflow <workflow name>. Cause: In the XML file, you specified a SUSPENSION_EMAIL attribute for the WORKFLOW element that references a non-existent Email task. Action: Edit the XML file, and verify the SUSPENSION_EMAIL matches a reusable Email task. Or, export the object again and then import it. REP_32210 Error: Name conflict or invalid object name <object name> for element <element name>. Cause: In the XML file, you entered invalid characters for the specified element name, or you specified an element name that conflicts with another element name. Action: Edit the XML file, and rename the element using valid characters only. Or, export the object again and then import it. REP_32211 Warning: missing both start and end range in key <KEYRANGE> for element <element name>. Cause: In the XML file, both the STARTRANGE and ENDRANGE attributes are empty for the specified KEYRANGE element. Action: Edit the XML file, and enter a value for the STARTRANGE, ENDRANGE, or both. Or, edit the start range and end range values in the session after you import it. REP_32212 Warning: the session transformation <SESSTRANSFORMATIONINST name> does not exist in the mapping <mapping name> in target folder. Cause: In the XML file, you specified SINSTANCENAME and TRANSFORMATIONTYPE attributes in a SESSTRANSFORMATIONINST element that does not match a transformation in the mapping associated with the session. This might have happened if you deleted the transformation in the mapping after you exported the session. Action: Edit the XML file, and verify the SESSTRANSFORMATIONINST element refers to an existing transformation in the referenced mapping. Or, edit the session after you import it. REP_32213 Error: the session transformation <SESSTRANSFORMATIONINST name> is not partitionable and is connected to a stage with more than one partitions. Cause: In the XML file, you included a non-partitionable SESSTRANSFORMATIONINST element in a pipeline with more than one partition. REP Messages 425
- 442. Action: Export the object again and then import it. REP_32214 Warning: invalid key name <KEYRANGE or HASHKEY name> for element <element name>. Cause: In the XML file, you specified a NAME attribute in a KEYRANGE or HASHKEY element that references a non-existent transformation port. Action: Edit the XML file, and enter a valid NAME. Or, export the object again and then import it. REP_32215 Error: Invalid DSQ type <DSQINSTTYPE> for element <SESSIONEXTENSION name>. Cause: In the XML file, you specified an invalid DSQINSTTYPE attribute for the SESSIONEXTENSION element. Action: Edit the XML file, and specify a valid DSQINSTTYPE attribute. Or, export the object again and then import it. REP_32216 Error: connection reference <CONNECTIONREFERENCE name> type <TYPE> and subtype <SUBTYPE> is not valid for the extension. Cause: In the XML file, you specified CONNECTIONTYPE and CONNECTIONSUBTYPE attributes in the specified CONNECTIONREFERENCE element that are not valid for the TYPE and SUBTYPE attributes of the SESSIONEXTENSION element. Action: Edit the XML file, and verify the type and subtypes of the CONNECTIONREFERENCE and SESSIONEXTENSION elements are compatible. Or, export the object again and then import it. REP_32217 Error: a partition name <PARTITIONNAME> is given for a non-partitionable connection reference for session transformation instance <session transformation instance name>. Cause: In the XML file, you included a PARTITIONNAME attribute in a CONNECTIONREFERENCE element that is not partitionable. Action: Edit the XML file, and remove the PARTITIONNAME attribute from the CONNECTIONREFERENCE element. Or, export the object again and then import it. REP_32218 Error: Invalid task type <task type> for element <element name>. Cause: In the XML file, you specified an invalid TYPE attribute in the TASK element. Action: Edit the XML file, and enter a valid TYPE for the TASK. Or, export the object again and then import it. 426 Chapter 55: REP Messages
- 443. REP_32219 Warning: cannot find the referenced config object <REFOBJECTNAME>, default session config is used. Cause: In the XML file, you specified a REFOBJECTNAME attribute in a CONFIGREFERNCE element that references a non-existent CONFIG element. Action: This is a warning. The Workflow Manager uses a default session configuration. REP_32220 Invalid partition type <PARTITIONTYPE> for session transformation <SESSTRANSFORMATIONINST>. Cause: In the XML file, you specified an invalid PARTITIONTYPE attribute in the SESSTRANSFORMATIONINST element. Action: Edit the XML file, and enter a valid PARTITIONTYPE. Or, export the object again and then import it. REP_32222 Error: duplicate object <object name> of type <object type>. Cause: The XML file contains two objects with the same name and type. Action: Edit the XML file, and rename the duplicate object. Or, export the object again and then import it. REP_32223 Error: two Schedulers of conflicting types specified for workflow <WORKFLOW name>: reusable <SCHEDULER under FOLDER> and nonreusable <SCHEDULER under WORKFLOW>. Cause: In the XML file, you specified SCHEDULERNAME and REUSABLE_SCHEDULER attributes in a WORKFLOW element that does not match a SCHEDULER element under the WORKFLOW element or a SCHEDULER element under the FOLDER element. Action: Edit the XML file, and verify the SCHEDULERNAME and REUSABLE_SCHEDULER attributes refer to only one SCHEDULER. Include reusable schedulers under the FOLDER element, and include non- reusable schedulers under the WORFKLOW element. Or, export the object again and then import it. REP_32224 Error: Task <TASKNAME> is not found for instance <TASKINSTANCE name>. Cause: In the XML file, you specified a TASKNAME attribute in a TASKINSTANCE element that references a non-existent reusable TASK element. Action: Edit the XML file, and verify the TASKNAME and REUSABLE attributes in TASKINSTANCE element the refer to only one TASK element. Include reusable tasks under the FOLDER element, and include non-reusable tasks under the WORFKLOW element. Or, export the object again and then import it. REP Messages 427
- 444. REP_32225 Error: Invalid value <value> for <attribute in SCHEDULER element> in Scheduler. Cause: In the XML file, you specified a invalid value for the specified attribute in the SCHEDULER element. Action: Edit the XML file, and enter a valid value. Or, export the object again and then import it. REP_32292 Error: The transformation [transformation name] has no input groups. Cause: You imported a Custom transformation defined with no input groups. Action: Edit the XML file and define at least one input group. Or, export the object and import it again. REP_32293 Error: The transformation [transformation name] has no output groups. Cause: You imported a Custom transformation defined with no output groups. Action: Edit the XML file and define at least one output group. Or, export the object and import it again. REP_32294 Error: Group [group name] of the transformation [transformation name] is both an input group and an output group. Cause: You imported a Custom transformation with a group defined as both an output and input group. Action: Edit the XML file and define the group as either an input, output, or input/ output group. Or, export the object and import it again. REP_32409 Session <name> has a log file name which is longer than 600 characters. Session is not valid. Cause: The session log file name is too long. Action: On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension. REP_32410 Session has a log file name which is longer than 600 characters. Session is not valid. Cause: The session log file name is too long. Action: On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension. REP_32413 Session <name> has a log directory name which is longer than 600 characters. Session is not valid. Cause: The session log file directory name is too long. Action: On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters. 428 Chapter 55: REP Messages
- 445. REP_32414 Session has a log directory name which is longer than 600 characters. Session is not valid. Cause: The session log file directory name is too long. Action: On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters. REP_32426 Session config <session configuration object name>. The number of runs to save session log on must be in the range 0 to 2147483647. Cause: For the named session configuration object, you are saving session logs by number of runs. The number of runs you specified is out of range. Action: On the session properties Config Object tab, Log Options settings, specify a number of runs between 0 and 2,147,483,647. REP_32427 The number of runs to save session log on must be in the range 0 to 2147483647. Cause: You are saving session logs by number of runs. The number of runs you specified is out of range. Action: Specify a number of runs between 0 and 2,147,483,647 for the session log options settings. REP_32467 Parameter file name is too long. Cause: The parameter file name for the workflow is too long. Action: On the workflow Properties tab, specify a parameter file name of 600 characters or fewer, including the file extension. REP_32469 Log file name is too long. Cause: The workflow log file name is too long. Action: On the workflow Properties tab, specify a workflow log file name of 600 characters or fewer, including the file extension. REP_32473 Log count must be in the range of 0 to 2147483647. Cause: You are saving workflow logs by number of runs. The number of runs you specified is out of range. Action: On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647. REP_32471 Log directory name is too long. Cause: The workflow log file directory name is too long. Action: On the workflow Properties tab, specify a workflow log file directory name of 600 characters or fewer, including delimiters. REP Messages 429
- 446. REP_32472 'Save workflow log for these runs' must be in the range of 0 to 2147483647. Cause: You are saving workflow logs by number of runs. The number of runs you specified is out of range. Action: On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647. REP_32475 Workflow task <name> parameter file name is too long. Cause: The parameter file name for the named workflow is too long. Action: On the workflow Properties tab, specify a parameter file name of 600 characters or fewer, including the file extension. REP_32477 Workflow task <workflow name> log file name is too long. Cause: The workflow log file name for the named workflow is too long. Action: On the workflow Properties tab, specify a workflow log file name of 600 characters or fewer, including the file extension. REP_32479 Workflow task <workflow name> log directory name is too long. Cause: The workflow log file directory name for the named workflow is too long. Action: On the workflow Properties tab, specify a workflow log file directory name of 600 characters or fewer, including delimiters. REP_32480 Workflow task <session name> log options is invalid. Cause: The session log save option is invalid. This can occur if the session was imported and the session log save option was incorrectly defined. Action: Check the Save Session Log By option on the session Properties tab. Choose to save session logs either by either timestamp or by number of runs. REP_32481 Workflow log option is invalid. Cause: The workflow save log option is invalid. This can occur if the workflow was imported and the workflow log save option was incorrectly defined. Action: Check the Save Workflow Log By option on the workflow Properties tab. Choose to save logs either by either timestamp or by number of runs. REP_32482 Workflow task <workflow name>: 'Save workflow log for these runs' must be in the range of 0 to 2147483647. Cause: You are saving workflow logs for the named workflow for a certain number of runs. The number of runs you specified is out of range. Action: Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure the number of runs is between 0 and 2,147,483,647. 430 Chapter 55: REP Messages
- 447. REP_32483 'Save workflow log for these runs' must be in the range of 0 to 2147483647. Cause: You are saving workflow logs by number of runs. The number of runs you specified is out of range. Action: On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647. REP_32490 Workflow task <workflow name> log directory name must have a delimiter. Cause: The workflow log file directory name for the named workflow does not end in a delimiter, either use โโ on Windows systems, or โ/โ on UNIX systems. Action: On the workflow Properties tab, include the appropriate delimiter after the workflow log file directory name. REP_32491 Log directory name must have a delimiter. Cause: The workflow log file directory name does not end in a delimiter, either use โโ on Windows systems, or โ/โ on UNIX systems. Action: On the workflow Properties tab, include the appropriate delimiter after the workflow log file directory name. REP_32494 The first character in a name cannot be a number. Cause: You entered a name in which the first character is a number. Action: Enter a name in which the first character is a letter. REP_32495 Spaces are not allowed in a name. Cause: You entered a name that includes spaces. Action: Enter a name that contains no spaces. REP_32496 The first character in a name cannot be <character>. Cause: You entered a name in which the specified character is not allowed as the first character in the name. Action: Enter a name that does not contain the specified character. REP_32497 The character <character> is not allowed in a name. Cause: You entered a name in which the specified character is not allowed. Action: Enter a name that does not include this character. REP_32498 Name length is too large. Cause: You entered a name that is too long. Action: Enter a shorter name. REP_32499 This is not a valid name. Cause: Internal error. REP Messages 431
- 448. Action: Contact your plug-in vendor. REP_32523 Session <name> has different connection subtype across partitions. Cause: The named session has multiple partitions. The source or target connection types for at least two partitions differ. Action: Update the session properties and specify the same source or target connection type for all partitions. REP_32524 Session has different connection subtype across partitions. Cause: The current session has multiple partitions. The source or target connection types for at least two partitions differ. Action: Update the session properties and specify the same source or target connection type for all partitions. REP_32532 Missing required hash key for <transformation> in session <name>. Cause: You selected hash user keys partitioning at the named transformation, but the hash key is missing. This may have occurred because you updated the mapping and replaced the named transformation with one that contains different ports. Action: Edit the session properties and either specify a hash key at the named transformation or change the partition type. REP_32533 Missing required hash key for <transformation>. Same as REP_32532. REP_32534 Invalid hash key <key name> for <transformation> in session <name>. Cause: You selected hash user keys partitioning at the named transformation, but the hash key you chose is no longer valid. This may have occurred because you updated the mapping and the selected key is no longer in the named transformation. Action: Edit the session properties and specify a new hash key at the transformation. REP_32535 Invalid hash key <key name> for instance <name>. Cause: You selected hash user keys partitioning at the named transformation instance, but the hash key you chose is no longer valid. This may have occurred because you updated the mapping and the selected key is no longer in the named transformation. Action: Edit the session properties and specify a new hash key at the transformation instance. REP_32536 Hash key <key name> for instance <name> in session <name> has invalid port type. Cause: You selected key range or hash user keys partitioning at the named transformation instance, but the key is no longer an input or an input/output 432 Chapter 55: REP Messages
- 449. port. This may have occurred because you updated the mapping and changed the port types in the named transformation instance. Action: Edit the session properties and select an input or input/output port as the key. REP_32537 Hash key <key name> for instance <name> has invalid port type. Same as REP_32536. REP_32542 Empty key range for <transformation> in session <name>. Cause: You selected key range partitioning at the named transformation. Both the start and end values for at least one key range are empty, and there is no a SQL override or filter condition for the transformation. Action: Either supply the missing start and end values for the key range, or specify a SQL override or filter condition for the transformation. REP_32543 Missing required hash key for <transformation>. Same as REP_32542. REP_32544 Timer task <name> uses an empty workflow variable. Cause: The Timer task uses a workflow variable to calculate the wait, but the variable has a null value. Action: Verify that the Timer task uses the correct variable. Also check the workflow or server log to determine why the variable value is null. REP_32546 Timer task <name> uses an invalid workflow variable. Cause: The Timer task uses a workflow variable to calculate the wait, but the variable is invalid. Action: Verify that the Timer task uses the correct variable. Also check the workflow to make sure the variable exists. REP_32548 Timer task <name> uses a workflow variable which is not Date/Time datatype. Cause: The named Timer task uses a workflow variable to calculate the wait, but the variable datatype is not Date/Time. Action: Check the timer task to make sure you specified the correct variable. Also check the workflow to make sure the variable datatype is Date/Time. REP_32550 Key not specified for key range partition for <partition name:transformation> in session <name>. Cause: You selected key range partitioning at the named transformation, but there is no partition key. This may have occurred because you updated the mapping and replaced the transformation with one that contains different ports. Action: Edit the session properties and either specify a partition key at the transformation or change the partition type. REP Messages 433
- 450. REP_32551 Key not specified for key range partition for <partition name:transformation>. Same as REP_32550. REP_32558 Workflow task <workflow name>: 'Save workflow log for these runs' has an invalid Integration Service variable associated with it. Cause: You are saving workflow logs for the named workflow by number of runs. The number of runs you specified is based on an invalid variable. Action: Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure that you specified the correct server variable. Also, verify that the variable you specified is an integer variable. REP_32559 'Save workflow log for these runs' has an invalid server variable associated with it. Cause: You are saving workflow logs by number of runs. The number of runs you specified is based on an invalid server variable. Action: Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure that you specified the correct server variable. Also verify that the server variable you specified is an integer variable. REP_32701 Key not specified for Hash User Keys partition (group <group name>, instance <transformation instance name>, session <session name>). Cause: You ran a session with a hash user keys partition point at a multigroup transformation, but you did not specify a key. Action: Edit the session properties and specify a key for the group. Or, change the partition type of the group. REP_32702 Key not specified for Hash User Keys partition (group <group name>, instance <transformation instance name>). Same as REP_32701. REP_32705 Key not specified for Key Range partition (group <group name>, instance <transformation instance name>, session <session instance name>). Cause: You selected key range partitioning, but you did not specify a key for the group. Action: Edit the session properties to specify a key for the group or change the partition type for the group. REP_32706 Key not specified for Key Range partition (group <group name> instance <transformation instance name>). Same as REP_32705. 434 Chapter 55: REP Messages
- 451. REP_32827 Syntax error: bad variable name <variable name>. Cause: You altered the XML file or created an invalid mapping variable name. The imported mapping variable has an invalid name. The name has to start with $$, has to be longer than two characters, and can only have alphanumeric characters and underscores. Action: Make sure mapping variable names follow the correct format. REP_32828 A variable with this name, <variable name>, already exists in the mapping. Cause: You altered the XML file or created an invalid mapping variable name. The imported mapping variable name is not unique within the imported mapping. Action: Make sure mapping variable names are unique within any mapping. REP_32898 Warning: Failed to upgrade XML source <source>. Cause: The XML source has inconsistencies and failed to upgrade. The XML source described in the error is not usable in the upgraded repository. Any mapping or session that uses the source is also unusable. Action: Re-import the XML source. REP_32899 Warning: Failed to upgrade XML target <target>. Cause: The XML target has inconsistencies and failed to upgrade. The XML target described in the error is not usable in the upgraded repository. Any mappings or sessions that use the target are also unusable. Action: Re-import the XML target. REP_51037 Database Connection Error: <error>. Cause: The Repository Service or Repository Agent process could not connect to the database. Action: Check preceding messages to see the cause of the error. Check the database log for related error messages. Verify the database user name, password, and connect string are correct. REP_51042 Repository Agent connection failed. System Error (errno = <error number>) <error message>: Cannot read message header. Read <number> bytes. Cause: The connection to the Repository Agent process failed due to a system error. Action: Check the system event log for related error messages to see the cause of the error. Try the operation again. If the problem persists, contact the network administrator. REP Messages 435
- 452. REP_51048 Communication failed because of network errors. [System Error (errno = <error number>): <error message>.] Please try connecting to the repository again. Cause: The PowerCenter Client or the Integration Service cannot connect to the Repository Agent. Action: Read the operating system error referenced in this message and make any necessary changes. There might be network problems. REP_51054 Internal error: Cannot allocate buffer of size <size> bytes to receive incoming message. The system may be out of memory. Cause: The system is low on resources. Action: Free some system resources. or Cause: Internal error. Action: Contact Informatica Technical Support. REP_50156 Repository Agent connection failed. [Unable to read from client socket. Read <number> bytes.] Cause: The repository client application lost connectivity to the Repository Agent process. Action: Verify that the Repository Agent process is running. If the Repository Agent is not running, restart it. Also, verify the repository database is running. REP_51058 Unknown TCP/IP error. Please try connecting to the repository again. Cause: The PowerCenter Client or the Integration Service cannot connect to the Repository Agent due to a network problem. This might happen if the Repository Agent machine was disconnected from the network, or if it lost power. Action: Verify the PowerCenter Client and Integration Service machines can connect to the Repository Agent machine and try to connect again. REP_51059 Repository Agent connection failed, another Repository Agent on host <host name> port <port number> is already connected to this repository <repository name>. Cause: There is another Repository Agent process already running for the repository. Action: Connect to the running Repository Agent, or wait for it to shut down before connecting again. REP_51071 Invalid name: You must specify a name. Cause: You tried to create a metadata extension, but left the metadata extension name blank. 436 Chapter 55: REP Messages
- 453. Action: Specify a name for the metadata extension. REP_51072 A metadata extension named <name> already exists in the current domain. Cause: You tried to create or rename a metadata extension. However, another metadata extension with the name you specified already exists for the same type of object in the domain. Action: Specify a unique name for the metadata extension. REP_51073 <Value> is not a valid integer value. Please enter an integer value between <minimum value> and <maximum value>. Cause: You entered a value for an integer metadata extension that is either too large or too small. Action: Enter a value that is between the minimum and maximum values. 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. Cause: You tried to change the precision for a string metadata extension, but the existing string is longer than the precision you specified. Action: Either shorten the length of the existing metadata extension and then change the precision, or specify a precision that is greater than or equal to the length of the existing metadata extension. REP_51075 The maximum length is too large. Please specify a value smaller than or equal to <maximum length>. Cause: You tried to enter a precision for a string metadata extension that is too long. Action: Specify a precision that is less than or equal to the maximum length. REP_51112 The reserved keyword <keyword> cannot be used. Cause: You specified a keyword that is reserved. You cannot use reserved keywords. Action: Specify a non-keyword. REP_51115 A table with the name <name> already exists. Please enter a unique name. Cause: You specified a table name that is already in use. Action: Enter a unique table name. REP_51116 This business name has already been used by the source table <database name>:<name> in the repository and has been renamed to <name>. You must save your changes before renaming this table. Cause: You changed the value for the business name in a source definition. You then attempted to enter the old business name in another source definition. This is not allowed. For example, you changed the business name in the source S1 REP Messages 437
- 454. from B1 to B2. You then entered the business name B1 to another source definition, S2. Action: Save your changes in the repository after entering the new business name for the source definition. Then you can use the old business name for another source definition. REP_51117 This business name has already been used by the source table <database name>:<source name>. Please enter a unique name. Cause: You specified a business name that is already in use. Action: Enter a unique business name. REP_51120 The column <column> cannot allow nulls. Cause: The Integration Service received data for a column that is null. This is not allowed. Action: Check the data and mapping for inconsistencies. REP_51122 A column with the name, <name>, already exists. Please enter a unique name. Cause: You specified a name for a column that is already in use. Action: Enter a unique name for the column. REP_51126 A group with this name already exists. Please enter a unique name. Cause: You specified a group name that is already in use. Action: Enter a unique name for the group. REP_51130 The length/precision cannot be set larger than <number>. Cause: You entered a value for length or precision that is too large. Action: Enter a value that is below the specified maximum length or precision. REP_51131 The length/precision must be greater than 0. Cause: You entered a value for length or precision that is less than zero. Action: Enter a value for length or precision greater than zero. REP_51133 The scale cannot be larger than <number>. Cause: You entered a value for scale that is too large. Action: Enter a value below the specified maximum scale. REP_51134 The absolute value of the scale cannot be larger than the length/precision. Cause: The absolute value of the scale you entered is larger than the value for length or precision. For example, you set the precision to 5, but set the scale to 7. 438 Chapter 55: REP Messages
- 455. Action: Enter a value for scale whose absolute value does not exceed the value for length or precision. REP_51135 The scale cannot be set less than -<number>. Cause: You entered a value for scale that is less than the minimum allowed value. Action: Enter a value for scale above the specified minimum value. REP_51136 The owner name is too long. Please enter a name less than 80 characters. Cause: You entered an owner name that exceeds 80 characters. Action: Enter an owner name using 80 characters or fewer. REP_51137 This business name has already been used by the target table <name> in the repository and has been renamed to <name>. You must save your changes before renaming this table. Cause: You changed the value for the business name in a target definition. You then attempted to enter the old business name in another target definition. This is not allowed. For example, you changed the business name in the target T1 from B1 to B2. You then entered the business name B1 to another target definition, T2. Action: Save your changes in the repository after entering the new business name for the target definition. Then you can use the old business name for another target definition. REP_51138 This business name has already been used by the target table <name>. Please enter a unique name. Cause: The business name is already in use. Action: Enter a unique business name. 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>. Cause: When you copy a folder, you do not have permission to a connection object in the target repository. Action: The Copy Folder Wizard will copy the connection from the source repository and rename it. REP_51292 Initialization property name cannot be empty. Cause: There is no initialization property value. Action: Add an initialization property. REP Messages 439
- 456. REP_51293 Initialization property <property> already exists. Please enter a unique name. Cause: The name for the specified initialization property already exists. Action: Enter a unique name for the initialization property. REP_51294 Initialization property <property> doesn't exist. Cause: The specified initialization property does not exist. Action: Specify an existing initialization property. REP_51295 <property> is a built-in initialization property. Cause: You attempted to delete, create, or rename an initialization property that is a built-in initialization property. You cannot modify a built-in initialization property. Action: Do not attempt to delete, create, or modify built-in initialization properties. REP_51296 The description of a built-in initialization property cannot be modified. Cause: You attempted to modify the description of a built-in initialization property. This is not allowed. Action: Do not modify the description of a built-in initialization property. REP_51297 Built-in initialization property cannot be deleted. Cause: You attempted to delete a built-in initialization property. Action: Do not delete a built-in initialization property. REP_51298 Initialization property name cannot have more than 80 characters. Cause: The initialization property name exceeds 80 characters. Action: Enter an initialization property name using 80 characters or fewer. REP_51300 Error: Inconsistent repository. Repository <repository name> does not have an Administrator user. Repository initialization failed. Cause: The repository database may have inconsistencies. Action: Restore the repository from a backup file and check the database server log for errors. or Cause: Internal error. Action: Contact Informatica Technical Support. REP_51301 Unable to send messages to the Repository Service. Initialization of repository <repository name> failed. Cause: Internal error. 440 Chapter 55: REP Messages
- 457. Action: Contact Informatica Technical Support. REP_51304 Partition number <number> is not valid. Cause: Plug-in internal error. Action: Contact the plug-in application vendor. REP_51343 Unable to connect to the database server. Please check the connection to the database server. Cause: The Repository Agent process could not connect to the repository database server. Action: Verify the repository database is running. Verify that you have a network connection to the repository database system. Verify the database user name, password, and connect string are correct. Verify the database type specified in the repository configuration is correct. REP_51357 Failed to fetch the connection <connection name> specified for $Source because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use. Cause: The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Source Connection Value session property, you did not specify Relational: or Application: before the connection name. Action: Enter Relational: or Application: before the connection name for $Source Connection Value on the Properties tab of the session properties. REP_51358 Failed to fetch the connection <connection name> specified for $Target because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use. Cause: The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Target Connection Value session property, you did not specify Relational: or Application: before the connection name. Action: Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties. REP_51378 Failed to fetch the connection <connection name> specified for REH DB Log because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use. Cause: The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Target Connection Value session property, you did not specify Relational: or Application: before the connection name. REP Messages 441
- 458. Action: Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties. REP_51444 โMessageSendBufferSizeโ value <message send buffer size> is invalid, ignoring invalid value <message send buffer size>. Using system default value. Cause: The repository is on a Windows machine and the repository configuration file specifies an invalid value for the MessageSendBufferSize parameter. The Repository Agent uses the default message send buffer size. Action: Edit the repository configuration file and verify the MessageSendBufferSize size is greater than or equal to zero. When you specify zero, the Repository Agent ignores the MessageSendBufferSize parameter. REP_51445 โMessageReceiveBufferSizeโ value <message receive buffer size> is invalid, ignoring invalid value <message receive buffer size>. Using system default value. Cause: The repository is on a Windows machine and the repository configuration file specifies an invalid value for the MessageReceiveBufferSize parameter. The Repository Agent uses the default message receive buffer size. Action: Edit the repository configuration file and verify the MessageReceiveBufferSize size is greater than or equal to zero. When you specify zero, the Repository Agent ignores the MessageReceiveBufferSize parameter. REP_51447 Repository agent connection failed. A repository request has timed out. [System Error <error number>]. Please try connecting to the repository again. Cause: The timeout values of the Repository Agent requests are too small. Or, you made a request for a large repository object, which decreased network performance. Action: Increase the MessageReceiveTimeout value and MessageSendTimeout value from the repository configuration. or Cause: Repository Agent timed out due to a slow network. Action: Verify that the network is running properly. or Cause: The repository is stopped. Action: Start the repository. 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>. Cause: The value specified for Database Pool Expiry Timeout is invalid. For example, it may be less than the minimum, or it may be a negative number or a letter. 442 Chapter 55: REP Messages
- 459. Action: Accept the default value for Database Pool Expiry Timeout. or Action: Enter a valid value for Database Pool Expiry Timeout in the Repository Service advanced properties. REP_51503 The value <number of connections> specified for Database Pool Expiry Threshold value is invalid. The Repository Service is using the default value <number>. Cause: The value specified for Database Pool Expiry Threshold is invalid. For example, it may be less than the minimum, or it may be a negative number or a letter. Action: Accept the default value for Database Pool Expiry Threshold. or Action: Enter a valid value for Database Pool Expiry Threshold in the Repository Service advanced properties. REP_51507 Target <target name> cannot have FileName field. Cause: You are importing a target that has a column defined as a FileName port, but the target does not support a FileName port. The target must be a flat file. Action: Remove the ISFILENAMEFIELD = "YES" field attribute in the XML file. REP_51508 Target <target name> has existing FileName field. Cause: You are importing a target the has two FileName ports. A flat file target can have one FileName port. Action: Remove the ISFILENAMEFIELD = "YES" field attribute for one of the columns in the XML file. REP_51509 Workflow task <workflow ID> maximum automatic recovery attempts must be in the range of 0 to 2147483647. Cause: The Maximum Automatic Recovery Attempts option contains a negative number. Action: Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab. The number must be zero or greater. REP_51510 Maximum automatic recovery attempts must be in the range of 0 to 2147483647. Cause: The Maximum Automatic Recovery Attempts is a negative number. Action: Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab. The number must be zero or greater. REP Messages 443
- 460. REP_51814 Repository connection failed. Cause: The Repository Agent process could not connect to the repository database. Action: Check preceding messages to see the cause of the error. REP_51815 Failed to read the repository connection information. Cause: The Repository Agent process could not read connectivity information from the repository configuration. Action: Verify the information in the repository configuration is correct. REP_51832 The license key for the repagent has expired. Cause: The product license key is expired. Action: Contact Informatica Technical Support to obtain a new license key. REP_51848 Cannot enable object versioning without a team-based development license key. Cause: PowerCenter cannot enable object versioning because the license assigned to the repository does not have the team-based development option. Action: Apply a license that has the team-based development option to the Repository Service. You can purchase and get this option from Informatica. REP_51849 The versioned repository cannot be enabled or restored without a team-based development license key. Cause: PowerCenter cannot enable object versioning until you have a team-based development license key. Action: Apply the Repository Service to a license that has the team-based development option. You can purchase and get this option from Informatica. REP_51961 The value of the environment variable <environment variable name> needs to be encrypted with the latest version of pmpasswd. Cause: The environment variable was encrypted using an old version of pmpasswd. Effective in PowerCenter 8.1, pmpasswd uses a new, more robust encryption algorithm. Action: Use the current version of pmpasswd to encrypt all passwords that you store as environment variables, and update the environment variables with the new encrypted passwords. REP_55035 An error occurred during deployment. Cause: The Repository Agent process could not copy a folder. Action: Check preceding messages to see the cause of the error. This error message may be preceded by REP_51056. 444 Chapter 55: REP Messages
- 461. REP_55036 An error occurred during folder comparison. Cause: The Repository Agent process could not compare two folders. Action: Check preceding messages to see the cause of the error. REP_57064 Maximum number of connections exceeded. Cause: The maximum number of connections to the Repository Agent process exceeded the number of connections specified in the repository configuration. Action: Edit the repository configuration and increase the value of the MaximumConnections configuration option. Also, closed inactive connections to the repository. REP_57071 Unable to connect to the repository database. Please check the Repository Agent configuration. Cause: The Repository Agent could not connect to the repository database. Action: Verify the connectivity information in the repository configuration is correct. Verify that the repository database is running. REP_57084 Maximum number of concurrent locks exceeded. Cause: The Repository Agent process exceeded the number of repository object locks specified in the repository configuration. Action: Edit the repository configuration and increase the value of the MaximumLocks configuration option. Also, release residual locks. 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. Cause: The specified database connection name exists as both a relational and application connection. You entered the database connection name for the Stored Procedure or Lookup transformation location in the session properties, but you did not specify Relational: or Application: before the connection name. Action: Enter Relational: or Application: before the connection name for the Stored Procedure or Lookup transformation location in the session properties. or Cause: The database connection name in the From field in the Replace Connections dialog box exists as both a relational and application connection. You entered the database connection name in at least one session or transformation, but you did not specify Relational: or Application: before the connection name. Action: Enter Relational: or Application: before the connection name in all transformation properties and session properties that specify this database connection name. REP Messages 445
- 462. REP_57201 Internal Error: Repository object is inconsistent. Cause: Internal error. Action: Contact Informatica Technical Support. REP_57269 This connection has been terminated. Cause: A repository connection ended because a repository or domain administrator terminated the repository connection, and then a PowerCenter Client tried to reconnect to the repository with the same connection. Action: Verify that the repository administrator does not need to have all users disconnected from the repository for maintenance or other purposes. Then retry the operation in the PowerCenter Client. REP_61002 WARNING: <XML definition> contained elements or attributes whose prefixes were removed. Cause: You are upgrading an XML definition that contains prefixed attributes or elements. The XML parser removes prefixes from attributes and elements and completes your repository upgrade. Action: Complete the repository upgrade and import the XML definition again. REP_61003 Empty key range for key <key name> (group <group name>, instance <transformation instance name>, session <session instance name>). Cause: You did not specify a key range for the specified key. Action: Edit the key range and specify the start and end value for the key. REP_61004 Empty key range for key <key name> (group <group name> session <session name>). Same as REP_61003. REP_61010 Failed to validate transformation field <field name>. Cause: Internal error. The field ID or the table ID that the field belongs to is zero. Action: Contact Informatica Technical Support. REP_61011 Cannot have cycles in transformation fields. Cause: Internal error. Action: Contact Informatica Technical Support. REP_61012 Error: Field <port name> of transformation <transformation name> could not be validated. Cause: The Designer could not validate the port in the transformation. Action: Check other error messages preceding this error message. 446 Chapter 55: REP Messages
- 463. REP_61013 Invalid group encountered while validating group order. Cause: Internal error. Action: Contact Informatica Technical Support. REP_61014 Error: The groups of transformation <transformation name> could not be validated. Cause: The Designer could not validate the transformation. Action: Check other error messages preceding this error message. REP_61027 Unable to set database connection property. Cause: Internal error. Action: Contact Informatica Technical Support. REP_61031 Failed to upgrade <XML definition> because removal of prefixes generated an invalid XPATH. Cause: The upgrade process removed a prefix from an element or an attribute. The resulting XML map is not unique and could not be upgraded to a valid XPath. Action: Import the XML definition again. REP_61032 Failed to upgrade <XML source> because removal of prefixes caused element names to conflict! Cause: The upgrade strips prefixes from XML element names. The upgraded names may conflict with other element names. Action: Import the XML definition again. REP_61059 Warning: Failed to upgrade XML source <source>, version <version>, folder <folder>. Cause: You cannot upgrade the source XML definition because it has inconsistencies. Action: The XML definition is unusable. You must recreate it. REP_61060 Warning: Failed to upgrade XML target <target>, version <version>, folder <folder>. Cause: You cannot upgrade the target XML definition because it has inconsistencies. Action: The XML definition is unusable. You must recreate it. REP_61063 An error was encountered during the upgrade. Cause: An error occurred while upgrading an XML source or target. This error might occur because of memory problems or loss of a database connection while fetching/inserting the source or target. Action: Run the upgrade again. If the upgrade fails again, call Informatica Technical Support. REP Messages 447
- 464. 448 Chapter 55: REP Messages
- 465. Chapter 56 REP_CORE Messages This chapter includes the following topic: โฆ REP_CORE Messages, 450 Error messages listed numerically. 449
- 466. REP_CORE Messages REP_CORE_59046 The high availability license is absent for the Repository Service process <name>. Cause: The high availability option is required for failover of the Repository Service process. You do not have the high availability option. Action: None. 450 Chapter 56: REP_CORE Messages
- 467. Chapter 57 RFC Messages This chapter includes the following topic: โฆ RFC Messages, 452 Error messages listed numerically. 451
- 468. RFC Messages RFC_17420 Property <property name> is invalid. Error encountered while parsing function list. Cause: The Integration Service encountered errors when parsing the FunctionNameList property in the RFCTransactionSupport Custom transformation. Action: Check the string value of the FunctionNameList property in the initialization properties of the RFCTransactionSupport Custom transformation. RFC_17421 The functions in the property <FunctionNameList> do not match the number of functions in the property <NumberOfFunctions>. Cause: In the initialization properties of the RFCTransactionSupport Custom transformation, the value of the property โNumberOfFunctionsโ does not match the number of function names in the string value of the property โFunctionNameList.โ Action: Check the values of both properties. Make sure the two values match in number of functions. RFC_17422 Function Name <Function name> and Sequence ID <Sequence ID> do not match. One of them is incorrect. Cause: The specified function name and sequence ID for the incoming row to the Custom transformation is not in sync. Data may be incorrect or corrupt. Action: Prepared data might be modified or incorrectly prepared in the prepared data pipeline. Check the specified row data. RFC_17423 Input for function <Function name> is received while expecting input for function <Function name>. Cause: There is only one function in the mapping and the value of sequence ID is not 1, or you have more than one function in the mapping and the order of SequenceID is not in sequential order. For example, the first row comes into the RFCMSFunctionCall Custom transformation with SeqID = 1, the second row comes into the RFCMSFunctionCall Custom transformation with SeqID = 3. Action: The RFCFunctionCall Custom transformation expects the SequenceID to increase by increment of 1 from the previous SequenceID. Check the data in the PreparedData targets. RFC_17424 Call to function <Function name> corresponding to TransactionID = <Transaction ID>, IntegrationID = <Integration ID> failed. Cannot continue transaction. Cause: The function call to SAP with the specified TransactionID and IntegrationID has failed. 452 Chapter 57: RFC Messages
- 469. Action: See the error messages in the session log for more information. RFC_17425 Commit call failed for TransactionID <Transaction ID>. Cause: The commit function call to SAP has failed. Action: See the error messages in the session log for more information. RFC_17427 Error when trying to create SAP internal table for function table parameter <Parameter name>. Cause: The Integration Service failed to create new SAP internal table. Action: Check if the node where the Integration Service process runs is out of memory. RFC_17439 The value of all connected input indicator ports is NULL. The source file may be invalid. See the session log to find the row with the error. Cause: The source file may be invalid. Action: Examine the session log and the source file and eliminate errors. RFC_17447 Wait until Commit is selected. The server will wait until the commit call completes. Cause: This is an informational message. The BAPI_TRANSACTION_COMMIT commit function waits to complete work on one transaction before starting another. Action: None. RFC_17448 Wait until Commit is disabled. The server will return immediately after the commit call. Cause: This is an informational message. The ABAP4_COMMIT_WORK commit function does not wait to complete one transaction before starting another. Action: None. RFC_17449 The commit function is BAPI_TRANSACTION_COMMIT. Cause: This is an informational message. The BAPI_TRANSACTION_COMMIT commit function waits to complete work on one transaction before starting another. Action: None. RFC_17450 The commit function is ABAP4_COMMIT_WORK. Cause: This is an informational message. The ABAP4_COMMIT_WORK commit function does not wait to complete one transaction before starting another. Action: None. RFC Messages 453
- 470. RFC_17451 Invalid commit function <commit function> selected. BAPI_TRANSACTION_COMMIT and ABAP4_COMMIT_WORK are the only allowed commit functions. Cause: You may have tried to use an unsupported commit function. Action: Use either the BAPI_TRANSACTION_COMMIT or ABAP4_COMMIT_WORK commit functions. 454 Chapter 57: RFC Messages
- 471. Chapter 58 RR Messages This chapter includes the following topic: โฆ RR Messages, 456 Error messages listed numerically. 455
- 472. RR Messages RR_4004 ERROR: Failed sanity check. No primary key in source tables. Cause: The source tables specified in the mapping do not contain primary keys. Action: Use source tables that contain primary keys or edit the source tables appropriately. When using multiple sources, you must create the appropriate primary-foreign key relationships. RR_4006 ERROR: Failed sanity check. No key in node... Cause: The source tables specified in the mapping do not contain the appropriate primary key-foreign key relationships. When using multiple source tables with a Source Qualifier, each table must have a primary key-foreign key relationship. Action: Use source tables that contain the appropriate primary key-foreign key relationships, or edit the source tables appropriately. RR_4025 Error executing stored procedure... Cause: You have requested a stored procedure that does not exist in the source databases. Action: Check the source database for the stored procedure you have specified. or Cause: The Integration Service encountered an error while trying to run a stored procedure. Action: Check the session log for related error messages. RR_4032 Warning: # of sorted ports <number of ports> must be less than # of projected fields <number of connected output ports>. Ignoring sort request. Cause: The number of output ports connected from the Source Qualifier transformation to another transformation is less than the number entered in the Source Qualifier number of sorted ports option. Action: Change the sort count to less than or equal to connected ports in the Designer. RR_4033 Error parsing stored procedure call text <call text>. Cause: The specified stored procedure call text is incorrect. Action: Correct the call text before running the session again. RR_4034 Projected column metadata fetch failed. Cause: Internal error. Action: Contact Informatica Technical Support. 456 Chapter 58: RR Messages
- 473. RR_4035 SQL error. Cause: Error executing SQL query. Action: Make sure the query can run using SQL Override in the Source Qualifier. Otherwise, contact Informatica Technical Support. RR_4036 Error connecting to database <database name>. Cause: The Integration Service failed to connect to the database. You may have logged in incorrectly. Action: Enter the correct login information. user names and passwords may be case- sensitive. RR_4038 Error setting stored procedures. Session-> m_pMapping corrupt. Cause: Internal error. The repository might be out of memory or have inconsistencies. Action: Contact Informatica Technical Support. RR_4039 User defined query <query> contains character(s) that is (are) not valid in the code page of the source database connection. The invalid character starts at position <number> of the query. Cause: You entered a query containing characters that are invalid in the source database connection code page. Action: Change the query to contain characters included in the source database connection code page only. RR_4040 User defined join condition and/or source filter condition <string> contains character(s) that is(are) not valid in the code page of the source database connection. The invalid character starts at position <number> in the above condition. Cause: The join condition or the source filter condition or the combination of both join and filter conditions contain characters that are invalid in the source database connection code page only. Action: Change either the join, filter, or both conditions to contain characters included in the source database connection code page. RR_4041 User defined source filter condition <string> contains character(s) that is (are) not valid in the code page of the source database connection. The invalid character starts at position <number> of the filter condition. Cause: You entered a filter condition containing characters that are invalid in the source database connection code page. Action: Change the filter condition to contain characters included in the source database connection code page. RR Messages 457
- 474. 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. Cause: You defined a partition key for a port in the source qualifier that you deleted. Action: Edit the session to remove the partition key from the Source Qualifier. Then save the new partition information in the session and run it again. 458 Chapter 58: RR Messages
- 475. Chapter 59 RS Messages This chapter includes the following topic: โฆ RS Messages, 460 Error messages listed numerically. 459
- 476. RS Messages RS_39037 Failed to start repository <repository name>. Cause: The Repository Service failed to start a Repository Agent process for the repository. Action: Check preceding error messages in the Repository Service log file to see the cause of the error. Verify that the repository database is running. Verify that the repository configuration information is correct. Verify that another Repository Service is not running a Repository Agent for the repository. RS_39061 Cannot start repository <repository name> as it is being shut. Cause: You cannot start the repository because it is in the process of being shut down. Action: If you want to start the repository, wait until it is shut down before trying to start it. Verify that the system administrator is not shutting down the repository for maintenance purposes. RS_39068 Failed to register LDR <local repository name> to GDR <global repository name>. Cause: The Repository Service could not register the local repository to the global repository because you specified incorrect connectivity information for either the local or global repository. Message RS_39090 or message RS_39091 may precede this message. Action: Check preceding messages for more information. RS_39090 Cannot complete [Register] operation because of failure to start or connect to repository [repository_name]. Cause: The Repository Service could not register a local repository to a global repository because it could not start the Repository Agent process for one of the repositories. Action: Check preceding messages to see the cause of the error. Also, verify that the local and global repository databases are running, and that you entered correct connectivity information. RS_39091 Cannot complete [UnRegister] operation because of failure to start or connect to repository [repository_name]. Cause: The Repository Service could not unregister a local repository from a global repository because it could not start the Repository Agent process for one of the repositories. Action: Check preceding error messages in the Repository Service log file to see the cause of the error. Verify that the repository database is running. Verify that the repository configuration information is correct. Verify that another Repository Service is not running a Repository Agent for the repository. 460 Chapter 59: RS Messages
- 477. RS_39092 Cannot promote repository [repository_name] to be a Global repository because of failure to start or connect to the repository. Cause: The Repository Service could not promote a local repository to a global repository because it could not start a Repository Agent process for the repository. Action: Check preceding error messages in the Repository Service log file to see the cause of the error. Verify that the repository database is running. Verify that the repository configuration information is correct. Verify that another Repository Service is not running a Repository Agent for the repository. RS_39107 Cannot start repository <repository name> as it has been disabled. Cause: The Repository Service cannot start the repository because it is disabled. Action: Enable the repository. If you cannot enable it, a repository administrator may have disabled the repository for maintenance. RS_39109 Cannot enable repository <repository name> as it is not disabled. Cause: The Repository Service cannot enable the repository because it is already enabled. Action: None. RS_39120 ERROR: This product license does not allow global repositories. Only a PowerCenter license does that. Cause: You cannot create global repositories or promote a local repository to a global repository with your current license. Action: If you want to create global repositories, you need to purchase the Team-based Development option. RS_39121 ERROR: This product license does not allow registering or unregistering repositories. Only a PowerCenter license does that. Cause: You cannot register a local repository with or unregister a local repository from a global repository with your current license. Action: If you want to register or unregister repositories in a repository domain, you need to purchase the Team-based Development option. RS_39141 ERROR: Invalid characters in repository name <repository name>. Cause: The repository name contains invalid characters. Action: Create a new repository configuration. Include only valid characters when you specify the repository name. RS Messages 461
- 478. RS_39145 Failed to copy repository <repository name> to repository <target repository name>. Cause: The Repository Service cannot copy a repository to another database because a repository already resides in the target database. Action: Back up the repository in the target database if you want to save the data, then delete it. or Cause: The Repository Service cannot copy a repository to another database. Action: Check the target database server log or preceding messages in the Repository Service log for the cause of the error. RS_39209 Failed to complete a call to repository <repository name>. Cause: The Repository Server failed to connect to the Repository Agent for the specified repository. The Repository Agent may have stopped. Action: Verify the Repository Agent is running. Read related error messages for more information. 462 Chapter 59: RS Messages
- 479. Chapter 60 SDK_ Messages This chapter includes the following topic: โฆ SDKC Messages, 464 โฆ SDKS Messages, 465 โฆ SDKXML Messages, 466 Error messages listed numerically. 463
- 480. SDKC Messages SDKC_37005 Global locale could not be found for this process. Cause: Internal error. Action: Contact Informatica Technical Support. SDKC_37006 Invalid code page id <ID>. Cause: The code page is invalid. Action: Specify a valid code page. SDKC_37007 Failed to create locale. Cause: Internal error. Action: Contact Informatica Technical Support. SDKC_37008 Could not load message catalog. Cause: You specified an invalid path for the message catalog. Action: Specify a valid message catalog path. 464 Chapter 60: SDK_ Messages
- 481. SDKS Messages SDKS_38005 Couldn't load the library <library> for plug-in #<ID>. Cause: PowerCenter could not load the specified library for the repository plug-in. The library or dependent libraries may not be in the proper directory. Action: Verify that the library and any dependent libraries are in the proper directories. SDKS_38006 Plug-in #<ID>'s interface version <version> is not compatible with SDK interface version <version>. Cause: The version of the plug-in and the SDK version are not compatible. Action: Update the plug-in version to an SDK-compatible version. SDKS_38007 Error occurred during <phase> <reader/writer> plug-in #<ID>. Cause: There was an error during plug-in initialization or deinitialization. Action: See additional error messages for more information. SDKS_38200 Partition-level [SQ_MSMQ_SOURCE]: Plug-in #310000 failed in init(). Cause: Internal error. Action: Contact Informatica Technical Support. SDKS_38505 Plug-in #<ID>'s target <target> indicated that the error threshold <number> has been reached. Cause: The Integration Service reached the maximum number of errors for the session. The session failed. Action: If you want to increase the number of allowable errors per session, increase the session error threshold. SDKS_38605 Plug-in #<ID>'s target <target> encountered a transient failure. Cause: The Integration Service was unable to write data to the target because of a connection failure. Action: Verify that a connection to the target can be established. SDKS Messages 465
- 482. SDKXML Messages SDKXML_43009 Plug-in level: CT failed in <function name>() Cause: The plug-in for a Java Custom transformation or Java transformation failed during the execution of a plug-in level function. Action: If the message occurs for a session that contains a Java transformation, recompile the code for the transformation in the Designer and run the session again. 466 Chapter 60: SDK_ Messages
- 483. Chapter 61 SEBL Messages This chapter includes the following topic: โฆ SEBL Messages, 468 Error messages listed numerically. 467
- 484. SEBL Messages SEBL_30005 Not all sources are related in application source qualifier <application source qualifier name>. Cause: You tried to connect or associate two unrelated table source definitions in the listed application source qualifier. You can only connect or associate related table source definitions in an application source qualifier. Action: Disconnect one of the unrelated table source definitions. or Action: Remove one of the associated source definitions. SEBL_30006 Unknown error occurred in application source qualifier <application source qualifier name>. Cause: Internal error. Action: Contact Informatica Technical Support. SEBL_30008 Application source qualifier <application source qualifier name> has projected port with no inbound link. Cause: The listed application source qualifier has a connected output port, and the corresponding input port is not connected. Action: Connect the necessary input port, or disconnect the connected output port. SEBL_30009 SQL Error <SQL statement>. Cause: Internal error. The Integration Service encountered an error in the listed SQL statement. Action: Contact Informatica Technical Support. SEBL_30011 Application source qualifier <application source qualifier name> has invalid user-defined query <query> with character error at <number> location. Cause: You entered a query containing characters that are not valid in the application connection code page. Action: Edit the query so all characters are valid in the application connection code page. SEBL_30012 Application source qualifier <application source qualifier name> has invalid filter clause <filter> with character error at <number> location. Cause: You entered a filter condition containing characters that are not valid in the application connection code page. Action: Edit the filter condition so all characters are valid in the application connection code page. 468 Chapter 61: SEBL Messages
- 485. SEBL_30013 Application source qualifier <application source qualifier name> has invalid join and/or filter override <join override> with character error at <number> location. Cause: You entered a join condition and/or source filter condition that contain characters that are not valid in the application connection code page. Action: Edit the join and/or filter conditions so all characters are valid in the application connection code page. SEBL_30014 Application source qualifier <application source qualifier name> has more than one business component attached. Cause: The listed application source qualifier is associated or connected to more than one Siebel business component source definition. You can associate or connect only one business component source definition to a single application source qualifier. Action: Disconnect one of the business component source definitions from the application source qualifier. or Action: Remove one of the associated business component source definitions. or Action: To use more than one business component in a single mapping, create an application source qualifier for each business component you want to use. Use a Joiner transformation to join two related business components. SEBL_30015 Application source qualifier <application source qualifier name> has business component and other sources. Cause: The listed application source qualifier is connected to a business component source definition and other source definitions. You cannot join a business component with other Siebel sources. Action: Use a separate application source qualifier for each Siebel source definition. SEBL_30019 Application source qualifier <application source qualifier name> has filter clause which uses one or more fields that were not selected. Cause: The listed application source qualifier has a filter clause which uses one or more fields that you did not select from the business component. Action: In the filter clause, only use the fields that you select from the business component. SEBL_30020 Application source qualifier <application source qualifier name> has join override clause which uses one or more fields that were not selected. Cause: The listed application source qualifier has a join override clause which uses one or more fields that you did not select from the business component. SEBL Messages 469
- 486. Action: In the join override clause, only use the fields that you select from the business component. SEBL_30022 Application source qualifier <application source qualifier name> has partitions with key names that use one or more fields that were not selected. Cause: The listed application source qualifier has partitions with key names that use one or more fields that you did not select from the business component. Action: For key names in partitions, only use the fields that you select from the business component. SEBL_30023 One or more fields used to partition source(s) of application source qualifier <application source qualifier name> have been deleted. Cause: You defined a partition key for a port in the application source qualifier that you deleted. Action: Edit the session to remove the partition key from the application source qualifier. Then save the new partition information in the session and run it again. 470 Chapter 61: SEBL Messages
- 487. Chapter 62 SF Messages This chapter includes the following topic: โฆ SF Messages, 472 Error messages listed numerically. 471
- 488. SF Messages SF_34032 Closing client application <application>'s connection dues to PROTOCOL ERROR. Please contact Informatica Technical Support. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34033 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34034 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34035 PROTOCOL ERROR: Got request ID <request ID> while expecting request ID <request ID> from client application <application> on connection <connection ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34036 PROTOCOL ERROR: Got request key <key> while expecting request key <key> from client application <application> on connection <connection ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34037 PROTOCOL ERROR: Got request type <request type> while in state <state> from client application <application> on connection <connection ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34062 Cannot open service control manager. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34063 Cannot close service control manager. Cause: Internal error. Action: Contact Informatica Technical Support. 472 Chapter 62: SF Messages
- 489. SF_34064 Cannot lock service database. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34065 Cannot unlock service database. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34066 Cannot open service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34067 Cannot close service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34068 Cannot query service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34069 Cannot control service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34070 Cannot stop service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34071 Cannot delete service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34072 Cannot create service. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34094 Caught a fatal signal. Will abort this server process shortly. Cause: Internal error. Action: Contact Informatica Technical Support. SF Messages 473
- 490. SF_34095 Aborting this process due to a fatal signal. Cause: Internal error. This message is preceded by SF_34094. Action: Contact Informatica Technical Support. SF_34096 Caught SIGFPE signal. Aborting this server process. Cause: Internal error. Action: Contact Informatica Technical Support. SF_34098 Failed to allocate memory (out of virtual memory). Cause: The Integration Service requires more memory. Action: Increase the amount of available virtual memory on the Integration Service system. SF_34105 Failed to redirect standard error (stderr) messages to the file <file name>. System error is <system error number> <system error message>. Cause: You enabled the Integration Service configuration flag, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard error messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory. Action: Review the system error and contact your system administrator. SF_34106 Failed to redirect standard output (stdout) messages to the file <file name>. System error is <system error number> <system error message>. Cause: You enabled the Integration Service configuration flag, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard output messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory. Action: Review the system error and contact your system administrator. SF_34109 Failed to open file <file name> for redirecting console output (stdout/stderr) messages System error is <system error number> <system error message>. Cause: You enabled the Integration Service configuration flag, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service failed to open the file to write messages. Action: Verify that the user starting the Integration Service has write permission on the file directory. or Action: Review the system error and contact your system administrator. 474 Chapter 62: SF Messages
- 491. 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. Cause: During a transient failure, the Integration Service could not access the $PMStorageDir to store the request for recovery. Action: Verify that the Integration Service can access $PMStorageDir. If the directory does not exist or cannot be written to, the request cannot be persisted. SF_34130 Cannot get the storage files in directory <directory name>. Cause: The storage directory does not exist or there are no storage files in this directory. Action: Make sure the $PMStorageDir directory path is set to directory that exists, and you have proper write permissions to the directory. SF_34132 Errors encountered while reading from storage files. Cause: You do not have write permission, or the disk is full. Action: Make sure you have write permission, and the disk has enough room for the storage file. SF_34134 Error in writing to storage file <file name>. Cause: You do not have write permission, or the disk is full. Action: Make sure you have write permission, and the disk has enough room for the storage file. SF_34135 Errors encountered while writing to storage files. Cause: The Integration Service does not have write permission on the directory to write the state of operations. Action: Verify that the user configured to start Informatica Services has write permission, and the disk has enough room for the storage file. SF_34136 Error in removing storage file <file name>. Cause: The storage file is in use, or you do not have write permissions on the storage file. Action: Make sure you have write permission, and the disk has enough room for the storage file. SF_34155 Child process [process ID] terminated due to spurious abort errno [error number]. Cause: The Session or Command task exited unexpectedly and the machine running the Integration Service process generated an error. Action: Use the error number to determine the cause of the error. If it indicates an out- of-memory error, increase the swap space or reduce the maximum processes SF Messages 475
- 492. threshold. You define the maximum processes threshold on the Properties tab for the node in the Administration Console. Review the core file of the process for the Command task. 476 Chapter 62: SF Messages
- 493. Chapter 63 SM Messages This chapter includes the following topic: โฆ SM Messages, 478 Error messages listed numerically. 477
- 494. SM Messages SM_7024 Transformation Parse Fatal Error: Filter clause did not evaluate to a numeric value. Cause: The filter condition you specified in Filter transformation does not evaluate to a numeric value. Action: Verify that the filter condition evaluates to a numeric value. SM_7027 Transformation evaluation error; current row skipped... trying to delete a non- existing row. Cause: The Integration Service failed to evaluate an expression with a particular row, forcing it to skip that row. Action: Check the session log for information about the skipped row. SM_7038 Aggregate Error: The data movement mode <data movement mode for Integration Service> for the Integration Service does not match the data movement mode <data movement mode in cache> in cache. Cause: You started a session using incremental aggregation after changing the Integration Service data movement mode. The Integration Service cannot access incremental aggregation files created in a different data movement mode. Action: Delete the existing incremental aggregation files. Or, configure the session to reinitialize the aggregate cache. Or, if the Integration Service data movement mode was changed in error, change the data movement mode back to its original setting. SM_7051 Aggregate error: index file timestamp is earlier than the timestamp of the Aggregator transformation or mapping. Cause: You modified a mapping containing an Aggregator transformation or modified the Aggregator transformation. Then, when you ran the incremental aggregation session, the Integration Service tried to reuse the existing cache file that was invalid with the Aggregator modifications. Action: The mapping and Aggregator transformation timestamp must be earlier than the cache file. Either reinitialize the aggregate cache or delete the cache file manually. SM_7072 Aggregate Error: Expecting keys to be descending. Cause: You selected the Sorted Input option in an Aggregator transformation, but the data entering the Aggregator transformation is not sorted. Action: Sort the data before the Aggregator transformation, or clear the Sorted Input option. You can sort the data using the Sorted Ports option in the Source Qualifier transformation, or you can use a Sorter transformation. 478 Chapter 63: SM Messages
- 495. SM_7073 Aggregate Error: Expecting keys to be ascending. Same as SM_7072. SM_7087 Aggregate Error: code page <code page> and cached code page <code page> are not two-way compatible. Cause: You changed the session code page using incremental aggregation. The new code page is not compatible with the previous code page. Therefore, the data in the existing aggregate cache is not compatible with the new session code page. Action: To reuse the data in the cache, set the code page of the current session to a compatible code page. Otherwise, reinitialize the cache or manually delete the cache file. SM_7088 Aggregate Error: sort order <sort order> and cached sort order <sort order> mismatch. Cause: You changed the session sort order. The new sort order is not compatible with the previous code page sort order. Therefore, the data in the existing aggregate cache is not compatible with the new session code page. Action: If you want to reuse the data in the cache, set the sort order of the current session to a compatible code page sort order. Otherwise, reinitialize the cache or manually delete the cache file. SM_7089 Aggregate error: Unknown code page <code page> in the aggregation cache. Cause: The Integration Service cannot identify the code page used to create the incremental aggregate cache because the cache was generated in a different server environment with a different code page. Action: Reinitialize the cache or manually delete the cache file. SM_7091 Transformation Parse Fatal Error: Update Strategy Expression did not evaluate to a numeric value. Cause: The update strategy expression you specified in the Update Strategy transformation does not evaluate to a numeric value. Action: Verify that the update strategy expression evaluates to a numeric value. SM_7096 Aggregate Error: Unable to execute cache upgrade utility <utility name>. Cause: The Integration Service failed to upgrade the incremental aggregation files because it could not locate the specified cache upgrade utility. Action: Verify that the cache upgrade utility, pmcacheupgr on UNIX or pmcacheupgr.exe on Windows, exists in the PowerCenter Services installation directory. SM Messages 479
- 496. SM_7099 Fatal Error: Header from incremental aggregation files for Aggregator transformation <transformation name> has invalid data. Cause: The Integration Service failed to upgrade the incremental aggregation files because the files contain corrupt data. Action: If you have a backup of the incremental aggregation files, replace the corrupted files with the backup files and run the session again. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM_7200 Error reading from incremental aggregation files for Aggregator transformation <transformation name>. Cause: The Integration Service failed to upgrade the incremental aggregation files because the Integration Service does not have read permission on the cache directory. Action: Verify that the user configured to start Informatica Services has read permission on the cache directory. SM_7202 The upgrade of the incremental aggregation files for Aggregator transformation <transformation name> failed. Unable to write data to new cache file. Check if enough disk space is available. Cause: The Integration Service failed to upgrade the incremental aggregation files because the cache directory has inadequate disk space or the Integration Service does not have write permission on the cache directory. Action: Check the disk for free space. Or, verify that the user configured to start Informatica Services has write permission on the cache directory. SM_7203 Key length for transformation <transformation name> has changed. Cause: The Integration Service failed to upgrade the incremental aggregation files because you changed the precision for one or more of the group by ports in the Aggregator transformation. Action: To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM_7204 Row size for transformation <transformation name> has changed. Cause: The Integration Service failed to upgrade the incremental aggregation files because you changed the precision for one or more of the ports in the Aggregator transformation that are not defined as group by ports. Action: To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. 480 Chapter 63: SM Messages
- 497. SM_7207 Incremental aggregation upgrade error. Cause: The Integration Service failed to upgrade the incremental aggregation files. Action: See additional error messages for more information. SM_7208 Mapping has been modified since the incremental aggregation files for transformation <transformation name> were last saved. Cause: The Integration Service failed to upgrade the incremental aggregation files because you modified a mapping containing an Aggregator transformation or modified the Aggregator transformation. Then, when you ran the incremental aggregation session, the Integration Service tried to reuse the existing cache file that was invalid with the Aggregator modifications. Action: To reuse the data in the cache, revert to the last version of the mapping. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM_7209 Cache for transformation <transformation name> was created in a precision mode different from the one specified by the session. Cause: The Integration Service failed to upgrade the incremental aggregation files because the Enable High Precision session option used for the incremental aggregation files differs from the option used for the current session. Action: If the Enable High Precision session option was changed in error, change the option back to its original setting. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM_7210 Number of partitions has changed since cache creation. Cause: The Integration Service failed to upgrade the incremental aggregation files because you changed the number of partitions in the session. Action: To reuse the data in the cache, change the number of partitions back to the original value. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM_7211 The Integration Service data movement mode differs from the data movement mode used when the cache was created. Cause: The Integration Service failed to upgrade the incremental aggregation files because you started a session using incremental aggregation after changing the Integration Service data movement mode. The Integration Service cannot access incremental aggregation files created in a different data movement mode. Action: If the Integration Service data movement mode was changed in error, change the data movement mode back to its original setting. Otherwise, delete the existing incremental aggregation files or configure the session to reinitialize the aggregate cache. SM Messages 481
- 498. SM_7217 Error: Failed to expand update override <text> for target instance <target name>. Cause: The Integration Service cannot expand a parameter or variable in the target update override. Action: Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. or Cause: The Integration Service cannot expand the parameter or variable in the target update override due to an internal error. Action: Contact Informatica Technical Support. 482 Chapter 63: SM Messages
- 499. Chapter 64 SORT Messages This chapter includes the following topic: โฆ SORT Messages, 484 Error messages listed numerically. 483
- 500. 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]. Cause: The Integration Service could not allocate memory for the Sorter or Lookup transformation because there is not enough available memory. Action: Free memory resources or increase the swap space on the Integration Service system. You can also reduce the cache size to match the amount of available memory. SORT_40090 There are only <amount of available memory> megabytes of <total memory> available. Either increase the swap space or decrease the Cache Size in the Transformation [transformation name]. Cause: You ran the session on a UNIX Integration Service and the necessary cache size of the specified transformation exceeds the maximum memory allowed for processes that run on the UNIX machine. Action: Increase the memory limit for processes on the UNIX machine. or Same as SORT_40046. SORT_40095 File or filesystem <file or file system name> could not be accessed. Cause: The Integration Service could not access the specified file. Action: Verify you have read permission for the specified file. SORT_40096 Temp file <file name> could not be opened: <error message>. Cause: The Integration Service could not open a temporary file for the Sorter transformation. Action: Verify the user who started the Integration Service has read, write, and execute permissions for the Sorter transformation work directory. SORT_40102 This sort requires at least <value> MB of memory. Cause: You specified too small a value for the Sorter transformation cache size. The Integration Service cannot perform the sort operation. Action: Increase the Sorter transformation cache size. SORT_40111 This sort has been cancelled. Cause: The Integration Service cancelled the sort operation. Action: Check preceding messages to see the cause of the error. 484 Chapter 64: SORT Messages
- 501. SORT_40179 Insufficient space to map <amount of memory> MB of memory: <error message>. Either increase the swap space or decrease the Cache Size in the Transformation [transformation name]. Same as SORT_40046. SORT_40189 The sort library could not create a thread. Cause: The Integration Service system does not have enough resources to run the sort operation. Action: Free Integration Service system resources by closing applications. After you free system resources, restart the workflow. SORT_40304 This operation appears to need <value> MB of memory; excessive paging is possible; continuing. Cause: You specified a Sorter cache size above the minimum required cache size, but the Sorter cache size is small compared to the size of the incoming data. The Integration Service can proceed with the sort operation, but the session will have decreased performance. Action: To increase session performance, increase the Sorter transformation cache size. SORT_40401 A fatal Sort error has occurred in function <function name>. Errno = <error number>. Cause: Internal error. Action: Contact Informatica Technical Support. SORT_40406 In transformation [transformation name], an error has occurred [error message]. Cause: The Integration Service encountered an error at the specified Sorter or Lookup transformation. Action: Read the error message displayed in this error message and other messages in the session log for more information. SORT_40407 In transformation [transformation name] in partition [partition number], an error has occurred [error message]. Cause: The Integration Service encountered an error when it processed a row in the specified partition and transformation. Action: Read the error message displayed in this error message and other messages in the session log for more information. SORT_40409 Internal sorter error <error>. Cause: Internal error. Action: Contact Informatica Technical Support. SORT Messages 485
- 502. SORT_40414 Error: Total row size [row size] in transformation [transformation name] is more than the allowed maximum [8 MB]. Cause: The sum of all port sizes in the specified Sorter or Lookup transformation exceeds 8 MB. Action: Disconnect any port that you do not need in your mapping. Consider redesigning the mapping to reduce the number of ports in the specified transformation. Or, reduce the precision of large string or binary ports. SORT_40415 Work directory <directory name> does not exist. Cause: The directory name specified for the Sorter transformation work directory does not exist. Action: Verify the Work Directory option in the Sorter transformation properties specifies an existing directory. SORT_40416 Work directory <directory> does not have read/write/execute permission. Cause: The user who started the Integration Service does not have read, write, and execute permissions on the Sorter transformation work directory. Action: Grant read, write, and execute permissions for the Sorter transformation work directory to the user who starts the Integration Service. 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. Cause: The Sorter transformation cache size is too large. Action: Reduce the Sorter transformation cache size in the session properties. 486 Chapter 64: SORT Messages
- 503. Chapter 65 SPC Messages This chapter includes the following topic: โฆ SPC Messages, 488 Error messages listed numerically. 487
- 504. SPC Messages SPC_10027 Cannot start process for service <service name> on node <node name>. Process is shutting down. Try again later. Cause: The service is shutting down. You cannot enable the service until it completely shuts down. Action: To enable the service, disable the service, and then enable it again. 488 Chapter 65: SPC Messages
- 505. Chapter 66 SQL Messages This chapter includes the following topic: โฆ SQL Messages, 490 Error messages listed numerically. 489
- 506. SQL Messages SQL_50001 IOutputBuffer::setRowType() API has failed. Cause: The Integration Service failed to generate an output row from the SQL transformation. Action: Review previous error messages for more information. SQL_50002 NULL DB Handle returned. Cause: The Integration Service failed to connect to a database using a dynamic connection with an SQL transformation. Action: The source data contains invalid connection data. The database user name, database password, server, or connect string is not correct for the database. SQL_50003 ScriptName is empty. Cause: The SQL transformation is configured to run an external SQL script but the ScriptName port contains no data. Action: The ScriptName port must contain the name and path of the file containing an SQL script to run for each input row. Verify ScriptName port is connected and the source data contains the file name. SQL_50004 SetProperty failed. Cause: The Integration Service failed to set database properties for an SQL transformation dynamic connection. Action: The dynamic connection contains Advanced Option name-value pairs. Verify that you spelled the options correctly and each option is valid for the database type. The Advanced Options are not case sensitive. SQL_50005 Logical Connection Object Name is empty. Cause: The Integration Service failed to connect to a database for this row because the LogicalConnectionObject port of the SQL transformation contains no data. Action: Verify that the LogicalConnectionObject port is connected and the source data contains a valid connection object name in each row. SQL_50006 FlushOutRow failed. Cause: The Integration Service failed to generate an output row from the SQL transformation. Action: Review previous error messages for more information. 490 Chapter 66: SQL Messages
- 507. SQL_50007 ODL Error has occurred. Please see the pre-defined error port for detailed error message. Cause: The Integration Service encountered a database error while processing an SQL query from the SQL transformation. Action: Review the error messages from the SQL transformation SQLError port. SQL_50008 Number of columns in the select query is greater than the number of output ports in the SQL transformation. Cause: The SQL transformation does not have an output port for each column in the SQL SELECT statement. Action: Add the missing output ports to the SQL transformation. SQL_50009 Static Connection information is inappropriate to create a valid database handle. Cause: The Integration Service cannot connect to the database because the connection defined in Workflow Manager connections is not valid for the SQL transformation. Action: Use a relational database connection for the SQL transformation. Verify the database type in the connection is valid for the SQL transformation. SQL_50010 Error: File handle could not be created. Cause: The Integration Service could not find the script file for the SQL transformation. Action: Verify the script file exists and is accessible by the Integration Service. SQL_50011 The SQL Query entered through the Designer is empty. Cause: An SQL transformation is configured to run query mode. However, the transformation does not have an SQL query. Action: Add an SQL query to the transformation. SQL_50013 Setting the data in target failed. Cause: The Integration Service failed to write output data from the SQL transformation. Action: See previous error messages for more information. SQL_50014 Getting the data from source failed. Cause: The Integration Service was unable to access the source data for the SQL transformation. Action: See previous error messages for more information. SQL Messages 491
- 508. SQL_50015 Failed to connect to the database. Cause: The Integration Service could not connect to the database with the dynamic connection data from the source. Action: Verify the database user name, password, and connect string are correct for the database. SQL_50017 Failed to get the relational connection name attribute from repository. Cause: The Integration Service failed to find the database connection name in the repository. Action: Verify that the database connection name is a valid connection name in Workflow Manager connections. SQL_50018 Failed to get the connections. Cause: The Integration Service could not connect to the database with the dynamic connection. Action: Verify that the database user name, password, and connect string are correct for the database. 492 Chapter 66: SQL Messages
- 509. Chapter 67 SR Messages This chapter includes the following topic: โฆ SR Messages, 494 Error messages listed numerically. 493
- 510. SR Messages SR_17000 Projected column metadata fetch failed. Cause: Internal error. Action: Contact Informatica Technical Support. SR_17001 Maximum column length is zero. Cause: Internal error. Action: Contact Informatica Technical Support. SR_17004 ERROR: Connect failed. SAP driver has not been loaded. Cause: Internal error. Action: Contact Informatica Technical Support. SR_17005 ERROR: Connect failed: SAP error message <SAP message>. Cause: Connection could not be established between PowerCenter and SAP. Action: Consult your SAP administrator. Also see the RFC trace file or SAP system log for more details. SR_17006 Unknown data transfer mode. The mode can only be staging or streaming. Cause: Internal Error. Action: Contact Informatica Technical Support. SR_17007 ERROR: Run failed: SAP error message <ABAP program name or staging file name or Application Source Qualifier form name> SAP <error message>. Cause: There was a problem with the RFC communication with SAP. Action: Get the detailed message from the session log. See the RFC trace file, SAP system log, and SAP documentation for more details. Contact Informatica Technical Support for further assistance. SR_17009 Error in CPIC: <error message>. Cause: You generated the ABAP program for a mapping on one SAP system, but you ran the session with the mapping on another SAP system. Action: Regenerate the ABAP program for the mapping against the source system and run the session on the same SAP system. SR_17010 Error in parsing filter expression: <expression>. Cause: SAP could not parse a filter expression. 494 Chapter 67: SR Messages
- 511. Action: If you entered a filter override in the session properties, verify the syntax. If you entered a filter override in the mapping properties, open the mapping in the Designer and validate the filter. SR_17011 Error in passing parameters to SAP system: <SAP message>. Cause: The SAP system is down. Action: Check with SAP system administrator. SR_17012 Could not start program in Background mode: <SAP message>. Cause: You may not have permission to release the background job. Action: Verify with the SAP administrator that you have proper permissions. You must have authorization on S_DATASET, S_PROGRAM, and S_BTCH_JOB objects. SR_17013 Could not get status information for a Background job: <SAP message>. Cause: The connection to the SAP system is broken. Action: Check with your SAP system administrator or contact Informatica Technical Support. SR_17014 ERROR: File open failed. Cause: The Integration Service could not open the staging file. Action: Verify the path to the file. SR_17015 Could not delete the Staging File <filename>: <SAP message>. Cause: You accessed the staging file through NFS mount, and the Integration Service user may not have write permission on the staging file or directory. Action: Get write permissions from the system administrator for the Integration Service user. SR_17016 The program <program name> was generated but not installed for mapping <mapping name> version <version number>. Cause: You generated an ABAP program for this mapping, but you did not install it on the SAP system. Action: Open the Generate and Install dialog box in the Mapping Designer and install the ABAP program for the mapping. SR_17020 Memory allocation for tree <tree name> failed. Cause: Insufficient heap memory allocation. Action: Reduce the number of processes running, or increase the virtual memory on the Integration Service host. SR Messages 495
- 512. SR_17021 ERROR in getting information for SetId <SetID name> and Table Name <table name>. Cause: You might have transported the ABAP program to a system that contains different hierarchy and/or master table information. Action: Verify the SAP source matches the definition in your repository. or Cause: RFC error. Action: Contact your SAP administrator. SR_17022 No hierarchy data found for <hierarchy name>. Cause: The leaf nodes of the hierarchy are empty. There are no key values. Action: Verify the hierarchy from which you are trying to extract. SR_17023 Tree is inconsistent. Cause: Internal SAP error. Action: Contact your SAP administrator. SR_17024 Error in passing parameters to SAP system for hierarchy with SetID <setid name> and TableName <table name>. Cause: SAP could not import hierarchy information from PowerCenter, possibly because the SAP administrator did not run the transport program, YPMPARSQ. Action: Have the SAP administrator run the program YPMPARSQ from the ZERP development class. SR_17025 ERROR: Run failed for hierarchy with SetID <setid name> and TableName <table name>: SAP error message <ABAP program name or staging filename or Application Source Qualifier form name>. Cause: Either the SAP system failed or the program to extract from a hierarchy failed. Action: Check with your SAP administrator. SR_17026 No program name found for stream mode for this mapping <mapping name> version <version number>. Please use the PowerCenter Designer to generate and install program for this mapping. Cause: Either you have not installed an ABAP program for this mapping, or you are trying to run a session in the wrong mode. Action: If you have not installed the ABAP program, use the Designer and install the ABAP program. If you have installed the ABAP program, make sure the source type in the session properties matches the program mode of the installed ABAP. 496 Chapter 67: SR Messages
- 513. SR_17027 No program name found for file mode for this mapping <mapping name> version <version number>. Please use the PowerCenter Designer to generate and install program for this mapping. Cause: Either you have not installed an ABAP program for this mapping, or you are trying to run a session in the wrong mode. Action: If you have not installed the ABAP program, use the Designer and install the ABAP program. If you have installed the ABAP program, make sure the source type in the session properties matches the program mode of the installed ABAP. 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. Cause: You saved the repository with the mapping open after you installed the ABAP program on the application server. Action: In the Designer, open the mapping and save the repository. Then install the ABAP program. SR_17055 The time at which a file mode program was installed for this mapping is older than the time at which this mapping was saved last. The mapping name is <mapping name>, version <version number> and the program name is <program name>. Please regenerate and install the program using PowerCenter Designer for this mapping. Cause: You saved the repository with the mapping open after you installed the ABAP program on the application server. Action: In the Designer, open the mapping and save the repository. Then install the ABAP program. SR_17057 Unable to retrieve code page information for code page ID <code page ID>. Cause: The pmlocale.bin file is missing or does not have the code page ID you selected in the database connection. Action: Verify the existence of the pmlocale.bin file and the code page information. SR_17058 Unable to create a locale from code page <code page> <code page ID>. Cause: Internal error. Action: Contact Informatica Technical Support. SR_17059 SAP Code page: <code page ID> is not compatible with the user selected code page <code page>. Cause: The SAP code page is not compatible with the code page you selected in the database connection. SR Messages 497
- 514. Action: Select a code page that is compatible with the Integration Service and the SAP system. SR_17085 SAP Extraction Version could not be verified. Cause: The Integration Service could not verify the version of the transport files. Action: Verify that the SAP system is running and the transports are activated. Call Informatica Technical Support. SR_17061 Last error encountered is: Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17062 Error in RFC program. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17063 Error in network communications. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17064 SAP logon error. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17065 SAP system exception raised. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17067 RFC protocol error. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. 498 Chapter 67: SR Messages
- 515. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17068 RFC internal error. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17069 RFC registered server was cancelled. Cause: The PowerCenter Client or Integration Service cannot communicate with the mySAP or SAP BW system. Action: See the additional error message for more information. Also see the SAP trace file for more information. SR_17073 No program was generated as mapping contains only SAP Information Hierarchies. Cause: You generated a program for a mapping that has a SAP table reader source of type hierarchy. Action: You do not need to generate a program if the mapping has a SAP table reader source that is of type hierarchy. SR_17090 The Application Source Qualifier <Application Source Qualifier> has invalid user defined query <query> with character error at <number> location. Cause: You entered a query containing characters that are not valid in the source database connection code page. Action: Change the query to contain characters in the source database connection code page. SR_17091 The Application Source Qualifier <Application Source Qualifier> has invalid filter clause <filter> with character error at <number> location. Cause: You entered a filter condition containing characters that are not valid with the source database connection code page. Action: Change the filter condition to contain characters included in the source database connection code page. SR_17092 The Application Source Qualifier <Application Source Qualifier> has invalid join and/or filter override <join override> with character error at <number> location. Cause: You entered a join condition and/or a source filter condition that contain characters that are not valid in the source database connection code page. SR Messages 499
- 516. Action: Change either the join, filter, or both conditions to contain characters in the source database connection code page. 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. Cause: You defined a partition key for a port in the Application Source Qualifier that you deleted. Action: Edit the session to remove the partition key from the Application Source Qualifier. Then save the new partition information in the session and run again. or Action: Change the application connection code page to UTF-8 encoding. 500 Chapter 67: SR Messages
- 517. Chapter 68 TE Messages This chapter includes the following topic: โฆ TE Messages, 502 Error messages listed numerically. 501
- 518. TE Messages TE_7014 Unknown transformation type. Cause: Internal error. You may have repository inconsistencies. Action: Contact Informatica Technical Support. TE_7016 Failed to allocate/initialize server transformation <transformation name>. Cause: Internal allocation or initialization error. Action: Contact Informatica Technical Support. TE_7017 Failed to initialize server transformation <transformation name>. Cause: Internal error. Action: Contact Informatica Technical Support. TE_7018 Failed to create row data. Same as TE_7017. TE_7019 Failed to initialize Sequence Transformation. Same as TE_7017. TE_7020 Unbound field <field name> in Source Qualifier <transformation name>. Same as TE_7017. TE_7092 Error: Data cache size specified for this session must be at least <minimum number of bytes> bytes. Cause: The session failed due to an insufficient amount of cache memory. Action: Increase the data cache size. TE_7102 TE Init Error: Failed to get the last saved time for mapping <mapping name>. Cause: The repository database server could not provide the last saved time when the mapping was saved. A previous problem with the database might have caused some data inconsistencies. Action: Contact Informatica Technical Support. TE_7104 Error occurred while creating group <group number> of target <target name>. Cause: During initialization, the Integration Service failed to create a group object. Action: Check the previous message in the log for more information. TE_7105 Error occurred while creating transformation <transformation name>. Cause: During initialization, the Integration Service failed to create a transformation object. 502 Chapter 68: TE Messages
- 519. Action: Check the previous message in the log for more information. TE_7106 Failed to allocate/initialize/target <target name> group ID <group ID>. Cause: During initialization, the Integration Service failed to create an XML group ID. Action: Check the previous message in the session log for more information. TE_7109 Fatal Error: Mapping conflicts with RealTime commit. Cause: The mapping contains two active sources in a pipeline. You cannot use two active sources in a pipeline for a real-time session. Action: Use only one active source in a pipeline for a real-time session. TE_7111 Error: RealTime commit does not allow partition types other than pass- through for each partitioning point. Cause: You selected a partition type other than pass-through for a partition point for a real-time session. Action: When you run a real-time session, select pass-through partitioning at all partition points. or Action: partition points. TE_7112 Error: Guaranteed Message Delivery does not allow XML targets in the mapping. Cause: The session contains an XML target. When you enable message recovery for a session, you cannot use an XML target in the mapping. Action: Use a target other than an XML target in the mapping for the session. or Action: Do not use message recovery for the session. To remove message recovery for the session, clear the Enable Recovery option in the session properties. TE_7113 Error: Guaranteed Message Delivery does not allow mapping variables in the mapping. Cause: The session contains mapping variables. When you enable message recovery for a session, you cannot use mapping variables in the mapping. Action: Remove the mapping variables from the session. or Action: Do not use message recovery for the session. To remove message recovery for the session, clear the Enable Recovery option in the session properties. TE Messages 503
- 520. TE_7114 Error: Guaranteed Message Delivery does not allow a dynamic lookup cache in the mapping. Cause: The session contains a dynamic lookup cache. When you enable message recovery for a session, you cannot use a dynamic lookup cache in the mapping. Action: Use a static lookup cache in a mapping for the session. or Action: Do not use message recovery for the session. To remove message recovery for the session, clear the Enable Recovery option in the session properties. TE_7115 Error: The source configured for Guaranteed Message Delivery cannot be a Joiner transformation master source. Cause: The session contains a mapping with a JMS source that is a Joiner master source. When you enable message recovery for the session, the source cannot be the Joiner master source. Action: Do not use message recovery for the session. To remove message recovery for the session, clear the Enable Recovery option in the session properties. TE_7116 Error: Guaranteed Message Delivery does not allow partition types other than pass-through for each partitioning point. Cause: You enabled message recovery and selected a partition type other than pass- through for a partition point. Action: When you enable message recovery, you must select pass-through partitioning at all partition points in the session properties. or Action: Do not use message recovery for the session. To remove message recovery for the session, clear the Enable Recovery option in the session properties. TE_7117 Error: RealTime commit does not allow non-realtime SDK targets in the mapping. Cause: You configured a session using Real-time Flush Latency as a session condition. However, the mapping contains an SDK target definition that you cannot use with real-time sessions. Action: Enter 0 for the Real-time Flush Latency session condition. TE_7122 Error: Session is running in UDC mode; however, the target [target name] is not receiving transactions from any upstream transformations. Cause: You ran a user-defined commit session, but you did not connect the specified target to an upstream effective transaction generator. Action: Connect an effective transaction generator, such as a Transaction Control transformation, to the target. 504 Chapter 68: TE Messages
- 521. TE_7127 Error: Real-time commit does not allow user-defined commit. Cause: You configured a session to read messages from an MQSeries source with the FlushLatency(n) filter condition. The commit type was set to user-defined commit. This is not allowed. Action: To run a workflow in real time with the FlushLatency(n) filter condition, select source-based commit as the commit type. or Action: To run a workflow with user-defined commit as the commit type, remove the FlushLatency(n) filter condition. If you want to run a workflow in real time with the user-defined commit type, enter the ForcedEOQ(n) filter condition. TE_7131 Error: The transformation <transformation> is not configured to propagate transactions. Real-time is not supported. Cause: You configured a session using Real-time Flush Latency as a session condition. Or, you configured a session to read messages from an MQSeries source with the FlushLatency(n) filter condition. However, the pipeline configuration prevents the session from being run in real time. Action: If you do not want to run the session in real time, set the value for the Real- time Flush Latency session condition to 0. For a mapping with an MQSeries source, remove FlushLatency(n) function from the filter condition. or Action: To run the session in real time, verify that your pipeline does not contain any real-time limitations. TE_7133 Master Input for Unsorted Joiner < joiner transformation name > cannot be partitioned because Joiner is not a partition point. Cause: You partitioned the master pipeline without adding a partition point at the unsorted Joiner transformation. This can cause input rows from the same key value to be routed to different partitions. Action: Add a hash auto-keys partition point at the Joiner transformation to ensure data of the same key value is routed to the same partition. TE_7134 Master Input for Sorted Joiner <joiner transformation name> is partitioned. Please refer to documentation to find out how to insure that all input rows that have the same key are routed to the same partition of the Joiner. Cause: You partitioned the master pipeline, which contains a sorted Joiner transformation. If you did not group the sorted data before passing it to the Joiner transformation, you can get unexpected results. Action: Verify that you configured partitions in the master pipeline to pass sorted and grouped data to the sorted Joiner transformation. TE Messages 505
- 522. TE_7135 Error: Recovery is enabled for more than one source in the concurrent source set. Recovery is not supported for such mappings. The sources enabled for GMD in the concurrent source set are <source names>. Cause: You attempted to perform session recovery on a mapping that contains one target load order group with multiple sources, and one or more of those sources is a real-time source. The real-time sources in the target load order group are connected to a multiple input group transformation or target. Action: If the sources are connected to a Joiner transformation, you can enable the backward compatibility flag. The backward compatibility flag allows the Integration Service to read sources connected to a Joiner transformation sequentially as it did in versions prior to 6.x. or Action: If the sources in the target load order group are connected to a multiple input group other than the Joiner transformation, disable session recovery. To remove message recovery for the session, clear the Enable Recovery option in the session properties. 506 Chapter 68: TE Messages
- 523. Chapter 69 TIB Messages This chapter includes the following topic: โฆ TIB Messages, 508 Error messages listed numerically. 507
- 524. TIB Messages TIB_34001 Cannot get connection property <connection property>. Cause: Internal error. The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. TIB_34002 Invalid subject <subject>. Cause: The Subject attribute in the application connection for TIBCO sources and targets is invalid. Action: Enter a valid subject name for the Subject attribute in the application connection for the TIBCO source or target. or Cause: The ReplySubject value in the session properties is invalid. Action: Enter a valid reply subject name for the ReplySubject property in the session properties. or Cause: A TIBCO target message contains an invalid subject. Action: Verify that the value for the subject for TIBCO target messages is valid. For more information about subject names, see the TIBCO documentation. TIB_34003 Cannot get source property <source property>. Cause: Internal error. The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. TIB_34004 Invalid queue limit policy <queue limit policy>. Cause: Internal error. The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. TIB_34005 Queue maximum event limit <number> must be greater than or equal to 0. Cause: The queue maximum event limit is invalid. The value must be greater than or equal to 0. Action: Enter a queue maximum event limit of at least 0. TIB_34006 Queue discard amount <number> must be greater than or equal to 0. Cause: The queue discard amount value is invalid. The value must be greater than or equal to 0. Action: Enter a queue discard amount value of at least 0. 508 Chapter 69: TIB Messages
- 525. TIB_34007 Idle time <number> must be greater than or equal to -1. Cause: The value for the Idle Time session condition is invalid. The value must be greater than or equal to -1. Action: Enter a value for the Idle Time session condition of at least -1. TIB_34008 Message count <number> must be greater than or equal to -1. Cause: The value for the Message Count session condition is invalid. The value must be greater than or equal to -1. Action: Enter a value for the Message Count session condition of at least -1. TIB_34009 Real-time flush latency <number> must be greater than or equal to 0. Cause: The value for the Real-time Flush Latency session condition is invalid. The value must be greater than or equal to 0. Action: Enter a value for the Real-time Flush Latency session condition of at least 0. TIB_34010 Cannot get target property <property>. Cause: Internal error. The PowerCenter repository contains inconsistencies. Action: Contact Informatica Technical Support. TIB_34011 Send interval <number> must be greater than or equal to 0. Cause: The value for Send Interval is invalid. The value must be greater than or equal to 0. Action: Enter a value for Send Interval of at least 0. TIB_34012 Time limit <number> must be greater than or equal to 0. Cause: The value for Time Limit is invalid. The value must be greater than or equal to 0. Action: Enter a value for Time Limit of at least 0. TIB_34014 Reader time limit <number> must be greater than or equal to 0. Cause: The invalid value for Reader Time Limit is invalid. The value must be greater than or equal to 0. Action: Enter a value for Reader Time Limit of at least 0. TIB_34015 Invalid cmName <cmName>. Cause: The CM name in the application connection for the TIBCO source or target is invalid. Action: Enter a valid CM name. TIB_34021 Invalid field map <field map value>. Cause: Internal error. The PowerCenter repository contains inconsistencies. TIB Messages 509
- 526. Action: Contact Informatica Technical Support. TIB_34022 Failed to confirm certified message: <TIBCO error message>. Cause: The Integration Service could not confirm the specified certified message. Action: Consult the TIBCO documentation for instructions to correct the error. TIB_34023 Invalid IP address <IP address>. Should be either unsigned integer or in the format of a.b.c.d, where a, b, c and d range from 0-255. Cause: The IP address for the column is invalid. The datatype for the column should be uint. The value of the column should be in the format of a.b.c.d, where a, b, c, and d range from 0-255. For example, 300.300.300.300 is an invalid value for the column, whereas 127.0.0.1 is a valid value for the column. Action: Verify that the data contains the correct value for IP address. TIB_34024 Invalid IP port <port>. Should range from <nunber>-<number>. Cause: The port for the column is invalid. The value should range from 1 to 65,535. Action: Verify that the data contains the correct value for the port. TIB_34025 Incompatible datatype for field <field>. Cause: Some connected ports in the mapping have datatypes that are not compatible with the message data fields. Action: Modify the mapping to include datatypes that are compatible. TIB_34026 Data overflow happened when trying to insert value <value> into field of type <datatype>. Cause: The Integration Service could not pass all the data from one column to another. The specified value is too large for the column with the specified datatype. Action: Modify the datatype for the column in the mapping. TIB_34027 Invalid date. Cause: The date value for the column is invalid. Action: Check the data. Make sure the data contains valid values for the date. TIB_34028 Data overflow. Cause: The Integration Service could not pass all the data from one column to another. The precision of the output port might be larger than the precision of the input port. For example, the datatype of the output port is int64 and the datatype of the input port is int8. The precision of the output port is higher than the precision of the input port. As a result, the data might contain inconsistencies. The row was rejected. 510 Chapter 69: TIB Messages
- 527. Action: Modify the mapping by changing the precision or datatypes of the ports so that the precision of the output port is greater than or equal to the precision of the output port. TIB_34029 Invalid value or data overflow. Cause: The data contained an invalid value for a column. Action: Check the data. Verify that the data contains values for the column, which are valid. or Cause: The Integration Service could not pass all the data from one column to another. The data contains inconsistencies. The row was rejected. Action: Modify the mapping to include datatypes that are compatible. TIB_34030 Data overflow happened when trying to insert value <value> into field of type <type>. Cause: Some connected ports in the mapping have different datatypes. The input port has a larger datatype than the output port. As a result, the Integration Service could not pass all the data during the session. Action: Modify the mapping so that the connected columns contain datatypes of a similar range. or Cause: The Integration Service could not pass all the data from one column to another. The specified value is too large for the column with the specified datatype. Action: Modify the datatype for the column in the mapping. TIB_34031 Datatype of <datatype> is expected to be msg for field <field>. Cause: You passed invalid data to a column with the datatype msg. The Integration Service rejected the row. Action: Check the data. The TIBCO data should be of the datatype msg. TIB_34032 Extracting data for field <field> failed: <TIBCO error message>. Cause: The Integration Service could not read data from the specified field. Action: Consult the TIBCO documentation for information about fixing the error. TIB_34033 Data conversion failed for field <field>: <TIBCO error message>. Cause: The Integration Service could not convert the data for the specified field from one datatype to another. Action: Consult the TIBCO documentation for information about fixing the error. TIB Messages 511
- 528. TIB_34034 Failed to add a field <field> to a message: <TIBCO error message>. Cause: The Integration Service encountered an error while adding a message field to the TIBCO target definition. Action: Consult the TIBCO documentation for information about fixing the error. TIB_34035 Failed to pre-register listener <listener name>: <TIBCO error message>. Cause: The Integration Service could not pre-register the specified subscriber. Action: Consult the TIBCO documentation for instructions to correct the error. TIB_34036