DSXchange

The Merge stage was a bad piece of advice on my part if the metadata matches between the two files. But then, if all you are trying to do is concatenate two identically formatted files together, how is that a job for DataStage? Sure, you can write one, but why do it when a simple call to your operat...

Welcome Aboard! :D It always helps to include as much information as possible so that people have some idea how to help you. It looks like you've got a job with (at a minimum) a Link Collector stage that is giving you problems. What exact version of DataStage? I'd also be curious which flavor of UNI...

Just kidding... mostly. Hard to tell when there are many numbered questions like that in a post.

Well, there is a Merge stage which 'joins' two sequential file sources, but I don't believe it is available in the version you have. There is also a Filter option in the Sequential File stage, but again I don't recall if it was available in the 5.x version of the product. It would let you issue an o...

But what would qualify as a 'null' in a fixed width sequential file? Any inner column that might qualify would have to be all spaces to maintain the sizing of the record. Are we talking about that or trailing (i.e. missing) columns from the end of the record?

I wrote:Ah... the bulk loader. There is a PRESERVE BLANKS option, from what I recall, for situations like that.

And then ArndW wrote:but not from Px

Aha! Nothing like a Ray Wurlod class to get the investigative juices flowing. Always another enviroment variable out there lurking:

What Arnd has been trying to get across is there is generally no need to do these explicit conversions in the Server version of DataStage. It is quite happy taking a character field and providing it to a numeric field in Oracle as long as there aren't anything but numbers in the field. The conversio...

Hope they get the job, Arnd.

yes ur right the generated sql query will also have TO_DATE format, but the format used in TO_DATE would be some default format, and it may not be same as your input data in that case you need to have User-defined query. Need? Again, not really. You can either go the custom sql route (which I try t...

Why, when the stage will do the TO_DATE for you automatically? Doing it that way forces the use of Custom SQL (yuck) for any table that has a DATE field in it. If you stick with a Timestamp datatype in the Target OCI, you can still work with it as a string all through your job (if you like), as long...

Do you all get the same numbers or does your DS MJC actually work ? Never benchmarked them. Sounds to me like yours actually worked just fine, just not at the speed you would have liked to have seen. It doesn't surprise me, the difference is compile times. They are all different architectures and s...

Why not use the Version Control utility that comes with DataStage to do the actual promotion in addition to what you are doing with CCC Harvest? Save you all those export/import hassles and will compile jobs in the project they are promoted to, along with marking the jobs Read Only outside of devel...

The 'where' clause refers to whichever columns you have marked as Keys - so regardless of the actual keys in the table, only mark the columns you want to be used in the where clause for this statement. All of the columns not marked as keys will be updated. Make sure you've set the Update Action on a...

Sorry, no. Did verify, however, that the sort looks for the first occurance of 'scratchdisk' in the default pool and that's what it uses. A couple of confusing bits here. When you say it's a "fatal error" and yet the job "isn't affected", what does that mean? A red marker in the Director log but it ...

Post your Routine code.