Database Management Systems

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 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.

The question asks what blocks pointing to data blocks (single indirect, double indirect) are collectively known as. While these are technically part of the inode's indirect pointer structure, 'Metadata' (option B) is the best available answer among the options, though it's not entirely precise - they're more accurately called indirect pointer blocks or simply indirect blocks.

Materialized views store actual data physically, unlike regular views which are just stored queries. When base tables are dropped, the materialized view's data remains in storage. The view may become invalid or unusable, but the data is not automatically deleted. The statement is false.

ORA-12154 indicates the TNS listener cannot resolve the service name. The solution is to verify and correct the tnsnames.ora file parameters. Once corrected and saved, reconnecting is sufficient - restarting the client machine or forms server is unnecessary and excessive.

Conformed dimensions are dimensions that have the same meaning and content across multiple data marts. They enable integration of disparate data marts into a coherent data warehouse by ensuring consistent dimension keys and definitions. This allows drilling across data marts without data integrity issues.

Compound Growth Factor (CGF) measures how data volume grows over time in a data warehouse environment. As historical data accumulates and new sources are added, the data can explode exponentially. CGF quantifies this growth phenomenon, particularly relevant for storage capacity planning and performance management.