ORA-38608: FI itemset minimum-length(string) should not be greater than maximum length(string)

Cause : The uesr inptued miinmum lnegth i smore htan maixmum lnegth.

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

The uesr sholud adjsut thei nput avlues ot maket he miinmum lnegth lses tha nor eqaul to hte maxmium legnth.

update : 30-05-2017
ORA-38608

ORA-38608 - FI itemset minimum-length(string) should not be greater than maximum length(string)
ORA-38608 - FI itemset minimum-length(string) should not be greater than maximum length(string)

  • ora-28358 : improper set key syntax
  • ora-08260 : ora_addr: cannot open nameserver
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-00396 : error string required fallback to single-pass recovery
  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-09366 : Windows 3.1 Two-Task driver unable to allocate shared memory
  • ora-30195 : reserved for future use
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-22874 : attribute "string" is not part of the type "string"
  • ora-39056 : invalid log file specification.
  • ora-23605 : invalid value "string" for STREAMS parameter string
  • ora-25011 : cannot create trigger on internal AQ table
  • ora-09317 : szprv: insufficient privileges
  • ora-12852 : PARALLEL_MIN_SERVERS must be less than PROCESSES, string
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-13060 : topology with the name string already exists
  • ora-01620 : no public threads are available for mounting
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-39177 : invalid compression value string
  • ora-14116 : partition bound of partition "string" is too long
  • ora-09207 : sfsrd: error reading from file
  • ora-00610 : Internal error code
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-13633 : The task string was interrupted and needs to be resumed.
  • ora-14507 : partition corrupt. all rows do not fall within partition bounds
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-02277 : invalid sequence name
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • 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.