Shulou(Shulou.com)06/01 Report--

There are always some DBA or engineer-installed databases that are not standard enough to find the alarm log file according to the regular discussion. Let me tell you a little way, no matter how you don't follow the routine, I can find the alarm log.

1. View the parameter 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

Usually, the alarm log will be in the path corresponding to the parameter background_dump_dest.

2. Or use the find command

Find /-name al*.log

The name of the alarm log is regular alert_sid.log,so. You can find it.

3. Pay attention

Note:

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

4. Alert_sid.log description

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.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.