 |
 |
Archives of the TeradataForum
Message Posted: Thu, 03 Feb 2011 @ 09:39:24 GMT
| Subj: | | Re: Diffrence between dbc.accesslog and dbc.logonoff |
| |
| From: | | Anomy Anom |
<-- Anonymously Posted: Thursday, February 2, 2011 21:35 -->
| | Regarding access logging, the following information appears in the 13.10 version of the Security Administration manual, Chapter 11:
"Auditing Access Logs." | |
My question is not about the definition of dbc.accesslog or dbc.logonoff, but When dbc.accesslog is locked by a query [ delete from
dbc.accesslog], a normal select query was abended with an erorr 2631. (2631: Transaction ABORTed due to Deadlock)
In the otherhand, when dbc.logonoff is locked by a query [ delete from dbc.logonoff], a logon action was waiting until the lock was
released.
Why is there a differrence across the two cases?
| |
