Saturday 13 June 2015

OHS12c: Admin port conflict issue while configuring the new instance.

  • There are 2 options available while installing OHS.
    • Collocated HTTP Server
    • Standalone HTTP Server
  • At the time of configure OHS, below screen appear in the middle of configurations. 

  • In the above screen, we should not use Weblogic Server Admin & Port information. This is specific to OHS Configurations and have to use local sever info (other than Weblogic Admin Server Port). 
  • If we use Admin server info & if already Admin Sever is running then will get below error stack ( If we start OHS Instance).
    • [2015-06-12T04:22:23.3124-04:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [e_sock: could not bind to address 10.25.11.10:7001
    • [2015-04-12T04:22:23.3124-04:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [worker.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [ shutting down
    • [2015-04-12T04:22:23.3124-04:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: My_OHS_Server1] [host_addr: 10.25.11.6] [pid: 25178] [tid: 140568266618688] [user: oracle ..
  • Make sure have other port info other than Admin server info. 
  • If you have already used Admin info then try to modify the configuration at OHS configuration files and start OHS instance.

Finally OHS instance will come into normal state.


No comments:

Post a Comment