There is a minimum patch level on 18.104.22.168 on some platforms required for
it to function properly.
On Mon, Apr 16, 2018, 4:14 PM Norman Dunbar <oracle@xxxxxxxxxxxxxxx> wrote:
I'm pretty sure it is because I used it on a recent cloud project. On
Azure, Windows and 22.214.171.124.
Unless, of course, I've quoted the wrong setting! Check docs.oracle.com
for the 11g networking manual for details. I can't, I'm in the bath!!!!!!!!
On 16 April 2018 15:50:58 BST, John Dunn <JDunn@xxxxxxxxx> wrote:
Is SQLNET.EXPIRE_TIME available in Oracle 11?
Senior Solutions Engineer
Sefas Innovation Limited.
Tel: + 44 (0) 117 910 0529
Advanced notice of holidays : 3rd April, 23rd-26 April 2018
With effect from 1st April 2017 my normal working days are Monday to
*From:* Norman Dunbar [mailto:oracle@xxxxxxxxxxxxxxx]
*Sent:* 16 April 2018 10:09
*To:* John Dunn; John Dunn; oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Oracle running under Amazon Web services : database
connections timing out
If I renember correctly, adding SQLNET.EXPIRE_TIME=15 does a probe every
15 minutes to check connections are alive and effectively is a keepalive.
I've had to use this in the past. It goes on the server by the way, not the
Sent from my Android device with K-9 Mail. Please excuse my brevity.