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

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

  • ora-16076 : unknown standby database destination
  • ora-13909 : Invalid combination of threshold value and operator.
  • ora-09351 : Windows 32-bit Two-Task driver unable to allocate shared memory
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-30337 : multiple JOIN KEY clauses specified for the same parent level
  • ora-02180 : invalid option for CREATE TABLESPACE
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-25405 : transaction status unknown
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-06310 : IPA: Environment variable(s) not set
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-01048 : Couldn't find the specified procedure in the given context
  • ora-32809 : foreign queue string is already registered
  • ora-31614 : routine string received this error from string: string
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-30956 : invalid option for XML Index
  • ora-06777 : TLI Driver: error reading parms
  • ora-01873 : the leading precision of the interval is too small
  • ora-12408 : unsupported operation: string
  • ora-39771 : stream must be loaded before its handle is freed
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-06117 : NETTCP: unable to create ORASRV: quota exceeded
  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-32006 : %s initialization parameter has been deprecated
  • ora-12432 : LBAC error: string
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • 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.