Database Management Systems

EXPLAIN PLAN is the SQL command used to analyze and display the execution path that Oracle's optimizer will use for a SQL statement. 'Exp' and 'Imp' are import/export utilities, and 'vi' is a text editor - none analyze SQL access paths.

Frequent COMMITs release undo segments (which store before-images for rollback), release row and table locks, and free other resources held by the transaction. This improves concurrency and reduces resource contention. The statement is true.

ADDM stands for Automated Database Diagnostic Monitor, an Oracle feature that analyzes database performance and provides recommendations. It identifies bottlenecks, inefficient SQL, and resource issues automatically.

V$SQLSTATS is the Oracle view that provides resource utilization metrics for SQL queries, including CPU time, buffer gets, and disk reads. V$SQL provides query text and execution statistics but not detailed resource metrics, while the other two views don't exist.

Automatic Workload Repository (AWR) was introduced in Oracle 10g as part of the Automatic Workload Repository infrastructure. It provides statistics and performance metrics for database optimization. AWR did not exist in earlier versions like 8i or 9i.

In Oracle database schema objects, indexes, tables, triggers, and packages all belong to a specific schema. Public synonyms, however, are database-wide objects that are not owned by any particular schema - they are created with the PUBLIC keyword and are accessible to all users. This makes Public synonyms the correct answer as 'not a schema object'.

In Oracle data dictionary, USER_TABLES is the correct view name to retrieve information about tables owned by the current user. USER_TABS is not a valid Oracle dictionary view. The answer is A only. Other valid views include ALL_TABLES (tables accessible to user) and DBA_TABLES (all tables in database), but the question specifically asks about a given schema.

In traditional Oracle rollback segment architecture (pre-undo tablespace), a rollback segment must allocate a minimum of TWO extents before it can be used for transaction rollback information. This is a fundamental requirement for rollback segment initialization. The first extent contains the segment header, and at least one additional extent is needed for transaction data.

The Oracle data dictionary is a collection of read-only tables and views that store metadata about the database structure. It contains information about all physical and logical structures including tables, tablespaces, datafiles, users, privileges, and other database objects. This metadata is essential for the database to function and manage itself efficiently.

Oracle Enterprise Manager Grid Control is a comprehensive management tool that monitors and manages the entire IT infrastructure. It can manage server machines (hardware/OS), Oracle application servers, Oracle databases, and even third-party products through various management packs and connectors.

Oracle database supports multiple embedded languages. Java can run within the database via Java Virtual Machine (JVM). SQL and PL/SQL are native languages. While C can interact through OCI (Oracle Call Interface), option B about 'any other language linked to OCI' is misleading - not all OCI-linked languages can run INSIDE the database, only Java, SQL, and PL/SQL are truly embedded.

The Grid abstraction layer in Oracle is designed to hide complexity from developers and DBAs. Application developers write SQL and PL/SQL code without needing to understand the underlying Grid infrastructure, resource management, or clustering details. The Grid manages resources transparently, allowing developers to focus on business logic rather than infrastructure implementation.

An SOA registry serves as a central metadata repository for services - storing information about service locations, interfaces, policies, and dependencies. A repository stores actual service artifacts, while a registry stores metadata and references.

The Sorter transformation can be configured with the 'Distinct' output option to treat output rows as distinct, removing duplicates during the sort operation. When enabled, the Sorter uses the sort key columns to identify and eliminate duplicate rows, passing only unique rows to downstream transformations. This is more efficient than using an Aggregator or Expression transformation after sorting to remove duplicates. The other options are incorrect: duplicates are not rejected, they can be eliminated; there's no case-based duplicate sorting behavior.