ORA-14522: Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]

Cause : A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object.

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

Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created.

update : 24-09-2017
ORA-14522

ORA-14522 - Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
ORA-14522 - Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]

  • ora-02453 : duplicate HASH IS specification
  • ora-13859 : Action cannot be specified without the module specification
  • ora-07204 : sltln: name translation failed due to lack of output buffer space.
  • ora-19618 : cannot name files after restoreValidate has been called
  • ora-07229 : slcpuc: error in getting number of CPUs.
  • ora-25229 : error on transformation of message string string
  • ora-01933 : cannot create a stored object using privileges from a role
  • ora-02220 : invalid MINEXTENTS storage option value
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-08464 : input raw decimal data contains more than 42 digits
  • ora-13220 : failed to compare tile with the geometry
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-19502 : write error on file "string", blockno string (blocksize=string)
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-22854 : invalid option for LOB storage index
  • ora-23352 : duplicate destination for deferred transaction
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-26735 : operation not allowed on the specified file group version
  • ora-31012 : Given XPATH expression not supported
  • ora-16154 : suspect attribute: string
  • ora-23409 : could not find an unused refresh group number
  • ora-13025 : polygon does not close
  • ora-12017 : cannot alter primary key mview 'string' to a rowid mview
  • ora-12422 : max policies exceeded
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-31076 : required attribute "string" not specified
  • ora-16524 : unsupported operation
  • ora-23336 : priority group string does not exist
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • 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.