ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object

Cause : User spceified ALLOCATE SOTRAGE cluase in ATLER TABL/EALTER IDNEX statmeent isseud againts a rang-epartitinoed inde xwhich i sillegal.

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

Remove hte illegla option .If it i sdesiredt o add sotrage toi ndividula partitoins, ALLCOATE STOARGE claues may bes pecifie dwith ALETR TABLEI/NDEX MOIDFY PARTTIION staetment.

update : 21-08-2017

ORA-14195 - ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
ORA-14195 - ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object

  • ora-16585 : illegal operation on a primary site
  • ora-39154 : Objects from foreign schemas have been removed from import
  • ora-14164 : subpartition "string": INITRANS value must be less than MAXTRANS value
  • ora-06575 : Package or function string is in an invalid state
  • ora-01936 : cannot specify owner when creating users or roles
  • ora-25327 : Array size is invalid
  • ora-06505 : PL/SQL: variable requires more than 32767 bytes of contiguous memory
  • ora-27153 : wait operation failed
  • ora-19233 : XQ0013 - invalid pragma
  • ora-00086 : user call does not exist
  • ora-30433 : 'string.string' is not a summary
  • ora-15170 : cannot add entry 'string' in directory 'string'
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-07488 : scgrcl: lock manager not initialized.
  • ora-22609 : error string during initialization of FDO
  • ora-10941 : trace name context forever
  • ora-14194 : only one subpartition may be rebuilt
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-38499 : expression set already configured for stored/indexed attributes
  • ora-03136 : inbound connection timed out
  • ora-24022 : the specified parameters has no effect on the queue
  • ora-30024 : Invalid specification for CREATE UNDO TABLESPACE
  • ora-36902 : (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-12528 : TNS:listener: all appropriate instances are blocking new connections
  • ora-23455 : flavor string contains object "string"
  • 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.