Changing the array size and record count to 1 is also working...
Apparently, there is something wrong with the values stored in memory or something... and when the DB is making commits for each line, then, there is no problem anymore...
A bit strange...
Search found 18 matches
- Wed Jun 27, 2012 6:02 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modified field in logs : wrong dates
- Replies: 7
- Views: 8343
- Wed Jun 27, 2012 6:00 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modified field in logs : wrong dates
- Replies: 7
- Views: 8343
The good news is that I succeeded in reproducing the problem ! When the ODBC stage is doing ONLY inserts, everything is working properly ! But if there is one update only, then, all the inserts are wrong (for the dates)! I think there is a bug somewhere... As a workaround, I think I will split the u...
- Wed Jun 27, 2012 2:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modified field in logs : wrong dates
- Replies: 7
- Views: 8343
Is it possible that the INSERT statement and the UPDATE statement make these differences ? Apparently, when the insert is made, the date is wrong and when the record is updated, it's correct ! :shock: The target is on ODBC. Can the ODBC driver cause this problem ? The SQL is generated and not user-d...
- Wed Jun 27, 2012 1:23 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modified field in logs : wrong dates
- Replies: 7
- Views: 8343
The source field is an Oracle DATE field. I've tried to convert it to a varchar field, using the following syntax : TO_CHAR(TRANSACTION_DATE,'YYYY-MM-DD HH24:MI:SS'). I've populated the data into a flat file and I got the good values (the same as in the source) but it's still wrong in the SQL Server...
- Tue Jun 26, 2012 7:43 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modified field in logs : wrong dates
- Replies: 7
- Views: 8343
Modified field in logs : wrong dates
Hello ! I'm asking a question to Datastage gurus because I'm totally lost here. I've got a simple parallel job with an Oracle connector as a source, then a simple transformer and an ODBC stage as the target. The target is actually an SQL Server Database. I get wrong results in the date fields in the...
- Wed Jun 20, 2007 3:43 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Conditional update of a field
- Replies: 1
- Views: 1327
Conditional update of a field
Hi everybody ! I wanted to know if there is a way to make an update of a field only if a certain condition is OK. I have a lot of fields and I want to update all of them in all cases but one only if a condition is satisfied for a piece of data. In the transform, I would like to make this test : If l...
- Wed Feb 28, 2007 10:58 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Universe Stage - [RPC] error code = 81002 - Timeout ?
- Replies: 9
- Views: 6911
I don't exactly know how to achieve that ! :oops: Must I Telnet the DS server or can I manage to test it in the Datastage Administrator ? But this request should be well-build because sometimes it's working well... I think there is no syntax-error... I can 'view data' without any error when I look a...
- Wed Feb 28, 2007 8:01 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Universe Stage - [RPC] error code = 81002 - Timeout ?
- Replies: 9
- Views: 6911
Ok, I will remove extra quotes around the table name (but it shouldn't resolve the problem since some of the treatments are going well...) I've already read Ray's answer on that page but I don't see why this answer is related to my problem... :oops: I don't have a 'GROUP' field in my table... If Ray...
- Wed Feb 28, 2007 3:18 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Universe Stage - [RPC] error code = 81002 - Timeout ?
- Replies: 9
- Views: 6911
Universe Stage - [RPC] error code = 81002 - Timeout ?
Hi, I have a problem in a job using Universe stages... In my job log I get the following error (some of the executions are ending well and some are throwing this error): TraverseesR2kSeafret..Transformer.FS_FERRYY000: DSD.BCIGetByKey call to SQLFreeStmt failed. SQL statement:SELECT DS.FE.FERRYY000.@...
- Thu Feb 08, 2007 10:47 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
I made a mistake ! I did not check the box (Log warnings after activities that finish with status other than OK). That's why i was not getting the warning message... Now I get the warning message even with only two stages ! The two stages are the following : Routine activity with two triggers : Fail...
- Thu Feb 08, 2007 10:16 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
- Thu Feb 08, 2007 10:10 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
- Thu Feb 08, 2007 8:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
- Thu Feb 08, 2007 7:16 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
Thanks Ray for answering... but I still can't manage to make it work... :? I have a routine Activity that is calling a routine and the return code of the routine is not 0, it is a string (I use it as DB connection parameter). I have created 2 triggers (that go to the same sequencer) : One is custom ...
- Thu Feb 08, 2007 5:23 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine job did not finish OK
- Replies: 15
- Views: 19705
Hi everybody ! I have the same problem as explicited and i have not very well understood what ray said... :oops: How can i Provide an explicit trigger from my Routine activity that handles all expected return values ? The trigger is the third tab in my routine activity, right ? What must i add in or...