Why Are Reports Taking Too Long to Run?

Scheduled processes based on Oracle Analytics Publisher reports might take too long to run because of something going on with the reports themselves. When users submit these processes, they're essentially running Analytics Publisher reports.

Many predefined scheduled processes are based on Analytics Publisher reports. All the custom jobs definitions that were created brand new (not created by duplicating or editing predefined job definitions) are also based on reports. Predefined or custom job definitions based on Analytics Publisher reports have the BIPJobType job type.

So if there are performance issues with the scheduled processes queue, check if there are processes based on reports that are taking too long to run, for example 30 minutes or even multiple hours. Usually that means the SQL queries are slow in fetching data. If the problematic processes are for custom reports, revisit and tune the custom reports. In general, if you have custom reports running as scheduled processes, keep an eye on them regularly to make sure they don't take too long and prevent other processes in the queue from running in a timely manner.

You should also monitor the report performance using tools from Analytics Publisher. As an administrator, you can run queries against the ESS_REQUEST_HISTORY table from Analytics Publisher. This way, you’ll know if the table is getting larger or if there are any issues such as too many submissions of certain processes.