Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: shutdown abort and database consistency
I think you could test this one by doing a very large insert into a table with a couple of indexes. Then abort the database before the commit.
Then, on the restart, do
SELECT /*+ full(t) */ COUNT(*) from tablet T; and watch the redo and undo fly.
-- Jonathan Lewis http://www.jlcomp.demon.co.uk Next Seminars UK July / Sept Australia July / August Malaysia September USA (MI) November http://www.jlcomp.demon.co.uk/seminar.html Mark D Powell wrote in message <178d2795.0207100732.29d3ba74_at_posting.google.com>...Received on Wed Jul 10 2002 - 12:55:14 CDT
>
>Howard, you were right to point out that only those blocks that a new
>transaction accesses would be rolled back by the new transaction and
>not all remaining unrolled back blocks from the original transaction.
>But this brings up the interesting question of if you run the same SQL
>and the rollback has not yet taken place could your second transaction
>end up having to rollback every block affected by the original
>transaction? And in a situation like this what would be the
>likelihood of a 'snapshot too old' from delayed block cleanout?
>
>-- Mark D Powell --