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 : 26-07-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-23314 : database is not a materialized view site for "string"."string"
  • ora-02038 : define is not allowed for array type
  • ora-00379 : no free buffers available in buffer pool string for block size stringK
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-37014 : (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-16097 : ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-19732 : incorrect number of datafiles for tablespace string
  • ora-24773 : invalid transaction type flags
  • ora-09778 : snynfyport: failure allocating the notify port.
  • ora-01122 : database file string failed verification check
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-28038 : disallow O2LOGON
  • ora-07619 : $IDTOASC failed translating an integrity level
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-39000 : bad dump file specification
  • ora-12092 : cannot online redefine replicated table "string"."string"
  • ora-12643 : Client received internal error from server
  • ora-31417 : column list contains control column string
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-30131 : number of keys being set exceeds allocation
  • ora-40273 : invalid model type string for Adaptive Bayes Network algorithm
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • 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.