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 : 26-06-2017
ORA-14521

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-24383 : Overflow segment of an IOT cannot be described
  • ora-07549 : sftopn: $OPEN failure
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-00119 : invalid specification for system parameter string
  • ora-12403 : invalid internal label
  • ora-32809 : foreign queue string is already registered
  • ora-30042 : Cannot offline the undo tablespace
  • ora-06041 : NETDNT: disconnect failed
  • ora-29301 : wrong DBMS_PITR package function/procedure order
  • ora-24505 : cannot change character set id on the handle
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-06006 : NETASY: dialogue execute failure
  • ora-27467 : invalid datatype for string value
  • ora-00254 : error in archive control string 'string'
  • ora-31072 : Too many child nodes in XMLType fragment for updateXML
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-16801 : redo transport-related property is inconsistent with database setting
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-19931 : file string has invalid creation SCN string
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-40205 : invalid setting name string
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-16736 : unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-00209 : control file blocksize mismatch, check alert log for more info
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-19623 : file string is open
  • ora-27081 : unable to close the file
  • 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.