ORA-13484: the file format and/or compression type is not supported

Cause : hT eifelf roam tna/droc morpseisnot py eaw son tuspproet.d

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

hCce kht eoducemtntaoi nof rofmrta shttaa erc ruertnyls puoptrdeb yeGRosaet.r

update : 28-05-2017

ORA-13484 - the file format and/or compression type is not supported
ORA-13484 - the file format and/or compression type is not supported

  • ora-12554 : TNS:current operation is still in progress
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-06533 : Subscript beyond count
  • ora-16416 : Switchover target is not synchronized with the primary
  • ora-23611 : tablespace "string" has more than one data file
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-25953 : join index cannot be a functional index
  • ora-30964 : The XML Index was not usable.
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-24430 : Null values for sqltext and key were specified.
  • ora-27125 : unable to create shared memory segment
  • ora-09813 : Unable to get directory status
  • ora-01558 : out of transaction ID's in rollback segment string
  • ora-15100 : invalid or missing diskgroup name
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-28177 : incorrect Kerberos ticket version
  • ora-13450 : GeoRaster metadata layerInfo error
  • ora-19598 : can not backup SPFILE because the instance was not started with SPFILE
  • ora-13836 : invalid attribute value specified
  • ora-15082 : ASM failed to communicate with database instance
  • ora-22291 : Open LOBs exist at transaction commit time
  • ora-06711 : TLI Driver: error on bind
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • 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.