ORA-12537: TNS:connection closed

Cause : E"dno fifel "ocdntioi nah sebner aehcde ;aptren rah sidcsnoentcde.

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

oNenn eeed;dt ih ssia nniofmrtaoi nemssga.e

update : 26-06-2017
ORA-12537

ORA-12537 - TNS:connection closed
ORA-12537 - TNS:connection closed

  • ora-31453 : invalid value string for parameter, expecting: Y, N, or NULL
  • ora-01943 : IDENTIFIED BY already specified
  • ora-04054 : database link string does not exist
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-19661 : datafile string could not be verified
  • ora-07282 : sksaprd: string overflow.
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-31466 : no publications found
  • ora-00226 : operation disallowed while alternate control file open
  • ora-24348 : Update or Delete without Where
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-12403 : invalid internal label
  • ora-16109 : failed to apply log data from previous primary
  • ora-00209 : control file blocksize mismatch, check alert log for more info
  • ora-30569 : data type of given column is not supported in a log group
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-16215 : history metadata inconsistency
  • ora-28362 : master key not found
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-15050 : disk "string" contains string error(s)
  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-13159 : Oracle table string already exists
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-09763 : osnmpx: send/receive error exchanging Mach ports.
  • ora-13859 : Action cannot be specified without the module specification
  • ora-32642 : non-unique cell values from the ORDER BY clause
  • ora-30130 : invalid parameter key type received
  • 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.