LIBRARY CACHE LOCKS DUE TO INVALID LOGIN ATTEMPTS (Doc ID 1309738.1)
Bug 12990384: HIGH LIBRARY CACHE LOCK IN 11.2.0.2.0
Bug 12990384: HIGH LIBRARY CACHE LOCK IN 11.2.0.2.0
There was new SLEEP () code introduced which will get activated after Failed Login Attempts exceeds 3 and not the threshold setting set for the FAILED_LOGIN_ATTEMPTS parameter value.
Please set the below event in your init.ora file and restart the database.
EVENT="28401 TRACE NAME CONTEXT FOREVER, LEVEL 1"
After setting the above event, you will not be observing the "Library Cache Lock" issue during login with wrong password.
This event was introduced from 11gR2 release onwards to allow customer to turn off the "sleep" after three failed logon attempts, by adding the event to their instance initialization file.
Please set the below event in your init.ora file and restart the database.
EVENT="28401 TRACE NAME CONTEXT FOREVER, LEVEL 1"
After setting the above event, you will not be observing the "Library Cache Lock" issue during login with wrong password.
This event was introduced from 11gR2 release onwards to allow customer to turn off the "sleep" after three failed logon attempts, by adding the event to their instance initialization file.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/20500445/viewspace-708594/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/20500445/viewspace-708594/
扫一扫
2714
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
