DSXchange

Of course, this happens all the time. I just don't see how anyone can expect a single job (or jobs) be built that will somehow magically be able to figure out any and all incoming formats and produce what the consuming system needs. That, from what I recall, was the original request. However, a seri...

Transformers capture rejects in Server jobs, in PX jobs the stages themselves do. Drag a link from your target stage and you'll be able to declare it a Reject Row.

I use stage variables quite often and for multiple reasons. Primary reason is to keep derivations in one place for multiple use in other places as noted in this thread... sometimes even just for one other place. However that's hardly the only reason. Another is the ability to simplify and 'self-docu...

You mean 'decimal'.

Your second column isn't decimal - not with those alpha characters in it. Looks like a varchar that happens to have a period in it to me.

Interesting. If you've got something that works, stick with it. My standard advice would be to use Timestamp datatypes in your jobs, let the stage generate the SQL and build a library of routines all developers use to make date handling across your jobs consistent and error free. For example, this I...

No worries, it's good to report stuff like that - we need to keep Walter busy.

No, you'd need to do pretty much what you are doing if you really want to stop and restart things. Or use the dsjob command line to issue a stop request. I'm sure there's some 'Universe' command available but I've never seen a need to pursue anything of this nature. We just backup. Curious - when yo...

There is no 'Oracle date format', it's up to the tool you use to decide what external format to show the dates in. By default you get the $NLS_DATE format. I would guess your 'conversion' is actually doing nothing and passing things through unchanged, which is what happens if the conversion fails. ...

I'm seeing the same thing, but I never use that feature for Ray - there's just too dang many posts. Suggest you go to the regular 'Search' function and use some keywords to narrow things down. You can constrain based on author there as well. Unless you really were planning on browsing through almost...

That... can't be working, unless 'working' just means not blowing up. Have you checked in Oracle and see the same dates there as were sent? I'm asking because the OCI stages don't take dates in internal format.

Only a wee little stub of an article, but this might help.

So... mark the SR_ID column as the 'Key' field to get it in the generated where clause. And yes, all records that match will be updated.

There's no DataStage magic here, just plain old ordinary SQL.

Don't lose any brain cells over this. Simple inserts don't need those privs, more complex partitioned loads would, I'd wager. As do your selects... which I'm sure has been explained here several times. Search, my good man, search!

Wouldnt a job write to the same sequential file twice, if there is a delay between the two write operations ? If the file is not written to in the same active stage ? Yes, as I explained earlier, the two writer processes must run in a serial fashion, one after the other. Once the first completes an...

Key doesn't mean Primary Key in this context, it just means the field(s) to use in the where clause. How would you do this in straight SQL? You do the same here, mark the fields needed in the where clause as 'key' field, anything else will be updated.