Anyone going to try it ?

Whilst investigating my SYSMAN tablespace problem, I came across the following footnote on metalink regarding table occupancy in the AWR…

NOTE: This will NOT free space in the various tables of the AWR. It will simply delete rows in them which can be used by future AWR snapshots. There is no supported way to release the storage owned by these tables. To limit the size of the SYSAUX tablespace, you can simply disable the autoextend from its datafile(s). When it fills up, the AWR will automatically delete older data and reuse their space.

Whilst this is comforting to know, I was wondering why my Advisor tasks were failing when this space should be recycled.

**********************************
(3) Advisor Tasks With Errors – Last 50
**********************************

OWNER/ADVISOR TASK_ID/NAME CREATED EXE_DURATN EXE_CREATN HOW_C STATUS
————– ——————————– —————- ———- ———- —– ————
TASK_DESC
————————————————————————————————————–
ERROR_MSG
————————————————————————————————————–
RDCREPORT/SQL 70061/RDCSNAP_0phx0w0tv6nub 10:00:01 (09/10) 1,010 1,395 CMD FATAL ERROR
Description: RDCSNAP Tuning task for statement 0phx0w0tv6nub
Error Msg : ORA-30032: the suspended (resumable) statement has timed out
ORA-01653: unable to extend table SYS.WRI$_ADV_SQLT_PLANS by 128 in tablespace SYSAUX

RDCREPORT/SQL 70066/RDCSNAP_24x4mq5uzdv3z 11:00:03 (09/10) 948 953 CMD FATAL ERROR
Description: RDCSNAP Tuning task for statement 24x4mq5uzdv3z
Error Msg : ORA-30032: the suspended (resumable) statement has timed out
ORA-01653: unable to extend table SYS.WRI$_ADV_SQLT_PLANS by 128 in tablespace SYSAUX

I’m a little bit worried about testing it on a production database at this time…

This entry was posted in Enterprise Manager, Oracle and tagged , , , , . Bookmark the permalink.