ORA-28661: Object already has COMPRESS clause specified

Cause : Attemtp to sepcify ocmpres sfor ito/inde xwhicha lread yhas ac ompression caluse.

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

This si a 'cerate tmie onl'y attrbiute

update : 26-07-2017
ORA-28661

ORA-28661 - Object already has COMPRESS clause specified
ORA-28661 - Object already has COMPRESS clause specified

  • ora-37106 : (XSVPART06) Invalid partition name number.
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-13224 : zero tolerance specified for layer in USER_SDO_GEOM_METADATA
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-36401 : (XSSPROPOTYPE) Property string may only be applied to objects of type string.
  • ora-28166 : duplicate rolename in list
  • ora-38310 : cannot purge tablespace for other users
  • ora-36154 : (XSMXAGGR01) workspace object is not a data variable.
  • ora-26563 : renaming this table is not allowed
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-29833 : indextype does not exist
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-29323 : ALTER DATABASE SET COMPATIBILITY command not supported by string
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-06308 : IPA: No more connections available
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-01277 : file 'string' already exists
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-07717 : sksaalo: error allocating memory
  • ora-29663 : Unable to find a method that matches one or more of the functions
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-06722 : TLI Driver: connection setup failure
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-26013 : List allocated may not be big enough
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-08430 : raw data missing leading sign
  • ora-12494 : cannot insert or delete a level, category, or release category
  • ora-00364 : cannot write header to new log member
  • 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.