Identify the two situations in which you use the alert log file in your database to check the details.
(Choose two.)
A.
Running a query on a table returns “ORA-600: Internal Error.”
B.
Inserting a value in a table returns “ORA-01722: invalid number.”
C.
Creating a table returns “ORA-00955: name is already used by an existing object.”
D.
Inserting a value in a table returns “ORA-00001: unique constraint (SYS.PK_TECHP) violated.”
E.
Inserting a row in a table returns “ORA-00060: deadlock detected while waiting for resource.”
Each database has a alert_ .log file. This file is located where the database server, if you set $ ORACLE_BASE, then the default, this file is stored in the $ ORACLE_BASE / diag / rdbms / / / trace in.
Database files are listed in the warning messages in chronological order of log files, for example:
• Any non-default initialization parameters to use when starting
• All internal error has occurred (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60)
• management operations, such as SQL statements CREATE, ALTER, DROP DATABASE, and TABLESPACE, as well as Enterprise Manager or SQL * Plus statements STARTUP, SHUTDOWN, ARCHIVE LOG, and RECOVER
• multiple messages and functions shared server and dispatcher processes and associated errors
• An error occurred while the automatic refresh materialized views
Oracle DB using the alert log to keep records of these events, as an alternative to displaying this information on the operator console. (Many systems will also display information in the console.) If an administrative operation is completed successfully, the system will be “completed (Completed)” message and a time stamp is written in the alert log
To check the details: BCD already have described in detail of the cause of the error.