Bursting Report Not Working After Upgrade To BI Publisher 184.108.40.206 (from 220.127.116.11)
(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.
Bursting report not working after upgrade to BI Publisher 18.104.22.168 from 22.214.171.124.
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 126.96.36.199) 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 188.8.131.52 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 184.108.40.206, 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?
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