Whitespace Considerations
Sun Data Integrator handles whitespace differently depending on the execution strategy. When joining a flat file table and an Oracle table where the comparison column in the Oracle table contains whitespace, refer to the table below.
Table 1–1 Execution Strategies for Flat File and Oracle Table Joins|
Strategy Specified |
Description |
|---|---|
|
Best Fit |
Uses the staging execution strategy since the source tables are from different databases. The results will be the same as if staging was selected. |
|
Staging |
Data Integrator extracts source tables from source databases and stages the data in temporary tables in the target database. By default, whitespace is trimmed. |
|
Pipeline |
Data Integrator uses an internal database engine instead of temporary tables, accessing data directly from the source tables rather than extracting it to temporary tables. To avoid whitespace causing failure in the join condition, add LTRIM/RTRIM operators to the Oracle table column. The result will be the same as Staging/Best Fit. Note – In future this feature will be made obsolete |
- © 2010, Oracle Corporation and/or its affiliates