RMAN异库恢复之EM(3)

emctl start dbconsole 启动 failed. 查看日志 .
1./oracle/database/product/10.2.0/db_1/dbserver_testdb1/sysman/log 13:50 $cat emagent.trc
2011-02-11 11:08:51 Thread-4135864000 ERROR http: snmehl_allocateListenerPort: failed to bind socket: 地址已在使用 (errno=98)
2011-02-11 11:08:51 Thread-4135864000 ERROR http: nmehl_startHttpListener: failed to listen to HTTP port for http://dbserver:3938/emd/main
2011-02-11 11:08:51 Thread-4135864000 ERROR main: nmehl_startHttpListener failed starting http listener

2./oracle/database/product/10.2.0/db_1/dbserver_testdb1/sysman/log 13:46 $cat emoms.log
2011-02-11 11:07:26,277 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ias.ias.IASIntegration
2011-02-11 11:07:26,519 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.eml.target.slb.common.SLBIntegration
2011-02-11 11:07:26,598 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.eml.ssl.intg.SSLIntegration
2011-02-11 11:07:26,690 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.tip.oem.central.domain.ProcessConnectDomainIntg
2011-02-11 11:07:26,691 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.tip.oem.central.instance.ProcessConnectInstanceIntg
2011-02-11 11:07:26,693 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.webdb.admin.em.PortalIntegration
2011-02-11 11:07:26,694 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.webdb.admin.em.SSOIntegration
2011-02-11 11:07:26,695 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.reports.em.RepIntg
2011-02-11 11:07:26,697 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsEmailIntegration
2011-02-11 11:07:26,700 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOidIntegration
2011-02-11 11:07:26,702 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOvfIntegration
2011-02-11 11:07:26,703 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWebconfIntegration
2011-02-11 11:07:26,705 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWirelessIntg
2011-02-11 11:07:26,706 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsCalGrpIntegration
/oracle/database/product/10.2.0/db_1/dbserver_testdb1/sysman/log 13:46 $

emagent.trc  说3938端口已经被占用.按照 failed to bind socket:  这个关键句到 metalink里搜.找到如下解决方法.尝试了下.然后将agent进程kill掉.重创建em.生效

Grid Control Agent Startup Fails With ' failed to bind socket: Address already in use' Error [ID 746857.1]
		Modified 09-APR-2010     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

---

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.5 - Release: 10.2 to 10.2
Information in this document applies to any platform.

Symptoms

When installing Management Agent 10.2.0.4, it fails at the Configuration Assistant screen with the following error:

After exiting from Configuration Assistant screen, attempting to start the Agent displays the following error:

The /sysman/log/emagent.trc file contains the following error:

The following checks were carried out but did not resolve the issue:

1. Checked for incorrect/inconsistent hostname and/or IP configuration for server /etc/hosts file or DNS. See Note 427842.1

2. Checked ORACLE_HOSTNAME environment variable does not conflict with actual hostname.

3. Checked port used by the Agent is not being used by another application. See Note 443524.1
Agent port is not used by another application, however, netstat output displays many network connections in TIME_WAIT status.  

Cause

The Agent by default listens on more than one NIC.

Solution

References

NOTE:422296.1 - Unable to start agent after transferring package from one node to other on a MC/ServiceGuard cluster
NOTE:427842.1 - Problem: Grid Control Installation - "Failed to allocate free Enterprise Manager Central Console Port"
NOTE:443524.1 - Grid Control Agent Startup Fails with "Failed to Start HTTP Listener" Error

Related Products Enterprise Management > Enterprise Manager Consoles, Packs, and Plugins > Enterprise Manager Grid Control > Enterprise Manager Grid Control Enterprise Management > Enterprise Manager Consoles, Packs, and Plugins > Enterprise Manager Grid Control > Enterprise Manager Grid Control Keywords HTTP LISTENER; STARTUP FAILS; MANAGEMENT AGENT; ADDRESS ALREADY IN USE; SOCKET; EMCTL START AGENT; EMAGENT.TRC; ENTERPRISE MANAGER

Back to top

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/11780477/viewspace-687012/，如需转载，请注明出处，否则将追究法律责任。