Database Management Systems

Creating an Oracle database requires SYSDBA privilege, which is the highest administrative privilege. DBA is a role that grants database administration permissions but does NOT include database creation authority. SYSOPER provides startup/shutdown and basic operations but cannot create databases. RESOURCE is a schema-level role for object creation with no database creation rights.

The control file contains the database's physical structure metadata including all data file names and locations. When you execute ALTER DATABASE RENAME FILE, Oracle automatically updates the control file to reflect the new path. Alert log entries are chronological records, parameter files are manual configs, and Registry stores Oracle software metadata - none auto-update from rename operations.

The server parameter file (SPFILE) is a binary file maintained by the Oracle server, providing persistent storage and automatic synchronization of initialization parameters. While ALTER SYSTEM can update both memory and SPFILE, and changes persist across restarts, option A captures the core advantage - Oracle actively manages the SPFILE, preventing human edit errors and ensuring consistency.

Index segments store sorted copies of indexed columns, allowing Oracle to locate rows without scanning entire tables. This dramatically improves query performance, especially for large tables with selective WHERE clauses. Tables store actual data, temporary segments hold intermediate query results, and bootstrap segments contain internal metadata - none exist primarily for query performance enhancement.

The DELAY attribute in LOG_ARCHIVE_DEST_n parameter on the PRIMARY database causes archived logs to be held for the specified minutes before being applied on the standby. Setting 'SERVICE=PRODS DELAY 20' on PROD ensures PRODS waits 20 minutes before applying shipped logs. This prevents corrupted or erroneous data from being immediately propagated to the standby, providing a recovery window.

After creating the recovery catalog tablespace, user, schema, and granting privileges, then creating the catalog with RMAN, the mandatory next step is registering the target database in the catalog. Option A (setting incarnation) happens later if needed. Option B (synchronizing) occurs during registration and subsequent updates. Option D (resetting incarnation) is only required for advanced recovery scenarios like flashback or point-in-time recovery to a different incarnation, not during initial setup.

When a replication site pulls changes from another site, it's called snapshot replication. The snapshot site requests and pulls data refreshes from the master site. Master sites push changes, snapshot sites pull them.

Cluster tables allow rows from multiple tables to be stored in the same data block based on a cluster key. This improves join performance for frequently joined tables. Partitioned tables split a single table, unclustered is the default, and index-organized tables store data within the index structure.

A hot backup is taken while the database is online and running, allowing users to continue working during backup. This contrasts with cold backup, which requires shutting down the database. The key characteristic is that the database remains operational.

I/O slaves are specialized processes that only perform write operations to data files. DBWn (Database Writer) processes perform both data gathering (identifying dirty buffers) and writing them to disk. The synchronous/asynchronous I/O distinction is incorrect - both can work with either type.

OSDBA is the operating system group that grants SYSDBA privileges when connecting to an Oracle database. Members of this group can perform database administration tasks. The other options (9iDBA, OSADM, OSOPER) are not valid Oracle operating system groups for SYSDBA access.

After configuring connection parameters (service name, protocol, host, port), the Oracle Net Configuration Assistant's logical next step is testing whether the connection works. This validates the configuration before completing. The listener and net service name would have been configured earlier in the process.

Direct-path export bypasses the SQL statement processing layer, writing data directly to the export file, which is significantly faster than conventional path. Export cannot export tablespaces or data files directly (only schema objects). FULL export respects schema boundaries. Transportable tablespaces are faster than export/import for table transfer.

The LOG_ARCHIVE_START parameter in the initialization parameter file controls whether automatic archiving starts when the instance starts up. Setting it to TRUE enables this. Automatic archiving is not the default. LOG_ARCHIVE_MAX_PROCESSES controls the number of archiver processes, not whether archiving is enabled.