Partitioning sort and Sort Stage
Posted: Thu Jul 31, 2008 6:07 am
description :
I got a job abort with an err saying
"
xf_OpCnt,0: Fatal Error: Unable to initialize communication channel on SRVDA007. This is typically caused by a configuration problem. Examples of typical problems include:
1) The temporary directory, identified by $TMPDIR and/or the scratch disks in your ORCHESTRATE configuration, is located on a non-local filesystem (e. g. mounted over NFS).
2) The temporary directory is located on a filesystem with insufficient space.
"
Action
1> Cleared the scratchdisk though it was just 10 mb datafiles . Didn't clear any thing from the Temp dir had 7315 files and total data 10 mb. But still the job failed .
2>The Ds code was doing a hash partitioning and sorting in a redup stage . Changed that to Sort Stage and "same" partition for the redup stage. And it worked.
that made me think what is the difference in case of memory usage in sort stage and partitioning sort ? Assuming same keys and Hash partitioning and same server load.
And should I get this error on the first place when it is DS windows server and the scratchdisk folder size is virtually unlimited ?
looking forward to your replies.
&
Thank you for sharing your views ....
I got a job abort with an err saying
"
xf_OpCnt,0: Fatal Error: Unable to initialize communication channel on SRVDA007. This is typically caused by a configuration problem. Examples of typical problems include:
1) The temporary directory, identified by $TMPDIR and/or the scratch disks in your ORCHESTRATE configuration, is located on a non-local filesystem (e. g. mounted over NFS).
2) The temporary directory is located on a filesystem with insufficient space.
"
Action
1> Cleared the scratchdisk though it was just 10 mb datafiles . Didn't clear any thing from the Temp dir had 7315 files and total data 10 mb. But still the job failed .
2>The Ds code was doing a hash partitioning and sorting in a redup stage . Changed that to Sort Stage and "same" partition for the redup stage. And it worked.
that made me think what is the difference in case of memory usage in sort stage and partitioning sort ? Assuming same keys and Hash partitioning and same server load.
And should I get this error on the first place when it is DS windows server and the scratchdisk folder size is virtually unlimited ?
looking forward to your replies.
&
Thank you for sharing your views ....