When pulling data off of our Teradata DB w/ Fast Export via UNIX Solaris 2.8, the script erred with the following out out.
**** 18:38:16 UTY8724 Select request submitted to the RDBMS.
**** 19:23:19 UTY8725 Select execution completed. 39824 data blocks
generated.
**** 19:28:19 UTY8726 588139 records written to output file.
UTY8732 472.40 blocks processed per minute (5-minute sample).
UTY8732 472.40 blocks processed per minute (running average).
**** 19:33:19 UTY8726 1561729 records written to output file.
UTY8732 782.00 blocks processed per minute (5-minute sample).
UTY8732 627.20 blocks processed per minute (running average).
**** 19:38:19 UTY8726 2574910 records written to output file.
UTY8732 813.80 blocks processed per minute (5-minute sample).
UTY8732 689.40 blocks processed per minute (running average).
**** 19:43:19 UTY8726 3629176 records written to output file.
UTY8732 846.80 blocks processed per minute (5-minute sample).
UTY8732 728.75 blocks processed per minute (running average).
**** 19:48:20 UTY8726 5379895 records written to output file.
UTY8732 1401.53 blocks processed per minute (5-minute sample).
UTY8732 863.66 blocks processed per minute (running average).
**** 19:53:20 UTY8726 7388329 records written to output file.
UTY8732 1613.20 blocks processed per minute (5-minute sample).
UTY8732 988.52 blocks processed per minute (running average).
**** 19:55:10 UTY4014 Access module error '34' received during 'write'
operation: 'pmunxWBuf:
fwrite byte count error, errno=27'
**** 19:55:10 UTY8721 Error attempting to write file
After examining the file system to see if it was full I noticed that the file was near 2GB.
I checked with our UNIX system admin to see if the box I was landing the data on had any file size limitations. According to the sysadmin the OS can support file sizes larger then 2 GB, and indicated we are not running Veritas. Just to humor me the sysadmin then showed me files on the system that were larger then 2 GB.
Having eliminated the 'landing zone' my attention has turned to the host. So far the people I have talked to haven't had much insight as to what the problem might be or if I can fix it. They recommended I open a ticket with NCR. Before I do that I wanted to reach out to the community to see if anyone else has had a similar problem.
Has anyone had a problem with file size limits with Teradata Fast Export? If anyone has a fix for this problem or ideas on how I can further my search I would really appreciate it.
Thanks,
Rob
**** 18:38:16 UTY8724 Select request submitted to the RDBMS.
**** 19:23:19 UTY8725 Select execution completed. 39824 data blocks
generated.
**** 19:28:19 UTY8726 588139 records written to output file.
UTY8732 472.40 blocks processed per minute (5-minute sample).
UTY8732 472.40 blocks processed per minute (running average).
**** 19:33:19 UTY8726 1561729 records written to output file.
UTY8732 782.00 blocks processed per minute (5-minute sample).
UTY8732 627.20 blocks processed per minute (running average).
**** 19:38:19 UTY8726 2574910 records written to output file.
UTY8732 813.80 blocks processed per minute (5-minute sample).
UTY8732 689.40 blocks processed per minute (running average).
**** 19:43:19 UTY8726 3629176 records written to output file.
UTY8732 846.80 blocks processed per minute (5-minute sample).
UTY8732 728.75 blocks processed per minute (running average).
**** 19:48:20 UTY8726 5379895 records written to output file.
UTY8732 1401.53 blocks processed per minute (5-minute sample).
UTY8732 863.66 blocks processed per minute (running average).
**** 19:53:20 UTY8726 7388329 records written to output file.
UTY8732 1613.20 blocks processed per minute (5-minute sample).
UTY8732 988.52 blocks processed per minute (running average).
**** 19:55:10 UTY4014 Access module error '34' received during 'write'
operation: 'pmunxWBuf:
fwrite byte count error, errno=27'
**** 19:55:10 UTY8721 Error attempting to write file
After examining the file system to see if it was full I noticed that the file was near 2GB.
I checked with our UNIX system admin to see if the box I was landing the data on had any file size limitations. According to the sysadmin the OS can support file sizes larger then 2 GB, and indicated we are not running Veritas. Just to humor me the sysadmin then showed me files on the system that were larger then 2 GB.
Having eliminated the 'landing zone' my attention has turned to the host. So far the people I have talked to haven't had much insight as to what the problem might be or if I can fix it. They recommended I open a ticket with NCR. Before I do that I wanted to reach out to the community to see if anyone else has had a similar problem.
Has anyone had a problem with file size limits with Teradata Fast Export? If anyone has a fix for this problem or ideas on how I can further my search I would really appreciate it.
Thanks,
Rob
