TE Messages

Explanation:	The repository database server could not provide the last saved time of the mapping. A previous problem with the database might have caused some data inconsistencies.
User Response:	Contact Informatica Global Customer Support.

TE_7104 An error occurred while creating group <group number> of target <target name>.

Explanation:	During session initialization, the Integration Service failed to create a group object.
User Response:	Review the session log for related messages.

TE_7105 An error occurred while creating transformation <transformation name>.

Explanation:	During session initialization, the Integration Service failed to create a transformation object.
User Response:	Review the session log for related messages.

TE_7106 Failed to allocate or initialize the group ID <group ID> for target <target name>.

Explanation:	During session initialization, the Integration Service failed to create an XML group ID.
User Response:	Check the previous message in the session log for more information.

TE_7112 Message recovery with non-repeatable source does not allow XML targets in the mapping.

User Response:

Use a target other than an XML target or disable message recovery.

TE_7117 A real-time session cannot have non-realtime SDK targets in the mapping.

Explanation:	You configured real-time flush latency in the session. However, the mapping contains an SDK target definition that you cannot use with real-time sessions.
User Response:	Disable real-time flush latency by setting it to 0.

TE_7122 The session is configured for user-defined commit, but the target <target name> is not receiving transactions from any upstream transformation.

Explanation:	The session is configured for user-defined commit, but the target in the mapping is not connected to an upstream effective transaction generator.
User Response:	Change the commit type, or connect the target to an effective transaction generator, such as a Transaction Control transformation.

TE_7127 You cannot perform a user-defined commit for a real-time session.

User Response:

Use a source-based commit, disable flush latency, or enable forced EOQ.

TE_7131 The transformation <transformation> is not configured to propagate transactions. The session cannot run in real time.

Explanation:	You configured real-time flush latency in the session or through the FlushLatency(n) filter condition for WebSphere MQ. The mapping configuration prevents the session from being run in real time.
User Response:	Disable flush latency, or verify that the mapping does not contain any real-time limitations.

TE_7133 The master input for the unsorted Joiner transformation <transformation name> cannot be partitioned because the Joiner transformation is not a partition point.

Explanation:	You partitioned the master pipeline without adding a partition point at the unsorted Joiner transformation. This can cause input rows from the same key value to be routed to different partitions.
User Response:	Add a hash auto-keys partition point at the Joiner transformation to ensure data of the same key value is routed to the same partition.

TE_7134 Warning. The master input for the sorted Joiner transformation <transformation name> is partitioned.

Explanation:	You partitioned the master pipeline, which contains a sorted Joiner transformation. If you did not group the sorted data before passing it to the Joiner transformation, you can get unexpected results.
User Response:	Verify that the partitions in the master pipeline are configured to pass sorted and grouped data to the sorted Joiner transformation.

TE_7135 You cannot recover a session when the target load group has multiple sources, and at least one source is a real-time source. The source names are <source names>.

Explanation:

You tried to recover a session that contains one target load order group with multiple sources, and one or more of those sources is a real-time source. The real-time sources in the target load order group are connected to a multiple input group transformation or target.

User Response:

If the sources are connected to a Joiner transformation, you can enable the backward compatibility flag. The backward compatibility flag allows the Integration Service to read sources connected to a Joiner transformation sequentially as it did in versions prior to 6.x.

If the sources in the target load order group are connected to a multiple input group other than the Joiner transformation, disable session recovery.

TE Messages

TE_7102 Initialization error. Failed to get the last saved time for mapping <mapping name>.

TE_7104 An error occurred while creating group <group number> of target <target name>.

TE_7105 An error occurred while creating transformation <transformation name>.

TE_7106 Failed to allocate or initialize the group ID <group ID> for target <target name>.

TE_7112 Message recovery with non-repeatable source does not allow XML targets in the mapping.

TE_7117 A real-time session cannot have non-realtime SDK targets in the mapping.

TE_7122 The session is configured for user-defined commit, but the target <target name> is not receiving transactions from any upstream transformation.

TE_7127 You cannot perform a user-defined commit for a real-time session.

TE_7131 The transformation <transformation> is not configured to propagate transactions. The session cannot run in real time.

TE_7133 The master input for the unsorted Joiner transformation <transformation name> cannot be partitioned because the Joiner transformation is not a partition point.

TE_7134 Warning. The master input for the sorted Joiner transformation <transformation name> is partitioned.

TE_7135 You cannot recover a session when the target load group has multiple sources, and at least one source is a real-time source. The source names are <source names>.