Archives of the TeradataForum
Message Posted: Wed, 29 Jun 2005 @ 11:13:59 GMT
What are the possible reasons that could result in the above error message.We are getting this error on one of our mainframe jobs when it connects to teradata in ANSI mode.
This job has 4-5 simple select queries returning a large volume of data.When ever we do a rerun for this job,it runs fine.
Will tuning the queries help me to prevent this error?.
Is there a way by which I can monitor the resource usage (or check if other jobs have locked the tables needed by this job) in teradata .Any pointers in this will be of great help.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|