Archives of the TeradataForum
Message Posted: Tue, 09 Dec 2003 @ 08:01:31 GMT
I have been receiving the following error on a couple of my multiload scripts the last few weeks:
"UTY3410 A semi-colon was not found to terminate the current statement."
This is caused because every time the multiload script is opened either by a mload or by a person notepad is adding a date/time stamp to the bottom of the script. As I see it MLoad reads the script, preforms what is needed (deletes, insert, updates), reads the end transaction and then tries to read the date/time stamps (of course no semi-colons at the end). Once it does this the script then errors out. If you do not clean up the errors from this then of course the table is locked and you will not be able to load the next day's data. I have attached the last part of the out log for people to view.
Has anyone else experienced this? What is most annoying is that the same script has been running perfectly fine for the last several months and now we are starting to get this type of error messaging.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|