BI Publisher (MOSC)

MOSC Banner

BIP not sending HTTP notification on bursting job where sql query produces no results

edited Mar 19, 2015 8:52AM in BI Publisher (MOSC) 7 commentsAnswered ✓

Hi,

We have identified a possible bug in BI Publisher. Would it be possible to verify?

We are scheduling a report with bursting using the web-services API, which will notify our web application via HTTP notification when the job is finished. It has both a standard SQL and a Bursting SQL statement that splits up the report on client ID.

If the SQL in the datamodel returns no rows, the job fails (which is fine because you can't split output that doesn't exist). However, information on job success/failure is NOT BEING SENT via HTTP.

This means our web application is never notified of the job having failed. Instead it appears that the job is "still running" because no notification has been sent. This looks like a special case bug that is not being handled by BIP: a notification of job failure should always be sent via HTTP regardless on what the failure is caused by.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS BI Publisher Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center