Troubleshooting Informatica Error Messages and Resolution – Part 235

SQLServerF1

OPT_63083Pushdown optimization to the source stops at the repartition point <transformation name> because a downstream Joiner transformation is not properly partitioned on the join key.
Cause:You configured a join condition for the upstream Joiner transformation that is different from the partition key specified for the key-range partition. The join condition and partition key must match.
Action:Configure the join condition and the key-range partition to match.

OPT_63102Pushdown optimization stops at Source Qualifier transformation <transformation name> because it contains an SQL override, and view creation is not enabled.
Cause:You configured a session that contains an SQL override for pushdown optimization, but you did not configure the session to create a view.
Action:When you configure the session containing an SQL override for pushdown optimization, ensure that you configure the session to create a view. You configure this setting on the Properties tab of the session properties.
OPT_63106Pushdown optimization stops at the Source Qualifier transformation <transformation name> because SQL override is specified for some but not all partitions.
Cause:When you configure a session that contains an SQL override for pushdown optimization, you must configure the SQL override for all partitions in the session.
Action:Configure an SQL override for all partitions in the session.

OPT_63107Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains an SQL override with Informatica join syntax.
Cause:The SQL override contains Informatica join syntax. Because the Integration Service creates a view to process the SQL override, the syntax must be compatible with the source database.
Action:Use source database syntax when you write the SQL override.
OPT_63108Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains a user-defined join with Informatica join syntax.
Cause:The user-defined join contains Informatica join syntax. Because the Integration Service pushes the transformation logic for the join to the source database, the syntax must be compatible with the source database.
Action:Use source database syntax when you write the user-defined join.

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 *