Initial logins to DB2 through vas pam.d modules fail or QAS enabled AD account can log in successfully to the Unix machine and authenticate to DB2. After a period of time the account can no longer to authenticate to DB2. The following error may be seen:
20120713 06:00:04:943 W125E- ODBC error: "[IBM][CLI Driver] SQL30082N Security processing failed with reason "19" ("USERID DISABLED or RESTRICTED"). SQLSTATE=08001"
Running a /opt/quest/bin/vastool flush or logging out / logging back in resolves the issue temporarily.
Product Defect# 25778
* vasd: Incremental updates would fail to update the shadow attributes of a user
in the vasd memory cache. This leads to users failing to log in especially on
solaris through DB2. Fixed if they log in through ssh or similiar.
WORKAROUND:
Run the following command:
/opt/quest/bin/vastool nssdiag nssflush
This is an efficent way to reload all the required data and correct the issue temporarily.
STATUS:
Fixed in 4.0.3.80 and up
RESOLUTION:
Upgrade to QAS 4.0.3 Maintenance Release
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center