| ERROR: ORA-00018: maximum number of sessions exceeded |
SID USERNAME EVENT PROGRAM BLOCKING_SESSION ---------- ------------------------------ ---------------------------------------- -----------------------------------------------------------1002 OPGCEP1 library cache lock JDBC Thin Client 576 1003 OPGCEP1 library cache lock JDBC Thin Client 576 1004 OPGCEP1 library cache lock JDBC Thin Client 576 1005 SQL*Net message from client JDBC Thin Client 576 1006 library cache lock JDBC Thin Client 576 |
| Dear Customer, 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. Best Regards, Tracy Li (李秀文) Oracle Global Software Support |
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/29302187/viewspace-2093605/ ,如需转载,请注明出处,否则将追究法律责任。