DSXchange

I have mimiced your scenorio.But didnt get any warning.I am using V8.5. Job1: Row gen---->copy--->Dataset(sort and hash partitioned applied in Dataset for key column) Job2: row gen | (sort on key) | V Dataset-(same partition)-->Join---->peek No warning either job1 ot Job2.

I believe this is a partitioning issue.When the data is send to the shared container it is grouped as per your need but when it gets into shared container,it is getting re partitioned thus affecting your group logic.If it is so it is better to use a same partition in input column of shared container...

Experts....

Your intervention is highly appreciated...

We have write permission.If I run the job second time it finishes with out warning and there is no pattern regarding the warning.

Is this a fixed width file or a delimited file?
One option I see from your data is take the whole string in one column and use substring to strip first 8 charecters and then convert it from string to date

To my knowledge, Dataset cannot be ftped from one server to another server.Dataset is not a single file like a flat file.descriptor file is internally connected to datafiles which are located as per config file

<DATAFile>,0: Could not delete descriptor file: <Descriptor file.ds>
filesystem related error

Hello Team, I am getting a warning while I am running the job. When deleting data set <DataSET Descriptor File.ds>, previous delete attempt not complete; removing <DAATSETDescriptorFile.DS>.being_deleted in order to proceed. But when I re run the job it finishes with out warning.I do fear that when ...

Thnaks Andr for your time and information. As per my knowledge,the metadata information is embeded in the descriptor file.So as per the documentation you pasted.Does it mean that every time when we run the dataset with Overwrite(Discard records) policy, datastage will delete the data files and write...

Hello Team, We mostly use Append/Overwrite/create(error if exist) as update policy while we are using dataset as target stage.Can any one help me in understanding the other update policies please. Use existing(discard records) Use existing(discard records and schema) Are we using above policies if s...

Thanks a lot Mike, Ray,Chullet..

Even though SCD is a robust stage to handle this scenorio.I implemented it in the way we implement in 7x as it shows me whats going on rather than bundling it in single stage.

Thanks a lot again for you time and response.

Thanks Mike for quick response!!

Out of my curiosity how to implement this scenario in DataStage 7 where we don't have SCD stage?

Mike we record every transaction. So if we have 3 transactions which occurred for a product we are pulling all three. One of the subset requirements is if these three transactions have same key then it will be either an update or an insert. We need to push three records into fact and 1 record as an ...

Thanks alot Mike for quick response. Our source is a transaction DB where I can get duplicate keys with same value and the fact information might vary based on quantity of the products bought by customers. We are using change capture to see if there is an update of insert. I believe Merge stage does...

Thanks Mike for your response, But it didn't work.

If I understood well, the modified scenario is
Today:

Key,Value ,QTY
ABC,10,1
ABC,10 ,2

Yesterday:
Key,Value
ABC,20

O/P:

Key,Value,Change code,QTY
ABC,10,Update ,1
ABC,10,Insert,2