ORA-12421: different size binary labels

Cause : The label sizes for the binary label operation were not equal.

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

Provide binary labels with the same lengths for the operation.

update : 24-07-2017
ORA-12421

ORA-12421 - different size binary labels
ORA-12421 - different size binary labels

  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-27102 : out of memory
  • ora-23348 : cannot replicate procedure string; only IN parameters supported
  • ora-27144 : attempt to kill process failed
  • ora-24142 : invalid ruleset name
  • ora-30163 : The thread safety initialization failed
  • ora-02209 : invalid MAXTRANS option value
  • ora-16636 : Fast-Start Failover target standby in error state, cannot stop observer
  • ora-10946 : trace name context forever
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-23609 : unable to find directory object for directory string
  • ora-19526 : only one location allowed for parameter string
  • ora-31608 : specified object of type string not found
  • ora-12419 : null binary label value
  • ora-38436 : attribute set used for an Expression set may not be modified.
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-29353 : The transportable list is too long.
  • ora-29393 : user string does not exist or is not logged on
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-24330 : internal OCI error
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-13231 : failed to create index table [string] during R-tree creation
  • ora-09988 : error while detaching SGA
  • ora-13332 : invalid LRS point
  • ora-14095 : ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-16416 : Switchover target is not synchronized with the primary
  • ora-12423 : invalid position specified
  • 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.