alert_sid.log 告警日志找不到怎么辦？

總是有一些DBA或者工程師安裝的數(shù)據(jù)庫不夠規(guī)范，按照常規(guī)討論找不到告警日志文件。告訴大家一個(gè)小方法，不管你怎么不按照套路出牌，我都能找到告警日志。

1、查看參數(shù)background_dump_dest
SQL> show parameter dump

NAME TYPE VALUE

background_core_dump string partial
background_dump_dest string /u01/app/diag/rdbms/bdpdb/bdpdb/trace
core_dump_dest string /u01/app/diag/rdbms/bdpdb/bdpdb/cdump
max_dump_file_size string unlimited
shadow_core_dump string partial
user_dump_dest string /u01/app/diag/rdbms/bdpdb/bdpdb/trace
通常告警日志會在background_dump_dest這個(gè)參數(shù)對應(yīng)路徑下

2、或者使用查找命令
find / -name al*.log
--告警日志的名字是有規(guī)律的alert_sid.log，so 你可以find了

3、注意
Note:

The BACKGROUND_DUMP_DEST parameter is deprecated in Oracle Database 12c Release 1 (12.1.0.1).

4、alert_sid.log說明
An alert log in the directory specified by BACKGROUND_DUMP_DEST logs significant database events and messages. Anything that affects the database instance or global database is recorded here. The alert log is a normal text file. Its file name is operating system-dependent. For platforms that support multiple instances, it takes the form alert_sid.log, where sid is the system identifier. This file grows slowly, but without limit, so you might want to delete it periodically. You can delete the file even when the database is running.