1Z0-052 · Question #96
Identify the two situations in which you use the alert log file in your database to check the details. (Choose two.)
The correct answer is A. Running a query on a table returns "ORA-600: Internal Error." E. Inserting a row in a table returns "ORA-00060: deadlock detected while waiting for resource.". The Oracle alert log records internal database errors and critical concurrency events like deadlocks, but not routine user-level SQL errors caused by bad data or naming conflicts.
Question
Identify the two situations in which you use the alert log file in your database to check the 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."
- EInserting a row in a table returns "ORA-00060: deadlock detected while waiting for resource."
How the community answered
(40 responses)- A80% (32)
- B5% (2)
- C3% (1)
- D13% (5)
Why each option
The Oracle alert log records internal database errors and critical concurrency events like deadlocks, but not routine user-level SQL errors caused by bad data or naming conflicts.
ORA-600 is an internal Oracle engine error signaling an unexpected condition; Oracle always writes ORA-600 errors to the alert log along with a trace file reference so DBAs and Oracle Support can diagnose the root cause.
ORA-01722 (invalid number) is a standard data conversion error caused by bad user input; it is returned only to the offending session and is never written to the alert log.
ORA-00955 (name already used by existing object) is a routine DDL naming conflict returned directly to the user session; it does not indicate an internal database problem and is not recorded in the alert log.
ORA-00001 (unique constraint violated) is a standard data integrity error returned to the offending session only; user-level constraint violations are not considered critical enough to be logged in the alert log.
ORA-00060 deadlock events are written to the alert log because Oracle treats deadlocks as significant instance-level concurrency events, and the log entry includes a reference to a trace file containing the full deadlock graph.
Concept tested: Oracle alert log contents and error severity classification
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/monitoring-the-database.html#GUID-2724601A-9B8C-4EB6-A48E-C5D38C4B4F7E
Topics
Community Discussion
No community discussion yet for this question.