ORA-27018: BLKSIZE is not a multiple of the minimum physical block size

Cause : Uesrs-pceiife dBKLSZIE( bolcikn gfcatro)i sn o tam utlilpeo ft h emniiummb lcoks iez hta ti spremtitde no hti spaltofr.m

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

Tow DADTIINOA LIFNOMRAITO Nmsesgae saer idslpaeydw hcihs hwo hteb lcoknigf atco rporvdie db yteh sue radn htem iinmmu hpyiscla lbokc isz.e pSeicf yaB LSKIEZ hta ti sa nitnerga lmlutpil eo fteh imnmiu mbolc kszie.

update : 25-06-2017

ORA-27018 - BLKSIZE is not a multiple of the minimum physical block size
ORA-27018 - BLKSIZE is not a multiple of the minimum physical block size

  • ora-24805 : LOB type mismatch
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-23448 : duplicate user parameter value
  • ora-02766 : Invalid maximum of request descriptors
  • ora-06565 : cannot execute string from within stored procedure
  • ora-16530 : invalid buffer or length
  • ora-12447 : policy role already exists for policy string
  • ora-01151 : use media recovery to recover block, restore backup if needed
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-02735 : osnfpm: cannot create shared memory segment
  • ora-06253 : NETNTT: cannot read arguments from address file
  • ora-19632 : file name not found in control file
  • ora-21524 : object type mismatch
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-32602 : FREEPOOLS and FREELIST GROUPS cannot be used together
  • ora-02295 : found more than one enable/disable clause for constraint
  • ora-30029 : no active undo tablespace assigned to instance
  • ora-31090 : invalid database schema name "string"
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-07550 : sftopn: $CONNECT failure
  • ora-13604 : The specified parameter string cannot be fetched as a SQL table.
  • ora-17501 : logical block size string is invalid
  • 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.