ASM Instance Showing Down In 11g Grid Control With Error ORA-15000
(Doc ID 1276657.1)
Last updated on FEBRUARY 14, 2022
Applies to:
Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]Information in this document applies to any platform.
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 the 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:
Changes
Monitoring configuration is set to use the SYSASM role for the instance SYS user.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |