ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table

Cause : User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal.

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

Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.

update : 26-06-2017
ORA-14065

ORA-14065 - ALLOCATE STORAGE may not be specified for a partitioned table
ORA-14065 - ALLOCATE STORAGE may not be specified for a partitioned table

  • ora-22280 : no more buffers available for operation
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-16094 : database shutdown during archival operation
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-14276 : EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
  • ora-13451 : GeoRaster metadata scaling function error
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-28578 : protocol error during callback from an external procedure
  • ora-02203 : INITIAL storage options not allowed
  • ora-10701 : Dump direct loader index keys
  • ora-22319 : type attribute information altered in ALTER TYPE
  • ora-16619 : health check timed out
  • ora-23331 : column group string does not exist
  • ora-19734 : wrong creation SCN - control file expects converted plugged-in datafile
  • ora-02899 : smscre: Cannot create SGA with Extended Shared Memory feature
  • ora-31084 : error while creating table "string"."string" for element "string"
  • ora-01162 : block size string in file header does not match configured block sizes
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-02206 : duplicate INITRANS option specification
  • ora-07756 : slemcf: fread failure
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-30132 : invalid key index supplied
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-14514 : LOCAL option not valid without subpartition name
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-30767 : OID type mismatch
  • ora-19957 : database should have no datafiles in unknown state
  • ora-14158 : too many subpartition descriptions
  • ora-10970 : backout event for bug 2133357
  • 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.