nerdexam
Oracle

1Z0-052 · Question #17

Identify the two situations in which the alert log file is updated with details. (Choose two.)

The correct answer is A. Running a query on a table returns "ORA-600: Internal Error" E. Rebuilding an index using ALTER INDEX ... REBUILD fails with an error "ORA-01578. The Oracle alert log records internal errors (ORA-600) and physical block corruption errors (ORA-01578) encountered during DDL operations, but not ordinary user or application-level errors.

Performing Database Maintenance

Question

Identify the two situations in which the alert log file is updated with details. (Choose two.)

Options

  • ARunning a query on a table returns "ORA-600: Internal Error"
  • BInserting a value in a table returns "ORA-01722: Invalid Number"
  • CCreating a table returns "ORA-00955: name is already used by an existing object'
  • DInserting a value in a table returns "ORA-00001: unique constraint (SYS.PK_TECHP) violated."
  • ERebuilding an index using ALTER INDEX ... REBUILD fails with an error "ORA-01578:
  • FRebuilding an index using ALTER INDEX .... REBUILD fails with an error "ORA-01578:

How the community answered

(29 responses)
  • A
    72% (21)
  • C
    7% (2)
  • D
    17% (5)
  • F
    3% (1)

Why each option

The Oracle alert log records internal errors (ORA-600) and physical block corruption errors (ORA-01578) encountered during DDL operations, but not ordinary user or application-level errors.

ARunning a query on a table returns "ORA-600: Internal Error"Correct

ORA-600 is an internal Oracle engine error indicating an unexpected condition or bug within Oracle itself; such errors are always written to the alert log because they require investigation by Oracle Support and signal a potential database integrity issue.

BInserting a value in a table returns "ORA-01722: Invalid Number"

ORA-01722 (Invalid Number) is a user-level data conversion error caused by incorrect application data and is handled entirely at the session level, so Oracle never writes it to the alert log.

CCreating a table returns "ORA-00955: name is already used by an existing object'

ORA-00955 (name already used by an existing object) is a user DDL error caused by a naming conflict; it is a session-level error and does not meet the threshold for alert log recording.

DInserting a value in a table returns "ORA-00001: unique constraint (SYS.PK_TECHP) violated."

ORA-00001 (unique constraint violated) is a common user DML error caused by duplicate data; it is an application-level error handled at the session level and is not written to the alert log.

ERebuilding an index using ALTER INDEX ... REBUILD fails with an error "ORA-01578:Correct

ORA-01578 (data block corruption) occurring during a DDL operation like ALTER INDEX REBUILD is recorded in the alert log because physical block corruption is a critical database-level condition that DBAs must investigate and remediate.

FRebuilding an index using ALTER INDEX .... REBUILD fails with an error "ORA-01578:

This choice represents a scenario that does not involve an internal or physical corruption error qualifying for alert log recording; the specific error context differs from the block corruption case in choice E that triggers an alert log entry.

Concept tested: Oracle alert log error recording criteria

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/diagnosing-and-resolving-problems.html

Topics

#alert log#ORA-600 internal error#critical errors#database monitoring

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-052 Practice