I am experiencing adverse impact of such partitioning. I am planning to change it to same partitioning ans see how it performs. Will share the results once done.rkashyap wrote:Large no of partitions (36) on the table may have adverse impact on performance.
Search found 78 matches
- Tue Jul 21, 2015 12:52 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Datastage - Oracle Connector - Partitioned table-dump score
- Replies: 5
- Views: 5187
- Fri Jul 17, 2015 2:55 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Datastage - Oracle Connector - Partitioned table-dump score
- Replies: 5
- Views: 5187
- Thu Jul 16, 2015 7:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Datastage - Oracle Connector - Partitioned table-dump score
- Replies: 5
- Views: 5187
Datastage - Oracle Connector - Partitioned table-dump score
Hi Guys, I am trying to understand below job score. Environment Details - DataStage - 9.1.2 Oracle -- 11gR2 OS - Oracle Solaris Config File - 4 node Oracle connector Partition Type - Oracle Connector Write Mode - Insert Target table is partitioned by Range Method Job Detail -- DataSet ------ > Copy ...
- Mon Jul 13, 2015 12:05 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Pivot Enterprise Stage - Vertical Pivot issue
- Replies: 8
- Views: 8187
- Sun Jul 12, 2015 11:42 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Pivot Enterprise Stage - Vertical Pivot issue
- Replies: 8
- Views: 8187
- Sat Jul 11, 2015 8:22 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Pivot Enterprise Stage - Vertical Pivot issue
- Replies: 8
- Views: 8187
This issue is resolved now. Even though hash partitioning and sorting were set up properly it was not behaving as per expectation. Issue Identification:- Upon observing dump score it was cleat that Vertical Pivot stage was inserting it's own 'tsort' operator which was only happening on KEY columns a...
- Fri Jul 10, 2015 6:23 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Pivot Enterprise Stage - Vertical Pivot issue
- Replies: 8
- Views: 8187
- Fri Jul 10, 2015 8:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Pivot Enterprise Stage - Vertical Pivot issue
- Replies: 8
- Views: 8187
Pivot Enterprise Stage - Vertical Pivot issue
I am trying to pivot rows to columns using Pivot Enterprise Stage (vertical Pivot) Somehow I am unable to execute successfully in parallel mode. Here is the detailed issue. I have mainly three columns KEY (bunch of group by columns) SEQ (values ranging 1 to 48 ) and VALUE (contains actual values - 4...
- Wed Nov 28, 2012 6:06 pm
- Forum: General
- Topic: Mirror Image of InfoSphere environment, possible?
- Replies: 2
- Views: 1573
Mirror Image of InfoSphere environment, possible?
Hi Experts, 1)My question is whether it is possible to create a mirror image of the datastage env on a seperate Unix matchine to use for a limited time say 3 weeks, just like a disaster recovery mechanism? 2)In this scenario does Licencing based on CPUs be an issue? 3)If the IP and the hostname chan...
- Wed Oct 31, 2012 2:15 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695
- Sun Oct 28, 2012 8:37 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695
- Tue Oct 23, 2012 2:45 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695
- Sun Oct 21, 2012 9:03 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695
Hi ArndW, Thanks, this is a very nice workaround. But I want the lookup stage to work in this case. This will also help me solve a bigger issue of this perticular server not performing well in case of jobs with lookup stage. This server performs slower than a server with less resources and very same...
- Sun Oct 21, 2012 8:54 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695
Re: Lookup job fails with error "Could not alloc memory
Hi Rohit, THe database is Oracle. Data is over 9 million or around 7 Gb in the reference. The hardware architecture of both servers are not same. It is very strange that same jobs runs fine with same data/DB in a server with 2 CPU, 15 Gb Ram less space allocated to Scratch and Datasets. But is fails...
- Thu Oct 18, 2012 12:32 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Lookup job fails with error "Could not alloc memory for
- Replies: 21
- Views: 9695