nerdexam
Oracle

1Z0-062 · Question #292

Your database is configured in ARCHIVELOG mode, and a daily full database backup is taken by using RMAN. Control file autobackup is configured. Loss of which three database files can lead to an…

The correct answer is A. inactive online redo log file group E. active online redo log file group F. all the control flies. This question asks about file types whose loss can cause incomplete recovery in an Oracle database configured for ARCHIVELOG mode with RMAN backups and control file autobackup.

Performing Backup and Recovery

Question

Your database is configured in ARCHIVELOG mode, and a daily full database backup is taken by using RMAN. Control file autobackup is configured. Loss of which three database files can lead to an incomplete recovery? (Choose three.)

Options

  • Ainactive online redo log file group
  • Ba data file belonging to the default temporary tablespace
  • Ca data file belonging to the SYSAUX tablespace
  • Dserver parameter file (SPFILE)
  • Eactive online redo log file group
  • Fall the control flies

How the community answered

(42 responses)
  • A
    43% (18)
  • B
    17% (7)
  • C
    33% (14)
  • D
    7% (3)

Why each option

This question asks about file types whose loss can cause incomplete recovery in an Oracle database configured for ARCHIVELOG mode with RMAN backups and control file autobackup.

Ainactive online redo log file groupCorrect

The loss of inactive online redo log files means that redo records required for point-in-time recovery beyond the latest archived log might be missing, leading to an incomplete recovery.

Ba data file belonging to the default temporary tablespace

A temporary tablespace stores temporary segment data and does not contain user or system data that needs to be recovered to ensure transactional consistency; its loss does not typically lead to incomplete recovery.

Ca data file belonging to the SYSAUX tablespace

A data file belonging to the SYSAUX tablespace contains auxiliary system data. While critical, its loss alone can often be recovered completely using RMAN backups and archived redo logs, assuming other vital files are intact.

Dserver parameter file (SPFILE)

The SPFILE (Server Parameter File) defines the instance's initialization parameters. Its loss can be restored from backup or recreated manually; it does not directly contain data requiring transaction recovery and thus doesn't cause incomplete recovery itself.

Eactive online redo log file groupCorrect

The active online redo log file group contains the most recent redo records that have not yet been archived. Losing this file group means that changes since the last archived log cannot be recovered, necessitating an incomplete recovery.

Fall the control fliesCorrect

If all control files are lost, even with autobackup, the database structure and the mapping of data files to redo log files might be lost, making it difficult or impossible to reconstruct the database to a consistent state without incomplete recovery.

Concept tested: Oracle database recovery, critical file types

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/performing-recovery.html#GUID-E5E2C429-8758-4D54-B83F-5589BB5D1905

Topics

#database recovery#ARCHIVELOG mode#redo log files#control file

Community Discussion

No community discussion yet for this question.

Full 1Z0-062 Practice