New Features for DBA’s

Subscribe to Posts by Email


 

Subscriber Count

    700

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages
«  
  »

11g Grid Infrastructure (RAC): CRS Startup Sequence

 

This is about to understand the startup sequence of Grid Infrastructure daemons and its resources in 11gR2 RAC.

 

In 11g RAC aka Grid Infrastructure we all know there are additional background daemons and agents, and the Oracle documentation is not so clear nor the other blog.

 

For example:- I have found below diagram from metalink which is very confusing.

 

 

Whilst reading the book “http://www.amazon.com/Pro-Oracle-Database-11g-Linux/dp/1430229586” found excellent diagram representing the same but very understandable manner. (at least for me)

 

image

Without much hassle or discussion with bottom to top approach, I understand now,

OHASD Phase:-

  • OHASD (Oracle High Availability Server Daemon) starts Firsts and it will start

OHASD Agent Phase:-

  • OHASD Agent starts and in turn this will start
gipcd Grid interprocess communication daemon, used for monitoring cluster interconnect
mdnsd Multicast DNS service It resolves DNS requests on behalf of GNS
gns The Grid Naming Service (GNS), a gateway between DNS and mdnsd, resolves DNS requests
gpnpd Grid Plug and Play Daemon, Basically a profile similar like OCR contents stored in XML format in $GI_HOME/gpnp/profiles/<peer> etc., this is where used by OCSSD also to read the ASM disk locations to start up with out having ASM to be up, moreover this also provides the plug and play profile where this can be distributed across nodes to cluster
evmd/

evmlogger

 Evm service will be provided by evmd daemon, which is a information about events happening in cluster, stop node,start node, start instance etc.
  • cssdagent (cluster synchronization service agent), in turn starts
ocssd Cluster synchronization service daemon which manages node membership in the cluster

If cssd found that ocssd is down, it will reboot the node to protect the data integrity.

 

  • cssdmonitor (cluster synchronization service monitor), replaces oprocd and provides I/O fencing

 

  • OHASD orarootagent starts and in turn starts
crsd.bin Cluster ready services, which manages high availability of cluster resources , like stopping , starting, failing over etc.
diskmon.bin disk monitor (diskdaemon monitor) provides I/O fencing for exadata storage
octssd.bin Cluster synchronization time services , provides Network time protocol services but manages its own rather depending on OS

CRSD Agent Phase:- crsd.bin starts two more agents

crsd orarootagent(Oracle root agent) starts and in turn this will start

gns Grid interprocess communication daemon, used for monitoring cluster interconnect
gns vip Multicast DNS service It resolves DNS requests on behalf of GNS
Network Monitor the additional networks to provide HAIP to cluster interconnects
Scan vip Monitor the scan vip, if found fail or unreachable failed to other node
Node vip Monitor the node vip, if found fail or unreachable failed to other node

crsd oraagent(Oracle Agent) starts and in turn it will start (the same functionality in 11gr1 and 10g managed by racgmain and racgimon background process) which is now managed by crs Oracle agent itself.

·

ASM & disk groups Start & monitor local asm instance
ONS FAN feature, provides notification to interested client
eONS FAN feature, provides notification to interested client
SCAN Listener Start & Monitor scan listener
Node Listener Start & monitor the node listener (rdbms?)

Hope this helps, comments & suggestions are most welcome.

-Thanks

Geek DBA

September 28th, 2012 | Tags: , , , | Category: GridInfrastructure

11 comments to 11g Grid Infrastructure (RAC): CRS Startup Sequence