DSXchange

Search this forum. Has been covered a lot. Search on conditional triggers or something to that effect.

It will not matter.

Auto purge option works without fault. Someone must have cleared one of the logs using the CLEAR.FILE option which disables the auto purge option. If you want a routine to purge the logs you can create it. Its simple, all you need is to get the job id's and pass them one by one to the TCL command CL...

Welcome Aboard Teradata has a limit on how many load utility operation can be run concurrently. You are exceding the limit. Its exceding the timeout session as well as the tenacity(number of retries). Either increase the tenacity number or control the number of concurrent operations. Its not a datas...

Welcome Aboard
Answer to such questions can be found by a simple google. Try doing some research.

Well, right now i am running out of ideas. The only other thing that i can think of is doing everything via a script. A nasty shell/awk script. Start thinking in those lines. If i have time on monday i can work on it, but no promises.

Try calling the script from a routine calling DSExecute(). You can manipulate the return of 'Output' and extract the first record from the dynamic array using Field(). See if that works. if even that doesnt work then why not just mail from unix itself. If you have never used the os mail before searc...

I did some more research and this is what i found on bugzilla. Check it out
https://bugzilla.redhat.com/bugzilla/sh ... ?id=150277

Hmm, pretty cool. I will give that a shot on monday.

leomauer wrote:2. In every multi-value field replace commas with @VM (char(253))

You mean @FM
But how would you then read from the hashed file with 12 defined on your output ?

A common join key(s) are needed for them to be put together. As Sam requested, give us more info. Sample data would be nice.

The code ORA-02291tells you all. You have a foreign key in the record which has no entry in the parent table. Click on the error code in blue for more details.

Its telling you that the problem is with the routine "GetNextBatchNumber". The other two names that you mentioned also seem to be user defined routines. You need to look at them and see whats going on and why they are acting up. Is this the first time your getting the error?

Search this site, its been covered gazillions of times.

In your temp table, the first column, can that have duplicates?