Archives of the TeradataForum
Message Posted: Tue, 27 Apr 2010 @ 13:57:36 GMT
Varun Kore wrote:
This looks like it may be a timing or locking issue.
SQL Assistant (or ODBC really) did recognize the expired password and prompt for a new one.
It looks like your BTEQ session tried to logon before the dictionary updates had been applied so it failed because the password was incorrect.
The BTEQ session may have delayed the completion of the ODBC logon (dictionary locks - when it was trying to change the password) If the logon timed out it would report the last error message it received, which was the original password expired error. (ODBC originally displayed the dialog that asks for a new password when it received this error)
The good news is that this shows that (using your version of ODBC) SQL Assistant did prompt for a new password when the old one had expired. (That was the original problem reported in this thread.)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|