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

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

  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-00024 : logins from more than one process not allowed in single-process mode
  • ora-38729 : Not enough flashback database log data to do FLASHBACK.
  • ora-24410 : scrollable cursor max size exceeded
  • ora-01324 : cannot add file string due to DB_ID mismatch
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-02363 : error reading from file: string
  • ora-01263 : Name given for file destination directory is invalid
  • ora-19728 : data object number conflict between table string and partition string in table string
  • ora-01697 : control file is for a clone database
  • ora-29830 : operator does not exist
  • ora-06746 : TLI Driver: cannot alloc t_call
  • ora-19111 : error during evaluation of the XQuery expression
  • ora-06520 : PL/SQL: Error loading external library
  • ora-19657 : cannot inspect current datafile string
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-38952 : Source database not compatible
  • ora-01301 : error writing to file during flat file build
  • ora-02829 : No segment of the proper size is available
  • ora-39034 : Table string does not exist.
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-01141 : error renaming data file string - new file 'string' not found
  • ora-19320 : Host name not specified in HTTP URL
  • ora-29330 : Source script length too big
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-33297 : (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.
  • ora-36271 : (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
  • ora-28347 : encryption properties mismatch
  • 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.