ORA-12476: least upper bound resulted in an invalid OS label

Cause : You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.

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

Consult your OS label management documentation for information on invalid label generation.

update : 21-07-2017

ORA-12476 - least upper bound resulted in an invalid OS label
ORA-12476 - least upper bound resulted in an invalid OS label

  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-01298 : conflicting dictionary option
  • ora-12317 : logon to database (link name string) denied
  • ora-01118 : cannot add any more database files: limit of string exceeded
  • ora-01370 : Specified restart SCN is too old
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-07552 : sftget: $GET failure
  • ora-30687 : session terminated by debugger
  • ora-30153 : An invalid File Object is passed to the OCIFile function
  • ora-13407 : invalid storage parameter
  • ora-27214 : skgfrsfe: file search failed
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-01544 : cannot drop system rollback segment
  • ora-02074 : cannot string in a distributed transaction
  • ora-32141 : get method does not match the type of the parameter
  • ora-28350 : cannot encrypt the specified column recorded in CDC synchronized change table
  • ora-22161 : type code [string] is not valid
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-14166 : missing INTO keyword
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-16769 : the physical standby database is open read-only
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-13519 : Database id (string) exists in the workload repository
  • ora-19575 : expected string blocks in file string, found string
  • ora-38794 : Flashback target time not in current incarnation
  • ora-02759 : Not enough request descriptors available
  • ora-01329 : unable to truncate required build table
  • ora-21600 : path expression too long
  • 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.