Search found 53125 matches
- Fri Sep 09, 2005 5:49 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Rejecting non-numeric fields
- Replies: 7
- Views: 1899
My problem is that there can be dirty data in any numeric coulmn for any of the tables that we are loading from our Legacy system, no way to know ahead of time. I'm trying to set a trap that will reject any coulmn. <paranoia>If there's a chance it will be dirty you have to check.</paranoia> One of ...
- Fri Sep 09, 2005 5:46 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: UV TABLE
- Replies: 1
- Views: 786
It's impossible to tell without knowing what the data types are and what data you are actually delivering. You may be able to determine this by inspecting the warning messages in the log, or you can definitely see the data by tracing the Transformer stage. The reason the intermediate text file works...
- Fri Sep 09, 2005 5:43 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: error in jobs status after hard disk failure
- Replies: 4
- Views: 2064
Why does that work? After your hard disk crash, any hashed file that was open was left in an inconsistent state. For example, the configuration table for job number 79 (RT_CONFIG79) possibly was left with inconsistent header information. Copying and compiling a job creates a new job, with a new job...
- Fri Sep 09, 2005 5:37 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error:- ds_udtGetNextPacket Error calling DSHELPER
- Replies: 5
- Views: 2492
- Fri Sep 09, 2005 5:35 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: VOC Entry Details
- Replies: 7
- Views: 5588
It was right when I posted but, yes, they have reorganized the site. Now you can get it here (the $45 is for a paper copy - the PDF remains free). You can not directly query the VOC file for key columns of hashed files. Metadata are not stored in the VOC file; only the location of the data portion a...
- Fri Sep 09, 2005 4:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Log in Detail
- Replies: 4
- Views: 1686
The three dots indicate that there is more message. If you make the field wider you may see more. However, I'm guessing that there are explicit line breaks in the message, which means that only the first line is displayed in Summary view. This may be a change in behaviour since the previous release;...
- Fri Sep 09, 2005 4:14 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Error Compiling Parallel Job with Transformer Stage
- Replies: 3
- Views: 1648
You are using 2 output links but the second output link does not have any output columns. Is the problem because of that? When the second output link is a reject link from a Sequential File stage you can not dictate the metadata; you get one column, the raw input record. Something similar is true i...
- Fri Sep 09, 2005 4:10 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance Mointoring on Solaris
- Replies: 5
- Views: 1466
My thought was that this computational load could account for the perceived increase in CPU consumption, particularly if a Transformer stage is involved (you are also carrying the call overheads to the generated library). How to trace and prove that may be tricky. Alas, I'm at a server-only site cur...
- Fri Sep 09, 2005 4:06 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Log in Detail
- Replies: 4
- Views: 1686
- Fri Sep 09, 2005 12:30 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Performance issue
- Replies: 2
- Views: 985
Either way you are splitting the processing. But you need to be clever to ensure that each process reads only a subset of the rows. Using a Link Partitioner, you still have only one process reading the file. This will remain an I/O bottleneck, even though spreading the processing may result in some ...
- Fri Sep 09, 2005 12:19 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: function that returns the datatype
- Replies: 2
- Views: 1018
Re: function that returns the datatype
Is there a function in datastage that returns the datype (sqltype) of a field value as interpreted by the source during extraction? Cheers, Shyam No. DataStage is driven by the metadata. Therefore metadata need to be constant at run time. The information could be "hacked" from the design informatio...
- Thu Sep 08, 2005 11:54 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Loading Time in DB2
- Replies: 3
- Views: 1417
- Thu Sep 08, 2005 10:02 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: string to number
- Replies: 9
- Views: 3635
Try "MD" here means "masked decimal, and 2 is the number of implied decimal places in the input.
Code: Select all
Oconv(TheString, "MD2")- Thu Sep 08, 2005 4:54 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: link shared private file cache enabled, overriding no cache
- Replies: 5
- Views: 1146
- Thu Sep 08, 2005 4:44 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Rejecting non-numeric fields
- Replies: 7
- Views: 1899