Archives of the TeradataForum
Message Posted: Tue, 03 Jan 2006 @ 16:53:19 GMT
<-- Anonymously Posted: Tuesday, January 03, 2006 11:54 -->
Thank you all for the replies.
I raised and incident and it was promptly resolved.
The files were ALS files written by a BUG in the Alert Viewer software.
It turns out that one must explicitly select the <NO ACTION> option in the GUI interface by highlighting it and applying the changes; otherwise it will do the <WRITE TO LOG>.
It is not just sufficient to see and witness the <NO ACTION> in the GUI interface, but it has to be selected and applied in some cases (not all).
I started by removing all the ALS files and then inspecting the first ones that appeared to see which ALERTS were being recorded. Then it was a matter of selecting <NO ACTION> and applying the change for the offending entries.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|