Hi Gurus, I am not sure what is the issue with our job running for 3 hours and aborting with code 141 error. This job does not retrieve any rows from the database, basically it just hangs and then timeouts. We are using an odbc stage which extracts from db2 database and writes to a file. The same jo...
The job was started by designer -- which takes no limit by default.
So when we use dsjob utility, DataStage uses job control and we can set limits by -warn <no of warnings>. What is the default if we do not specify -warn option?
I would like to know why a job is not aborting after throwing more than 50 warning messages.
The warning settings are abort job after 50 warnings.
Appreciate any help. Thanks
auto purge setting will only work for new jobs that have auto-purge enabled before they are created. For existing jobs you can export/import them to enable auto purge setting.
Hi, the Db2 Load utility writes directly to the storage (containers) and does not use the SQL insert. Therefore the data can not be commited until the load utility finishes. BUT there is an option SAVECOUNT which implements consistency points - similar to commit but not on a SQL basis. So SAVECOUNT...