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 : 24-05-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-06106 : NETTCP: socket creation failure
  • ora-13281 : failure in execution of SQL statement to retrieve WKT
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-01922 : CASCADE must be specified to drop 'string'
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-07595 : sppid: $GETJPIW failure
  • ora-16072 : a minimum of one standby database destination is required
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-00313 : open failed for members of log group string of thread string
  • ora-24100 : error in ktz testing layer
  • ora-27061 : waiting for async I/Os failed
  • ora-27153 : wait operation failed
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-00293 : control file out of sync with redo log
  • ora-26742 : Maximum number of ignored transactions exceeded
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-01227 : log string is inconsistent with other logs
  • ora-30195 : reserved for future use
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-09985 : SGA definition file could not be read
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-30087 : Adding two datetime values is not allowed
  • ora-01905 : STORAGE keyword expected
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-19692 : missing creation stamp on piece string
  • ora-39206 : A parallel degree of string is invalid.
  • ora-06000 : NETASY: port open failure
  • 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.