ORA-00018: maximum number of sessions exceeded
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博客 ” ，链接：https://blog.itpub.net/20500445/viewspace-708594/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
最新文章
- EXP-00091: Exporting questionable statistics
- How to re-install JVM
- How to do oracle database character set migration
- Get the below error after duplicating database
- How to do the batch job (disable/enable constraint)
- ORA-01940: cannot drop a user that is currently connected
- How to get the TOP SQL
- Change the max extents of table
- Fix undo tablespace issue Errors
- Identify tablespace fragmentation
