Oracle Database Errors or Warnings from Error ORA-28665 to ORA-28674
ORA-28665: table and partition must have same compression attribute
Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition
Action: Make sure the compression attributes match If they don’t, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS
ORA-28666: option not allowed for an index on UROWID column(s)
Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s)
Action: Build the index without these options
ORA-28667: USING INDEX option not allowed for the primary key of an IOT
Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required.
Action: Remove the USING INDEX clause and specify all attributes directly for the table
ORA-28668: cannot reference mapping table of an index-organized table
Cause: An attempt to directly access the mapping table of an index-organized table
Action: Issue the statement against the parent index-organized table containing the specified mapping table.
ORA-28669: bitmap index can not be created on an IOT with no mapping table
Cause: User attempted to create a bitmap index on an index-organized table without a mapping table.
Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using ‘ALTER TABLE .. MOVE MAPPING TABLE’.
ORA-28670: mapping table cannot be dropped due to an existing bitmap index
Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexed.
Action: Drop the bitmap index(es) before dropping the mapping table.
ORA-28671: UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal.
Action: Issue a partition level operation with ALTER INDEX .. PARTITION .. UPDATE BLOCK REFERENCES
ORA-28672: UPDATE BLOCK REFERENCES may not be used on a global index
Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned index on a partitioned IOT and a global partitioned index on a non-partitioned IOT.
Action: Use online index [partition] rebuild to fix the block references
ORA-28673: Merge operation not allowed on an index-organized table
Cause: User attempted merge operation on an index-organized table. Merge is not supported on a IOT .
Action: Use updates and inserts on index-organized table .
ORA-28674: cannot reference transient index-organized table
Cause: An attempt was made to directly access a transient table created created on behalf of a index-organized table partition maintenance operation.
Action: Issue the statement against the associated permanent index-organized table.
Above are list of Oracle Database Errors or Warnings from Error ORA-28665 to ORA-28674 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.