ETL Tools Quiz: Informatica & DataStage

In PRPC, the 'group_class' property identifies the type or kind of group (e.g., access groups, work groups). This is a standard system property used for group classification. Option A ('class') is generic and not specific to groups.

In Documentum's r_object_id format, the first 2 hexadecimal characters represent the object type/format (e.g., '09' for dm_document, '0b' for dm_folder). The remaining characters include repository identifier and unique ID. This hex prefix helps identify the object type quickly without querying the type table.

In DataStage, jobs in a Protected project cannot be compiled. Protected projects are read-only by design to prevent unauthorized changes. You must check out the job or have appropriate permissions to compile.

A purged log has been permanently deleted from DataStage's repository and cannot be retrieved through standard interfaces like DS Director, Administrator, or Manager. Purge is irreversible. Once logs are purged, they are gone.

Pipeline partitioning in DataStage operates within a single process (in-process). It's an optimization technique where multiple partitions are processed sequentially within one process to minimize overhead. Inter-process and sequence process are not the correct technical terms for pipeline parallelism.

The DS_AUDIT table in the DataStage repository stores audit trail information about job modifications and other metadata changes. DS_JOBDETAILS stores static job definitions, not modification history. The correct query filters by INSTANCE (job name).

APT_RECORD_COUNTS is the environment variable that enables reporting of record counts per partition, which helps identify data skew. APT_PM_PLAYER_TIMING reports player timing statistics. APT_SKEW_DATA is not a valid environment variable.

Parallelism in DataStage can be tuned through the configuration file (node pools, resource allocation), by running specific stages sequentially on selected nodes, and by changing partition algorithms/modes. All three are valid tuning knobs.

You can call a DataStage Routine in a Sequence job using either the Routine Activity (direct call) or the User Variable activity (by setting a variable to the routine's return value). Both methods work. Routine Activity is more explicit.

Sequence jobs can call other sequence jobs through the Job Activity stage. This nesting allows hierarchical job orchestration and is a common design pattern. There's no restriction on nested sequences.

Invocation ID is a feature specifically for Multiple Instance jobs, allowing each instance to be uniquely identified. Regular parallel jobs don't use Invocation IDs. Shared containers don't enable Invocation ID on their own.

SOA stands for Service Oriented Architecture, which is a software design pattern where services are provided to other components through network communication. Informatica follows SOA principles where data integration services are loosely coupled, reusable, and can be accessed independently over the network.

Target load plan in Informatica defines the order in which multiple target tables are populated within a single mapping. The constraint exists because you need enough source qualifiers (which represent data sources) to drive the population of each target table in the specified sequence. If you have more targets than source qualifiers, the mapping cannot execute properly.

When you import a source table in Informatica, it creates a static definition of that table structure at the time of import. Changes made later in the actual database are not automatically reflected in the imported source definition or mappings that use it. You must manually re-import or synchronize the source definition to pick up database changes.

Connected lookups participate in the data flow and can return multiple port values through a single lookup call, while unconnected lookups are called from expressions using :LKP syntax and return only one value. Unconnected lookups generally perform better because they're only executed when needed (cached results possible) and don't require continuous connection to the lookup source during data flow processing.

In Informatica PowerCenter, session properties can be configured to create a new log file each time the session runs. This is controlled by the 'Session Log File' options where you can append a timestamp or create separate logs for each run, preventing log files from being overwritten.

In a sequential batch in Informatica, sessions run one after another in a defined sequence. Each session waits for the previous session to complete before starting, which is useful when there are dependencies between sessions.