ORA-14057: partition "string": sum of PCTUSED and PCTFREE may not exceed 100

Cause : thes um fo PCUTSEDa nd CPTFREE fo ra pratitoin wohse anme e(xplciitl yspeicfie dby hte uesr) si dipslayde int hism essgae ecxeed s100 .Not etha tif CPTUSDE an/dor CPTFREE vaules ofr tihs pratitoin wree nto spceifide exlpicilty, edfautl vaules ofr teh patritinoed atbleo r idnex owuldb e uesd. fI, i ntur,n deafultP CTUESD adn/orP CTFERE 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 as um fo PCUTSEDa nd CPTFREE fo rthep arttiiond oesn ot xecee d100

update : 28-04-2017

ORA-14057 - partition "string": sum of PCTUSED and PCTFREE may not exceed 100
ORA-14057 - partition "string": sum of PCTUSED and PCTFREE may not exceed 100

  • ora-28338 : cannot encrypt indexed column(s) with salt
  • ora-22318 : input type is not an array type
  • ora-07489 : scgrcl: cannot get lock status.
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-09775 : osnmrs: reset protocol error
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-07742 : slemop: $CONNECT failure
  • ora-10707 : Simulate process death for instance registration
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-12925 : tablespace string is not in force logging mode
  • ora-10641 : Cannot find a rollback segment to bind to
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-16809 : multiple warnings detected for the database
  • ora-37120 : MDX string is null
  • ora-25102 : PARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-24002 : QUEUE_TABLE string does not exist
  • ora-01209 : data file is from before the last RESETLOGS
  • ora-13001 : dimensions mismatch error
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-06305 : IPA: Illegal message type
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-06932 : CMX: error in local name
  • ora-38702 : Cannot update flashback database log file header.
  • ora-39091 : unable to determine logical standby and streams status
  • ora-12607 : TNS: Connect timeout occurred
  • ora-08179 : concurrency check failed
  • ora-29885 : domain index is defined on the column to be modified
  • 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.