OPT Messages

Explanation:	The Integration Service could not map the datatype correctly.
User Response:	Contact Informatica Global Customer Support.

OPT_63007 ERROR: Failed to expand configuration parameter [$$PushdownConfig].

Explanation:	The Integration Service could not expand the $$PushdownConfig configuration parameter because it could not locate the parameter file or could not locate the specified parameter within the parameter file.
User Response:	Verify that the parameter file contains the correct path, and a value for the $$PushdownConfig parameter is specified within the file.

OPT_63008 ERROR: Configuration parameter [$$PushdownConfig] contains an invalid value.

Explanation:	The Integration Service could not expand the $$PushdownConfig configuration parameter because the parameter files specifies an invalid value for the $$PushdownConfig parameter.
User Response:	Verify that the parameter file specifies a valid value for the $$PushdownConfig configuration parameter.

OPT_63009 ERROR: Source-side pushdown optimization stops at transformation <transformation name> because of an internal error that occurred while parsing a timestamp. Contact Informatica Global Customer Support.

Explanation:	An internal error occurred while parsing a timestamp.
User Response:	Contact Informatica Global Customer Support.

OPT_63014 Pushdown optimization to source stops at the transformation <transformation name> because the mapping contains too many pipeline branches.

Explanation:	The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 four-way branches. The Integration Service cannot generate SQL to push all the branches of the mapping to the database.
User Response:	None.

OPT_63015 Pushdown optimization to target stops at the transformation <transformation name> because the mapping contains too many pipeline branches.

Explanation:	The mapping contains more than 64 two-way branches, 43 three-way branches, or 32 four-way branches. The Integration Service cannot generate SQL to push all the branches of the mapping to the database.
User Response:	None.

OPT_63021 Pushdown optimization stops at the transformation <transformation name> because it is connected to multiple targets.

Explanation:	You attempted to push a transformation to multiple targets for target-side partial pushdown optimization. The Integration Service cannot generate the SQL to push the transformation to both targets.
User Response:	None.

OPT_63022 Pushdown optimization stops at the transformation <transformation name> because no port depends on values from the upstream transformation <transformation name>.

Explanation:	You created an expression that does not use upstream output port values. The Integration Service cannot generate an SQL statement for an expression that does not use output ports from upstream transformations because it cannot determine the values to use.
User Response:	None.

OPT_63070 Pushdown optimization to the source stops at the transformation <transformation name> because it is a partition point and the partition type is not hash auto-keys or pass-through.

Explanation:	To push transformation logic for a partitioned transformation to the database, the partition type must be hash auto-keys or pass-through. If the partition type is hash auto-keys, the source must be key-range partitioned, and the key ranges cannot gap or overlap.
User Response:	Change the partition type for the transformation to hash auto-keys or pass-through.

OPT_63072 Pushdown optimization to the source stops at the partition point <transformation name> because the source is not key-range partitioned.

Explanation:	The transformation uses a hash auto-keys partition, and the source is not key-range partitioned. When the partition is hash auto-keys, you must also configure the source for key-range partitioning.
User Response:	Configure the source for key-range partitioning.

OPT_63076 Pushdown optimization to the source stops at the partition point <transformation name> because the source has a partition with an end key- range different from the start key range of the next partition.

Explanation:	You configured the source for key range partitioning, but you did not ensure that the end key range for a partition matches the start range for the next partition. The end key range for each partition must equal the start range for the next partition, and it cannot overlap with the next partition.
User Response:	Modify the start or end key-range to ensure that the end key range for the partition equals the start range for the next partition.

OPT_63077 Pushdown optimization to the source stops at the partition point <transformation name> because the source contains a user-defined filter on a per-partition basis.

Explanation:	You added a user-defined distinct filter condition at the Source Qualifier transformation. Two or more partitions use a different filter condition. The Integration Service cannot push transformation logic to the source when you use a distinct user-defined filter.
User Response:	None.

OPT_63078 Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Aggregator transformation is not properly partitioned on the aggregate key.

Explanation:	You configured a group by port for the upstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match.
User Response:	Configure the group by port and partition key to match.

OPT_63079 Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Sorter transformation is not properly partitioned on the distinct sort key.

Explanation:	You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match.
User Response:	Configure the sort key and partition key to match.

OPT_63080 Pushdown optimization to the source stops at the partition point <transformation name> because an upstream Joiner transformation is not properly partitioned on the join key.

Explanation:	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.
User Response:	Configure the join condition and the partition key to match.

OPT_63081 Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Aggregator transformation is not properly partitioned on the aggregate key.

Explanation:	You configured a group by port for the downstream Aggregator transformation that is different from the partition key specified for the key-range partition. The group by port and partition key must match.
User Response:	Configure the group by port and partition key to match.

OPT_63082 Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Sorter transformation is not properly partitioned on the distinct sort key.

Explanation:	You configured a sort key for the upstream Sorter transformation that is different from the partition key specified for the key-range partition. The sort key and partition key must match.
User Response:	Configure the sort key and partition key to match.

OPT_63083 Pushdown optimization to the source stops at the partition point <transformation name> because a downstream Joiner transformation is not properly partitioned on the join key.

Explanation:	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.
User Response:	Configure the join condition and the key-range partition to match.

OPT_63102 Pushdown optimization stops at Source Qualifier transformation <transformation name> because it contains an SQL override, and view creation is not enabled.

Explanation:	You configured a session that contains an SQL override for pushdown optimization, but you did not configure the session to create a view.
User Response:	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_63106 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because SQL override is specified for some but not all partitions.

Explanation:	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.
User Response:	Configure an SQL override for all partitions in the session.

OPT_63107 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains an SQL override with Informatica join syntax.

Explanation:	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.
User Response:	Use source database syntax when you write the SQL override.

OPT_63108 Pushdown optimization stops at the Source Qualifier transformation <transformation name> because it contains a user-defined join with Informatica join syntax.

Explanation:	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.
User Response:	Use source database syntax when you write the user-defined join.

OPT_63120 Pushdown optimization stops at the Aggregator transformation <transformation name> because there is an upstream Aggregator transformation.

Explanation:	The Aggregator transformation is the second Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for more than one Aggregator transformation in a pipeline. This occurs because the SQL generated for two consecutive Aggregator transformations results in a nested Aggregator function, which cannot be processed on the database.
User Response:	None.

OPT_63131 Pushdown optimization stops at the Joiner transformation <transformation name> because an input pipeline contains an Aggregator transformation.

Explanation:	An Aggregator transformation exists in an input pipeline. The database must perform join operations before aggregation operations, so the Integration Service cannot generate an SQL statement for a Joiner transformation that is downstream from an Aggregator transformation.
User Response:	None.

OPT_63133 Pushdown optimization stops at the Joiner transformation <transformation name> because it is configured for an outer join and the master source joins multiple tables.

Explanation:	The master source joins multiple tables. The Integration Service cannot generate SQL to join multiple tables with an outer join.
User Response:	None.

OPT_63147 Pushdown optimization stops at the Lookup transformation <transformation name> because it is downstream from an Aggregator transformation.

Explanation:	The Lookup transformation is downstream from an Aggregator transformation in the pipeline. The Integration Service cannot generate SQL statements for a Lookup transformation downstream from an Aggregator transformation.
User Response:	None.

OPT_63152 Pushdown optimization stops at the Sorter transformation <transformation name> because the distinct key <port name> is not used downstream.

Explanation:	The Integration Service cannot generate SQL for a Sorter transformation configured for a distinct sort when the distinct key is not used downstream.
User Response:	None.

OPT_63157 Pushdown optimization stops at the Union transformation <transformation name> because the sources use different database connections.

Explanation:	The Union transformations joins sources that are from different databases or that use different database connections.
User Response:	If the Union transformation joins sources from the same database, ensure that you specify the same database connection in the session properties.

OPT_63170 ERROR: Pushdown optimization stops at the transformation <transformation name> because it contains an invalid expression.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

OPT_63175 ERROR: Pushdown optimization stops at the transformation <transformation name> because the mapping parameter <mapping parameter name> cannot be expanded.

Explanation:	The transformation contains a mapping parameter that cannot be expanded. The parameter file may be corrupt, the path to the parameter file may be incorrect, or the parameter file name may be incorrect.
User Response:	Modify the parameter file, the path to the parameter file, or the parameter file name.

OPT_63177 Pushdown optimization stops at the transformation <transformation name> because expression <expression name> with < parameter name> parameters cannot be pushed to the database.

Explanation:	The expression uses a parameter that represents a datatype that is unsupported on the database.
User Response:	None.

OPT_63193 Pushdown optimization to target stops at the transformation <transformation name> because the expression <expression name> uses a boolean expression for parameter <parameter name>.

Explanation:	The numeric expression contains a boolean subexpression. Numeric and boolean values are not compatible in SQL. To convert a boolean expression to a numeric expression, the database requires a case statement, which cannot be performed with target-side pushdown optimization.
User Response:	None.

OPT_63205 Error encountered while attempting to partition session at runtime.

Explanation:	The Integration Service could not dynamically partition the session.
User Response:	Review previous messages in the session log to determine the cause.

OPT_63206 Invalid Partition Count <count>.

Explanation:	You set dynamic partitioning based on the number of partitions but the attribute does not contain a valid value.
User Response:	Set the Number of Partitions to the $DynamicPartitionCount session parameter or enter a number greater than 1.

OPT_63207 Partition Count is 1. Dynamic Partitioning has been disabled.

Explanation:	The Number of Partitions session attribute is 1. The session runs in one partition.
User Response:	Set the number of partitions to a number greater than 1, or change the method of partitioning.

OPT_63213 Error retrieving database partition information <database name>.

Explanation:	When you use database partitioning, the Integration Service generates SQL queries to access data in each database partition. The Integration Service queries of the database system catalog failed.
User Response:	Review previous messages to determine why the database is inaccessible.

OPT_63214 Error creating partitions.

Explanation:	The Integration Service is using database partitioning, but it cannot retrieve partition IDs or partition names.
User Response:	Review previous messages to determine why the partitions are inaccessible.

OPT_63215 Error partitioning session attributes.

Explanation:	The Integration Service could not create partition-level attributes for dynamic partitions.
User Response:	Verify that you enter valid values for the session parameters that the Integration Service uses to create dynamic partition attributes. Partition-level attributes include source, target, and reject file names and locations.

OPT_63216 Error partitioning key range for transformation <transformation name>.

Explanation:	You are using key range partitioning and the Integration Service cannot partition the key ranges you defined for a transformation.
User Response:	Verify the key ranges do not have gaps or overlapping ranges.

OPT_63217 Transformation <transformation name> uses a key range data type that cannot be partitioned.

Explanation:	The key range partition key must be a number or a date for a dynamic partitioned session.
User Response:	Disable dynamic partitioning or change the key type to a number or date.

OPT_63218 Key range not closed.

Explanation:	You cannot enable dynamic partitioning for a transformation that uses an open range of partition key numbers.
User Response:	Disable dynamic partitioning or change the key range to a closed range of numbers.

OPT_63219 Transformation <transformation> uses pass-through partitioning which is disallowed by dynamic partitioning.

Explanation:	You cannot enable dynamic partitioning for a relational source using a pass-through partition type. The session runs in one partition by default.
User Response:	Disable dynamic partitioning or use a database partition type.

OPT_63220 Transformation <transformation name> specifies user defined SQL that will not be partitioned.

Explanation:	You enabled dynamic partitioning for a session with a transformation that has user-defined SQL. The session runs in one partition by default.
User Response:	Disable dynamic partitioning or remove the user-defined SQL.

OPT_63221 The Source Qualifier transformation <transformation name> will not be partitioned because one or more transformations upstream from the Source Qualifier transformation cannot be partitioned.

Explanation:	The number of partitions must be consistent across a pipeline in a mapping. If the Integration Service cannot dynamically partition a transformation in a pipeline, it does not partition the pipeline. The session runs in one partition by default.
User Response:	Disable dynamic partitioning.

OPT_63222 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK readers is not supported.

Explanation:	You enabled dynamic partitioning in a session containing an SDK source. You cannot enable dynamic partitioning for SDK and PowerExchange sources and targets. The session runs in one partition by default.
User Response:	Disable dynamic partitioning.

OPT_63223 Transformation <transformation name> will not be partitioned because dynamic partitioning of SDK writers is not supported.

Explanation:	You enabled dynamic partitioning in a session containing an SDK target. You cannot enable dynamic partitioning for SDK and PowerExchange sources and targets. The session runs in one partition by default.
User Response:	Disable dynamic partitioning.

OPT_63224 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML readers is not supported.

Explanation:	You enabled dynamic partitioning for a pipeline that contains an XML source transformation. The session runs in one partition by default.
User Response:	Disable dynamic partitioning.

OPT_63225 Transformation <transformation name> will not be partitioned because dynamic partitioning of XML writers is not supported.

Explanation:	You enabled dynamic partitioning for a pipeline that contains an XML target transformation. The session runs in one partition by default.
User Response:	Disable dynamic partitioning.

OPT_63226 Transformation <transformation name> will not be partitioned because partitionable attribute <attribute name> has a user specified value.

Explanation:	The Integration Service does not partition a transformation when you enter a value for a partition-level attribute.
User Response:	To use dynamic partitioning with a Custom transformation, clear the referenced attribute. For other transformations, set the cache directory to the default, $PMCacheDir.

OPT_63227 Transformation <transformation name> is not partitionable.

Explanation:	You enabled dynamic partitioning for a session that contains a transformation that is not partitionable. The session runs in one partition by default.
User Response:	Disable dynamic partitioning or change the transformation that is not partitionable.

OPT_63229 Unable to determine count of partitions for Dynamic Partitioning because an error was encountered while expanding parameter <parameter name>.

Explanation:	The Integration Service could not determine the number of partitions to create.
User Response:	Verify that the $DynamicPartitionCount session parameter contains a number greater than 1.

OPT_63234 Dynamic partitioning failed to detect the number of CPUs because of the following system error: <error>.

Explanation:	A fatal error occurred. If the Integration Service runs on a grid, the fatal error occurred on the node which ran the preparer DTM process.
User Response:	Review the session log for related messages, or contact Informatica Global Customer Support.

OPT_63282 Source-side pushdown optimization stops at partition point <partition name>.

Explanation:	The Integration Service is unable to determine why pushdown optimization stops at this partition point.
User Response:	Contact Informatica Global Customer Support.