ORA-29786: SIHA attribute GET failed with Error If 11gR2 ASM instance is created manually [ID 976075

ORA-29786: SIHA attribute GET failed with Error If 11gR2 ASM instance is created manually [ID 976075.1]

To Bottom

---

Modified:Aug 11, 2011Type:PROBLEMStatus:PUBLISHEDPriority:3

Comments (0)

In this Document
  Symptoms
  Changes
  Cause
  Solution

---

Symptoms

After creating an initial parameter file init+ASM.ora manually and starting an ASM instance, certain ASM commands fails with ORA-29786 in sqlplus:

sqlplus / as sysasm
SQL> create spfile='$ORACLE_HOME/spfile+ASM.ora' from pfile='$ORACLE_HOME/dbs/init+ASM.ora';
create spfile='$ORACLE_HOME/spfile+ASM.ora' from pfile='$ORACLE_HOME/dbs/init+ASM.ora'
*
ERROR at line 1:
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]

SQL> create diskgroup dg1 normal redundancy disk'/opt/oracle/oradata/nobilldb/DG1_dev0' disk'/opt/oracle/oradata/nobilldb/DG1_dev1';

Diskgroup created.

SQL> drop diskgroup dg1;
drop diskgroup dg1
*
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-29786: SIHA attribute GET failed with error [Attribute 'SPFILE' sts[200]
lsts[0]]

Better option to create ASM instance is to run asmca in GUI/Silent mode.

Changes

Starting with 11gR2, ASM instance is a resoure in CRS repository also in single instance installations. Hence, it must be registered to OCR before doing certain operations like create/drop diskgroup, create pfile/spfile, etc. 

Cause

ASM instance is created and started manually but it is not registered to cluster repository.

Solution

If ASM instance is created manually, add ASM instance to CRS repository with srvctl add asm:

srvctl add asm  -p $ORACLE_HOME/dbs/init+ASM.ora

srvctl add asm -h -- will give the options