fastexport gives Access module error '34'

Tools
N/A

fastexport gives Access module error '34'

Hi,

If any one can suggest how to overcome the following error:

I am trying to export one small table (approx. size is only 1 megabyte) to a remote pipe(\\pc2\pipe\Pipe_1755) using demo Teradata Fastexport v07.06.02.000 on my XP pc. But it gives access module error 34.

On the other hand, my export works when I used local pipe (\\.\pipe\Pipe_1755) for the same table, and also worked for some other tables even using remote pipe name. This also works when I export to a binary file, and import this binary file by me import process.

As I am aware about the max file size (specially for unix) and correct named pipe name, which might cause such error. But this is a small table and pipe name is correct as they worked with other tables. May be this is happening due to using the demo teradata.

If someone could point to the right cause.

Thanks,
Mahib

**** 09:27:40 UTY4014 Access module error '34' received during 'write' operation: 'pmunxWBuf:
fwrite byte count error (Invalid argument)'
**** 09:27:40 UTY8721 Error attempting to write file \\pc2\pipe\BWPipe_1755, return code is
12.
========================================================================
= =
= Logoff/Disconnect =
= =
========================================================================
**** 09:27:40 UTY1001 Unexpected parcel: 11, expected 10.

my table structure is-

CREATE TABLE table1
(
col1 INTEGER,
col2 INTEGER,
col3 SMALLINT,
col4 SMALLINT,
col5 DECIMAL(13,0),
col6 DATE FORMAT 'YY/MM/DD',
col7 CHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC,
col8 DATE FORMAT 'YY/MM/DD')
PRIMARY INDEX ( col1 );

Excerpt from my fastexport script:

.BEGIN EXPORT SESSIONS 2;
.EXPORT OUTFILE '\\pc2\pipe\BWPipe_1755' FORMAT binary MODE indicator;
SELECT
col1,
col2,
col3,
col4,
col5,
col6(format 'YYYY-MM-DD'),
col7,
col8(format 'YYYY-MM-DD') FROM table1 WHERE 1=1;
.END EXPORT;
1 REPLY
N/A

Re: fastexport gives Access module error '34'

Its purely result of insufficient disk space. I had the same issue and i corrected it by changing the file output directory location.