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

Last updated on AUGUST 09, 2017

Applies to:

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

Symptoms

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: 0059iZTabp20rmcLxio2yW0007uK000003,0] [tid: 40f7c940] [16020] Metadata Database Type: Oracle 11g [[
Data Source Name: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx.xx.com)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=xxx)))
Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 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 (xxxxxxxxx:32404) [No addresses matched the properties for the request]
[opmn] [ERROR:1] [] [libopmncustom] Process Ping Failed: coreapplication_obisch1~OracleBISchedulerComponent~coreapplication_obisch1~1 (xxxxxxxxx:32404)
[opmn] [ERROR:1] [] [libopmncustom] Ping failed in Ready callback for proc:xxxxxxxxx

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms