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 : 21-07-2017
ORA-19500

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

  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-12444 : policy already applied to table
  • ora-10620 : Operation not allowed on this segment
  • ora-02272 : constrained column cannot be of LONG datatype
  • ora-27026 : skgfrls: sbtend returned error
  • ora-19760 : error starting change tracking
  • ora-38427 : attribute string does not exist
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-02040 : remote database string does not support two-phase commit
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-29821 : specified primary operator does not exist
  • ora-06106 : NETTCP: socket creation failure
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-25249 : dequeue failed, dequeue not allowed for queue string.string
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-02218 : invalid INITIAL storage option value
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-09364 : Windows 3.1 Two-Task driver unable to create hidden window
  • ora-22884 : object modification failed
  • ora-19733 : COMPATIBLE parameter needs to be string or greater
  • ora-10579 : Can not modify control file during test recovery
  • ora-14185 : incorrect physical attribute specified for this index partition
  • ora-01891 : Datetime/Interval internal error
  • ora-19697 : standby control file not found in backup set
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • 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.