The reason is happening is due to the fact that Sybase Open Client connectivity used 64-bit architecture while the ODBC driver is designed for 32-bit architecture that is used by Datastage.
Hence this instability & non consistent behaviour.
Regards,
NV
Search found 178 matches
- Fri Dec 08, 2006 6:24 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DataStage 7.5.x with Sybase IQ 12.6 on Linux
- Replies: 6
- Views: 3512
- Fri Dec 08, 2006 6:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sybase table locked
- Replies: 2
- Views: 940
- Wed Sep 27, 2006 1:06 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle - Delete & Then Insert
- Replies: 7
- Views: 2093
- Tue Sep 26, 2006 11:00 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle - Delete & Then Insert
- Replies: 7
- Views: 2093
- Mon Sep 25, 2006 11:41 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle - Delete & Then Insert
- Replies: 7
- Views: 2093
- Mon Sep 25, 2006 8:59 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle - Delete & Then Insert
- Replies: 7
- Views: 2093
Oracle - Delete & Then Insert
Hi, We have a requirement where we need to clean the table prior to insert. Example if src has 100 records. The idea is, if for some reason the job fails/aborts/hangs (may be due to DB problem or any other reason), when we RE RUN the job it should clear the previous loaded records (if any) and then ...
- Wed Sep 13, 2006 8:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: StringToDecimal Conversion Error
- Replies: 3
- Views: 1801
- Wed Sep 13, 2006 8:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: StringToDecimal Conversion Error
- Replies: 3
- Views: 1801
StringToDecimal Conversion Error
Hi, I am reading "amount" from a fixed width seq file as a Char e.g (2259 or 36153.35) and then the only transformation I do before writting to an Oracle table is do type conversion using StringToDecimal. For some strange reason it stores these values as 2259.580000000000 and 36153.3499999...
- Tue Sep 05, 2006 1:48 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Header & Trailer Record Warning
- Replies: 11
- Views: 5064
- Fri Sep 01, 2006 2:31 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Header & Trailer Record Warning
- Replies: 11
- Views: 5064
- Tue Aug 29, 2006 2:38 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Multi Instance job
- Replies: 5
- Views: 1444
- Tue Aug 29, 2006 1:57 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Multi Instance job
- Replies: 5
- Views: 1444
- Tue Aug 29, 2006 12:55 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Multi Instance job
- Replies: 5
- Views: 1444
Multi Instance job
Hi, we are using a multi instance job and will be passing values like B and C as invocation ids so that we can read from different source files. I want these to be concatenated to the final outbound files respectively.So what should I add as a part of output filename to be able to do it. e.g. we wan...
- Tue Aug 29, 2006 7:14 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Header & Trailer Record Warning
- Replies: 11
- Views: 5064
- Mon Aug 28, 2006 11:25 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Header & Trailer Record Warning
- Replies: 11
- Views: 5064
Header & Trailer Record Warning
Hi, I get the following warning message when I try to read from the Source Sequential file "SEQ_Histpion,0: Delimiter for field "Field004" not found; input: {0d}, at offset: 107" The reason is that the Header (and also Trailer) record do not have same metadata as all other data r...