oracle RAC Startup Sequence

By -
Cluster ware start up sequence for oracle release 11gr2.

This description is also from the MOS note stated above

Short summary of the startup sequence: INIT spawns init.ohasd (with respawn) which in turn starts the OHASD process (Oracle High Availability Services Daemon).
This daemon spawns 4 processes.

Level 1: OHASD Spawns:

    cssdagent         - Agent responsible for spawning CSSD.
    orarootagent     - Agent responsible for managing all root owned ohasd resources.
    oraagent         - Agent responsible for managing all oracle owned ohasd resources.
    cssdmonitor        - Monitors CSSD and node health (along wth the cssdagent).
 

Level 2: OHASD rootagent spawns:
    CSDD (ora.cssd)     - Cluster Synchronization Services
    CRSD(ora.crsd)     - Primary daemon responsible for managing cluster resources.
    CTSSD(ora.ctssd)     - Cluster Time Synchronization Services Daemon
    Diskmon(ora.diskmon)
    ACFS (ASM Cluster File System) Drivers

Level 2: OHASD oraagent spawns:

    MDNSD(ora.mdnsd)     - Used for DNS lookup
    GIPCD(ora.gipcd)     - Used for inter-process and inter-node communication
    GPNPD(ora.gpnpd)     - Grid Plug & Play Profile Daemon
    EVMD(ora.evmd)     - Event Monitor Daemon
    ASM(ora.asm)     - Resource for monitoring ASM instances

Level 3: CRSD spawns:

    orarootagent     - Agent responsible for managing all root owned crsd resources.
    oraagent         - Agent responsible for managing all oracle owned crsd resources.

Level 4: CRSD rootagent spawns:

    Network resource     - To monitor the public network
    SCAN VIP(s)     - Single Client Access Name Virtual IPs
    Node VIPs         - One per node
    ACFS Registery     - For mounting ASM Cluster File System
    GNS VIP (optional)     - VIP for GNS

Level 4: CRSD oraagent spawns:

    ASM Resouce     - ASM Instance(s) resource
    Diskgroup         - Used for managing/monitoring ASM diskgroups.
    DB Resource     - Used for monitoring and managing the DB and instances
    SCAN Listener     - Listener for single client access name, listening on SCAN VIP
    Listener         - Node listener listening on the Node VIP
    Services         - Used for monitoring and managing services
    ONS         - Oracle Notification Service
    eONS         - Enhanced Oracle Notification Service
    GSD         - For 9i backward compatibility
    GNS (optional)     - Grid Naming Service - Performs name resolution

Resource: http://reneantunez.blogspot.in/2012/10/rac-11gr2-clusterware-startup-sequence.html

For easy one: http://vineetarneja.blogspot.in/2017/08/oracle-11gr2-rac-startup-sequence.html

Best Regards
Nikhil Kumar.

Comments

Post a Comment

Popular posts from this blog

How to set the root password after creating instance on oracle cloud

By -
How to set the root password after creating instance on oracle cloud? since you have created instance on oracle cloud, it requires you private .ppk key file to login from putty you can login on your instance by directly providing that private key. and on Linux/Unix defult user is "opc". since during creation of instance it  will not ask you for  root password. You dont need any password to connect to root. to connect to root type below command as opc user. [opc@sts ~]$ sudo su [root@sts opc]# by this you will login as root. Now change your password [root@sts opc]# passwd Changing password for user root. New password: Retype new password: passwd: all authentication tokens updated successfully. [root@sts opc]# All done. Thanks & Regards Nikhil Kumar.
Read more

TNS-12541 TNS-12560 TNS-00511 TNS:protocol adapter error No listener

By -
Oracle Listener does not start with errors:  TNS-12541: TNS:no listener TNS-12560, TNS-00511, Linux Error: 2: No such file or directory, The listener supports no services euls25002.sgp.st.com:oraSID 51> ps -ef | grep -i tns root       330     2  0 Jul19 ?        00:00:00 [netns] oraSID   17512     1  0 Jul20 ?        00:01:25 /oracleSID/SID/121/bin/tnslsnr LISTENER_SID -inherit oraSID   56223 56131  0 08:02 pts/1    00:00:00 grep --color=auto -i tns euls25002.sgp.st.com:oraSID 52> lsnrctl status LISTENER_SID LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 25-SEP-2017 08:02:19 Copyright (c) 1991, 2014, Oracle.  All rights reserved. Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SID.WORLD)) TNS-12541: TNS:no listener  TNS-12560: TNS:protocol adapter error   TNS-00511: No listener    Linux Error: 2: No such file or directory ...
Read more

Queryable inventory could not determine the current opatch status.

By -
[oracle@Testing02 OPatch]$ ./datapatch -verbose SQL Patching tool version 12.2.0.1.0 Production on Fri May 15 15:54:19 2020 Copyright (c) 2012, 2019, Oracle.  All rights reserved. Log file for this invocation: /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log Connecting to database...OK Bootstrapping registry and package to current versions...done Queryable inventory could not determine the current opatch status. Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual' and/or check the invocation log /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log for the complete error. Prereq check failed, exiting without installing any patches. Please refer to MOS Note 1609718.1 and/or the invocation log /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log for information on how to resolve the above errors. SQL...
Read more