Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

BIP Bursting issue

Received Response
73
Views
5
Comments

Summary

BIP Bursting issue

Content

Hi,

We are trying to implement bursting on our BIP report. When we are scheduling the report, we are seeing the error message as below

"oracle.xdo.servlet.scheduler.ProcessingException: Error getting report data"

Below is the bursting SQL we have used.

select Distinct(EmailID) KEY,

'Allocated-Commingled_Template' as TEMPLATE,

'RTF' TEMPLATE_FORMAT,

'en-US'  LOCALE,

'PDF'  OUTPUT_FORMAT,

'EMAIL'  DEL_CHANNEL,

EmailID  PARAMETER1,

'<1234@oracle.com>' PARAMETER2,

'<1234@oracle.com>' PARAMETER3,

'Subject: Your Invoices'  PARAMETER4,

'Hi'  PARAMETER5,

'true'  PARAMETER6,

'donotreply@mycompany.com'  PARAMETER7

from BIP_POC_DataModel

Can some one help with this?

Answers

  • Sherry George
    Sherry George Rank 7 - Analytics & AI Coach

    I assume the BIP report runs fine when bursting is not used, in that case does the bursting definition posted run successfully if run from SQL client like SQL Developer?

  • Sherry George
    Sherry George Rank 7 - Analytics & AI Coach

    Why are you querying from DUAL, isn't BIP_POC_DataModel a table? Is your data model created using SQL query?

    Edit: The "BIP_POC_DataModel' should be a table you can query (OBIEE SA or a database table/view) and it should not be the name of the dataset.

  • Sainath K
    Sainath K Rank 3 - Community Apprentice

    And BIP is working fine without the Bursting definition.

  • Sainath K
    Sainath K Rank 3 - Community Apprentice

    Hi George,

    Thanks for your response.

    That SQL is working fine in SQL developer when we are firing the Query on Dual table.

    The 'EmailID' that we are giving as Parameter1 is a column from our data model. Not sure if it is getting loaded.

    Thanks

  • Sainath K
    Sainath K Rank 3 - Community Apprentice

    Hi George,

    We have created a Physical database table and this resolved the issue.


    Thank you so much!