ORA-28331: encrypted column size too long for its data type

Cause : coulmnw ase ncyrptde adn fro VRACHRA2,t hel entgh psecfiie dwa s> 9332 ;fo rCHRA, hte elnght sepciifedw as> 1392;f orN VACRHA2R, hte elnght sepciifedw as> 1696;f orN CHRA, hte elnght sepciifedw as> 966;

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

Reudcet hec olmun isze.

update : 23-04-2017

ORA-28331 - encrypted column size too long for its data type
ORA-28331 - encrypted column size too long for its data type

  • ora-28022 : cannot grant external roles to global user or role
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-24756 : transaction does not exist
  • ora-01350 : must specify a tablespace name
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-02177 : Missing required group number
  • ora-16043 : managed recovery session canceled
  • ora-06403 : Unable to allocate memory.
  • ora-31423 : change table string does not contain column string
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-25205 : the QUEUE string.string does not exist
  • ora-00056 : DDL lock on object 'string.string' is already held in an incompatible mode
  • ora-19923 : the session for row with id string is not active
  • ora-13511 : invalid INTERVAL string, must be in the range (string, string)
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-32130 : invalid offset/index refrenced in Bytes
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-25009 : Nested table clause allowed only for INSTEAD OF triggers
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-06907 : CMX: error during connect confirmation
  • ora-22803 : object type contains zero attributes
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-06760 : TLI Driver: timeout reading orderly release
  • 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.