ORA-14521: 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 partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-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 default tablespace 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 partitions/subpartitions being created.

update : 27-04-2017

ORA-14521 - Default tablespace string block size [string] for string string does not match existing string block size [string]
ORA-14521 - Default tablespace string block size [string] for string string does not match existing string block size [string]

  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-15183 : ASMLIB initialization error [string]
  • ora-29865 : indextype is invalid
  • ora-31227 : DBMS_LDAP: invalid LDAP MESSAGE handle
  • ora-24146 : rule string.string already exists
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-16125 : large transaction string string string is waiting for more data
  • ora-16642 : db_unique_name mismatch
  • ora-31467 : no column found in the source table
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-13526 : baseline (string) does not exist
  • ora-00018 : maximum number of sessions exceeded
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-02257 : maximum number of columns exceeded
  • ora-40109 : inconsistent logical data record
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-30555 : global index partitioning key is an expression
  • ora-19921 : maximum number of string rows exceeded
  • ora-12045 : invalid ALTER MATERIALIZED VIEW LOG option
  • ora-27024 : skgfqsbi: sbtinit2 returned error
  • ora-16772 : error switching over between primary and standby databases
  • ora-00341 : log string of thread string, wrong log # string in header
  • ora-06570 : shared pool object does not exist, cannot be pinned
  • ora-03240 : User's temporary tablespace same as tablespace being migrated
  • ora-30115 : error when processing an environment variable
  • ora-01122 : database file string failed verification check
  • ora-13764 : Value "string" is illegal as a result percentage.
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-24305 : bad bind or define context
  • 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.