DSXchange

No, there's no "log file" but rather they are stored in a database table. You could auto-purge everything but the most recent run but don't imagine that's what you're after. So... why the desire for a new one each run? What problem are you trying to solve?

Then build the body text with an 'if-then-else' construct. It's just a string you can build before the actual call, check the INTERIMSTATUS as noted to see which way to set it.

Could be, hard to say without active monitoring running at that exact moment. Doesn't change the fact at 20,000 is a crazy large number. Take the average internal sizes of your fields, add them up and multiply that number by 20000, that's the number of bytes you're asking the client software to push...

True, but us mere mortals duplicate the code.

Good advice but the issue is here:

Setting null to this non-nullable field: StageVar0_StgCreatedDate

Stage variables are not nullable.

Hmm... what exact 8.x version? Have you checked to see if there are any patches for that connector? Ping your official support provider.

Didn't notice this was your first post here and you can't be missing all that much of what I posted, so sure.

20000? Yikes. Drop it down to 1 to make sure that's the issue and then raise it in logical increments until performance is acceptable and it no more blow up.

UPDATE ATTRIBUTE_TABLE SET VALUE_KEY=?,SERVICE_ID=?
WHERE DIM_KEY=? and CLIENT_ID=? and WEEK_KEY=? and VALUE_KEY=?

Where you bind the OLD_VALUE_KEY column into the proper place in the SQL just like every other field.

Thanks. Put me in the "used to use" camp for XMLSpy as well, a license for that is pretty darn expensive. I've also used the freeware 'Community' edition of Liquid XML and it's pretty nice for what is basically 'cripple-ware'.

I'm not sure what you mean as NULL is never equal to anything, including another NULL.

Of course, all file paths are paths local to the DataStage server. So, if you terminate at the XML Output stage, there is zero output but if you send the XML Output data to a Sequential File stage, it writes it out properly? And this with no other change in the XML Output stage other than linking th...

Yikes, every row performs a UNION of all records in 'TAB A' with three full table scans each time. No wonder it is slow.

Improve the query or switch to a UV stage over a Hashed File stage.

More details. The error is specific to the OCI stage, what exactly is going on in there? Settings, number / sizes of fields, etc etc etc.

Please delete your duplicate post in the other forum, posting the same question multiple times just upsets the natives.

You can do that (delete any of your own posts) as long as there have been no replies to it. Hurry! Go now before it's too late!