Search found 53125 matches
- Sat Aug 12, 2006 2:58 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: TRIM
- Replies: 9
- Views: 7175
- Sat Aug 12, 2006 2:56 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Metadata - list of all tables
- Replies: 15
- Views: 5245
- Sat Aug 12, 2006 2:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: row too big for inter stage rowbuffer
- Replies: 6
- Views: 3284
- Sat Aug 12, 2006 12:57 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Date Timezone Conversion
- Replies: 8
- Views: 5876
Create a Lookup File Set showing, for each time zone, the offset from GMT (or UTC if you're a purist!), the date daylight saving kicks in and the date daylight saving kicks out. Keep this maintained (up to date). Use a Lookup stage to get the offset, and adjust hours accordingly (convert hours to se...
- Sat Aug 12, 2006 12:52 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Quote(') or Quote(")
- Replies: 4
- Views: 1253
While it does not matter in DataStage itself you do have to get it right in a number of locations. In SQL, double quotes are used for identifiers and single quotes for string constants. In shell scripts, single quotes are "hard quotes" while double quotes are "soft quotes": some expansions are possi...
- Sat Aug 12, 2006 12:47 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: v7.1 vs v7.6
- Replies: 8
- Views: 2660
- Sat Aug 12, 2006 12:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Project Corruption
- Replies: 8
- Views: 2258
- Fri Aug 11, 2006 10:57 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: The routine KeyMgtGetNextValueConcurrent
- Replies: 8
- Views: 1747
It's done differently in parallel jobs, because there are multiple streams of data being processed: blocking those flows is not permitted and forcing single-threading (to get unique values) is discouraged. Instead, there is a Surrogate Key Generator stage or Column Generator stage that can be used i...
- Fri Aug 11, 2006 10:50 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: SybaseOC stage not opening
- Replies: 8
- Views: 1848
- Fri Aug 11, 2006 10:37 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Capturing Error meessages in director
- Replies: 4
- Views: 697
- Fri Aug 11, 2006 10:34 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Not able to view data from localuv DSN
- Replies: 5
- Views: 2375
- Fri Aug 11, 2006 10:31 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Abnormal termination of stage AGGREGATOR
- Replies: 2
- Views: 905
Your Aggregator stage has exhausted its available memory. While there is a set of tunables for addressing how the Aggregator stage allocates memory, there is still a finite upper limit. Sorting the input by the grouping columns means that some memory can be freed as soon as one of those values chang...
- Fri Aug 11, 2006 10:25 pm
- Forum: IBM QualityStage
- Topic: does QS perform Like matches?
- Replies: 1
- Views: 1334
- Fri Aug 11, 2006 10:22 pm
- Forum: IBM QualityStage
- Topic: What is a "single-domain field"?
- Replies: 4
- Views: 1952
A single-domain field is most easily thought of as a single column. A single column contains a finite number of discrete values - these are its "domain". Arguably the domain is the set of legal values, but that's what data quality is about determining. With Character Concatenate investigation you ca...
- Fri Aug 11, 2006 2:25 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Getting record count from Transformer
- Replies: 6
- Views: 6437
System variable @INROWNUM maintains the count of rows on the input link, while each output link maintains its own @OUTROWNUM (on each partition in each case). You could collect these into an extra two columns on each output link, and use downstream Copy stages to split them out, and Aggregator stage...