Search found 53125 matches
- Tue Feb 19, 2008 5:51 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parallel routine issue when using library file
- Replies: 3
- Views: 1603
- Tue Feb 19, 2008 5:50 am
- Forum: General
- Topic: Exporting jobs through Commad prompt
- Replies: 7
- Views: 4406
- Tue Feb 19, 2008 5:49 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in compiling the job
- Replies: 6
- Views: 1409
- Tue Feb 19, 2008 5:46 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Renaming a link breaks a transformer
- Replies: 7
- Views: 1901
Are you referring to the Key Expression on second (and subsequent) reference input links, or subsequent fields on the (only) reference input link? The latter do not need to change; they are not qualified by link name on the reference input link itself. However, some of your stage variable, constrain...
- Tue Feb 19, 2008 5:42 am
- Forum: General
- Topic: Importing dsx file server side (from a ksh script)
- Replies: 2
- Views: 1553
- Tue Feb 19, 2008 3:37 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: retrieving job status from dsjob
- Replies: 8
- Views: 2944
When you originally specified dsjob we understood that you meant to do this from the command line. Oconv() is not available at the command line. What you have done is appropriate within a DataStage job but, if you're going to do that, why incur the overhead of invoking dsjob command? There are perfe...
- Tue Feb 19, 2008 3:35 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: eliminate warning messages in Datastage server edition
- Replies: 4
- Views: 1608
Thorough analysis, cogent design, comprehensive implementation. Identify all possible causes of warnings in the development phase (unit testing) and code to prevent their occurrence. Then, in production, any warnings that do occur are not the fault of the ETL process, and may be regarded as genuine ...
- Tue Feb 19, 2008 3:32 am
- Forum: General
- Topic: returning failed record and feild
- Replies: 5
- Views: 1513
The log will contain any error message generated by the database server. This may or may not contain the name of a column. It may, for example, contain the name of the constraint that was violated. It's then up to you to examing the column values (also logged) to determine which value(s) caused the ...
- Tue Feb 19, 2008 2:39 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Lots of warning because of transformation
- Replies: 4
- Views: 1438
- Tue Feb 19, 2008 2:38 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Conversion code
- Replies: 9
- Views: 2194
- Tue Feb 19, 2008 2:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Aggregator
- Replies: 1
- Views: 677
It is possible. Whether you can write the code to execute faster than that written by the experts depends on how good your programming skills are, and whether you can avoid some of the compromises they necessarily must take (for example you might only handle particular data types; they must accommod...
- Tue Feb 19, 2008 2:34 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parallel job reports failure (code 139)
- Replies: 9
- Views: 6082
Sounds like you need to get your Oracle DBA on board, and maybe your network administrator as well, to find out whether it's Oracle that's raising the SIGPIPE signals and, if so, for what reason (for example unexpected delays). That Oshexecuter.sh has core dumped may indicate that something at the D...
- Tue Feb 19, 2008 1:53 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SH: sqlplus: not found.
- Replies: 6
- Views: 3750
What is different between the good and bad runs? Are there any before-job subroutines or different paths through job sequences involved where the environment settings might be changed? Look at the log event called "Environment variable settings..." for each kind of job. Try to elucidate where they m...
- Tue Feb 19, 2008 1:51 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance of Aggregator
- Replies: 2
- Views: 960
It depends (as always). If the grouping columns are supported by indexes, then it may well be faster to do it in the database. If you have sorted data, then it may be faster to use an Aggregator stage. Is the database local or remote? If remote, it may be better to aggregate in the database, because...
- Tue Feb 19, 2008 1:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parallel job reports failure (code 139)
- Replies: 9
- Views: 6082