DSXchange

I had a hunch that the trigger expression was set to 'unconditional' and hence your experience of same behaviour regardless of 'automatically handle....' option checked.

Ok, I am still blurry on the requirement. If todays cycle ran and someone tries to run it again it should not run. Is that correct?

Accidently huh? No amount of code can outsmart stupids.

Yea, funny guys, ha ha ha.

Did you try searching ?
Do an exact search on keywords "irreconcilable constraints"

Is the delete record the first record in the file by any chance? If it is then make sure you have "First line is column name" to false.

You need to go through the manuals. The logdetail needs an event id. logsum does not and gives the entire log.

Error message
If there is truncation occuring, there has to be error messages in the log. Maybe the data is coming in like this. Did you verify by spot checking a few records in the source?

Do an order by and max(timestamp) in the Ora and the result of that, will be your lookup. This way you will have only one row per name.

Neither do I, dsxchange sort of makes you an expert in all fields, does'nt it

O yea, the good ol' RMM stage.

Do an exact search on keywords "Invalid character conversion".

We have temp directory and we stage our files there. We have a cleanup process that cleansup these files after 30 days. We can even call it TempStg. Regardless of the name, if you are staging files in that particular directory, dont get rid of them that soon. Its better to move them or archive them ...

Pay attention to what Ray said. You always have to send the trigger file which is usally an empty file after your main file transfer is complete. Hence get them to send two files and wait for the trigger file (second file).

Can you post the exact error message by copy pasting from the log.