| ORA-24300 When Configuring GC Agent to monitor 11g ASM [ID 977472.1] | |||||
|
|
|||||
|
修改时间 05-OCT-2011 类型 PROBLEM 状态 PUBLISHED |
|||||
Applies to:
Enterprise Manager for Oracle Database - Version: 11.1.0.6 to 11.2.0.1 - Release: 11.1 to 11.2
Information in this document applies to any platform.
When configuring an 11gR1 or 11gR2 ASM target in Enterprise Manager Grid Control 10gR5 (10.2.0.5) using the sysasm role ORA-24300 is raised and the target configuration is unable to continue.
Symptoms
When configuring the Grid Control monitoring credentials for 11g (11gR1 or 11gR2) ASM using SYSASM role the connection test fails with "DiskGroup_Usage - ORA-24300: bad value for mode".
When an attempt to use the SYSDBA role is made ORA-1031 is returned.
NOTE: The SYSASM role is not the recommended configuration from a security and privilege perspective for monitoring due to its super user types of privileges.
Changes
None.
Cause
Solution
First make sure that there is a password file for the ASM instance being configured. On Unix/Linux this password file will be under $ORACLE_ASM_HOME/dbs, on Windows this password file will be under %ORACLE_ASM_HOME%/dbs.
If the password file does NOT exist, you must first create the password file to avoid ORA-1031 errors.
For 11gR2 follow the procedure below to create the ASM password file:
1. Create the password file for ASM on all nodes (if RAC) as follows:
orapwd file=$GRID_INFRASTRUCTURE_HOME/dbs/orapw+ASM password=<password> entries=5
2. Update the password file with the following users/roles:
sqlplus / as sysasm
SQL> create user asmsnmp identified by
SQL> grant sysasm to sys;
SQL> grant sysdba to asmsnmp;
3. Review changes to the password file by querying v$pwfile_users:
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
--------- ----- ----- -----
SYS TRUE TRUE TRUE
ASMSNMP TRUE FALSE FALSE
For 11gR1 follow the procedure below to create the ASM password file:
1. Create the password file for ASM on all nodes (if RAC) as follows:
orapwd file=$ORA_ASM_HOME/dbs/orapw<ASM_SID> password=<password> entries=5
2. Update the password file with the following users/roles:
sqlplus / as sysdba
SQL> grant sysasm to sys;
3. Review changes to the password file by querying v$pwfile_users:
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
--------- ----- ----- -----
SYS TRUE FALSE TRUE
After creating/validating the password file entries and existence:
NOTE: The SYSASM role is not the recommended configuration from a security and privilege perspective for monitoring due to its super user types of privileges.
Within Grid Control configure the agent monitoring credentials for the ASM instance(s) target to connect to the ASM instance(s) as asmsnmp (11gR2) or sys (11gR1) with the role of SYSDBA. This will avoid the ORA-24300 error described in
BUG 9190006 and is the recommended configuration.
References
BUG:9190006 - ORA-24300 WHEN ATTEMPTING TO SYSASM ROLE FOR MONITORING 11GR2 ASM