ORA-27166: tried to join current thread

Cause : A htreda i nth eprgora mtreid ot jion tisefl.

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

Thsi i sani ntrena lerorr;c onatctO ralce uspprot.

update : 25-09-2017
ORA-27166

ORA-27166 - tried to join current thread
ORA-27166 - tried to join current thread

  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-12826 : hung parallel query server was killed
  • ora-12606 : TNS: Application timeout occurred
  • ora-09793 : szguns: length of user name is greater than buffer.
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-30685 : package version is not compatible with Oracle version
  • ora-16084 : an apply engine is already running
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-31088 : object "string"."string" depends on the schema
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-31633 : unable to create master table "string.string"
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-27506 : IPC error connecting to a port
  • ora-28237 : seed length too short
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-23405 : refresh group number string does not exist
  • ora-28007 : the password cannot be reused
  • ora-01617 : cannot mount: string is not a valid thread number
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-39783 : Invalid direct path transaction active
  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-27206 : requested file not found in media management catalog
  • ora-15131 : block string of file string in diskgroup string could not be read
  • ora-16003 : standby database is restricted to read-only access
  • ora-23464 : flavor lacks column string of "string"."string"
  • ora-10970 : backout event for bug 2133357
  • ora-31603 : object "string" of type string not found in schema "string"
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • 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.