ORA-17501: logical block size string 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

check INIT.ORA file parameters

update : 28-05-2017

ORA-17501 - logical block size string is invalid
ORA-17501 - logical block size string is invalid

  • ora-25182 : feature not currently available for index-organized tables
  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-29818 : column name not properly specified
  • ora-13138 : could not determine name of object string
  • ora-23438 : missing refresh group template
  • ora-07415 : slpath: allocation of memory buffer failed.
  • ora-35095 : (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.
  • ora-10572 : Test recovery canceled due to errors
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-16068 : redo log file activation identifier mismatch
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-06550 : line string, column string: string
  • ora-31484 : source database version must be at least or greater
  • ora-09775 : osnmrs: reset protocol error
  • ora-19715 : invalid format string for generated name
  • ora-14116 : partition bound of partition "string" is too long
  • ora-16083 : LogMiner session has not been created
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-00302 : limit of string logs exceeded
  • ora-29373 : resource manager is not on
  • ora-26519 : no memory available to allocate
  • ora-29760 : instance_number parameter not specified
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-25192 : invalid option for an index-organized table
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-16771 : failover to a physical standby database failed
  • ora-38415 : invalid name or datatype for the attribute: string
  • ora-01099 : cannot mount database in SHARED mode if started in single process mode
  • ora-07643 : smsalo: SMSVAR 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.