oracle database connection timed out

[kinmun]

recently we installed a FG300D as 2nd tier firewall.

FortiOS version is 5.4.3.

users start experiencing database connection timed out after leaving their connection idle for some time.

we suspect it could be due to the FG300D.

2nd tier firewall is internal facing.

the error message from Toad is end-of-file on communication channel.

[Toshi_Esumi]

session-ttl (3600sec by default) is likely affecting to oracle connections when users are not generating traffic. I'm not oracle expert but recently dealt with POS system disconnection after we put multiple FGs in place at one of customer networks. You could change the default value which affects to all types of traffic but better adjusting ttl only to the impacted traffic, your case oracle connection(port 1521? You should know better than me). Because the longer FW keeps the sessions, the more memory it would take up. There are multiple ways to do this adjustment. Below KB is one of them and I used for the POS system situation(the second one for 4.0MR1-or-later. Still works with 5.4).

http://kb.fortinet.com/kb....do?externalId=FD30171

[Kenundrum]

The answer by Toshi is one part of it- there is also a config change on the oracle side. You need to add the line SQLNET.EXPIRE_TIME to your sqlnet.ora. That parameter sets a time in minutes for the server to check if a client is still connected. this causes a small amount of traffic on port 1521 and keeps the connection alive for the firewall to reset the session TTL. In general, most people set the SQLNET.EXPIRE_TIME = 10 which would do a keepalive (in effect) every 10 minutes. As long as the session-ttl setting on the fortigate is greater than that, you should not have any more oracle timeouts. The oracle setting also has the side effect of purging stale connections that didn't terminate properly which helps when you need to change the online or mount status of the oracle system.

[Sunil_Panchal_NSE7]

Dear Kenundrum ,

did this issue is revolved by doing these changes