In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Starting from 11g, Oracle has made great adjustments to the log structure, and the log storage directory and storage format have changed. The following summarizes the storage directory and directory structure of Oracle Database, Oracle snooping, ASM, and Oracle GI logs.
1. Oracle Database log
The Oracle Database log is stored in the $ORACLE_BASE/diag/rdbms// directory.
ORACLE_BASE/diag/rdbms///alert is used to store Oracle Database's alert log, which is stored as a xml file, which is a new feature introduced by 11g.
ORACLE_BASE/diag/rdbms///trace is used to store the alert log and trace log of Oracle Database. Alert logs are stored as text files with a naming convention of alert_.log
ORACLE_BASE/diag/rdbms///cdump is used to store the memory dump directory directory.
ORACLE_BASE/diag/rdbms///incident is used to store event-related log and file information.
2. Monitor log
The listening log in a single instance environment is stored in $ORACLE_BASE/diag/tnslsnr//. But if the log is in the RAC environment, the log is stored in $GRID_BASE/diag/tnslsnr//
The directory structure and function are similar to Oracle Database.
3. ASM log
ASM logs are stored in $GRID_BASE/diag/asm//
The directory structure and function are similar to Oracle Database.
4. Oracle cluster log
The Oracle Clusterware diagnostic log file is stored in the $GRID_HOME/log/ directory. Each component in GI has its own directory in the $GRID_HOME/log/ directory. Debug log files related to clusterware for Oracle clusterware are stored in the $GRID_HOME/log/ directory. In a typical 11g R2 GI directory, you can find the following directories, which contain debug log files for different components of GI:
$GRID_HOME/log//alert.log-for problems with clusterware, check this file first
GRID_HOME/log//agent contains trace and diagnostic log files for oraagent, orarootagent, oracssdagent, and oracssdmonitor of CRSD and OHASD daemons.
GRID_HOME/log//client contains trace and diagnostic logs for various GI clients, such as CLSCFG/GPNP/OCRCONFIG/OLSNODES/OIFCFG.
GRID_HOME/log//crfmond contains trace and diagnostic log files for system monitoring service records provided by the Oracle Cluster Health Monitor (Oracle CHM).
GRID_HOME/log//cssd contains cluster synchronization CSS logs, which include actions from client-side CSS listeners, such as reconfiguration, lack of check-in, connection, and disconnection. In some cases, the logger logs the message with the category of the restart operation auth.crit that Oracle completed. This information can be used to check the exact time when the restart occurred.
GRID_HOME/log//cvu contains trace and debug logs generated by the Oracle cluster verification utility.
GRID_HOME/log//evmd contains trace and diagnostic files for the event volume manager (EVM) and the evmlogger daemon. It is used less frequently in debugging than in crsd and cssd directories.
GRID_HOME/log//gnsd contains trace and debug log files to troubleshoot issues related to the Oracle grid naming service, which was introduced in Oracle GI.
GRID_HOME/log//mdnsd contains trace and diagnostic log files for troubleshooting multicast domain name services. The Oracle grid naming service uses this service to manage name resolution and service discovery.
GRID_HOME/log//racg includes trace and debug logs in each Oracle RACG executable.
GRID_HOME/log//crflogd contains trace and diagnostic log files for the cluster logger service records provided by the Oracle Cluster Health Monitor (Oracle CHM).
GRID_HOME/log//crsd contains trace and diagnostic log files for the Oracle CRSD daemon, which is a good place to start in the event of any Oracle clusterware problems.
GRID_HOME/log//ctssd contains debug log files for troubleshooting the Oracle cluster time synchronization service, which was introduced in Oracle GI to synchronize clocks on cluster nodes.
The debug log file used by $GRID_HOME/log//diskmon to troubleshoot the Oracle disk monitor daemon.
GRID_HOME/log//giplcd contains debug and trace files for troubleshooting Oracle grid inter-process communication keeper process problems.
GRID_HOME/log//gpnpd contains logs and output files for the Oracle grid plug-and-play daemon.
GRID_HOME/log//ohasd contains logs and output files for the Oracle high availability service daemon. Ohasd log files are really important for diagnosing cluster startup problems in Oracle11g and later versions.
GRID_HOME/log//srvm contains the log file for the Oracle Server Manager service.
Reference: Oracle Database 11g RAC Manual, Administrator's Guide
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.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.