Schedule Report Job Not Picking Up Bursting Definition
(Doc ID 2222369.1)
Last updated on JULY 20, 2023
Applies to:
BI Publisher (formerly XML Publisher) - Version 12.2 to 12.2 [Release 12.2]Information in this document applies to any platform.
Reviewed for relevance 21 Mar 19.
Symptoms
Schedule Report job not picking bursting definition.
When trying to schedule/submit a newly created email report, the outputs is not showing 'View bursting definition' on the schedule report job page.
But, instead it is showing 'Output1'.
Emails are not getting generated when the report is submitted.
ERROR MESSAGE in bipublisher.log file:
Error message in the bipublisher log shows a problem with the email address:
[2016-12-09T11:44:50.563-05:00] [instance] [ERROR] [] [oracle.xdo] [tid: 2836] [userId: ] [ecid: e6a2b424-9e9d-4f66-888c-987aec1b56dd-00009fa7,0:1] [APP: bipublisher] [partition-name: DOMAIN] [tenant-name: GLOBAL] oracle.xdo.XDOException: URLFactory: Protocol 'mailto' is not found.[[
at oracle.xdo.common.net.URLFactory.getURLStreamHandler(URLFactory.java:140)
at oracle.xdo.common.net.URLFactory.createURL(URLFactory.java:170)
at oracle.xdo.template.fo.util.Uri.createURL(Uri.java:171)
at oracle.xdo.template.fo.util.Uri.createURL(Uri.java:213)
at oracle.xdo.template.fo.util.Uri.getURIString(Uri.java:143)
at oracle.xdo.template.fo.area.BasicLinkArea.(BasicLinkArea.java:48)
at oracle.xdo.template.fo.elements.FOBasicLink.createAreaObject(FOBasicLink.java:53)
at oracle.xdo.template.fo.elements.FOBasicLink.doLayout(FOBasicLink.java:43)
at oracle.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:359)
at oracle.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:255)
at oracle.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:168)
at oracle.xdo.template.fo.elements.FOFlow.doLayout(FOFlow.java:111)
at oracle.xdo.template.fo.elements.FormattingEngine.startLayout(FormattingEngine.java:274)
at oracle.xdo.template.fo.elements.FormattingEngine.run(FormattingEngine.java:165)
at oracle.xdo.template.fo.FOHandler.endElement(FOHandler.java:780)
at oracle.xdo.common.xml.XSLTHandler$EEEntry.sendEvent(XSLTHandler.java:595)
at oracle.xdo.common.xml.XSLTMerger.startElement(XSLTMerger.java:51)
at oracle.xdo12c.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:182)
at oracle.xdo12c.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1635)
at oracle.xdo12c.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:458)
at oracle.xdo12c.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:404)
at oracle.xdo12c.parser.v2.XMLParser.parse(XMLParser.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at oracle.xdo.common.xml.XDOSAXParser.invokeParse(XDOSAXParser.java:300)
at oracle.xdo.common.xml.XDOSAXParser.parse(XDOSAXParser.java:149)
at oracle.xdo.template.fo.FOProcessingEngine.process(FOProcessingEngine.java:441)
at oracle.xdo.template.FOProcessor.generate(FOProcessor.java:1278)
at oracle.xdo.template.FOPWrapper.generate(FOPWrapper.java:45)
at oracle.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:168)
at oracle.xdo.servlet.CoreProcessor.process(CoreProcessor.java:667)
at oracle.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:116)
at oracle.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:1418)
at oracle.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:395)
at oracle.xdo.servlet.resources.ReportItemServiceImpl$ReportItemRunner.call(ReportItemServiceImpl.java:86)
at oracle.xdo.servlet.resources.ReportItemServiceImpl$ReportItemRunner.call(ReportItemServiceImpl.java:61)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
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 |
Cause |
Solution |