OWB Repository Browser - Execution Job Report Very Very Slow

Question

Dear All,
I have tried searching the Oracle Forum, but could not find any threads with above problems, would like to check if there are other gurus who can help with above issue:
We are currently monitoring our ETL Jobs with Repository Browser (10GR2) and found the Repository Browser excruciatingly slow. The first screen for the Execution Summary Report shows up pretty fast, however whenever we want to drill further inthe Execution Job Reports, it takes almost 20 Minutes for the next screen to pop-up, and when we drill into the Process Flow Details it is another 20-40 Minutes.
We have tried the following but it does not work:
1) Purging the audit details to only 1-2 days audit data
2) Re-analyzing all tables belonging to OWB_REPO_OWNER

Answer 1

In Metalink:
Subject: Poor performance of RAB Runtime Audit Browser
Doc ID: Note:389800.1 Type: PROBLEM
Last Revision Date: 30-AUG-2006 Status: PUBLISHED
In this Document
Symptoms
Cause
Solution
Applies to: Oracle Warehouse Builder - Version: 10.2.0
This problem can occur on any platform.
SymptomsRAB shows poor performance. CauseThe problem has been tracked to the view definition for WB_RTV_EXECUTION_STORES.
The table function that is used in that view is causing the performance degradation.
Bug 5498665: REPOSITORY BROWSER TOO SLOW : PERF PROBLEM WITH INTERNAL VIEW
SolutionReplace the view wb_rtv_execution_stores.
SQL> connect <owb_unified_repository>/<password>
SQL> create or replace view wb_rtv_execution_stores
as
select
audit_execution_id,
task_object_store_uoid as store_uoid
from
wb_rt_audit_executions
where
task_object_store_uoid is not null and
task_object_store_uoid <> '{0}'
union select
audit_execution_id,
execution_store_uoid as store_uoid
from
wb_rt_audit_executions
where
execution_store_uoid is not null and
execution_store_uoid <> '{0}'
union select
audit_execution_id,
execution_object_store_uoid as store_uoid
from
wb_rt_audit_executions
where
execution_object_store_uoid is not null and
execution_object_store_uoid <> '{0}';
Regards
Detlef