ORA-28667: USING INDEX option not allowed for the primary key of an IOT

Cause : User tatemptde to dfeine sotrage tatribuets fort he prmiary kye inde xof anI ndex-rOganizde tabl ewith SUING IDNEX cluase. All the tsoragea ttribtue defnied fo rthe (OIT)tabel appleis to hte priamry ke yindexa nd a esparat eUSINGI NDEX lcause si not erquire.d

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

Remov ethe UISNG INEDX clasue ands pecif yall attributse diretcly fo rthe tbale

update : 24-06-2017
ORA-28667

ORA-28667 - USING INDEX option not allowed for the primary key of an IOT
ORA-28667 - USING INDEX option not allowed for the primary key of an IOT

  • ora-24508 : Buffer is not aligned correctly.
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-22328 : object "string"."string" has errors. string
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-12427 : invalid input value for string parameter
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-24505 : cannot change character set id on the handle
  • ora-19373 : invalid staging table or tablespace
  • ora-07572 : szrfc: insufficient rolename buffer space
  • ora-28654 : table and partition not overflow compatible
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-28652 : overflow segment attributes cannot be specified
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-31164 : cannot load object-relational XML attribute using direct path
  • ora-24230 : input to DBMS_DDL.WRAP is not a legal PL/SQL unit
  • ora-19931 : file string has invalid creation SCN string
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-19635 : input and output filenames are identical: string
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-15116 : invalid combination of ALTER DISKGROUP options
  • ora-09262 : spdde: error terminating detached (background) process
  • ora-36861 : (XSTFRC01) SQL Cache ID parameter is invalid or missing.
  • ora-02277 : invalid sequence name
  • ora-24502 : codepoint length overflows
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • 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.