Archives of the TeradataForum
Message Posted: Fri, 26 Sep 2003 @ 17:51:59 GMT
we have a view that selects from 3 tables, and I believe that when a select is issued on the view, teradata places/tries to place a READ (Which is the default) lock on the underlying tables.
There is a nearly continuous data insertion going on on one of the table (which the view depends on), and by default teradat places a write lock on the table, disallowing any read lock request. I checked the tearadata manual which essentially says that write lock on any row makes the table unreadable. Is it entirely true??
In our case, the read request is timing out due to the write lock on the table. Can we take an access lock on the table for read to solve this issue in the following way: DOes the access lock reads data from the locked rows??
Thanks in advance.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|