Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
BIP Report produces output when bursting is not selected, when bursting selected no output

We have an odd issue with a report with bursting that suddenly has stopped working. The report output is produced when the report is scheduled without the bursting option. When the bursting option is selected, there is no output - however, clicking the XML link shows report data. The xml confirms that the 'key' is present and matches the bursting 'key'.
Diagnostics do not help to identify the issue.
Any ideas? Is this a common issue?
Answers
-
When a layout for the full report is used with bursting, it usually as to be modified to work with the bursting subset of data.
Rgds,
Kevin
0 -
The report/bursting worked before, but has suddenly stopped. Not sure what has happened. The report output has a key column with static data populated '1'. The bursting sql is based on the following (obfuscated here):
SELECT '1' KEY
,'xxxx' TEMPLATE
,:xdo_user_report_locale LOCALE
,'csv' OUTPUT_FORMAT
,'FTP' DEL_CHANNEL
,'xxxx.csv' OUTPUT_NAME
,'username' PARAMETER1
,'pw' PARAMETER2
,'' PARAMETER3
,'/ftpdir' PARAMETER4
,'xxxx.csv' PARAMETER5
,'true' PARAMETER6
FROM DUALThe above has worked before on the same report.
0 -
What error are you seeing in he Job History page?
Rgds,
Kevin
0 -
This is the error:
Waiting Time: 0.8 seconds
Data Fetch Time: 0.2 seconds
Total Execution Time: 0.4 seconds
Job Priority: Normal
Waiting Time: 0.8 seconds
Data Fetch Time: 0.2 seconds
Total Execution Time: 0.4 seconds
Job Priority: Normal
Job processor caused exception
[INSTANCE_ID=bip.bi_serverHA] [INSTANCE_JOB_ID=1308368]
DATA_PROCESSING_FAILED
[INSTANCE_ID=bip.bi_serverHA]
There is no data to process
[INSTANCE_ID=bip.bi_serverHA] oracle.xdo.servlet.scheduler.ProcessingException:
There is no data to process
[INSTANCE_ID=bip.bi_serverHA]
at oracle.xdo.enterpriseScheduler.bursting.BurstingDataProcessor.process(BurstingDataProcessor.java:329)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.execute(BurstingJobProcessor.java:622)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobP
Thanks.
0 -
That indicates an issue with the output of the bursting query.
Test the bursting query using a dumy data model.
Rgds,
Kevin
0 -
The bursting query does work, I checked that separately on a paas db.
This is an odd one; thanks for helping.
Kind regards
0 -
Your results and the query do not match.
You should have only one bursted result using select '1' as "KEY".
Kevin
0 -
The burst query only produces one row. Not sure what else you could mean.
0 -
Your job history answer looked like there were three results.
Try diagnostics, report and data engine.
Then review your diagnostics log.
Rgds,
Kevin
0 -
Diagnostics Log entry for the query:
Total Number Of Rows Processed:15Diagnostics Log entry for the bursting query:
Bursting sql output size = [1] rows.Query does have data for KEY - values:'1'. Bursting is done on '1' key.
The error message suggests that there is no data to process:
[052925_083844425][][STATEMENT] !!!!!!! BurstingDataProcessor.process :: Data processor failed::[INSTANCE_JOB_ID=1308348]::NO_DATA_TO_PROCESS::[INSTANCE_ID=bip.bi_server1] oracle.xdo.servlet.scheduler.ProcessingException: ::NO_DATA_TO_PROCESS::[INSTANCE_ID=bip.bi_server1] at oracle.xdo.enterpriseScheduler.bursting.BurstingDataProcessor.process(BurstingDataProcessor.java:329) at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.execute(BurstingJobProcessor.java:622) at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.onMessage(BurstingJobProcessor.java:240) at oracle.xdo.enterpriseScheduler.util.CheckpointEnabledListener.onMessage(CheckpointEnabledListener.java:26) at oracle.xdo.enterpriseScheduler.jmswrapper.client.JMSMessageConsumer.processMessage(JMSMessageConsumer.java:276) at oracle.xdo.enterpriseScheduler.jmswrapper.client.ThreadedMessageDispatcherOpt$DispatchWorker.run(ThreadedMessageDispatcherOpt.java:146) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:842) !!!!!!!
However, as shown above, the report query produces 15 rows (verified by the XML output that I can download via the link on the job history).0