Unexpected Behaviour : Sequence query of LOV executing twice in Scheduled reports
Hi,
We are facing an unexpected behavior in scheduled report. Execution fails with following run time error. Same report executes fine when it is run online.
IOException:[INSTANCE_JOB_ID=1431] Invalid parameters requested.
oracle.xdo.servlet.data.DataException: Invalid parameters requested.
at oracle.xdo.servlet.ReportException.fillInStackTrace(ReportException.java:124)
at oracle.xdo.servlet.data.DataException.fillInStackTrace(DataException.java:127)
at java.lang.Throwable.<init>(Throwable.ja
We are using a sequence to uniquely identify each report execution (scheduled or online). The sequence is queried in a LOV query and attached to a report parameter(P_QUEUEID). When I checked the trace logs, I found that sequence is generated twice. First, while report is submitted as a job(eg: 2165). Second when report starts executing(eg: 2166). Later somewhere it is trying assigning 2166 to LOV and failing as the two values do not match.
We are facing an unexpected behavior in scheduled report. Execution fails with following run time error. Same report executes fine when it is run online.
IOException:[INSTANCE_JOB_ID=1431] Invalid parameters requested.
oracle.xdo.servlet.data.DataException: Invalid parameters requested.
at oracle.xdo.servlet.ReportException.fillInStackTrace(ReportException.java:124)
at oracle.xdo.servlet.data.DataException.fillInStackTrace(DataException.java:127)
at java.lang.Throwable.<init>(Throwable.ja
We are using a sequence to uniquely identify each report execution (scheduled or online). The sequence is queried in a LOV query and attached to a report parameter(P_QUEUEID). When I checked the trace logs, I found that sequence is generated twice. First, while report is submitted as a job(eg: 2165). Second when report starts executing(eg: 2166). Later somewhere it is trying assigning 2166 to LOV and failing as the two values do not match.
0