ORA-12405: invalid label list

Cause : Thep oliyc deetrmiend taht teh laebl lsit wsa inavlidf or tis itnendde us.e

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

Chekc th epolciy cnostriantso n teh spceifi clis tof albel.s

update : 26-05-2017
ORA-12405

ORA-12405 - invalid label list
ORA-12405 - invalid label list

  • ora-31671 : Worker process string had an unhandled exception.
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-07588 : spdcr: $GETJPIW get image name failure
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-02054 : transaction string in-doubt
  • ora-38748 : cannot flashback data file string - file is in use or recovery
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-13261 : geometry table string does not exist
  • ora-13426 : invalid window parameter for subset operation
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-27047 : unable to read the header block of file
  • ora-24340 : cannot support more than 255 columns
  • ora-31210 : DBMS_LDAP: PL/SQL - LDAP get_dn error.
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-12926 : FORCE LOGGING option already specified
  • ora-36871 : (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
  • ora-19681 : block media recovery on control file not possible
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-14645 : STORE IN clause cannot be specified for Range List objects
  • ora-06592 : CASE not found while executing CASE statement
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered 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.