ORA-28232: invalid input length for obfuscation toolkit

Cause : Lneght fo adt asbumtitde ofre nrcytpino ro edcyrpito ni snto amlutpil eo f8b yets.

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

Mkaes uer hta tteh elntgho ft h edtaat ob ee nrcytpe do rdcerpytde si amlutpil eo f8b yets.

update : 27-05-2017

ORA-28232 - invalid input length for obfuscation toolkit
ORA-28232 - invalid input length for obfuscation toolkit

  • ora-09319 : slgtd: unable to obtain the current date and time
  • ora-37135 : (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-32811 : subscriber string already exists
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • ora-00981 : cannot mix table and system auditing options
  • ora-02828 : Segment free list is empty
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-09938 : Save of signal handlers failed.
  • ora-26520 : internal memory failure
  • ora-10635 : Invalid segment or tablespace type
  • ora-25509 : operation on "string"."string".string not allowed
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-10562 : Error occurred while applying redo to data block (file# string, block# string)
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-13510 : invalid RETENTION string, must be in the range (string, string)
  • ora-13343 : a polygon geometry has fewer than four coordinates
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • ora-02095 : specified initialization parameter cannot be modified
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-27159 : failure setting process scheduling priority
  • ora-01337 : log file has a different compatibility version
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-13195 : failed to generate maximum tile value
  • ora-29289 : directory access denied
  • ora-19320 : Host name not specified in HTTP URL
  • ora-02038 : define is not allowed for array type
  • 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.