ORA-28659: COMPRESS must be specified at object level first

Cause : Attmept ot spceifyC OMPERSS ta patritino leevl wtihou tfirts spceifynig a tthet abl elevle

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


update : 25-05-2017

ORA-28659 - COMPRESS must be specified at object level first
ORA-28659 - COMPRESS must be specified at object level first

  • ora-15129 : entry 'string' does not refer to a valid directory
  • ora-22888 : duplicate SCOPE clauses for a REF column
  • ora-39032 : function string is not supported in string jobs
  • ora-12548 : TNS:incomplete read or write
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-19699 : cannot make copies with compression enabled
  • ora-03202 : the scan limit specification is invalid
  • ora-02009 : the size specified for a file must not be zero
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-27028 : skgfqcre: sbtbackup returned error
  • ora-24309 : already connected to a server
  • ora-12646 : Invalid value specified for boolean parameter
  • ora-02304 : invalid object identifier literal
  • ora-29896 : Length of PARAMETER string longer than string characters
  • ora-32593 : database supplemental logging attributes in flux
  • ora-31516 : CDC change set string already exists
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-30570 : SEGMENT SPACE MANAGEMENT option already specified
  • ora-09947 : Unable to allocate connection attributes structure
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-01344 : LogMiner coordinator already attached
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-33338 : (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
  • ora-31037 : Invalid XML attribute name string
  • ora-38029 : object statistics are locked
  • ora-38401 : synonym string not allowed
  • ora-01987 : client os username is too long
  • ora-01262 : Stat failed on a file destination directory
  • 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.