Grid Plug and Play [GPNP] Profile :

It is small xml file located  in $GRID_HOME/gpnp/<hostname>/profiles/peer under the name profile.xml. It is used to establish the correct global personality of a node. Each node maintains a local copy of the GPnP Profile and is maintanied by the GPnP Deamon (GPnPD) .

Now , with above file we will understand what it stores .

  1. Cluster Name : In our case rac cluster.
  2. Storage used for CSS : here +asm
  3. Storage used for ASM: SPFILE location, ASM DiskString
  4. Public or Private[Interconnect] Network classification : In above example eth0 is used for public network and eth1 is used for Interconnect.

With above example we have learn what is stored in GPnP profile. Now , how it is being accessed ?

To start Oracle Clusterware , voting disk needs to be accessed. If voting disk in stored in ASM , GPnP will tell clusterware that it is stored in ASM.

kfed utility is used to read voting disk even if asm is not up.

Whenever a node is started/added to the cluster, the clusterware software on the starting node starts a GPnP agent.

If node if already a part of cluster , GPnP profile is read by GPnP agent.

If the node is being added to the cluster, GPnP agent locates agent on another existing node using multicast protocol (provided by mDNS) and gets the profile from that agent.

We can also check GPnP profile using below command :

Stay tuned for More articles on Oracle RAC

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel : https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.