Database Management Systems

Smart identification is the specific mechanism in HP/Micro Focus UFT (QTP) used to identify test objects during a run session when the learned properties do not uniquely identify the object. Recovery scenarios are for handling unexpected events, not standard object identification.

Oracle Warehouse Builder (OWB) is an ETL tool for data warehousing. It allows designing and creating target database schemas, designing and creating OLAP environments, and defining and creating data flows between sources and targets. OWB is a comprehensive data integration and warehousing solution.

Repositories in data management or metadata repositories (like Informatica or OBI) store metadata definitions. Metadata describes data models, mappings, schemas, and configurations. While objects, mappings, and tables are defined, the repository fundamentally stores their metadata definitions rather than the actual raw data or transient mappings.

In Oracle Warehouse Builder (OWB), OLAP (Online Analytical Processing) constructs are represented by dimensional objects. OWB allows developers to design Facts and Dimensions, which form the star or snowflake schemas crucial for OLAP cubes.

In Oracle Warehouse Builder, metadata can be created through importing source/target definitions, importing stored code and design definitions, and creating API definitions. Creating mappings is primarily about designing data transformation logic rather than creating metadata structures, making it the exception in this context.

Warehouse Builder captures file structure into its metadata repository through file sampling. By analyzing sample data from the file, OWB can automatically detect and infer the file structure, delimiters, and data types, which is more efficient than manual definition or simple importing.

Technical users require full read/write access to the OWB metadata repository to perform development, deployment, and maintenance tasks. Read-only access would prevent essential operations, while no access would make technical work impossible.

The Runtime Schema in OWB contains audit tables and packages that track execution history, performance metrics, and runtime information. Runtime Audit Viewer is used to display this data, but the actual tables and packages reside in the Runtime Schema.

OWB includes three main Data Quality components: Match, Merge, and Purge. These components help clean, standardize, and deduplicate data during ETL processes. The number 3 correctly represents the core data quality functionality.

Oracle 9i integrated relational and OLAP structures within the same database kernel, allowing seamless interoperability. This unified approach eliminated the need for separate OLAP engines and enabled efficient mixed workloads.

A physical map in mainframe terminology refers to the Load Module - the actual executable code that gets loaded into memory when the map is used. This is distinct from the logical map or copybook which defines the data structure.

In CICS, a HANDLE CONDITION command establishes an error handling routine that remains active for the duration of the program. The only way to deactivate or modify it before program termination is to issue another HANDLE CONDITION command, which either replaces or augments the existing condition handler.

In Genesys configuration systems, database queries and definitions are typically stored in XML configuration files. The 'cabinets.xml' file is a standard Genesys configuration file that contains database query definitions and connection specifications. The other files listed handle different aspects (connection pooling, service properties, working documents).

USER_OBJECTS is the correct Oracle system view that shows all objects owned by the current user, including views and their status (VALID or INVALID). USER_VIEWS contains view text/definitions but not status. USER_TAB_COLUMNS describes column information, and USER_TABLES only lists tables.