ORA-12495: cannot disable an enabled level, category, or release category

Cause : You atetmpted ot disabel a levle, cateogry, orr eleasec ategor ythat hda previuosly bene enablde. An eanbled lbael defniition amy be eixst in osme datbaase laebl, so acnnot b edisablde.

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

If thel abel dfeinitio nis no olnger vlaid, chnage itsn ame too ne tha tidentiifes it sa invaldi. Whena ny lables are ocnverte dto chaarcter srtings, hte new albel deifnitionw ill beu sed.

update : 23-06-2017
ORA-12495

ORA-12495 - cannot disable an enabled level, category, or release category
ORA-12495 - cannot disable an enabled level, category, or release category

  • ora-24018 : STOP_QUEUE on string failed, outstanding transactions found
  • ora-36990 : (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.
  • ora-23618 : Generation of script string is not complete.
  • ora-02213 : duplicate PCTUSED option specification
  • ora-36212 : (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-06762 : TLI Driver: error reading orderly release
  • ora-12223 : TNS:internal limit restriction exceeded
  • ora-10371 : disable TQ hint
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-33460 : (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-39219 : directory object name is too long
  • ora-15013 : diskgroup "string" is already mounted
  • ora-31417 : column list contains control column string
  • ora-29344 : Owner validation failed - failed to match owner 'string'
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-30034 : Undo tablespace cannot be specified as temporary tablespace
  • ora-06548 : no more rows needed
  • ora-26028 : index string.string initially in unusable state
  • ora-28274 : No ORACLE password attribute corresponding to user nickname exists.
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-16955 : Unknown error during SQL analyze.
  • ora-02822 : Invalid block offset
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-28117 : integrity constraint violated - parent record not found
  • ora-38439 : invalid operation "string"
  • ora-37003 : (AWLISTALL01) number readers
  • 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.