Re-partition before target stage. You may have duplicates in data...
Thanks
Search found 4 matches
- Mon Jan 30, 2012 10:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: deadlock error
- Replies: 16
- Views: 9904
- Tue Dec 22, 2009 10:53 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Refreshing Business Objects Report via datastage
- Replies: 4
- Views: 2946
Re: Refreshing Business Objects Report via datastage
I don't think it is possible. One way is you can create dummy file after completion of job. based on dummy file arrival, Run a batch job to refresh BO.
- Tue Dec 22, 2009 9:42 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: The JOB every hour brings me a different result
- Replies: 5
- Views: 3322
Re: The JOB every hour brings me a different result
Before aggregator, you need to select hash partition with correct partition keys if you are using multinode config file..
- Tue Dec 22, 2009 9:26 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: null field in schema file
- Replies: 2
- Views: 2422
Re: null field in schema file
Hi,
I think you need to use string[max=50] instead of string[50]. If you use string[50] then datastage will consider as char(50) and will expect 50 characters data.
Thanks
I think you need to use string[max=50] instead of string[50]. If you use string[50] then datastage will consider as char(50) and will expect 50 characters data.
Thanks