Report sometimes running for indefinite when using bom explode function
We have a Report usually running around 50mins, but sometimes it can run for 5hrs or more, we have to kill it. The report will run a package bompexpl.explosion_report, and query the result.
When the report run 5hrs or more, we will killed it, and bounce the DB. The report will run as normal, ard 50mins.
We noticed that it may due to the archived log switch, this will happened.
Is it when performing huge bompexpl.explosion_report that using the temporary table, and at the moment archived log switch happened, will cause this issue?