Oracle Cluster components

Oracle storage components for cluster parts

Oracle A cluster component consists of its storage structure and a set of processes running on each cluster node. The storage structure consists of two parts: OCR, voting disk plus two local files-OLR and Gpnp

[[Email protected]~]$Cat/etc/oracle/ocr.loc
ocrconfig_loc=+data/bj-ft-cluster/ocrfile/registry.255.873380471
Local_only=false
[Email protected] ~]$crsctl query CSS Votedisk
# # state file Universalid file Name Disk Group
--  -----   -----------------               --------- ---------
1. ONLINE A2B7346146744F3DBF03D9CD47A184CB (/DEV/ORACLEASM/DISKS/DISK1) [DATA]
Located 1 Voting disk (s).

Oracle two files for cluster components: OLR and GPNP configuration files are stored in the local file system.

[[Email protected]~]$ Cat/etc/oracle/olr.loc
Olrconfig_loc=/apps/ora12c/12.1.0/grid/cdata/bj-ft-vm-123-16.olr
Crs_home=/apps/ora12c/12.1.0/grid

[[Email protected]~]$ Ocrcheck-local-config
Oracle Local Registry configuration is:
Device/filename:/APPS/ORA12C/12.1.0/GRID/CDATA/BJ-FT-VM-123-16.OLR

[[Email protected]]$ More $GRID _home/gpnp/bj-ft-vm-123-16/profiles/peer/profile.xml

Cluster piece software stack

starting with ORACLE11GR2, Oracle re-engineered the cluster components into two software stacks: Highly available stacks and CRS stacks, each composed of several background processes

The highly available stack is the Oracle underlying service stack, based on the Oracle Ohas process. Includes: Gpnp, GNS, GIPC, MDNs, Osysmond, Ologgerd

CRS The stack is an Oracle upper stack that relies on a highly available stack, including: CRS, CSS, Cssdagent, Cssdmonitor, CTSS, EVM, ONS, Oracle ASM, oraagent, Orarootagent

Cluster part boot sequence

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5A/35/wKiom1T5aKTBc5EvAAMVPC5sVrk409.jpg "title=" QQ picture 20150306164254.png "alt=" Wkiom1t5aktbc5evaamvpc5svrk409.jpg "/>

Level NO. 0:

The cluster components are automatically started through the INIT process of the operating system. The init process derives the INIT.OHASD process, and the INIT.OHASD process starts the OHASD process again.

This configuration is written in /etc/inittab in the file

[[Email protected]~]$ cat/etc/inittab|grep init.d|grep-v grep
HTFA:35:RESPAWN:/ETC/INIT.D/INIT.TFA Run >/dev/null 2>&1</dev/null
H1:35:RESPAWN:/ETC/INIT.D/INIT.OHASD Run >/dev/null 2>&1</dev/null

if the system is rhel6, the files used to configure and start the INIT.OHASD process are /etc/init/oracle-ohasd.conf

[[Email protected]~]# cat/etc/init/oracle-ohasd.conf
# Copyright (c) 2001, Oracle and/or its affiliates. All rightsreserved.
#
# Oracle OHASD Startup

Start on RunLevel [35]
Stop on RunLevel [!35]
Respawn
EXEC/ETC/INIT.D/INIT.OHASD Run >/dev/null 2>&1</dev/null

The Init.ohasdrun part of the article started the Ohasd.bin background process

[[Email protected]]$ PS Aux|grep ohasd|grep-v grep
Root 3822 0.4 0.8 385384 66268? SSL 13:57 0:23/apps/ora12c/12.1.0/grid/bin/ohasd.binreboot
Root 3931 0.0 0.0 10796 1184? Ss 13:58 0:00/BIN/SH/ETC/INIT.D/INIT.OHASD Run

Once OHASD is started at level No. 0, at the next level of 1-4, OHASD will directly or indirectly initiate other processes for cluster components, as well as other resources managed.

Level 1th: OHASD Direct derivation of 4 agent processes

Cssdmonitor : CSS Monitor process

ohasdorarootagent : Oracle root Agent process for highly available stacks

ohasdoraagent : Oracle Agent process for highly available stacks

cssdagent : The proxy process for CSS

Level 2nd:

ohasdoraagent will derive 5 processes

MDNSD : MDNs Daemon

GIPCD : The process of inter-process communication between grids

GPNPD : Gpnp Configuration daemon

EVMD : Event Monitor Process

ASM : Monitoring resources for ASM Instances

ohasdorarootagent will derive 4 processes

CRSD : CRS Daemon

CTSSD : CTSS Daemon

Diskmon : Disk Monitor daemon

ACFS : (ASM Cluster file system) driver

Level 3rd:

CRSD derivation of two CRSD agent processes: CRSD orarootagent and CRSD oraagent

Level 4th:

crsdorarootagent start the following resources

networksources : network resources

Scanip : Scan IP

node VIP : Virtual IP for each node

Acfregisry : Acfs Registration Form

GNSVIP : If you use GNS, the corresponding GNS virtual IP

crsdoraagent start the following resources

asminstance : ASM Instance

diskgroups : Used to manage and monitor ASM disk groups

dbresources : For managing, monitoring databases and instances

Scanlistener : Scan is listening to the IP of scan

Listener : The VIP of the node is listening

Services : Database service

Eons : ONS Enhancements

ONS :

GNS : Process Name resolution

GSD : For backwards compatibility

Finishing: In-depth understanding of Oracle RAC 12c

This article is from the "just out of the shell of the Birds" blog, please be sure to keep this source http://qhd2004.blog.51cto.com/629417/1617994

Oracle Cluster components