we are getting with an TPT export the error code 2595.
2595 The FastExport select request has been aborted.
Explanation: The current Select request has been aborted.
Generated By: LCTExpSt
For Whom: End user
Remedy: Examine the reason of the abort, do whatever necessary to correct the problem and then resubmit the Select
So far we had not been able to find out the reason.
The export is a plain table export and the SQL against this table is working fine.
Did anybody had seen this error before?
Any idea where to look for?
We have also seen similar issue with TPT Export running through JDBC via windows host.What is also strange that the error does not come up at a certain file size. It varies from some 10 to 40 GigaBytes on the drive. (There is also an “order by” in the view, to make sure records always come in a same order). this is around 100 Million export however user were able to extract 1.5 Billion Row on some other table on same database. This is on 14.00.03 (SLS11)
abhijitvyas, TPT Export doesn't use the Teradata JDBC Driver. I'm not sure what you meant here. Did you mean you're using ODBC with TPT? Or did you mean you are using the Teradata JDBC Driver's JDBC FastExport feature?
Yes that's right. Now that's clarified that there is no JDBC involvement can you kindly share any inputs on how this can be addressed ?
It would be appreciated if somebody could give us a hint as to where to start debugging when getting the 2595 error. It is three years already since we saw this problem and it keeps coming up for big tables.