本文详细介绍了如何管理数据库的跟踪文件和警报日志大小，包括设置后台进程跟踪文件的位置（BACKGROUND_DUMP_DEST）和服务器进程跟踪文件的位置（USER_DUMP_DEST）。同时，文章解释了如何控制所有跟踪文件的最大尺寸（MAX_DUMP_FILE_SIZE），并特别强调了在运行实例时安全删除警报日志的重要性，以及备份旧日志以供未来诊断使用。
##Location of Trace Files
1.trace files for background processes and the alert log :
BACKGROUND_DUMP_DEST
2.All trace files for server processes :
USER_DUMP_DEST
##Controlling the Size of Trace Files
control the maximum size of all trace files (excluding the alert log) using the initialization parameter<wbr> MAX_DUMP_FILE_SIZE<br><br> 对于alert log 若想要控制其大小，需要删除之前的alert log ，否者数据库还是会在之前的alert log 中追加日志，起不到控制其大小的作用。<br><wbr><br><wbr><wbr> NOTE: <You can safely delete the alert log while the instance is running, although you should consider making an archived copy of it first. This archived copy could prove valuable if you should have a future problem that requires investigating the history of an instance.还是在删除前备份下alert log ，以备以后的诊断之用><br></wbr></wbr></wbr></wbr>
1.trace files for background processes and the alert log :
BACKGROUND_DUMP_DEST
2.All trace files for server processes :
USER_DUMP_DEST
##Controlling the Size of Trace Files
control the maximum size of all trace files (excluding the alert log) using the initialization parameter<wbr> MAX_DUMP_FILE_SIZE<br><br> 对于alert log 若想要控制其大小，需要删除之前的alert log ，否者数据库还是会在之前的alert log 中追加日志，起不到控制其大小的作用。<br><wbr><br><wbr><wbr> NOTE: <You can safely delete the alert log while the instance is running, although you should consider making an archived copy of it first. This archived copy could prove valuable if you should have a future problem that requires investigating the history of an instance.还是在删除前备份下alert log ，以备以后的诊断之用><br></wbr></wbr></wbr></wbr>
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
