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 : 18-08-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-25964 : column type incompatible with join column type
  • ora-30752 : column or table string is not substitutable
  • ora-12019 : master table is a synonym to a remote object
  • ora-31600 : invalid input value string for parameter string in function string
  • ora-13047 : unable to determine ordinate count from table _SDOLAYER
  • ora-16529 : bad sender id
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-23309 : object string.string of type string exists
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-22151 : cannot resize non-zero variable-length array to zero elements
  • ora-10568 : Failed to allocate recovery state object: out of SGA memory
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-16813 : log apply service not running on apply instance string recorded by the broker
  • ora-02289 : sequence does not exist
  • ora-27373 : unknown or illegal event source queue
  • ora-01289 : cannot add duplicate logfile string
  • ora-29871 : invalid alter option for a domain index
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-28602 : statement not permitted on tables containing bitmap indexes
  • ora-00077 : dump string is not valid
  • ora-27059 : could not reduce file size
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-06977 : X.25 Driver: X.25 Level 2 failure
  • ora-26049 : Unscoped REF column has non-existent table name.
  • ora-01536 : space quota exceeded for tablespace 'string'
  • ora-22613 : buflen does not match the size of the scalar
  • ora-02783 : Both post and wait functions were not specified
  • ora-28027 : privileged database links may be used by global users
  • 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.