DSXchange

Hi, Can you copy and paste here..a polish character that you are not able to see properly ? Thanks, Raghu Hi Guys, Here i am giving a little bit clarification to what i have tried. The input file: Unicode format(utf8) while opening the file r u able to see the special charecters "Yes" How ...

Is there any published literature or tips on the performance of DataStage on various hardware & OS platforms(linux vs. Solaris). I understand that actual capacity planning will depend on expected load on the ETL server, etc. but if I know we want to stay on DataStage(Server edition 7.5.1a) will...

I am quite sure that we are never going to do a full load anytime now and in near future. So, its all a matter of doing the daily incremental loading. And, also when I load the hashed file with more than 80 million keys..it has to be a 64bit hashed file( since its gonna hit 2.2GB) which again I thi...

The key here is to not load all 80 million target records into the hashed used for lookup - there's no need for that. That's what Ken explained - a method to only load the natural keys from the 80 million target records that match up with the staged incremental data. That way your lookup has the mi...

Kris, that's basically what Ken explained in his post. Hey Craig, I am doing exactly what Ken has suggested. But Raghu seems to come up with a different idea. Was just trying to findout what he is suggesting, clearly so that it would help. It wouldn't hurt to know if there is another way..right :wi...

I do have a timestamp field in my target table. But, I didnt quite follow you on how I incrementally load the hashed file. Based upon the timestamp in my target table, I pull only those records from my source which have changed since the target table has been last loaded. Now, this incremental data...

What I meant was, there are 80 million rows in my target table, each row identified by a distinct key. Is that what you wanted to know? Kris If you have 80 million unique records in your target table, then -Time stamp your target table. -Incrementally load your hash file. So assuming 1 million reco...

Hi everyone, I am working on Datastage 7.5.1 server version running on Unix with DB2 database.DS Client is on windows XP. When i use the inbuilt fuction KeyMgtGetNextValue(%dummy%) in order to generate a surrogate key, it works fine.For example for 5 records the last key generated is 5. However whe...

Hi All, I have a job designed to do incremental loading based upon the last updated date in the target table. I stage all the incremental data in a sequential file and lookup against a hashed file containing all the key values of the target table and based upon key found and notfound I do my insert...

Hi, Iam using a KeyMgtGetNextValueConcurrent function in my job . When I am using in development environment it is generating numbers like this CBL1 to CBL100 and If I ran second time it is generating from CBL101 to CBL200 but when I am using for testing it is generating from CBL1 to CBL100. But I ...

The solution is pretty straight forward - put an NLS_LANG entry in your dsenv file that matches your source / target systems and you should be fine. But as mentioned by someone in the post, wouldn't changing the dsenv file affect all projects that run on the DataStage Server. Instead cannot this be...

Hi Yamini and All,

When I am trying to use NVarchar i get the following error: ' Stage does not support UNICODE character set'

I tried using the OCI 9i Stage as well as the DRS stage, both times getting the same error.

Any suggestions?

Thanks,
Raghu

Hi All, Our DataStage jobs that have running fine for over a month now have suddenly started hanging without returning any error. These are simple jobs using OCI9i Stage for the source and target and couple of transformer stages. It does not seem to be an issue with the database as all projects usin...

Hi All, A column defined in Oracle9i as NUMBER gets translated as Decimal with length as 38 and scale as 0 OCI9i Stage. I suspect that this is causing rounding up of numeric values to some extent and could be the reason for some of the mismatches when we do tests like select sum(col1) from table in ...

Thanks Arnd and Sainath.

Topic Closed...

-Raghu