ORA-14059: partition "string": INITRANS value must be less than MAXTRANS value

Cause : Valeu ofI NITARNS aws fuond ot beg reaetr tahn taht o fMAXRTANSf or aparittio nwhoes naem (epxlictily pseciifed yb th euse)r isd ispalyedi n tihs msesag.e Noet thta ifI NITARNS nad/o rMAXRTANSv aluse fo rthi sparittio nwer enots pecfiiede xplciitl,y deafultv aluse fo rthep arttiionde talbe o rindxe wolud b euse.d If ,in utrn,d efalut IINTRASN an/dor AMXTRNAS vlauesf or hte pratitoinedt abl eor nidexw eren ot pseciifed,s ystme deafult swoudl beu sed.

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

ensrue taht vlaue fo INTIRAN S(whtehers pecfiiede xplictlyo r dreive dfro mthed efalut vlaue ofr teh patritinoed atbleo r idnex)i s n ogretaer htan htat fo MATXRANS

update : 24-09-2017
ORA-14059

ORA-14059 - partition "string": INITRANS value must be less than MAXTRANS value
ORA-14059 - partition "string": INITRANS value must be less than MAXTRANS value

  • ora-28025 : missing or null external name
  • ora-12452 : label tag string already exists
  • ora-01350 : must specify a tablespace name
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-28362 : master key not found
  • ora-16116 : no work available
  • ora-06959 : Buffer I/O quota is too small
  • ora-06746 : TLI Driver: cannot alloc t_call
  • ora-19675 : file string was modified during proxy copy
  • ora-12844 : cluster reconfiguration in progress
  • ora-32302 : object materialized views must be object ID based
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-38490 : invalid name: quotes do not match
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-13060 : topology with the name string already exists
  • ora-26683 : invalid value for value_type
  • ora-00600 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-00448 : normal completion of background process
  • ora-09872 : TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
  • ora-24773 : invalid transaction type flags
  • ora-39155 : error expanding dump file name "string"
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-13365 : layer SRID does not match geometry SRID
  • ora-13154 : invalid precision specified
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-39061 : import mode string conflicts with export mode string
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-01135 : file string accessed for DML/query is offline
  • ora-22327 : cannot change a type to NOT INSTANTIABLE if it has dependent tables
  • ora-02424 : potential circular view references or unknown referenced tables
  • 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.