writing log file after aborting job

stivazzi · Post by **stivazzi** » Fri Jun 23, 2006 2:18 am

Good morning to everyone... i have a job, starting in parallel mode and then calling a server shared container which writes on 3 tables with "enable transaction grouping". to rollback all the tables i call UtilityAbortToLog (please don't tell me i can't use it in production, i MUST rollback, and it's the only way i found!)... the problem is that i have to save log (or rejected records) in a file to be sent to the user...and the system rollbacks even the file :D
how can i do?

ArndW · Post by **ArndW** » Fri Jun 23, 2006 2:48 am

On of the options when writing to a sequential file is "cleanup on failure" and that defaults to "true". If you change that value the file won't be removed upon job failure.

ray.wurlod · Post by **ray.wurlod** » Fri Jun 23, 2006 3:57 am

Split the job so that rows are written to a staging area (text files) by one job, then loaded (server job?) from those. That way you have preserved the data to be loaded even in cases where you need to rollback.

You can monitor the load in your load job so that, if you want to restart from a known point (say 50,000 rows have been committed) you can restart the recovery load from row number 50,001.