ORA-14058: partition number 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 nubmer p(arttiion saren umbreed tsartnig wtih 1 )is idsplyaed ni thsi message .Not etha tif NIITRNAS adn/orM AXTARNS avlue sfort hisp arttiionw eren ot pseciifed xepliictly ,defualt avlue sfort he aprtiitone dtabel ori nde xwoudl beu sed .If,i n trun, edfautl INTIRAN Sando/r MXATRASN vaules ofr teh patritinoed atbleo r idnex ewre ont sepcifeid, ysste mdefualtsw oul dbe sued.

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 : 26-05-2017

ORA-14058 - partition number string: INITRANS value must be less than MAXTRANS value
ORA-14058 - partition number string: INITRANS value must be less than MAXTRANS value

  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-04041 : package specification must be created first before creating package body
  • ora-31164 : cannot load object-relational XML attribute using direct path
  • ora-15131 : block string of file string in diskgroup string could not be read
  • ora-06745 : TLI Driver: listener already running
  • ora-26098 : direct path context is not prepared
  • ora-06750 : TLI Driver: sync failed
  • ora-02488 : Error encountered when accessing file [string] for trace conversion
  • ora-29286 : internal error
  • ora-00306 : limit of string instances in this database
  • ora-16759 : resource guard unable to start SQL Apply with initial SCN
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-01579 : write error occurred during recovery
  • ora-02020 : too many database links in use
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-07457 : cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
  • ora-01070 : Using an old version of Oracle for the server
  • ora-28656 : incomplete attribute specification
  • ora-14072 : fixed table may not be truncated
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-31012 : Given XPATH expression not supported
  • ora-15033 : disk 'string' belongs to diskgroup "string"
  • ora-12735 : Instant Client Light: unsupported client character set string
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-26079 : file "string" is not part of table string.string
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-34350 : (MXDSS06) string is an open analytic workspace.
  • ora-01193 : file string is not the same file seen at start of recovery
  • 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.