Archives of the TeradataForum
Message Posted: Mon, 07 Oct 2002 @ 11:22:39 GMT
for exporting large amounts of data on Solaris we use FastExport with an Outmod that splits the data into several files due to a 2GB- border.
We now encountered some network problems, the connection to the database broke down and fexp re-sent the SQL statement to the database (with the message "UTY8720 Re-starting this FastExport task because the RDBMS crashed", but the exported data was corrupt because the Outmod did not get a "restart" signal (else we would abort as soon as this signal (entry code 5/6) was received by the Outmod) and the Export ended with return code 0.
Is there any way to avoid this? How can I recognize such a situation and react on it when he "correct" entry code is not sent (or did I miss something important)?
Thanks for any advice.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|