Re: Loooooong wait to shutdown Oracle immediate on Linux
From: joel garry <joel-garry_at_home.com>
Date: Wed, 24 Feb 2010 17:28:38 -0800 (PST)
Message-ID: <a0822837-4234-45bf-9716-6e0aaa9f9728_at_y7g2000prc.googlegroups.com>
On Feb 24, 4:01 pm, Jia Lu <roka..._at_gmail.com> wrote:
> On 2月25日, 午前1:57, joel garry <joel-ga..._at_home.com> wrote:
>
> > You might check what is attached to the db.
>
> Thanks for your answer.
> Which way do you suggest to check the db events when I did shutdown
> immediate ?
> Thank you.
Date: Wed, 24 Feb 2010 17:28:38 -0800 (PST)
Message-ID: <a0822837-4234-45bf-9716-6e0aaa9f9728_at_y7g2000prc.googlegroups.com>
On Feb 24, 4:01 pm, Jia Lu <roka..._at_gmail.com> wrote:
> On 2月25日, 午前1:57, joel garry <joel-ga..._at_home.com> wrote:
>
> > You might check what is attached to the db.
>
> Thanks for your answer.
> Which way do you suggest to check the db events when I did shutdown
> immediate ?
> Thank you.
Look at v$session and v$process, or dbconsole show sessions, before you shutdown. Also look at the processes from the OS side. You might become familiar with ways to look at undo and long running transactions. One of the main tasks of a dba is to be familiar with what your app is doing.
jg
-- _at_home.com is bogus. http://blog.sucuri.net/2010/02/godaddy-security-update.htmlReceived on Wed Feb 24 2010 - 19:28:38 CST