Shulou(Shulou.com)06/01 Report--

The password of the application (JDBC) has expired or changed, and the application is still connected with the old password. Due to 11g password error delay verification, resulting in library cache lock.

At the beginning of the check, you can see that the library cache lock is all JDBC applications, and the sql id is empty (that is, it hasn't started running sql yet).

Check the ash and find that the only sql id for the application is b84cknyvnyq25, which is the update user$ table. This makes it easy to relate to the user's authentication when logging in.

11g he has a password error delayed verification, and when the application is connected with the wrong password, it will continue to loop CPU, accompanied by library cache lock.

You can set event 28401 to disable this feature.

At present, it is normal after the revision.

Specific modification process:

SQL > show parameter event

NAME TYPE VALUE

-

Event string

Xml_db_events string enable

SQL > alter system set event='28401 trace name context forever,level 1' scope=spfile

System altered.

SQL > shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL > startup

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.