Error Eml.omshandshake Processfailure.806 - Omshandshake Failed
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How can I change the connection descriptor used by Oracle Enterprise Manager? up vote 2 down vote favorite I've recently changed the SERVICE_NAME of my 11g database and Enterprise Manager can no longer connect to it: 2014-01-08 10:36:06,047 [HTTPThreadGroup-3] ERROR eml.OMSHandshake processFailure.806 - OMSHandshake failed.(AGENT URL = https://Test9.lab.nyc-14.knoa.com:3938/emd/main)(ERROR = INTERNAL_ERROR)(CAUSE =java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor The Connection descriptor used by the client was: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=Test9.lab.nyc-14.knoa.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=test9.lab.nyc-14.knoa.com))) ) The SERVICE_NAME in there is indeed the old one. I've updated NETWORK\ADMIN\tnsnames.ora but that didn't fix it. Where does Enterprise Manager read the connection descriptor from? oracle oracle-11g-r2 share|improve this question asked Jan 8 '14 at 15:41 Bogdan Calmac 11115 Have you changed the listener.ora on the DB server? –Philᵀᴹ Jan 8 '14 at 15:57 listener.ora does not seem to have a SERVICE_NAME. As far as I know, the DB server dynamically registers its service name with the listener at startup. –Bogdan Calmac Jan 8 '14 at 16:01 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote I'm guessing because you haven't specified what version of OEM you're using. If you're using OEM 12C, go to the DB home then click on "Oracle Database", "Target Setup", "Monitoring Configuration". You can change the SID there. share|improve this answer answered Jan 8 '14 at 16:06 Phil Sumner 1,256312 I'm using 11g R2. The problem is with the SERVICE_NAME, not the SID. Also in the O
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Enterprise Manager All PlacesEnterprise Manager http://dba.stackexchange.com/questions/56372/how-can-i-change-the-connection-descriptor-used-by-oracle-enterprise-manager This discussion is archived 4 Replies Latest reply on Sep 16, 2011 6:24 AM by GBA Problem with Oracle DbConsole user8302582 Sep 15, 2011 8:28 AM I change a sysman password, and change the emd and target xml file. But this service not https://community.oracle.com/thread/2286337 start the error in the em.log is 2011-09-15 10:16:11,731 [HTTPThreadGroup-57] ERROR eml.OMSHandshake processFailure.806 - OMSHandshake failed.(AGENT URL = https://DL380G7.int.extraco.es:3938/emd/main)(ERROR = INTERNAL_ERROR)(CAUSE =java.sql.SQLException: ORA-01017: nombre de usuario/contraseña no válidos; conexión denegada ) 2011-09-15 10:16:21,730 [HTTPThreadGroup-91] ERROR conn.ConnectionService verifyRepositoryEx.891 - Invalid Connection Pool. ERROR = ORA-01017: nombre de usuario/contraseña no válidos; conexión denegada 2011-09-15 10:16:31,777 [HTTPThreadGroup-87] ERROR conn.ConnectionService verifyRepositoryEx.891 - Invalid Connection Pool. ERROR = ORA-01017: nombre de usuario/contraseña no válidos; conexión denegada 2011-09-15 10:16:41,792 [HTTPThreadGroup-88] ERROR eml.OMSHandshake processFailure.806 - OMSHandshake failed.(AGENT URL = https://DL380G7.int.extraco.es:3938/emd/main)(ERROR = INTERNAL_ERROR)(CAUSE =java.sql.SQLException: ORA-01017: nombre de usuario/contraseña no válidos; conexión denegada ) 2011-09-15 10:16:51,823 [HTTPThreadGroup-87] ERROR conn.ConnectionService verifyRepositoryEx.891 - Invalid Connection Pool. ERROR = ORA-01017: nombre de usuario/contraseña no válidos; conexión denegada 2011-09-15 10:17:01,791 [HTTPThreadGroup-91] ERROR eml.OMSHandshake processFailure.806 - OMSHandshake failed.(AGENT URL = ht
it has been changed and we now have to use the emctl command. After changing the hostname http://www.pafumi.net/OEM%20Reinstalling%20Procedure.html or IP address, EM dbconsole port, instance SID, or even TZ settings, EM is going to fail. Example to Re-Configure to another port: Using "emca" you can http://blog.csdn.net/u011616400/article/details/41889915 reconfigure eg. the port number to 1150: Code: emca -reconfig ports -DBCONTROL_HTTP_PORT 1150 To change the listener port or the hostname of the Repository Database we now have error eml.omshandshake to use the emctl config oms command as shown below. emctl config oms -store_repos_details -repos_port 1528 -repos_sid emrep -repos_host wintest01 -repos_user SYSMAN -repos_pwd oracle11g To check what are the OMS Repository details we can use the emctl config oms -list_repos_details command. For example - D:\Oracle\Product\Middleware\oms11g\BIN>emctl config oms -list_repos_details Oracle Enterprise Manager 11g Release 1 Grid Control error eml.omshandshake processfailure.806 Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved. Repository Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=wintest01)(PORT=1528)))(CONNECT_DATA=(SID=emrep))) Repository Host : wintest01 Repository Port : 1528 Repository SID : emrep Repository User : SYSMAN The emoms.properties file actually has these lines …. ########################################################################################################### ##################################### README ########################################### ########################################################################################################### #NOTE #1. EMOMS(LOGGING).PROPERTIES FILE HAS BEEN REMOVED #2. OMS PROPERTIES / LOGGING PROPERTIES SHOULD BE MODIFIED USING EMCTL GET/SET/DELETE/LIST PROPERTY COMMANDS #3. The USAGE OF EMCTL GET/SET/DELETE/LIST PROPERTY IS PROVIDED BELOW, BUT # FOR LATEST UPDATED COMMANDS PLEASE CHECK EMCTL HELP MESSAGE In more serious cases there's only one solution - reinstallation Check the status: emca -deconfig dbcontrol 1. Change the %ORACLE_HOME%\network\admin\listener.ora file from an IP number to machine name. 2. Change the %ORACLE_HOME%\network\admin\tnsnames.ora file from an IP number to a machine name. 3. Change the C:\WINDOWS\System32\drivers\etc\hosts file by adding this line beneath the default localhost line (for the new Hostname value): 127.0.0.1 localhost 10.10.10.10 mybox mybox.acme.com 4. Change the Windows hostname by navigating: Start > Control Panel > System (cl
Enterprise Manager show database status is unavailable 2014-12-12 09:39 175人阅读 评论(0) 收藏 举报 本文章已收录于： 分类： ORACLE_基础知识（26） 作者同类文章X 版权声明：本文为博主原创文章，未经博主允许不得转载。 Enterprise Manager show database status is unavailable 查看日志：$ORACLE_HOME/lucky_orcl/sysman/log/emoms.log 2011-08-02 14:40:46,822 [HTTPThreadGroup-4] ERROR eml.OMSHandshake processFailure.806 - OMSHandshake failed.(AGENT URL = https://maclean04.oracledatabase12g.com:3938/emd/main)(ERROR = INTERNAL_ERROR)(CAUSE =java.sql.SQLException: ORA-28000: the account is locked ) 2011-08-02 14:40:48,244 [HTTPThreadGroup-4] ERROR conn.ConnectionService verifyRepositoryEx.891 - Invalid Connection Pool. ERROR = ORA-28000: the account is locked 从以上EM日志可以发现问题为ORA-28000，显然是EM相关的数据库用户被locked。10g中与EM相关的数据库用户包括SYSMAN和DBSNMP，分别查询该2个用户的状态: SQL> select account_status,lock_date,username from dba_users where username in ('SYSMAN','DBSNMP'); ACCOUNT_STATUS LOCK_DATE USERNAME -------------------------------- --------------- ------------------------------ OPEN DBSNMP LOCKED(TIMED) 02-JUL-11 SYSMAN SYSMAN用户被锁定了，状态为LOCKED(TIMED)，说明是登陆密码不正确多次登陆后被锁的。 SQL> alter user sysman account unlock; User altered. 重启EM后重新登陆，发现问题仍未解决，再次检查账户信息 SQL> select account_status,lock_date,username from dba_users where username in ('SYSMAN','DBSNMP'); ACCOUNT_STATUS LOCK_DATE USERNAME -------------------------------- --------------- ------------------------------ OPEN DBSNMP LOCKED(TIMED) 02-AUG-11 SYSMAN 发现SYSMAN用户又被locked，显然是有人在数据库内修改了SYSMAN的密码后，没有重新配置EM中的SYSMAN密码，导致每次EM启动时都会尝试用错误的密码登陆数据库，最终造成SYSMAN用户被LOCKED(TIMED)住，并出现”ORA-28000: the account is locked”错误。 找出根本原因后问题就显得十分简单了，我们只需要关闭EM，并同步数据库和EM中的SYSMAN密码