Re: Confirming Database is Down on Windows
Date: Wed, 11 Mar 2009 13:31:13 -0700 (PDT)
I need to know for sure the database is DOWN rather than just not accessible to new connections, as I want to ensure it is safe to run a cold backup.
Messy background: We have a whole bunch of (noarchivelog) development databases in another country - unfortunately due to complex politics, time zones, geography etc., we do the backups but the developers control startup/shutdown times according to their work patterns. I know this sounds chaotic but mostly the schedule is regular.
However we'd like to know if the databases are truly down before starting a cold backup - and we can't just force them shut as when they are left up, they are left up for good reason. It's often not easy to contact the developers to find out what's going on, so we'd like a reliable and quick check of databases being down and ready for backup (like grep'ing ps for pmon and smon etc. as we do on unix).
From: Jared Still <jkstill_at_gmail.com> To: charlottejanehammond_at_yahoo.com
Sent: Wednesday, March 11, 2009 6:22:19 PM Subject: Re: Confirming Database is Down on Windows
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.
Certifiable Oracle DBA and Part Time Perl Evangelist