ORA-06124: NETTCP: timeout waiting for ORASRV

Cause : The ORACLE server process was started but failed to respond after N secs.

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

For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = which will come into effect the next time the SQL*Net TCP/IP server is started.

update : 24-08-2017
ORA-06124

ORA-06124 - NETTCP: timeout waiting for ORASRV
ORA-06124 - NETTCP: timeout waiting for ORASRV

  • ora-08004 : sequence string.NEXTVAL string stringVALUE and cannot be instantiated
  • ora-13186 : fixed tile size tessellation failed
  • ora-19241 : XP0021 - cast to type string failed
  • ora-30445 : workload queries not found
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-07703 : error in archive text: need '/' after device type
  • ora-25352 : no current transaction
  • ora-09883 : Two Task interface: oratab file does not exist
  • ora-30183 : invalid field width specifier
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-13061 : topology with the name string does not exist
  • ora-13416 : invalid geometry parameter
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-19620 : %s is not of string type
  • ora-31481 : change source string is not a HotLog change source
  • ora-00103 : invalid network protocol; reserved for use by dispatchers
  • ora-31626 : job does not exist
  • ora-06580 : Hash Join ran out of memory while keeping large rows in memory
  • ora-00251 : LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
  • ora-31021 : Element definition not found
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-32014 : error processing parameter "string" from the SPFILE restore image
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-07597 : spguns: $GETJPIW failure
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-13065 : cannot delete a child layer with a parent layer
  • 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.