Some time after the blog called “There’s a little problem.”, I was still looking for some type of closure. The report from the hardware vendor doesn’t actually say anything of substance, well except – “It’s nowt to do with us mate”. I might as well point out that this wasn’t quite what we were looking for, but it was infact all we got from them.
Out of curiosity mainly, but there was also a need to have some kind of closure involved. I decided to try and investigate a little further, I did a little cruising on the vendors site – also through several support forums. All to little avail and although there were instances of people having similar problems, none actually matched.
There was one irrefutable fact here, the system had worked for the full day handling several million transactions without fault. Only when a change was made in a disk array did disaster strike, the report concluded that the action could not possibly have been the cause and that in fact the database had been corrupt all day. I’m sure that had the report been from the database vendor it would have read the other way round.
However on my return to one of the forums, there was a response to my query. Not the one that I expected – one from the vendor trying to find out who the customer was. Now I should have thought that if the vendor had only seen this once before they could have worked this out, but maybe I’m lending too much credence to the ability of the vendor in this matter.
Still I’m going to keep going with this and either prove or disprove my theory, perhaps I should respond – I know of several sites with the same or very similar configurations.