DSXchange

Is mgt_code your key in the hashed file and declared as such inyour lookup? Are both VarChar(10) columns trimmed, i.e. with no hidden extra leading or trailing spaces?

brajesh527 wrote:...Unable to create temporary work file, aborting.
[ENOSPC] No space left on device

This would be the directory you are using for temporary workspace that is filling up.

Hah - I obviously overlooked the "server" part of the question but did think it was an interview question, so I got the response at least partially correct :D .

This error is coming from your SMTPMail, not DataStage. I did a google "SMTPMail Network error 10061" and got many hits. The "smtp.md2net.com.br" server is visible from my machine, but I don't have a "telnet" program installed to test if the machine at that address is a...

With a post like that you won't get many qualified responses. The simple answer is "drop it on your canvas in the designer and attach two or more inputs and one output to it". Unless you explain what your issue is, no more help can be forthcoming.

Make a copy of the job and remove the second aggregator and join stage (I am assuming that your first aggregator is called "Aggregator_1"). Recompile and see if the error is reproduceable. If yes, then please post some information on what you are doing in the aggregator. SIGSEGV is a segme...

Server imposes no such limitation on string length, so if that is what MQ can handle then it should work. How about testing it - that shouldn't take more than half an hour to set up the queue and read/write the long string to/from it.

There is no easy answer. I would pare down the data to a few rows which demonstrate the problem, i.e. which deliver different results, and then see if there is some sort of explanation.

You can issue a DSStopJob(DSGetJobInfo(DSJ.ME,DSJ.JOBCONTROLLER)) call, this will issue a stop request to the parent job when only one parent exists; with more parents (a calling b calling c) you would need to parse the result of DSGetJobInfo(DSJ.ME,DSJ.JOBCONTROLLER) to get all the jobs. This is on...

You've hit the limit set by your ldedit value. The quick solution is to change all char and varchar columns to varchar columns with no size limit; this can reduce your memory use per row. If the data width cannot be decreased then I would either consider changing your lookup to a join or to split yo...

Are you inserting all the table columns when it is empty? If there are columns defined that you don't have in your job and that don't have any default values set by triggers and that are not nullable you will get this error.

The first line in the director log will show the runtime values for the parameters, what does your run show for #HashFileDirectory#? Also, in the hashed file stage, what did you specify for the full name, perhaps ?

I though paraphrasing and reiterating might help

After resetting your job in the director there will be a couple of new log entries. One of those shows up with the text "From previous run..."

Could you please post the whole error message. This type of problem could occur if someone has modified your table DDL and added a new, not nullable, column -- but the error message will state which column is causing the error. You can also debug this by putting a PEEK stage right before you databas...