My Oracle Support Banner

Bursting Report Not Working After Upgrade To BI Publisher 12.2.1.3 (from 12.2.1.2) (Doc ID 2638692.1)

Last updated on FEBRUARY 13, 2020

Applies to:

BI Publisher (formerly XML Publisher) - Version 12c and later
Information in this document applies to any platform.

Goal

Bursting report not working after upgrade to BI Publisher 12.2.1.3 from 12.2.1.2.

The client setup is a complex data-model where they parse several parameters to select the data, due to the complexity of the queries it was no option to use the bursting definition on the normal database tables.


Their solution (worked perfectly in BIP 11 and BIP 12.2.1.2) was that they created an function (with autonomous transaction) which they included in their SQL-query in the datamodel. This function save all data needed to build the list for the bursting definition.

Their bursting definition is nothing more than a select of the table:
Select * from report_requests  where request_number = :p_request_number.

But the data in this table only exists AFTER the SQLQuery in the datamodel have been executed, in BIP 11 and BIP 12.2.1.2 the order was first run the datamodel and then use the query of the bursting definition.


Now it seems that this order has been changed in 12.2.1.3, First the query from the bursting definition is executed and after that the queries in the datamodel are executed.


Could you let us know how we can make sure the query from the bursting definition is executed AFTER the queries in the datamodel?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.