E-BIP/OAS: OAS2024: BI Publisher not Able to Schedule a Report or Open Report Jobs after Upgrade to OAS 7.6
(Doc ID 3031407.1)
Last updated on OCTOBER 21, 2024
Applies to:
BI Publisher (formerly XML Publisher) - Version 5.6.3 and laterInformation in this document applies to any platform.
Symptoms
OAS2024: BI Publisher not able to schedule a report and also not able to open Report Jobs after In-place upgrade from OAS 6.4 to OAS 7.6
The scheduler diagnostic page shows -
However, quartz2-config.properties is present and found under <BI_DOMAIN_HOME>/config/fmwconfig/biconfig/bipublisher/Admin/Scheduler/
The issue can be reproduced at will with the following steps:
------------------------------------------------------------------
1. Perform OAS In-place Upgrade from OAS 6.4 to OAS2024.
2. Login to xmlpserver - home page - Click on Report Job. Received error "Your session has expired. Click OK to log in again"
Error: java.lang.NullPointerException
at jsp_servlet._schedule.__jobinfo._jspService(__jobinfo.java:589)
3. Click on Report to schedule, enter the details submit the job is showing an error as below:
ServletException: HTTP Status: 500, Servlet name: /schedule/jobInfo.jsp, Request URI: /xmlpserver/schedule/jobInfo.jsp, Exception Msg: java.lang.NullPointerException, Exception Type: javax.servlet.ServletException
oracle.xdo.service.scheduling.SchedulingException: Error initializing quartz. Check Scheduler Diagnostics page for more details.
at oracle.xdo.service.scheduling.DummySchedulingService.<init>(DummySchedulingService.java:22)
at jsp_servlet._schedule.__jobinfo._jspService(__jobinfo.java:474)
BI Server logs shows:
[bi_server1] [ERROR] [] [oracle.bi.majel.dxd.svs] [tid: pool-35-thread-1] [userId: <anonymous>] [ecid: d4e0ce11-e58b-451f-a48f-39a64c1ce49a-000000ae,0] [APP: bi-majel-application] [partition-name: DOMAIN] [tenant-name: GLOBAL] DATAWATCH TRIGGER HAS FAILED BECAUSE OF: java.lang.NullPointerException[[
at oracle.bi.majel.dxd.svs.DataWatchTrigger.getCPUsPerNode(DataWatchTrigger.java:86)
Changes
Upgrade to OAS 7.6.
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |