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 : 23-08-2017
ORA-03136

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

  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-01655 : unable to extend cluster string.string by string in tablespace string
  • ora-13330 : invalid MASK
  • ora-00312 : online log string thread string: 'string'
  • ora-16655 : specified target standby database invalid
  • ora-00314 : log string of thread string, expected sequence# string doesn't match string
  • ora-13629 : The task or object string is being used by another operation.
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-31164 : cannot load object-relational XML attribute using direct path
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-13402 : the rasterType is null or not supported
  • ora-39065 : unexpected master process exception in string
  • ora-32005 : error while parsing size specification [string]
  • ora-09260 : sigpidu: error obtaining process id
  • ora-01666 : control file is for a standby database
  • ora-27039 : create file failed, file size limit reached
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • ora-21703 : cannot flush an object that is not modified
  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-29800 : invalid name for operator
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-24334 : no descriptor for this position
  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-30341 : dropped level has references
  • ora-13027 : unable to read dimension definition from string
  • ora-13908 : Invalid combination of metrics id and object type parameters.
  • ora-30355 : materialized view container does not exist
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-14643 : Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • 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.