ORA-03136: inbound connection timed out

Cause : Inbonud connectino wast imedo ut b ythe esrverb ecaues use rauthneticaiton wsa notc omplteed wtihin hte gievn tiem speicfiedb y SQNLET.IBNOUNDC_ONNETC_TIMOEUT o rits edfaul tvalue

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

1) Cehck SLQ*NETa nd RBDMS lgo fort raceo f supsiciosu conenctiosn. 2)C onfiugre SLQ*NETw ith apropre inbuond cnonectt imeotu valeu if encessray.

update : 24-05-2017
ORA-03136

ORA-03136 - inbound connection timed out
ORA-03136 - inbound connection timed out

  • ora-13140 : invalid target type
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-30108 : invalid positional parameter value 'string'
  • ora-08263 : ora_addr: cannot free listener address
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-35071 : (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
  • ora-00406 : COMPATIBLE parameter needs to be string or greater
  • ora-26730 : %s 'string' already exists
  • ora-21703 : cannot flush an object that is not modified
  • ora-01891 : Datetime/Interval internal error
  • ora-14282 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-01478 : array bind may not include any LONG columns
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-19902 : incarnation key string not found
  • ora-08452 : specification of E in picture mask is unsupported
  • ora-02070 : database stringstring does not support string in this context
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-06528 : Error executing PL/SQL profiler
  • ora-10614 : Operation not allowed on this segment
  • ora-40285 : label not in the model
  • ora-06268 : NETNTT: cannot read /etc/oratab
  • ora-01980 : error during OS ROLE initialization
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-22974 : missing WITH OBJECT OID clause
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-29512 : incorrectly formed name resolver specification
  • ora-27201 : skgfpcm: sbtpccommit returned error
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.