Unexpected growth of a RBS

[maguila]

I have a data base with 12 RBS's, one of them have 2177 extents, 2169 extends, 2205 wraps and it have grown more than 200 times the size of the other RBS's, is this normal?, a colleague made a big move to copy a great amount of rows from a MS Access data base to a table of that data base.

Thank you

[OracleDoc]

You've kind of answered your own question.
"Your colleague made a big move". Chances are he didn't specify a commit after every 500 or so rows, therefore causing one big transaction which made your rollback segment grow. Just be glad you had enough extents specified and room in your tablespace otherwise you'd get a snapshot too old error. You can go into OEM and shrink it back down.

[Mr.Hanky]

Yet another developer in need of a serious smack down.
Commits R GuD, commits R yor freind!

[gandolf989]

Originally posted by Mr.Hanky
Yet another developer in need of a serious smack down.
Commits R GuD, commits R yor freind!

That's a gross over simplification of this situation.
But then gross is your specialty.

It is possible to get snapshot too old for committing too often. PL/SQL Collections are a great way to get around snapshot too old.

[Mr.Hanky]

SPARE ME THE EXCUSES AND USE A COMMIT DEVELOPER BOY!!

[Dosth]

IS that the best solution ? Or should be it be creating a bigger rollback segment say large get the transaction sorted and get the new large rbs offline ... ?

[cruser3]

IMHO - it should be an optimization of both - RBS size and code i.e commits, collections - u should achive a balance based on your transaction actvity !

[gandolf989]

Originally posted by Mr.Hanky
SPARE ME THE EXCUSES AND USE A COMMIT DEVELOPER BOY!!

Yet another gross over simplification.
Way to go McPoo.

When to commit depends on the situation.
There is no one size fits all solution to this problem.

[Mr.Hanky]

See above!

If it is growing X200, you need a commit, plain and simple.
Or you need to break the job up into mangable segments, same difference.

[gandolf989]

Originally posted by Mr.Hanky
See above!

If it is growing X200, you need a commit, plain and simple.
Or you need to break the job up into mangable segments, same difference.

Yes it does need incremental commits to work well. However, my comment was related to your comment not the issue at hand. I should have been more specific.