Page 2 of 2
Posted: Mon Sep 08, 2008 9:26 am
by thurmy34
Hi All
Just to let you know that the job didn't abort two days in a row without doing anything.
Maybe an another job in the production corrupt the hash directory.
Thanks
Posted: Mon Sep 08, 2008 9:34 am
by chulett
Right, which is what Ray suggested you look for if I recall correctly. Or it could be another process entirely - for example, on Windows servers we've seen Anti-Virus software do crap like this.
Posted: Fri Mar 13, 2009 4:52 am
by thurmy34
Hi All
I think i found why my hashed file was corrupt sometimes.
I did all by myself.
In my job control i made a mistake in the execution order.
So the job who read the hashed file start before the job who writes was finished.
It's in my opinion just a matter of seconds.
Posted: Fri Mar 13, 2009 4:55 am
by thurmy34
Hi All
I think i found why my hashed file was corrupt sometimes.
I did all by myself.
In my job control i made a mistake in the execution order.
So the job who read the hashed file start before the job who writes was finished.
It's in my opinion just a matter of seconds.
Posted: Fri Mar 13, 2009 1:15 pm
by ray.wurlod
Bonne chance!