  File reporting SS$_FORCEDERROR (bad block)? 
 The Question is:
 
I've have provided the above error to our database experts and discussed it
 with VMS systems administrators and we agree that there is either a problem
 with the file itself or the blocks the file was written to on the disk drive.
 This error started to ap
pear after file was moved from a disk going bad to a new replacement disk. Our
 DB staff agree that they should move smaller files and then build file from
 within database application but they're question is, "does VMS have a file
 size limitation?"
 
 The Answer is :
 
  You have encountered a disk error; a bad block.
 
  This error and this behaviour is entirely unrelated to the file size.
 
  Please see topic (6926) for details of OpenVMS bad block handling.
 
  Please see the OpenVMS FAQ for discussions of the maximum file size.
 
  As should become obvious from topic (6926), you will want to seriously
  consider implementing host-based volume shadowing (mirroring) and/or RAID.
 Answer written or last revised on  1-NOV-2001 
