Oracle Practice Test - 9

To enable users to add values to a list item, you need a combo box style (which allows input) and the Add_List_Element built-in. The When-List-Activated trigger fires when the list is accessed, making it the right place to add new items. Option A correctly specifies both the combo box style and the appropriate trigger.

FAST_START_MTTR_TARGET controls the Mean Time To Recover (MTTR) and indirectly affects checkpoint frequency. A lower MTTR target requires more frequent checkpoints, which speeds up the roll forward phase of recovery by reducing redo to apply. Other options either don't control checkpoint frequency (LOG_CHECKPOINT_* parameters control timing directly) or aren't primarily about MTTR.

LOG_ARCHIVE_MIN_SUCCEED_DEST=2 means archival must succeed to at least 2 destinations before redo logs can be overwritten. The destinations include 1 local mandatory + 1 local optional = 2 local destinations. The remote mandatory is the third destination but isn't counted for the minimum since we already have 2 local ones. Option B correctly identifies that archival to both local destinations is sufficient.

STATSPACK is the correct tool for comparing snapshots over time. It captures database performance statistics at intervals and provides reports to compare different snapshots. LOCK MANAGER handles locking, ORACLE EXPERT is for tuning recommendations, and UTLBSTAT/UTLESTAT are older tools replaced by STATSPACK.

Coalescing a tablespace combines adjacent free space fragments into larger contiguous extents. When importing a table that requires a single contiguous area larger than any existing free space, coalescing can create the needed space. Other options (cascade, constraint, primary key) are import-related parameters or constraints that don't address space consolidation.

POPULATE_GROUP

DBMS_SCHEDULER.PURGE_LOG() purges both window logs and job logs from the scheduler. It doesn't selectively purge only one type or only yesterday's logs. The command cleans up all accumulated logs to manage disk space.

The instance recovery time

With control files intact, STARTUP NOMOUNT is sufficient (control files exist so MOUNT isn't needed). The sequence is: NOMOUNT → RESTORE → RECOVER → OPEN. RESETLOGS is only required after incomplete recovery or missing logs, which isn't stated here. Option A shows the correct sequence without RESETLOGS.

SQL tuning uses a bottom-up approach by examining individual SQL statements and their execution plans to identify and fix bottlenecks. Proactive tuning is top-down (system-wide), reactive tuning responds to problems, and 'active tuning' isn't a standard term. SQL tuning is methodical and statement-focused.

CALL_FORM creates a modal relationship - the called form must be closed before returning to the caller. OPEN_FORM is modeless. The chain shows FormB called FormE with CALL_FORM, so FormE is currently modal over FormB. FormF can be invoked from FormE using CALL_FORM because FormE is active and can initiate modal calls. Other options are incorrect because CALL_FORM from Forms A, C, or D would block their respective parents.

OC4J (Oracle Containers for J2EE) starts in a separate window when running forms from Forms Builder. This window must remain open - closing it terminates the OC4J instance, which would interrupt form execution. The window cannot be closed without affecting the running instance.

When a willing-to-wait latch request is granted on the first attempt (no spin/wait), the GETS statistic is incremented. SLEEPS increments after spinning, MISSES increments when not immediately available, and IMMEDIATE_GETS is for no-wait mode. Immediate success on first attempt directly increments GETS.

In Oracle Shared Server architecture, after the listener provides the dispatcher address, the user process connects directly to that dispatcher. The dispatcher then manages multiple client connections efficiently by placing requests in request queues and retrieving responses from response queues.

DBA_FREE_SPACE is the data dictionary view that displays information about free extents available in tablespaces. Each row represents one free extent in a tablespace, showing the tablespace name, file ID, block ID, and bytes/blocks free.

ROUND(45.953, -1) rounds to 50 because the negative second parameter means round to tens place (45.953 becomes 50). TRUNC(45.936, 2) truncates to 45.93 by keeping only 2 decimal places (no rounding, just truncation).

FAST_START_MTTR_TARGET specifies the mean time to recover (MTTR) in seconds, which directly influences checkpoint frequency. Oracle automatically adjusts checkpoint intervals to meet the specified recovery time goal, affecting the roll forward phase during crash recovery.

Tuning at design time is most cost-effective and efficient. Design-time tuning prevents performance issues before code is written, avoids expensive rework later, and establishes proper architecture, indexing strategies, and access patterns from the start.

Oracle supports BEFORE, AFTER, and INSTEAD OF triggers. DURING is not a valid trigger timing in Oracle. Triggers fire either before or after a DML operation (or instead of, for views), but not during the operation itself.

A read-only tablespace should be backed up immediately after being placed in read-only mode. Once read-only, the tablespace cannot change, so this single backup suffices until the tablespace returns to read-write mode. Backing up after the mode change ensures consistency.

POPULATE_GROUP executes the query associated with a query record group and populates it with data. This built-in is specifically designed for record groups created at design time or runtime that need to be populated from their defined query.

V$CONTROLFILE is the dynamic performance view that contains information about control files, including their names and status. This view provides a list of all control files currently in use by the database instance.

When CONTROLFILE AUTOBACKUP is ON, RMAN automatically creates a control file autobackup after certain operations, regardless of whether a control file was already included in the backup set. This ensures redundancy and recoverability even if recent backups exist.