More columns can be added to the query with good information. To view all the information that can called from the “dbc.logonoff” view: “help view dbc.logonoff<\/em>“<\/p>\n![](\"http:\/\/www.theSQLReport.com\/wp-content\/uploads\/2016\/12\/LogonEvent.jpg\")
<\/a><\/p>\n
In Teradata, there is a way to view the reason that a username is not authenticating.\u00a0 Teradata is good about collecting information at the time of authentication.\u00a0 It can be verified, when an error like “Error: Logon failed!” occurs, if it is something like a bad password, or if the account is locked.<\/p>\n
select\r\n\u00a0 cast(cast(logdate as format 'YYYY-MM-DD') as varchar(100))\r\n\u00a0 ,cast(logtime as varchar(100))\r\n\u00a0 ,username\r\n\u00a0 ,cast(cast(logondate as format 'YYYY-MM-DD') as varchar(100))\r\n\u00a0 ,cast(logontime as varchar(100))\r\n\u00a0 ,ClientIpAddress\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0 ,ClientProgramName\r\n\u00a0 ,ClientSystemUserId\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0 ,event\r\n\u00a0 from dbc.logonoff\r\n\u00a0 where logdate >= date '2016-12-01'\r\n\u00a0 and event not in ('Logon','Logoff')\r\n\u00a0 order by 1 desc, 2 desc<\/pre>\n<\/a><\/p>\nMore columns can be added to the query with good information. To view all the information that can called from the “dbc.logonoff” view: “help view dbc.logonoff<\/em>“<\/p>\n