Oracle 11gR2 RAC Database使用emca配置集群dbconsole

前端之家收集整理的这篇文章主要介绍了Oracle 11gR2 RAC Database使用emca配置集群dbconsole前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
下面的步骤详细的说明了在Oracle 11gR2 RAC Database环境下使用emca配置集群dbconsole遇到的部分问题及解决方法

1.数据库环境。
@H_403_5@@H_403_5@
Oracle Exadata Machine x4-2@H_403_5@
Oracle RAC Database 11.2.0.4.6 for Linux x86_64bit@H_403_5@
[root@dm01db01 ~]# uname -r@H_403_5@
2.6.39-400.126.1.el5uek@H_403_5@

2.使用EMCA创建EM。
@H_403_5@@H_403_5@
[root@dm01db01 ~]# su - oracle@H_403_5@
[oracle@dm01db01 ~]$emca -config dbcontrol db -repos create -cluster@H_403_5@@H_403_5@
......@H_403_5@
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor@H_403_5@
收到ORA-12514报错。@H_403_5@
emca工具输出的日志被存放在$GRID_BASE/cfgtoollogs/emca目录下。@H_403_5@
查看/u01/app/grid/cfgtoollogs/emca/emca_2014_06_18_10_26_50.log日志:@H_403_5@
Jun 18,2014 10:27:17 AM oracle.sysman.emcp.util.GeneralUtil initsqlEngineRemotely@H_403_5@
CONFIG: sqlEngine connecting with Service Name: +ASM,oracleHome: /u01/app/11.2.0.4/grid,and user: ASMSNMP scan name: dm01-scan scan port: 1521@H_403_5@
WARNING: Error during db connection : ORA-12514: TNS:listener does not currently know of service requested in connect descriptor@H_403_5@
CONFIG: Waiting for 5 second before reconnection@H_403_5@
sqlEngineRemotely@H_403_5@
403_5@
CONFIG: sqlEngine created successfully and connected@H_403_5@
403_5@
CONFIG: Setting param: CONFIRMATION ANSWER value:@H_403_5@
403_5@
CONFIG: Setting param: CONFIRMATION ANSWER value: no@H_403_5@
从最后面的日志可以看出,报ORA-12514错误的原因是不能通过SCAN LISTENER连接到ASM实例,说明ASM实例没有向SCAN LISTENER动态注册。@H_403_5@
3.ASM实例向SCAN LISTENER动态注册
@H_403_5@@H_403_5@
[root@dm01db01 ~]# su - grid@H_403_5@
[grid@dm01db01 ~]$ sqlplus / as sysasm@H_403_5@
sql*Plus: Release 11.2.0.4.0 Production on Wed Jun 18 23:18:09 2014@H_403_5@
Copyright (c) 1982,2013,Oracle. All rights reserved.@H_403_5@
Connected to:@H_403_5@
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production@H_403_5@
With the Real Application Clusters and Automatic Storage Management options@H_403_5@
sql> show parameter spfile@H_403_5@
NAME TYPE@H_403_5@
------------------------------------ ---------------------------------@H_403_5@
VALUE@H_403_5@
------------------------------@H_403_5@
spfile string@H_403_5@
+DBFS_DG/cluster-clu1/asmparam@H_403_5@
eterfile/registry.253.84996746@H_403_5@
5@H_403_5@
sql> show parameter remote@H_403_5@
remote_listener string@H_403_5@
remote_login_passwordfile string@H_403_5@
EXCLUSIVE@H_403_5@
remote_os_authent boolean@H_403_5@
FALSE@H_403_5@
remote_os_roles boolean@H_403_5@
sql> alter system set remote_listener='dm01-scan:1521';@H_403_5@
System altered.@H_403_5@
sql> alter system register;@H_403_5@
@H_403_5@
sql> show parameter remote_listener@H_403_5@
NAME @H_403_5@ TYPE@H_403_5@
dm01-scan:1521@H_403_5@
sql> exit@H_403_5@
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production@H_403_5@
[grid@dm01db01 ~]$ lsnrctl status listener_scan1@H_403_5@
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 18-JUN-2014 23:19:09@H_403_5@
Copyright (c) 1991,102); font-family:"Courier New"; font-size:16px">Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))@H_403_5@
STATUS of the LISTENER@H_403_5@
------------------------@H_403_5@
Alias LISTENER_SCAN1@H_403_5@
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production@H_403_5@
Start Date 17-JUN-2014 12:25:14@H_403_5@
Uptime 1 days 10 hr. 53 min. 55 sec@H_403_5@
Trace Level off@H_403_5@
Security ON: Local OS Authentication@H_403_5@
SNMP OFF@H_403_5@
Listener Parameter File /u01/app/11.2.0.4/grid/network/admin/listener.ora@H_403_5@
Listener Log File /u01/app/11.2.0.4/grid/log/diag/tnslsnr/dm01db01/listener_scan1/alert/log.xml@H_403_5@
Listening Endpoints Summary...@H_403_5@
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_SCAN1)))@H_403_5@
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.3.16)(PORT=1521)))@H_403_5@
Services Summary...@H_403_5@
Service "+ASM" has 2 instance(s).@H_403_5@
Instance "+ASM1",status READY,has 1 handler(s) for this service...@H_403_5@
Instance "+ASM2",102); font-family:"Courier New"; font-size:16px">Service "tequdb" has 2 instance(s).@H_403_5@
Instance "tequdb1",102); font-family:"Courier New"; font-size:16px"> Instance "tequdb2",102); font-family:"Courier New"; font-size:16px">The command completed successfully@H_403_5@
4.再次使用EMCA创建EM。
@H_403_5@@H_403_5@
[oracle@dm01db01 ~]$ emca -config dbcontrol db -repos create -cluster@H_403_5@
STARTED EMCA at Jun 18,2014 11:19:44 PM@H_403_5@
EM Configuration Assistant,Version 11.2.0.3.0 Production@H_403_5@
Copyright (c) 2003,2011,102); font-family:"Courier New"; font-size:16px">Enter the following information:@H_403_5@
Database unique name: tequdb@H_403_5@
Service name: tequdb@H_403_5@
Listener port number: 1521@H_403_5@
Listener ORACLE_HOME [ /u01/app/11.2.0.4/grid ]:@H_403_5@
Password for SYS user: @H_403_5@
Password for DBSNMP user: @H_403_5@
Password for SYSMAN user: @H_403_5@
Cluster name: cluster-clu1@H_403_5@
Email address for notifications (optional):@H_403_5@
Outgoing Mail (SMTP) server for notifications (optional):@H_403_5@
ASM ORACLE_HOME [ /u01/app/11.2.0.4/grid ]:@H_403_5@
ASM port [ 1521 ]:@H_403_5@
ASM username [ ASMSNMP ]:@H_403_5@
ASM user password: @H_403_5@
-----------------------------------------------------------------@H_403_5@
You have specified the following settings@H_403_5@
Database ORACLE_HOME ................ /u01/app/oracle/product/11.2.0.4/dbhome_1@H_403_5@
Database instance hostname ................ Listener ORACLE_HOME ................ /u01/app/11.2.0.4/grid@H_403_5@
Listener port number ................ 1521@H_403_5@
Cluster name ................ cluster-clu1@H_403_5@
Database unique name ................ tequdb@H_403_5@
Email address for notifications ...............@H_403_5@
Outgoing Mail (SMTP) server for notifications ...............@H_403_5@
ASM ORACLE_HOME ................ /u01/app/11.2.0.4/grid@H_403_5@
ASM port ................ 1521@H_403_5@
ASM user role ................ SYSDBA@H_403_5@
ASM username ................ ASMSNMP@H_403_5@
Do you wish to continue? [yes(Y)/no(N)]: y@H_403_5@
403_5@
INFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/tequdb/emca_2014_06_18_23_19_44.log.@H_403_5@
403_5@
INFO: Creating the EM repository (this may take a while) ...@H_403_5@
WARNING: ORA-28003: password verification for the specified password Failed@H_403_5@
ORA-20006: Password too simple@H_403_5@
403_5@
SEVERE: Error creating the repository@H_403_5@
INFO: Refer to the log file at /u01/app/oracle/cfgtoollogs/emca/tequdb/emca_repos_create_.log for more details.@H_403_5@
403_5@
Refer to the log file at /u01/app/oracle/cfgtoollogs/emca/tequdb/emca_2014_06_18_23_19_44.log for more details.@H_403_5@
Could not complete the configuration. Refer to the log file at /u01/app/oracle/cfgtoollogs/emca/tequdb/emca_2014_06_18_23_19_44.log for more details.@H_403_5@
这个告警参考如下MOS文章:@H_403_5@
EMCA: RepManager Fails With Password Verification Error ORA-28003 (文档 ID 779098.1)@H_403_5@
修改时间:@H_403_5@ 2013-10-23@H_403_5@ 类型:@H_403_5@ PROBLEM@H_403_5@

In this Document@H_403_5@

Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.@H_403_5@@H_403_5@

APPLIES TO:

Enterprise Manager Base Platform - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]@H_403_5@
Information in this document applies to any platform.@H_403_5@
Checked for relevance on 22-Oct-2013@H_403_5@ @H_403_5@

SYMPTOMS

While using EMCA to create DB Console repository,this fails with:

CONFIG: ORA-28003: password verification for the specified password Failed
ORA-20003: Password should contain at least one \

CAUSE

This is treated in internal BUG 4195090.

SOLUTION

a) Disable the Password verification
b) Create the Repository
c) Enable the password verification.

Note: For disabling the password verification function,Note 114930.1can be used. For example:

sql> alter profile default limit password_verify_function null;

5.禁用密码验证函数
@H_403_5@@H_403_5@
[oracle@dm01db01 ~]$ sql@H_403_5@
sql*Plus: Release 11.2.0.4.0 Production on Wed Jun 18 23:29:28 2014@H_403_5@
With the Partitioning,Real Application Clusters,Automatic Storage Management,OLAP,@H_403_5@
Data Mining and Real Application Testing options@H_403_5@
sql> set linesize 200@H_403_5@
sql> set pagesize 200@H_403_5@
sql> select * from dba_profiles where profile='DEFAULT';@H_403_5@
PROFILE RESOURCE_NAME RESOURCE LIMIT@H_403_5@
------------------------------ -------------------------------- -------- ----------------------------------------@H_403_5@
DEFAULT COMPOSITE_LIMIT KERNEL UNLIMITED@H_403_5@
DEFAULT SESSIONS_PER_USER KERNEL UNLIMITED@H_403_5@
DEFAULT cpu_PER_SESSION KERNEL UNLIMITED@H_403_5@
DEFAULT cpu_PER_CALL KERNEL UNLIMITED@H_403_5@
DEFAULT LOGICAL_READS_PER_SESSION KERNEL UNLIMITED@H_403_5@
DEFAULT LOGICAL_READS_PER_CALL KERNEL UNLIMITED@H_403_5@
DEFAULT IDLE_TIME KERNEL UNLIMITED@H_403_5@
DEFAULT CONNECT_TIME KERNEL UNLIMITED@H_403_5@
DEFAULT PRIVATE_SGA KERNEL UNLIMITED@H_403_5@
DEFAULT Failed_LOGIN_ATTEMPTS PASSWORD 10@H_403_5@
DEFAULT PASSWORD_LIFE_TIME PASSWORD UNLIMITED@H_403_5@
DEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITED@H_403_5@
DEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITED@H_403_5@
DEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD VERIFY_FUNCTION_11G@H_403_5@
DEFAULT PASSWORD_LOCK_TIME PASSWORD 1@H_403_5@
DEFAULT PASSWORD_GRACE_TIME PASSWORD 7@H_403_5@
16 rows selected.@H_403_5@
sql> alter profile default limit password_verify_function null;@H_403_5@
Profile altered.@H_403_5@
6.使用EMCA创建EM。
@H_403_5@@H_403_5@
403_5@
403_5@
INFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/tequdb/emca_2014_06_18_23_30_26.log.@H_403_5@
403_5@
403_5@
INFO: Repository successfully created@H_403_5@
403_5@
INFO: Uploading configuration data to EM repository (this may take a while) ...@H_403_5@
403_5@
INFO: Uploaded configuration data successfully@H_403_5@
403_5@
INFO: Propagating /u01/app/oracle/product/11.2.0.4/dbhome_1/oc4j/j2ee/OC4J_DBConsole_dm01db01_tequdb to remote nodes ...@H_403_5@
403_5@
INFO: Propagating /u01/app/oracle/product/11.2.0.4/dbhome_1/oc4j/j2ee/OC4J_DBConsole_dm01db02_tequdb to remote nodes ...@H_403_5@
403_5@
INFO: Propagating /u01/app/oracle/product/11.2.0.4/dbhome_1/dm01db01_tequdb to remote nodes ...@H_403_5@
403_5@
INFO: Propagating /u01/app/oracle/product/11.2.0.4/dbhome_1/dm01db02_tequdb to remote nodes ...@H_403_5@
403_5@
INFO: Securing Database Control (this may take a while) ...@H_403_5@
403_5@
INFO: Starting Database Control (this may take a while) ...@H_403_5@
403_5@
INFO: Database Control started successfully@H_403_5@
INFO: >>>>>>>>>>> The Database Control URL is https://dm01db01.tequ.com:1158/em <<<<<<<<<<<@H_403_5@
403_5@
INFO:@H_403_5@
**************** Current Configuration ****************@H_403_5@
INSTANCE NODE DBCONTROL_UPLOAD_HOST@H_403_5@
---------- ---------- ---------------------@H_403_5@
tequdb dm01db01 dm01db01.tequ.com@H_403_5@
tequdb dm01db02 dm01db01.tequ.com@H_403_5@
403_5@
WARNING:@H_403_5@
************************ WARNING ************************@H_403_5@
Management Repository has been placed in secure mode wherein Enterprise Manager data will be encrypted. The encryption key has been placed in the file: /u01/app/oracle/product/11.2.0.4/dbhome_1/dm01db01_tequdb/sysman/config/emkey.ora. Ensure this file is backed up as the encrypted data will become unusable if this file is lost.@H_403_5@
***********************************************************@H_403_5@
Enterprise Manager configuration completed successfully@H_403_5@
FINISHED EMCA at Jun 18,2014 11:46:24 PM@H_403_5@
成功创建EM。@H_403_5@
7.重新启用密码验证函数
@H_403_5@@H_403_5@
sql> alter profile default limit password_verify_function VERIFY_FUNCTION_11G;@H_403_5@
sql> select * from dba_profiles;@H_403_5@
配置完成后检查是否能够正常的登录EM工具,另外还有两点需要注意:@H_403_5@
1).emca是用操作系统oracle用户执行的。@H_403_5@
2).不能使用IP地址访问EM工具,一定使用机器名访问,例如:https://dm01db01.tequ.com:1158/em@H_403_5@

同时这篇文章也是对《@H_403_5@构建最高可用Oracle数据库系统:Oracle 11gR2 RAC管理、维护与性能优化@H_403_5@》的10.6.2小节的补充和完善。@H_403_5@


@H_403_5@

来源:http://blog.itpub.net/23135684/viewspace-1188673/@H_403_5@@H_403_5@

猜你在找的Oracle相关文章