No replies then?
I have a workaround for this but I'd still like my doubts clarified especially if my assumption for the duplicate rows returned is correct.
Search found 284 matches
- Tue Aug 09, 2016 8:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Duplicate entry issue - Lookup stage
- Replies: 12
- Views: 13323
- Fri Jul 08, 2016 12:53 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Problem compiling job due to multiple environment variables
- Replies: 5
- Views: 4266
- Thu Jul 07, 2016 1:27 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Problem compiling job due to multiple environment variables
- Replies: 5
- Views: 4266
Problem compiling job due to multiple environment variables
Hi folks I have a strange problem. Here goes. We all know DataStage is strictly case-sensitive. I thus have 2 environment variables, both pointing to the path where my .ds (dataset descriptor) files are stored - one if PathDS and the other is PathDs. this is because at some point we were using DS an...
- Fri Apr 29, 2016 1:24 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: ORCHADMIN command - nitty gritty
- Replies: 5
- Views: 3920
Actually I think there were so many datasets, i panicked something was going wrong when the screen scrolled indefinitely - I thus stopped the command prematurely thinking I was deleting everything...:-o However with the echo command I managed to list out (in a file) the individual orchadmin commands...
- Wed Apr 27, 2016 8:36 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: ORCHADMIN command - nitty gritty
- Replies: 5
- Views: 3920
- Wed Apr 27, 2016 7:58 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: ORCHADMIN command - nitty gritty
- Replies: 5
- Views: 3920
ORCHADMIN command - nitty gritty
Hi all By now I've understood why the orchadmin command should be used to delete datasets and why we shouldn't go for the kill with an rm command. However I have a few follow up questions which I hope someone here can help me out with: 1) Is the orchadmin rm command only for datasets or filesets as ...
- Fri Mar 25, 2016 3:29 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup vs. Join
- Replies: 6
- Views: 7474
however if what I understand is correct, this is not refreshed at job runtime? You are correct - Lookup File Stages use static lookup tables that must be refreshed manually. Which means this is useful only if my lookup data doesn't change too often. In my case my reference (lookup data) changes eve...
- Thu Mar 24, 2016 3:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup vs. Join
- Replies: 6
- Views: 7474
Thanks Ray. I'll try and find out what kind of environement we're in (SMP/MPP) but i'll go by the assumption that and 'Entire' Partition is not going to affect the runtime too adversely. I admit I'm not too familiar with the Lookup File Set stage - however if what I understand is correct, this is no...
- Wed Mar 23, 2016 3:10 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup vs. Join
- Replies: 6
- Views: 7474
Hi Thomas Thanks very much for that. I thus understand that it's not the total number of records in the reference link that decides whether a join should be used in place of a lookup. Rather it is the ratio between the number of lines in the reference and stream that plays the decisive role? In this...
- Wed Mar 23, 2016 8:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup vs. Join
- Replies: 6
- Views: 7474
Lookup vs. Join
Hello world This is a question that involves the use of lookups and joins - so basic DataStage fundamentals. This is what my current knowledge on the subject stands at, i.e. when to use what. Considering that I want a left outer join, if the number of lines in my lookup dataset (right hand side data...
- Sat Mar 12, 2016 4:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How can I get the minimum date in the aggregator?
- Replies: 10
- Views: 6760
- Fri Mar 11, 2016 11:33 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Maximum value of Date
- Replies: 6
- Views: 4177
Old topic (I know) but I had to go through this (and other similar ones) since I was looking for a solution. On a hunch I tried the option Preserve type = True within the Aggregator itself....worked fine...:-) No more warnings / aborts. Basically what happens I guess is on choosing to preserve the d...
- Fri Mar 11, 2016 11:32 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Max of date from Aggregator
- Replies: 3
- Views: 7845
Old topic (I know) but I had to go through this (and other similar ones) since I was looking for a solution. On a hunch I tried the option Preserve type = True within the Aggregator itself....worked fine...:-) No more warnings / aborts. Basically what happens I guess is on choosing to preserve the d...
- Fri Mar 11, 2016 11:32 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Date type cast
- Replies: 12
- Views: 9806
Old topic (I know) but I had to go through this (and other similar ones) since I was looking for a solution. On a hunch I tried the option Preserve type = True within the Aggregator itself....worked fine...:-) No more warnings / aborts. Basically what happens I guess is on choosing to preserve the d...
- Fri Mar 11, 2016 11:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How can I get the minimum date in the aggregator?
- Replies: 10
- Views: 6760
Old topic (I know) but I had to go through this (and other similar ones) since I was looking for a solution. On a hunch I tried the option Preserve type = True within the Aggregator itself....worked fine...:-) No more warnings / aborts. Basically what happens I guess is on choosing to preserve the d...