Search found 104 matches
- Wed Oct 14, 2009 7:59 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Look-up
- Replies: 7
- Views: 3629
- Wed Oct 14, 2009 7:47 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: ODBC parallel reading
- Replies: 0
- Views: 791
ODBC parallel reading
Hi guys, Did you know you could read from ODBC with parallel method : 1) Set partition column in the ODBC stage using a numerical field that is ideally a key. 2) edit the SQL clause and add 'WHERE %orchmodColumn%' 3) In the next stage which dispatches data onto nodes, use the Modulus method on the s...
- Thu Oct 01, 2009 7:25 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Facts loading strategy
- Replies: 1
- Views: 1040
Re: Facts loading strategy
Hey guys, I'm loading a 3 300 000 rows table containing invoices. I have two modes : 1) Full loading 2) Daily Loading For the daily loading mode I have 2 fields containing the creation date and the update date in the source date. Thus I can filter only records created or updated after the last load...
- Thu Oct 01, 2009 3:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Facts loading strategy
- Replies: 1
- Views: 1040
Facts loading strategy
Hey guys, I'm loading a 3 300 000 rows table containing invoices. I have two modes : 1) Full loading 2) Daily Loading For the daily loading mode I have 2 fields containing the creation date and the update date in the source date. Thus I can filter only records created or updated after the last load....
- Mon Sep 28, 2009 6:58 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Reg:Fatal Error in the Datastage 8.1
- Replies: 3
- Views: 4109
Re: Reg:Fatal Error in the Datastage 8.1
Hi, In one of the ETL job we are getting the Fatal Error as : Fatal Error:Not a list value ;table. I was not able to figure out,what was the exact error in the ETL job. About the job design: Basically we are reading the Data from Database table and doing 6 look ups including Range look up on some o...
- Fri Sep 25, 2009 8:58 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Partitioning with Transformer stage
- Replies: 8
- Views: 3723
- Fri Sep 18, 2009 6:10 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: INSERT useing Oracle stage fails - Special characters
- Replies: 17
- Views: 6575
That would not be a hex or binary viewer. The goal is to get the numeric representation of what is in that character. ... IBM's answer : CCSID 500 is a EBCDIC charset. Our application will not be able to work with this. You have to convert to a equivalent ASCII charset using the DD driver. Since CC...
- Thu Sep 17, 2009 2:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD - Effective Date - Do not always use currentTimeStamp()
- Replies: 5
- Views: 3485
Whoa algfr! You're out in the weeds. Why do you think you have to use current timestamp for a type 2 effective date? I think I've never used that derivation, so I know it's not a stage requirement. Let's go back to the derivation that you would like to use and post the error message that you're get...
- Wed Sep 16, 2009 2:24 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD - Effective Date - Do not always use currentTimeStamp()
- Replies: 5
- Views: 3485
- Tue Sep 15, 2009 5:06 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update performance issue
- Replies: 26
- Views: 10049
whats being used as upsert mode, insert then update or update then insert? what happens if you lower the array size/transaction size/commit interval. Oracle places a row level lock during insert/update. seems like update query is waiting for the inserted record to commit and then its updating the s...
- Tue Sep 15, 2009 3:01 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update performance issue
- Replies: 26
- Views: 10049
- Tue Sep 15, 2009 2:23 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update performance issue
- Replies: 26
- Views: 10049
There seems to be both updates and inserts in the same time, thus causing locks. When the data volume is lower or the initial table is empty, it runs fine.algfr wrote:How is that ? Do you mean there is a configuration to be done ? Please explain.Sainath.Srinivasan wrote:Database level integrity constraints and commit intervals.
- Thu Sep 10, 2009 5:15 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Close command : parallel
- Replies: 9
- Views: 2180
- Wed Sep 09, 2009 9:13 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Close command : parallel
- Replies: 9
- Views: 2180
- Wed Sep 09, 2009 3:11 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Close command : parallel
- Replies: 9
- Views: 2180
Close command : parallel
Just a quick question.
When I perform a close command and am running on 2 nodes, is this normal that the close command perform for EACH node and not only once after the load is completed ?
I use Oracle
Thanks
When I perform a close command and am running on 2 nodes, is this normal that the close command perform for EACH node and not only once after the load is completed ?
I use Oracle
Thanks