Re: shutdown took a long time!

Before doing a shutdown, execute:

    select used_urec, used_ublk from v$transaction;

This shows the amount of UNDO (records and blocks) in use by transactions which are not yet committed. If you do a shutdown immediate, this is the volume of rollback that would have to take place.

If the numbers are increasing, you have a transaction which is working. If you have numbers that are decreasing you have a transaction that is already rolling back.

If the numbers are very large, you may as well do a shutdown abort, and let Oracle tidy up the mess on the next startup.

With a little experimentation, you can calibrate your system to figure out a guide figure for used_urec per second for normal operation. It will only be a rough guide though.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar - UK, April 3rd - 5th
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases


y wrote in message <3C859BF0.4A41A9DB_at_y.y>...


>Hi,

>Today, when I shutdown my oracle instance/database, it took me a long

>time.

>

>I would like to know where I should check besides alert log ?

>

>Thanks for any help!

>