No worries... sometimes people search for "too much", too specific of a search string. Can help to cut it back, to use a more generic portion of the message. Sure it gives you more to weed thru, but your fish is in the net. Somewhere.
Do you still need help? If so, please do give us some details of your job design, stages used, settings, etc.
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:No worries... sometimes people search for "too much", too specific of a search string. Can help to cut it back, to use a more generic portion of the message. Sure it gives you more to weed thru, but your fish is in the net. Somewhere.
Do you still need help? If so, please do give us some details of your job design, stages used, settings, etc.
Hi,
Thanks a lot for help...What we have figured out is that in one of our job where this problem is occurring, we are having a CDC stage, few joiners and the data is getting loaded in Oracle table. Now the data volume is too high almost 20 million records.
we were checking for the performance of jobs on a project level and we've enabled the $APT_PM_PLAYER_TIMING parameter. This was causing the DataStage server to operate GetTimeOfTheDay function with AIX. This was the prime reason where time between 2 subsequent records was having a difference of 2 milliseconds on the lesser side. So one of our team member who had a good knowledge of AIX set up some parameter that resolved the issue for us.
Thanks & Regards
Parag Saundattikar
Certified for Infosphere DataStage v8.0
chulett wrote:No worries... sometimes people search for "too much", too specific of a search string. Can help to cut it back, to use a more generic portion of the message. Sure it gives you more to weed thru, but your fish is in the net. Somewhere.
Do you still need help? If so, please do give us some details of your job design, stages used, settings, etc.
Hi,
Thanks a lot for help...What we have figured out is that in one of our job where this problem is occurring, we are having a CDC stage, few joiners and the data is getting loaded in Oracle table. Now the data volume is too high almost 20 million records.
we were checking for the performance of jobs on a project level and we've enabled the $APT_PM_PLAYER_TIMING parameter. This was causing the DataStage server to operate GetTimeOfTheDay function with AIX. This was the prime reason where time between 2 subsequent records was having a difference of 2 milliseconds on the lesser side. So one of our team member who had a good knowledge of AIX set up some parameter that resolved the issue for us.