Database Management Systems

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.

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.

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.

The correct order for creating an RMAN recovery catalog is: 5) Create tablespace first, 4) Create user/schema owner, 1) Grant necessary privileges (CONNECT, RESOURCE, RECOVERY_CATALOG_OWNER), 3) Create the catalog using RMAN, 6) Connect to target database with SYSDBA, 2) Register target database in catalog. This sequence ensures prerequisites are met before dependent steps - the tablespace must exist before creating the user, the user must exist before granting privileges, and privileges must be granted before creating the catalog.

When a database is switched to ARCHIVELOG mode using ALTER DATABASE ARCHIVELOG, this mode change is recorded in the control file. The control file stores critical database information including the database name, checkpoint information, and archiving mode. SPFILE (option A) stores initialization parameters. Archive logs (option B) are the output of archiving, not where the mode is stored. The System tablespace (option D) stores data dictionary objects, not database state information.

Use the UNIFORM clause for allocating new extents and set a very high extent size.

When a replication site contains subsets of another site's data, this is called snapshot replication (also known as materialized view replication). A snapshot site stores and maintains copies of data from a master site, allowing for read-only access and periodic refresh. This is different from master-site replication (option A) which maintains full copies. Option C is incorrect because the question specifically describes a subset scenario, which characterizes snapshot sites, not a combination of both types.

When the Data Length Semantics property is set to BYTE, Oracle measures column length in bytes rather than characters. For multi-byte character sets (like UTF-8 or AL32UTF8), a single character might require multiple bytes. If Maximum Length is set based on character count but BYTE semantics are used, the actual byte capacity may be insufficient for the expected number of characters, requiring manual adjustment. Option A is false because display issues depend on item width, not Maximum Length. Option B is false because Initial Value must respect validation range constraints. Option C is false because Required property at the form level is independent of database constraints.

The Export/Import direct-path feature extracts data faster than conventional-path export because it bypasses the SQL evaluation layer and reads data directly from disk blocks, formatting it as Oracle export format. This reduces CPU overhead and processing time. Option B is incorrect because Export cannot directly export tablespaces or data files (those are physical storage structures, not logical database objects). Option C is incorrect because FULL export mode only exports objects in schemas that the user has privileges to access, not all objects regardless of schema. Option D is incorrect because transportable tablespaces (which copy data files) are much faster than export/import for moving large volumes of table data.

Oracle instance startup progresses through three main states: NOMOUNT (reads parameter file and starts instance), MOUNT (associates instance with control file and database), and OPEN (makes database available for users). Option D lists all three valid stages. Options A, B, and C include invalid or non-existent commands like STARTUP CLOSE, START MOUNTALL, STARTUP EXIT, and STARTUP START.

Online control file backups require the database to be in ARCHIVELOG mode, which enables continuous archiving of redo logs. In NOARCHIVELOG mode, the database must be shut down for consistent backups. FAILOVER and FASTBACK are not valid database modes. ALTER DATABASE with backup options requires ARCHIVELOG mode for online operation.

Dynamic data replication to remote databases is achieved through database triggers, which can automatically propagate DML changes to remote tables. Stored procedures and database procedures must be explicitly invoked. Cursors are query result iterators, not replication mechanisms. Triggers provide the automatic, event-driven replication needed.

In Multithreaded Server (MTS) architecture, V$QUEUE displays contention statistics for dispatcher queues, showing if requests are waiting for server processes. V$CIRCUIT shows virtual circuit information. V$SESSION shows session information but not server process contention. DBA_USERS lists database users, not server contention. V$QUEUE is specifically designed to monitor MTS dispatcher queue performance.

The data dictionary cache is part of the System Global Area (SGA) that stores data dictionary information including user privileges, object definitions, and security attributes. When a server process needs to validate user privileges, it queries this cached information rather than accessing the physical data dictionary tables on disk, which significantly improves performance. The buffer cache stores database blocks, the library cache holds SQL and PL/SQL code, and the redo log buffer stores redo entries - none of these contain privilege validation data.