How to resolve ORA-29701: Unable to Connect to Cluster Manager -- IP address change for the server and server is rebooted.

posted May 18, 2011, 12:20 PM by Sachchida Ojha   [ updated May 23, 2011, 6:55 AM ]

I ran into ORA-29701 when I tried to start the ASM instance on va-ieng03 after Sys Admin rebooted the server. The only change that occurred was that the IP address had changed. Below you will find the steps that I followed to resolve this issue:

1. Set ORACLE_HOME to ASM

2. crsctl status resource -t
-> check if services are offline

crsctl status resource -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd 1 OFFLINE OFFLINE va-ieng03
ora.diskmon 1 OFFLINE OFFLINE va-ieng03

3. crsctl status resource –p

-> what are auto_start settings?

4. If they are offline, you can try to set the following:
crsctl status resource –p

-> what are auto_start settings?

5. Modify settings if they are not set to 1
crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"

6. Start crs
crs_start –all

7. verify that statuses changed:

crsctl status resource -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd 1 ONLINE ONLINE va-ieng03
ora.diskmon 1 ONLINE ONLINE va-ieng03


crsctl status resource -p


8. Add ASM service

srvctl add asm


9. Start ASM
srvctl start asm

10. Connect to ASM (with sys as sysasm) and mount at least one of the disk groups

11. Create temporary init.ora for ASM

"init+ASM.ora" [New file]

asm_diskgroups='RAT1_DATA','TDB1_DATA','PROD_FRA'
instance_type='asm'
large_pool_size=12M
remote_login_passwordfile='EXCLUSIVE'

12. Bounce ASM instance

13. Create spfile for ASM

14. Bounce ASM instance

15. Start DB instances

 

Comments