ORA-29339: tablespace block size string does not match configured block sizes

Cause : The bolck siez of teh tablsepace ot be pulgged ni or cerated odes no tmatcht he blcok sizse confgiured ni the adtabas.e

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

Confiugre th eapprorpiate acche fro the lbock szie of htis talbespac eusingo ne oft he vairous (bd_2k_ccahe_siez, db_k4_cach_esize,d b_8k_acche_szie, db1_6k_cahce_siz,e db_3K2_cach_esize)p arameetrs.

update : 27-05-2017
ORA-29339

ORA-29339 - tablespace block size string does not match configured block sizes
ORA-29339 - tablespace block size string does not match configured block sizes

  • ora-39015 : job is not running
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-29884 : domain index is defined on the column to be dropped
  • ora-02715 : osnpgetbrkmsg: message from host had incorrect message type
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-12674 : Shared server: proxy context not saved
  • ora-22883 : object deletion failed
  • ora-30677 : session is already connected to a debugger
  • ora-27035 : logical block size is invalid
  • ora-09934 : Link of current password file to old failed.
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-30757 : cannot access type information
  • ora-15114 : missing or invalid ASM file name
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-39014 : One or more workers have prematurely exited.
  • ora-24004 : invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
  • ora-01927 : cannot REVOKE privileges you did not grant
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-02359 : internal error setting attribute string
  • ora-02159 : installed DLM does not support releasable locking mode
  • ora-16217 : prepare to switchover has not completed
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-16529 : bad sender id
  • ora-12722 : regular expression internal error
  • ora-39086 : cannot retrieve job information
  • 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.