DSXchange

How come everything you post is "weird"? :D Weird is something, I should not have used eh? But then, I could not think of another word in this scenario, because my query works fine outside DataStage but not inside it :) I say Junk rows because, those are not actual data. As I said, same q...

I am accessing DB2 database using ODBC Enterprise stage. The query used inside it is running fine when fired on Database using Toad. But the same query when used inside ODBC stage, returns junk rows which are not there in the table. The junk rows returned are in addition to the valid rows and are at...

ray.wurlod wrote:That changes the question. ...

:D
Yes. I know. But the target was sequential file. So decided to have target metadata changed to integer since the priority was rounding rather than having metadata as varchar

Your requirements are bad for a CHAR. If your database target was a varchar, then yes you could 'discard trailing spaces' easily. ... The problem is that the downstream apps which use the sql server target table are facing issues while querying. The field is Char in target as well, but DataStage is...

But as per requirement, need to do away with those trailing spaces...If I define target metadata as varchar, it works..Is this a good idea? Is there any other way?

Source DB2(ODBC Enterprise)---->Transformer------->Target SQL Sever(ODBC Enterprise) The incoming field is Char(3). Target also it is Char(3) Spaces are being added to end while writing to target. I used Trim in transformer. No change. I tried Convert(). No effect. Any suggestion. Ineed only actual ...

Just changed metadata of target seq file to Integer. So rounding happens automatically

I have a requirement wherein I need to round off incoming decimal data and convert to varchar and then right to seq file without leading or trailing zeroes. Rounding Off condition as below Suppose data is 345.5 or lower output should be 345 and if it is greater than 345.5 then output should be 346. ...

Thanks for all the replies

Remove Duplicates worked but here is the catch My source has 6 records with same key and different timestamp. Job structure was like ODBC----->RemDuplicate-------->DataSet I was hash partitioning on col1 and col2 with inline sort in rem duplicate stage. Then selected the option Duplicate to Retain =...

The combination of col1 and col2 is never a duplicate. Col1 individually may have duplicates but when it combines with col2, then there is no duplicate. So we cannot use remove duplicates stage or even remove duplicates via sort stage. Using header also cannot solve the issue as it will only return ...

Using Remove Duplicates wont work as there are no duplicates here..The combination of col1 and col2 is always unique

I have the requirement as follows: col1 is sorted ascending and col2 is descending. I need to fetch only the first row of the sort output. The scenario is that col1 contains the key and col2 is timestamp...key is repeated and timestamp is unique. I need only those keys with max(timestamp). So i have...

Nagac wrote:Thanks mate,

I have given the length and scale in output metadata in modify stage

And....? Is the issue resolved ?

You need to mention the Length and scale in modify stage output metadata as otherwise it will take the default value. The error is because the incoming data is of length 9 and you have not mentioned any length or scale in the modify stage metadata