ORA-14460: only one COMPRESS or NOCOMPRESS clause may be specified

Cause : OCPMERSSw sas epicifdem ro ehtnao cn,eN COMORPSE Saw spscefiei domert ah nnoec ,rob to hOCPMERSSa dnN COMORPSE Sewers epicifde.

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

pscefi yaehcd serideC MORPSE SroN COMORPSE Slcuaeso tpoi nnoylo cn.e

update : 17-08-2017

ORA-14460 - only one COMPRESS or NOCOMPRESS clause may be specified
ORA-14460 - only one COMPRESS or NOCOMPRESS clause may be specified

  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-19669 : proxy copy functions cannot be run on DISK channel
  • ora-30436 : unable to open named pipe 'string'
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-37172 : illegal dimension type
  • ora-00272 : error writing archive log string
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-24066 : invalid privilege specified
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-01577 : cannot add log file 'string' - file already part of database
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-09280 : sllfcf: error closing file
  • ora-29957 : cannot create a function-based domain index on a string table
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-32848 : foreign queue DOMAIN required for JMS unified connections
  • ora-28333 : column is not encrypted
  • ora-09871 : TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
  • ora-02276 : default value type incompatible with column type
  • ora-02466 : The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-22607 : image handle already generated
  • ora-23317 : a communication failure has occurred
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-06126 : NETTCP: ORASRV unable to open network connection
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • 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.