Archives of the TeradataForum
Message Posted: Thu, 25 Sep 2008 @ 18:58:22 GMT
Subj: | | Re: Error 3132: Access Logging step has failed |
|
From: | | Sanchez, Idrike |
| *** Failure 3132 Access Logging step has failed. The transaction was aborted | |
We get this often (twice this week).
Any query that would normally insert a row in the access log table that runs while the access log table has a lock will fail this way. In our
case it occurs during the daily accesslog rollup\purging. The delete of the previous days accesslog record is normally fast (See below for log
excerpt). However, any query unlucky enough to try to run during that second will fail this way. We have adjusted our routines to retry when
this error occurs.
Kiki Sanchez
Data Warehouse Group
Technology Division
Continental Airlines
('Current Time (Before AccessLog Clear): '||Current Time(0))
------------------------------------------------------------
Current Time (Before AccessLog Clear): 00:11:20+00:00
+---------+---------+---------+---------+---------+---------+---------+
*** Delete completed. xxx rows removed.
*** Total elapsed time was 1 second.
+---------+---------+---------+---------+---------+---------+---------+
*** Query completed. One row found. One column returned.
*** Total elapsed time was 1 second.
('Current Time (After AccessLog Clear): '||Current Time(0))
-----------------------------------------------------------
Current Time (After AccessLog Clear): 00:11:20+00:00
|