DSXchange

Nitin, It's easy in DS Server... you just need to play around with the ASCII codes to generate this kind of sequence. But the PX solution may be a little bit more tricky as BASIC routines are not directly runnable in PX. The reason is PX is written in C while DS Server routines are written in UV BAS...

quote: Originally posted by spracht Vladimir (and all), Would you go for a static file if you knew that it won't exeed it's limit in the next 6 month, but probably in 2 years? Thanks in advance! Stephan Hi Stephan, It all boils down to how much performance improvement you've gained by using this sol...

Hi Roy, On the database side... Did you check your table locks? Do you have other processes that update, insert or delete data from your tables on the 20th iteration of this job? Since you mention that you run many jobs in parallel, I suggest you monitor the table locking in Oracle. You can monitor ...

In addition to what Kim suggested, you might want to consider a Static hash file. It is known to increase performance by at least 30%. You can use the hash file calculator (HFC) to estimate the pre-determined size of your hash file. HFC is found in the DataStage installation disk under Unsupported U...

Hi Rasi, The Aggregator stage performs better when the input data is sorted. It doesn't consume more resource than when input data is not sorted. If you don't get the error when you remove it, then you don't have a resource problem. The "out of sequence" error in this case means that your ...

I have a friend who hit the same problem with Link Collector stage in DS6 (Server). He raised the issue to Ascential and it is a confirmed bug! [:(]

I suggest you also send your case to them so it will help raise the severity/priority level.

regards,
vladimir

If you want to create 64-bit hash files, make sure you set this in uvconfig in DSHOME:

64BIT_FILES 1

This will allow you to breach the 2GB limit but it works ONLY if your platform allows you to create 64-bit files.

regards,
vladimir

quote: Originally posted by rasi Out of 11 column 10 column is pre-sorted before using aggregator stage. All the 10 sorted column is enabled with the Group button and the left out one column does the sum for the group. How was the pre-sorting done? Was the data sorted from source or by Sort stage? T...

In addition to what has been suggested above, you might want to try these... 1. split your job into two streams - one doing the update only while another is doing insert only. 2. for the job that updates, make sure that you are using the right index to avoid full table scans - this is the rule-of-th...

"Abnormal termination of stage..." is the most ubiquitous yet most un-helpful warning message in DataStage. It's vague (can't tell you what EXACTLY is the error) and usually is caused by a lot of things. The worst I experienced was the memory leak on the ORA OCI stage in DS4.2. Anyway, thi...

Thanks Ray. Btw, I've just read from the DS PX document that server jobs can be created and accessed using Shared Containers [:0] All server plug-ins (including hash files) are available. Can the Shared Container be used to address Nitin's problems? I don't have a PX server so I can't try it myself....

indeed, that's soundz Grrrr...EEK to me! [:D] nevertheless, we need focus here [:)] how about this solution... 1. generate a surrogate key (just a plain sequence) for each record. so now you have key, skey, fld2, fld3 2. stage your data into a staging table, say tmpTable 3. use this query select a.k...

it's not in PX?! duh![xx(] I'm not familiar with PX yet but there's a work-around to your problem... well, IF we can sort your data... you will need two hash files - one to get the fist value and another to hold the last value. here's the trick: 1. create a hash file with key and fld2 2. sort key an...

You can also find the FIRST and LAST aggregation function in the Aggregator stage. I think that will solve your problem.

regards,
vladimir

John, Just out of curiosity, have you tried running job SEL060ReportFailedFile alone? Pls try to trigger it and supply the parameters manually - don't forget to set pFailPercentage to 10.0784 - and let us know what happens. If the job runs successfully, try to re-add SEL060ReportFailedFile into the ...