Intermittent connection errors

Question

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. The connection only fails through the VIP. The Big-Ip logs are clean. Here is the output from sqlplus and tnsping.&nbsp;
&nbsp;C:\Documents and Settings\a042740&gt;sqlplus fidst_user/****@gfirdbp 
&nbsp;SQL*Plus: Release 10.2.0.1.0 - Production on Fri Aug 13 10:06:44 2010 
&nbsp;Copyright (c) 1982, 2005, Oracle. All rights reserved. 
&nbsp;ERROR: 
&nbsp;ORA-12160: TNS:internal error: Bad error number&nbsp;&nbsp;
&nbsp;C:\Documents and Settings\a042740&gt;tnsping gfirdbp 
&nbsp;TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 13-AUG-2010 10:08:35 
&nbsp;Copyright (c) 1997, 2005, Oracle. All rights reserved. 
&nbsp;Used parameter files: 
&nbsp;C:\oracle\product\10.2.0\client_1
etwork\admin\sqlnet.ora 
&nbsp;Used TNSNAMES adapter to resolve the alias 
&nbsp;Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = GFIRDB)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = fcmfixp) (SRVR = DEDICATED))) 
&nbsp;TNS-12537: TNS:connection closed&nbsp;

chris_akker_129 · Answer

Hi Brian, just a quick follow-up for you, we have just published a deployment guide for BIG-IP for oracle database and RAC.  You can find it on f5.com/oracle in the database section.  Let us know if this helps with your issue. 
&nbsp;  
&nbsp; -Chris. &nbsp;

bletardph_10497 · Answer

Hi!&nbsp;
&nbsp;I have also the same issue even after following the deployment guide "Oracle Database and RAC (BIG-IP LTM)" (document is 'oracle-rac-database-dg.pdf)
&nbsp;I'm able to connect with SQL Developer but after a while (more or less 5 min, 300 sec which is the default TCP timeout if I'm right) I'm getting a reset and I get the following error message in SQL Developer :
&nbsp;"Your database connection has been reset. Any pending transactions or session state has been lost."&nbsp;
&nbsp;Then if I retry, it's ok, I'm getting re-connected.&nbsp;
&nbsp;I'm missing something in one of (or the two ?) TCP profiles but what ?&nbsp;

bletardph_10497 · Answer

Hi Chris! 
&nbsp;  
&nbsp; Thanks for your reply... 
&nbsp; I've made some very quick tests today... 
&nbsp;  
&nbsp; I've checked in the sqlnet.ora file and  the timeout is set to  
&nbsp; TCP.CONNECT_TIMEOUT=10 
&nbsp;  
&nbsp; On the BigIP, the value for Idle Timeout is set to 3600 seconds. 
&nbsp; I've also uncheck 'Reset on Timeout' in the profile but still... My SQLDeveloper gets diconnected after a while... 
&nbsp; Will have to block some time to sniff... 
&nbsp;  
&nbsp; Phil

chris_akker_129 · Answer

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: 
&nbsp;  
&nbsp; 8.In the Idle Timeout box, type the value of the SQLNET.EXPIRE_TIME in your Oracle Net settings. 
&nbsp; 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. 
&nbsp; 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). 
&nbsp; 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 
&nbsp; 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. 
&nbsp;  
&nbsp; Thanx  - Chris. 
&nbsp;  &nbsp;

chris_akker_129 · Answer

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: 
&nbsp;  
&nbsp; 8.In the Idle Timeout box, type the value of the SQLNET.EXPIRE_TIME in your Oracle Net settings. 
&nbsp; 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. 
&nbsp; 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). 
&nbsp; 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 
&nbsp; 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. 
&nbsp;  
&nbsp; Thanx  - Chris. 
&nbsp;  &nbsp;

Forum Discussion

Intermittent connection errors

Recent Discussions

AS3 Limitations

Help needed with iRule (connection closed log )

Use of SSL Decryption.

VLAN Failsafe Functionality

FTP PASV mode to Extended Passive mode

Related Content

Site-to-Site Connectivity in F5 Distributed Cloud Network Connect – Reference Architecture

Securely connecting Kubernetes Microservices with F5 Distributed Cloud

AWS Transit Gateway Connect: GRE + BGP = ?

After applied ASM Policy to Virtual Server, connections will reset with Internal error in log

DevCentral Connects hosts Capture the Flag!

ABOUT DEVCENTRAL

RESOURCES

SUPPORT

PARTNERS