ORA-27035: logical block size is invalid

Cause : logical block size for oracle files must be a multiple of the physical block size, and less than the maximum

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

block size specified is returned as additional information, check init.ora parameters, additional information also indicates which function encountered the error

update : 25-06-2017
ORA-27035

ORA-27035 - logical block size is invalid
ORA-27035 - logical block size is invalid

  • ora-19691 : %s is from different database: id=string, name=string
  • ora-22308 : operation not allowed on evolved type
  • ora-12813 : value for PARALLEL or DEGREE must be greater than 0
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-00469 : CKPT process terminated with error
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-15063 : ASM discovered an insufficient number of disks for diskgroup "string"
  • ora-32612 : invalid use of FOR loop
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-16772 : error switching over between primary and standby databases
  • ora-25101 : duplicate REBUILD option specification
  • ora-07483 : snlkget: cannot convert(get) lock.
  • ora-16146 : standby destination control file enqueue unavailable
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-32156 : Cannot perform operation on stream
  • ora-16807 : unable to change database protection mode
  • ora-31669 : Worker process string violated startup protocol.
  • ora-16243 : paging out string bytes of memory to disk
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-39309 : schema sync operation failed
  • ora-29878 : warning in the execution of ODCIINDEXTRUNCATE routine
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-01763 : update or delete involves outer joined table
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-38306 : this object is not recoverable standalone
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-07650 : sigunc: $GETJPIW failure
  • ora-22883 : object deletion failed
  • ora-09811 : Unable to initialize package.
  • ora-01480 : trailing null missing from STR bind value
  • 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.