REP Messages

Explanation:	The Integration Service failed to connect to the database server. You may have logged in incorrectly.
User Response:	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.

Explanation:	The Integration Service cannot locate a necessary SQL script file.
User Response:	In the win.ini file, make sure the HOME entry in the Informatica PowerMart entry points to the directory where the SQL script is located. If the HOME entry is correct, contact Informatica Global Customer Support.

REP_12014 An error occurred while accessing the repository.

Explanation:	The Repository Service encountered an error while accessing the repository.
User Response:	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>.

Explanation:	The Service Manager was unable to connect to a local repository from the global repository.
User Response:	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>.

Explanation:	The Service Manager was unable to connect to the global repository from a local repository.
User Response:	Verify that the local repository is registered with the global repository. Also, verify that the Repository Services for both repositories are running. In addition, verify that the connectivity information for the global repository is up to date.

REP_12033 The repository being accessed is incompatible with this version.

Explanation:	The repository version does not match the client and/or server version.
User Response:	If the repository is older, upgrade the repository. If the software is older, upgrade the software.

REP_12119 A repository does not exist at the specified database connection.

Explanation:	The Integration Service failed to connect to the database. You may have logged in incorrectly.
User Response:	Log in with the correct information. User names and passwords may be case sensitive.
Explanation:	You do not have the appropriate database privilege to view repository tables.
User Response:	Have the database administrator review the database privileges.

REP_12122 Unable to unlock this folder. Please try again.

Explanation:	This is a database error.
User Response:	Check the server event or error log for related database error messages. If necessary, see the database documentation for appropriate action.

REP_12123 Unable to delete this folder. Please try again.

Explanation:	This is a database error.
User Response:	Check the server event or error log for related database error messages. If necessary, see the database documentation for appropriate action.

REP_12124 Unable to delete this folder. The folder is in use by another user.

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

REP_12164 Domain-related error: <error message>.

Explanation:	The Service Manager could not complete the requested operation.
User Response:	Read the error description and make any necessary changes to the domain connectivity. For more information, look up the cause and action for the error code.

REP_12225 The value entered is not valid for memory attributes.

Explanation:	The value for the memory attribute is invalid.
User Response:	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_12233 Increment By must be less than or equal to 2147483647.

Explanation:	The value for the Sequence Generator transformation property Increment By is more than the maximum value of the Integer datatype.
User Response:	Set the value of Increment By to less than or equal to the maximum value of the Integer datatype.

REP_12325 Internal error. No connection callback.

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

REP_12326 Error getting connection information for remote repository.

Explanation:	The global repository is missing required configuration parameters to connect to another repository.
User Response:	Connect to the registered repository and correct the configuration parameters.

REP_12327 Internal error. Connection callback returned an error.

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

REP_12328 The repository at this location does not have the same name.

Explanation:	Either the database connection or the repository name entered is incorrect.
User Response:	The status bar displays the correct repository name. Correct the inaccurate information.
Explanation:	You tried to connect to a repository on the network, but there was a network failure during the connect process.
User Response:	Verify that the PowerCenter Client and the repository are connected to the network. When you connect to the repository again, enter the host name and port number of the repository in the Connect to Repository dialog box.

REP_12330 Failed to fetch repository information.

Explanation:	This is a database error.
User Response:	Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.

REP_12332 Error initializing repository object information.

Explanation:	You are low or out of memory.
User Response:	Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the system.
Explanation:	This is a database error.
User Response:	Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.

REP_12333 More than one GDR found.

Explanation:	The Integration Service found inconsistent repository information.
User Response:	Contact Informatica Global Customer Support.

REP_12334 Repository name mismatch.

Explanation:	A global repository and a repository registered with it have the same name.
User Response:	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.

Explanation:	You tried a global repository operation, such as registering a repository, when you were not connected to a global repository.
User Response:	If desired, promote the repository to a global repository.

REP_12336 This repository is already registered with the GDR <global repository name>.

Explanation:	You tried to register a repository to a global repository that is registered with a different global repository.
User Response:	If the repository should be registered with the new global repository, unregister the repository from the original global repository. Register with the new global repository.

REP_12337 This is not a local repository.

Explanation:	You tried to register a dependent repository with a global repository. Only independent repositories can be registered with a global repository.
User Response:	If the repository should be registered with a new global repository, unregister the repository from the original global repository. Then register with the new global repository.

REP_12338 A repository with this name has already been registered.

Explanation:	You tried to register a local repository when a local repository of the same name exists in the global repository.
User Response:	Unregister the repository. Copy the repository to another location with a new name, then re-register the repository.

REP_12339 Internal error. Error allocating a new repository ID.

Explanation:	Database error.
User Response:	Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.

REP_12340 Error updating remote repository.

Explanation:	Database error.
User Response:	Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.

REP_12341 Error updating GDR.

Explanation:	Database error.
User Response:	Check the server event or error log for related database error messages. If no database error is reported, contact Informatica Global Customer Support.
Explanation:	The Repository Service of the local repository is running on a node that is not configured to run the service version of the Repository Service.
User Response:	Configure the Repository Service of the local repository to run on a node that is configured to run the service version of the Repository Service.

REP_12342 The selected repository is not registered with the current Global Repository.

Explanation:	You tried to unregister a repository that is not registered with the current global repository.
User Response:	You can only unregister repositories registered with a global repository.

REP_12346 Memory allocation failed.

Explanation:	Insufficient memory allocation.
User Response:	Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the system.

REP_12347 An error occurred while updating connection information in the repository.

Explanation:	A database error occurred while updating connection information during repository registration or while editing connection information.
User Response:	Check the Repository Service event or error log for a related database error message. If no database error is reported, contact Informatica Global Customer Support.

REP_12352 The current user does not have the privilege to perform this operation.

Explanation:	You tried to perform an operation without the appropriate privileges.
User Response:	Have the database administrator review the privileges.

REP_12355 The object <object name> has been modified since the time it was read.

Explanation:	You tried to edit a repository object that has been modified and saved by another user since you opened the object.
User Response:	Close the object and open it again to view the edited object.

REP_12357 The object <object name> is already locked by <user name>. Do you want to reobtain the lock?

Explanation:	You tried to edit an object that has been locked by the user name. Either someone used the user name and password to access this object, or the client shut down while you were working on the object.
User Response:	If someone is using the user name and password, click No, then ask that person to close the object and log out. If the PowerCenter Client shut down while you were working on the object, and you are sure that no one else has the object open, click Yes.

REP_12363 Warning: Unable to check whether correct indices for the Teradata repository have been created. Please verify that you backup the repository and then restore it after you upgrade it.

Explanation:	The database user starting the repository does not have permission to query the Teradata dictionary. The Repository Service needs to query the Teradata dictionary to verify whether the Teradata repository tables have the correct primary indexes.
User Response:	After you upgrade a Teradata repository, verify you back it up and restore it before starting it. This causes the Repository Service to create new primary indexes for the repository tables. You must back up and restore a Teradata repository before you can start it.

REP_12364 For Teradata upgrade process to be complete, please take a backup of the repository (repository_name), delete existing repository and restore from the backup file. Then start the repository.

Explanation:	You upgraded the Teradata repository and tried to start it without backing it up and restoring it.
User Response:	Back up the repository and restore it. This causes the Repository Service to create primary indexes for the repository tables. You must back up and restore the repository before you can start it.

REP_12370 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A repository upgrade is required.

Explanation:	The repository needs to be upgraded to the current version expected by the product.
User Response:	Use the Administrator tool to upgrade the repository.

REP_12371 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A product upgrade is required.

Explanation:	The repository has been upgraded to a newer version of the product.
User Response:	Upgrade the PowerCenter Client, Repository Service, and the Integration Service.

REP_12372 The repository has data that is newer than this release of the product expects. (The repository data version is <version> while the product expects <version>). A product upgrade may be required.

Explanation:	The repository has been upgraded to a newer version of the product.
User Response:	Upgrade the PowerCenter Client, Repository Service, and the Integration Service.

REP_12373 The repository has data that may be too old for this release of the product. (The repository data version is <version> while the product expects <version>). A repository data upgrade may be required.

Explanation:	The repository needs to be upgraded to the current version expected by the product.
User Response:	Use the Administrator tool to upgrade the repository.

REP_12381 Unable to perform the operation since an expected object was not found. Please check the repository.

Explanation:	Internal error. The repository may contain inconsistencies.
User Response:	Contact Informatica Global Customer Support.

REP_12382 Error while updating the object information in the repository. Either no row or more than one row was updated.

Explanation:	Internal error. The repository may contain inconsistencies.
User Response:	Contact Informatica Global Customer Support.

REP_12386 There is no database object available for the repository <repository name>. (A repository is not supported on the requested database or the appropriate database driver is not available.

Explanation:	A repository is not supported on the database type specified in the configuration file.
User Response:	Check the Integration Service Setup and correct the database type of the repository.

REP_12387 The attempt to get a <save/fetch> lock on the <object type> <object name> timed out due to the following conflicting lock: User <user name> on the computer <hostname> running the <application> obtained a <save/fetch> lock on the <object type> <object name> at <time>. Please try again.

Explanation:	You tried to access or save a repository object, and the repository could not create the necessary fetch or save lock to allow you to perform the task. This occurred because another user has the object locked.
User Response:	Try again the operation again. If the problem persists, use the information provided to determine if the listed user is accessing the object. If you can verify the object is not being used or accessed, ask the administrator to unlock the object as necessary.

REP_12389 Unable to set database connection property <number>.

Explanation:	A database error prevented the repository connection from setting required database connection parameters.
User Response:	Make sure the repository database server is up and running. If there is no problem in the database, try connecting to the repository again. If the problem persists, contact Informatica Global Customer Support.

REP_12390 Mapping <mapping name> contains a dependency that points to a non existent port. The mapping is assumed to be invalid.

Explanation:	You started a session that uses a mapplet, and information about the mapping is inconsistent in the repository.
User Response:	Open the mapping in the Designer, validate the mapping and save it again. If the problem persists, the inconsistency is in the mapplet used by the mapping. Open the mapplet, validate, and save it. Then validate and save the mapping again.

REP_12392 GID creation failed for repository <repository name>.

Explanation:	Internal error. This might be caused by hardware failure.
User Response:	Contact Informatica Global Customer Support.

REP_12403 Unable to retrieve locale information.

Explanation:	The repository cannot find or read the pmlocale.bin file.
User Response:	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>.

Explanation:	A repository database error occurred causing the internal ID generation to fail.
User Response:	If a repository database error occurred, try again after correcting the database problem.
Explanation:	The repository has inconsistent data.
User Response:	Contact Informatica Global Customer Support.

REP_12405 Failed to fetch new IDs.

Explanation:	A repository database error occurred causing the internal ID generation to fail.
User Response:	If a repository database error occurred, try again after correcting the database problem.
Explanation:	The repository has inconsistent data.
User Response:	Contact Informatica Global Customer Support.

REP_12415 Error comparing last saved times for objects in this folder!

Explanation:	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.
User Response:	Try the operation again. Check the database server log for a possible cause to the problem. If there is no database error, contact Informatica Global Customer Support.

REP_12416 Error comparing deployed times for shared folders!

Explanation:	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.
User Response:	Try the operation again. Check the database server log for a possible cause to the problem. If there is no database error, contact Informatica Global Customer Support.

REP_12422 Unable to connect to GDR!

Explanation:

The database hosting the global repository is not available or the connectivity information for the global repository is incorrect.

User Response:

Verify that the connectivity information is the same on all client systems. If the connection is a secondary connection, make sure the connectivity information for the global repository did not change after the local repository was registered. If you moved the global repository to a different Repository Service, or edited the configuration information for the global repository, the connectivity information may have changed. To update the connectivity information in the repository domain, propagate the connectivity information for the global repository to the local repository.

REP_12449 Internal error.

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

REP_12450 Unable to create output file <file name>.

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

Explanation:	You tried to back up the repository and the Administrator tool could not write to the backup file. The hard disk may be full or damaged.
User Response:	Make sure enough disk space exists and there is no problem with the hard disk.

REP_12454 Unable to open input file <file name>!

Explanation:	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.
User Response:	Check the hard disk for possible problems. You might have to restore the backup file from an older backup. Contact Informatica Global Customer Support.

REP_12456 Failed to read from file <file name>!

Explanation:	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.
User Response:	Check the hard disk for possible problems. You might have to restore the backup file from an older backup. Contact Informatica Global Customer Support.

REP_12457 Unexpected data in file <file name>!

Explanation:	The repository backup file has data inconsistencies.
User Response:	Check the hard disk for possible problems. You might have to restore the backup files from an older backup. Contact Informatica Global Customer Support.

REP_12466 Error inserting repository object information.

Explanation:	A repository database error caused the repository creation or upgrade to fail.
User Response:	Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12467 Error inserting repository object attribute information.

Explanation:	A repository database error caused the repository creation or upgrade to fail.
User Response:	Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12468 Error inserting server locale information.

Explanation:	A repository database error caused the repository creation or upgrade to fail.
User Response:	Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12469 Error initializing object tree.

Explanation:	A repository was not created, upgraded, or restored correctly. If the problem occurs in a repository that is in use, the database may have inconsistencies.
User Response:	Contact Informatica Global Customer Support.

REP_12470 Error updating repository information.

Explanation:	A repository database error caused the repository creation or upgrade to fail.
User Response:	Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12471 Error creating first user.

Explanation:	A repository database error caused the repository creation to fail.
User Response:	Try to create the repository again after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12477 This repository contains folders which are currently in use. A repository cannot be deleted while it is in use.

Explanation:	You tried to delete a repository while other users are logged in to the repository. Even if there are no users connected, the repository could contain residual locks.
User Response:	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.

REP_12488 Unable to add new internal sequence generator.

Explanation:	A repository database error caused the repository creation or upgrade to fail.
User Response:	Try to create or upgrade the repository after fixing the database error. If the problem persists, contact Informatica Global Customer Support.

REP_12492 This repository contains folders which are currently in use. A repository cannot be upgraded while folders are in use.

Explanation:	You tried to upgrade a repository when other users are logged in to the repository. If there are no users connected, the repository might contain residual locks.
User Response:	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.

REP_12494 The Repository is newer than the version supported by this software release. Unable to do an upgrade.

Explanation:	The product version is older than the repository version.
User Response:	Release all old locks in the repository. Upgrade the PowerCenter Client to the latest version, then upgrade the repository.

REP_12496 This repository is too old to be upgraded.

Explanation:	You tried to upgrade a repository with a newer release of the Repository Manager that does not support upgrading that repository version.
User Response:	Contact Informatica Global Customer Support.

REP_12505 Error while executing script file <file name>.

Explanation:	A database error or a problem occurred in the script.
User Response:	Correct the database error and try the operation again. If there is no database error, contact Informatica Global Customer Support.

REP_12581 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.

Explanation:	The script file cannot be found in the PowerCenter Client installation directory or the file is corrupt.
User Response:	Install the PowerCenter Client again to get the correct scripts. If the problem persists, contact Informatica Global Customer Support.

REP_12589 Error occurred in locking.

Explanation:	An internal error occurred due to a database error or inconsistent data in the repository. This error might be accompanied by a more descriptive error message or a database error message.
User Response:	Abort the operation and try again. If the problem persists and there is no database error, contact Informatica Global Customer Support.

REP_12590 Error updating <repository name> in GDR.

Explanation:	A database error occurred while registering or unregistering a repository.
User Response:	If a database error occurred, correct the database error and try again. Otherwise, contact Informatica Global Customer Support.

REP_12591 Error updating <repository name> in GDR (Repository may be left in inconsistent state).

Explanation:	A repository database error occurred when you tried to register or unregister a repository.
User Response:	If a repository database error occurred, correct the database error and try again. If the operation succeeds then the inconsistency in the repository will have been corrected. Otherwise, contact Informatica Global Customer Support.

REP_12651 Memory allocation failed.

Explanation:	The Integration Service machine is out of memory.
User Response:	Increase virtual memory or close other applications.

REP_12654 Password is too long.

Explanation:	You entered a password that exceeded the limit of 76 characters.
User Response:	Use a shorter password.

REP_12678 The connection to Global DataMart Repository is unavailable for some reason.

Explanation:	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.
User Response:	Check the database error message for more information and correct the problem. Update connection information in the Administrator tool if it has changed.

REP_12708 Unable to allocate memory.

Explanation:	The Integration Service machine is out of memory.
User Response:	Increase virtual memory or close other applications.

REP_12709 Unable to find database type for this source.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer 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).

Explanation:

Validation error. The code page of the source database connection is not a subset of the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode.

User Response:

If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions:

•Choose a different source database connection for the session.
•Choose a different Integration Service to run the workflow.
•Correct the code page configured for the source database connection.
•Correct the code page registered for the Integration Service.

REP_12735 The source file <file name> and Integration Service <Integration Service name> do not have compatible code pages. (One way compatibility is required.)

Explanation:	Validation error. The code page of the source file is not a subset of the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode.
User Response:	If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions: •Choose a different source file and code page for the session. •Choose a different Integration Service to run the workflow. •Correct the code page registered for the Integration Service.

REP_12736 The database <database name> and Integration Service <Integration Service name> do not have compatible code pages.

Explanation:

Validation error. The session contains a Lookup or Stored Procedure transformation and the code page for the lookup or stored procedure database is not compatible with the Integration Service code page. This causes the session to fail when the Integration Service runs in the Unicode data movement mode.

User Response:

If the Integration Service runs in ASCII mode, you can ignore this warning. If the Integration Service runs in Unicode mode, correct the problem with one of the following actions:

•Choose a different Integration Service to run the workflow.
•Correct the configured code page for the database in the Workflow Manager.
•Choose a different lookup or stored procedure database in the session properties.
•Correct the code page registered for the Integration Service.

REP_12773 The Global Repository code page (<code page name>) is not compatible with the selected code page (<code page name>).

Explanation:	While upgrading a local repository, the local repository code page must be a superset of the global repository code page.
User Response:	Choose an appropriate code page.

REP_12782 The repository <repository name>’s code page <code page name> and <PowerCenter Client>’s code page <code page name> are incompatible.

Explanation:	The PowerCenter Client code page is not compatible with the code page of the repository to which you are trying to connect. The PowerCenter Client and repository code pages must be compatible. Their code pages must also be compatible with the Integration Service code page.
User Response:	Change the code page for the PowerCenter Client to one that is compatible with the repository code page. Or, if you need to change the repository code page, you can copy the repository to a new location or backup and restore it. Both actions allow you to configure a different code page for the repository.

REP_12934 Failed to fetch information for user <user name>.

Explanation:	This is a database error.
User Response:	Read the accompanying database error message for more details.
Explanation:	The computer running the PowerCenter Client is out of memory.
User Response:	Close other applications.

REP_12950 Lookup Transformation <transformation name> has INVALID lookup condition: Lookup Table Column <column name> and Transformation Port <port name> are the same.

Explanation:	You entered an incorrect expression value for the lookup condition in the XML file. The lookup table column is the same as the transformation port.
User Response:	Edit the XML file and make sure the lookup table column is different from the transformation port. Or, export the object again and then import it.

REP_12951 The lookup condition is not valid: Lookup Table Column <column name> and Transformation Port <port name> are the same. Transformation is not valid.

Explanation:	You entered an incorrect expression value for the lookup condition in the XML file. The lookup table column is the same as the transformation port.
User Response:	Edit the XML file and make sure the lookup table column is different from the transformation port. Or, export the object again and then import it.

REP_12952 Joiner Transformation <transformation name> has INVALID joiner condition: Master <port name> and Detail <port name> are the same.

Explanation:	You entered an incorrect expression value for the join condition in the XML file. The master port is the same as the detail port.
User Response:	Edit the XML file and make sure the master port is different from the detail port. Or, export the object again and then import it.

REP_12953 The joiner condition is not valid: Master <port name> and Detail <port name> are the same. Transformation is not valid.

Explanation:	You entered an incorrect expression value for the join condition. The master port is the same as the detail port.
User Response:	Edit the XML file and make sure the master port is different from the detail port. Or, export the object again and then import it.

REP_12954 Warning: The Call Text attribute of Stored Procedure transformation <transformation name> has non-empty value when the Stored Procedure Type attribute is set to Normal.

Explanation:	The call text attribute for the stored procedure contains a value when you defined the stored procedure type attribute as Normal in the XML file.
User Response:	Edit the XML file and make sure the call text attribute value is empty when you define the stored procedure type attribute as Normal. Or, export the object again and then import it.

REP_12955 Warning: The Call Text attribute of Stored Procedure transformation has non-empty value when attribute Store Procedure Type is set to Normal.

Explanation:	The call text attribute contains a value when you defined the stored procedure type attribute as Normal in the XML file.
User Response:	Edit the XML file and make sure the call text attribute value is empty when you define the stored procedure type attribute as Normal. Or, export the object again and then import it.

REP_12975 There is no existing MQ Connection to choose for <connection string> in the target repository.

Explanation:	This is an informational message. You tried to copy a WebSphere MQ session to a target repository with no defined queue connections.
User Response:	Create at least one queue connection in the target repository.

REP_12991 Failed to connect to <repository name> Repository Agent on host <host name> (port number: <port number>). System error message: <error message>.

Explanation:	A repository client could not connect to a Repository Agent process. The Repository Agent host name or port number may be incorrect.
User Response:	Verify that the host name and port number specified in the repository client connection information is the same as the information specified in the Repository Agent configuration.

REP_12994 Server system error (errno = <error number>): <system error message>.

Explanation:	An error occurred on the Repository Service system.
User Response:	For Repository Service on Windows, check the system event log for related error messages. See Windows help and look up the specified system error number. For Repository Service on UNIX, locate the error in the /usr/include/sys/errno.h file. See the UNIX Documentation for explanation of the error.

REP_12995 Failed to shutdown Integration Service.

Explanation:	The Integration Service would not shut down.
User Response:	Check preceding messages to see the cause of the error.

REP_12996 No key is selected for Sorter transformation <transformation name>.

Explanation:	You did not configure a sort key for the Sorter transformation.
User Response:	Edit the Sorter transformation and select one or more ports to use as a sort key.

REP_12999 No key is selected for Sorter transformation. This transformation is not valid.

Explanation:	You did not configure a sort key for the Sorter transformation.
User Response:	Edit the Sorter transformation and select one or more ports to use as a sort key.

REP_22674 Custom Transformation <transformation name> has non-ASCII character(s) in its class name.

Explanation:	The Custom transformation class name contains non 7-bit ASCII characters.
User Response:	Edit the transformation properties and enter 7-bit ASCII characters for the class name.

REP_32000 Error: Could not find DSQ instance <Source Qualifier name> for <source>.

Explanation:	The Source Qualifier transformation associated with the source is missing in the XML file.
User Response:	Edit the XML file and verify that it has a valid entry for the Source Qualifier transformation. Or, export the object again and then import it.

REP_32001 Error: Source Reference: <source> DBD: <source> for DSQ <Source Qualifier name> not found.

Explanation:	The source associated with a specified Source Qualifier transformation is missing in the XML file.
User Response:	Edit the XML file and verify it has a valid source for the specified Source Qualifier transformation. Or, export the object again and then import it.

REP_32002 Error: There are more than one groups with the order: <number> in <group>.

Explanation:	The XML file specifies more than one group with the same order for that particular source, target, or transformation.
User Response:	Check the ORDER entry under the GROUP node for that specified source, target, or transformation in the XML file. Or, export the object again and then import it.

REP_32003 Error: Field order does not match group order.

Explanation:	The field order does not match the group order in the XML file.
User Response:	Edit the XML file and make sure the field order matches the group order. Or, export the object again and then import it.

REP_32004 Error: Invalid Transformation type <type> for transformation <transformation name>.

Explanation:	In the XML file, you defined the TYPE Attribute in the TRANSFORMATION element as an incorrect value.
User Response:	Edit the XML file and enter a legal transformation type for the attribute TYPE. Or, export the object again and then import it.

REP_32007 Folder referenced by the shortcut object does not exist, object will be created in the current folder.

Explanation:	The shortcut to an object does not contain folder information. You might have renamed or deleted the folder.
User Response:	Restore the folder in the target repository. Otherwise the object is imported as the actual object the shortcut references, as defined by the metadata in the XML file, under the current folder.

REP_32010 Error: Object referenced by shortcut: <shortcut>. Referring to <object> in Repository: <repository name>. Folder: <folder name> not found.

Explanation:	You deleted or renamed a folder that contains a shortcut in the specified repository.
User Response:	Restore the folder or re-create the shortcut to the object in the folder.

REP_32011 Internal Error: Could not copy object.

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

REP_32013 Error encountered while Parsing file.

Explanation:	The XML file from which you tried to import is invalid or does not follow the powrmart.dtd file.
User Response:	Edit the XML file and make sure it is valid against the powrmart.dtd file.

REP_32014 The DTD file name is not specified.

Explanation:	The XML file does not contain the DTD file name.
User Response:	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>.

Explanation:	The repository code page specified in the XML file is not compatible with the target repository code page.
User Response:	Cannot import the XML file. Edit the XML file and make sure the code pages are compatible.

REP_32016 Error: Invalid Database Type: <database type>.

Explanation:	The database name in the XML file for that object is not supported or invalid.
User Response:	Edit the XML file and verify the database type. Or, export the object again and then import it.

REP_32018 Invalid Delimiters: <delimiter>.

Explanation:	You defined invalid delimiters for a flat file source in the XML file.
User Response:	Edit the XML file under the FLAT FILE node. Or, export the object again and then import it.

REP_32019 Error: Invalid table attribute: <attribute>.

Explanation:	You defined a table attribute type in the XML that is not supported.
User Response:	Edit the XML file for that attribute. Or, export the object again and then import it.

REP_32020 Warning: Could not link fields <field name>:<field name>:<field name>: Instance <instance> to Field: <field name> Instance <instance>.

Explanation:	An invalid connector node exists for a mapping or mapplet in the XML file.
User Response:	Fix the CONNECTOR node under the mapping or mapplet. Or, export the object again and then import it.

REP_32021 Error: Invalid Key Type: <key type>.

Explanation:	You defined a key type for a source object in the XML file that is not supported.
User Response:	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>.

Explanation:	You defined a group in the XML file that does not exist for that table field.
User Response:	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>.

Explanation:	You defined an invalid ODBC type for a table field in the XML file.
User Response:	Edit the XML file for the ODBC data type for that particular field.

REP_32025 Error: Invalid Field Attribute: <attribute> found for field: <field>.

Explanation:	You defined an invalid field attribute for a table field in the XML file.
User Response:	Edit the XML file for that particular attribute. Or, export the object again and then import it.

REP_32026 Error: Could not find field: <field> in Instance: <instance>.

Explanation:	You specified a Foreign Key field name does not exist in the referenced source.
User Response:	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>.

Explanation:	The DBD or source for a specified foreign key field name is missing in the XML file.
User Response:	Edit the XML file. Or, export the object again and then import it.

REP_32028 Error: This source cannot have groups.

Explanation:	You defined a group node for a source that does not support groups in the XML file.
User Response:	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>.

Explanation:	Unable to add group information.
User Response:	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>.

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

REP_32031 Error: Missing or Invalid TYPE attribute for Group: <group>.

Explanation:	You defined a group type in the XML file that is missing or invalid.
User Response:	Edit the group type node in the XML file.

REP_32032 Error: Cannot import tables of type <TABLETYPE value>.

Explanation:	You entered an invalid value for the TABLETYPE attribute in the TARGET element in the XML file.
User Response:	Edit the XML file and enter NONE for the TABLETYPE attribute. Or, export the object again and then import it.

REP_32033 Error: This target cannot have groups.

Explanation:	You specified a target in the XML file that does not support groups.
User Response:	Edit the XML file and remove the group node. Or, export the object again and then import it.

REP_32034 Database Error: while Assigning Ids for Target: <target name>.

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

REP_32035 Error: Invalid Initialization Property: <INITPROP name>.

Explanation:	You entered NO for the USERDEFINED attribute and entered an invalid value for the NAME attribute for the INITPROP element in the XML file.
User Response:	If the INITPROP element represents a user-defined initialization property in the transformation, edit the XML file and enter YES for the USERDEFINED attribute. Otherwise, export the object again and then import it.

REP_32036 Error: This transformation cannot have groups.

Explanation:	In the XML file, you entered a GROUP element for a transformation that does not support groups.
User Response:	Edit the XML file to remove the GROUP element from the transformation that does not support groups. Or, export the object again and then import it.

REP_32037 Database Error: while Assigning Ids for Transformation: <transformation>.

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

REP_32038 Error: Invalid Datatype: <datatype> for field: <field name>.

Explanation:	You entered an invalid datatype for the field in the XML file.
User Response:	Edit the XML file to specify a supported datatype. Or, export the object again and then import it.

REP_32039 Error: Missing ATTRIBUTE <XML attribute name> for field: <SOURCEFIELD name or TRANSFORMFIELD name>.

Explanation:	The specified attribute is missing or empty in the specified element in the XML file.
User Response:	Edit the XML file and enter the necessary attribute in the specified element or add a value for the specified attribute. Or, export the object again and then import it.

REP_32040 Error: Could not find associated source field: <SOURCEFIELD name> for <Normalizer transformation>.

Explanation:	In the XML file, the specified REF_SOURCEFIELD attribute in the TRANSFORMFIELD element in the specified Normalizer transformation does not match the name of a SOURCEFIELD element.
User Response:	Edit the XML field and verify the REF_SOURCEFIELD attribute matches the name of a SOURCEFIELD element in the XML file. Or, export the object again and then import it.

REP_32041 Error: Invalid Instance Type: <TYPE value>.

Explanation:	You specified an invalid entry for the TYPE attribute in the INSTANCE element for a transformation.
User Response:	Edit the XML file and enter a valid instance type for the TYPE attribute. Or, export the object again and then import it.

REP_32042 Error: Invalid reference field <REF_FIELD name> for Transformation field: <TRANSFORMFIELD name>.

Explanation:	In the XML file, a TRANSFORMFIELD element contains a value for the REF_FIELD attribute that does not match a SOURCEFIELD element.
User Response:	Edit the XML file and verify the REF_FIELD attribute matches the name of the SOURCEFIELD element. Or, export the object again and then import it.

REP_32043 Error: Missing attribute <MAPPLETGROUP> or <REF_FIELD> for Field: <mapplet name>.

Explanation:	In the XML file, either the REF_FIELD or MAPPLETGROUP attribute is missing from a TRANSFORMFIELD element inside a TRANSFORMATION element for a mapplet.
User Response:	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>.

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

Explanation:	The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file.
User Response:	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.
Explanation:	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.
User Response:	Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it.

REP_32046 Error: Invalid reference field: <REF_FIELD> for Field: <TRANSFORMFIELD name> Transformation: <TRANSFORMATION name>.

Explanation:	The specified TRANSFORMFIELD element in the specified Lookup transformation is missing a REF_FIELD attribute in the XML file.
User Response:	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.
Explanation:	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.
User Response:	Edit the XML file and verify the REF_FIELD attribute matches the name of another TRANSFORMFIELD element. Or, export the object again and then import it.

REP_32047 Error: Invalid Mapplet Group <MAPPLETGROUP> for Field: <MAPPLETGROUP value> Transformation: <transformation name>.

Explanation:	In the XML file, the MAPPLETGROUP attribute value does not match the name of the GROUP element for the mapplet.
User Response:	Edit the XML file and verify the MAPPLETGROUP attribute matches the GROUP name for the mapplet. Or, export the object again and then import it.

REP_32050 Error: Could not find Transformation definition for: <transformation or source or target name>.

Explanation:	The TRANSFORMATION_NAME attribute in the INSTANCE element does not match a TRANSFORMATION element name in the XML file.
User Response:	Edit the XML file and verify the TRANSFORMATION_NAME attribute matches a TRANSFORMATION element name. Or, export the object again and then import it.

REP_32056 Error: Missing or Empty Attribute: <attribute name>.

Explanation:	You did not enter the specified attribute in either a SOURCE, SOURCEFIELD, or TARGETFIELD element in the XML file.
User Response:	Edit the XML file and enter the necessary attribute. Or, export the object again and then import it.

REP_32057 Error: Populating default fields for MQ Source.

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

REP_32058 Error: Populating default fields for MQ Target.

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

REP_32060 Error: Could not get datatype description for field: <field name>.

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

REP_32063 Error: An Unknown target field attribute: <attribute ID> has been detected for Field: <field name>.

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

REP_32066 Error: Could not get group for source field: <source field>.

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

REP_32072 Invalid date in schedule info.

Explanation:	You defined an invalid date in the XML file for a session start and end time in the schedule information node.
User Response:	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>.

Explanation:	Internal Error. This REP message is specific to sessions with SAP R/3 sources.
User Response:	Contact Informatica Global Customer Support.

REP_32079 Failed to export SAPVariable <SAP variable>.

Explanation:	Internal Error. This REP message is specific to sessions with SAP R/3 sources.
User Response:	Contact Informatica Global Customer Support.

REP_32081 Invalid schedule info.

Explanation:	You set invalid schedule information for the session in the XML file.
User Response:	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.

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

REP_32088 Error: Unable to fetch database connection.

Explanation:	The database connection specified for the session in the XML file does not exist in the target repository.
User Response:	Create a database connection in the target repository with the name defined in the XML file, or select an existing database connection from the Workflow Manager.

REP_32089 Error: Unable to fetch registered server information for the session.

Explanation:	The Integration Service specified for the session in the XML file does not exist in the target repository.
User Response:	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.

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

REP_32091 Error: Unable to fetch mapping DSQ related information.

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

REP_32092 Error: Unable to fetch database connection: <database connection> associated with the data Source Qualifier transformation: <transformation name>.

Explanation:	The database connection specified for the session in the XML file does not exist in the target repository.
User Response:	Create a database connection in the target repository with the name defined in the XML file, or select an existing database connection from the Workflow Manager.

REP_32093 Error: Unable to fetch partitions for the session <session name>.

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

REP_32095 Error: Invalid Mapping Name for the session <session name>.

Explanation:	You defined an invalid mapping name associated with the session in the XML file.
User Response:	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>.

Explanation:	Unable to retrieve the connection object defined in the XML file for that session.
User Response:	Create a connection object or select an existing one using the Workflow Manager.

REP_32097 Warning: FTP connection <FTP connection> not found. Session will be imported without reference to FTP connection.

Explanation:	Unable to retrieve the connection object defined in the XML file for that session.
User Response:	Create a connection object or select an existing one using the Workflow Manager.

REP_32098 Warning: Loader connection <external loader connection> not found. Session will be imported without reference to Loader connection.

Explanation:	Unable to retrieve the connection object defined in the XML file for that session.
User Response:	Create a connection object or select an existing one using the Workflow Manager.

REP_32101 Error: Internal Error encountered in initializing Parser.

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

REP_32103 Warning: Invalid Usage type: <type> for field: <field name>.

Explanation:	You defined an invalid usage type description under the flat file node in the XML file.
User Response:	Edit the XML file. Or, export the object again and then import it.

REP_32105 Error: Invalid Codepage: <code page> for Flat File.

Explanation:	You defined a code page for the flat file object in the XML file that is not compatible with the repository code page information.
User Response:	Cannot import the source.

REP_32111 Error: Invalid Database Type: <DATABASETYPE value> for source: <SOURCE name>.

Explanation:	You entered an invalid database type in the DATABASETYPE attribute in the SOURCE element for the specified source.
User Response:	Edit the XML file and correct the DATABASETYPE attribute in the SOURCE element. Or, export the object again and then import it.

REP_32112 Error: Missing or Empty Name for: <element>.

Explanation:	You did not enter a NAME attribute for the specified element.
User Response:	Edit the XML file and add a NAME attribute in the specified element. Or, export the object again and then import it.

REP_32113 Error: Invalid number of fields for transformation: <Sequence transformation name>.

Explanation:	In the XML file, you included more than two TRANSFORMFIELD elements in the specified TRANSFORMATION element for a Sequence Generator transformation.
User Response:	Edit the XML file and make sure the Sequence Generator transformation has exactly two TRANSFORMFIELD elements. Or, export the object again and then import it.

REP_32115 Error: <object> <object name> cannot be imported as it is potentially unsafe. Importing any associated mapping/mapplet might result in an error.

Explanation:	You created or modified an object in the XML file that cannot be created or modified.
User Response:	Export the object again and then import it.

REP_32116 Error: The mapping: <mapping name> is potentially unsafe and cannot be imported.

Explanation:	In the XML file, you modified an object that contains a CRCVALUE code. The object is a part of the specified mapping.
User Response:	Export the object again and then import it.

REP_32117 Error: <transformation type> <transformation name> is potentially unsafe and will not be available for import.

Explanation:	In the XML file, you modified either a source, target, or transformation that contains a CRCVALUE code.
User Response:	Export the object again and then import it.

REP_32118 Error: Invalid Usage Flags: <flag>.

Explanation:	You specified an invalid usage flag in the XML file.
User Response:	Edit the XML file. Or, export the object again and then import it.

REP_32121 Warning: Removing instance <instance name>. Could not find source instance for this Source Qualifier transformation instance.

Explanation:	You defined a Source Qualifier transformation in the XML file that is not associated with a source.
User Response:	Edit the XML file. Or, export the object again and then import it.

REP_32122 Error: Transformation <transformation name> has an invalid reusable setting.

Explanation:	You defined a non-reusable transformation as reusable in the XML file.
User Response:	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.

Explanation:	You deleted or renamed the first field for the Rank transformation in the XML file.
User Response:	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.

Explanation:	You did not define an expression type for the transformation in the XML file, or you defined an invalid expression type.
User Response:	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.

Explanation:	You did not define a Rank port type for the Rank transformation in the XML file.
User Response:	Edit the XML file and make sure there is only one field which has the port type as Rank. Or, export the object again and then import it.

REP_32132 Error: Transformation <transformation name> has duplicate group <group> due to the same group order.

Explanation:	You defined duplicated groups in the group order in the XML file.
User Response:	Edit the XML file and make sure the group order has different groups. Or, export the object again and then import it.

REP_32135 Error: Invalid precision: <number> specified for field: <field name>. The maximum precision is 65535.

Explanation:	You defined the field precision in the XML file greater than the maximum of 65,535.
User Response:	Edit the XML file and make sure the precision is less than or equal to the maximum precision, which is 65,535.

REP_32136 Error: Invalid scale: <number> specified for field: <field name>. The scale cannot be greater than the precision or the maximum scale which is 65535.

Explanation:	You defined the scale for a field in the XML file with an invalid number. The scale is either greater than the corresponding precision or greater than the maximum scale allowed, which is 65,535.
User Response:	Edit the XML file and make sure the scale for the field is less than or equal to the precision for the field.

REP_32137 The first field of lookup transformation <transformation name> has to be a Dynamic Lookup field when dynamic lookup cache is enabled. Transformation is not valid.

Explanation:	In the XML file, you defined the dynamic lookup cache attribute to YES, but you did not define the first lookup port as NewLookupRow.
User Response:	When the dynamic lookup cache attribute is set to YES, the first field has to be NewLookupRow. Edit the XML file, or export the object again and then import it.

REP_32138 Field <field name> for lookup transformation <transformation name> cannot be a Dynamic Lookup field when dynamic lookup cache is disabled. Transformation is not valid.

Explanation:	In the XML file, you defined a lookup port as NewLookupRow, but you defined the dynamic lookup cache as NO.
User Response:	You cannot have the NewLookupRow when the dynamic lookup cache attribute is set to NO. Edit the XML file, or export the object again and then import it.

REP_32139 In Lookup transformation <transformation name>, the content(s) of the generated Dynamic Lookup field <field name> has been changed. Transformation is not valid.

Explanation:	You modified the definition of the NewLookupRow port in the XML file.
User Response:	Do not change the NewLookupRow port in the XML file. Export the object again and then import it.

REP_32140 In Rank transformation <transformation name>, the content(s) of the RANKINDEX field <field name> has been changed. Transformation is not valid.

Explanation:	You modified the contents of the RANKINDEX field in the Rank transformation in the XML file.
User Response:	Do not modify the RANKINDEX field in the XML file. Export the object again and then import it.

REP_32141 In Sequence Generator transformation <transformation name>, the content(s) of field <field name> has been changed. Transformation is not valid.

Explanation:	You modified the definitions of the NEXTVAL and CURRVAL fields in the Sequence Generator transformation in the XML file.
User Response:	Do not modify these fields in the XML file. Export the object again and then import it.

REP_32144 Error: Missing or invalid attribute <attribute name> for <element name>: <attribute value>.

Explanation:	In the XML file, you entered an invalid value or no value for the specified attribute in the specified element.
User Response:	Edit the XML file and define a valid value for the specified attribute. Or, export the object again and then import it.

REP_32148 Error: Invalid datatype for mapping variable <MAPPINGVARIABLE name>.

Explanation:	You entered an invalid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element in the XML file.
User Response:	Edit the XML file and define a valid value for the DATATYPE attribute in the specified MAPPINGVARIABLE element. Or, export the object again and then import it.

REP_32149 Error: Invalid datatype for aggregate COUNT for mapping variable <MAPPINGVARIABLE name>.

Explanation:	In the XML file, you specified COUNT for the AGGFUNCTION attribute, and you entered an invalid value for the DATATYPE attribute for the specified MAPPINGVARIABLE element.
User Response:	Edit the XML file and enter either LONG or SHORT for the DATATYPE attribute for the MAPPINGVARIABLE element. Or, export the object again and then import it.

REP_32150 Error: Invalid aggregate type for mapping variable <MAPPINGVARIABLE name>.

Explanation:	In the XML file, you specified NO for the ISPARAM attribute, and you entered an invalid value for the AGGFUNCTION attribute for the specified MAPPINGVARIABLE element.
User Response:	Edit the XML file and enter COUNT, MIN, or MAX for the AGGFUNCTION attribute for the MAPPINGVARIABLE element. Or, export the object again and then import it.

REP_32151 Error: No name for the imported mapping variable.

Explanation:	In the XML file, the NAME attribute is missing from the MAPPINGVARIABLE element.
User Response:	Edit the XML file and add a NAME attribute to the MAPPINGVARIABLE element. Or, export the object again and then import it.

REP_32167 Error: Duplicate instances of type: <instance type> name: <instance name>.

Explanation:	In the XML file, you defined two instances of the same type with the same instance name.
User Response:	Edit the XML file and rename one of the transformation instance names. Also, rename any references to it in the mapping or mapplet. Import the object again.

REP_32171 The mapping originally assigned to this session has been changed. Cannot import the session.

Explanation:	You copied a mapping to a repository, but the mapping was modified, deleted or renamed.
User Response:	Copy or import the original mapping to the target repository again.

REP_32173 Error: Expected unsigned value for attribute: <attribute value>, found value: <value>.

Explanation:	You provided a negative or invalid value for an unsigned number in the XML file.
User Response:	Correct the value in the XML file. Or, export the object again and then import it.

REP_32174 Error: Invalid value: <value>, expecting unsigned value for attribute: <attribute>, for <element>: <element name>.

Explanation:	You provided a negative or invalid value for an unsigned number in the XML file.
User Response:	Edit the XML file and define a valid value for the attribute OCCURS. Or, export the object again and then import it.

REP_32175 Error: Invalid target database type: <target database name> for target: <target name>.

Explanation:	You defined an invalid database type in the XML file, or the database type is not valid for a target.
User Response:	Edit the XML file and define the correct database type for the DATABASETYPE attribute in the TARGET element. Or, export the object again and then import it.

REP_32176 Two or more fields in the xml data Source Qualifier transformation: <Source Qualifier name> refer to the same field: <field name> in the source.

Explanation:	In the XML file, you defined two transformation fields for the XML Source Qualifier transformation with the same value for the REF_SOURCEFIELD attribute.
User Response:	Edit the XML file and provide the correct value. Or, export the object again and then import it.

REP_32177 Error: Invalid database type '<database type>' for target '<target name>'. A plugin required to handle this is missing. This target will not be available for import.

Explanation:	In the XML file, you defined a plugin database type for the target, but you did not register the plugin in the PowerCenter Client.
User Response:	Register the plugin the PowerCenter Client before importing the file. Or, edit the XML file and specify an existing database type.

REP_32178 Error: Invalid Database Type: <database type> for target: <target name>, or the Database Type is not installed in this repository.

Explanation:	In the XML file, you defined a plugin database type for the target, but you did not install the plugin in the repository.
User Response:	Install the plugin in the repository before importing the file. Or, edit the XML file and specify an existing database type.

REP_32180 Error: Invalid Task type <task type> for task <task name>.

Explanation:	In the XML file, you specified an invalid TYPE attribute for the TASK element.
User Response:	Edit the XML file, and specify a valid TYPE for the TASK. Or, export the object again and then import it.

REP_32181 Error: Invalid Extension type: <session extension type> for element <SESSIONEXTENSION element>.

Explanation:	In the XML file, you specified an invalid TYPE attribute for the SESSIONEXTENSION element.
User Response:	Edit the XML file, and specify a valid TYPE for the SESSIONEXTENSION. Or, export the object again and then import it.

REP_32185 Error: The mapping <mapping name> associated with the session <session name> is invalid.

Explanation:	In the XML file, you specified a mapping that is invalid.
User Response:	In the Designer, validate the mapping before importing the session. Or, choose a different valid mapping for the session.

REP_32186 Error: expected a timer for task <Timer task name>.

Explanation:	In the XML file, you did not specify a TIMER element for the Timer TASK.
User Response:	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.

Explanation:	The XML file references a mapping that does not exist in the repository.
User Response:	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>.

Explanation:	In the XML file, the type of the SESSIONEXTENSION element does not match a SESSTRANSFORMATIONINST element.
User Response:	Edit the XML file, and verify the type of the SESSIONEXTENSION element matches a SESSTRANSFORMATIONINST element. Or, export the object again and then import it.

REP_32191 Warning: missing or empty attribute <attribute name> for element <element name>.

Explanation:	The XML file contains an empty or missing attribute.
User Response:	Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it.

REP_32192 Error: Invalid Component Type <session component type> for element <SESSIONCOMPONENT name>.

Explanation:	In the XML file, you specified an invalid TYPE attribute for the SESSIONCOMPONENT element.
User Response:	Edit the XML file, and specify a valid TYPE attribute for the SESSIONCOMPONENT element. Or, export the object again and then import it.

REP_32193 Error: missing or empty attribute <attribute name> for element <element name>.

Explanation:	The XML file contains an empty attribute, or the attribute is missing.
User Response:	Edit the XML file and specify a valid attribute for the element. Or, export the object again and then import it.

REP_32194 Error: Invalid partition type <PARTITIONTYPE name> for session transformation <SESSTRANSFORMATIONINST name>.

Explanation:	In the XML file, you specified an invalid PARTITIONTYPE attribute for the SESSTRANSFORMATIONINST element.
User Response:	Edit the XML file, and specify a valid PARTITIONTYPE. Or, export the object again and then import it.

REP_32195 Error: extension subType <SESSIONEXTENSION subtype> for extension type <SESSIONEXTENSION type> is invalid for element <SESSIONEXTENSION name>.

Explanation:	In the XML file, you specified an invalid SUBTYPE attribute for the SESSIONEXTENSION element with the specified TYPE attribute. The SUBTYPE attribute must be compatible with the TYPE attribute.
User Response:	Edit the XML file, and specify a valid SUBTYPE. Or, export the object again and then import it.

REP_32196 Error: connection reference <connection reference> with connection number <number> is not found for element <SESSIONEXTENSION name> due to the following error:

Explanation:	In the SESSIONEXTENSION element, the referenced CONNECTIONREFERENCE element does not exist.
User Response:	Edit the XML file, and specify a valid CONNECTIONREFERENCE. Or, export the object again and then import it.

REP_32198 Error: Invalid connection type <connection type> for connection reference <connection reference>.

Explanation:	In the XML file, you specified an invalid CONNECTIONTYPE attribute for the CONNECTIONREFERENCE element.
User Response:	Edit the XML file, and specify a valid CONNECTIONTYPE attribute. Or, export the object again and then import it.

REP_32199 Error: Invalid partition name <partition name> for element <element name>.

Explanation:	In the XML file, you specified an invalid PARTITIONNAME attribute for the specified element.
User Response:	Edit the XML file, and specify a valid PARTITIONNAME attribute. Or, export the object again and then import it.

REP_32202 Error: Invalid DSQ instance name < Source Qualifier transformation name> for session transformation instance <session transformation instance name>.

Explanation:	In the XML file, you specified a DSQINSTNAME attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element.
User Response:	Edit the XML file, and verify the DSQINSTNAME attribute matches the SESSTRANSFORMATIONINST element name. Or, export the object again and then import it.

REP_32203 Error: the number of partition <PARTITION name> is out of range [1-32] for session transformation <SESSTRANSFORMATIONINST name> in session <session name>.

Explanation:	The number of PARTITIONs under SESSTRANSFORMATIONINST is invalid.
User Response:	Remove, as appropriate, the PARTITIONs from under the SESSTRANSFORMATIONINST so that the number of PARTITIONs is less than or equal to 32.

REP_32204 Error: building session <session name>.

Explanation:	The SESSION element or some of its sub-elements are invalid.
User Response:	View the Output window for more information. Export the object again and then import it.

REP_32205 Error: Invalid DSQ <Source Qualifier name> of type <DSQINSTTYPE> for the extension in session transformation instance <SESSTRANSFORMATIONINST name>.

Explanation:	In the XML file, you specified a DSQINSTNAME and DSQINSTTYPE attribute in a SESSIONEXTENSION element that references a non-existent SESSTRANSFORMATIONINST element or a SESSTRANSFORMATIONINST element that does not match the name and type specified in the SESSIONEXTENSION element.
User Response:	Edit the XML file, and verify the DSQINSTNAME and DSQINSTTYPE attributes match the SESSTRANSFORMATIONINST element name and type. Or, export the object again and then import it.

REP_32207 Error: Invalid datatype for workflow variable <workflow variable name>.

Explanation:	In the XML file, you specified an invalid DATATYPE attribute for the WORKFLOWVARIABLE element.
User Response:	Edit the XML file, and specify a valid DATATYPE attribute for the WORKFLOWVARIABLE element. Or, export the object again and then import it.

REP_32208 Error: The extension of type <SESSIONEXTENSION type> and subtype <SESSIONEXTENSION subtype> does not exist for session transformation instance <SESSTRANSFORMATIONINST name>.

Explanation:	In the XML file, the TYPE and SUBTYPE attributes for the SESSIONEXTENSION element are not supported for the SESSTRANSFORMATIONINST element.
User Response:	Edit the XML file, and specify TYPE and SUBTYPE attributes in the SESSIONEXTENSION element that the SESSTRANSFORMATIONINST element supports.

REP_32209 Error: Invalid suspension email <SUSPENSION_EMAIL name> for workflow <workflow name>.

Explanation:	In the XML file, you specified a SUSPENSION_EMAIL attribute for the WORKFLOW element that references a non-existent Email task.
User Response:	Edit the XML file, and verify the SUSPENSION_EMAIL matches a reusable Email task. Or, export the object again and then import it.

REP_32210 Error: Name conflict or invalid object name <object name> for element <element name>.

Explanation:	In the XML file, you entered invalid characters for the specified element name, or you specified an element name that conflicts with another element name.
User Response:	Edit the XML file, and rename the element using valid characters only. Or, export the object again and then import it.

REP_32211 Warning: missing both start and end range in key <KEYRANGE> for element <element name>.

Explanation:	In the XML file, both the STARTRANGE and ENDRANGE attributes are empty for the specified KEYRANGE element.
User Response:	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.

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

Explanation:	In the XML file, you included a non-partitionable SESSTRANSFORMATIONINST element in a pipeline with more than one partition.
User Response:	Export the object again and then import it.

REP_32214 Warning: invalid key name <KEYRANGE or HASHKEY name> for element <element name>.

Explanation:	In the XML file, you specified a NAME attribute in a KEYRANGE or HASHKEY element that references a non-existent transformation port.
User Response:	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>.

Explanation:	In the XML file, you specified an invalid DSQINSTTYPE attribute for the SESSIONEXTENSION element.
User Response:	Edit the XML file, and specify a valid DSQINSTTYPE attribute. Or, export the object again and then import it.

REP_32216 Error: connection reference <CONNECTIONREFERENCE name> type <TYPE> and subtype <SUBTYPE> is not valid for the extension.

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

Explanation:	In the XML file, you included a PARTITIONNAME attribute in a CONNECTIONREFERENCE element that is not partitionable.
User Response:	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>.

Explanation:	In the XML file, you specified an invalid TYPE attribute in the TASK element.
User Response:	Edit the XML file, and enter a valid TYPE for the TASK. Or, export the object again and then import it.

REP_32219 Warning: cannot find the referenced config object <REFOBJECTNAME>, default session config is used.

Explanation:	In the XML file, you specified a REFOBJECTNAME attribute in a CONFIGREFERNCE element that references a non-existent CONFIG element.
User Response:	This is a warning. The Workflow Manager uses a default session configuration.

REP_32220 Invalid partition type <PARTITIONTYPE> for session transformation <SESSTRANSFORMATIONINST>.

Explanation:	In the XML file, you specified an invalid PARTITIONTYPE attribute in the SESSTRANSFORMATIONINST element.
User Response:	Edit the XML file, and enter a valid PARTITIONTYPE. Or, export the object again and then import it.

REP_32222 Error: duplicate object <object name> of type <object type>.

Explanation:	The XML file contains two objects with the same name and type.
User Response:	Edit the XML file, and rename the duplicate object. Or, export the object again and then import it.

REP_32223 Error: two Schedulers of conflicting types specified for workflow <WORKFLOW name>: reusable <SCHEDULER under FOLDER> and nonreusable <SCHEDULER under WORKFLOW>.

Explanation:	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.
User Response:	Edit the XML file, and verify the SCHEDULERNAME and REUSABLE_SCHEDULER attributes refer to only one SCHEDULER. Include reusable schedulers under the FOLDER element, and include non-reusable schedulers under the WORFKLOW element. Or, export the object again and then import it.

REP_32224 Error: Task <TASKNAME> is not found for instance <TASKINSTANCE name>.

Explanation:	In the XML file, you specified a TASKNAME attribute in a TASKINSTANCE element that references a non-existent reusable TASK element.
User Response:	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_32225 Error: Invalid value <value> for <attribute in SCHEDULER element> in Scheduler.

Explanation:	In the XML file, you specified a invalid value for the specified attribute in the SCHEDULER element.
User Response:	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.

Explanation:	You imported a Custom transformation defined with no input groups.
User Response:	Edit the XML file and define at least one input group. Or, export the object and import it again.

REP_32293 Error: The transformation <transformation name> has no output groups.

Explanation:	You imported a Custom transformation defined with no output groups.
User Response:	Edit the XML file and define at least one output group. Or, export the object and import it again.

REP_32294 Error: Group <group> of the transformation <transformation name> is both an input group and an output group.

Explanation:	You imported a Custom transformation with a group defined as both an output and input group.
User Response:	Edit the XML file and define the group as either an input, output, or input/output group. Or, export the object and import it again.

REP_32409 Session <session name> has a log file name which is longer than 600 characters. Session is not valid.

Explanation:	The session log file name is too long.
User Response:	On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension.

REP_32410 Session has a log file name which is longer than 600 characters. Session is not valid.

Explanation:	The session log file name is too long.
User Response:	On the session Properties tab, specify a session log file name of 600 characters or fewer, including the file extension.

REP_32413 Session <session name> has a log directory name which is longer than 600 characters. Session is not valid.

Explanation:	The session log file directory name is too long.
User Response:	On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters.

REP_32414 Session has a log directory name which is longer than 600 characters. Session is not valid.

Explanation:	The session log file directory name is too long.
User Response:	On the session Properties tab, specify a session log file directory name of 600 characters or fewer, including delimiters.

REP_32426 Session config <session configuration object name>. The number of runs to save session log on must be in the range 0 to 2147483647.

Explanation:	For the named session configuration object, you are saving session logs by number of runs. The number of runs you specified is out of range.
User Response:	On the session properties Config Object tab, Log Options settings, specify a number of runs between 0 and 2,147,483,647.

REP_32427 The number of runs to save session log on must be in the range 0 to 2147483647.

Explanation:	You are saving session logs by number of runs. The number of runs you specified is out of range.
User Response:	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.

Explanation:	The parameter file name for the workflow is too long.
User Response:	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.

Explanation:	The workflow log file name is too long.
User Response:	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.

Explanation:	You are saving workflow logs by number of runs. The number of runs you specified is out of range.
User Response:	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.

Explanation:	The workflow log file directory name is too long.
User Response:	On the workflow Properties tab, specify a workflow log file directory name of 600 characters or fewer, including delimiters.

REP_32472 'Save workflow log for these runs' must be in the range of 0 to 2147483647.

Explanation:	You are saving workflow logs by number of runs. The number of runs you specified is out of range.
User Response:	On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647.

REP_32475 Workflow task <workflow name> parameter file name is too long.

Explanation:	The parameter file name for the named workflow is too long.
User Response:	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.

Explanation:	The workflow log file name for the named workflow is too long.
User Response:	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.

Explanation:	The workflow log file directory name for the named workflow is too long.
User Response:	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.

Explanation:	The session log save option is invalid. This can occur if the session was imported and the session log save option was incorrectly defined.
User Response:	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.

Explanation:	The workflow save log option is invalid. This can occur if the workflow was imported and the workflow log save option was incorrectly defined.
User Response:	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.

Explanation:	You are saving workflow logs for the named workflow for a certain number of runs. The number of runs you specified is out of range.
User Response:	Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure the number of runs is between 0 and 2,147,483,647.

REP_32483 ‘Save workflow log for these runs’ must be in the range of 0 to 2147483647.

Explanation:	You are saving workflow logs by number of runs. The number of runs you specified is out of range.
User Response:	On the workflow Properties tab, specify a number of runs between 0 and 2,147,483,647.

REP_32490 Workflow task <workflow name> log directory name must have a delimiter.

Explanation:	The workflow log file directory name for the named workflow does not end in a delimiter, either use “\” on Windows systems, or “/” on UNIX systems.
User Response:	On the workflow Properties tab, include the appropriate delimiter after the workflow log file directory name.

REP_32491 Log directory name must have a delimiter.

Explanation:	The workflow log file directory name does not end in a delimiter, either use “\” on Windows systems, or “/” on UNIX systems.
User Response:	On the workflow Properties tab, include the appropriate delimiter after the workflow log file directory name.

REP_32494 The first character in a name cannot be a number.

Explanation:	You entered a name in which the first character is a number.
User Response:	Enter a name in which the first character is a letter.

REP_32495 Spaces are not allowed in a name.

Explanation:	You entered a name that includes spaces.
User Response:	Enter a name that contains no spaces.

REP_32496 The first character in a name cannot be <character>.

Explanation:	You entered a name in which the specified character is not allowed as the first character in the name.
User Response:	Enter a name that does not contain the specified character.

REP_32497 The character <character> is not allowed in a name.

Explanation:	You entered a name in which the specified character is not allowed.
User Response:	Enter a name that does not include this character.

REP_32498 Name length is too large.

Explanation:	You entered a name that is too long.
User Response:	Enter a shorter name.

REP_32499 This is not a valid name.

Explanation:	Internal error.
User Response:	Contact the plug-in vendor.

REP_32523 Session <session name> has different connection subtype across partitions.

Explanation:	The named session has multiple partitions. The source or target connection types for at least two partitions differ.
User Response:	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.

Explanation:	The current session has multiple partitions. The source or target connection types for at least two partitions differ.
User Response:	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 <session name>.

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

Explanation:	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.
User Response:	Edit the session properties and either specify a hash key at the named transformation or change the partition type.

REP_32534 Invalid hash key <key name> for <transformation name> in session <session name>.

Explanation:	You selected hash user keys partitioning at the named transformation, but the hash key you chose is no longer valid. This may have occurred because you updated the mapping and the selected key is no longer in the named transformation.
User Response:	Edit the session properties and specify a new hash key at the transformation.

REP_32535 Invalid hash key <key name> for instance <transformation name>.

Explanation:	You selected hash user keys partitioning at the named transformation instance, but the hash key you chose is no longer valid. This may have occurred because you updated the mapping and the selected key is no longer in the named transformation.
User Response:	Edit the session properties and specify a new hash key at the transformation instance.

REP_32536 Hash key <key name> for instance <transformation name> in session <session name> has invalid port type.

Explanation:	You selected key range or hash user keys partitioning at the named transformation instance, but the key is no longer an input or an input/output port. This may have occurred because you updated the mapping and changed the port types in the named transformation instance.
User Response:	Edit the session properties and select an input or input/output port as the key.

REP_32537 Hash key <key name> for instance <transformation name> in session <session name> has invalid port type.

Explanation:

You selected key range or hash user keys partitioning at the named transformation instance, but the key is no longer an input or an input/output port. This may have occurred because you updated the mapping and changed the port types in the named transformation instance.

Edit the session properties and select an input or input/output port as the key.

Same as REP_32536.

REP_32542 Empty key range for <transformation name> in session <session name>.

Explanation:	You selected key range partitioning at the named transformation. Both the start and end values for at least one key range are empty, and there is no a SQL override or filter condition for the transformation.
User Response:	Either supply the missing start and end values for the key range, or specify a SQL override or filter condition for the transformation.

REP_32543 Missing required hash key for <transformation name>.

Explanation:	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.
User Response:	Either supply the missing start and end values for the key range, or specify a SQL override or filter condition for the transformation.

REP_32544 Timer task <Timer task name> uses an empty workflow variable.

Explanation:	The Timer task uses a workflow variable to calculate the wait, but the variable has a null value.
User Response:	Verify that the Timer task uses the correct variable. Also check the workflow or server log to determine why the variable value is null.

REP_32546 Timer task <Timer task name> uses an invalid workflow variable.

Explanation:	The Timer task uses a workflow variable to calculate the wait, but the variable is invalid.
User Response:	Verify that the Timer task uses the correct variable. Also check the workflow to make sure the variable exists.

REP_32548 Timer task <Timer task name> uses a workflow variable which is not Date/Time datatype.

Explanation:	The named Timer task uses a workflow variable to calculate the wait, but the variable datatype is not Date/Time.
User Response:	Check the timer task to make sure you specified the correct variable. Also check the workflow to make sure the variable datatype is Date/Time.

REP_32550 Key not specified for key range partition for <partition name:transformation name> in session <session name>.

Explanation:	You selected key range partitioning at the named transformation, but there is no partition key. This may have occurred because you updated the mapping and replaced the transformation with one that contains different ports.
User Response:	Edit the session properties and either specify a partition key at the transformation or change the partition type.

REP_32551 Key not specified for key range partition for <partition name:transformation>.

Explanation:	You selected key range partitioning at the named transformation, but there is no partition key. This may have occurred because you updated the mapping and replaced the transformation with one that contains different ports.
User Response:	Edit the session properties and either specify a partition key at the transformation or change the partition type.

REP_32558 Workflow task <workflow name>: ‘Save workflow log for these runs’ has an invalid Integration Service variable associated with it.

Explanation:	You are saving workflow logs for the named workflow by number of runs. The number of runs you specified is based on an invalid variable.
User Response:	Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure that you specified the correct service variable. Also, verify that the variable you specified is an integer variable.

REP_32559 ‘Save workflow log for these runs’ has an invalid Integration Service variable associated with it.

Explanation:	You are saving workflow logs by number of runs. The number of runs you specified is based on an invalid service variable.
User Response:	Check the Workflow Logs For These Runs option on the workflow Properties tab. Make sure that you specified the correct service variable. Also verify that the service variable you specified is an integer variable.

REP_32701 Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>, session <session name>).

Explanation:	You ran a session with a hash user keys partition point at a multi-group transformation, but you did not specify a key.
User Response:	Edit the session properties and specify a key for the group. Or, change the partition type of the group.

REP_32702 Key not specified for Hash User Keys partition (group <group>, instance <transformation instance name>).

Explanation:	You ran a session with a hash user keys partition point at a multi-group transformation, but you did not specify a key.
User Response:	Edit the session properties and specify a key for the group. Or, change the partition type of the group.

REP_32705 Key not specified for Key Range partition (group <group>, instance <transformation instance name>, session <session instance name>).

Explanation:	You selected key range partitioning, but you did not specify a key for the group.
User Response:	Edit the session properties to specify a key for the group or change the partition type for the group.

REP_32706 Key not specified for Key Range partition (group <group> instance <transformation instance name>).

Explanation:	You selected key range partitioning, but you did not specify a key for the group.
User Response:	Edit the session properties to specify a key for the group or change the partition type for the group.

REP_32827 Syntax error: bad variable name <variable name>.

Explanation:	You altered the XML file or created an invalid mapping variable name. The imported mapping variable has an invalid name. The name has to start with $$, has to be longer than two characters, and can only have alphanumeric characters and underscores.
User Response:	Make sure mapping variable names follow the correct format.

REP_32828 A variable with this name, <variable name>, already exists in the mapping.

Explanation:	You altered the XML file or created an invalid mapping variable name. The imported mapping variable name is not unique within the imported mapping.
User Response:	Make sure mapping variable names are unique within any mapping.

REP_32898 Warning: Failed to upgrade XML source <source>.

Explanation:	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.
User Response:	Re-import the XML source.

REP_32899 Warning: Failed to upgrade XML target <target>.

Explanation:	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.
User Response:	Re-import the XML target.

REP_51037 Database Connection Error: <error>.

Explanation:	The Repository Service or Repository Agent process could not connect to the database.
User Response:	Check preceding messages to see the cause of the error. Check the database log for related error messages. Verify the database user name, password, and connect string are correct.

REP_51042 Repository Agent connection failed. System Error (errno = <error number>) <error message>: Cannot read message header. Read <number> bytes.

Explanation:	The connection to the Repository Agent process failed due to a system error.
User Response:	Check the system event log for related error messages to see the cause of the error. Try the operation again. If the problem persists, contact the network administrator.

REP_51048 Communication failed because of network errors. [System Error (errno = <error number>): <error message>.] Please try connecting to the repository again.

Explanation:	The PowerCenter Client or the Integration Service cannot connect to the Repository Agent.
User Response:	Read the operating system error referenced in this message and make any necessary changes. There might be network problems.

REP_51054 Internal error: Cannot allocate buffer of size <size> bytes to receive incoming message. The system may be out of memory.

Explanation:	The system is low on resources.
User Response:	Free some system resources.
Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

REP_51056 Unable to read from client socket. Read <number> bytes.

Explanation:	The repository client lost connectivity to the Repository Agent process.
User Response:	Verify that the Repository Agent process is running. If the Repository Agent is not running, restart it. Also, verify the repository database is running.

REP_51058 Unknown TCP/IP error. Please try connecting to the repository again.

Explanation:	The PowerCenter Client or the Integration Service cannot connect to the Repository Agent due to a network problem. This might happen if the Repository Agent machine was disconnected from the network, or if it lost power.
User Response:	Verify the PowerCenter Client and Integration Service machines can connect to the Repository Agent machine and try to connect again.

REP_51059 Repository Agent connection failed, another Repository Agent on host <host name> port <port number> is already connected to this repository <repository name>.

Explanation:	There is another Repository Agent process already running for the repository.
User Response:	Connect to the running Repository Agent, or wait for it to shut down before connecting again.

REP_51071 Invalid name: You must specify a name.

Explanation:	You tried to create a metadata extension, but left the metadata extension name blank.
User Response:	Specify a name for the metadata extension.

REP_51072 A metadata extension named <metadata extension name> already exists in the current domain.

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

Explanation:	You entered a value for an integer metadata extension that is either too large or too small.
User Response:	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.

Explanation:	You tried to change the precision for a string metadata extension, but the existing string is longer than the precision you specified.
User Response:	Either shorten the length of the existing metadata extension and then change the precision, or specify a precision that is greater than or equal to the length of the existing metadata extension.

REP_51075 The maximum length is too large. Please specify a value smaller than or equal to <maximum length>.

Explanation:	You tried to enter a precision for a string metadata extension that is too long.
User Response:	Specify a precision that is less than or equal to the maximum length.

REP_51112 The reserved keyword <keyword> cannot be used.

Explanation:	You specified a keyword that is reserved. You cannot use reserved keywords.
User Response:	Specify a non-keyword.

REP_51115 A table with the name <table name> already exists. Please enter a unique name.

Explanation:	You specified a table name that is already in use.
User Response:	Enter a unique table name.

REP_51116 This business name has already been used by the source table <database name>:<table name> in the repository and has been renamed to <table name>. You must save your changes before renaming this table.

Explanation:	You changed the value for the business name in a source definition. You then attempted to enter the old business name in another source definition. This is not allowed. For example, you changed the business name in the source S1 from B1 to B2. You then entered the business name B1 to another source definition, S2.
User Response:	Save the changes in the repository after entering the new business name for the source definition. Then you can use the old business name for another source definition.

REP_51120 The column <column> cannot allow nulls.

Explanation:	The Integration Service received data for a column that is null. This is not allowed.
User Response:	Check the data and mapping for inconsistencies.

REP_51134 The absolute value of the scale cannot be larger than the length/precision.

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

Explanation:	You entered a value for scale that is less than the minimum allowed value.
User Response:	Enter a value for scale above the specified minimum value.

REP_51137 This business name has already been used by the target table <table name> in the repository and has been renamed to <table name>. You must save your changes before renaming this table.

Explanation:	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.
User Response:	Save the changes in the repository after entering the new business name for the target definition. Then you can use the old business name for another target definition.

REP_51178 Warning: A matching Application connection was detected, but you do not have permission to access this Application connection <connection name>. This Application connection will be copied and renamed to <new connection name>.

Explanation:	When you copy a folder, you do not have permission to a connection object in the target repository.
User Response:	The Copy Folder Wizard will copy the connection from the source repository and rename it.

REP_51292 Initialization property name cannot be empty.

Explanation:	There is no initialization property value.
User Response:	Add an initialization property.

REP_51294 Initialization property <property> doesn’t exist.

Explanation:	The specified initialization property does not exist.
User Response:	Specify an existing initialization property.

REP_51295 <property> is a built-in initialization property.

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

Explanation:	You attempted to modify the description of a built-in initialization property. This is not allowed.
User Response:	Do not modify the description of a built-in initialization property.

REP_51297 Built-in initialization property cannot be deleted.

Explanation:	You attempted to delete a built-in initialization property.
User Response:	Do not delete a built-in initialization property.

REP_51298 Initialization property name cannot have more than 80 characters.

Explanation:	The initialization property name exceeds 80 characters.
User Response:	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.

Explanation:	The repository database may have inconsistencies.
User Response:	Restore the repository from a backup file and check the database server log for errors.
Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

REP_51301 Unable to send messages to the Repository Service. Initialization of repository <repository name> failed.

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

REP_51304 Partition number <number> is not valid.

Explanation:	Plug-in internal error.
User Response:	Contact the plug-in application vendor.

REP_51343 Unable to connect to the database server. Please check the connection to the database server.

Explanation:	The Repository Agent process could not connect to the repository database server.
User Response:	Verify the repository database is running. Verify that you have a network connection to the repository database system. Verify the database user name, password, and connect string are correct. Verify the database type specified in the repository configuration is correct.

REP_51357 Failed to fetch the connection <connection name> specified for $Source because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use.

Explanation:	The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Source Connection Value session property, you did not specify Relational: or Application: before the connection name.
User Response:	Enter Relational: or Application: before the connection name for $Source Connection Value on the Properties tab of the session properties.

REP_51358 Failed to fetch the connection <connection name> specified for $Target because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use.

Explanation:	The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Target Connection Value session property, you did not specify Relational: or Application: before the connection name.
User Response:	Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties.

REP_51378 Failed to fetch the connection <connection name> specified for REH DB Log because multiple connections of different types have this name and the Integration Service cannot determine which one of these connections to use.

Explanation:	The specified database connection name exists as both a relational and application connection. When you entered the database connection name for the $Target Connection Value session property, you did not specify Relational: or Application: before the connection name.
User Response:	Enter Relational: or Application: before the connection name for $Target Connection Value on the Properties tab of the session properties.

REP_51444 “MessageSendBufferSize” value <message send buffer size> is invalid, ignoring invalid value <message send buffer size>. Using system default value.

Explanation:	The repository is on a Windows machine and the repository configuration file specifies an invalid value for the MessageSendBufferSize parameter. The Repository Agent uses the default message send buffer size.
User Response:	Edit the repository configuration file and verify the MessageSendBufferSize size is greater than or equal to zero. When you specify zero, the Repository Agent ignores the MessageSendBufferSize parameter.

REP_51445 “MessageReceiveBufferSize” value <message receive buffer size> is invalid, ignoring invalid value <message receive buffer size>. Using system default value.

Explanation:	The repository is on a Windows machine and the repository configuration file specifies an invalid value for the MessageReceiveBufferSize parameter. The Repository Agent uses the default message receive buffer size.
User Response:	Edit the repository configuration file and verify the MessageReceiveBufferSize size is greater than or equal to zero. When you specify zero, the Repository Agent ignores the MessageReceiveBufferSize parameter.

REP_51447 A repository request has timed out. [System Error (errno = <error number>): <system error message>]. Please try connecting to the repository again.

Explanation:	The timeout values of the Repository Service requests are too small. Or, you made a request for a large repository object, which decreased network performance.
User Response:	Increase the MessageReceiveTimeout value and MessageSendTimeout value from the repository configuration.
Explanation:	Repository Service request timed out due to a slow network.
User Response:	Verify that the network is running properly.
Explanation:	The repository is stopped.
User Response:	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>.

Explanation:	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.
User Response:	Accept the default value for Database Pool Expiry Timeout. Enter a valid value for Database Pool Expiry Timeout in the Repository Service advanced properties.

REP_51503 The value <number of connections> specified for Database Pool Expiry Threshold value is invalid. The Repository Service is using the default value <number>.

Explanation:	The value specified for Database Pool Expiry Threshold is invalid. For example, it may be less than the minimum, or it may be a negative number or a letter.
User Response:	Accept the default value for Database Pool Expiry Threshold. Enter a valid value for Database Pool Expiry Threshold in the Repository Service advanced properties.

REP_51507 Target <target name> cannot have FileName field.

Explanation:	You are importing a target that has a column defined as a FileName port, but the target does not support a FileName port. The target must be a flat file.
User Response:	Remove the ISFILENAMEFIELD = “YES” field attribute in the XML file.

REP_51508 Target <target name> has existing FileName field.

Explanation:	You are importing a target the has two FileName ports. A flat file target can have one FileName port.
User Response:	Remove the ISFILENAMEFIELD =“YES” field attribute for one of the columns in the XML file.

REP_51509 Workflow task <workflow ID> maximum automatic recovery attempts must be in the range of 0 to 2147483647.

Explanation:	The Maximum Automatic Recovery Attempts option contains a negative number.
User Response:	Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab. The number must be zero or greater.

REP_51510 Maximum automatic recovery attempts must be in the range of 0 to 2147483647.

Explanation:	The Maximum Automatic Recovery Attempts is a negative number.
User Response:	Change the Maximum Automatic Recovery Attempts option on the workflow Properties tab. The number must be zero or greater.

REP_51814 Repository connection failed.

Explanation:	The Repository Agent process could not connect to the repository database.
User Response:	Check preceding messages to see the cause of the error.

REP_51815 Failed to read the repository connection information.

Explanation:	The Repository Agent process could not read connectivity information from the repository configuration.
User Response:	Verify the information in the repository configuration is correct.

REP_51832 The license key for the repagent has expired.

Explanation:	The product license key is expired.
User Response:	Contact Informatica Global Customer Support to obtain a new license key.

REP_51848 Cannot enable object versioning without a team-based development license key.

Explanation:	PowerCenter cannot enable object versioning because the license assigned to the repository does not have the team-based development option.
User Response:	Apply a license that has the team-based development option to the Repository Service. You can purchase this option from Informatica.

REP_51849 The versioned repository cannot be enabled or restored without a team-based development license key.

Explanation:	PowerCenter cannot enable object versioning until you have a team-based development license key.
User Response:	Apply the Repository Service to a license that has the team-based development option. You can purchase this option from Informatica.

REP_51961 The value of the environment variable <environment variable name> needs to be encrypted with the latest version of pmpasswd.

Explanation:	The environment variable was encrypted using an old version of pmpasswd. Effective in PowerCenter 8.1, pmpasswd uses a new, more robust encryption algorithm.
User Response:	Use the current version of pmpasswd to encrypt all passwords that you store as environment variables, and update the environment variables with the new encrypted passwords.

REP_55035 An error occurred during deployment.

Explanation:	The Repository Agent process could not copy a folder.
User Response:	Check preceding messages to see the cause of the error. This error message may be preceded by REP_51056.

REP_55036 An error occurred during folder comparison.

Explanation:	The Repository Agent process could not compare two folders.
User Response:	Check preceding messages to see the cause of the error.

REP_55102 Failed to connect to Repository Service <service name>.

Explanation:	The login information is not valid or the user does not have permissions on the repository.
User Response:	Action: Verify that the user name and password is correct. Also verify that the user has permissions on the repository.
Explanation:	The host is not accessible from the client machine because of a firewall or an incorrect host name and port number was specified for the repository connection.
User Response:	Verify that the connection information is valid and that the client machine can access the host machine.
Explanation:	The repository version is not the same version as the PowerCenter Client or the Integration Service.
User Response:	Verify that the PowerCenter Client, the Integration Service, and the Repository Service are the same product version. If not, upgrade them to the same version.
Explanation:	The application encountered an error while connecting to the repository.
User Response:	Check the preceding messages to see the cause of the error.

REP_57060 Login failure.

Explanation:	The Service Manager could not authenticate the user.
User Response:	Check the additional error messages for more information.

REP_57064 Maximum number of connections exceeded.

Explanation:	The maximum number of connections to the Repository Agent process exceeded the number of connections specified in the repository configuration.
User Response:	Edit the repository configuration and increase the value of the MaximumConnections configuration option. Also, closed inactive connections to the repository.

REP_57071 Unable to connect to the repository database. Please check the Repository Agent configuration.

Explanation:	The Repository Agent could not connect to the repository database.
User Response:	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.

Explanation:	The Repository Agent process exceeded the number of repository object locks specified in the repository configuration.
User Response:	Edit the repository configuration and increase the value of the MaximumLocks configuration option. Also, release residual locks.

REP_57145 No data found in the database.

Explanation:	An internal error occurred due to inconsistent data in the repository.
User Response:	Contact Informatica Global Customer Support.

REP_57151 Invalid function arguments.

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

REP_57169 Multiple connections of different types have the same name, and some sessions and/or transformations contain this name without a type prefix (such as “Relational:”) as connection information. This ambiguity must be resolved by prefixing those connection information.

Explanation:	The specified database connection name exists as both a relational and application connection. You entered the database connection name for the Stored Procedure or Lookup transformation location in the session properties, but you did not specify Relational: or Application: before the connection name.
User Response:	Enter Relational: or Application: before the connection name for the Stored Procedure or Lookup transformation location in the session properties.
Explanation:	The database connection name in the From field in the Replace Connections dialog box exists as both a relational and application connection. You entered the database connection name in at least one session or transformation, but you did not specify Relational: or Application: before the connection name.
User Response:	Enter Relational: or Application: before the connection name in all transformation properties and session properties that specify this database connection name.

REP_57201 Internal Error: Repository object is inconsistent.

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

REP_57269 This connection has been terminated.

Explanation:	A repository connection ended because a repository or domain administrator terminated the repository connection, and then a PowerCenter Client tried to reconnect to the repository with the same connection.
User Response:	Verify that the repository administrator does not need to have all users disconnected from the repository for maintenance or other purposes. Then retry the operation in the PowerCenter Client.

REP_58224 Failed to connect from <PowerCenter Client tool> to repository <repository name> because the repository users and groups have not been upgraded.

Explanation:	The PowerCenter Client could not connect to a repository because the repository users and groups have not been upgraded.
User Response:	Upgrade the repository users and groups in the Administrator tool. Then retry the operation in the PowerCenter Client.

REP_61002 WARNING: <XML definition> contained elements or attributes whose prefixes were removed.

Explanation:	You are upgrading an XML definition that contains prefixed attributes or elements. The XML parser removes prefixes from attributes and elements and completes the repository upgrade.
User Response:	Complete the repository upgrade and import the XML definition again.

REP_61003 Empty key range for key <key name> (group <group>, instance <transformation instance name>, session <session instance name>).

Explanation:	You did not specify a key range for the specified key.
User Response:	Edit the key range and specify the start and end value for the key.

REP_61004 Empty key range for key <key name> (group <group> session <session name>).

Explanation:	You did not specify a key range for the specified key.
User Response:	Edit the key range and specify the start and end value for the key.

REP_61010 Failed to validate transformation field <field name>.

Explanation:	Internal error. The field ID or the table ID that the field belongs to is zero.
User Response:	Contact Informatica Global Customer Support.

REP_61011 Cannot have cycles in transformation fields.

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

REP_61012 Error: Field <port name> of transformation <transformation name> could not be validated.

Explanation:	The Designer could not validate the port in the transformation.
User Response:	Check other error messages preceding this error message.

REP_61013 Invalid group encountered while validating group order.

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

REP_61014 Error: The groups of transformation <transformation name> could not be validated.

Explanation:	The Designer could not validate the transformation.
User Response:	Check other error messages preceding this error message.

REP_61027 Unable to set database connection property.

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

REP_61031 Failed to upgrade <XML definition> because removal of prefixes generated an invalid XPATH.

Explanation:	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.
User Response:	Import the XML definition again.

REP_61032 Failed to upgrade <XML source> because removal of prefixes caused element names to conflict!

Explanation:	The upgrade strips prefixes from XML element names. The upgraded names may conflict with other element names.
User Response:	Import the XML definition again.

REP_61059 Warning: Failed to upgrade XML source <source>, version <version>, folder <folder>.

Explanation:	You cannot upgrade the source XML definition because it has inconsistencies.
User Response:	The XML definition is unusable. You must recreate it.

REP_61060 Warning: Failed to upgrade XML target <target>, version <version>, folder <folder>.

Explanation:	You cannot upgrade the target XML definition because it has inconsistencies.
User Response:	The XML definition is unusable. You must recreate it.

REP_61063 An error was encountered during the upgrade.

Explanation:	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.
User Response:	Run the upgrade again. If the upgrade fails again, call Informatica Global Customer Support.

REP_62340 Transformation <source or target instance name> uses connection variable <connection variable name>, but its value is not specified.

Explanation:	The source or target connection name is specified using the connection variable $Source or $Target. The value of the connection variable is not defined and the Integration Service cannot determine which database connection to use when it runs the session.
User Response:	Enter a value for the $Source or $Target connection variable on the General Options settings of the Properties tab in the session properties.

REP_62373 Lookup Transformation <transformation name> has no associated Partial Pipeline. No single group Source Qualifier of name <Lookup table name>. Transformation is not valid.

Explanation:	The Pipeline Lookup transformation is not valid because there is no valid partial pipeline to lookup. The partial pipeline does not have a single group source in the Source Qualifier for a lookup. Therefore, the Lookup Table Name attribute in the Pipeline Lookup transformation does not match the Source Qualifier name in the partial pipeline.
User Response:	Verify that the partial pipeline is valid and has a single group source in the Source Qualifier for the lookup.

REP_62377 User name variable <variable name> is not well defined.

Explanation:	The user name for a connection object is defined in a parameter file using session parameter $ParamName. The session parameter value is incorrect. For example, the parameter value is blank, or the parameter is not defined in the parameter file.
User Response:	Verify that the parameter is defined in the parameter file. Verify that the parameter value is not blank.

REP_62378 Password variable <variable name> is not well defined.

Explanation:	The password for a connection object is defined in a parameter file using session parameter $ParamName. The session parameter value is incorrect. For example, the parameter value is blank, or the parameter is not defined in the parameter file.
User Response:	Verify that the parameter is defined in the parameter file. Verify that the parameter value is not blank.

REP_62379 Connection name <parameter value> for connection variable <variable name> is not well defined.

Explanation:	A session parameter such as $DBConnectionName was used to define a session connection. In the parameter file, the session parameter value is incorrect. For example, the parameter value is blank, or the parameter is not defined in the parameter file.
User Response:	Verify that the parameter is defined in the parameter file. Verify that the parameter value is not blank.

REP_62385 Advanced recovery cannot be enabled since the session has mapping variables.

Explanation:	If a session uses mapping variables, you cannot configure the session recovery strategy to resume from the last checkpoint.
User Response:	To set the recovery strategy to resume from the last checkpoint, remove the mapping variables in the session.

REP_62386 Advanced recovery cannot be enabled for session <session name> since the session has mapping variables.

Explanation:	If a session uses mapping variables, you cannot configure the session recovery strategy to resume from the last checkpoint.
User Response:	To set the recovery strategy to resume from the last checkpoint, remove the mapping variables in the session.

REP Messages

REP_12001 Failed to log onto database server.

REP_12005 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.

REP_12014 An error occurred while accessing the repository.

REP_12021 Failed to connect to local repository <local repository name> in domain <PowerCenter domain of local repository> from global repository <global repository name> in <PowerCenter domain of global repository>.

REP_12022 Failed to connect to global repository <global repository name> in domain <PowerCenter domain of global repository> from local repository <local repository name> in <PowerCenter domain of local repository>.

REP_12033 The repository being accessed is incompatible with this version.

REP_12119 A repository does not exist at the specified database connection.

REP_12122 Unable to unlock this folder. Please try again.

REP_12123 Unable to delete this folder. Please try again.

REP_12124 Unable to delete this folder. The folder is in use by another user.

REP_12164 Domain-related error: <error message>.

REP_12225 The value entered is not valid for memory attributes.

REP_12233 Increment By must be less than or equal to 2147483647.

REP_12325 Internal error. No connection callback.

REP_12326 Error getting connection information for remote repository.

REP_12327 Internal error. Connection callback returned an error.

REP_12328 The repository at this location does not have the same name.

REP_12330 Failed to fetch repository information.

REP_12332 Error initializing repository object information.

REP_12333 More than one GDR found.

REP_12334 Repository name mismatch.

REP_12335 The current repository is not a GDR.

REP_12336 This repository is already registered with the GDR <global repository name>.

REP_12337 This is not a local repository.

REP_12338 A repository with this name has already been registered.

REP_12339 Internal error. Error allocating a new repository ID.

REP_12340 Error updating remote repository.

REP_12341 Error updating GDR.

REP_12342 The selected repository is not registered with the current Global Repository.

REP_12346 Memory allocation failed.

REP_12347 An error occurred while updating connection information in the repository.

REP_12352 The current user does not have the privilege to perform this operation.

REP_12355 The object <object name> has been modified since the time it was read.

REP_12357 The object <object name> is already locked by <user name>. Do you want to reobtain the lock?

REP_12363 Warning: Unable to check whether correct indices for the Teradata repository have been created. Please verify that you backup the repository and then restore it after you upgrade it.

REP_12364 For Teradata upgrade process to be complete, please take a backup of the repository (repository_name), delete existing repository and restore from the backup file. Then start the repository.

REP_12370 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A repository upgrade is required.

REP_12371 The repository version is incompatible with this release of the product. (The repository version is <version> while the product expects <version>). A product upgrade is required.

REP_12372 The repository has data that is newer than this release of the product expects. (The repository data version is <version> while the product expects <version>). A product upgrade may be required.

REP_12373 The repository has data that may be too old for this release of the product. (The repository data version is <version> while the product expects <version>). A repository data upgrade may be required.

REP_12381 Unable to perform the operation since an expected object was not found. Please check the repository.

REP_12382 Error while updating the object information in the repository. Either no row or more than one row was updated.

REP_12386 There is no database object available for the repository <repository name>. (A repository is not supported on the requested database or the appropriate database driver is not available.

REP_12387 The attempt to get a <save/fetch> lock on the <object type> <object name> timed out due to the following conflicting lock: User <user name> on the computer <hostname> running the <application> obtained a <save/fetch> lock on the <object type> <object name> at <time>. Please try again.

REP_12389 Unable to set database connection property <number>.

REP_12390 Mapping <mapping name> contains a dependency that points to a non existent port. The mapping is assumed to be invalid.

REP_12392 GID creation failed for repository <repository name>.

REP_12403 Unable to retrieve locale information.

REP_12404 Failed to allocate new IDs for internal sequence generator: <sequence name>.

REP_12405 Failed to fetch new IDs.

REP_12415 Error comparing last saved times for objects in this folder!

REP_12416 Error comparing deployed times for shared folders!

REP_12422 Unable to connect to GDR!

REP_12449 Internal error.

REP_12450 Unable to create output file <file name>.

REP_12452 Failed to write to file <file name>!

REP_12454 Unable to open input file <file name>!

REP_12456 Failed to read from file <file name>!

REP_12457 Unexpected data in file <file name>!

REP_12466 Error inserting repository object information.

REP_12467 Error inserting repository object attribute information.

REP_12468 Error inserting server locale information.

REP_12469 Error initializing object tree.

REP_12470 Error updating repository information.

REP_12471 Error creating first user.

REP_12477 This repository contains folders which are currently in use. A repository cannot be deleted while it is in use.

REP_12488 Unable to add new internal sequence generator.

REP_12492 This repository contains folders which are currently in use. A repository cannot be upgraded while folders are in use.

REP_12494 The Repository is newer than the version supported by this software release. Unable to do an upgrade.

REP_12496 This repository is too old to be upgraded.

REP_12505 Error while executing script file <file name>.

REP_12581 An error occurred while opening a packaged SQL script file for execution. The product was probably not installed correctly. Contact customer support for assistance.

REP_12589 Error occurred in locking.

REP_12590 Error updating <repository name> in GDR.

REP_12591 Error updating <repository name> in GDR (Repository may be left in inconsistent state).

REP_12651 Memory allocation failed.

REP_12654 Password is too long.

REP_12678 The connection to Global DataMart Repository is unavailable for some reason.

REP_12708 Unable to allocate memory.