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 : 25-04-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-00705 : inconsistent state during start up; shut down the instance, then restart it
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-01988 : remote os logon is not allowed
  • ora-25111 : creation of BITMAP cluster indices is not supported
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-01085 : preceding errors in deferred rpc to "string.string.string"
  • ora-01577 : cannot add log file 'string' - file already part of database
  • ora-23468 : missing string string
  • ora-28523 : ORACLE and heterogeneous agent are incompatible versions
  • ora-03208 : partitioned type must be specified for a non-composite object
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-31627 : API call succeeded but more information is available
  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-19248 : XQ0028 - invalid node in document constructor
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-02286 : no options specified for ALTER SEQUENCE
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-22880 : invalid REF
  • ora-32738 : Hang analysis aborted due to failed memory copy
  • ora-08447 : syntax error in USAGE clause in mask options
  • ora-13348 : polygon boundary is not closed
  • ora-19810 : Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
  • ora-29703 : error occurred in global enqueue service operation
  • ora-09214 : sfdone: I/O error detected
  • ora-00706 : error changing format of file 'string'
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-25145 : allocation policy already specified
  • ora-00293 : control file out of sync with redo log
  • ora-38704 : Checksum error in flashback database log file header.
  • 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.