Oracle 11g、12c大量错误登陆尝试带来的数据库异常

最新推荐文章于 2025-08-01 11:22:09 发布

czmmiao

最新推荐文章于 2025-08-01 11:22:09 发布

阅读量813

点赞数

CC 4.0 BY-SA版权

分类专栏： Oracle日常管理文章标签：数据库

本文链接：https://blog.youkuaiyun.com/czmmiao/article/details/84923547

Oracle日常管理专栏收录该内容

141 篇文章

订阅专栏

本文讨论了Oracle数据库早期版本中并发错误密码登录可能导致的数据库hang和性能问题。提出了利用event28401禁用特定特性，并强调了从管理层面解决问题的重要性。提供了在Oracle11g Release 11.1.0.7及更高版本中禁用该特性的具体步骤。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Information in this document applies to any platform.

CAUSE

A hang is possible in earlier versions of RDBMS as a result of an unpublished bug fixed in the following versions:

    12.1.0.1 (Base Release)
    11.2.0.2 (Server Patch Set)
    11.1.0.7 Patch 42 on Windows Platforms

Document 9776608.8 Bug 9776608 - Hang from concurrent login to same account with a wrong password

Even with this fix, numerous failed logins attempts can cause row cache lock waits and/or library cache lock waits. 

This was reported in:

Bug 11742803 LOTS OF 'LIBRARY CACHE LOCK' DURING USER LOGON AUTHENTICATION
This was closed as not a bug because there is an intentional wait when a login fails.

SOLUTION

In Oracle 11g Release 11.1.0.7,  the wait is disabled unconditionally
In Oracle 11g Release 2 and higher, in order to disable the wait between login failures the event 28401 needs to be explicitly enabled:
The event can be set as follows:

alter system set event ="28401 TRACE NAME CONTEXT FOREVER, LEVEL 1" scope=spfile;

To unset the event, set as follows:
SQL> Alter system set event= '28401 trace name context off' scope=spfile ;

小结：
关于大量的并发的错误密码连接数据库可能会导致数据库hang、或者引起性能问题，对数据库的影响非常大，近期就遇到过这样的一个案例。当然Oracle本身这个特性是非常好的，但是在当下确实会遇到一些问题，大家可以使用event 28401禁用这个特性。但是最好是要从管理上解决掉这样的问题，从安全层面做好管控。

参考至：http://blog.51cto.com/roidba/2061373

如有错误，欢迎指正

邮箱:czmcj@163.com