Troubleshooting Informatica Error Messages and Resolution – Part 98

SQLServerF1

CMN_1921External loader error. Control File will be generated for First Partition Only.
Cause:You tried to override the control file for a partition other than the first partition in the Teradata target definition. The Integration Service only uses the control file specified in the first partition when you create multiple partitions in a session that uses Multiload or FastLoad to load to Teradata.
Action:Verify the control file in the first partition of the session uses the attributes you want for the session.

CMN_1922External loader error. Update is not valid for target instance [target definition name] since no primary key(s) is mapped to the target.
Cause:The Teradata target table does not have a primary key, so the Integration Service cannot generate a control file and update the target.
Action:Define a primary key on the target table and run the session again.
CMN_1923External loader error. Update is not valid for target instance [target definition name] since no non-key field(s) is mapped to the target.
Cause:The primary key column in the Teradata target definition is not connected to an upstream transformation in the mapping. The Integration Service cannot generate a control file and cannot update the target.
Action:Connect the primary key column in the Teradata target definition to an upstream port in the mapping. Run the session again.
CMN_1924External loader error. Delete is not valid for target instance [target definition name] since no primary key(s) is mapped to the target.
Same as CMN_1923.

CMN_1925The server does not support delimited files with the Teradata external loaders.
Cause:The session uses a delimited flat file target to load data to the Teradata target using FastLoad, Multiload, or TPump.
Action:Edit the session properties and configure the Teradata target to use a fixed-width flat file.
CMN_1926Error: Teradata external loader requires a primary key on table [target table name] when using load mode [load mode].
Cause:The Teradata external loader connection uses the specified load mode, such as update or upsert, but the target table has no primary key. The target table must have a primary key for the Integration Service to use this load mode.
Action:Define a primary key on the target table and run the session again.

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.

Thanks,
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 *