My Oracle Support Banner

Oracle Fusion BI Publisher: BI Publisher report jobs stuck in Running status after BI bounce or patching (Doc ID 2388668.1)

Last updated on MAY 14, 2018

Applies to:

Oracle Fusion Application Toolkit Cloud Service - Version 11.12.1.0.0 to 11.12.1.0.0 [Release 1.0]
Information in this document applies to any platform.

Symptoms

The BI Report Jobs are stuck in Running status after the BI Server gets bounced or patched. This in turn corrupts the JMS configuration page as shown in the following page:

1. Login to BI Analytics

2. Click on Administration

3. Manage BI Publisher

4. Click on Scheduler Diagnostics page.

1) Check the BI Publisher Administration → Scheduler Diagnostics page. If JMS configuration shows critical and the following messages, then you are hitting this issue:

Enterprise Scheduler Critical Open jms_cluster_config file failed: ConfigProvider is not available.
   --JMS Critical Open jms_cluster_config file failed: ConfigProvider is not available.
      ----JMS Cluster Config /u01/APPLTOP/instance/BIShared/BIPublisher/repository/Admin/Scheduler/jms_cluster_config.properties 

                     Critical Open jms_cluster_config file failed: ConfigProvider is not available.
             ------JMS_PROVIDER_TYPE Critical No JMS is selected.

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.