nerdexam
Oracle

1Z0-062 · Question #264

You areadministering a database that supports an OLTP workload. The default UNDO tablespace is a fixed size tablespace with the RETENTION NOGUARATNEE clause and undo retention set to 12 minutes. The…

The correct answer is A. The Oracle server is unable to generate a read-consistent image for a block containing. The ORA-01555 error 'snapshot too old' indicates that an ongoing query could not reconstruct a read-consistent view of data because necessary undo information was overwritten or aged out due to insufficient undo retention or space.

Managing Undo Data

Question

You areadministering a database that supports an OLTP workload. The default UNDO tablespace is a fixed size tablespace with the RETENTION NOGUARATNEE clause and undo retention set to 12 minutes. The user SCOTT queries a large table during peak activity. Thequery runs for more than 15 minutes and then SCOTT receives the following error:

ORA-01555: snapshot too old Which is possible reason for this?

Options

  • AThe Oracle server is unable to generate a read-consistent image for a block containing
  • BThe query is unable to place data blocks in the UNDO tablespace.
  • CThe flashback data archive is not enabled for the table on which the query is issued.
  • DThere is not enough space in Fast Recovery Area.
  • EThe Oracle server is unable to generate a read-consistent image for a block containing

How the community answered

(30 responses)
  • A
    70% (21)
  • B
    3% (1)
  • C
    10% (3)
  • D
    13% (4)
  • E
    3% (1)

Why each option

The ORA-01555 error 'snapshot too old' indicates that an ongoing query could not reconstruct a read-consistent view of data because necessary undo information was overwritten or aged out due to insufficient undo retention or space.

AThe Oracle server is unable to generate a read-consistent image for a block containingCorrect

The ORA-01555 'snapshot too old' error occurs when a long-running query cannot reconstruct a consistent view of data because the required undo information, which allows a block to be read as it was at the query's start time, has been overwritten or aged out from the undo tablespace, especially with `RETENTION NOGUARANTEE` and an undo retention period shorter than the query duration.

BThe query is unable to place data blocks in the UNDO tablespace.

The ORA-01555 error signifies an issue with reading old versions of data due to missing undo, not an inability to write new data blocks into the undo tablespace.

CThe flashback data archive is not enabled for the table on which the query is issued.

Flashback Data Archive (FDA) provides long-term historical data, but it does not directly manage the undo segments necessary for read consistency of current transactions which cause ORA-01555.

DThere is not enough space in Fast Recovery Area.

The Fast Recovery Area (FRA) stores backups, archived redo logs, and flashback logs, but it is not used for storing the undo segments that are critical for achieving read consistency during active transactions.

EThe Oracle server is unable to generate a read-consistent image for a block containing

This choice is a duplicate of option A, and since only one answer is marked correct, A is the intended specific correct reason.

Concept tested: ORA-01555 'snapshot too old' and UNDO management

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/errer/ora-01555.html

Topics

#UNDO tablespace#ORA-01555#Undo retention#Read consistency

Community Discussion

No community discussion yet for this question.

Full 1Z0-062 Practice