This is one of my fist posts under Pythian’s blog. I will try to keep those short and simple at the beginning.
Recently I was troubleshooting a new GNS (Grid Name Services) functionality.
For more information please see here: Oracle Clusterware Network Configuration Concepts.
I have noticed that there is a-trace-level parameter in the GNS process string.
# ps -ef | grep gns
root 26790 1 2 14:41 ? 00:00:00 /u01/app/11.2.0/grid/bin/gnsd.bin -trace-level 0 -ip-address 10.10.193.201 -startup-endpoint ipc://GNS_hostrac01_23867_408c49e351f1f6a8
root 26825 17210 0 14:41 pts/1 00:00:00 grep gns
Unfortunately there is no description as of now in the documentation or MOS on how to change it to generate invaluable diagnostic information.
NOTE: I am sure the documentation will be updated in Database 12c version (c for Cloud ;)
For a time being the following should work for you:
# /u01/app/11.2.0/grid/bin/crsctl modify resource ora.gns -attr "TRACE_LEVEL=6"
# /u01/app/11.2.0/grid/bin/srvctl stop gns
# /u01/app/11.2.0/grid/bin/srvctl start gns
I hope that this advice will help you to diagnose your GNS issue.
I will blog about the way I resolved future GNS-related issues later on.
It looks like I have said too much for my very first post already.
See you around,
Just another DBA from down under
thanks for the hint and congratulations on your 1st blogpost! Keep them coming!
Thank you for your warm Welcome!
I will try my best to highlight my best findings in regular DBA work here from now on.
Stay tuned ;)