In order to switch between undo management modes, you must shutdown and restart, so
all sessions are disconnected. Therefore, session cleanout is not the culprit.
OTS's answer does not make sense since the error is that the file can't be read, not
an ORA-1555 as I would expect if the rbs can't
they eventually said its data dictionary blocks in the old RBS, that were
having delayed block cleanout. they couldnt be cleaned out because the
tablespace was offline.
its a bug.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, January 06,
Ryan,
I agree with OTS. If you had dropped the rollback segment(s) before creating
the object then you'd probably never have seen the error. I have found that SCN's do
get cached by your session and sometimes don't get updated correctly. Therefore even
though you had switched to
I have a TAR open on this and Im arguing with the Oracle tech support guy.
Here is what happened. We upgraded an instance to 9i. Switched to automatic undo
management. Set our undo parameters to point to a newly created undo tablespace.
1. took our old rollback tablespace(with rollback
