Technology Stack - EBS (MOSC)

MOSC Banner

ORA-3136 Inbound connection timed out

edited Oct 12, 2018 5:05AM in Technology Stack - EBS (MOSC) 3 commentsAnswered

So, in our production EBS 12.1 database's alert.log, we have regular mentioning of ORA-3136, like shown below (IP's and ports are masked)

Question: how in eBS do I find out which process/action is causing this one ?

*********************************************************************** Fatal NI connect error 12170.   VERSION INFORMATION:         TNS for Linux: Version 12.1.0.2.0 - Production         Oracle Bequeath NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production         TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production   Time: 21-SEP-2018 07:43:19   Tracing not turned on.   Tns error struct:     ns main err code: 12535 TNS-12535: TNS:operation timed out     ns secondary err code: 12606     nt main err code: 0     nt secondary err code: 0     nt OS err code: 0   Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=A.B.C.D)(PORT=Z)) Fri Sep 21 07:43:19 2018 WARNING: inbound connection timed out (ORA-3136) Fri Sep 21 07:43:36 2018 ***********************************************************************

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

EBS TechStack Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center