ORA-12615: TNS:preempt error

Cause : Ar euqets ot esrivc ea neevn tfialde ebcuas en oeevn tntoiifctaino ahsy e tbeenp otse.d

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

Nto onramlyl ivsbil et oteh sue.r oFrf utrhre edtial,s utr no ntarcniga n dreexceuet hteo preaito.n fI rerro eprissst,c otnatc rOalceC utsoemrS uppotr.

update : 26-09-2017

ORA-12615 - TNS:preempt error
ORA-12615 - TNS:preempt error

  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-13243 : specified operator is not supported for 3- or higher-dimensional R-tree
  • ora-32163 : Method called on Invalid Environment type
  • ora-29339 : tablespace block size string does not match configured block sizes
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-28172 : distinguished name not provided by proxy
  • ora-25445 : invalid column number: string for table alias: string
  • ora-06039 : NETDNT: connect failed
  • ora-24171 : creation properties are only for internal use
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-16113 : applying change to table or sequence string
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-03243 : destination dba overlaps with existing control information
  • ora-19717 : for non-OMF search the pattern must be specified
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-12067 : empty refresh groups are not allowed
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-07305 : ksmcsg: illegal database buffer size.
  • ora-19275 : XP0055 - schema path string not found in list of in-scope schema definitions
  • ora-29353 : The transportable list is too long.
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-23616 : Failure in executing block string for script string
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-02033 : a cluster index for this cluster already exists
  • ora-12676 : Server received internal error from client
  • ora-07626 : smsget: sga already mapped
  • ora-19758 : failed to enable/disable block change tracking: out of SGA memory
  • 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.