AWR Performance: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
* Solution 1 | * Solution 1 | ||
Reference: Oracle Support Note 2929370.1 | |||
<syntaxhighlight lang=sql> | <syntaxhighlight lang=sql> | ||
| Line 12: | Line 14: | ||
-- OR | -- OR | ||
alter session set "_optimizer_push_pred_cost_based" = false; | alter session set "_optimizer_push_pred_cost_based" = false; | ||
</syntaxhighlight> | |||
* Solution 2 | |||
Reference: Oracle Support Note 2148489.1 | |||
<syntaxhighlight lang=sql> | |||
DBMS_STATS.DELETE_SYSTEM_STATS('NOWORKLOAD'); | |||
DBMS_STATS.GATHER_SYSTEM_STATS(GATHERING_MODE => 'NOWORKLOAD'); | |||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 11:21, 13 June 2024
This article is a stub. You can help us by expanding it.
Overview
Sometimes, generating AWR reports can be very slow. This article lists some potential remedies.
- Solution 1
Reference: Oracle Support Note 2929370.1
alter session set "_push_join_predicate"=false;
-- OR
alter session set "_optimizer_push_pred_cost_based" = false;
- Solution 2
Reference: Oracle Support Note 2148489.1
DBMS_STATS.DELETE_SYSTEM_STATS('NOWORKLOAD');
DBMS_STATS.GATHER_SYSTEM_STATS(GATHERING_MODE => 'NOWORKLOAD');