Re: Confirming Database is Down on Windows
From: Jared Still <jkstill_at_gmail.com>
Date: Wed, 11 Mar 2009 11:22:19 -0700
Message-ID: <bf46380903111122o4008828er1380690774230856_at_mail.gmail.com>
On Wed, Mar 11, 2009 at 10:42 AM, Charlotte Hammond < charlottejanehammond_at_yahoo.com> wrote:
Date: Wed, 11 Mar 2009 11:22:19 -0700
Message-ID: <bf46380903111122o4008828er1380690774230856_at_mail.gmail.com>
On Wed, Mar 11, 2009 at 10:42 AM, Charlotte Hammond < charlottejanehammond_at_yahoo.com> wrote:
>
> Simply connecting doesn't confirm it either: I get an "ORA-01034 ORACLE
> not available" if I try to connect (even as SYS) to a database doing a
> transactional shutdown, even though the users who are doing the transactions
> are still merrily working away.
>
I'm confused as to why this is insufficient.
eg. If my database monitor cannot connect to the database, I am going to investigate. It doesn't matter at that time if the listener has died, or a 'shutdown' was issued and users are still working away, it should still be investigated IMO.
Maybe a little more background as to what you are trying to accomplish is in order.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 11 2009 - 13:22:19 CDT