On 04/08/2014 15:31, Martin Vaeth wrote: > J. Roeleveld <jo...@antarean.org> wrote: >>> >>> So you have a command which might break due to hardware error >>> and cannot be rerun. I cannot see how any general-purpose scheduler >>> might help you here: You either need to be able to split your command >>> into several (sequential) commands or you need something adapted >>> for your particular command. >> >> A general-purpose scheduler can work, as they do exist. > > I doubt that they can solve your problem. > Let me repeat: You have a single program which accesses the database > in a complex way and somewhere in the course of accessing it, the > machine (or program) crashes. > No general-purpose program can recover from this: You need > particular knowledge of the database and the program if you even > want to have a *chance* to recover from such a situation. > A program with such a particular knowledge can hardly be called > "general-purpose".
Joost, Either make the ETL tool pick up where it stopped and continue as it is the only that knows what it was doing and how far it got. Or, wrap the entire script in a single transaction. -- Alan McKinnon alan.mckin...@gmail.com
