Search found 53125 matches
- Tue Feb 06, 2007 3:55 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Unexpected Job Failure
- Replies: 14
- Views: 8374
Are you using TENACITY? If not, an process that can not get a Teradata session will abort. It may be this that you are seeing, and would explain the apparent randomness of the behaviour - sometimes processes can all get sessions, occasionally one can't. TENACITY will allow such sessions to wait. (As...
- Tue Feb 06, 2007 3:50 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: hashed file key field
- Replies: 12
- Views: 3807
- Tue Feb 06, 2007 3:48 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Hash File Performance Problem
- Replies: 10
- Views: 3520
- Tue Feb 06, 2007 3:42 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: environmental variable in a rountine
- Replies: 12
- Views: 3810
- Tue Feb 06, 2007 3:41 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: what is DSJ.ME ?
- Replies: 7
- Views: 5719
- Tue Feb 06, 2007 3:38 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Return function in datastage routine
- Replies: 6
- Views: 1575
- Tue Feb 06, 2007 3:31 pm
- Forum: General
- Topic: Has file lookup using less than or rather than
- Replies: 2
- Views: 1268
- Tue Feb 06, 2007 1:42 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: How to abort a job in Afterjob sub routine
- Replies: 18
- Views: 3988
Your requirement to abort the job is unnecessary. A far better design would be to check that the row (or key value) in question does not already exit in the target table before attempting to insert it. Any row that does already exist can be captured in a different ("reject"?) stream and processed ac...
- Mon Feb 05, 2007 8:13 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Error : Not bounded length
- Replies: 31
- Views: 7176
It means that there is at least one field in your job design defined as VarChar but without a Precision (maximum length) value. While this is legal in some places (for example Data Set stages) it is not legal in others. Whichever operator governed by your particular combined operator controller is c...
- Mon Feb 05, 2007 8:11 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: From sequencial file to sequencial file
- Replies: 3
- Views: 972
- Mon Feb 05, 2007 8:09 pm
- Forum: General
- Topic: orchestrate schema vs plug-in metadata definitions
- Replies: 3
- Views: 1559
- Mon Feb 05, 2007 5:39 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: dspackinst - Package installation
- Replies: 11
- Views: 2002
- Mon Feb 05, 2007 3:48 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: ABOUT AIX VERSION
- Replies: 9
- Views: 1327
- Mon Feb 05, 2007 3:46 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: How to configure DSN for Oracle In unix (Server)
- Replies: 22
- Views: 8704
- Mon Feb 05, 2007 3:44 pm
- Forum: General
- Topic: how: reject file rows that have too many cols (parall jb)
- Replies: 1
- Views: 1019
Welcome aboard. :D The Sequential File stage can have a second output link, called the "rejects" link. This link will capture, as a raw string, any row that does not match the metadata (table definition) being used to read the file. Subsequently in the job, rows on the rejects link can be reprocesse...