Message Reference > C Message Codes > CMN Messages
  

CMN Messages

CMN_1003 Server port not specified.

Explanation:
You did not specify the Integration Service port in the Administrator tool.
User Response:
In the Administrator tool, enter a valid value for the Integration Service port.

CMN_1006 Failed to connect to repository.

Explanation:
Connection information may be missing or invalid in the Administrator tool.
User Response:
In the Administrator tool, 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.

Explanation:
An internal error occurred. Related error messages may appear to further diagnose the error.
User Response:
Contact Informatica Global Customer Support.

CMN_1009 Internal error: Failed to execute child process.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
An error occurred while the system allocated shared memory.
User Response:
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.

Explanation:
Insufficient shared memory allocation.
User Response:
Check the session log for related error messages. If none appear, contact Informatica Global Customer Support.

CMN_1017 Error encountered decrypting password.

Explanation:
You entered an invalid password in the Administrator tool.
User Response:
Make sure you entered the password correctly. Passwords may be case sensitive. If the password is correct, contact Informatica Global Customer Support.

CMN_1021 Database driver event.

Explanation:
A database driver event occurred.
User Response:
Check the session log for a related database driver error message. If necessary, see the database documentation for an action.

CMN_1022 Database driver error.

Explanation:
A database driver error occurred.
User Response:
Check the session log for a related database driver error message. If necessary, see the database documentation for an action.

CMN_1023 Database license key not specified.

Explanation:
You did not specify the database license key in the Administrator tool.
User Response:
In the Administrator tool, enter a valid database license key.

CMN_1024 Invalid database license key <license key>.

Explanation:
You entered an invalid license key in the Administrator tool.
User Response:
In the Administrator tool, specify a valid database license key.

CMN_1026 Incorrect repository version.

Explanation:
The repository and software versions do not match. One has been updated, while the other has not been updated.
User Response:
If the repository is older, upgrade the repository. If the software is older, upgrade the software.

CMN_1028 ERROR: Illegal operation on a non-mutex.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1029 ERROR: Illegal operation on a mutex.

Explanation:
Internal error.
Response:
Contact Informatica Global Customer Support.

CMN_1030 ERROR: Illegal unlock operation -- mutex not locked.

Explanation:
Internal error.
Response:
Contact Informatica Global Customer Support.

CMN_1035 Sybase event.

Explanation:
A Sybase event has occurred.
User Response:
Check the session log for a related Sybase event. If necessary, see the Sybase documentation for appropriate action.

CMN_1036 Sybase error.

Explanation:
A Sybase error has occurred.
User Response:
Check the session log for a related Sybase error message. If necessary, see the Sybase documentation for appropriate action.

CMN_1037 Oracle event.

Explanation:
An Oracle event has occurred.
User Response:
Check the session log for a related Oracle event. If necessary, see the Oracle documentation for appropriate action.

CMN_1038 Oracle error.

Explanation:
An Oracle error has occurred.
User Response:
Check the session log for a related Oracle error message. If necessary, see the Oracle documentation for appropriate action.

CMN_1040 SQL Server Error.

Explanation:
A Microsoft SQL Server error has occurred.
User Response:
Check the session log for a related Microsoft SQL Server error message. If necessary, see the Microsoft SQL Server documentation for appropriate action.

CMN_1044 DB2 Error.

Explanation:
A DB2 error has occurred.
User Response:
Check the session log for a related DB2 error message. If necessary, see the DB2 documentation for appropriate action.

CMN_1046 ODBC Error.

Explanation:
You created an ODBC data source, but no longer have the underlying native connectivity software or environment.
User Response:
Reconfigure the native connectivity environment and then run the session.
Explanation:
A session with DB2 UDB EEE sources or targets failed when the Integration Service ran on AIX and used both the DataDirect ODBC driver manager and the DB2 UDB EEE CAE ODBC driver. This problem occurred because the DataDirect ODBC driver manager and the DB2 UDB EEE CAE ODBC driver are not compatible.
User Response:
Do not use an ODBC connection. Be sure to only use a native DB2 CAE connection to a DB2 database.

CMN_1049 PM error.

Explanation:
This is a generic error.
User Response:
Check the session log for related error messages.

CMN_1050 PM event.

Explanation:
This is a generic error.
User Response:
Check the session log for related error messages.

CMN_1053 Error information.

Explanation:
This is a generic error.
User Response:
This message varies depending on the error. Check the session log for more specific messages.

CMN_1054 Memory allocation error.

Explanation:
Error in memory allocation. The system resources may be low.
User Response:
Close any unnecessary applications and restart the system. If the problem persists, you may need to add RAM to the system.

CMN_1055 Error preparing SQL statement to fetch lookup data.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1056 Error executing SQL statement to fetch lookup data.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1057 Error in fetching lookup data from database.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1061 ERROR: Process terminating on signal/exception.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1062 Error creating lookup cache.

Explanation:
An error occurred while creating the lookup cache.
User Response:
Check the session log for related error messages.

CMN_1063 ERROR: Multiple match found in lookup.

Explanation:
In a Lookup transformation, you specified the Lookup Policy on Multiple Match option to return this error message when encountering multiple occurrences of data.
User Response:
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.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1065 Error in lookup SQL statement execute.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1066 Error in lookup SQL statement fetch.

Explanation:
A port name or datatype specified in a Lookup transformation does not match the lookup table in the database. Both port names and datatypes must match exactly.
User Response:
This message should be followed by information naming the port or table. Correct the port name or datatype in the Lookup transformation, and save the mapping.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. You may have logged in incorrectly.
User Response:
Log in with the correct information. User names and passwords may be case sensitive.
Explanation:
The Integration Service failed to connect to the database containing the lookup table. The database containing the lookup table may be down.
User Response:
Make sure the database is up before running the session again.

CMN_1075 ERROR: Data overflow.

Explanation:
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.
User Response:
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.

Explanation:
The configuration parameters for the database may be incorrect.
User Response:
Check the database connection defined in the Workflow Manager.
Explanation:
The database or network may be down.
User Response:
Make sure they are both up before running the session again.

CMN_1077 Lookup table not found in the database.

Explanation:
The lookup table may have been deleted or renamed since the mapping was last saved.
User Response:
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.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1079 WARNING: Lookup table contains no data.

Explanation:
The lookup table specified in the mapping contains no data because you specified an invalid lookup table.
User Response:
Make sure the mapping contains the correct name of the lookup table.
Explanation:
The lookup table specified in the mapping is empty.
User Response:
Import or enter the correct data for the lookup table.

CMN_1082 ERROR: Invalid lookup condition.

Explanation:
In a Lookup transformation, the lookup condition is invalid or blank.
User Response:
Correct the invalid lookup condition.

CMN_1083 Error encountered encrypting password.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1086 <Transformation name>: Number of error exceeded threshold number.

Explanation:
The specified transformation reached the error threshold.
User Response:
Examine the incoming data and the transformation configuration to locate the problem, then correct the problem. Or increase the error threshold.

CMN_1087 ERROR: PowerMart Username not specified.

Explanation:
You did not specify a user name in the Administrator tool.
User Response:
Enter a valid value for user name.

CMN_1088 ERROR: PowerMart Password is not specified.

Explanation:
You did not specify a password in the Administrator tool.
User Response:
In the Administrator tool, enter a valid value for Password. Passwords must be in 7-bit ASCII.

CMN_1089 ERROR: Invalid lookup connect string.

Explanation:
A Lookup transformation contains an invalid location for its lookup table.
User Response:
Check the location of the lookup table, and then enter the correct location in the Lookup transformation.

CMN_1093 ERROR: Invalid join condition supplied.

Explanation:
A Joiner transformation in the mapping specifies an invalid join condition.
User Response:
Make sure the condition for each Joiner transformation in the session contains at least one valid join.
Explanation:
If each Joiner transformation uses valid conditions, you may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_1094 ERROR: No valid field from the master relation.

Explanation:
One of the Joiner transformations in the mapping has a master port that is not used in the join condition or the output port.
User Response:
Make sure to use the master ports as required.
Explanation:
If there are no extraneous input ports connected to the Joiner transformations, you may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_1095 ERROR: Field name used in join not found in transform definition.

Explanation:
The Integration Service could not locate a port specified in the Joiner transformation. You may have repository inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_1096 ERROR: Operator not supported in the join condition.

Explanation:
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.
User Response:
Edit the join condition in the session properties, using an equal sign (=) as an operator.

CMN_1097 ERROR: No valid output field.

Explanation:
A Joiner transformation has no output links. Each Joiner transformation needs to have at least one output link.
User Response:
Make sure each Joiner transformation has at least one linked output port.

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

Explanation:
The directory specified for the index and data caches has run out of memory.
User Response:
Free up disk space in the cache directory.
Explanation:
The Informatica services account or the operating system user in the operating system profile does not have the appropriate privileges to access that directory.
User Response:
Grant write permission on the directory to the Informatica services account or the operating system user in the operating system profile.

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

Explanation:
In the mapping, one Source Qualifier transformation has been linked to two Joiner transformations in the same target load order group, and has been specified as the master source in one Joiner transformation and the detail source in the other.
User Response:
Edit the Joiner transformations so the same Source Qualifier transformation is the master source in both Joiner transformations in the same target load order group.
If you need to keep the Source Qualifier transformation as the master source in one Joiner transformation and the detail source in the other, create a separate target load order group and place one of the Joiner transformations in that second group.

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

Explanation:
In the mapping, one Source Qualifier transformation has been linked to two Joiner transformations in the same target load order group, and has been specified as the master source in one Joiner transformation and the detail source in the other.
User Response:
Edit the Joiner transformations so the same Source Qualifier transformation is the master source in both Joiner transformations in the same target load order group.
If you need to keep the Source Qualifier transformation as the master source in one Joiner transformation and the detail source in the other, create a separate target load order group and place one of the Joiner transformations in that second group.

CMN_1101 ERROR: Alter the mapping and place the target tables violating this constraint in different target load order groups.

Explanation:
In the mapping, one Source Qualifier transformation has been linked to two Joiner transformations in the same target load order group, and has been specified as the master source in one Joiner transformation and the detail source in the other.
User Response:
Edit the Joiner transformations so the same Source Qualifier transformation is the master source in both Joiner transformations in the same target load order group.
If you need to keep the Source Qualifier transformation as the master source in one Joiner transformation and the detail source in the other, create a separate target load order group and place one of the Joiner transformations in that second group.

CMN_1102 ERROR: No ports in the join condition are connected.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1103 WARNING: No row found from the master relation. Joiner will not produce any output row.

Explanation:
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.
User Response:
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.

Explanation:
The mapping contains an invalid datatype conversion.
User Response:
In the Designer, validate the mapping to locate the invalid conversion.

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

Explanation:
The index cache ran out of memory, causing the Integration Service to use the index file at a local directory that ran out of disk space as well.
User Response:
This message is preceded by a file error. Correct the file error before running the session again.

CMN_1106 ERROR: Index file operation error in Joiner.

Explanation:
This is a file error. It is followed by another message naming the Joiner and the specific file error.
User Response:
Correct the file error before running the session again.

CMN_1107 ERROR: Data file operation error in Joiner.

Explanation:
This is a file error. It is followed by another message naming the Joiner and the specific file error.
User Response:
Correct the file error before running the session again.

CMN_1108 ERROR: PowerMart product license key not specified.

Explanation:
You did not specify the PowerCenter product license key in the Administrator tool.
User Response:
Specify a valid product license key in the Administrator tool.

CMN_1109 ERROR: Invalid PowerMart product license key <key name>.

Explanation:
The specified PowerCenter product license key listed in the Administrator tool is invalid.
User Response:
In the Administrator tool, enter a valid Informatica product license key. If the license key is accurate, contact Informatica Global Customer Support.

CMN_1111 Error encountered decrypting PowerMart password.

Explanation:
The Integration Service encountered an invalid password in the Administrator tool.
User Response:
Check the password in the Administrator tool.

CMN_1120 Error <error code> getting status of attachment file <file name>.

Explanation:
The session is configured to send post-session email with an attached file. The Informatica services account or the operating system user in the operating system profile does not have read permission on the attachment file directory.
User Response:
Grant read permission on the attachment file path to the Informatica services account or the operating system user in the operating system profile.

CMN_1121 Attachment file <file name> not found.

Explanation:
You configured a session for post-session email with an attached file. The Integration Service on UNIX could not locate specified file.
User Response:
Verify the directory and file name for the attachment file are entered correctly in the session properties. Verify the file exists in the specified directory.

CMN_1122 Attachment file <file name> is not a regular file.

Explanation:
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.
User Response:
Specify a regular attachment file in the session for post-session email.

CMN_1123 Error opening attachment file <file name> for read.

Explanation:
The session is configured to send post-session email with an attached file. The Integration Services account or the operating system user in the operating system profile may not have read permissions on the attachment file.
User Response:
Grant read permissions on the attachment file to the Informatica services account or the operating system user in the operating system profile.

CMN_1124 Error reading from attachment file <file name>.

Explanation:
A system error, such as disk corruption, occurred while a Integration Service on UNIX tried to attach a file to a post-session email.
User Response:
Resolve the system error condition.

CMN_1125 Error opening temporary email <temporary file name> file for write.

Explanation:
An Integration Service on UNIX encountered an error trying to create post-session email. The directory from where the Integration Service was started does not have write permissions for the Integration Services account.
User Response:
Make sure the directory has write permissions.

CMN_1126 Error writing to temporary email file (out of disk space?).

Explanation:
The Integration Service on UNIX encountered an error creating post-session email, possibly due to lack of disk space.
User Response:
Make sure there is sufficient disk space on the machine hosting the Integration Service.

CMN_1127 Warning: Error in deleting temporary email file.

Explanation:
The Integration Service on UNIX could not delete a temporary file name used to create post-session email.
User Response:
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.

Explanation:
An error occurred while the Integration Service on UNIX tried to execute a shell command. The listed error code is a UNIX error code.
User Response:
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.

Explanation:
The rmail UNIX command used to send email returned an error. The listed error code is a UNIX error code.
User Response:
Check the rmail documentation.

CMN_1134 This PowerMart Server build does not support database type (Microsoft SQL Server).

Explanation:
The Integration Service on UNIX tried to load Microsoft SQL Server as a target database using native drivers. The Integration Service on UNIX does not support Microsoft SQL Server database type.
User Response:
Use the DataDirect ODBC SQL Server driver for UNIX to load Microsoft SQL Server.

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

Explanation:
An application error occurred.
Note the file name and line number and contact Informatica Global Customer Support.

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

Explanation:
The session failed because you loaded to Sybase 11 and configured the Table Name Prefix option in the mapping target instance or in the session properties.
User Response:
If you load to multiple Sybase 11 tables with different owners, create views of all the target tables in one database. Ensure that the owner of the views has all required permissions on the target tables. Create the database connection in the Workflow Manager using the target owner as the user in the connection. Or, if the target tables have the same owner, make sure the user in the database connection is the owner of the targets.

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

User Response:
Recache the lookup source.

CMN_1557 The precision is different from the saved disk cache.

Explanation:
The Lookup transformation uses a persistent named cache, and the high precision option for the session was enabled or disabled between session runs. The precision setting for the session differs from the precision setting for the lookup cache.
User Response:
Recache the lookup source, or change the high precision setting to the previous setting.

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

Explanation:
The Lookup transformation uses a persistent named cache, and the Integration Service data movement mode was changed between session runs.
User Response:
Recache the lookup source, or change the data movement mode to the previous mode.

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

Explanation:
The Lookup transformation uses a persistent named cache, and the code page for the Integration Service was changed between session runs. The Integration Service and cache code pages are no longer compatible.
User Response:
Recache the lookup source, or change the code page to the previous code page.

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

Explanation:
The system could not find a code page for the source. The pmlocale.bin file might be corrupt or incomplete.
User Response:
Install a complete pmlocale.bin file from the installation DVD.

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

Explanation:
The system could not locate locale information for the source. The pmlocale.bin file that contains the locale information might be corrupt or incomplete.
User Response:
Install pmlocale.bin file from the installation DVD.

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

Explanation:
The Lookup transformation uses a persistent named cache, and the Unicode mode sort order was changed between session runs.
User Response:
Recache the lookup source, or change the sort order to the previous sort order.

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

Explanation:
In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value.
User Response:
Increase the lookup index cache size to the value recommended in the error message.

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

Explanation:
In the Designer or Workflow Manager, you entered a value for the lookup index cache that is less than the recommended value.
User Response:
Increase the lookup index cache size to the value recommended in the error message.

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

Explanation:
The precision for the lookup input port and the lookup output port do not match.
User Response:
In the lookup condition, verify that the ports in the Lookup Table Column and the Transformation Port have the same precision.

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

Explanation:
The mapping is invalid and you cannot run the session.
User Response:
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.

Explanation:
The mapping is invalid and you cannot run the session.
User Response:
Check the mapping, make changes, and revalidate it.

CMN_1627 Internal error restoring row from cache.

Explanation:
Internal error, or there may be problems with the joiner cache files.
User Response:
Truncate the targets and run the session again.

CMN_1628 Joiner <Joiner transformation name> initialization error creating detail input row data.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1629 Joiner <Joiner transformation name> initialization error creating master input row data.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1630 ERROR: Unexpected error encountered at file <file name> line <line number>.

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

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

Explanation:
An error occurred while aborting a row in the Joiner transformation instance.
User Response:
Check other error messages preceding this error message in the log.

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

Explanation:
You cannot share static and dynamic lookups in the same target load order group.
User Response:
Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group.

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

Explanation:
You cannot share two dynamic lookups in the same target load order group.
User Response:
Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group.

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

Explanation:
You cannot share static and dynamic or two dynamic lookups in the same target load order group.
User Response:
Remove the cache file name prefix. Or, use a unique prefix to share the cache with the Lookup transformation in another target load order group.

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

Explanation:
One session is trying to read from a cache file while another session is still writing to it.
User Response:
Wait until the first session completes, then run the session.

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

Explanation:
One session is trying to write to a cache file while another session is reading from it.
User Response:
Wait until the first session completes, then run the session.

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

Explanation:
A session is trying to write to a cache file while another session is reading from the file.
User Response:
Wait until the first session completes, and then run the session.

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

Explanation:
You configured a Lookup transformation to use a dynamic lookup cache and the lookup table contains duplicate rows.
User Response:
Eliminate duplicate rows in the lookup table, or use a static cache.

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

Explanation:
Two Lookup transformations have different connect strings, but have the same cache file name.
User Response:
Make sure the connect strings match.

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

Explanation:
Two Lookup transformations have different query overrides, but have the same cache file name.
User Response:
If you want to share the cache, use the same query override. If you do not want to share the cache, change the cache file name for one of the Lookup transformations.

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

Explanation:
Two Lookup transformations have different query overrides, but have the same cache file name.
User Response:
If you want to share the cache, use the same query override. If you do not want to share the cache, change the cache file name for one of the Lookup transformations.

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

Explanation:
Two Lookup transformations use different lookup tables, but have the same cache file name.
User Response:
If you want to share the cache, the lookup table names must match. If you do not want to share the cache, change the cache file name for one of the Lookup transformations.

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

Explanation:
When you have multiple Lookup transformations in a mapping, the first lookup creates a cache file. The second lookup tries to use the same cache file, but cannot because the condition does not match. Because both lookups use the same cache file name, the second lookup cannot create a cache file.
User Response:
If you do not want to share the cache, change the cache file name for one of the lookups. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions.

CMN_1660 Error: The number <number> of condition columns of Lookup <transformation name> is different from <number> Lookup <transformation name> even though they have the same cache file name prefix <prefix name> and <cache file name> needs to be refreshed / updated.

Explanation:
The second Lookup transformation uses a subset of condition columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of condition columns must be the same.
User Response:
If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions.

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

Explanation:
The second Lookup transformation uses a subset of condition columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of condition columns must be the same.
User Response:
If you do not want to share the cache, change the cache file name for one of the Lookup transformations. If you want to share the cache, make sure the shared transformations use the same ports in the lookup conditions.

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

Explanation:
The second Lookup transformation uses a subset of output columns of the first Lookup transformation. However, the second Lookup transformation needs to update the cache. The number of output columns must be the same.
User Response:
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.

Explanation:
The second Lookup transformation uses a subset of output columns of the first Lookup transformation. However, the second Lookup transformation needs to refresh the cache. The number of output columns must be the same.
User Response:
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.

Explanation:
You reached the limit of unique sequence IDs that can be generated for inserting rows in the dynamic lookup cache.
User Response:
Check the value of this port in the rows that are used to initialize the lookup cache. Try to modify the value.

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

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
The Lookup transformation uses a persistent named cache, and the lookup SQL override was changed between session runs.
User Response:
Recache the lookup source, or change the lookup SQL override to the previous one.

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

Explanation:
Another session with a named lookup cache in the mapping may be running that is using this cache file.
User Response:
Use unique cache file names for the named Lookup transformation.

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

Explanation:
Another session with an unnamed Lookup transformation in the mapping may be running that is using this cache file.
User Response:
Use unique cache file names for the named Lookup transformation.

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

Explanation:
The Lookup transformation has been configured to use a cache file name prefix, but it has not been configured for a persistent lookup cache. You can use a cache file name prefix only with a persistent lookup cache.
User Response:
Change the Lookup properties to either remove the cache file name prefix or use a persistent cache.

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

Explanation:
In a previous target load order group in a mapping, a dynamic Lookup transformation created a cache file. A static Lookup transformation uses the same cache file name and cannot delete it.
User Response:
Use unique cache file names for the transformations.

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

Explanation:
In a previous target load order group in a mapping, a static Lookup transformation created a cache file. A dynamic Lookup transformation uses the same cache file name and cannot delete it.
User Response:
Use unique cache file names for the transformations.

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

Explanation:
You specified a cache size larger than the system can allocate.
User Response:
Either reduce cache size for the transformation or increase virtual memory available in the machine.

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

Explanation:
In the session, you disabled caching for a Lookup transformation that you configured to use as a dynamic cache.
User Response:
If you configure a Lookup transformation with a dynamic cache, you must enable caching in the session.

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

Explanation:
There is insufficient process memory.
User Response:
Reduce the DTM buffer pool size, or free system resources.

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

Explanation:
Two Lookup transformations are configured to share a lookup cache, but the datatypes of the cached columns in the Lookup transformations do not match.
User Response:
If you are using a named cache, verify that the caching structures match. If you are using an unnamed cache, verify that the caching structures are compatible.

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

Explanation:
The Integration Service failed to set database option DBARITHABORT for a database connection to Microsoft SQL Server.
User Response:
Make sure Microsoft SQL Server is running and check Microsoft SQL Server network settings so that the Integration Service can connect to the database and set the DBARITHABORT option.

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

Explanation:
The Integration Service failed to set any database option for a database connection to Microsoft SQL Server.
User Response:
Make sure Microsoft SQL Server is running and you can set the database connection and database connection options.

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

Explanation:
You specified a SQL override for this Lookup transformation and specified the ORDER BY clause incorrectly.
User Response:
When you override the lookup query ORDER BY clause, you must put the condition ports first.

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

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
The address you specified in the Shared Memory Base Address is already in use.
User Response:
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>.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_1705 Error attaching to system shared memory <ID> because it has been removed.

Explanation:
The Load Manager terminated unexpectedly. Or the system shared memory was manually removed using the ipcrm command.
User Response:
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.

Explanation:
The lookup query contains one or more characters that are not encoded in character set of the lookup database code page.
User Response:
Identify the invalid character referenced in the session log. Edit the lookup query so that it contains characters encoded in the character sets of both the Integration Service code page and the lookup database code page.
You can also configure the lookup database to use a code page that contains encoding for the lookup data character set and is compatible with the Integration Service code page.
Explanation:
The lookup database uses a code page that is not supported by PowerCenter.
User Response:
Select a code page for the lookup database that is supported by PowerCenter and contains encoding for the lookup data character set.

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

Explanation:
You upgraded a session using a persistent lookup cache and the Integration Service ran it for the first time since the upgrade.
User Response:
None. The Integration Service rebuilds the cache from the lookup table.

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

Explanation:
The Integration Service could not delete the specified cache file.
User Response:
Check the additional error message for more information.

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

Explanation:
The Integration Service could not open the specified cache file.
User Response:
Check the additional error message for more information.

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

Explanation:
Operating system error.
User Response:
Contact internal technical support.

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

Explanation:
Operating system error.
User Response:
Contact internal technical support.

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

Explanation:
The Integration Service could not truncate the specified cache file.
User Response:
Check the additional error message for more information.

CMN_1769 Inconsistent recovery cache.

Explanation:
The Integration Service cannot run the session enabled for recovery because the recovery cache file does not contain valid data.
User Response:
Delete all recovery cache files associated with the session and run the session with recovery disabled to create a cache file. To determine which recovery cache file is associated with the session, compare the time at which the file was last modified with the time the session failed. If the times are the approximately the same, you can associate the cache file with the session.
You can also refer to the cache file names to determine which files are associated with the session. Recovery cache file names use the following format:
pmgmd_metadata_<repository ID>_<workflow ID>_<folder ID>_
<session ID>_<transformation ID>_<partition ID>_<group ID>_
<checkpoint ID>_<sequence number>.dat
For example, in the following file name, the session ID is 102:
pmgmd_metadata_7661f424_379f_11d7_947e_f63b53abfef7_103_2_102_0_0_0_1_1.dat
Use the REP_LOAD_SESSIONS MX View on the repository database to determine the name of the session associated with the session ID. You can use REP_LOAD_SESSIONS to view information about reusable sessions.

CMN_1770 Recovery cache consumer is registered more than once.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

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

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

Explanation:
The Integration Service cannot find the cache file directory for message recovery.
User Response:
Verify that the cache file directory exists. Specify the correct path to the cache file directory in the session properties. If the cache file directory does not exist, create a directory and specify a directory path in the session properties.

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

Explanation:
In a cached Lookup transformation in the Designer, you specified a database connection name that exists as both a Relational and Application database connection in the Workflow Manager. When the Integration Service runs the session, it cannot determine which connection to use.
User Response:
In the session properties, select the correct database connection name for the Lookup transformation. Or, you can enter “Relational:” before the connection name if it is a Relational connection, or type “Application:” before the connection name if it is an Application connection.

CMN_1774 Error: Logical connection <database connection> in Lookup <Lookup transformation name> is either an invalid connection or it exists in both Relational and Application type connections.

Explanation:
In a cached Lookup transformation in the Designer, you specified a database connection name that exists as both a Relational and Application database connection in the Workflow Manager. When the Integration Service runs the session, it cannot determine which connection to use.
User Response:
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_1775 Recovery cache directory <directory name> is invalid.

Explanation:
The name for the recovery cache folder is not valid.
User Response:
From the Properties settings on the sources tab in the session properties, specify a valid path for the recovery cache folder.

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

Explanation:
For a Lookup or Stored Procedure transformation, you selected an Application database connection type that is not a relational database.
User Response:
Select a Relational database connection, or select an Application database connection based on a relational database, such as a PeopleSoft connection.

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

Explanation:
The Integration Service failed to read data from the specified cache file.
User Response:
Check the additional error message for more information.

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

Explanation:
The Integration Service failed to write data to the specified cache file.
User Response:
Check the additional error message for more information.

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

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

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

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

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

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

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

Explanation:
In the Location Information session property for a Lookup transformation, you specified a database connection name that is too long.
User Response:
Edit the database connection name in either the Relational or Application Connection Browser.

CMN_1785 Lookup SQL override <Lookup transformation> has references to mapping parameters or variables that cannot be resolved correctly.

Explanation:
You referenced a mapping parameter or variable in the lookup SQL override, but the Integration Service could not resolve the parameter or variable to text.
User Response:
Edit the lookup SQL override and verify you spelled the mapping parameter or variable correctly. Also, verify you declared the mapping parameter or variable in the mapping.

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

Explanation:
The Integration Service failed to update the row in the dynamic lookup cache.
User Response:
Check the session log for related error messages.

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

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

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

Explanation:
The Lookup transformation uses a persistent named cache, and the number of partitions in the pipeline that contains the Lookup transformation was changed between session runs.
User Response:
Recache the lookup source, or change the number of partitions to the previous number.

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

Explanation:
You configured two Lookup transformations in a mapping to share a named cache, but you configured only one transformation for cache partitioning. The Integration Service cannot share a partitioned cache with a non-partitioned cache.
User Response:
Edit the session properties and configure either both Lookup transformations with a hash auto-keys partition point or neither with a hash auto-keys partition point.
Edit the mapping so that the Lookup transformations do not share a cache.
Explanation:
You configured two Lookup transformations in separate target load order groups to share a named cache, but you configured a different number of partitions for the target load order groups.
User Response:
Edit the session properties and configure the same number of partitions for each Lookup transformation.
Edit the mapping so that the Lookup transformations do not share a cache.

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

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

CMN_1804 Cache cannot be empty when running in recovery mode.

Explanation:
You enabled recovery for a session. The session failed. Before you started the recovery session, the cache was emptied. This is not allowed.
User Response:
When a session configured for recovery fails, make sure that the cache is not emptied before starting the recovery session.

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

Explanation:
The Integration Service could not read the recovery cache file.
User Response:
See the additional error message for more information.

CMN_1807 Cache version does not match with <version>.

Explanation:
You enabled recovery for a session. The session failed. Before you started the recovery session, the cache folder was modified. This is not allowed.
User Response:
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>.

Explanation:
You enabled recovery for a session. The session failed. 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.
User Response:
Run sessions in recovery mode on the same platform as the initial session.

CMN_1809 Partition number does not match with <number>.

Explanation:
You enabled recovery for a session. The session failed. Before you started the recovery session, the number of partitions for the session changed. This is not allowed.
User Response:
When a session configured for recovery fails, make sure that the number of partitions does not change before starting the recovery session.

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

Explanation:
You ran a session with multiple partitions that uses a named persistent lookup cache, but the Integration Service cannot access some of the cache files.
User Response:
Verify the Integration Service can access all cache files for each partition. Or, remove all existing persistent named cache files and run the session again. If all named persistent cache files do not exist, the Integration Service rebuilds the persistent cache files.

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

Explanation:
You ran a flat file lookup session configured for sorted input, but the data for the condition columns is not grouped.
User Response:
Clear the sorted input option in the Lookup transformation.
Ensure that data in the condition columns are grouped.

CMN_1919 External loader error. Error getting Teradata loader information.

Explanation:
The Integration Service could not fetch information from the repository to build the Teradata control file.
User Response:
Verify the Integration Service machine can connect to the Repository Service machine and that the Repository Service machine can connect to the repository. Verify the repository machine is plugged in and connected to the network.

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

Explanation:
The Integration Service could not fetch information from the repository to build the Teradata control file.
User Response:
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_1921 External loader error. Control File will be generated for First Partition Only.

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

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

Explanation:
The Teradata target table does not have a primary key, so the Integration Service cannot generate a control file and update the target.
User Response:
Define a primary key on the target table and run the session again.

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

Explanation:
The primary key column in the Teradata target definition is not connected to an upstream transformation in the mapping. The Integration Service cannot generate a control file and cannot update the target.
User Response:
Connect the primary key column in the Teradata target definition to an upstream port in the mapping. Run the session again.

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

Explanation:
The primary key column in the Teradata target definition is not connected to an upstream transformation in the mapping. The Integration Service cannot generate a control file and cannot update the target.
User Response:
Connect the primary key column in the Teradata target definition to an upstream port in the mapping. Run the session again.

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

Explanation:
The Teradata external loader connection uses the specified load mode, such as update or upsert, but the target table has no primary key. The target table must have a primary key for the Integration Service to use this load mode.
User Response:
Define a primary key on the target table and run the session again.

CMN_1927 Error: Unable to set null character.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

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

Explanation:
The Integration Service cannot perform upserts on the Teradata target table.
User Response:
Verify the target table has a primary key and that the primary key column in the target definition is connected to an upstream transformation.

CMN_1929 External loader error <error message>.

Explanation:
The Integration Service cannot generate the Teradata control file because some control file option values are missing, such as the TPDID value.
User Response:
Edit the external loader connection in the session and enter a value for all options.

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

Explanation:
The service encountered an error while communicating with the Licensing Service.
User Response:
See the additional error message for more information.

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

Explanation:
The service is not licensed to run on the operating system of the node.
User Response:
Get a license to run the service on the operating system.
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 message>.

Explanation:
The log directory is not valid or does not have enough disk space.
User Response:
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.
Create a small file in the log directory to ensure that you are not out of disk space.

CMN_2006 Unable to create log file <log file name>.

Explanation:
The log directory is not valid or does not have enough disk space.
User Response:
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.
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>.

Explanation:
The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure.
User Response:
Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file.
Explanation:
The Integration Service cannot expand a parameter or variable in the call text of the Stored Procedure due to an internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_2028 The Integration Service cannot parse user variable at position <user variable position> in file <file>.

Explanation:
The Integration Service cannot find a value for the user variable in the specified position in the control file.
User Response:
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.

Explanation:
The upgraded mapping contains a pipeline branch with a Transaction Control transformation that concatenates with another branch in the same pipeline. This mapping is no longer valid in PowerCenter.
User Response:
Edit the mapping and move the Transaction Control transformation either before or after the concatenation.

CMN_17800 Property <property name> is missing.

Explanation:
A required property for a Custom transformation does not exist. You may have modified the transformation.
User Response:
If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again.

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

Explanation:
The Integration Service cannot find a column in a Custom transformation. You may have modified the transformation.
User Response:
If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again.

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

Explanation:
The transformation datatype and SAP datatype are not compatible for the specified transformation. You may have modified the transformation.
User Response:
If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again.

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

Explanation:
The Integration Service received data from the SAP system. The SAP system may have sent data with a precision or scale that is too large.
User Response:
Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port.
Explanation:
The data contains inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_17808 Data conversion error for port <port number>.

Explanation:
The Integration Service received data from the SAP system. The SAP system may have sent data with a precision or scale that is too large.
User Response:
Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port.
Explanation:
The data contains inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_17809 Message from SAP LastError: <error message>.

Explanation:
SAP error.
User Response:
See the additional error message for more information.

CMN_17810 Property <property> is invalid.

Explanation:
The SequenceID or the Function Name property in the Custom transformation is invalid.
User Response:
If you received this error for an SAP/ALE IDoc Interpreter or SAP/ALE IDoc Prepare transformation, create the transformation again.

CMN_17815 Memory allocation error.

Explanation:
Out of memory error.
User Response:
Contact internal technical support.

CMN_17816 Error when trying to install SAP structure <structure>.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_17817 Connection to SAP system is lost.

Explanation:
Due to the length of the PowerCenter session, the SAP connection may have timed out.
User Response:
Restart the session.

CMN_17818 Error in appending a line to SAP internal table.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

CMN_17825 The value for property <property> is not specified.

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

CMN_17829 Failed to connect to SAP system.

Explanation:
The Integration Service could not connect to the SAP system because the SAP RFC/BAPI Interface or SAP_ALE_IDoc_Writer application connection contains invalid values for several connection attributes.
User Response:
Verify that the application connection contains valid values for the User Name, Password, and Connect String attributes.

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

Explanation:
The source file name specified for the 6.x IDoc_Writer AEP transformation may be incorrect.
User Response:
Verify that the source file name is correct.

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

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

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

Explanation:
The code page specified in the SAP RFC/BAPI Interface application connection is not compatible with the SAP server.
User Response:
Verify that the code page entered for the application connection is compatible with the SAP server.

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

Explanation:
The code page specified for the Integration Service is not compatible with the SAP server.
User Response:
Verify that the Integration Service code page is compatible with the SAP server.

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

Explanation:
The Integration Service encountered a row error. As a result, the session failed.
User Response:
See the session error log to determine the row that contains the error and view more information about the error.

CMN_17848 The value for the property <TypeOfAEP> should be <value>.

Explanation:
The 6.x IDoc_Writer AEP transformation contains an invalid value for the TypeOfAEP property.
User Response:
Enter the specified value for the TypeOfAEP property.

CMN_17851 Cannot get target property <property>.

Explanation:
Internal error.
The PowerCenter repository contains inconsistencies.
User Response:
Contact Informatica Global Customer Support.

CMN_17853 Error threshold for the session is reached.

Explanation:
The Integration Service has reached the error threshold configured in the session properties.
User Response:
Eliminate the errors in the data.
Increase the error threshold.

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

Explanation:
The length of the control field exceeds the precision set for it.
User Response:
Eliminate the errors in the data.
Increase the precision for the control field.

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

Explanation:
The Lookup transformation uses a dynamic cache and the workflow is configured to run concurrently with same instance name.
User Response:
Configure the Lookup transformation to use a static cache or define unique names for each workflow instance.

CMN_65013 Helper process for pmimprocess failed to initialize: <error message>.

Explanation:
An internal error occurred when using an operating system profile to run a workflow.
User Response:
See additional error message for more information.

CMN_65014 Integration Service failed to spawn child process: <error message>.

Explanation:
An internal error occurred when using an operating system profile to run a workflow.
User Response:
See additional error message for more information.

CMN_65015 The Integration Service failed to open a pipe <pipe name> to read the parameter file, perform a file wait task, or to read a session log.

Explanation:
The Integration Service failed to open a pipe to read the parameter file, perform a file wait task, or to read a session log.
User Response:
Contact Informatica Global Customer Support.

CMN_65016 Child process <child process id> terminated unexpectedly.

Explanation:
A child process for the pmimprocess terminated unexpectedly.
User Response:
Contact Informatica Global Customer Support

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

Explanation:
The pmimprocess was not configured.
User Response:
Set the user and groups to root and enable the setuid bit for pmimprocess before you use operating system profiles.

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

Explanation:
The operating system profile contains an invalid operating system user name.
User Response:
Verify that the operating system user name is valid for nodes in the domain.

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

Explanation:
An internal error occurred when using an operating system profile to run a workflow.
User Response:
Contact Informatica Global Customer Support.

CMN_65020 pmimprocess failed to append library path environment variable.

Explanation:
pmimprocess failed to append a library path environment variable.
User Response:
Contact Informatica Global Customer Support.

CMN_65025 Recovery file <recovery file name> is inconsistent. The expected recovery file size is <expected recovery file size>, but the recovery file size is <recovery file size>.

User Response:
Restart the session in cold start mode.

CMN_65040 Recovery file <recovery file name> is inconsistent. The size <recovery file size> is less than the minimum size of 4 bytes.

User Response:
Restart the session in cold start mode.

CMN_65050 The Integration Service could not log in to the SMTP server.

Explanation:
The SMTP server may require a user name and password.
User Response:
Disable the login requirements on the SMTP server. For more information about configuring the Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics Guide.

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

Explanation:
The SMTP server machine may not be accessible.
User Response:
Verify that the Integration Service machine can access the SMTP server machine. For more information about configuring the Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics Guide.

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

Explanation:
The SMTP server custom properties for the Integration Service process may contain invalid values.
User Response:
Verify the values of the custom properties. For more information about configuring the Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics Guide.

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

Explanation:
The SMTP server address custom property for the Integration Service process contains an invalid server address.
User Response:
Verify the server address in the custom property. For more information about configuring the Integration Service to send SMTP email on Windows, see the PowerCenter Workflow Basics Guide.

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

Explanation:
The dynamic Lookup transformation does not have a conditional expression to update the dynamic cache.
User Response:
Create an expression that returns a boolean or numeric value.

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

Explanation:
A Lookup transformation that returns multiple rows is sharing a lookup cache with a Lookup transformation that returns one row for each input row.
User Response:
Verify that the Lookup transformations that share named cache have the same multiple match properties.