Database Tuning (MOSC)

MOSC Banner

SYSAUX growing out of control and filled up

edited Feb 27, 2019 2:51PM in Database Tuning (MOSC) 5 commentsAnswered

Hi

My SYSAUX have grown out of proportion.

I attempted to manually drop via "exec dbms_workload_repository.drop_snapshot_range(low_snap_id => 1, high_snap_id=>&&v_snap_id);"  but that backfired  when it took 3 days and filled up my UNDO ( 70Gb ) . I had to cancel but had to wait 2 days for rollback while I got snapshot to old errors.

Is there a way to partition the culprit tables and indexes by hand and then drop those partitions or is it better to drop and recreate the SYSAUX via the two scripts in the .../rdbms/admin/

Some articles say I can do do the following ?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center