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-05-2017
ORA-19500

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

  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-16051 : parameter string contains an invalid delay time
  • ora-24788 : cannot switch to specified transaction (server type)
  • ora-19638 : file string is not current enough to apply this incremental backup
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-00155 : cannot perform work outside of global transaction
  • ora-27062 : could not find pending async I/Os
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-32607 : invalid ITERATE value in MODEL clause
  • ora-08322 : scnmin: open/convert of bias lock failed
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-06528 : Error executing PL/SQL profiler
  • ora-39085 : cannot update job string for user string
  • ora-07404 : sfareq: Timeout occurred waiting for request to complete.
  • ora-16621 : database name for ADD DATABASE must be unique
  • ora-00262 : current log string of closed thread string cannot switch
  • ora-29302 : database is not open clone
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-16589 : Data Guard Connection process detected a network transfer error
  • ora-22912 : specified column or attribute is not a nested table type
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • ora-38724 : Invalid option to the FLASHBACK DATABASE command.
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-27399 : job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege
  • ora-02259 : duplicate UNIQUE/PRIMARY KEY specifications
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-25158 : Cannot specify RELY for foreign key if the associated primary key is NORELY
  • 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.