Database Home > Related LinksRELATED LINKS) "Area >" Alert Log Content (Alertlog content) "
Each database has a alert_<sid >.log file. This file is located in the same server as the databaseif $oracle_base is set, this file is stored by default in the$ORACLE the _base/diag/rdbms/<db_name>/<sid>/trace. Database alert files are log files that list messages in chronological order, such as:? Any non-default initialization parameters that are used at startup? All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that have occurred? Administrative operations, such as SQL statements create, ALTER, DROP DATABASE, and Tablespace,as well as Enterprise Manager or Sql*plus statement startup, SHUTDOWN, ARCHIVE LOGand Recover? Multiple messages and errors related to the functionality of the shared server and dispatcher processes? Errors that occur when the entity view is automatically refreshed Oracle DB uses an alert log to keep records of these events as shown on the Operator consoleAlternative methods of information. (Many systems will display this information in the console at the same time.) ) If a management actioncompletes successfully, the system writes the "completed (completed)" message and a timestamp to the alert log. Enterprise Manager can monitor the alert log files and notify you of serious errors. You can also view the log,to check for non-critical errors and informational messages. Because the alert file grows to a size that cannot be managed, you canback up the file regularly and delete the current alert file. When the database tries to write to the alert file again, it re-Create a new alert file. Note: $ORACLE The _base/diag/rdbms/<db_name>/<sid>/alert directory has an XMLversion of the alert log. to determine the location of the alert log through Sql*plus, follow these steps:? Use Sql*plus (or other query tools, such as SQL Developer) to connect to the database. Query the V$diag_info view.to view a plain text alert log without XML markup, do the following:? In the V$diag_info query results, note the path that corresponds to the DIAG Trace entry. Change the directory tothe path. ? Open the Alert_sid.log file using a text editor.to view the alert log in XML format, do the following:? In the V$diag_info query results, note the path that corresponds to the DIAG Alert entry. Change the directory tothe path. ? Open the Log.xml file using a text editor. [email protected]> SELECT * from v$diag_info; inst_id NAME &N Bsp value--------------------------------------------------------------------- --------------------- 1 Diag Enabled true 1 ADR Base /u01/app/oracle 1 ADR Home /u01/app/oracle /diag/rdbms/test0924/test0924 1 diag Trace &NBS P /u01/app/oracle/diag/rdbms/test0924/test0924/trace 1 diag Alert & nbsp /u01/app/oracle/diag/rdbms/test0924/test0924/alert 0%IAG Incident /u01/app/oracle/diag/rdbms/test0924/test0924/incident 1 Diag cdump /u01/app/oracle/diag/rdbms/ test0924/test0924/cdump 1 Health Monitor &NBSP;/U01/AP p/oracle/diag/rdbms/test0924/test0924/hm 1 Default Trace File &NBSP ;/u01/app/oracle/diag/rdbms/test0924/test0924/trace/test0924_ORA_24429.TRC1 Active problem count 0 1 active Incident count 0 rows selected.
? Each server and background process writes information to the associated trace file. The error message is written to the corresponding trace file. Automated Diagnostic Data Archive (ADR). – Central repository with tracking and event logging information for the entire system – store database diagnostic data such as:-Trace-Alert logs-health state monitor reports each server and background process writes information to the associated trace file. When the process detects an internal error, it will haveThe information about the error is dumped into the trace file for the process. If an internal error occurs and the information is written in the trace file,the administrator should contact Oracle Support Services. All file names for the trace files that are associated with the background process contain the name of the process that generated the trace file. The onlyexceptions are trace files that are generated by the job queue process (JNNN). Additional information in the trace file can provide guidance for optimizing an application or an instance. The background process is alwaysThe information is written to the trace file when appropriate. From Oracle Database One G, an advanced error diagnosis infrastructure was introduced to avoid, detect, diagnose, andsolve the problem. In particular, this feature addresses issues that include critical errors, such as database code bugs, metadata lossbad and serious errors caused by customer data corruption. When a critical error occurs, an unexpected event number is assigned to it, and the diagnostic data for the error is immediately captured by the system(such as a trace file) and use that number to mark this data. The data is then stored in the Automated diagnostics repository(ADR, file-based repositories outside the database), which can later be numbered by an unexpected eventretrieve and analyze the data. ADR is a central repository that contains tracking and event logging information for the entire system to provide database diagnosticsdata (such as tracking, alert logs, Health Monitor reports, and so on). The ADR root is also known as the ADR base directory, and its location is set by the Diagnostic_dest initialization parameter. If you omit this argument or leave it blank, the database is set to Diagnostic_dest at startup, as follows:? If the ORACLE_BASE environment variable is set, the Diagnostic_dest is set to theoracle_base the specified directory. ? If the ORACLE_BASE environment variable is not set, the diagnostic_dest is set to$ORACLE _home/log. The location of the ADR home directory is given by the following path, which begins with the ADR base directory:./diag/product_type/db_id/instance_id
Source: http://blog.csdn.net/rlhua/article/details/12709243
