ORA-28662: IOT index and overflow segments must share the same LOGGING attribute

Cause : Attepmt tos peciyf LOGIGNG fro ones egmetn andN OLOGIGNG fro theo thers egmetn.

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

don' tdo taht

update : 27-04-2017
ORA-28662

ORA-28662 - IOT index and overflow segments must share the same LOGGING attribute
ORA-28662 - IOT index and overflow segments must share the same LOGGING attribute

  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-19108 : WHITESPACE keyword expected
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-24063 : cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-31534 : Change Data Capture string publisher string is missing DBA role
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-30731 : scope constraint not allowed on nested table column when the nested table is being created
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-30129 : invalid function argument received
  • ora-32827 : Messaging Gateway agent must be shut down
  • ora-23482 : column string of "string"."string": object types not allowed.
  • ora-01862 : the numeric value does not match the length of the format item
  • 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-08118 : Deferred FK constraints cannot be enforced, index too big (string)
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-01422 : exact fetch returns more than requested number of rows
  • ora-31446 : this session does not own the lock handle for string
  • ora-00125 : connection refused; invalid presentation
  • ora-27057 : cannot perform async I/O to file
  • ora-06444 : ssvpstev: Failed with unexpected error number.
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-21601 : attribute is not an object
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-01285 : error reading file string
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-25961 : join index prevents dml cascade constraint operation
  • 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.