DSXchange

You need to 'source' your dsenv file first to properly setup your environment, then run the command.

The output from the shared container. And that is not a ton of space. As noted, monitor is while the job is running to see if that is the issue.

That's just standard Command Line 101. You either need to have its "home" directory in your PATH or you need to fully path the command to execute. That or "cd" to the home directory first and then either hope you have "." in your PATH or prefix the command with "./...

Less than a nano-second, eh? I suppose you've actually measured that. :wink: Of course, one should be dumping the score in both cases and comparing startup times and the work being done, single versus multiple nodes and contrasting that to the volume of data being processed. For all we know, a Serve...

Stop using the dollar sign.

You need to monitor the space while the job is running.

That 'delay' would also be affected by the hash partitioning, which would not be happening on a single node. So while it may not be the complete answer as to why it is faster, but it is correct that no hashing is needed on a single node job run.

As noted, "/tmp".

"gettign qbporetd"?

First suggestion?

"Please ensure that you have sufficient scratchdisks in either the default or "buffer" pools on all nodes in your configuration file"

May we know what orchadmin syntax you are using and what errors or issues you are seeing?

So, it seems that "GetSourceListC5" is the shared container. What actual stages are in there? Have you checked that you have space available in /tmp? Permissions?

Hmmm... ok. Can you please mark the post as Resolved using the button at the top of the page?

As before, yes - right.

shobhitj wrote:But I have written that because if someone has faced same problem then can give some replies.

Or you can just ask your question / state your issue. If someone can help, they will, even without you asking for anything "ASAP". Actually, you'll find that approach... counter-productive.

I'd try downloading 8.1 again, if indeed it was something you downloaded.