ORA-14520: Tablespace string block size [string] does not match existing object block size [string]

Cause : A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object's default tablespace (or one of the object's partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object's partitions/subpartitions.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Specify a tablespace of the same block size as the partitioned object.

update : 25-04-2017
ORA-14520

ORA-14520 - Tablespace string block size [string] does not match existing object block size [string]
ORA-14520 - Tablespace string block size [string] does not match existing object block size [string]

  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-08197 : Flashback Table operation is not supported on clustered tables
  • ora-06904 : CMX: no transport address available for remote application
  • ora-30571 : invalid SEGMENT SPACE MANAGEMENT clause
  • ora-21613 : key does not exist
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-26736 : Data Pump error
  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-13199 : %s
  • ora-29277 : invalid SMTP operation
  • ora-06616 : LU6.2 Driver: Attach to LU failed
  • ora-22275 : invalid LOB locator specified
  • ora-03124 : two-task internal error
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-13333 : invalid LRS measure
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-06957 : No SID is currently available
  • ora-07821 : sspsdn: SYS$DELLNM failure
  • ora-31497 : invalid value specified for first_scn
  • ora-06522 : %s
  • ora-37173 : null dimension source data
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-01905 : STORAGE keyword expected
  • ora-13380 : network not found
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-10361 : check buffer change vector count consistency
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-01620 : no public threads are available for mounting
  • 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.