You have 2 issues you want to correct here. Issue one is:
'Thread 1 cannot allocate new log, sequence 44' . See
</code>
http://asktom.oracle.com/pls/asktom/f?p=100:11:::::P11_QUESTION_ID:69012348056 <code>for the cause and the solution.
The other more troubling error (troubling because it prevents things from taking place whereas the cannot allocate new log just means they take longer to complete) is the
ORA-1650: unable to extend rollback segment RBS02 by 16 errors. That means whatever operation was being done at that point in time failed and was rolled back (if you got these during the run of initjvm -- it failed, you'll need to rerun it after correcting).
Having sufficient rollback is
critical for the database. Don't shortchange it.
Start with at least a couple (5 say) rollback segments whose
initial=next=1m and
minextents=25, maxextents=150. I like to put each rollback segment into its own tablespace with its OWN autoextensible datafile. This allows each rollback segment to grow when needed (if the OS has room) and allows me to shrink any of the rollback segments back down to 25megs when I want to and shrink the corresponding datafile as well (i do this before backups for example). In this fashion, I let the rollback grow upto 150m (but no more -- really really huge transactions will still fail but I want them to -- you might not).
We do not switch to a new rollback segment when one fills up (that describes our behaviour with redo, not undo). We fail the transaction that was taking place and roll it back. This is an error you really don't want to see.