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 : 21-08-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-30023 : Duplicate undo tablespace specification
  • ora-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-10614 : Operation not allowed on this segment
  • ora-24332 : invalid object type
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-06901 : CMX: no local name assigned to local application
  • ora-09909 : Malloc of scratch buffer failed.
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-00449 : background process 'string' unexpectedly terminated with error string
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-07601 : spguno: $GETJPIW failure
  • ora-28302 : User does not exist in the LDAP directory service.
  • ora-07598 : spwat: $SETIMR failure
  • ora-06550 : line string, column string: string
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-03125 : client-server protocol violation
  • ora-13430 : the GeoRaster object has null attribute(s)
  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-27206 : requested file not found in media management catalog
  • ora-13114 : [string]_NODE$ table does not exist
  • ora-13340 : a point geometry has more than one coordinate
  • ora-06311 : IPA: Maximum number of servers reached
  • ora-29932 : the type being dropped is a statistics type
  • 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.