ORA-13466: format not appropriate for specified compression method

Cause : The poeratoin falied bceauset he GoeRastre objcet ha dan ianpprorpiatet ype ro foramt fo rthe psecifeid copmressoin mehtod. hTe GeRoaste rtypeo r fomrat i snot uspporetd byt he sepcifide comrpessino.

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

Chec kthe odcumetnatio nfor hte aprpopritae GeRoaste rtype sand ofrmat sfor aech cmopresison mtehod.U se SOD_GEO.RchanegFormta to rtansfrom th eGeoRsater bojectt o ana pprorpiatef orma,t or paply naothe rcomperssio nmethdo.

update : 21-08-2017
ORA-13466

ORA-13466 - format not appropriate for specified compression method
ORA-13466 - format not appropriate for specified compression method

  • ora-13501 : Cannot drop SYSAUX tablespace
  • ora-01044 : size string of buffer bound to variable exceeds maximum string
  • ora-04051 : user string cannot use database link string.string
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-15114 : missing or invalid ASM file name
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-23335 : priority group string already exists
  • ora-00349 : failure obtaining block size for 'string'
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-29956 : warning in the execution of ODCIINDEXEXCHANGEPARTITION routine
  • ora-37118 : The OLAP API library was not preloaded.
  • ora-28290 : Multiple entries found for the same Kerberos Principal Name
  • ora-06904 : CMX: no transport address available for remote application
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-30072 : invalid time zone value
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-27163 : out of memory
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-32730 : Command cannot be executed on remote instance
  • ora-12918 : Invalid tablespace type for default permanent tablespace
  • ora-13387 : sdo_batch_size for array inserts should be in the range [number,number]
  • ora-08197 : Flashback Table operation is not supported on clustered tables
  • ora-16795 : database resource guard detects that database re-creation is required
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-15063 : ASM discovered an insufficient number of disks for diskgroup "string"
  • 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.