setQueryTimeout() stopped working after upgrade from 10g to 11g

mpapesch

Hi,

we are upgrading our database server from Oracle 10g to 11g and are experiencing a strange problem: the JDBC statement <tt>cancel()</tt> and <tt>setQueryTimeout()</tt> methods no longer work.

Starting out with the information given in [1,2], what we found out so far is that there seems to be a combination of a different behavior of the database and some kind of network issue.

While 10g accepted the <tt>cancel()</tt> request and promptly answered with the corresponding <tt>ORA-01013</tt> (user requested cancel of current operation), 11g seems to try and contact the client for a confirmation of the cancellation.

If the client is in the same subnet as the database server everything works as expected.

If, however, the client is in a different subnet, this request from the database server does not make it back to the client through the firewall.

Right now we are kind of stuck and any help, reference to documentation, workarounds and questions are greatly appreciated.

I'll be glad to gather and provide further information.


Thanks in advance,

Matthias


[1] http://stackoverflow.com/questions/2376615/how-is-oracles-jdbc-query-timeout-implemented
[2] http://blog.tanelpoder.com/2010/02/17/how-to-cancel-a-query-running-in-another-session/

Joe Weinstein-Oracle

Hi! That is going to be enough of an Oracle-specific issue that you'll be more likely to get a quick answer with a service request to Oracle support. But you may get lucky and get an expert to answer here too...

mpapesch

Thank you for your quick response! We are considering this option now, while still hoping to get some further advice here ...

Regards,

Matthias

dsurber-Oracle

I agree with Joe, an SR is going to be your best bet. This is almost certainly not a JDBC problem. Filling the SR against JDBC will probably slow down resolving the issue. Based on what you have written this probably is an issue (not necessarily a problem) with SQLNet.

Douglas