Trace Files and the Alert Log (127)

Each server and background process can write to an associated trace file. When a
process detects an internal error, it dumps information about the error to its trace file.
If an internal error occurs and information is written to a trace file, the administrator
should contact Oracle Support Services.
All filenames of trace files associated with a background process contain the name of
the process that generated the trace file. The one exception to this is trace files
generated by job queue processes (Jnnn).
Additional information in trace files can provide guidance for tuning applications or
an instance. Background processes always write this information to a trace file when
appropriate.
Each database also has an alert.log. The alert log of a database is a chronological log
of messages and errors, including the following:
■ All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock
errors (ORA-60) that occur
■ Administrative operations, such as the SQL statements CREATE/ALTER/DROP
DATABASE/TABLESPACE and the Enterprise Manager or SQL*Plus statements
STARTUP, SHUTDOWN, ARCHIVE LOG, and RECOVER
■ Several messages and errors relating to the functions of shared server and
dispatcher processes
■ Errors during the automatic refresh of a materialized view
Oracle uses the alert log to keep a record of these events as an alternative to displaying
the information on an operator’s console. (Many systems also display this information
on the console.) If an administrative operation is successful, a message is written in the
alert log as "completed" along with a time stamp.

跟踪文件和预警日志文件
每个后台进程都有包含进程名的跟踪文件
预警日志文件是按时间来排序的 , 包含以下错误信息
1. 所有内部错误(ORA-600) , 块错误 , 死锁
2. 管理员操作 , create database/tablespace等
3. 共享服务和分配进程等服务和错误信息
4. 物化视图的刷新时的错误

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/10599713/viewspace-980333/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/10599713/viewspace-980333/