DSXchange

Examine the last few lines. WHats different. If its fixed width, it will be easy to examine which record is the culprit and why.

meena wrote: I can not use unix script or routine too. I need to do it in terms of stages & expression

Who put that limit?

What do you mean stop an acitivity? Does that mean that an acitivity is executing and simultaneously you are waiting for a file and if its over and hour and no file is found, stop the job activity? Is that what you want?

I dont think koti_2k2000 is sharing that info. Its more then just that .

Other errors like 'Heap Allocation Failed',SIGKILL,SIGSEGV,SIGINT are OS level errors. You can do thorough research on google and ways to avoid and/or get rid of them.

Great. Thanks for the Info RobinM.

Its just letting you know that the incoming data is not what is defined. Fix the length and precision and you should be fine.

Restart will happen only upon failure. If you job finishes with warnings, the DSEngine will consider it "a finished" job and run from the next job onwards. Just to give you a heads up

You need to get together with your DBA and do some analysis and monitoring. Run the job, let it fail. Ask the DBA what does he see at his end. How many threads alive, how many still alive after the job aborts etc etc etc.

No idea at all.

You can also access it via odbc stage with DSN as localuv. Add the metadata yourself and write queries there.

Perform the lookup, if there is a hit, send it down one link, if it does not, send it down the other. Merge the both before doing upsert or send both the links directly to the same database.

As Ray said, "Mega wierd".

I did. And it makes sense, I was just commenting on kashif's advice.

Why exactly do you want this, or your team lead wants this.