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 : 23-04-2017

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-19955 : only one open thread is allowed to change the DBID
  • ora-22616 : image is not of Oracle 8.1 format
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-22896 : cannot have both scope and referential constraint on REF column "string"
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-26753 : Mismatched columns found in 'string.string'
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-26520 : internal memory failure
  • ora-27369 : job of type EXECUTABLE failed with exit code: string
  • ora-19735 : wrong creation SCN - control file expects initial plugged-in datafile
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-01036 : illegal variable name/number
  • ora-01764 : new update value of join is not guaranteed to be unique
  • ora-19221 : XP0001 - XQuery static context component string not initialized
  • ora-02233 : invalid CLOSE mode
  • ora-15024 : discovered duplicately numbered ASM disk string
  • ora-01221 : data file string is not the same file to a background process
  • ora-27487 : invalid object privilege for a string
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-38029 : object statistics are locked
  • ora-30176 : invalid format code used in the format string
  • ora-02709 : osnpop: pipe creation failed
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-31161 : element or attribute "string" cannot be stored out of line
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-07618 : $IDTOASC failed translating a secrecy level
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-06953 : Not enough virtual memory
  • 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.