ORA-27164: tried to join detached thread

Cause : The prorgam trie dto joina detachde thread.

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

This isa n interanl error ;contactO racle spuport.

update : 30-04-2017

ORA-27164 - tried to join detached thread
ORA-27164 - tried to join detached thread

  • ora-19586 : %s k-byte limit is too small to hold piece directory
  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-23477 : unable to alter propagation mode for object group "string"."string"
  • ora-00074 : no process has been specified
  • ora-13340 : a point geometry has more than one coordinate
  • ora-09938 : Save of signal handlers failed.
  • ora-12200 : TNS:could not allocate memory
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-13455 : GeoRaster metadata TRS error
  • ora-24784 : Transaction exists
  • ora-07589 : spdde: system ID not set
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-23439 : refresh group template already exists
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-09922 : Can't spawn process - background log directory not created properly
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-30567 : name already used by an existing log group
  • ora-15101 : no action specified
  • ora-00154 : protocol error in transaction monitor
  • ora-30645 : reject limit out of range
  • ora-23603 : STREAMS enqueue aborted due to low SGA
  • ora-32620 : illegal subquery within MODEL rules
  • ora-02227 : invalid cluster name
  • ora-02396 : exceeded maximum idle time, please connect again
  • ora-16021 : session string destination cannot be the same as session string destination
  • ora-00439 : feature not enabled: 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.