DSXchange

Aaaarrrggh. I'll just have to work harder at it!

Depends. What is your definition of "duplicate" here? All columns the same or just a selected subset of columns the same? Or even just one column (a candidate key but not a key)? The techniques exist for all of these, but they're different. They can be cumbersome or elegant. For example, if a duplic...

I forgot to mention that we were VERY selective about which columns to load into the hashed file stage, so that the average row size was small, and we were able to get very many rows into the hashed file. Eventually, however, it did get too large to cache, but even disk based performance was far bet...

When you use a Hashed File stage, you get the opportunity (in the Stage properties) to specify an "account" (= DataStage project) or "directory" as the location of the hashed file. It is this "account" to which I referred. It's location is decoded though the DataStage system table UV.ACCOUNT if you ...

Once development/test and production are at the same release, there is no problem. Upgrading production from version 6 to version 7 is also no problem. Make sure you have a backup (export whole project) just in case. Install version 7. Any version 6 components will be automatically upgraded as part ...

No, they got the delivery wrong and delivered a 14-CPU authorization code. Which has been installed successfully.

The advice you have received is, quite simply, wrong. You get different views (one per instance) in the Director log view. This may have confused your support provider. (If your support provider can't understand the concept of a view, maybe you have another problem!) However, there is only one RT_LO...

Let me see if I understand what you're doing. You have a Hashed File stage with an input link and an output file link. On that basis let's investigate further. A passive stage (for example sequential file, hashed file) with an output link in the job has the function to READ from that file or table. ...

The best place is right here. There is no book or other documentation of the kind you seek. In general, any directory containing the files .Type30, DATA.30 and OVER.30 is a dynamic hashed file and should be left well alone from the UNIX command shell. In the project, things with names beginning DS_ ...

chou wrote:Hi all,

Please let me know the Upgrade from Version 5.2 to 7x and migration of all jobs into Production. where Dev is 7x and Production is 6x. Send me the link for Upgrading.

Thanks

It is simply not possible to promote version 7 development/test jobs into a version 6 production environment.

Interesting. Through IBM was ordered (for my current client - before I arrived) a 2-CPU DataStage licence for a 4-CPU AIX machine.

CLEAR.FILE on RT_LOG and RT_STATUS is highly likely to clear any logical corruption. This is not, however, 100% guaranteed, and definitely is not guaranteed to fix any physical corruption (for example bad spot on disk). It also means you lose the control records. DataStage will re-create the control...

There's definitely a problem here. You should be able to do 50000 rows in about a minute or two (depending on hardware) if source and target are text files. Maybe five. Perhaps the source file lacks an end-of-file character, and your BASIC Transformer stage is waiting forever for it. (This is how th...

Last year I worked with a telco in India. They were taking on one million new customers per week for eighteen months. (That's still only about 5% market share!) But the CDR numbers were huge, and the customer dimension was huge too. Hardware was a 32CPU SunFire 15000 with (initally) 34TB of disk and...

When I was last in India we were running an eight CPU licence on a 32 CPU SunFire server. DataStage (v6.x) never ran on more than eight CPUs even though we ran ten and twelve jobs simultaneously. However, I can't be certain that this was managed by DataStage or by UNIX (affinity) configuration. For ...