 |
 |
Archives of the TeradataForum
Message Posted: Fri, 29 Jul 2005 @ 08:15:48 GMT
| Subj: | | Re: Time out Waiting for Lock on UV Table. |
| |
| From: | | Victor Sokovin |
| | I was trying to mload a file to a table .The file had around 184 million records. | |
| | The session failed giving me the following error: | |
| | Timed out waiting for lock on <databasename>.<UV_tablename> ( eg. production.UV_fact_table_) | |
| | Can anyone suggest why the there was a session timeout for acqiuring the lock on the UV table , although there were no simultaneous
processes going on and hence no issue of any contention. | |
The system might have been busy with something else at that time and could not process this request within the maximum waiting time period.
Did this happen when you were trying to restart the ML process? If so, then it is possible that the previous ML job's lock on the UV table was
somehow still in place. Your DBA should be able to advise on such ghost locks and help you get rid of them.
If it is just a development database and you don't want to bother DBAs with this, then you might try the brute force approach: release ML lock,
drop all the temp tables, backup the target table, drop it and recreate from the backup. You might need to do something with the data as well if
you don't like the partial load from the failed ML session. This should normally give you a chance to repeat the load.
Regards,
Victor
| |
