Archives of the TeradataForum
Message Posted: Mon, 18 Jul 2005 @ 15:18:38 GMT
We are using the FastExport utility, Release FEXP.07.07.00.000, on the WIN32 platform. We invoke the FastExport Utility, specifying a named pipe for the OUTFILE directive. We have another C-based utility that creates the named pipe, waits for FastExport to connect, and then begins reading the fastexport data from the pipe. This sometimes works, and sometimes fails, depending on the BLOCKSIZE that we specify to FastExport. We have experimented with various block sizes and can find no commonality, for example it will fail with the default BLOCKSIZE (64260) or with BLOCKSIZE of 62000, but succeed with 32000 or 64000, or even 64010. Upon failure the FastExport log file always contains the following messages:
**** 11:19:35 UTY4014 Access module error '34' received during 'write' operation: 'pmunxWBuf: fwrite byte count error (Invalid argument)' **** 11:19:35 UTY8721 Error attempting to write file <\\mach1\pipe\SamplePipe>, return code is 12.
**** 11:19:35 UTY1001 Unexpected parcel: 11, expected 10.
The second message would seem to indicate that the FEXP utlilty expected a RECORD parcel, but got an END parcel instead.
We've trimmed the C-utility to the point of just reading the data into a buffer (32 or 64K bytes at a time), and looping until completion. We don't attempt to process the data at all. When it fails, it always fails at the same point (same total number of bytes read).
Are there any blocking factors or other system or CLI parameters that we can set to get this to work successfully regardless of the BLOCKSIZE?
Note that performing the FastExport directly to a regular file works independent of the BLOCKSIZE specified.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|