Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: shutdown abort and database consistency

Re: shutdown abort and database consistency

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Wed, 10 Jul 2002 18:55:14 +0100
Message-ID: <1026324409.256.0.nnrp-10.9e984b29@news.demon.co.uk>

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>...

>
>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 --
Received on Wed Jul 10 2002 - 12:55:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US