ORA-29701 when Oracle 11gR2 starts the ASM instance

[Grid @ vm11gr2]/home/grid>Sqlplus "/as sysasm"

SQL * Plus: Release 11.2.0.1.0 Production on Sun Oct 25 10:16:21 2009

Copyright (c) 1982,200 9, Oracle. All rights reserved.

Connected to an idle instance.
SQL>Startup
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
Unable to connect to the CSS service. Check on the operating system.

[Grid @ vm11gr2]/home/grid>Crsctl check css
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
[Grid @ vm11gr2]/home/grid>
[Grid @ vm11gr2]/home/grid> ps-ef | grep cssd
There is no CSS Service daemon process. Let's take a look at the HAS (High Availability Service) status.

[Grid @ vm11gr2]/home/grid>Crsctl check has
CRS-4638: Oracle High Availability Services is online

[Grid @ vm11gr2]/home/grid>Ps-ef | grep d. bin
Grid 5886 1 0 :06? 00:00:01/u01/app/grid/product/11.2/grid/bin/ohasd. bin reboot
[Grid @ vm11gr2]/home/grid>
The hasservice is actually started, and the ora.css d and ora. diskmon services depend on HAS maintenance.


Further view the status of each resource
[Grid @ vm11gr2]/home/grid>Crs_stat-t
Name Type Target State Host
--------------------------------------------------------------
Ora. FLASH_DATA.dg ora. diskgroup. type OFFLINE vm11gr2
Ora. SYS_DATA.dg ora. diskgroup. type OFFLINE vm11gr2
Ora. asm ora. asm. type OFFLINE vm11gr2
Ora.css d. type OFFLINE vm11gr2
Ora. diskmon ora. diskmon. type OFFLINE vm11gr2
[Grid @ vm11gr2]/home/grid>

[Grid @ vm11gr2]/home/grid>Crsctl status resource-t
--------------------------------------------------------------------------------
Name target state server state _ DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
Ora. FLASH_DATA.dg
OFFLINE vm11gr2
Ora. SYS_DATA.dg

OFFLINE vm11gr2
Ora. asm

OFFLINE vm11gr2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
Ora.css d

1 OFFLINE
Ora. diskmon

1 OFFLINE

Click the attributes of ora.css d and ora. diskmon.
[Grid @ vm11gr2]/home/grid> crs_stat-p ora.css d
Name‑ora.css d
Type‑ora.css d. type
ACTION_SCRIPT =
ACTIVE_PLACEMENT = 0
AUTO_START = never
CHECK_INTERVAL = 30
DESCRIPTION = "Resource type for CSSD"
FAILOVER_DELAY = 0
FAILURE_INTERVAL = 3
FAILURE_THRESHOLD = 5
HOSTING_MEMBERS =
PLACEMENT = balanced
RESTART_ATTEMPTS = 5
SCRIPT_TIMEOUT = 600
START_TIMEOUT = 600
STOP_TIMEOUT = 900
UPTIME_THRESHOLD = 1 m

[Grid @ vm11gr2]/home/grid>Crs_stat-p ora. diskmon
NAME = ora. diskmon
TYPE = ora. diskmon. type
ACTION_SCRIPT =
ACTIVE_PLACEMENT = 0
AUTO_START = never
CHECK_INTERVAL = 20
DESCRIPTION = "Resource type for Diskmon"
FAILOVER_DELAY = 0
FAILURE_INTERVAL = 3
FAILURE_THRESHOLD = 5
HOSTING_MEMBERS =
PLACEMENT = balanced
RESTART_ATTEMPTS = 10
SCRIPT_TIMEOUT = 60
START_TIMEOUT = 60
STOP_TIMEOUT = 60
UPTIME_THRESHOLD = 5S
[Grid @ vm11gr2]/home/grid>
The reason is basically found here. We can see that the AUTO_START attribute of these two resources is set to never by default, that is, they will not start automatically with the startup of the HAS service, by default, the HAS service is automatically started upon startup. okay, let's start it manually:
[Grid @ vm11gr2]/home/grid>Crsctl start resource ora.css d
CRS-2672: Attempting to start 'ora.css d' on 'vm11gr2'
CRS-2679: Attempting to clean 'ora. diskmon 'on 'vm11gr2'
CRS-2681: Clean of 'ora. diskmon' on 'vm11gr2' succeeded
CRS-2672: Attempting to start 'ora. diskmon 'on 'vm11gr2'
CRS-2676: Start of 'ora. diskmon' on 'vm11gr2' succeeded
CRS-2676: Start of 'ora.css d' on 'vm11gr2' succeeded
[Grid @ vm11gr2]/home/grid>

Note: ora.css d and ora. diskmon services are dependent on each other.

[Grid @ vm11gr2]/home/grid>Crs_stat-t
Name Type Target State Host
--------------------------------------------------------------
Ora. FLASH_DATA.dg ora. diskgroup. type OFFLINE vm11gr2
Ora. SYS_DATA.dg ora. diskgroup. type OFFLINE vm11gr2
Ora. asm ora. asm. type OFFLINE vm11gr2
Ora.css d. type ONLINE vm11gr2
Ora. diskmon ora. diskmon. type ONLINE vm11gr2
[Grid @ vm11gr2]/home/grid>
Css service up, restart asm instance

[Grid @ vm11gr2]/home/grid>Sqlplus "/as sysasm"

SQL * Plus: Release 11.2.0.1.0 Production on Sun Oct 25 10:30:03 2009

Copyright (c) 1982,200 9, Oracle. All rights reserved.

Connected to an idle instance.

SQL>Startup
ASM instance started

Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>Exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-Production
With the Automatic Storage Management option
[Grid @ vm11gr2]/home/grid>Crs_stat-t
Name Type Target State Host
--------------------------------------------------------------
Ora. FLASH_DATA.dg ora. diskgroup. type ONLINE vm11gr2
Ora. SYS_DATA.dg ora. diskgroup. type ONLINE vm11gr2
Ora. asm ora. asm. type ONLINE vm11gr2
Ora.css d. type ONLINE vm11gr2
Ora. diskmon ora. diskmon. type ONLINE vm11gr2
[Grid @ vm11gr2]/home/grid>

Tips

1) by default, HAS (High Availability Service) is automatically started. You can use the following command to cancel or enable automatic start.
Crsctl disable has
Crsctl enable has
2) HAS manual Start and Stop
Crsctl start has
Crsctl stop has
3) view the HAS status
Crsctl check has
4)if you want to enable the ora.css and ora. diskmon services to automatically start with HAS, you can use the AUTO_START attribute of the two services.
Crsctl modify resource "ora.css d"-attr "AUTO_START = 1"
Or
Crsctl modify resource "ora. diskmon"-attr "AUTO_START = 1"
5. If you want to cancel the Auto start of ora.css and ora. diskmon
Crsctl modify resource "ora.css d"-attr "AUTO_START = never"
Crsctl modify resource "ora. diskmon"-attr "AUTO_START = never"