[Info-Ingres] Problem when Ingres server is rebooted

[simonl at unwired.com.au]

Yes, but only if you have included retry loops in all your SQL
statements.  Otherwise the first SQL statement to be executed after
the server has gone down will fail and not be able to be retried
nicely.

Robert Allely wrote:
> This is easy if its an OpenROAD program. If you declare a
> dbsessionobject and use that as the connection,
> it can be re-established after its disconnected using the usual methods
> for the dbsessionobject class.
>
> Robert Allely
> Ports of Auckland Ltd
> NZ
>
>
> -----Original Message-----
> From: info-ingres-bounces at kettleriverconsulting.com
> [mailto:info-ingres-bounces at kettleriverconsulting.com] On Behalf Of
> Cecil Westerhof
> Sent: Thursday, 24 May 2007 5:33 p.m.
> To: info-ingres at kettleriverconsulting.com
> Subject: [Info-Ingres] Problem when Ingres server is rebooted
>
> We have a program that uses a remote Ingres database server. When the
> remote server reboots the database connection handle is offcourse not
> valid anymore. Is there a way to see that the remote server has
> rebooted? If so what is the best way to handle this? I suppose a close
> is not possible anymore. How do I clear the old handle? And when this is
> done, can I reconnect to the rebooted Ingres server?
>
> _______________________________________________
> Info-Ingres mailing list
> Info-Ingres at kettleriverconsulting.com
> http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres
> ***
> This e-mail is privileged and confidential.  If you are not the intended recipient please delete the message and notify the sender at Ports of Auckland Limited.
> ***