My Oracle Support Banner

OBIEE 11g: Scheduler Component Fails To Start (Doc ID 2090967.1)

Last updated on DECEMBER 08, 2019

Applies to:

Business Intelligence Server Enterprise Edition - Version to [Release 11g]
Information in this document applies to any platform.


The BI Scheduler component stays in "Init" status for a long time and after 5-10 minutes it changes to down and following messages are present in your nqscheduler and opmn log.

nqscheduler.log : In scheduler log below scheduler database connectivity message is present and there is no error message present in scheduler log but still scheduler does not come up.

[OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [<ECID>] [tid: 40f7c940] [16020] Metadata Database Type: Oracle 11g [[
Data Source Type: Oracle Database 11g Enterprise Edition Release - 64b

opmn.log : In opmn log there are scheduler ping failure error messages are captured

[opmn] [ERROR:1] [] [libopmncustom] Process Ping Failed: coreapplication_obisch1~OracleBISchedulerComponent~coreapplication_obisch1~1 (<Host>:<Port>) [No addresses matched the properties for the request]
[opmn] [ERROR:1] [] [libopmncustom] Process Ping Failed: coreapplication_obisch1~OracleBISchedulerComponent~coreapplication_obisch1~1 (<Host>:<Port>)
[opmn] [ERROR:1] [] [libopmncustom] Ping failed in Ready callback for proc:<Process>




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.