ORA-14452: attempt to create, alter or drop an index on temporary table already in use

Cause : An attempt was made to create, alter or drop an index on temporary table which is already in use.

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

All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions.

update : 23-06-2017
ORA-14452

ORA-14452 - attempt to create, alter or drop an index on temporary table already in use
ORA-14452 - attempt to create, alter or drop an index on temporary table already in use

  • ora-00215 : must be at least one control file
  • ora-31448 : invalid value for change_source
  • ora-32101 : cannot create OCI Environment
  • ora-13239 : sdo_dimensionality not specified during n-d R-tree creation
  • ora-14078 : you may not drop the highest partition of a GLOBAL index
  • ora-22629 : OCIAnyData is null
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-28583 : remote references are not permitted during agent callbacks
  • ora-29890 : specified primary operator does not have an index context
  • ora-27123 : unable to attach to shared memory segment
  • ora-29901 : function underlying operator binding does not exist
  • ora-12334 : database (link name string) is still open
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-23616 : Failure in executing block string for script string
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-39763 : stream must be completely loaded before it is reset
  • ora-23434 : master site string not known for object group
  • ora-39052 : cannot specify SKIP_CURRENT on initial start of a job.
  • ora-33219 : (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-35810 : (XSINPUTERR) The command has requested more input than was supplied in the command string.
  • ora-26054 : Direct Path Context prepared for a different mode than operation requested.
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-32742 : Hang analysis initialize failed
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-01142 : cannot end online backup - none of the files are in backup
  • 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.