당신은 주제를 찾고 있습니까 “ora 609 tns 12537 – How To Solve TNS protocol Adapter Error Of Oracle Database!!“? 다음 카테고리의 웹사이트 https://chewathai27.com/you 에서 귀하의 모든 질문에 답변해 드립니다: https://chewathai27.com/you/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 Cecret Point 이(가) 작성한 기사에는 조회수 26,903회 및 좋아요 135개 개의 좋아요가 있습니다.
ora 609 tns 12537 주제에 대한 동영상 보기
여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!
d여기에서 How To Solve TNS protocol Adapter Error Of Oracle Database!! – ora 609 tns 12537 주제에 대한 세부정보를 참조하세요
If You are encountered with an Oracle error saying \”TNS Protocol Adapter Error\” Then This Video is for You. It Will Guide You Step By Step.
ora 609 tns 12537 주제에 대한 자세한 내용은 여기를 참조하세요.
ORA-609 with TNS-12537: TNS:connection closed
ORA-609 with TNS-12537: TNS:connection closed · 1. This can happen suppose our client closed the connection immediately after initiating it. · 2.
Source: ora-data.blogspot.com
Date Published: 8/23/2022
View: 2884
Opiodr aborting process unknown ospid (Doc ID 1121357.1)
… could not attach to incoming connection ORA-12537: TNS:connection closed ORA-609 : opiodr aborting process unknown osp (2436\_7464).
Source: www.modb.pro
Date Published: 4/7/2022
View: 3883
Oracle11g ORA-609 TNS 12537 TNS 12560 – ITPub博客
Oracle11g ORA-609 TNS 12537 TNS 12560 … Tracing not turned on. … It can be somewhat challenging to determine the origin of the client that is …
Source: blog.itpub.net
Date Published: 12/22/2022
View: 7221
ORA-609 : Opiodr aborting process unknown ospid – IT Tutorial
Details of error are as follows. ORA-00609: could not attach to incoming connection ORA-12537: TNS:connection closed ORA-609 : opiodr aborting …
Source: ittutorial.org
Date Published: 10/13/2022
View: 9172
(Turn) TNS-12537 and ORA-609 errors appear at the same time
ns main err code: 12537 opiodr aborting process unknown osp (29191) as a result of ORA-609. TNS-12537: TNS:connection closed ns secondary err code: 12560
Source: blog.actorsfit.com
Date Published: 9/29/2022
View: 7133
ORA-609 : TNS-12537: TNS:connect… – 代码交流
ORA-609 TNS-12537 and TNS-12547 in 11g Alert.log [ID 1116960.1]. Cause. The ORA-609 error is thrown when a client connection of any kind failed to complete …
Source: www.daimajiaoliu.com
Date Published: 5/22/2021
View: 158
ORA-609 with TNS-12537 – About Oracle and more
ORA-609 with TNS-12537 · 1 Client initiates a connection to the database so it connects to the listener · 2 Listener starts (fork) a dedicated …
Source: stevecao.wordpress.com
Date Published: 6/18/2022
View: 9722
ORA-00609: could not attach to incoming connection ORA-609
This error is usually due to timeout issues. It indicates that a client connection has failed, or that a connection was aborted without …
Source: doyensys.com
Date Published: 12/11/2022
View: 5227
주제와 관련된 이미지 ora 609 tns 12537
주제와 관련된 더 많은 사진을 참조하십시오 How To Solve TNS protocol Adapter Error Of Oracle Database!!. 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.
주제에 대한 기사 평가 ora 609 tns 12537
- Author: Cecret Point
- Views: 조회수 26,903회
- Likes: 좋아요 135개
- Date Published: 2016. 2. 5.
- Video Url link: https://www.youtube.com/watch?v=_N8pCSo2WXA
ORA-609 with TNS-12537: TNS:connection closed
ORA-609 with TNS-12537: TNS:connection closed
We almost time receive an error such as ora-609 which shows in alert log as
TNS- TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (12345) as a result of ORA-609
This error means could not attach to incoming connection, so our database process was aborted or closed because incoming connection was not passed to it by listener. In our case we found sqlnet error stack as shown below
TNS-12537: TNS:connection closed
It means the dedicated process didn’t have a client connection anymore to work.
As we all know the process of client connections:
1. First Client initiates a connection to the database so it connects to the listener.
2. Then listener starts a dedicated DB process that will receive this connection or session.
3. After that, this dedicate process is started and listener passes the connection from the client to this process.
4. Then the sever process takes the connection from the listener to continue the handshake with the client.
5. After that Server process and client exchange messages or information required for establishing a session or user logon.
6. Then the session is opened now.
In our case, it may be when the dedicated process tries to communicate with the client it finds that connection was closed.
Solution or Work around:
We can eliminate this error by increasing the value of SQLNET.INBOUND_CONNECT_TIMEOUT in sqlnet.ora file.
By default the SQLNET.INBOUND_CONNECT_TIMEOUT value is 60 seconds.
The sqlnet.ora file can be found in RDBMS_HOME/network/admin.
For example:
$ cd $ORACLE_HOME/network/admin
$vi sqlnet.ora
And change the value of S QLNET.INBOUND_CONNECT_TIMEOUT as:
SQLNET.INBOUND_CONNECT_TIMEOUT=300
Then save the file.
There are many more possibilities which can cause this error such as:
1. This can happen suppose our client closed the connection immediately after initiating it.
2. This may occur when firewall kill the connection.
3. Sometimes, it may happen because of Database , OS or network performance problem.
4. This error may occur when some client crashes.
Hope this may also useful here:
Hope this may useful and helpful. Please let us know for any concerns either by below comments or write to @contact us: https://ora-data.blogspot.in/
Troubleshooting Guide ORA-609 : Opiodr aborting process unknown ospid (Doc ID 1121357.1)
In this Document
APPLIES TO:
Oracle Net Services – Version 11.1.0.7 and later
Oracle Database – Enterprise Edition – Version 11.1.0.7 and later
Information in this document applies to any platform.
PURPOSE
ORA-609 is being reported in the alert log. The error is intermittent and may not occur for days at a time.
Mon Oct 12 10:03:39 2009 Errors in file e:\app\oracle\diag\rdbms\center\center\trace\center_ora_7464.trc: ORA-00609: could not attach to incoming connection ORA-12537: TNS:connection closed ORA-609 : opiodr aborting process unknown ospid (2436\_7464)
Sqlnet.log that is local to the database server may report these errors:
Fatal NI connect error 12537, connecting to: (LOCAL=NO) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.1.0.7.0 – Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.7.0 – Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.7.0 – Production Time: 12-OCT-2009 10:03:39 Tracing to file: E:\app\oracle\product\11.1.0\db_1\NETWORK\trace\svr1_7464.trc Tns error struct: ns main err code: 12537 TNS-12537: TNS:connection closed ns secondary err code: 12560 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0
Listener log shows the connection was established with no apparent errors. This is because the connection failed AFTER the listener has handed off the connection to the server process.
12-OCT-2009 10:03:39 * (CONNECT_DATA=(SID=ORCL)) * (ADDRESS=(PROTOCOL=tcp)(HOST=123.456.1.123)(PORT=3158)) * establish * ORCL * 0 12-OCT-2009 10:03:39 * (CONNECT_DATA=(SID=ORCL)) * (ADDRESS=(PROTOCOL=tcp)(HOST=123.456.1.123)(PORT=3159)) * establish * ORCL * 0
Notice in this example Oracle Net Server trace, filename “svr_7464.trc”
Here the problem is seen when receiving the connection packet from client. Note that the ORA-609 does not appear in the Oracle Net trace. The ORA-609 is represented by the accompanying ns=12537 in this trace snippet.
[000001 12-OCT-2009 10:03:39:116] nscon: doing connect handshake… [000001 12-OCT-2009 10:03:39:116] nscon: recving a packet [000001 12-OCT-2009 10:03:39:116] nsprecv: entry [000001 12-OCT-2009 10:03:39:116] nsprecv: reading from transport… [000001 12-OCT-2009 10:03:39:116] nttrd: entry [000001 12-OCT-2009 10:03:39:163] nttrd: exit [000001 12-OCT-2009 10:03:39:163] ntt2err: entry [000001 12-OCT-2009 10:03:39:163] ntt2err: Read unexpected EOF ERROR on 7104 [000001 12-OCT-2009 10:03:39:163] ntt2err: exit [000001 12-OCT-2009 10:03:39:163] nsprecv: error exit [000001 12-OCT-2009 10:03:39:163] nserror: entry [000001 12-OCT-2009 10:03:39:163] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 [000001 12-OCT-2009 10:03:39:163] nscon: error exit [000001 12-OCT-2009 10:03:39:163] nsdo: nsctxrnk=0 [000001 12-OCT-2009 10:03:39:163] nsdo: error exit [000001 12-OCT-2009 10:03:39:163] nsinh_hoff: error recving requestOther times tracking ORA-609 via Alert and Oracle Net server traces, shows issue further on during handshake.
Alert.log except here:
Mon Dec 21 15:52:15 2009 ORA-609 : opiodr aborting process unknown ospid (21631120_1) [21-DEC-2009 15:52:15:025] nscon: sending NSPTAC packet [21-DEC-2009 15:52:15:025] nspsend: entry
[21-DEC-2009 15:52:15:031] ntt2err: Read unexpected EOF ERROR on 14 [21-DEC-2009 15:52:15:031] ntt2err: exit [21-DEC-2009 15:52:15:031] nsprecv: error exit [21-DEC-2009 15:52:15:031] nserror: entry [21-DEC-2009 15:52:15:031] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 [21-DEC-2009 15:52:15:031] nsrdr: error exit [21-DEC-2009 15:52:15:031] nsdo: nsctxrnk=0 [21-DEC-2009 15:52:15:031] nsdo: error exit [21-DEC-2009 15:52:15:031] nsnareceive: error exit [21-DEC-2009 15:52:15:031] nserror: entry [21-DEC-2009 15:52:15:031] nserror: nsres: id=0, op=68, ns=12537, ns2=12532; nt[0]=0, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 [21-DEC-2009 15:52:15:031] nacomrc: received 12637 bytes [21-DEC-2009 15:52:15:031] nacomrc: failed with error 12637 [21-DEC-2009 15:52:15:031] nacomrc: exit [21-DEC-2009 15:52:15:031] na_receive_packet: failed with error 12637 [21-DEC-2009 15:52:15:031] na_receive_packet: exit [21-DEC-2009 15:52:15:031] na_server: failed with error 12637It is common to find corresponding errors in the sqlnet.log file that is local to the instance.
E.g.
Fatal NI connect error 12537, connecting to: (LOCAL=NO) VERSION INFORMATION: TNS for Solaris: Version 11.2.0.2.0 – Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.2.0 – Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.2.0 – Production Time: 21-DEC-2009 15:52:15 Tracing not turned on. Tns error struct: ns main err code: 12537 TNS-12537: TNS:connection closed ns secondary err code: 12560 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0
Matched to an event in the Oracle Net Server Trace
TROUBLESHOOTING STEPS
1. Find the incoming client(s) making the connections from the listener.log.
Alert log will show an ORA-609 error similar to following :
Mon Oct 05 12:41:49 2009 ORA-609 : opiodr aborting process unknown ospid (21131406_1)
Go to the listener.log and find the entry for this connection. The entry in the listener.log should look similar to the following:
05-OCT-2009 12:41:49 * (CONNECT_DATA=(SID=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=sample.com)(PORT=1234)) * establish * orcl * 0
Notice the client address in our example is “sample.com”. One option is to locate several clients and enable client tracing at those sites. You might inspect the log file (ORACLE_HOME/network/log) at the client(s) and check specifically for timeout errors that might have occurred at the same timestamp.
2. Oracle Net Level 16 Client tracing. Add to a clients SQLNET.ORA file
DIAG_ADR_ENABLED=off TRACE_LEVEL_CLIENT = 16 TRACE_TIMESTAMP_CLIENT = ON TRACE_DIRECTORY_CLIENT =
TRACE_FILELEN_CLIENT = TRACE_FILENO_CLIENT = If the connection model is JDBC thin, Javanet tracing of a client is required. See Document 793415.1 How to Perform the Equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver.
If 11.2 JDBC thin client used, the following note can be used Document 1050942.1 How to Trace the Network Packets Exchanged Between JDBC and the RDBMS in Release 11.2
3. Oracle Net Level 16 Server tracing. Add to server side SQLNET.ORA file
DIAG_ADR_ENABLED=off TRACE_LEVEL_SERVER = 16 TRACE_TIMESTAMP_SERVER = ON TRACE_DIRECTORY_SERVER =
TRACE_FILELEN_SERVER = TRACE_FILENO_SERVER = Cyclic tracing will allow you to control the size of and number of trace files that are produced.
The TRACE_FILELEN parameter is for the size of a trace file.
The TRACE_FILENO parameter is the number of traces per process.
Important Notes: The SQLNET.ORA file is only read once on creation of a process. RDBMS Background process and shared server dispatchers will need to be restarted for parameter changes in the SQLNET.ORA to be picked up. Once a process has started to be traced, tracing will not stop until that the process stops. In an environment where both GRID and RDBMS homes are installed, instance would reference a sqlnet.ora file in RDBMS_HOME/network/admin by default. (Whereas the listener would refer to GRID_HOME/network/admin for its .ora files) Please note, that enabling Oracle Net server tracing can produce large amounts of trace, in a very short time frame. Even with cyclic tracing, each process will have the TRACE_FILENO_SERVER value amount of traces produced. Optimal tracing workflow should be to enable tracing, reproduce problem and then disable tracing. Thus limiting amount of time tracing is enabled. Setting TRACE_FILENO_SERVER to 1 and TRACE_FILELEN_SERVER = 20480, could be a solution to lowering the amount of trace generated per process. Remember the trace file will be overwritten and you could lose the important data covering the failure.
4. Errorstack: Setup errorstack to capture failure. This can be particular useful when capturing an Oracle Net client trace is not feasible.
SQL> alter system set events ‘609 errorstack(3)’ ;
Once a few traces have been collected while the error is reproduced:
SQL> alter session set events ‘609 off’ ;
Once you get a failure:
Review the SQLNET.LOG file on server.
Find the matching entry in the ALERT. LOG, compare via timestamp.
From the entry in the SQLNET.LOG file, you will have the Oracle Net server trace name, from the line “Tracing to file”.
Open the server trace and grep / search for the Connection ID value.
Then search the clients trace client directory for the same Connection ID value.
You’ll then having matching client and server traces.
This process is described in full in Document 374116.1 How to Match Oracle Net Client and Server Trace Files
Upload for review:
Matching Oracle Net client and server traces or matching Javanet and Server trace.
ALERT.LOG and LISTENER.LOG files. (Only required to upload data cover issue, not all the log files)
SQLNET.LOG from server ORACLE_HOME/network/log
Trace from errorstack.
Known Issues:
Often the ORA-609 is reported due to client disconnecting before the connection can be established fully. Timeout parameters INBOUND_CONNECT_TIMEOUT_
in the LISTENER.ORA file and SQLNET.INBOUND_CONNECT_TIMEOUT in the SQLNET.ORA need to be reviewed. If using the default of 60 seconds, (no explicit setting), then it is likely these parameters will need to be increased. Review and check network settings for the server machine where the database is running. Ensure settings are all correct and as expected and DNS servers are available
If the server platform is Microsoft Windows, check the Windows Services for TNS listener and database ensure each service is started using the same account.
Note: Some helpful information about finding diagnostic output.
Note 438148.1 How to Find the alert.log File (11g and Later)
REFERENCES
NOTE:1050942.1 – How to Trace the Network Packets Exchanged Between JDBC and the RDBMS
NOTE:609.1 – ORA-609 TNS-12537 and TNS-12547 in 11g Alert.log
NOTE:793415.1 – How to Perform the Equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver
NOTE:438148.1 – How to Find the alert.log File (11g and Later)
Oracle11g ORA-609 TNS 12537 TNS 12560_ITPUB博客
For that reason, we often recommend increasing the values for INBOUND_CONNECT_TIMEOUT at both listener and server side sqlnet.ora file as a preventive measure. If the problem is due to connection timeouts, an increase in the following parameters should eliminate or reduce the occurrence of the ORA-609s.
Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
Listener.ora: INBOUND_CONNECT_TIMEOUT_ listener_name =120
These settings are in seconds. Again, the default is 60. A setting of 120 seconds should resolve most if not all ORA-609 errors.
As explained in the Cause section, The ORA-609 error is thrown when a client connection of any kind failed to complete or aborted the connection process, so ORA-609 and TNS- errors are expected while shutting down the database – as client connection will fail to complete or aborted the connection process before the connection/authentication process was complete. So please ignore the ORA-609 and TNS- errors, if these are appear while database instance is shutting down.
If the issue persists and inbound connect does not have any effect, the following steps are intended to help locate the client that may be causing the errors.
1) Suppress the TNS errors in the alert.log by setting the following sqlnet.ora file parameter:
sqlnet.ora file (on the server): DIAG_ADR_ENABLED = OFF
ORA-609 : Opiodr aborting process unknown ospid
I got ” ORA-609 : Opiodr aborting process unknown ospid ” error in Oracle.
ORA-609 : Opiodr aborting process unknown ospid
Details of error are as follows.
ORA-00609: could not attach to incoming connection ORA-12537: TNS:connection closed ORA-609 : opiodr aborting process unknown ospid (2436_7464)
ORA-609 : opiodr aborting process unknown ospid (21631120_1)
Opiodr aborting process unknown ospid
This ORA-609 errors are related with the client disconnecting before the connection can be established fully. Timeout parameters INBOUND_CONNECT_TIMEOUT_
in the LISTENER.ORA file and SQLNET.INBOUND_CONNECT_TIMEOUT in the SQLNET.ORA need to be reviewed. If using the default of 60 seconds, (no explicit setting), then it is likely these parameters will need to be increased.
Review and check network settings for the server machine where the database is running. Ensure settings are all correct and as expected and DNS servers are available
If the server platform is Microsoft Windows, check the Windows Services for TNS listener and database ensure each service is started using the same account.
To solve this error, set SQLNET.INBOUND_CONNECT_TIMEOUT=180 in Sqlnet.ora.
and set INBOUND_CONNECT_TIMEOUT_listener_name=120 in Listener.ora under $ORACLE_HOME/network/admin.
1,337 views last month, 1 views today
(Turn) TNS-12537 and ORA-609 errors appear at the same time
Original address: http://hi.baidu.com/benmaoer/blog/item/ccf7a18badd18d6c9f2fb475.html
Alert log content:
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
Tracing not turned on.
Time: 09-FEB-2011 06:11:23
nt OS err code: 0
TNS-12537: TNS:connection closed
Tracing not turned on.
ns secondary err code: 12560
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 – Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
Tns error struct:
Tns error struct:
nt main err code: 0
ns main err code: 12537
ns main err code: 12537
Time: 09-FEB-2011 06:11:23
nt secondary err code: 0
nt OS err code: 0
TNS-12537: TNS:connection closed
TNS-12537: TNS:connection closed
ns secondary err code: 12560
ns secondary err code: 12560
nt main err code: 0
nt main err code: 0
Tracing not turned on.
nt secondary err code: 0
nt secondary err code: 0
Tns error struct:
nt OS err code: 0
nt OS err code: 0
ns main err code: 12537
opiodr aborting process unknown ospid (29191) as a result of ORA-609
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (29189) as a result of ORA-609
opiodr aborting process unknown ospid (29183) as a result of ORA-609
opiodr aborting process unknown ospid (29193) as a result of ORA-609
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 – Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
Time: 09-FEB-2011 06:11:23
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
Wed Feb 09 06:11:23 2011
***********************************************************************
nt main err code: 0
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
nt secondary err code: 0
nt OS err code: 0
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 – Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 – Production
opiodr aborting process unknown ospid (29201) as a result of ORA-609
opiodr aborting process unknown ospid (29199) as a result of ORA-609
Time: 09-FEB-2011 06:11:23
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (29203) as a result of ORA-609
Also check the listener log for no special exception
Trying on some machines like TNSPING XXX 60, the result is normal, no link problem
Obviously, as long as the first tnsping link is normal, the subsequent jdbc link will be normal; if the first time is abnormal, the subsequent jdbc link will easily return a timeout error.
Try to restart lsnrctl stop/start and reload the configuration file lsnrctl reload to re-register the database instance, but the timeout error cannot be resolved.
Obviously when tnsping xxxx N:
OK (56730 msec)
OK (80 msec)
OK (80 msec)
OK (70 msec)
OK (60 msec)
OK (70 msec)
OK (70 msec)
OK (80 msec)
OK (60 msec)
OK (60 msec)
OK (70 msec)
OK (60 msec)
OK (47820 msec)
OK (70 msec)
….
At the same time, there is no delay in the PING IP result, and the machine has not been installed with a firewall before And so on, you can eliminate network and firewall problems.
In the case of continuous TNSPING, there is an obvious link delay, which is suspected to be a problem with the listener.
After restarting the monitor, the problem can still be reproduced. Refer to the results of Google and comment out the DNS resolution in the/etc/resolve.conf file on the DB machine. The result of TNSPING returns to normal, and the alert log no longer shows tns-12537 errors. .
I haven’t figured out why DNS resolution affects the listener? The DNS has not been modified before, and it is initially suspected that there is a problem with the DNS.
Finally, according to the online document
http://forums.oracle.com/forums/thread.jspa?messageID=4489745
comment out the resolution of DNS in the configuration file/etc/resolve.conf
The documentation on metalink on TNS-12537 is not very useful, basically it may have nothing to do with the provided.
Troubleshooting ORA-12537/TNS-12537 TNS:Connection Closed [ID 555609.1]
Fatal NI Connect 12560 And ORA-609 Opiodr Aborting Process Errors In The Alert Log [ID 987162.1]
From “ITPUB Blog”, link: http://blog.itpub.net/7353848/viewspace-702563/, if you need to reprint, please indicate the source, otherwise legal liability will be pursued.
ORA-609 with TNS-12537
Question: Does it really mean cnnection was successfully established when you see the following information in listener.log:
12-OCT-2009 10:03:39 * (CONNECT_DATA=(SID=ORCL)) * (ADDRESS=(PROTOCOL=tcp)(HOST=123.456.1.123)(PORT=3158)) * establish * ORCL * 0
12-OCT-2009 10:03:39 * (CONNECT_DATA=(SID=ORCL)) * (ADDRESS=(PROTOCOL=tcp)(HOST=123.456.1.123)(PORT=3159)) * establish * ORCL * 0
Answer: NO!!!!
As a big picture, these are the steps for a client connection:
1 Client initiates a connection to the database so it connects to the listener
2 Listener starts (fork) a dedicated database process that will receive this connection (session)
3 After this dedicated process is started, the listener passes the connection from the client to this process
4 The server process takes the connection from the listener to continue the handshake with the client
5 Server process and client exchange information required for establishing a session (ASO, Two Task Common, User logon)
6 Session is opened
In the case of the above error the connection from the client was closed somewhere between 3. and 4. So when the dedicated process tries to communicate with the client it finds that connection closed.
Listener log shows the connection was established with no apparent errors. This is because the connection failed AFTER the listener has handed off the connection to the server process.
Reference:
Troubleshooting Guide ORA-609 : Opiodr aborting process unknown ospid (Doc ID 1121357.1)
Alert.log shows ORA-609 with TNS-12537: TNS:connection closed (Doc ID 1538717.1)
ORA-00609: could not attach to incoming connection ORA-609: opiodr aborting process unknown ospid ORA-609: opiodr aborting process unknown ospid Cause and Solution
This error is usually a secondary error. This means that the actual cause of the issue is another error in the stack trace or list of errors.
If you get this error, take a look at the other errors that you can see.
Cause: could not attach to incoming connection
This error is usually due to timeout issues. It indicates that a client connection has failed, or that a connection was aborted without finishing the connection.
Solution: To resolve this error, you can either look for the issue that is causing the timeout to occur, or increase the timeout limit.
If you want to increase the timeout limit, change the INBOUND_CONNECT_TIMEOUT value on both the listener and server side. This can be done in the sqlnet.ora file and the listener.ora file.
If you can’t resolve this error using any of these methods, then contact your database administrator or contact Oracle support. There could be a range of things specific to your environment that cause this error.
키워드에 대한 정보 ora 609 tns 12537
다음은 Bing에서 ora 609 tns 12537 주제에 대한 검색 결과입니다. 필요한 경우 더 읽을 수 있습니다.
이 기사는 인터넷의 다양한 출처에서 편집되었습니다. 이 기사가 유용했기를 바랍니다. 이 기사가 유용하다고 생각되면 공유하십시오. 매우 감사합니다!
사람들이 주제에 대해 자주 검색하는 키워드 How To Solve TNS protocol Adapter Error Of Oracle Database!!
- How To Solve TNS protocol Adapter Error Of Oracle Database
- TNs
- TNS
- tns
- protocol
- Protocol Adapter Error
- Oracle 10G Protocol Adapter Error
- TNS Protocol adapter Exception
- Oracle 10G Adapter Error
- TNS protocol Adapter error of oracle database
- database error tns
- tns protocol error of oracle database
How #To #Solve #TNS #protocol #Adapter #Error #Of #Oracle #Database!!
YouTube에서 ora 609 tns 12537 주제의 다른 동영상 보기
주제에 대한 기사를 시청해 주셔서 감사합니다 How To Solve TNS protocol Adapter Error Of Oracle Database!! | ora 609 tns 12537, 이 기사가 유용하다고 생각되면 공유하십시오, 매우 감사합니다.
