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-05-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-24126 : invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
  • ora-29902 : error in executing ODCIIndexStart() routine
  • ora-38312 : original name is used by an existing object
  • ora-23448 : duplicate user parameter value
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-14511 : cannot perform operation on a partitioned object
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-39219 : directory object name is too long
  • ora-33060 : (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0.
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-30181 : integer in argument index is not immediately followed by )
  • ora-38780 : Restore point 'string' does not exist.
  • ora-21603 : property id [string] is invalid
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-30106 : reserved for future use
  • ora-14636 : only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
  • ora-16606 : unable to find property "string"
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-19685 : SPFILE could not be verified
  • ora-24102 : invalid prefix for generate_job_name
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-27083 : waiting for async I/Os failed
  • ora-30465 : supplied run_id is not valid: string
  • ora-14264 : table is not partitioned by Composite Range method
  • ora-09218 : sfrfs: failed to refresh file size
  • ora-31617 : unable to open dump file "string" for write
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-12690 : Server Authentication failed, login cancelled
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • 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.