1834646 Members
2060 Online
110069 Solutions
New Discussion

Re: I/O Error

 
brian_31
Super Advisor

I/O Error

when the oracle team tries to add a datafile they get this error

When we try to add a datafile we get the error as HP-UX error : 5: I/O error. any ideas?

this is the exact error..
ORA-19502: write error on file "/oracle/data/clud_35/clud.data35", blockno 6401 (blocksize=8192)
ORA-27072: skgfdisp: I/O error
HP-UX Error: 5: I/O error
Additional information: 6401
(2007-01-01 01.08.19)

please advise

Thanks

brian
5 REPLIES 5
A. Clay Stephenson
Acclaimed Contributor

Re: I/O Error

Errno 5 indicates an EIO. If you do a man 2
write, you will see that the write system call sets errno = 5 on a physical i/o error. This means that an i/o error occurred at the hardware level so check for a bad disk, cable, etc.
If it ain't broke, I can fix that.
Sandman!
Honored Contributor

Re: I/O Error

Check the syslog.log file as well for errors. The disk on which you are trying to create the datafile maybe bad alongwith other ones. syslog.log would tell you which disk devices are having I/O problems.
brian_31
Super Advisor

Re: I/O Error

now when i try to extend the filesystem i get this error.

vgcfgbackup:/etc/lvmtab is out of date with the running kernel: kernel indicates 12 disks for "/dev/data10";/etc/lvmtab has 11 disks. cannot proceed with the backup

are these related errors?

thanks

brian
Torsten.
Acclaimed Contributor

Re: I/O Error

Hi,

did you replace a disk already?

This message indicates very often a wrong replacement procedure.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Wouter Jagers
Honored Contributor

Re: I/O Error

What can you find out about the device mounted on /oracle/data/clud_35 ?

Does an lvdisplay -v of the lvol show anything fishy ? Also try diskinfo -v on the physical volumes.

Cheers
an engineer's aim in a discussion is not to persuade, but to clarify.