Re: Client/Server - Check if database is UP

vgoel_at_pts.mot.com (Vikram Goel (Cntr)) wrote:

>Jeff,
 

>If you can within your application do a file check, check for a file named
>sgadef<sid_name>.ora, in the $ORACLE_HOME/dbs directory in Unix systems, here the
>value 0f sid_name is the sid you are connecting to.
 

>The other method is to do a connect to Oracle db, if no errors go for it,
>else get out. If you try to do inserts from your app you will still get errors, if
>the db is not up. Basicly you need to trap errors being returned by sqlnet in
>your app.
 

>Hope this helps,
 

>--
>Vikram Goel Motorola email: vgoel_at_pts.mot.com
>Sr. Oracle DBA - Consultant
>Aerotek Inc. My email: vgoel_at_emi.net
 

>Motorola Info:
>Mail Stop 39, Room S1014
>1500 Gateway Blvd,
>Boynton Beach, FL 33426
 

>In article <31BDF229.49C1_at_progress.com>, Jeff Bickart <bickart_at_progress.com> writes:
>>I am working on a Client/Server Oracle 7 application. We are trying
>>to figure out a way to determine if the database is available before
>>we attempt to write to the database. If the database is available
>>then write otherwise an alert-box will warn the user to try the
>>operation later. Does anybody have a clue on how to do this.
>>
>>Jeff Bickart

checking the sgadef* will not always work. e.g. sometimes when the instance crashed , this file may well not be cleaned.... Received on Sat Jun 15 1996 - 00:00:00 CEST