| There are at least a couple possible problems with Rdb and erasing data
in files. The erase pattern bbuffer is one common problem. To find
out if the erase pattern buffer is corrupt on the system, Have the
customer use ANALYSE/SYSTEM and issue the command
SDA> exa @exe$gl_erasepb;2000
It should show something like "Zeros suppressed from 80304000 through
80305FFF". If anything else, then the customer has the problem. There
is supposed to be a patch around (for one of the SCSI drivers; I don't
recall the name of the patch or the driver; search around in STARS for
it).
Otherwise, make sure that you've got the rest of the available VMS
patches installed, along with the current version of Open3D (if open3d
is installed, make sure that it is version 3.4 or later), if POLYCENTER
Performance Data Collector is installed, make sure that it is at least
version V2.2 and audit any disk controllers/devices to make sure that
they are up to rev.
|
|
There was a problem found recently in one of the SCSI port drivers (in
SYS$PKQDRIVER, specifically), and the problem effectively "corrupts"
the EXE$GL_ERASEPB erase pattern buffer.
See VMSZOO::RMS_OPENVMS note 2981.*, among other discussions.
If the patch kit is not available yet, log an IPMT.
(Note that the Rdb conference is located at ORAREP::NOMAHS::RDB_60.)
|