Archives of the TeradataForum

Message Posted: Wed, 02 Feb 2011 @ 09:53:30 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Wednesday, February 2, 2011 04:06 -->

Diffrence between dbc.accesslog and dbc.logonoff

Case of dbc.accesslog

     [2631: Transaction ABORTed due to Deadlock.] has occured, and it did not retry.
     [Select xx from table] was executed when [Delete from dbc.accesslog] was in a session.
     The message 2631 was returned and [Select ...] job was abended.

When RetryAccLogDeadlock on DBSCONTROL/Internal is set TRUE, 2631 should be returned, then Teradata is supposed to retry the query.

     The [Select...] job is connecting to Teradata using SAS Access to Teradata (ANSI mode).
     (Version SAS 9.1 Foundation)
     (Teradata Version V2R.06.02)

Case of dbc.logonoff

     [Logon to Teradata] was executed when [Delete from dbc.logonoff] was in a session.

The message 2631 was NOT returned.

[Logon to Teradata] was just waiting until [Delete from dbc.logonoff] was finished.

     The [Logon to Teradata] job is connecting to Teradata using SAS Access to Teradata (ANSI mode).
     (Version SAS 9.1 Foundation)
     (Teradata Version V2R.06.02)

My question is, why is there a diffrence between dbc.accesslog and dbc.logonoff?

	<Prev	Next>		<<First	<Prev	Next>	Last>>