All Forums Tools
lagerg 1 post Joined 11/10
10 Nov 2010
TPT Load Operator error table being loaded?

Using the tpt load operator i received an error stating my error limit has exceeded. so when i go to look at the error tables is says the select operation is not allowed and that my error table is being loaded. How do i know what the error is if i can't see the contents of the error table? version TPT 12

feinholz 1234 posts Joined 05/08
10 Nov 2010

This is a DBS issue, not a TPT issue.

When a data load job is running, the target and error tables remain locked during the acquisition phase. Since your job terminated in the middle of the acquisition phase, the tables remain in a locked state.

Again, this is not a client software issue (FastLoad jobs would result in the same behavior), but a DBS issue.

--SteveF

feinholz 1234 posts Joined 05/08
11 Nov 2010

BTW, another solution is to run a script with a BEGIN LOADING and END LOADING (no insert statement). This will cause the data loaded, up to the last checkpoint, to be committed to the table and then the locks will be released.

--SteveF

Jimm 298 posts Joined 09/07
11 Nov 2010

If you specify locking for access on rhe query, you can usually read the table:

Locking errortable for access
Select * From errortable;

teradater 29 posts Joined 11/10
17 Nov 2010

try this sql to see error tables, while they locked (Teradata Fastload Reference):
locking error_table_name for access
select errorcode, errorfieldname
from error_table_name;

ishtiaq.ahmed 1 post Joined 01/11
17 Jan 2011

If one TPT script is executing and there is an error while its execution. The error and work tables are locked now. So when i execute TPT script again. this time due to locked table loading is not done. So is there any way to unlock the error and work tables of TPT in case of incompletely run job. Becuase now i have to drop the table each time.

feinholz 1234 posts Joined 05/08
19 Jan 2011

As long as the restart log table is preserved, so that the restarted TPT job can retrieve the correct job status, the restarted job should run just fine without the need to drop the error tables and start all over.

If you are still experiencing issues, please email me so I can have you send me all of the pertinent logs and look over the issue.

Or you can open an incident with the GSC aand they can take a look.

The TPT operators do not require the error tables to be dropped prior to restarting a job that already ran.

--SteveF

ProudCat 13 posts Joined 09/11
02 Dec 2011

Hi, I'm experiencing exactly same issue. I ran tdload from a file but it failed at a certain data point however it failed to remove a lock from the table. So now I cannot select or truncate the table. Running tdload again returns me an error

Got RDBMS Error 2652: Operation not allowed: mydb.mytable is being Loaded.

This is clearly an incorrect behavior. The table should have been unlocked in the first place. However how do I clean up the lock now?

 

 

 

feinholz 1234 posts Joined 05/08
02 Dec 2011

When a job fails prematurely, the target table remains locked. This lock is enforced by the Teradata database.

However, the problem with the restart was a bug in our code and that has been fixed in 13.10 and so try downloading the latest 13.10 patch for TPT and that should fix this issue.

(The problem appears to have been fixed in efix patch #6, but it is always best to download the latest.)

 

 

--SteveF

ProudCat 13 posts Joined 09/11
05 Dec 2011

Thanks a lot for the response. We do have 13.10 version.

tdload -v

 Teradata Load Utility Version 13.10.00.04

What is the exact version of patch #6?

BTW, in order to solve this I dropped our table then it still failed and had to manually cleanup 3 tables _err, _log and _XXX (don't remember). And had to remove files from /var/opt/teradata/tbuild/checkpoint/ because it tried to resume a job while in fact the table is empty.

feinholz 1234 posts Joined 05/08
05 Dec 2011

Always download the latest and greatest set of patches for the entire product.

Efix patch #7 would be 13.10.00.07.

But you need to make sure to download all patches for all packages for TPT.

 

--SteveF

ProudCat 13 posts Joined 09/11
05 Dec 2011

I'm not sure how to go about it...

Is there a particular place on the Teradata website where I can download the latest patch? I clicked on the Download section and it contains a lot however I do not see anything pertaining to TPT patches.

Or do we have to go thru the official support channels to get the latest software?

The current version is from the CD we received originally.

Thanks a lot!

 

 

feinholz 1234 posts Joined 05/08
05 Dec 2011

You would have to go to the Teradata At Your Service website, but you will probably need to provide some type of customer information.

That is not my area (I am in engineering) so you may have to ask around with your account tea, to find out how you get to the patches.

 

--SteveF

brindamaiti 11 posts Joined 10/11
04 Apr 2012

Hello,

We are facing exactly the same issue. 

It is not possible to apply a patch now.

Can you please tell me the full name of the _err , _log and other work tables which need to be cleaned  up.

And if we are running as a user in the Teradata, what is the location of the tables . In the user's schema or dbc schema.

Thanks.

best regards,

Brinda

P.s: This help is very appreciated

feinholz 1234 posts Joined 05/08
04 Apr 2012

The names of the tables will be in the script you used.

If you used tdload, then the names of the tables correspond to the name of the target table, except with a _ET or _UV suffix.

The location of the tables is in the same database as the target table, unless you specified otherwise.

 

--SteveF

brindamaiti 11 posts Joined 10/11
11 Apr 2012

Thank feinholz  for all your reply.

plentyfish 16 posts Joined 05/10
21 Jun 2016

Hello, is there a way I can identify tables in load pending state?

You must sign in to leave a comment.