Hi Pavan,
Enable the APT_PM_PLAYER_TIMING and APT_DUMP_SCORE environment variables at job level and try .
Search found 4 matches
- Fri May 06, 2011 7:40 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: datastage memory usage
- Replies: 3
- Views: 4732
- Thu Jan 27, 2011 10:12 am
- Forum: General
- Topic: Query on DataStage Repository
- Replies: 12
- Views: 8256
ok no problem anyone can help me on this plz Hi Venkat, Chullett already explained how to do that... Here in detail what Chullett said, Go to director and switch off the categories (Folders) from View menu , Then all jobs will list out in one window.. Now go to project menu and select print , there...
- Thu Nov 11, 2010 12:19 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: deadlock while using Change capture in update
- Replies: 3
- Views: 2099
I would look at how you are reading your data - each database has different syntax for ensuring that you select without taking locks. In addition, you need to ensure that no 2 nodes can update the same records - the easiest solution here is to partition on the database key. Another easy, but ineffi...
- Wed Nov 10, 2010 5:33 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: deadlock while using Change capture in update
- Replies: 3
- Views: 2099
deadlock while using Change capture in update
We are using Change data capture + transformer(using constraints to split based on change code) to implement insert/update logic. But in the update link, if a parallel odbc connector stage is used, transaction deadlock message is displayed in the log and job aborts with partial data update.eg:- out ...