Message Reference > T Message Codes > TT Messages
  

TT Messages

TT_11009 Overflow error. The Sequence Generator transformation has reached the end of the configured end value.

User Response:
Change the end value or cycle the sequence.

TT_11013 An error occurred parsing group by ports.

Explanation:
In an Aggregator or Rank transformation, an aggregate expression is specified as a group by port. Group by ports cannot be aggregate expressions.
User Response:
Remove the aggregate expression from the group by port.
Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

TT_11014 An Aggregator transformation contains an expression or port that is not valid.

User Response:
Validate the expression, and then validate the mapping.
Explanation:
If the mapping is valid, this is an internal error.
User Response:
Contact Informatica Global Customer Support.

TT_11019 There is an error in the port <port name>. The default value for the port is set to: ERROR <error message>.

Explanation:
The named port is configured to generate the named message upon error.
User Response:
You can review the dropped row in the session log.

TT_11020 There is an error in the port <port name>. The default value for the port is set to: ABORT <error message>.

Explanation:
The port is configured to abort the session upon error.
User Response:
If you do not want to abort the session when the port contains an error, change the default value.

TT_11021 An error occurred moving data from the transformation <transformation name> to the transformation <transformation name>. The row was dropped.

User Response:
Review the session log for related messages about the row error. If you enabled row error logging, review the error log for related messages.

TT_11023 An error occurred converting data in the port <port name>. The row was dropped.

User Response:
Review the session log for related messages about the row error. If you enabled row error logging, review the error log for related messages.

TT_11041 Failed to initialize the transformation <transformation name>.

Explanation:
An error occurred preparing parameters for input and output ports of the transformation.
User Response:
Check the transformation input and output parameters.

TT_11070 The lookup override <lookup query> contains one or more characters that are not valid in the code page of the database connection. The invalid character starts at position <character position> in the query.

User Response:
Change the lookup override query to contain characters included in the lookup database connection code page.

TT_11077 The lookup query <lookup query> contains one or more characters that are not valid in the code page of the database connection. The invalid character starts at position <character position> in the query.

Explanation:
The lookup query contains one or more characters that are not encoded in the lookup database code page.
User Response:
Edit the lookup query so that the Integration Service can convert it from the Integration Service code page to the lookup database code page without loss of data.
Explanation:
The lookup database uses a code page that is not supported by Informatica.
User Response:
Select a code page for the lookup database that is supported by Informatica and contains encoding for the lookup data character set.

TT_11078 The stored procedure name <name of stored procedure> contains one or more characters that are not valid in the code page of the database connection. The invalid character starts at position <character position> in the name.

Explanation:
The stored procedure name contains one or more characters that are not encoded in the stored procedure database code page.
User Response:
Identify the invalid character referenced in the session log. Edit the stored procedure name so that the Integration Service can convert it from the Integration Service code page to the stored procedure database code page without loss of data.
Explanation:
The stored procedure database uses a code page that is not supported by Informatica.
User Response:
Select a code page for the stored procedure database that is supported by Informatica and contains encoding for the stored procedure data character set.

TT_11079 The field name <name of field> of stored procedure <name of stored procedure> contains one or more characters that are not valid in the code page of the database connection. The invalid character starts at position <character position> of the name.

Explanation:
The field name of a stored procedure contains one or more characters that are not encoded in the stored procedure database code page.
User Response:
Identify the invalid character referenced in the session log. Edit the stored procedure field name so that the Integration Service can convert it from the Integration Service code page to the stored procedure database code page without loss of data.
Explanation:
The stored procedure database uses a code page that is not supported by Informatica.
User Response:
Select a code page for the stored procedure database that is supported by Informatica and contains encoding for the stored procedure data character set.

TT_11090 The control expression of the Transaction Control transformation <transformation name> is evaluated to NULL.

Explanation:
The transaction control expression in a Transaction Control transformation evaluated to a null value. When the transaction control expression evaluates to any value other than continue, commit, or rollback, the Integration Service fails the session.
User Response:
Edit the transaction control expression so that it does not evaluate to NULL.

TT_11091 The control expression of the Transaction Control transformation <transformation name> is evaluated to <evaluated value>.

Explanation:
The transaction control expression in a Transaction Control transformation evaluated to an invalid value. When the transaction control expression evaluates to any value other than continue, commit, or rollback, the Integration Service fails the session.
User Response:
Edit the transaction control expression so that it does not evaluate to an invalid value.

TT_11100 The Joiner transformation <transformation name> input is not sorted. The row key value is <key value>.

Explanation:
The named Joiner transformation is configured to use sorted input, but the Joiner transformation received unsorted data.
User Response:
Configure the Joiner transformation to use unsorted input.
Verify that the session and mapping properties maintain sort order between the sorted data and the Joiner transformation.
In the mapping, verify that the columns in the join condition match the columns of the sorted data and that the mapping does not contain active transformations between the sorted data and the Joiner transformation.
In the session, verify that the partitioning properties maintain sort order between the sorted data and the Joiner transformation.

TT_11118 The cache directory configured for the transformation <transformation name> is empty or not valid.

User Response:
Specify a cache directory in the session or the transformation.

TT_11124 Warning. The number of rows output by a group of the source qualifier <transformation name> exceeds the limit of rows <number of rows> specified in the IDN license. No more rows will be processed on this group of the source qualifier.

Explanation:
The IDN license restricts the number of rows you can process in a group.
User Response:
Decrease the number of rows in the group or get a different license from Informatica.

TT_11134 The lookup cache file with the named prefix <prefix name> used by the Lookup transformation <Lookup transformation name> cannot be reused.

Explanation:
You attempted to use a persistent lookup cache that was incompatible with the Lookup transformation, and the Integration Service does not delete the lookup cache files when you use a named prefix. The lookup cache files can be unusable for the following reasons:
  • •If you change an attribute, such as the database connection in, the persistent cache may become incompatible with the Lookup transformation.
  • •If more than one session uses the same lookup cache name, the lookup cache may be incompatible with a Lookup transformation in one of the sessions. For example, if you modify the attributes in one session, but you do not modify the second session, the lookup cache becomes unusable for the second session.
  • •You upgraded the Integration Service. The format for information in the Lookup transformation in the upgraded version of the Integration Service is incompatible with the format of information in the cache file that was created by an earlier version of the Integration Service.
User Response:
Update the Lookup transformation attributes, or remove the existing lookup cache files. You must remove both the .idx and .dat files. This allows the Integration Service to create a lookup cache.

TT_11141 The transformation <transformation name> returned a row error status on receiving an input row on group <group>.

Explanation:
The Custom transformation procedure returned an error when it received a row in the specified input group. The Custom transformation procedure returned INFA_ROWERROR in the input row notification function.
User Response:
This is an informational message. If this is a recurring error, you may want to verify that the data passing into the Custom transformation meets the criteria defined by the Custom transformation procedure.

TT_11144 The cache for the Lookup transformation <transformation name> indicates that the source type is <source type>, but the source type for this transformation is <source type>.

Explanation:
The source type for the Lookup transformation was changed after the Integration Service saved the cache.
User Response:
Recache the lookup source, or change the source type to the previous type.

TT_11145 The cache for the Lookup transformation <transformation name> indicates that the source file is <file name>, but the source file specified is <file name>.

Explanation:
The source file name was changed after the Integration saved the lookup cache.
User Response:
Recache the lookup source, or change the lookup file name to the previous name.

TT_11146 The cache for the Lookup transformation <transformation name> indicates that the type of source file <source file type> does not match the one specified for the transformation.

Explanation:
The source file type in the session properties was changed after the session ran. For example, you may have changed the source file type from direct to indirect or from indirect to direct.
User Response:
Recache the lookup source, or change the lookup source file type in the session properties.

TT_11147 Lookup transformations <transformation name> and <transformation name> have the same cache file name prefix <prefix name> but have different source files <file name> and <file name>.

Explanation:
The cache file name prefix matches for each Lookup transformation, but the lookup sources have different file names.
User Response:
Configure the mapping so that the cache is no longer shared, or configure the session to use the same lookup source file.

TT_11148 The cache file name prefix for the Lookup transformations <transformation name> and <transformation name> have the same cache file name prefix <file name prefix> but have different source file types.

User Response:
Configure the session with the same lookup source file type for each Lookup transformation sharing the cache.

TT_11149 The Lookup transformation <Lookup transformation name> has an illegal file name <file name>.

Explanation:
You ran a session with a flat file lookup, and the Integration Service could not find the lookup file. Either the file name or directory was missing or invalid.
User Response:
In the session properties, verify the file name and directory of the lookup file source.

TT_11152 An error occurred processing the Normalizer transformation <transformation name>.

Explanation:
The mapping connects an active transformation and a passive transformation to the same downstream transformation or transformation input group.
User Response:
Remove the concatenation.

TT_11158 An error occurred reading the lookup source for the Lookup transformation <transformation name>.

Explanation:
The Integration Service encountered errors while reading the lookup source.
User Response:
Review the session log for related messages.

TT_11161 An error occurred reading the lookup source for the transformation <transformation name>. It fetched <number of read rows> rows and <number of error rows> error rows.

User Response:
Enable row error logging in the session, and check other error messages logged for more details. Also, verify that the code page for the lookup source is two-way compatible with the Integration Service and target code page.

TT_11166 You cannot connect the transformation <transformation name> downstream from a Sequence Generator transformation.

Explanation:
You connected a Sequence Generator transformation upstream from a Custom transformation or a transformation developed using the Custom transformation.
User Response:
Update the mapping.

TT_11168 The code page specified for transformation <transformation name> is not valid for the file <file name>.

User Response:
Specify a valid code page. The code page should specify the proper locale for the lookup source file.

TT_11169 The transformation <transformation name> code page <code page ID> is not found.

User Response:
Specify a valid code page. The code page should specify the proper locale for the lookup source file.

TT_11170 An error occurred processing transformation <transformation name> and creating locale from the code page <code page name> for file <file name>.

Explanation:
The code page you specified is not valid.
User Response:
Specify a valid code page. The code page should specify the proper locale for the lookup source file.

TT_11171 The Sequence Generator transformation <transformation name> has the CURRVAL port connected. When you connect the CURRVAL port, the Integration Service processes one row in each block.

User Response:
You can optimize performance by connecting only the NEXTVAL port in a mapping.

TT_11172 The dynamic Lookup transformation <transformation name> requires that a String or Binary lookup port and its associated port have the same length. Since lookup port <port name> has a length of <length> and the associated port <port name> has a length of <length>, the Integration Service used the larger length for both ports.

Explanation:
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.
User Response:
Edit the Lookup transformation and use the same precision for both ports.

TT_11180 The lookup cache <file name> was created with a match policy different from the multiple match policy used for the dynamic Lookup transformation <transformation name>.

User Response:
Verify that both lookup transformations use the same multiple match policy.

TT_11195 Warning. Unsorted input found when building the cache for the Lookup transformation <transformation name>. The current number of entries in the index cache is <number of entries>. The cache will be built by insertion. This will cause it to take longer and the index cache may require more space.

Explanation:
The SQL in the Lookup transformation does not sort data in the sort order that the Integration Service expects. The SQL sorts data in an incorrect order due to an ORDERBY clause in the SQL or because the user-defined SQL override retrieves the port data in a different order.
User Response:
To improve performance, review the SQL and fix the SQL to retrieve data in the sort order that the Integration Service expects.
Explanation:
The sort order settings for the database server and Integration Service do not match.
User Response:
To improve performance, configure a consistent sort order for the database server and the Integration Service.

TT_11204 An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the cache file name prefix <prefix>.

User Response:
Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file.
Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

TT_11209 The upgrade process failed to complete. The Sequence Generator transformation has an invalid datatype.

Explanation:
The mapping contains a Sequence Generator transformation in which the datatype for the NEXTVAL or CURRVAL output port is not Bigint.
User Response:
Import the mapping again or re-create the Sequence Generator transformation.

TT_11210 An error occurred expanding a parameter or variable in the Lookup transformation <transformation name> for the lookup table name <lookup table name>.

Explanation:
The session contains a mapplet variable or parameter to define a lookup table name. The Integration Service failed to expand the parameter or variable.
User Response:
Verify that the parameter file contains a parameter and value for the lookup table name. If you are using a mapping variable, verify the variable has a value.