ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object

Cause : Use rspeicfie dALLCOATES TORGAE calusei n ATLER ATBLEA/LTE RINDXE sttaemetn isused gaaints a arngep-arttiionde inedx wihch si ilelgal.

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

Remvoe teh ilelgalo ptino. I fit si deisredt o add stroaget o idniviudal aprtiitons ,ALLCOATES TORGAE calusem ay eb spceifide wiht ALETR TBALE/NIDEXM ODIYF PATRITINO sttaemetn.

update : 21-08-2017
ORA-14191

ORA-14191 - ALLOCATE STORAGE may not be specified for Composite Range partitioned object
ORA-14191 - ALLOCATE STORAGE may not be specified for Composite Range partitioned object

  • ora-02841 : Server died on start up
  • ora-02145 : missing STORAGE option
  • ora-12489 : default label not within clearance range
  • ora-27206 : requested file not found in media management catalog
  • ora-14051 : invalid ALTER MATERIALIZED VIEW option
  • ora-12056 : invalid REFRESH method
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-06566 : invalid number of rows specified
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-27146 : post/wait initialization failed
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-03001 : unimplemented feature
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-31099 : XDB Security Internal Error
  • ora-16805 : change of LogXptMode property violates overall protection mode
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-06953 : Not enough virtual memory
  • ora-16165 : LGWR failed to hear from network server
  • ora-24407 : connection pool already exists
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-00293 : control file out of sync with redo log
  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-32113 : Null object passed
  • 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.