How can i do to set a timeout on a EXECUTE SQL CONNECT statement?
I've tried using unix alarms, but it can happen that i receive a
connection also after a timeout has expired, so i can't really know if
the connection has been done or not.
Do you have suggestions?
Thanks
On May 3, 6:30 am, djake <d
@excite.it> wrote:
> How can i do to set a timeout on a EXECUTE SQL CONNECT statement?
> I've tried using unix alarms, but it can happen that i receive a
> connection also after a timeout has expired, so i can't really know if
> the connection has been done or not.
> Do you have suggestions?
> Thanks
All imbedded EXECUTE SQL statements set a return code so if the call
completes your program can check the sqlcs.h or equilivent control
structure to determine if the prior call was successful or
unsuccessful.
Externally you can query Oracle to see if the Unix pid has an
associated Oracle session.
Internally you should be able to issue a OS interrupt timer call
before you issue the connect that will signal your program if your
program does not cancel the timer call before it expires.
HTH -- Mark D Powell --
-----------------------------------------------Reply-----------------------------------------------
> All imbedded EXECUTE SQL statements set a return code so if the call
> completes your program can check the sqlcs.h or equilivent control
> structure to determine if the prior call was successful or
> unsuccessful.
Even if I check the structure the problem is that something my
connection result to be ok only many seconds after the timeout has
expired.
For exmple
At sec 1 I set my timeout at 15 sec
At sec 2 I start the connection
At sec 15 I get a timeout
At sec 18 I check the PRO*C struct and the connection result KO
At sec 25 for example I get the connection KO, even if the timeout has
expired.
So what you suggest me to do?
-----------------------------------------------Reply-----------------------------------------------
On 3 Mag, 16:30, djake <d
@excite.it> wrote:
> > All imbedded EXECUTE SQL statements set a return code so if the call
> > completes your program can check the sqlcs.h or equilivent control
> > structure to determine if the prior call was successful or
> > unsuccessful.
> Even if I check the structure the problem is that something my
> connection result to be ok only many seconds after the timeout has
> expired.
> For exmple
> At sec 1 I set my timeout at 15 sec
> At sec 2 I start the connection
> At sec 15 I get a timeout
> At sec 18 I check the PRO*C struct and the connection result KO
> At sec 25 for example I get the connection KO, even if the timeout has
> expired.
> So what you suggest me to do?
Sorry, at second 25 I get the connection OK
Add to del.icio.us |
Digg this |
Stumble it |
Powered by Megasolutions Inc
