BI Publisher (MOSC)

MOSC Banner

Bursting Report To File System Behaving Strangely

edited Apr 8, 2015 10:03AM in BI Publisher (MOSC) 1 commentAnswered

Hi Everyone,

There is no issue when the main query has a where condition as rownum < 100.


When the WHERE clause is removed or main query is run without the condition, the below error is observed in the xdo.log file =>


[030415_090940388][][STATEMENT] ToplinkDataHandler.getOutput() : called

[030415_090940388][][STATEMENT] Default read connection pool max:20, min:10, total:10, available:10

[030415_090940389][oracle.apps.xdo.servlet.scheduler.XDOJob][EXCEPTION] [ID:29651] Unexpected exception occurred while running the job.

oracle.apps.xdo.servlet.scheduler.ProcessingException: java.lang.NullPointerException

    at oracle.apps.xdo.servlet.scheduler.XDOJob.runBurstingReport(XDOJob.java:2184)

    at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:372)

    at org.quartz.core.JobRunShell.run(JobRunShell.java:195)

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