Sure, once you have connected to the database you could get some additional information via queries if you want. But if all you want to know is "Is the database available to users?" then it should be sufficient to use SQL*Plus from a client machine to connect and disconnect.
> -----Original Message-----
> Kevin Lange
>
> Why not simply write a query that gets ran by OS that selects
> the status and
> logins from v$instance. You should be able to parse that
> simple enough.
>
> -----Original Message-----
> From: Jacques Kilchoer [mailto:Jacques.Kilchoer_at_quest.com]
>
> If you try a bogus userid/password and use the ORA-1017 as
> "proof" that the
> database is up, you wouldn't know if the database is in
> restricted session
> mode. (Something that has burned me before.) I personally
> think the best way
> for verifying that the database is up is to create a session (create a
> userid that only has "create session" privilege and use that for
> verification.
>
> > -----Original Message-----
> > testa_at_dmc-it.com
> >
> > Mike, make your script attempt to login into the
> database(even with a
> > bogus userid/password),
> >
> > you get a ORA-1017 invalid userid/password, you know the
> > database is up
> > and you got a connection to it.
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Thu Mar 11 2004 - 17:58:52 CST
