Database Management Systems

TDQM (Teradata Query Management) is the component that enforces query limits based on predefined thresholds for resource usage. Teradata Manager is an administrative tool but does not directly limit queries. BTEQ is a query utility, and QueryMan is a legacy query interface.

In DataStage Oracle OCI stage, the Array Size property controls the number of rows written in each batch to the database. Increasing this value reduces network round trips between DataStage and Oracle by buffering more rows before sending them, which significantly improves write performance for bulk operations. This is a performance tuning technique specifically for write operations, not reads.

Informatica provides transaction control variables for managing session commits. TC_CONTINUE_TRANSACTION keeps the transaction open, TC_COMMIT_BEFORE commits before processing, and TC_ROLLBACK_BEFORE rolls back before processing. TC_STOP_TRANSACTION is not a valid transaction control variable - the correct options for stopping are handled through transaction settings or workflow conditions, not this variable name.

In Informatica repository, Delete moves objects to the recycle bin from where they can be recovered and restored. Purge permanently removes objects from the repository with no recovery option. The distinction is important for version control - deleted objects remain recoverable until purged, while purged objects are completely gone and cannot be reused.

Turbo Integrator uses ODBC (Open Database Connectivity) as the standard data source type for connecting to external databases. ODBC is a widely-accepted standard for database connectivity that provides a consistent interface across different database systems. Option A (ODBO) is a related but different standard for OLAP databases. Option B (TM1) is the application itself, not a data source type. Option D (Text) refers to flat file sources, not databases.

Subject-based addressing in messaging systems routes messages based on a topic or subject line rather than explicit source or destination addresses. This facilitates decoupled communication between data producers and data consumers. Other options are incorrect because they imply direct identification or addressing between specific producers and consumers.

The 'arraysize' property controls how many rows are fetched per network round-trip when reading from Oracle, which significantly impacts performance. Setting a larger array size reduces network overhead but uses more memory. The 'memsize' property is not a standard Oracle Enterprise stage property, 'partitionsize' is not applicable to Oracle reads, and 'transactsize' relates to write operations not reads.

In IBM InfoSphere DataStage, importing metadata from third-party data modeling tools (such as CA Erwin or Rational Data Architect) is achieved via the Meta Integration Model Bridges (MIMB), represented by importing using bridges.

When using the ODBC connector stage as a target, you must define: (1) connection properties to reach the ODBC data source, (2) input link properties to control how data flows into the stage, and (3) column definitions for the input data to map incoming fields. Output link column definition (Option B) is not required for a target stage since data flows in through the input link, not out.

The most accurate method is using Orchestrate Schema Definitions via orchdbutil because it directly queries Oracle's system tables to extract precise column definitions, data types, lengths, and constraints. This native Oracle bridge captures metadata more completely than generic importers. Options A, B, and C use higher-level import mechanisms that may lose precision or require additional manual verification.

The DB2 command used to cancel or stop a running utility is -TERM UTILITY(utility-id), where TERM is short for terminate. KILL is not a valid DB2 command for terminating utilities, and TERM alone without specifying the utility name or ID is syntactically incomplete.

DB2 system catalogs track plan-table dependencies. Both SYSIBM.SYSPLANDEP and SYSIBM.SYSPACKDEP contain this information depending on the DB2 version and configuration, so either query could work depending on your environment.

In DB2, REPAIR, LOAD, and IMAGCOPY are database-level utilities that require special privileges. UPDATE is a standard DML (Data Manipulation Language) operation that operates on table-level data, not a database administration privilege.

Oracle automatically stores a user's objects in their default tablespace when no TABLESPACE clause is specified. This default tablespace is assigned when the user is created. The SYSTEM tablespace is reserved for data dictionary objects, and user objects are not stored there by default.