Issue description:
When a job that is loading an empty table through FastLoad Functionality (Teradata Connector) aborts, it causes the mentioned table to be left in an irrecoverable Lock state, which cannot be cleared using an empty FastLoad, and which only workaround is to drop and recreate the table.

Hi,

Query on TASM. If we configure a group to have a MAXIMUM CPU utilisation of 60 Seconds, we would expect the query to migrate over to the next group when it reaches 60 Seconds.

Why then do we see queries running and consuming more than 60 seconds (sometimes up to 1 hours worth of CPUTIME) before migrating. We can see this in viewpoint, looking in DBQL only show the startingbands and ending bancds.