11g RAC R2 体系结构---进程，日志
进程结构：Overview of Oracle Clusterware Platform-Specific Software Components
When Oracle Clusterware is operational, several platform-specific processes or services run on each node in the cluster. This section describes these various processes and services.
同时参考10g Oracle Clusterware 组成
The Oracle Clusterware Stack
Oracle Clusterware consists of two separate stacks: an upper stack anchored by the Cluster Ready Services (CRS) daemon (crsd) and a lower stack
anchored by the Oracle High Availability Services daemon (ohasd). These two stacks have several processes that facilitate cluster operations. The following sections describe these stacks in more detail:
- The Cluster Ready Services Stack
- The Oracle High Availability Services Stack
The Cluster Ready Services Stack
The list in this section describes the processes that comprise CRS. The list includes components that are processes on Linux and UNIX operating systems, or services on Windows.
-
Cluster Ready Services (CRS): The primary program for managing high availability operations in a cluster.
The CRS daemon
(crsd) manages cluster resources based on the configuration information that is stored in OCR for each resource. This includes start, stop, monitor, and failover operations. Thecrsdprocess generates events when the status of a resource changes. When you have Oracle RAC installed, thecrsdprocess monitors the Oracle database instance, listener, and so on, and automatically restarts these components when a failure occurs.
-
Cluster Synchronization Services (CSS): Manages the cluster configuration by controlling which nodes are members of the cluster and by notifying members when a node joins or leaves the cluster. If you are using certified third-party clusterware, then CSS processes interface with your clusterware to manage node membership information.
-
The
cssdagentprocess monitors the cluster and provides I/O fencing. This service formerly was provided by Oracle Process Monitor Daemon (oprocd), also known asOraFenceServiceon Windows. Acssdagentfailure may result in Oracle Clusterware restarting the node. -
Oracle ASM: Provides disk management for Oracle Clusterware and Oracle Database.
-
Cluster Time Synchronization Service (CTSS): Provides time management in a cluster for Oracle Clusterware.
-
Event Management (EVM): A background process that publishes events that Oracle Clusterware creates.
-
Oracle Notification Service (ONS): A publish and subscribe service for communicating Fast Application Notification (FAN) events.
-
Oracle Agent (oraagent): Extends clusterware to support Oracle-specific requirements and complex resources. This process runs server callout scripts when FAN events occur. This process was known as RACG in Oracle Clusterware 11g release 1 (11.1).
-
Oracle Root Agent (orarootagent): A specialized
oraagentprocess that helpscrsdmanage resources owned byroot, such as the network, and the Grid virtual IP address.
The Cluster Synchronization Service (CSS), Event Management (EVM), and Oracle Notification Services (ONS) components communicate with other cluster component layers on other nodes in the same cluster database environment. These components are also the main communication links between Oracle Database, applications, and the Oracle Clusterware high availability components. In addition, these background processes monitor and manage database
operations.
The Oracle High Availability Services Stack
This section describes the processes that comprise the Oracle High Availability Services stack. The list includes components that are processes on Linux and UNIX operating systems, or services on Windows.
-
Cluster Logger Service (
ologgerd): Receives information from all the nodes in the cluster and persists in a CHM repository-based database. This service runs on only two nodes in a cluster. -
System Monitor Service (
osysmond): The monitoring and operating system metric collection service that sends the data to the cluster logger service. This service runs on every node in a cluster. -
Grid Plug and Play (GPNPD): Provides access to the Grid Plug and Play profile, and coordinates updates to the profile among the nodes of the cluster to ensure that all of the nodes have the most recent profile.
-
Grid Interprocess Communication (GIPC): A support daemon that enables Redundant Interconnect Usage.
-
Multicast Domain Name Service (mDNS): Used by Grid Plug and Play to locate profiles in the cluster, as well as by GNS to perform name resolution. The mDNS process is a background process on Linux and UNIX and on Windows.
-
Oracle Grid Naming Service (GNS): Handles requests sent by external DNS servers, performing name resolution for names defined by the cluster.
Table 1-1 List of Processes and Services Associated with Oracle Clusterware Components
| Oracle Clusterware Component | Linux/UNIX Process | Windows Services | Windows Processes |
|---|---|---|---|
| CRS |
|
|
|
| CSS |
|
|
|
| CTSS |
|
|
|
| EVM |
|
|
|
| GIPC |
|
|
|
| GNS |
|
|
|
| Grid Plug and Play |
|
|
|
| LOGGER |
|
|
|
| Master Diskmon |
|
|
|
| mDNS |
|
|
|
| Oracle agent |
|
|
|
| Oracle High Availability Services |
|
|
|
| ONS |
|
|
|
| Oracle root agent |
|
|
|
| SYSMON |
|
|
|
.
日志结构：Clusterware Log Files and the Unified Log Directory Structure
Oracle Database uses a unified log directory structure to consolidate the Oracle Clusterware component log files. This consolidated structure simplifies
diagnostic information collection and assists during data retrieval and problem analysis.
Table H-10 Locations of Oracle Clusterware Component Log Files
| Component | Log File Location |
|---|---|
| Cluster Health Monitor (CHM) |
The system monitor service and cluster logger service record log information in following locations, respectively: Grid_home/log/host_name/crfmond Grid_home/log/host_name/crflogd |
| Oracle Database Quality of Service Management (DBQOS) |
Oracle Database QoS Management Grid Operations Manager logs: Grid_home/oc4j/j2ee/home/log/dbwlm/auditing
Oracle Database QoS Management trace logs: Grid_home/oc4j/j2ee/home/log/dbwlm/logging
|
| Cluster Ready Services Daemon (CRSD) Log Files |
Grid_home/log/host_name/crsd |
| Cluster Synchronization Services(CSS) |
Grid_home/log/host_name/cssd |
| Cluster Time Synchronization Service (CTSS) |
Grid_home/log/host_name/ctssd |
| Grid Plug and Play |
Grid_home/log/host_name/gpnpd |
| Multicast Domain Name Service Daemon (MDNSD) |
Grid_home/log/host_name/mdnsd |
| Oracle Cluster Registry |
Oracle Cluster Registry tools (OCRDUMP, OCRCHECK, OCRCONFIG) record log information in the following location:Foot 2 Grid_home/log/host_name/client Cluster Ready Services records Oracle Cluster Registry log information in the following location: Grid_home/log/host_name/crsd |
| Oracle Grid Naming Service (GNS) |
Grid_home/log/host_name/gnsd |
| Oracle High Availability Services Daemon (OHASD) |
Grid_home/log/host_name/ohasd |
| Oracle Automatic Storage Management Cluster File System (Oracle ACFS) |
Grid_home/log/host_name/acfsrepl Grid_home/log/host_name/acfsreplroot Grid_home/log/host_name/acfssec Grid_home/log/host_name/acfs |
| Event Manager (EVM) information generated by |
Grid_home/log/host_name/evmd |
| Cluster Verification Utility (CVU) |
Grid_home/log/host_name/cvu |
| Oracle RAC RACG |
The Oracle RAC high availability trace files are located in the following two locations: Grid_home/log/host_name/racg $ORACLE_HOME/log/host_name/racg Core files are in subdirectories of the log directory. Each RACG executable has a subdirectory assigned exclusively for that executable. The name of the RACG executable subdirectory is the same as the name of the executable. Additionally, you can find logging information for the VIP in |
| Server Manager (SRVM) |
Grid_home/log/host_name/srvm |
| Disk Monitor Daemon ( |
Grid_home/log/host_name/diskmon |
| Grid Interprocess Communication Daemon (GIPCD) |
Grid_home/log/host_name/gipcd |
摘自文档《Database Clusterware Administration and Deployment Guide》