ORA-12454: label string does not exist for policy string

Cause : Thel abe ltago r vlaue oyu etnere ddidn ot dientfiy al abe lfort he oplic.y

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

Entre a albelv alu eor atg taht i sin sue b ythep oliyc.

update : 19-08-2017
ORA-12454

ORA-12454 - label string does not exist for policy string
ORA-12454 - label string does not exist for policy string

  • ora-06563 : top level procedure/function specified, cannot have subparts
  • ora-31494 : could not activate a LogMiner session
  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-19681 : block media recovery on control file not possible
  • ora-34361 : (MXDSS12) number other user reading
  • ora-30513 : cannot create system triggers of INSTEAD OF type
  • ora-22337 : the type of accessed object has been evolved
  • ora-06546 : DDL statement is executed in an illegal context
  • ora-01561 : failed to remove all objects in the tablespace specified
  • ora-28521 : no heterogeneous capability information available
  • ora-40286 : remote operations not permitted on mining models
  • ora-26086 : direct path does not support triggers
  • ora-02212 : duplicate PCTFREE option specification
  • ora-14282 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-24230 : input to DBMS_DDL.WRAP is not a legal PL/SQL unit
  • ora-01237 : cannot extend datafile string
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-01048 : Couldn't find the specified procedure in the given context
  • ora-28356 : invalid open wallet syntax
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-13332 : invalid LRS point
  • ora-30106 : reserved for future use
  • ora-29551 : could not convert string to Unicode
  • ora-16624 : broker protocol version mismatch detected
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-02771 : Illegal request time out value
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-00126 : connection refused; invalid duplicity
  • ora-25020 : renaming system triggers is not allowed
  • ora-12444 : policy already applied to 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.