Your program can work regular way. Just catch some exceptions.
The following list shows errors that commonly are returned to applications
during failover:
ORA-01012: not logged on
ORA-01033: Oracle initialization or shutdown in progress
ORA-01034: ORACLE not available
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
ORA-12203: TNS: unable to connect to destination
ORA-12500: TNS: listener failed to start a dedicated server process
ORA-12571: TNS: packet writer failure
These errors are returned by the Oracle Call Interface (OCI) to indicate the
failure of an application's request to perform a database operation. You can
resolve any of these errors by waiting 30 seconds to 1 minute before
reconnecting to the server and resuming processing transactions against the
Oracle database.
--
Mark Malakanov
Oracle DBA
"Brad Lotsberg" <lotsberg_at_willowglen.ab.ca> ???????/???????? ? ????????
?????????: news:38FB92D3.2922C708_at_willowglen.ab.ca...
> I am writing an OCI program and would like to be able to tell easily if
> the client - server network connection is OK. If it isn't , I suppose
> the return code from the OCI call will indicate an error, but it would
> be nice if I could "test" the connection at the beginning of a function
> and decide whether or not I should attempt to re-connect, or alternately
> if an OCI call fails, check the connection to determine if that might
> have been the cause of the failure. The ideal solution for me would be
> a simple OCI call that returns the server connection status, but I can't
> find such a call. Any ideas are appreciated.
>
> Thanks in advance,
>
> Brad Lotsberg, EET.
> lotsberg_at_willowglen.ab.ca
>
>
Received on Sat Apr 29 2000 - 00:00:00 CDT
