Killed TAF Connections Report ORA-3113 or ORA-3135 But Do Failover

(Doc ID 740135.1)

Last updated on OCTOBER 16, 2013

Applies to:

Oracle Net Services - Version to [Release 9.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 16-OCT-2013***
killed TAF session


When reproducing the failover scenario for a client, of killing a operating system process for an established connection, Transparent Application Failover (TAF) reports ORA-3113: end-of-file on communication channel or ORA-3135: connection lost contact. But the connection does failover.

Other failover scenarios, Instance or Node down work fine.

1st Session

sqlplus scott/tiger@rac

SQL*Plus: Release - Production on Tue Sep 17 09:21:16 2008
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options

SQL> select host_name from v$instance;


2nd Session, Kill the 1st session.

SQL> select username, paddr from v$session where username = 'SCOTT'; 

USERNAME                       PADDR 
------------------------------ ---------------- 
SCOTT                          00000000BA34E8A0 

SQL> select spid from v$process where addr = '00000000BA34E8A0'  ; 


At O/S prompt remove the process Kill -9 30787
First session shows

SQL> / 
select host_name from v$instance 

ERROR at line 1: 
ORA-03113: end-of-file on communication channel 

SQL> / 


ORA-3135 can also be reported to the screen.
Above testing was done using client side failover, added to alias stored in TNSNAMES.ORA file.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms