Oracle Warehouse Builder and Informatica PowerCenter Quiz

In Informatica PowerCenter, indexes and tables can be created or dropped at pre-session or post-session SQL commands at three levels: Source qualifier (before reading from source), Target (before writing to target), and Session (pre/post-session SQL). Workflow level doesn't have this SQL capability.

A master or normal outer join typically involves fewer matching complexities and smaller result sets compared to full outer joins or complex multi-table detail outer joins. Consequently, query optimizers process them more efficiently.

The Integration Service does NOT match null values in lookup transformations by default - null values do not match other null values unless specifically configured. The statement is false.

In router transformation, you CAN connect multiple output groups to a single target, and you can connect a single input group to multiple transformations. The statement is true.

When you specify sorted input for an aggregator transformation but don't actually sort the data correctly, the Integration Service fails the session because it expects pre-sorted data to optimize aggregation.

In a sequence generator, the sequence starts from the CURRENT value, not the start value. The start value is only used if the current value is null. So with current=11, the sequence starts from 11.

Only CONNECTED lookup transformations support user-defined default values. Unconnected lookups return a default value only when no match is found, but don't support the user-defined default value feature in the same way.

Reusable transformations CANNOT be converted to non-reusable. Once you create a reusable transformation, it remains reusable permanently. This is a one-way designation in Informatica.

When you don't group values in an aggregator transformation, the Integration Service returns ONE row for all input - effectively aggregating everything into a single output row.

With cycle checked, the sequence wraps around when it hits the end value. Starting from current=15, it generates: 15 (current), 20 (15+5), then cycles to 10 (start), then 15 (10+5), then 20 (15+5).

When the lookup table doesn't change between sessions, use PERSISTENT lookup cache. The cache file is saved to disk and reused across sessions, improving performance by avoiding repeated cache builds.

The filter condition in filter transformation is NOT case sensitive - it treats uppercase and lowercase letters as equivalent when evaluating string conditions.

Warehouse Builder supports multiple CASE tools as source metadata suppliers, including all the versions listed: Sybase Power Designer 7.0, CA Erwin 3.0 to 3.5.2, and CA AllFusion ERwin Data Modeler 4.0 SP1 to 4.1.

In Oracle Warehouse Builder, a single Runtime Repository Schema can manage and serve multiple Target schemas. This design allows one repository to track metadata and execution history for multiple data warehouse targets. The one-many cardinality means one repository instance corresponds to many target schemas.

Oracle Warehouse Builder supports heterogeneous data sources for ETL operations. This includes Oracle databases (native support), flat files (CSV, delimited, fixed-length), and enterprise systems like SAP R/3 through specific connectors. This multi-source capability is a key feature for enterprise data integration.

Oracle Warehouse Builder (OWB) is capable of generating SQL and PL/SQL for Oracle databases, as well as ABAP code for extracting data from SAP systems. Since it can generate all these languages depending on the target and source systems, 'All of the Above' is the correct answer.

OWB integrates with Oracle's parallel DML capabilities to significantly boost data loading performance. By enabling parallel inserts, updates, and deletes, large-scale data transformations can process multiple data partitions simultaneously. This feature is essential for high-performance data warehouse operations.