Re: cannot extend RBS -- can I commit?

Depending on how the data migration is being performed you can maybe do more frequent commits.

If it is a script you can review the script and add commit at logical intervals, if data is being installed from an export file set commit=y

You can also grow the rollback segment tablespace for the purpose of this commisioning and then rebuild it after the data is consistent to a better size for normal operation. Suggest you take all but set optimal value for each RBS th be equal to the size of 2 segments, then unused rollback segments will shrink to permit the in use RBS to shrink.

hope this helps

Verna Legaspi wrote in message <84gcbo$7ks$1_at_redftp.redftp.attws.com>...
>Hi everyone,
>
>I think we've finally come to the "root cause" of our software upgrade
>problem that we've been fighting for months (VERY LONG story). It seems
the
>software upgrade that modifies our database is running out of RBS space.
>The error we're getting is ORA-01562 (Failed to extent rollback segment #)
&
>ORA-01628 (max # extents (121) reached for rollback segment)
>
>My question is -- can I just do some kind of "forced commit" so that it
>doesn't need all that RBS?
>
>TIA,
>Verna
>
>
>
Received on Fri Dec 31 1999 - 10:14:44 CST