DSXchange

devesh_ssingh wrote:i am not able to think unless know the error which he donno other than abort...

Neither can we.

My response is similar to Ray's and is documented in the linked post.

Seems like it cannot find a file that it is looking for. Contact your official support provider, not sure anyone else would know what file that might be.

The reason and solution for this -14 timeout error has been posted here many, many (many) times. Anyone still unclear about it should just... exact search.

You would need to include a Server Shared Container in your PX job to do that, but it won't magically make it any faster. There is no such thing as a hashed file in a parallel job. You would need server job componentry and this might defeat your goal of speed. So... do you not read what others post...

OK, maybe just no-one in their right mind. :wink: I've told this before, but when sending XML to Google, they have a hard 100MB limit file size. 1 byte over on any file and the whole collection gets rejected. They didn't care what quantity you sent, but were quite emphatic about the individual sizes.

Which wasn't there when I posted. It was just the first line, now I see that Andy has gone back and added a novella on the subject of hacking in a new VOC record all Old Skool like.

Anytime, Sportclimber.

Not sure about the "downloading php files" part, perhaps that is going on and I have no clue. But it sounds like it is related to this, which has been going on, well... basically forever.

viewtopic.php?t=132187

Wrong forum.

Post your actual, complete, unedited error messages. And what matters is what the source/target actually say re: nullability, not how you declare the columns in the job.

You would need to include a Server Shared Container in your PX job to do that, but it won't magically make it any faster. How many records are we talking about here? Did you properly size the target hashed file for the anticipated volume?

Nobody wants to process LARGE xml files. Lots and lots of small ones, sure, but a small number of biggies? No thank you.

So... consider increasing the heap size limit, then. Talk to your System Admin for the 'how' of that.

Items in the "phantom" &PH& are only needed when the job is running that produced them. Most people prune that directory to a rolling 7(ish) days just to keep some level of detail around for forensic purposes.