Oracle Analytics Publisher

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Publisher

Categories

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

'No output available' with Report Status 'Success'

Accepted answer
574
Views
8
Comments
MarkPescatrice
MarkPescatrice Rank 2 - Community Beginner
in Oracle Analytics Publisher

I have a notification (BIP report) that I am testing in Prod, which is a copy of one we are using in Prod. It is scheduled to run every 30 minutes. When it completes with a status of Success, there is no output generated for my test notification. If I click 'Republish' the report output appears on the report output page.

image.png

I am guessing there is something wrong with the bursting definition, but I cannot figure this out. The data model Properties are identical (except for name, of course). The schedules are identical, down to the second. The data set is slightly different (I am testing a fix) and the bursting SQL query appears to be accurate.

The Report Job Name I am using is 'MJP Move to HR Notification Fix Test', which is used in the where clause of the data set and bursting query.

Z_NEM_MOVED_TO_HR_NOTIF_DM.xdm.catalog
Z_NEM_MOVED_TO_HR_NOTIF_REPORT.xdo.catalog

I'm at a loss, as I have looked at everything. What could I be missing in my troubleshooting? I have scoured MOS, CCC, and followed the https://docs.oracle.com/cd/E21764_01/bi.1111/e18862/T527073T555155.htm guide.

Thanks in advance for your assistance!

Tagged:

Best Answer

  • MarkPescatrice
    MarkPescatrice Rank 2 - Community Beginner
    Answer ✓

    Thank you @Kevin M-Oracle and @Mallikarjuna Kuppauru-Oracle , I truly appreciate the help. I had verified the bursting option before, so that wasn't the root cause.

    However, I found the solution to my problem, which was user error, of course. Maybe this helps someone else, but I compared the Data Model SQL to the Bursting SQL and found there was a slight difference. I corrected that and it resolved my problem.

    I am guessing that a best practice is this: assure that your Data Model query matches the query within the bursting definition.

Answers

  • Kevin M-Oracle
    Kevin M-Oracle Rank 6 - Analytics Lead

    The job history does not show split-by or deliver-by, it does not look like Bursting was enabled for the test.

    Rgds,

    Kevin

  • MarkPescatrice
    MarkPescatrice Rank 2 - Community Beginner

    Thanks for the quick response, @Kevin M-Oracle . I didn't notice that, but good call out. However, the split by and deliver by are both defined the same for both data models (the working and non-working versions).

    image.png

    I'm not sure what else I'm missing. Should I try to recreate the data model and see if this resolves the issue?

  • Kevin M-Oracle
    Kevin M-Oracle Rank 6 - Analytics Lead

    In the report properties, you have to check the box for bursting and select the bursting query.

    Rgds,

    Kevin

  • Mallikarjuna Kuppauru-Oracle
    Mallikarjuna Kuppauru-Oracle Rank 8 - Analytics Strategist

    Hi @MarkPescatrice

    You can check below check box .

    image.png

    Regards,

    Arjun

  • User_E9CUB
    User_E9CUB Rank 1 - Community Starter

    HI @Kevin M-Oracle @Mallikarjuna Kuppauru-Oracle

    We are facing similar issue where as Bursting is enabled. Report completed 'Success' Still We are getting 'No output available', however when we republish we can able to see the output.

    Because of this, couldn't burst the report. Could you please help here.

    Thanks

    Manoj

  • Kevin M-Oracle
    Kevin M-Oracle Rank 6 - Analytics Lead

    Trouble shoot the Bursting query, is it returning valid delvery datasets?

    Does the layout work with the bursting subset of data (split-by)?

    Rgds,

    Kevin

  • User_R6TYD
    User_R6TYD Rank 1 - Community Starter

    HI all,

    We are also facing same issue sometimes whenever we do any query changes it doesn't work as expected even bursting is enabled at reporting level.