本文介绍了Oracle数据库中的Alert日志文件，包括其位置、记录的内容类型，如错误消息、非默认初始化参数、管理操作等，并提供了关于如何管理和维护该日志文件的建议。
Each database has an alert_.log file. The file is on the server with the
database and is stored in the directory specified with the background_dump_dest initialization parameter. The alert file of a database is a chronological log of messages and errors, including the following:
• Any nondefault initialization parameters used at startup
• All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock
errors (ORA-60) that occurred
• Administrative operations, such as the SQL statements CREATE, ALTER, DROP DATABASE, and 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
Enterprise Manager monitors the alert log file and notifies you of critical errors. You can also view the log to see noncritical error and informative messages. The file can grow to an unmanageable size. You can occasionally back up the alert file and delete the current alert file. When the database attempts to write to the alert file again, it re-creates a new one.
database and is stored in the directory specified with the background_dump_dest initialization parameter. The alert file of a database is a chronological log of messages and errors, including the following:
• Any nondefault initialization parameters used at startup
• All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock
errors (ORA-60) that occurred
• Administrative operations, such as the SQL statements CREATE, ALTER, DROP DATABASE, and 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
Enterprise Manager monitors the alert log file and notifies you of critical errors. You can also view the log to see noncritical error and informative messages. The file can grow to an unmanageable size. You can occasionally back up the alert file and delete the current alert file. When the database attempts to write to the alert file again, it re-creates a new one.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/10640532/viewspace-592338/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/10640532/viewspace-592338/
扫一扫
2078
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
