topic Re: i/o error while working with database in Operating System - HP-UX

i/o error while working with database

so_2 — Fri, 18 Aug 2006 03:46:32 GMT

Hi all

My client is using a RIMS database and he encountered i/o issues with the server.
17:20:19 SRV 3: bkioRead:Unknown O/S error during Read, errno 5, fd 27, len
8192, offset 594255872, file /db06/PROD.rimsmod/db/rimsmod_11.d3. (6092)

#define EIO 5 /* I/O error

Suspecting this related with harddisk I checked the disks /logical volumes/ etc . But there are no probles found.
No trace were logged to syslog about any kind of i/o error.
The top is showing a helthy system, virtual memory operations are fine and bdf shows a pretty good amount of free space in all filesystems.

My client agreed to run the effected process again, to give me a chance to observe it online.

Could you all gurus give me the methods should be used to turn on maximum of diagnosing eg: configuring ems etc ..

Also will it be fine if i gave maximum importants to hard disks.

Thanks in advance
S.O

Re: i/o error while working with database

RAC_1 — Fri, 18 Aug 2006 03:52:31 GMT

If the error massge gives file name, you can try running following and see is you are able to read a file. Else you can also do full check on that file system and then on disk.
dd if=/path/file_name of=/dev/null
dd if=/FS_name of=/dev/null
dd if=/dev/rdsk/cxtxdx of=/dev/null bs=8k

Also Do you everything ok when you do vgdisplay and lvdisplay for that lvol?

And check disks invloved with STM.

Re: i/o error while working with database

Steven E. Protter — Fri, 18 Aug 2006 05:37:03 GMT

Shalom,

This could have been caused by the system temporarily being very busy and the disk response exceeding the tolerance for delay of the database application.

More than likely mstm,cstm, or xstm is going to show a problem with the disk. I strongly suggest you make sure this data backup is workng well because there may be trouble ahead.

SEP

Re: i/o error while working with database

Bill Hassell — Fri, 18 Aug 2006 09:27:24 GMT

This appears to be a duplicate of another post about block corruption. The important error messgae here is: error 5 which is a Unix errno number meaning I/O error. For disks, it means that the disk is bad and cannot be fixed except to replace it. fsck and database repairs cannot repair the damage (which is probably mechanical due to a head crash, or electrical due to flakey electronics) because the data is unreadable.