TargetNetezaStage: Failed to write to named pipe /tmp/server02_49736_nzw_0_1_20160310041042104013. Error code: 32 (CC_NZPipe::write, file CC_NZUnixPipe.cpp, line 321)
Should have enough space != does have enough space. Necessarily. Monitor the space during the load to be certain. Then we can move on to other possible causes.
The named pipe is used to transport the data through the ETL server.
-craig
"You can never have too many knives" -- Logan Nine Fingers
What's weird is that I didn't see this file increasing in size while the job was running, so I'm wondering if data is transferred into named pipe in one large batch...
There's a number of factors since many UNIX processes can leverage the /tmp space. If you've moved it elsewhere and still have the issue you could be seeing a problem with the connector itself. Unfortunately all the "32" means is "broken pipe" which doesn't really tell us anything and several issues could cause the pipe to break. Probably best to involve support on this one.
-craig
"You can never have too many knives" -- Logan Nine Fingers