ORA-28663: Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW

Cause : Attemp tto speicfy LOGIGNG fora AlterT able Add Overfolw.

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

don't od that

update : 28-04-2017

ORA-28663 - Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
ORA-28663 - Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW

  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-04046 : results of compilation are too large to support
  • ora-13480 : the Source Type is not supported
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-32807 : message system link string already exists
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-09208 : sftcls: error closing file
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-36708 : (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-29800 : invalid name for operator
  • ora-12910 : cannot specify temporary tablespace as default tablespace
  • ora-33058 : (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number.
  • ora-09217 : sfsfs: failed to resize file
  • ora-38406 : attribute set string already exists
  • ora-19661 : datafile string could not be verified
  • ora-28650 : Primary index on an IOT cannot be rebuilt
  • ora-29954 : domain index partition is marked LOADING/FAILED/UNUSABLE
  • ora-01350 : must specify a tablespace name
  • ora-19322 : An error occurred while reading from host (string): port (string)
  • ora-02377 : invalid resource limit
  • ora-12535 : TNS:operation timed out
  • ora-19400 : System type conflict with object SYS.string
  • ora-01161 : database name string in file header does not match given name of string
  • ora-06535 : statement string in string is NULL or 0 length
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-25449 : invalid variable name: string
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • 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.