ORA-29380: resource plan string is currently active and cannot be deleted

Cause : A nattepmtw a smdaet od eelt ea natciev lpa ni nteh epnidn gaera .N ocahnegsc a nb emdaet oa citv epaln.s

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

Dleeet htep lna hwe ni ti snto ni sue.

update : 25-04-2017

ORA-29380 - resource plan string is currently active and cannot be deleted
ORA-29380 - resource plan string is currently active and cannot be deleted

  • ora-23396 : database link "string" does not exist or has not been scheduled
  • ora-10620 : Operation not allowed on this segment
  • ora-16198 : Timeout incurred on internal channel during remote archival
  • ora-09952 : scgcmn: lk_open_convert unexpected return: open failed
  • ora-31661 : there are no metadata transform values of type VARCHAR2
  • ora-14094 : invalid ALTER TABLE EXCHANGE PARTITION option
  • ora-38306 : this object is not recoverable standalone
  • ora-39177 : invalid compression value string
  • ora-19625 : error identifying file string
  • ora-24142 : invalid ruleset name
  • ora-12920 : database is already in force logging mode
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-22283 : filename contains characters that refer to parent directory
  • ora-01058 : internal New Upi interface error
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-13900 : missing or invalid parameter string
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-24280 : invalid input value for parameter string
  • ora-09744 : smsget: mmap returned an error.
  • ora-12414 : internal LBAC error: string Error: string
  • ora-01259 : unable to delete datafile string
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-01660 : tablespace 'string' is already permanent
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-15010 : name is already used by an existing ASM disk
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-02311 : cannot alter with COMPILE option a valid type with type or table dependents
  • 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.