While starting ASM on 11g grid Infrastructure I was getting following errors :
SQL> connect / as sysasm
Connected to an idle instance.
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
Login with the account under which grid Infrastructure is install. In my case it's grid account and check if CSS is up and running.
$ ./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type OFFLINE OFFLINE
ora.DATA2.dg ora....up.type OFFLINE OFFLINE
ora....ER.lsnr ora....er.type ONLINE ONLINE node2
ora.asm ora.asm.type OFFLINE OFFLINE
ora.cssd ora.cssd.type ONLINE OFFLINE
ora.diskmon ora....on.type ONLINE OFFLINE
Looks like crs not started or autostart is diabled after server reboot. Let check this one out
root@node2 # ./crsctl enable crs
CRS-4013: This command is not supported in a single-node configuration.
CRS-4000: Command Enable failed, or completed with errors.
enable and disabled options are not supported with single-node configuration. Let start all the resources manually.
grid@node2$ $ ./crsctl start resource -all
CRS-5702: Resource 'ora.LISTENER.lsnr' is already running on 'node2'
CRS-2672: Attempting to start 'ora.cssd' on 'node2'
CRS-2679: Attempting to clean 'ora.diskmon' on 'node2'
CRS-2681: Clean of 'ora.diskmon' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'node2'
CRS-2676: Start of 'ora.diskmon' on 'node2' succeeded
CRS-2676: Start of 'ora.cssd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node2'
CRS-2676: Start of 'ora.asm' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.DATA.dg' on 'node2'
CRS-2672: Attempting to start 'ora.DATA2.dg' on 'node2'
CRS-2676: Start of 'ora.DATA.dg' on 'node2' succeeded
CRS-2676: Start of 'ora.DATA2.dg' on 'node2' succeeded
$ ps -ef | grep cssd
$ ./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type ONLINE ONLINE node2
ora.DATA2.dg ora....up.type ONLINE ONLINE node2
ora....ER.lsnr ora....er.type ONLINE ONLINE node2
ora.asm ora.asm.type ONLINE ONLINE node2
ora.cssd ora.cssd.type ONLINE ONLINE node2
ora.diskmon ora....on.type ONLINE ONLINE node2
back to business!
SQL> connect / as sysasm
Connected to an idle instance.
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
Login with the account under which grid Infrastructure is install. In my case it's grid account and check if CSS is up and running.
$ ./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type OFFLINE OFFLINE
ora.DATA2.dg ora....up.type OFFLINE OFFLINE
ora....ER.lsnr ora....er.type ONLINE ONLINE node2
ora.asm ora.asm.type OFFLINE OFFLINE
ora.cssd ora.cssd.type ONLINE OFFLINE
ora.diskmon ora....on.type ONLINE OFFLINE
Looks like crs not started or autostart is diabled after server reboot. Let check this one out
root@node2 # ./crsctl enable crs
CRS-4013: This command is not supported in a single-node configuration.
CRS-4000: Command Enable failed, or completed with errors.
enable and disabled options are not supported with single-node configuration. Let start all the resources manually.
grid@node2$ $ ./crsctl start resource -all
CRS-5702: Resource 'ora.LISTENER.lsnr' is already running on 'node2'
CRS-2672: Attempting to start 'ora.cssd' on 'node2'
CRS-2679: Attempting to clean 'ora.diskmon' on 'node2'
CRS-2681: Clean of 'ora.diskmon' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'node2'
CRS-2676: Start of 'ora.diskmon' on 'node2' succeeded
CRS-2676: Start of 'ora.cssd' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'node2'
CRS-2676: Start of 'ora.asm' on 'node2' succeeded
CRS-2672: Attempting to start 'ora.DATA.dg' on 'node2'
CRS-2672: Attempting to start 'ora.DATA2.dg' on 'node2'
CRS-2676: Start of 'ora.DATA.dg' on 'node2' succeeded
CRS-2676: Start of 'ora.DATA2.dg' on 'node2' succeeded
$ ps -ef | grep cssd
$ ./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type ONLINE ONLINE node2
ora.DATA2.dg ora....up.type ONLINE ONLINE node2
ora....ER.lsnr ora....er.type ONLINE ONLINE node2
ora.asm ora.asm.type ONLINE ONLINE node2
ora.cssd ora.cssd.type ONLINE ONLINE node2
ora.diskmon ora....on.type ONLINE ONLINE node2
back to business!