ORA-14066: illegal option for a non-partitioned index-organized table

Cause : An attmept wasm ade toi ssue aC REATE ro ALTERT ABLE cmomand o na non-aprtitioend IOT,b ut thec ommandc ontain san optoin thati s lega lonly fro partiitoned idnex-orgnaized tbales. Scuh optinos are:E NABLE ORW MOVEEMNT andD ISABLER OW MOVMEENT.

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

Removet he illgeal optoin(s) form the ocmmand.

update : 30-04-2017

ORA-14066 - illegal option for a non-partitioned index-organized table
ORA-14066 - illegal option for a non-partitioned index-organized table

  • ora-19615 : some files not found in backup set
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-02307 : cannot alter with REPLACE option a type that is not valid
  • ora-19931 : file string has invalid creation SCN string
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • ora-09214 : sfdone: I/O error detected
  • ora-07578 : szprv: $FIND_HELD failure
  • ora-32576 : missing TYPE keyword
  • ora-16629 : database reports a different protection level from the protection mode
  • ora-12436 : no policy options specified
  • ora-00207 : control files are not for the same database
  • ora-26724 : only SYS is allowed to set the Capture or Apply user to SYS.
  • ora-36830 : (XSLMGEN00) AW name cannot be NA
  • ora-12431 : invalid audit action
  • ora-00740 : datafile size of (string) blocks exceeds maximum file size
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-01585 : error identifying backup file string
  • ora-06748 : TLI Driver: cannot allocate t_discon
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-09215 : sfqio: error detected in IOCompletionRoutine
  • ora-13837 : invalid HASH_VALUE
  • ora-29254 : Invalid lower_bound argument passed to procedure dbms_sql.define_array
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-06735 : TLI Driver: client failed to close error conn
  • ora-12028 : materialized view type is not supported by master site string
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-02191 : correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT
  • 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.