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

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

  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • ora-14165 : MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
  • ora-23408 : this replication operation is not supported in a mixed configuration
  • ora-02203 : INITIAL storage options not allowed
  • ora-12056 : invalid REFRESH method
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-37153 : unknown exception caught: (case string)
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-28116 : insufficient privileges to do direct path access
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-01565 : error in identifying file 'string'
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-38950 : Source platform string not cross platform compliant
  • ora-06400 : NETCMN: No default host string specified
  • ora-30183 : invalid field width specifier
  • ora-16509 : the request timed out
  • ora-24292 : no more tables permitted in this sorted hash cluster
  • ora-31092 : invalid SQL name "string"
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-01217 : logfile member belongs to a different logfile group
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-14013 : duplicate partition name
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-25351 : transaction is currently in use
  • ora-12538 : TNS:no such protocol adapter
  • ora-16151 : Managed Standby Recovery not available
  • ora-12537 : TNS:connection closed
  • 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.