ORA-27004: invalid blocksize specified

Cause : internal error, blocksize specified is incorrect for the device on which file is being created, aditional information indicates blocksize specified, and the function that encountered the error

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

check for trace file and contact Oracle Support

update : 26-04-2017

ORA-27004 - invalid blocksize specified
ORA-27004 - invalid blocksize specified

  • ora-15054 : disk "string" does not exist in diskgroup "string"
  • ora-14190 : only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-25135 : cannot use the SINGLE TABLE option
  • ora-28522 : error initializing heterogeneous capabilities
  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-29662 : Unable to find a field that matches one or more of the attributes
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-01122 : database file string failed verification check
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-07700 : sksarch: interrupt received
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-15156 : cluster in rolling upgrade from version [string] to [string]
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-27461 : The value for attribute string is too large.
  • ora-31535 : cannot support change source string in this configuration
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-38410 : schema extension not allowed for the table name
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-30452 : cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
  • ora-38720 : Missing log file number.
  • ora-01686 : max # files (string) reached for the tablespace string
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-12920 : database is already in force logging mode
  • ora-07639 : smscre: SGA pad area not large enough (string bytes required)
  • ora-30686 : no dispatcher accepted TCP/IP connection request
  • 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.