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-06-2017

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

  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-16524 : unsupported operation
  • ora-24343 : user defined callback error
  • ora-12721 : operation cannot execute when other sessions are active
  • ora-30151 : File already exists
  • ora-32037 : unsupported use of LEVEL in membership condition
  • ora-12011 : execution of string jobs failed
  • ora-02381 : cannot drop PUBLIC_DEFAULT profile
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-40261 : input data for model build contains negative values
  • ora-16618 : response document of size "string" bytes is too large
  • ora-15060 : template "string" does not exist
  • ora-31088 : object "string"."string" depends on the schema
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-12583 : TNS:no reader
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-01540 : tablespace 'string' is not offline
  • ora-02784 : Invalid shared memory ID specified
  • ora-39113 : Unable to determine database version
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-13414 : invalid pyramid parameter
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-22981 : must specify a table/view having system generated OID
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-19287 : XP0017 - invalid number of arguments to function - string:string
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • 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.