ORA-19500: device block size string is invalid

Cause : the device block size returned by sequential I/O OSD is invalid

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

If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.

update : 26-04-2017

ORA-19500 - device block size string is invalid
ORA-19500 - device block size string is invalid

  • ora-40289 : duplicate attributes provided for data mining function
  • ora-13222 : failed to compute supercell for geometry in string
  • ora-15169 : destination 'string' is a subdirectory of 'string'
  • ora-01336 : specified dictionary file cannot be opened
  • ora-32050 : %s operation failed
  • ora-31493 : could not prepare session for LogMiner session
  • ora-36185 : (XSAGGR11) workspace object does not have any AGGCOUNT information.
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-23452 : flavor string of object group "string"."string" is already published
  • ora-39773 : parse of metadata stream failed
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-13785 : missing target object for tuning task "string"
  • ora-01880 : the fractional seconds must be between 0 and 999999999
  • ora-13437 : GeoRaster metadata blocking error
  • ora-01585 : error identifying backup file string
  • ora-25142 : default storage clause specified twice
  • ora-30980 : Invalid Input.
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-08436 : raw data has invalid sign digit
  • ora-37150 : line string, column string, string
  • ora-01128 : cannot start online backup - file string is offline
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-19734 : wrong creation SCN - control file expects converted plugged-in datafile
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-27471 : window "string.string" is already closed
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-13432 : GeoRaster metadata blankCellValue error
  • ora-31498 : description and remove_description cannot both be specified
  • ora-12472 : policy string is being used
  • 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.