Playing with GPNP profile.

Current scenario:

2 Node cluster

Cluster name : testdb01.example.com

Host names : test01, test02

Overview:



– Rename GPnP profile on a node (test02)

– Stop and restart crs

– File pending.xml is created in GRID_HOME/gpnp//profiles/peer

– Change ASM_DISKSTRING parameter which causes GPnP profile to be updated

– As soon as the parameter is changed, pending.xml is renamed to profile.xml and Discoverystring for ASM is updated in it.

– Rename GPnP profile on test02


   [root@test02 cdata]# mv /u01/app/11.2.0/grid/gpnp/test02/profiles/peer/profile.xml /u01/app/11.2.0/grid/gpnp/test02/profiles/peer/profile.bak


– Stop and restart crs on test02


     [root@test02 cdata]#crsctl stop crs
     [root@test02 cdata]#crsctl start crs

— Check the alert log simultaneously and note that just prior to the start of CSSD daemon,

GPnP daemon on node2 copies the GPnP profile from test01 and file pending.xml is created in GRID_HOME/gpnp//profiles/peer

[ohasd(24187)]CRS-2772:Server ‘test02? has been assigned to pool ‘Free’.
2013-01-17 01:35:14.635

[cssd(24416)]CRS-1713:CSSD daemon is started in clustered mode

[root@test02 cdata]# ls /u01/app/11.2.0/grid/gpnp/test02/profiles/peer/pending*

/u01/app/11.2.0/grid/gpnp/test02/profiles/peer/pending.xml

—- Open the file pending.xml and note that DiscoveryString for ASM is “”



DiscoveryString=””SPFile=”+DATA/testdb01/asmparameterfile/registry.253.804837235?/>

– Change ASM_DISKSTRING parameter which causes GPnP profile to be updated

 SQL>alter system set ASM_DISKSTRING=’ORCL:*’;

– As soon as the parameter is changed, pending.xml is renamed to profile.xml and Discoverystring for ASM is updated in it.


[root@test02 cdata]# ls /u01/app/11.2.0/grid/gpnp/test02/profiles/peer/profile.xml

/u01/app/11.2.0/grid/gpnp/test02/profiles/peer/profile.xml

—- Open the file profile.xml and note that DiscoveryString for ASM has been updated


DiscoveryString=”ORCL:*” SPFile=”+DATA/testdb01/asmparameterfile/registry.253.804837235?/>
———————————————————————————-

Note : Whenever GPnP profile is not present, it is automatically copied from existing nodes by GPnPd as pending.xml . Whenever, profile is updated, it is automatically renamed to profile.xml.

  • December 30, 2017 | 14 views
  • Comments