Search found 4992 matches
- Wed Oct 12, 2005 3:02 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Having problems proving latest claims in "Tips: Hash fi
- Replies: 5
- Views: 1197
- Wed Oct 12, 2005 1:13 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Concurrent reads from sequential file
- Replies: 4
- Views: 1058
- Wed Oct 12, 2005 12:07 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error when executing command
- Replies: 2
- Views: 2116
Your after routine ran a script xxxx.ksh that exited with a non-zero return code. Is this okay? You need to know, it's your script. The "-v" looks suspiciously close to the xxxx.ksh, is this a typo? If you want non-zero return codes to be valid, you have to check the box that says ignore non-zero re...
- Wed Oct 12, 2005 12:05 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Datastage and reporting
- Replies: 6
- Views: 1096
- Wed Oct 12, 2005 11:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Datastage and reporting
- Replies: 6
- Views: 1096
- Wed Oct 12, 2005 8:57 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Job Running Slow - Need Guidance to improve performance
- Replies: 9
- Views: 2572
You really need to know how many inserts and how many updates are being processed. The suggestions to split inserts from updates and bulk load the inserts are excellent ones. Your data could be trending 90% updates and 10% inserts, with the updates at the back of your source data. Your job could fly...
- Wed Oct 12, 2005 8:52 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: No. of Warning Message
- Replies: 1
- Views: 641
- Wed Oct 12, 2005 8:50 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error Code 256
- Replies: 5
- Views: 3537
- Tue Oct 11, 2005 3:40 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Attempted READ of record ID larger than file/table maximum
- Replies: 9
- Views: 4083
- Tue Oct 11, 2005 3:36 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: ORAOCI8 is used as lookup stage
- Replies: 12
- Views: 2013
Did anyone read my post? User defined sql is not executed to view data in a reference lookup. Lookup's SQL by their very nature can't be used in the View Data button. Since the SQL is expected to return a single row, you have to provide the Where clause information. To view data, you provide nothing...
- Tue Oct 11, 2005 3:30 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: FTP errors
- Replies: 4
- Views: 508
I know that FTP command line is faster than FTP stage because the FTP command line achieves maximum throughput by not waiting on DS to process anything. The transfer is dedicated, and has the potential to be very timely and reduce the chance of transfer errors, retries, and timeouts. Once the FTP is...
- Tue Oct 11, 2005 3:26 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: make changes to a shared container
- Replies: 8
- Views: 2963
almost irrational dislike of containers I think I'm quite rational. I rationally hate the implementation of the concept, but I'm cool with the concept. DS Functions are great examples of reusability. DS Transforms are NOT well implemented. After 9 years of major releases of DS you'd think engineeri...
- Tue Oct 11, 2005 2:22 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Generate Sequence Number
- Replies: 3
- Views: 1060
Re: Generate Sequence Number
How about accomplishing this at the database level, like using a sequence generator. Does this have any disadvantages compared to the one generated by the Datastage. That sticks a choke point in the database. You have a process individually handing out the next key ala a sequence. If you are simult...
- Tue Oct 11, 2005 2:02 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: FTP errors
- Replies: 4
- Views: 508
- Tue Oct 11, 2005 2:00 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Attempted READ of record ID larger than file/table maximum
- Replies: 9
- Views: 4083
Read it for yourself: # MAXKEYSIZE - This sets the maximum number of characters that can # be used within a primary key. The minimum value of 255 retains # the historical maximum key length as well as the historical encoding # of record locks within a 64-byte entry. Any other value, which must # be ...