Planning BI Publisher Scheduled Reports

Mtripath-Oracle

Description

BI Publisher Reports run on scheduled and ad-hoc basis on the BI Server. 

These reports can have large data volume and can run for long periods of time.

Reports consume system resources ( DB/ File storage etc) and sometimes the servers can become overloaded to due heavy traffic.

This idea proposes to mitigate the situation by providing a tool on Bi Publisher, which

--helps in providing information to user about anticipated load when the report will be run

--give and idea about run times based on prior executions of the report

--advise the user about potential run windows to mitigate jobs traffic

Use Case and Business Need

--Due to large reports being run on a daily basis, users may need help in submitting the jobs at appropriate times 

--The jobs plan provides customer windows into the load on the system and advises them when the appropriate window may be

--The tool will help to plot the report run times based on intelligent computation of resources derived from past runs

--Helps in reducing peak loads and data hot spots

More details

--Currently, the users can submit jobs, however, since there is no global view of the anticipated work load, many large volume reports may be fired at ones.

--It is possible to exceed system capacity under this situation.

--This can lead to run time issues like OOM/stuck threads etc

 

Original Idea Number: 23eccf01b8