ASM Instance Showing Down In 11g Grid Control With Error ORA-15000

ASM Instance Showing Down In 11g Grid Control With Error ORA-15000 [ID 1276657.1]

 

Symptoms

ASM 11.2
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0

ASM shows down in Grid Control . The collection error for status metric is :
ORA-15000: command disallowed by current instance type (DBD ERROR: OCISessionBegin)

select * from v$pwfile_users;

USERNAME SYSDB SYSOP SYSAS
------------------------------ ----- ----- -----
SYS TRUE TRUE TRUE
ASMSNMP TRUE FALSE FALSE

Testing the connection as follows it's working:

sqlplus sys/<password>@"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myasmhost)(Port=1521))(CONNECT_DATA=(SERVICE_NAME=+ASM1)(INSTANCE_NAME=+ASM1)(UR=A)))" as sysdba;

sqlplus sys/<password>@"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myasmhost)(Port=1521))(CONNECT_DATA=(SERVICE_NAME=+ASM1)(INSTANCE_NAME=+ASM1)(UR=A)))" as sysasm;

sqlplus ASMSNMP/<password>@"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myasmhost)(Port=1521))(CONNECT_DATA=(SERVICE_NAME=+ASM1)(INSTANCE_NAME=+ASM1)(UR=A)))" as sysdba;

emagent_perl.trc shows:

dbGetAdrHome.pl: Thu Oct 14 18:52:33 2010: WARN: get_diag_info_from_db: Could not connect to sys/(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOS
T=myasmhost)(Port=1521))(CONNECT_DATA=(SERVICE_NAME=+ASM1)(INSTANCE_NAME=+ASM1)(UR=A))): ORA-15000: command disallowed by current insta
nce type (DBD ERROR: OCISessionBegin)


Changes

Monitoring configuration is set to use the SYSASM role for the instance SYS user.

Cause

There is no support in the JDBC driver used by EM Agent to handle SYSASM connections.
Bug 5883719: PROVIDE SYSASM SUPPORT IN JDBC THIN

Also, there is no requirement or need or recommendation to use the SYSASM role in the ASM monitoring configuration. SYSDBA role is enough for monitoring the instance (more in note 977472.1). SYSASM role is used for administrating the ASM, not monitoring it.

Solution

Use SYSDBA role instead SYSASM role in Monitoring Configuration with: go to the ASM home page -> click on Monitoring Configuration link -> Change the role to SYSDBA -> test the connection and submit the change.