How to fix the "DiscoveryString" in profile.xml or "asm_diskstring" in ASM if set wrongly (Doc ID 1077094.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Goal

The purpose of this document is to show how to correct an incorrect value for the ASM discovery string stored in the global plug and play (GPNP) profile of an Grid Infrastructure home ($GRID_HOME/gpnp/<hostname>/profiles/peer/profile.xml).

WARNING: WARNING: It is NOT supported to modify the file profile.xml manually as it could result in an unrecoverable problem which in turn would require a rebuild of the entire cluster.

The GPNP profile is used by the CSS daemon during startup in order to discover the voting files (parameter "DiscoveryString"). An incorrect value for the discovery string will prevent the CSS daemon (and ultimately the entire CRS stack) from starting up.

Generally the discovery string will be empty i.e. it will use the default discovery method for the platform (see the following). Here is an example of a default setting when voting files are on ASM disks:

<orcl:ASM-Profile id="asm" DiscoveryString="" SPFile="+CRS/crs-cluster/asmparameterfile/registry.253.713102689"/>


The global plug and play profile is automatically updated whenever the ASM instance parameter 'asm_diskstring' is modified via the 'alter system' command.

If - for example - the following command is issued in sqlplus while connected to the ASM instance:

sqlplus / as sysasm
SQL> alter system set asm_diskstring='BAD*' scope=spfile;

the discovery string in the file profile.xml will become:

<orcl:ASM-Profile id="asm" DiscoveryString="BAD*" SPFile="+CRS/crs-cluster/asmparameterfile/registry.253.713102689"/>


On the next restart of the CRS stack, the ocssd.log will show the following errors and the startup will fail:

2010-03-24 16:01:05.762: [    CSSD][2986380176]clssnmvDDiscThread: using discovery string BAD* for initial discovery
2010-03-24 16:01:05.762: [   SKGFD][2986380176]Discovery with str:BAD*:

2010-03-24 16:01:05.762: [   SKGFD][2986380176]UFS discovery with :BAD*:

2010-03-24 16:01:05.762: [   SKGFD][2986380176]OSS discovery with :BAD*:

2010-03-24 16:01:05.762: [   SKGFD][2986380176]Discovery with asmlib :ASM:/opt/oracle/extapi/32/asm/orcl/1/libasm.so: str :BAD*:

2010-03-24 16:01:05.762: [    CSSD][2986380176]clssnmvDiskVerify: Successful discovery of 0 disks
2010-03-24 16:01:05.762: [    CSSD][2986380176]clssnmCompleteInitVFDiscovery: Completing initial voting file discovery
2010-03-24 16:01:05.762: [    CSSD][2986380176]clssnmvFindInitialConfigs: No voting files found
2010-03-24 16:01:05.763: [    CSSD][2986380176]###################################
2010-03-24 16:01:05.763: [    CSSD][2986380176]clssscExit: CSSD signal 11 in thread clssnmvDDiscThread
2010-03-24 16:01:05.763: [    CSSD][2986380176]###################################
2010-03-24 16:01:05.763: [    CSSD][2986380176]

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms