DSXchange

I have a requirement where I have to transpose records from row to column like the followings. Input records coming from flat fie as follows A,B,1,2,3,4,5,6 C,D,1,2,3,4,7,8 E,F,2,5,4,7,8,9 Considering the first two fields are the business key and rest are the different measure value. Output records ...

Here table action you mentioned as Append. So the new records will be loaded into the table. No truncation will be occurred here.

If you mention table action is truncate then it will truncate the table then load

I tried to generate unique number (in sequence) without any breakings between them So I have applied the following formula in a transformer where only this operation is happening. Formula : @INROWNUM * @NUMPARTITIONS + @PARTITIONNUM - @NUMPARTITIONS - 1 And also making the input partition to the tra...

First time I am usig the XML stage (introduced in 8.5) . When I am clicking on the Edit Assembly button, assembly window is not openeing. is it the issue with the patch installation or some other thing is happening?

Is this the existing issue with datastage 8.5 ?

You can do the same thing by using one sort and one remove duplicate stage.
First sort on the business keys and date(descending).
Then perform a remove duplicate on the basis of business keys to retrieve the max date.

Yes Ray,
The parameters are resolved (to fixed values) without being prompted for values when use the data browser.

My job design is DB2 connector------>copy-------> Dataaset. Now when I tried to view data in the db2 connector stage the parameter values used in the db2 connector database property become hard coded.Not only that if any parameter value being passed in the sql query itself then it is also hard coded...

If we convert all the measure of the aggregator to nullable no with using any null handling then input to aggregator in that case is not null.

Is there any dedicated logic for making the aggregated output columns in aggregator stage always nullable?

I have three columns as below

Key1(Not nullable) Key2(Not nullable) Amount(Not nullable)

Now when I am aggregating Amount field on the basis of the Key1 and Key2.
Now when I map the output the field Amount automatically becomes Nullable.
Is it the default behaviour of the aggregator stage?

If the column length is greater then 6 ,say 8 then it will not work.According to nareshketepald the length of the field is 50.

What is the length of the VARCHAR field? And are you using Datastage 8.5?

In this regard also one thing needs to be performed that the transformer must run in sequential mode.

Please try to find the unique index.It may happen you have unique index on one field and you are trying to insert same value of that field as before.
But when you are doing update first then that value changed so no duplicate in new value for that field so that can be inserted easily.