It looks like the segment-troublemaker (#5) was expanded 56 times:
initial size is 5Mb, increment size is 5Mb,optimal size set to (5*2)Mb. (56+2)*5Mb=290Mb=304087040
Maximum Number of extents (249) apparently was not reached.
My question is - why? Why ORACLE responded with "ORA-01562"?
It's obvious, that the total highwatermark size (even if it was reached at the same point in all segments) is less than 350Mb.
On the other hand, the total size available in ROLLBACK tablespace is 620Mb.
(We have 3 VSAM datasets with total 13260 TRKs on 3390 triple density DASD)
It could be possible that the rollback ts was fragmented, thus causing the extents for PRB05 to be thrown all over the ts with a bunch of free space in the ts, causing it to fail. Consider coalesing the ts before such operations and/or set Autoextend ON for the rollback ts.
Yout ORA-01562 message contains also the exact cause of the error - "ORA-01628" which has the following error message: "max # extents (string) reached for rollback segment string".
This means that your rollback segment has the above limit different that you thought it is - obviously it is not 249 as you think. Either the RB segment or the tablespace it is residing in must have been created with some MAXEXTENTS specification in the storage clause. Check the MAX_EXTENTS in DBA_ROLLBACK_SEGS.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?