Ora-03135 Error Code
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack ora-03135 connection lost contact process id Overflow the company Business Learn more about hiring developers or posting ads with us ora-03135 connection lost contact informatica Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a
Ora-03135 Connection Lost Contact Sap
community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up “ORA-03135: connection lost contact” when inserting large file up vote 6 down vote favorite I'm trying
Ora-03135 Connection Lost Contact Standby
to do an insert with a potentially large amount of binary data into a remote Oracle (11g) database using Entity Framework (ODP.Net). It works fine for really small files (<5 KB), but for larger ones (e.g. 44 KB) I get an error: "ORA-03135: connection lost contact". I don't think it's timing out, as the exception occurs within a second of executing the command. I tried setting both of the following in ora-03135 connection lost contact oracle 12c my connection string, but to no avail: Validate Connection=true Pooling=false I also looked in the listener.log file on the remote machine. It shows the connections being made, but no sign of exceptions or terminated connections. I'm up for suggested fixes or troubleshooting methods. Edit: The same SQL operations work when accessing an Oracle instance on the local network. c# oracle odp.net share|improve this question edited Jan 5 '14 at 19:07 Guido Leenders 2,0921828 asked Aug 28 '12 at 16:12 Ishmael Smyrnow 6491623 Well maybe it is not that, but I had the "ORA-03135: connection lost contact" on weird stuff when the connection was not lost at all it only happend that Oracle was no longer able to swallow the SQL statement submitted. I got it on huge queries (>2000 line of code). Maybe I am sending you on the right track but I thought after 4 hours no answer I at least could tell you that piece of my own experience. For me it looked like the message always appears when the parser of the SQL command crashed in the background. –hol Aug 28 '12 at 20:47 Might be worth checking the alert log on the remote machine to see if that reported an error. If n
session was terminated. 2) Check if the timeout parameters are set properly in
Ora-03135 Connection Lost Contact Data Guard
sqlnet.ora. Reference: http://docs.oracle.com/cd/B28359_01/server.111/b28278/e2100.htm#ORA-03135 ORA-03135 occurs when we try to ora 03135 connection lost contact dbd error ocisessionbegin connect oracle database and the connection gets time out. ORA-03135 can also be caused sqlplus ora-03135 connection lost contact by the firewall when connecting remotely. To resolve ORA-03135 exception we need to increase the value of the expire_time parameter in theSQLNET.ORAfile, as mentioned http://stackoverflow.com/questions/12163370/ora-03135-connection-lost-contact-when-inserting-large-file in Action part. We can also set the parameters sqlnet.inbound_connect_timeoutand inbound_connect_timeout_listenername to 0 can avoid the ORA-03135 error. SQLNET.ORA file is located under $ORACLE_HOME/network/admin/. Following is the Oracle Documentation having lists and description of sqlnet.ora file parameters - http://docs.oracle.com/cd/E11882_01/network.112/e10835/sqlnet.htm#NETRF182 We recently faced ORA-03135 on one of our http://nimishgarg.blogspot.com/2015/04/ora-03135-connection-lost-contact.html testing environment after Server Admin team did a firewall upgrade. Users were able connect to the database, but if their session was idle for some time, the connection was getting terminated. To resolveORA-03135we added following to SQLNET.ORA file SQLNET.EXPIRE_TIME = 10 This keeps connections alive by send a check to verify that client/server connections are active in every 10 minutes. If the probe finds a terminated connection, or a connection that is no longer in use, then it returns an error, causing the server process to exit. Related Posts - SQLNET: How does Oracle Client connect with Oracle Server - ORA-03113: end-of-file on communication channel - ORA-12154: TNS:could not resolve the connect identifier specified - ORA-12514: TNS:listener does not currently know of service requested in connect descriptor - ORA-01017: invalid username/password; logon denied Email ThisBlogThis!Share to TwitterShare to
HH24:MI:SS') from dual TO_CHAR(SYSDATE,'DD.MON.YYYYH ----------------------------- 28.SEP.2012 10:52:01 Elapsed: 00:00:00.01 (Delay for 35+ minutes) SQL> r 1* select to_char(sysdate,'DD.MON.YYYY HH24:MI:SS') from dual http://stelliosdba.blogspot.com/2012/10/ora-03135-connection-lost-contact.html select to_char(sysdate,'DD.MON.YYYY HH24:MI:SS') from dual * ERROR at line 1: ORA-03135: connection lost contact Elapsed: 00:05:22.63 Note the elapsed time of 5 mintes 22 seconds. To debug enable a client side SQL*net trace and reproduce the error. In this case after several tests the error occured after 30 minutes. Oracle 11.1+ database versions mask the "ORA-03135" error connection lost and return a result after the 5 minutes which may lead the DBA down the wrong path believing there is a problem with the database. For 11g the DIAG_ADR_ENABLED=off must be set otherwise trace files will go to the DIAGNOSTICS destination. To not interfer with other users create the SQLNET.ORA and TNSNAMES.ORA in your own directory and connection lost contact use them by setting the TNS_ADMIN variable. SQLNET.ORA TNSPING.TRACE_LEVEL=admin TNSPING.TRACE_DIRECTORY=/home/oracle/dba/user1/tns_admin/trace/ TRACE_LEVEL_CLIENT=admin TRACE_DIRECTORY_CLIENT=/home/oracle/dba/user1/tns_admin/trace/ TRACE_UNIQUE_CLIENT=on TRACE_TIMESTAMP_CLIENT=on TRACE_TIMESTAMP_SERVER=true TRACE_FILE_CLIENT=client_trace DIAG_ADR_ENABLED=off Information gathered in the trace file: [28-SEP-2012 11:29:21:622] nioqsm: send-break: failed to send oob break... [28-SEP-2012 11:29:21:622] nioqper: error from send-marker [28-SEP-2012 11:29:21:622] nioqper: ns main err code: 12547 [28-SEP-2012 11:29:21:622] nioqper: ns (2) err code: 12560 [28-SEP-2012 11:29:21:622] nioqper: nt main err code: 517 [28-SEP-2012 11:29:21:622] nioqper: nt (2) err code: 32 [28-SEP-2012 11:29:21:622] nioqper: nt OS err code: 0 [28-SEP-2012 11:29:21:622] nioqsm: exit [28-SEP-2012 11:29:21:622] nioqer: entry [28-SEP-2012 11:29:21:622] nioqce: entry [28-SEP-2012 11:29:21:622] nioqce: exit [28-SEP-2012 11:29:21:623] nioqer: exit [28-SEP-2012 11:29:21:623] nioqrs: nioqrs: Couldn't send break. returning 3135 The trace file data above matches what is in MOS note: ORA-3135 with Recovery Catalog Creation Across the Network (Firewall included) [ID 805088.1] "where nt[1]=32 is Operating System Dependent(OSD) error code. OSD error is Err#32 Broken pipe. This OSD error is also defined in errno.h: * #define EPIPE 32 /* Broken pipe */" Resolution was to set an SQLNET.EXPIRE_TIME=15 in the database