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 : 25-04-2017

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-00721 : changes by release string cannot be used by release string
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-09830 : snyAddPort: failed to perform a remote procedure call.
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-04088 : error during execution of trigger 'string.string'
  • ora-01451 : column to be modified to NULL cannot be modified to NULL
  • ora-00306 : limit of string instances in this database
  • ora-32134 : Cannot assign LOBs
  • ora-01354 : Supplemental log data must be added to run this command
  • ora-02167 : LOGFILE clause specified more than once
  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-01924 : role 'string' not granted or does not exist
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-15130 : diskgroup "string" is being dismounted
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-32142 : maximum number of iterations exceeded
  • ora-13241 : specified dimensionality does not match that of the data
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-39119 : worker process interrupt for delete worker processes call by master process
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-02477 : can not perform parallel direct load on object string
  • ora-32634 : automatic order MODEL evaluation does not converge
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-14294 : Number of partitions does not match number of subpartitions
  • ora-16026 : parameter string contains an invalid attribute value
  • ora-38490 : invalid name: quotes do not match
  • 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.