Rollback Segments growing... 911!!!

[THoey]

I have a table that gets loaded with approximately 300K of records each day. Normally I have a script that deletes records that are more than two weeks old, but it was disabled last month to collect some extra data.

Now, I am going through and cleaning up that table, putting it back to the two week limit. Since there are so many records to delete, I am doing it one day at a time, so that I don't over load the rollback segments. I delete a days worth of records and then do a commit. I thought this would free up space in the rollback segments, but using Oracle Storage Manager, I see that the size just keeps growing. The size of the available rollback segment is 1 gig and it is currently filled to 670 meg. I can increase the available size, but this doesn't seem right.

Is there a setting I need to use to free up this space upon a commit or am I just wrong in my understanding of this?

Any help soon would be greatly appreciated as I have another 8 days worth of data to delete.

Thanks in advance...

Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?

 

[THoey]

BTW, that was 300,000+ records loaded every day, not 300K of records...


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?

 

[MikeLacey]

Terry,

Isn't there an option to shrink an rbs in storage manager?

Mike
michael.j.lacey@ntlworld.com

http://www.cargill.com/

 

[THoey]

I think I finally ended up solving this by restarting Oracle. Went from 800M to 400M. Of course this is just a temp fix. I will look into "shrinking" on Monday...

Thanks Mike...

Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?