Analytics Software

Here is my Configuration:
OracleBI Discoverer 10g (10.1.2.3)
Oracle Business Intelligence Discoverer Plus 10g (10.1.2.55.26)
Discoverer Model - 10.1.2.55.26
Discoverer Server - 10.1.2.55.26
End User Layer - 5.1.1.0.0.0
End User Layer Library - 10.1.2.55.26
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
Copyright © 1999, 2005, Oracle. All rights reserved.


First of all, Disco scheduling in Plus works fine in our production instance. In our test instance, I have a user whom wants to schedule workbooks from time to time where a new folder is being tested. My problem is that when I am on step two of the schedule wizard and I select immediate (or manually place a time in that is very soon (e.g. 5 minutes from now)), the workbook took hours yesterday to show as “scheduled” in the “Managed Scheduled Workbooks” tool.
Today it works fine and runs immediately. I created a very simple workbook titled, "scheduling test", which has one column, a calculation which is set to sysdate. I began testing this yesterday.

Does any thoughts on what is causing this trouble?

I did the following:
1. I notice that a package is created in the scheduling schema for the workbook scheduled.
2. I tried to query for scheduled jobs created by dbms_job (queried Dba_Jobs using the system account and could not find the job...either yesterday or today).
3. I tried to query v$sql with the intent of seeing when the package, batch_rep_secure.submit_job,is executed...but could not find the scheduled records.
4. I tried gleaning information from the "Manage Scheduled Workbooks" tool associated with the Disco Administrator, and the time column was null (yesterday).
5. I had our dba check the init<sid>.ora file and confirmed that the job_queue_processes have been set to 10.

To rectify this yesterday, I just manually executed the package, EUL5_BATCH_PACKAGE10061409140713, and shortly thereafter, the scheduled workbook would have a new table associated with it which was consumable through Disco Plus.

My hunch is that our job queue was backed-up significantly yesterday and this was delaying the scheduling and running of scheduled workbooks.

Does any one have any thoughts about what the root cause was here and how I could confirm this?


Thanks,

Patrick