Troubleshooting Informatica Error Messages and Resolution – Part 401


TT_11171Warning: Sequence Generator Transformation <transformation name > has its <CurrVal> port connected. It is evaluation-order dependent, and thus mapping will be forced to run in one row per block mode.
Cause:The Integration Service processes one row in a block when CurrVal is connected.
Action:Informatica recommends that you do not use CurrVal. For example, connect NextVal to an Expression transformation in the pipeline to distribute the unique number.

TT_11172Dynamic Lookup [transformation name] requires that a string or binary lookup port and its associated port have the same length. Since lookup port [port name] had a length of [length] and the associated port [port name] had a length of [length], we used the larger length for both ports.
Cause:The dynamic Lookup transformation uses a string or binary lookup port of a certain precision with an associated port of a different precision. The Integration Service uses the larger precision for both ports.
Action:Edit the Lookup transformation and use the same precision for both ports.
TT_11174ERROR: Lookup transformation <Lookup transformation name> has a binary port <port name> in lookup condition.
Cause:The specified Lookup transformation uses a binary port in the lookup condition, but the Integration Service cannot perform lookups on binary data.
Action:Remove the binary port from the lookup condition.

TT_11180Error: Multiple match policy in lookup cache <file name> is different from policy for lookup transformation <transformation name>.
Cause:The lookup cache was created with a match policy different from the multiple match policy used for this lookup transformation. This lookup transformation uses a dynamic lookup cache.
Action:Verify that both lookup transformations use the same multiple match policy.
TT_11204Error: Transformation <name>: Failed to expand cache file name prefix <prefix>.
Cause:The Integration Service cannot expand a parameter or variable in the lookup cache file name prefix.
Action:Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file.
Cause:The Integration Service cannot expand a parameter or variable in the lookup cache file name prefix due to an internal error.
Action:Contact Informatica Technical Support.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *