Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: fast growing RBSs
How to stop an Oracle database (used to work on version 6, but haven't checked it for years).
i) Find out how many rollback segments there are
ii) Run up that many sessions
iii) In each session do a single row update to a small table
iv) Check that each transaction has attached to a different RBS
v) Do not commit, walk away
The rollback segments won't be able to wrap, and eventually they will extend to the limit of the tablespace or their maxextents.
--
Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
Joseph T wrote in message <7romf8$p2p$1_at_nnrp1.deja.com>...
>Yes, it is odd. We were on Oracle 8.0.5.0 on AIX; we've since gone to
>8.0.5.1. I don't know if the problem persists. The work-around is
>still in place. I didn't report it to Oracle.
>
>I suppose it is possible that there were uncommitted transactions. It's
>been quite some time, and I don't quite remember all of the details.
>
Received on Wed Sep 15 1999 - 13:53:13 CDT
![]() |
![]() |