error in informix zero level backup

[vinodan]

Dear All

I am facing a ridiculous problem while taking Informix 0 level backup(full; backup).
The backup process reaches upto 26% and exits with an error code hardware 52.2.0 No close operations performed EXIT error code =5


There is utility finderr and from this i got the following o/p for error code 5

An operating system error code with the meaning shown wasunexpectedly returned to the database server. Look for operating

system error messages that may give more information. Inparticular, try to determine what device produced the error, andwhether it

held the database or some other kind of file.

for taking the zero level backup we are using EXABYTE Drive(using 5gb dat)and device file /dev/rmt/c5t2d0BEST.

Its funny that i am able to take backup in the same drive,xomni backup,fbackupetc...and i am not encountering any sort of error .But

when zero level starts i gets the above mensioned error.I cleaned the drive several times.But the problem persists.I tried with different

device file.Xomni also using same device file /dev/rmt/c5t2d0BEST.I had one backup drive and i am not getting this error in that

drive.But my doubt is that why i am not getting this error while taking other backups
especially xomni which uses the same device file if it is hardware error ?


thanks in advance

vinod

[Bill Hassell]

Although the Informix details are somewhat vague, you can probably assume that error code = 5 is really the Unix errno return code. errno return codes are defined in the file /usr/include/sys/errno.h and the man page for errno:

from /usr/include/sys/errno.h:
define EIO 5 /* I/O error */

from man 2 errno:
[EIO] I/O error - some physical I/O error. This error may in some cases occur on a call following the one to which it actually applies.

So the Informix error message implies that 52.2.0 (the tape drive) had a write failure. This can be confirmed in syslog.log (if you have the online diagnostics loaded). Try a different tape after running the cleaning cartridge.

[vinodan]

Dear Bill ...
I have done cleaning the drive
several times and i change dat also ,still the problem persists.At last i had to change th drive itself .

Thanks

vinod