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 : 21-08-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-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-00453 : backgroud process 'string' is dead
  • ora-40283 : missing cost matrix
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-38463 : invalid XML Tag list
  • ora-29873 : warning in the execution of ODCIINDEXDROP routine
  • ora-02701 : osnoraenv: error translating oracle image name
  • ora-06259 : NETNTT: cannot read from remote process
  • ora-08430 : raw data missing leading sign
  • ora-01937 : missing or invalid role name
  • ora-24508 : Buffer is not aligned correctly.
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-16239 : IMMEDIATE option not available without standby redo logs
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-09270 : szalloc: error allocating memory for security
  • ora-27063 : number of bytes read/written is incorrect
  • ora-38429 : invalid datatype for a stored attribute: string
  • ora-02766 : Invalid maximum of request descriptors
  • ora-22928 : invalid privilege on directories
  • ora-07346 : slnrm: normalized file name is too long
  • ora-10360 : enable dbwr consistency checking
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-12638 : Credential retrieval failed
  • ora-16119 : building transaction at SCN string
  • ora-36914 : (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and it's ancestor.
  • 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.