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 : 29-05-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-09319 : slgtd: unable to obtain the current date and time
  • ora-13461 : the interleaving type is not supported
  • ora-13236 : internal error in R-tree processing: [string]
  • ora-32594 : invalid object category for COMMENT command
  • ora-26010 : Column string in table string is NOT NULL and is not being loaded
  • ora-02037 : uninitialized speed bind storage
  • ora-19706 : invalid SCN
  • ora-16758 : the specified apply instance is not running
  • ora-00337 : log file 'string' does not exist and no size specified
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-13766 : A ranking measure is required.
  • ora-09823 : device name is too long
  • ora-10630 : Illegal syntax specified with SHRINK clause
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-02710 : osnpop: fork failed
  • ora-25015 : cannot perform DML on this nested table view column
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • ora-30155 : An I/O Error occured during an OCIFile function call
  • ora-01779 : cannot modify a column which maps to a non key-preserved table
  • ora-02052 : remote transaction failure at string
  • ora-19625 : error identifying file string
  • ora-30115 : error when processing an environment variable
  • ora-19037 : XMLType result can not be a fragment
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-22604 : TDS handle already generated
  • ora-40216 : feature not supported
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-01338 : Other process is attached to LogMiner session
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-09350 : Windows 32-bit Two-Task driver unable to allocate context area
  • 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.