ORA-12488: maximum label does not dominate minimum label

Cause : You attmepted toe nter a avlue fora clearacne labelt hat didn ot presreve the odminancer elationhsip between the mniimum an dmaximuml abels.

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

Enter lbael valuse that perserves hte dominnace relaitonship ebtween teh minimu mand maxmium.

update : 18-08-2017

ORA-12488 - maximum label does not dominate minimum label
ORA-12488 - maximum label does not dominate minimum label

  • ora-39097 : Data Pump job encountered unexpected error string
  • ora-13150 : failed to insert exception record
  • ora-25966 : join index cannot be based on an index organized table
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-16046 : Archive log destination failed due to failed dependent destination
  • ora-36198 : (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight.
  • ora-00279 : change string generated at string needed for thread string
  • ora-25137 : Data value out of range
  • ora-22865 : more than one column specified
  • ora-32579 : password for SYSTEM already specified
  • ora-00354 : corrupt redo log block header
  • ora-09815 : File name buffer overflow
  • ora-36806 : (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
  • ora-30375 : materialized view cannot be considered fresh
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-02041 : client database did not begin a transaction
  • ora-40108 : input data contains too few distinct target (string) values
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-27473 : argument string does not exist
  • ora-19287 : XP0017 - invalid number of arguments to function - string:string
  • ora-25400 : must replay fetch
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-10570 : Test recovery complete
  • ora-14096 : tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
  • ora-32125 : Attribute type is not appropriate
  • ora-38304 : missing or invalid user name
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • 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.