本文解析了Oracle诊断后台进程在后台写入跟踪文件的行为，指出这通常是一个正常现象，并非问题所在。建议在没有数据库挂起或宕机的情况下忽略此现象。若遇到实际问题，应查看警报日志以获取更准确的故障定位。
oracle 给的回复是
Diag background process will write to trace file in the background dump destination hence DIAG backgroud process
take high I/O.
This should be normal and not a worry.
Diag process writing to trace file doesn't always indicate a problem.
The real impact of the problem can be seen only after reviewing the Alert logs.
However, If you are not facing any hang / shutdown with database then you can ignore it.
DIAG并不总是因为产生问题而生成trace 文件，
出现问题会在alert log文件中显示
因此如果没有出现hang 或者宕机的情况，是可以被忽略的。
Diag background process will write to trace file in the background dump destination hence DIAG backgroud process
take high I/O.
This should be normal and not a worry.
Diag process writing to trace file doesn't always indicate a problem.
The real impact of the problem can be seen only after reviewing the Alert logs.
However, If you are not facing any hang / shutdown with database then you can ignore it.
DIAG并不总是因为产生问题而生成trace 文件，
出现问题会在alert log文件中显示
因此如果没有出现hang 或者宕机的情况，是可以被忽略的。
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
