For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

brian_11825's avatar
brian_11825
Icon for Nimbostratus rankNimbostratus
Aug 17, 2010

Intermittent connection errors

We have a Big-Ip VIP fronting our two-node Oracle RAC. All too frequently we get application connection errors when connecting through the VIP. The nodes are fine and connecting directly to them works...
oracle
partner
Chris_Akker_129's avatar
Chris_Akker_129
Historic F5 Account
Aug 02, 2011
My apologies if I was not very clear. The actual sqlnet.ora setting is called the SQLNET.EXPIRE_TIME, I was referring to it generically as Sqlnet.Timeout. The TCP.CONNECT_TIMEOUT is for new connection timeouts, not existing connections. Here is the paragraph from the deployment guide that covers this that I referred to before:

 

 

8.In the Idle Timeout box, type the value of the SQLNET.EXPIRE_TIME in your Oracle Net settings.

 

If you have not changed the value of SQLNET.EXPIRE_TIME in your Oracle configuration from the default, you do not need to change the value of Idle Timeout in your BIG-IP configuration.

 

However, if you set your SQLNET.EXPIRE_TIME value to the Oracle recommended value of 10 minutes, change the value of Idle Timeout to a value that is slightly larger, such as 660 (11 minutes).

 

For more information on configuring your Oracle Net Expire Timeout, see the following link: http://download.oracle.com/docs/cd/B28359\_01/network.111/b28317/sqlnet.htmBIIEEGJH

 

Note: Setting 'Idle Timeout' to a value that is slightly larger than the Oracle SQLNET.EXPIRE_TIME setting will ensure that the BIG-IP does not prematurely close an idle connection, but will help to cleanup stale connections.

 

 

Thanx - Chris.