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 : 22-09-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-25011 : cannot create trigger on internal AQ table
  • ora-10259 : get error message text from remote using explicit call
  • ora-33557 : (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.
  • ora-06304 : IPA: Message receive error
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-38418 : ADT associated with the attribute set string does not exist
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-10931 : trace name context forever
  • ora-39134 : Cannot include "string" tablespace as a Transportable Tablespace
  • ora-31085 : schema "string" already registered
  • ora-28528 : Heterogeneous Services datatype conversion error
  • ora-02215 : duplicate tablespace name clause
  • ora-24909 : call in progress. Current operation cancelled
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-28536 : error in processing Heterogeneous Services initialization parameters
  • ora-02728 : osnfop: access error on oracle executable
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-16247 : DDL skipped on internal schema
  • ora-01227 : log string is inconsistent with other logs
  • ora-14287 : cannot REBUILD a partition of a Composite Range partitioned index
  • ora-29655 : USING clause is incompatible with its supertype
  • ora-38722 : ON or OFF expected.
  • ora-16140 : standby online logs have not been recovered
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-24155 : rule string.string not in rule set string.string
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-38743 : Time/SCN is in the future of the database.
  • ora-10644 : SYSTEM tablespace cannot be default temporary tablespace
  • ora-06114 : NETTCP: SID lookup 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.