I'd like to thank Ronald D. Bowman, Alan, and Raul Sossa S. for
their help.
I used scu utility (scu -f raw-device verify media) to scan
suspected disks and found NO bad blocks. It is consistent with "dia"
finding. The problem doesn't seem to be in the device itself as Alan and
Raul suggested. Raul thinks the corrupted DBfiles caused the error. I
passed his suggestion to our DBA. Thanks again.
Ying Xu
ITSS - System Management
email:ying.xu_at_telecheck.com
--------------------------------------------------
Original Message:
> Hi, Managers
>
> I got a DBA that complained that a bad disk was hit when he tried to
> rebuild
> indexes. His log file shows:
>
> ERROR at line 1:
> ORA-01114: IO error writing block to file 2044 (block # 49456)
> ORA-27072: skgfdisp: I/O error
> Digital Unix Error: 9: Bad file number
> Additional information: 49456
> Additional information: 1
> ORA-01114: IO error writing block to file 2044 (block # 49456)
> ORA-27072: skgfdisp: I/O error
> Digital Unix Error: 9: Bad file number
> Additional information: 49456
> Additional information: 1
>
> I did DEVEVENT disk analysis that didn't find any disk errors on that day.
> /var/adm/messages also didn't show anything.
>
> What's the command to look at bad blocks in Tru64 Unix?
>
> Could anybody guide me through
> this?
>
> Thanks.
>
> Ying Xu
> ITSS - System Management
> email:ying.xu_at_telecheck.com
>
Received on Fri Feb 04 2000 - 19:59:12 NZDT