After clearing checks can generate the past execution plans for
WRH $_SQL_TEXT also have the same problem, and can be regenerated, is never traced to
Because there are too many take up the SYSAUX tablespace

CodePudding user response:

This theory does not affect

CodePudding user response:

No effect, but to standardize the operation,
These WRH $_ who runs AWR are listed in the table at the beginning of the base table, who runs AWR report is generated, the amount of space depends on who runs AWR retention time and fine-grained 7 days (the default), a few cases are not automatic cleaning, this part of the space only by manual or truncate partition table way of recycling,
Some of them are the partition table, can clear the partition directly; All non-partitioned tables can only be cleared; Of course, the most important is to reduce who runs AWR retention time, otherwise will rise up again in a few days,
Detailed steps can refer to: "clean up the Oracle who runs AWR base table truncate WRH $"

CodePudding user response:

Empty, no impact, dropped the associative table also qing together,

CodePudding user response:

refer to the original poster ruanjianxuqiu126 response:

after clearing checks can generate the past execution plans for
WRH $_SQL_TEXT also have the same problem, and can be regenerated, is never traced to
Because there are too many occupy SYSAUX tablespace

Deleted don't ah, can affect some historical performance data, such as: who runs awr and its associated SQL plan,