Archives of the TeradataForum
Message Posted: Thu, 26 Apr 2007 @ 09:35:54 GMT
With all due respect to the previous posters, their advice will not help you solve your problem.
The advice provided (ulimit, 2GB etc) relate to real files, not named pipes. A named pipe is an in memory FIFO queue, not a file. However, this distiniction can be confusing because both named pipes, regular files and other things all appear in a standard directory listing.
Now to your problem. I'm not sure what the "isStaged" property is that you are refering to, perhaps it is in custom software that generates multi-load scripts - I can't help you with that, you will need to contact the people who supplied it.
However, I can tell you that multi-load (for whatever reason) will attempt at times attempt to "reposition" its "pointer" into the input file using an fseek operation.
Unfortunately fseek can not be performed on a pipe (named or anonymous) hence the error message you are getting:
10:48:08 UTY4014 Access module error '34' received during 'set position' operation: 'pmUnxDskSetPos: fseek error (Illegal seek)'
If you want to use a named pipe to supply data to multi-load, your script should either
1) use the named pipes access module (easiest option and provides a number of additional features)
2) develop an INMOD to handle the named pipe yourself (requires 'C' programming and will take some time).
So why doesn't the error occur all of the time. I don't know - but you typically only seem to encounter this problem with larger files.
I hope this helps
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|