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-04-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-14013 : duplicate partition name
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-24233 : argument passed to DBMS_UTILITY.VALIDATE is not legal
  • ora-06408 : NETCMN: incorrect message format
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-39029 : worker string with process name "string" prematurely terminated
  • ora-31640 : unable to open dump file "string" for read
  • ora-04078 : OLD and NEW values cannot be identical
  • ora-10997 : another startup/shutdown operation of this instance inprogress
  • ora-01482 : unsupported character set
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-29741 : IMR active for some, but not all members of cluster
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-29859 : error occurred in the execution of ODCIINDEXTRUNCATE routine
  • ora-01026 : multiple buffers of size > 4000 in the bind list
  • ora-16121 : applying transaction with commit SCN string
  • ora-28358 : improper set key syntax
  • ora-39208 : Parameter string is invalid for string jobs.
  • ora-16151 : Managed Standby Recovery not available
  • ora-29818 : column name not properly specified
  • ora-12461 : undefined level string for policy string
  • ora-12096 : error in materialized view log on "string"."string"
  • ora-16620 : one or more databases could not be contacted for a delete operation
  • ora-29851 : cannot build a domain index on more than one column
  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-38469 : invalid privilege for an expression set: string
  • ora-12490 : DBHIGH cannot be lowered
  • ora-27156 : request for process information failed
  • ora-24192 : the property name cannot be null
  • ora-16090 : archive log to be replaced not created by managed standby process
  • 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.