ORA-24300 When Configuring GC Agent to monitor 11g ASM [ID 977472.1]
来源:互联网 发布:上海华腾软件面试 编辑:程序博客网 时间:2024/05/20 06:22
ORA-24300 When Configuring GC Agent to monitor 11g ASM [ID 977472.1]
修改时间 05-OCT-2011 类型 PROBLEM 状态 PUBLISHED
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.
When an attempt to use the SYSDBA role is made ORA-1031 is returned.
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:
For 11gR1 follow the procedure below to create the ASM password file:
After creating/validating the password file entries and existence:
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 inBUG 9190006 and is the recommended configuration.
修改时间 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.2Information 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
BUG 9190006Solution
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 inBUG 9190006 and is the recommended configuration.
References
BUG:9190006 - ORA-24300 WHEN ATTEMPTING TO SYSASM ROLE FOR MONITORING 11GR2 ASM- ORA-24300 When Configuring GC Agent to monitor 11g ASM [ID 977472.1]
- ASM INSTANCE CRASHES FREQUENTLY WITH ORA-15082 in 11g [ID 1056695.1]
- RAC ASM instances crash with ORA-29702 when multiple ASM instances start(ed) [ID 733262.1]
- Higher 'direct path read' Waits in 11g when Compared to 10g (Doc ID 793845.1)
- Oracle 11g dataguard asm to asm
- ORA-15221 11gR2 (11.2.0.1) Unable To Create ASM Spfile Standalone (文档 ID 1082332.1)
- 11g ASM New Feature [ID 429098.1]
- 11g RAC to 单实例 dataguard ASM TO ASM
- oracle 11g R2 单实例 ASM 启动:ORA-29701:+unable+to+connect+to+Cluster+Synchronization+Service
- oracle 11g R2 单实例 ASM 启动:ORA-29701:+unable+to+connect+to+Cluster+Synchronization+Service
- Configuring JDeveloper 11g to use Struts 2
- ASMCA fails to create 11.2 ASM instance when upgrading from 10.2 [ID 1125053.1]
- ORA-01078 ORA-29701 11g单机asm系统启动后不能启动asm
- 11g单实例使用ASM监听出现ORA-12537
- oracle 11g ASM 的管理用户 asm shutdown immediate ORA-01031: insufficient privileges
- ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
- ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
- Alert: Querying v$asm_file Gives ORA-15196 After ASM Was Upgraded From 10gR2 To 11gR2 with an AU size > 1M [ID 1145365.1]
- 60 数据是核心
- Liferay6.0.5中WebContent编辑的一个bug
- Linux Shell编程入门
- ubuntu server 10.04 网卡丢失或不能联网
- mobile项目 GenerateResource任务意外失败 或 设计界面打不开
- ORA-24300 When Configuring GC Agent to monitor 11g ASM [ID 977472.1]
- 智能指针
- 性能测试需求分析
- jQuery Ajax中文乱码问题
- 数据结构——2路归并排序
- VC中判断目录,文件是否存在,创建目录的方法
- 关于eas 单据中有多个分录的情况下,默认是哪个实现了排序
- WP7 实现Listbox中长按弹出ContextMenu效果,获取选中的ListBoxItem
- Ant 开发