Hi Carrie I've found the information in this post extrememly helpful, but I do have a question regarding limiting sessions for the TPT Stream Operator. We are on a 4 node 2750 appliance runniing TD14.10 SLES11. The application team is using Informatica TPT API to run load jobs using the Stream Operator and each job initiates 23 sessions - most of which sit idle. They also at times run several jobs concurrently and I often see over 100 idle sessions for that user, with just a few active. They are using the "UtilityDatasizeSmall" query band which does not have any effect because the Stream Operator sessions are not classified as utility sessions. So my question is : How do I get the Stream Operator to limit the sessions per job ? I'm thinking that 12 to 14 might be a better value.
Regards
Mark
Hi Carrie
I've found the information in this post extrememly helpful, but I do have a question regarding limiting sessions for the TPT Stream Operator. We are on a 4 node 2750 appliance runniing TD14.10 SLES11. The application team is using Informatica TPT API to run load jobs using the Stream Operator and each job initiates 23 sessions - most of which sit idle. They also at times run several jobs concurrently and I often see over 100 idle sessions for that user, with just a few active. They are using the "UtilityDatasizeSmall" query band which does not have any effect because the Stream Operator sessions are not classified as utility sessions. So my question is : How do I get the Stream Operator to limit the sessions per job ? I'm thinking that 12 to 14 might be a better value.
Regards
Mark