I am a Teradata user rather than developer. My team uses SAS (9.4, windows desktop SAS) to access Teradtata (version 14) via the SAS SQL pass-through. In the past few months we have begun receiving errors from Teradata similar to these:
However, the Teradata team insists that they have changed the TDWM rules so that queries are not aborted by the TDWM, but put into the delay queue. Security settings prevent me from viewing the the TDWM rules database on our site so I have no way of verifiying this.
Assuming our database administrators are correct, is there any way Teradata would return the error messages above if my queries were not aborted by the workload manager? Our database administrators are working on this problem from their end, but my team of analysts supports about 30 users who are receiving this error multiple times daily. If there is anything I can do to help, I am willing to try.
It appears that the Workload Level Throttle for workload definition WD_STANDARD_SHORT is set to REJECT any queries over 17. The abort and error can be avoided if the option of REJECT is set to DELAY.
This can be done through Viewpoint and the Workload Designer Portlet. A DBA will need to edit the current ruleset by going into the Workloads and selecting WD_STANDARD_SHORT. Once there, click on Throttles. Make sure that the Default and all throttle settings in all Planned Environments and Health Conditions are set to DELAY and not REJECT. Do this for WD_STAND_VERY_LONG as well.
This is because of an override option by the client driver which says to reject the requests if it encounters a delay. DBSControl internal parameter 311 DisableFastFail should be set to TRUE to not reject the queries. The default is set to FALSE. When you change it to TRUE, they will not be rejected anymore