Tuesday, May 8, 2012

ORA-01031: insufficient privileges message during ASM start up & clusterware(ASM) refused to come up due to insufficient privilege


  •  I had made changes to sqlnet.ora file by putting a entry "SQLNET.AUTHENTICATION_SERVICES = (NONE)" (which is by default NTS). After making the change 20mins after suddenly in the DB alert log 
i got a message like "SLAVE COMMUNICATION ERROR WITH ASM ; TERMINATING PROCESS " & DB instances went down.
  • So after that i checked the ASM status from cluster which was in intermediate state.
  • So i thought of restarting cluster again, hoping it should resolve this, after doing the stop & start of cluster services. All services except the ASM
came up giving the error message "Insufficient Privilege to start" even though i was doing as root privilege.

  • After that i thought of starting ASM instances manually but this also throws the error "ORA-01031: insufficient privileges message" . So finding no other way
i thought of first raising a SR with ORACLE & lost nearly 2 hrs by collecting diagnostics information and uploading them but didn't get ant reply for SR
  • After this did some search and came to know this happened due to the entry in the SQLNET.ora file. So reverted the change.

Resolution:

Go to the SQLNET.ora file and remove the entry for "SQLNET.AUTHENTICATION_SERVICES=(NONE)" it should be set to default i.e. (NTS)

No comments:

Post a Comment