SQL1652N : File I/O error occurred

ray.wurlod · Post by **ray.wurlod** » Wed Jan 31, 2007 3:24 pm

There is no cure for stupidity.

What you can do is write them all to the same table (or even hashed file), using a generated key. Once all the runs are done, you can dump its contents to a single text file.

Or you can dump them to separate temporary text files (job parameter for its name perhaps) and cat them together when all the runs are done. Then delete the temporary files.

DSguru2B · Post by **DSguru2B** » Wed Jan 31, 2007 3:26 pm

Ray, I highly doubt we can do that for the message file and the command files created by the DB2 Bulk load.

ray.wurlod · Post by **ray.wurlod** » Wed Jan 31, 2007 3:32 pm

And I doubt that these are the ones where "single file" is being enforced.

If they are, the solution is simple. No more parallelism.

When "they" complain, the response is that it's the cost of stupidity.

DSguru2B · Post by **DSguru2B** » Wed Jan 31, 2007 3:36 pm

ray.wurlod wrote:When "they" complain, the response is that it's the cost of stupidity.

Read my footer quote

I_Server_Whale · Post by **I_Server_Whale** » Wed Jan 31, 2007 3:43 pm

DSguru2B wrote:
ray.wurlod wrote:When "they" complain, the response is that it's the cost of stupidity.
Read my footer quote

Couldn't agree more with both of your opinions.