Review the following usage considerations if you use Lookup transformations with PowerExchange sources or targets:
The Lookup transformation import process uses ODBC for nonrelational files and relational tables.
To use PWXPC to import definitions for nonrelational files or relational tables, first import the definitions in the
Import from PowerExchange
dialog box in either the Source Analyzer or Target Designer before configuring the lookup in the mapping.
You can use PWXPC connections for lookups. The type of connection depends on the following critieria:
For lookups that involve relational tables, use the appropriate relational connection for the database type, such as PWX DB2zOS, PWX DB2i5OS, PWX DB2LUW, PWX Microsoft SQL Server, or PWX Oracle.
For lookups that involve nonrelational files, select the PWX NRDB Lookup connection.
For NRDB lookups, the Lookup transformation property
Lookup Policy on Multiple Match
has no effect. The Lookup transformation always returns the first row that matches the lookup condition.
For nonactive DB2 lookups, the Lookup transformation appends FETCH FIRST 2 ROWS ONLY to the SQL that it sends to PWXPC. In this way, DB2 optimizes its processing and returns a result set with a maximum of two rows. Nonactive DB2 lookups are lookups with a
Lookup Policy on Multiple Match
value of
Report Error
,
Use First Value
,
Use Last Value
, or
Use Any Value
.
To use Lookup transformations with the
Resume from last checkpoint
recovery strategy, you must select either the
Lookup Source is Static
or
Lookup Cache Persistent
option for the transformation. If you do not select one of these options, you will not be able to validate the CDC session in Workflow Manager.
To use Lookup transformations with IMS databases, carefully consider the fields that are used to perform the search of the IMS database. Concatenated keys (CCK) fields achieve the best performance with the least impact on the IMS database.
To use Lookup transformations for targets in a CDC mapping, use special custom properties to ensure the change data stream is accessible across pipelines.
When a PowerCenter workflow runs an IDMS netport job in Central Version (CV) mode, such as when performing a lookup on an IDMS data source, and delays occur in processing the source data or performing other lookups, the netport job might return IDMS error code 0069. This error occurs when no activity has occurred in the netport job for the length of the CV internal timeout and the bind run unit has expired.
To disable IDMS timeouts, specify the following IDMS System Generation parameters: