Bug 7715339: a logon Failure triggers 'row cache lock' wait, 7715339row

Bug 7715339: a logon Failure triggers 'row cache lock' wait, 7715339row

Bug 7715339-Logon failures causes "row cache lock" waits-Allow disable of logon delay
(Document ID 7715339.8) to the bottom
Modification time: 2012-7-26 type: PATCH
For this document rating, email the link to this document to open the document printable page in a new window

Bug 7715339 Logon failures causes "row cache lock" waits-Allow disable of logon delay

This note gives a brief overview of bug 7715339.
The content was last updated on: 19-JUN-2012
Click here for details of each of the sections below.
Affects:

Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions> = 11.1
Versions confirmed as being affected
11.1.0.7
Platforms affected Generic (all/most platforms affected)
Fixed:

This issue is fixed in
11.2.0.1 (Base Release)
Symptoms:

Related:

Performance Affected (General)
Waits for "row cache lock"
Security (Authentication/Privileges/Auditing)
Description

In 11g there is an intentional delay between allowing failed logon
Attempts to retry. For some specific application types this can cause
A problem as the row cache entry is locked for the duration of
Delay. This can lead to excessive row cache lock waits for DC_USERS
For specific users/schemas.
 
This "fix" allows the logon delay to be disabled in 11.2.0.1 onwards
By setting event 28401 in the init. ora.
Eg:
Event = "28401 trace name context forever, level 1" # disable logon delay. ----- This event disables logon latency, a false state
This "event" will disable the logon sleep delay system-wide,
Ie. it will affect all user accounts, system-wide, and so shocould be used
With extreme caution.
 
Example scenario:
A mix of correct and incorrect logon attempts occur for user X
On each successive failed login attempt the failed logon count
Is incremented for user X.
 
Without this fix (without the event set ):
After 3 successive failures a sleep delay is introduced starting
At 3 seconds and extending to 10 seconds max. During each delay
The user X row cache lock is held in exclusive mode preventing
Any concurrent logon attempt as user X (and preventing any
Other operation which wowould need the row cache lock for user X ).
 
With the fix (with the event set ):
There is no sleep delay.
 
In either scenario the configured logon profile rules are still
Applied (eg: The profile option FAILED_LOGIN_ATTEMPTS is still
Honored and so if the account becomes locked due to exceeeding
This FAILED_LOGIN_ATTEMPTS then further attempts
Log in will then correctly fail immediately with no delay ).
 
Note:
One off fixes for this issue for 11.1.0.7 do not need an event set-
Interim patches for 11.1 disable the delay unconditionally.
 
Work Around:
Ensure the correct password is used-especially for connection
Intensive logons
 
Getting a Fix
Use one of the "Fixed" versions listed above
(For Patch Sets/bundles use the latest version available
Contents are cumulative-the "Fixed" version listed above is
The first version where the fix is wrongly DED)
Or
You can check for existing interim patches here: Patch: 7715339
 
Please note: The above is a summary description only. actual symptoms can vary. matching to any symptoms here does not confirm that you are encountering this problem. for questions about this bug please consult Oracle Support.
References

Bugs: 7715339 (This link will only work for PUBLISHED bugs)
Note: 245840.1 Information on the sections in this article

Learn this from DBA development without basic knowledge

The learning route recommended by itpub's VAGE is for reference only:
Preliminary stage: you can start with the OCP teaching material, as well as the Administrator's Guide, Concepts, Performance Tuning Guide, Backup and Recovery Advanced User's Guide, Backup and Recovery Basics in the document. In particular, the Administrator's Guide, Concepts, and Performance Tuning Guide should be read in detail. Multiple operations and multiple experiments.
Intermediate stage: continuous operations, and reading various articles on metalink. It is very important to go to the Oracle official website to find the OCM examination syllabus and try to break through the syllabus one by one. In other words, if you do not take the OCM examination, you should choose another one. For more information, see 9i & 10g programming art, cost-based oracle optimization rules, big talk cluster rac, and oracle rac diaries.
Advanced: continue reading (optimization, features, integration) to learn in depth. You can take the following content as the topic and study it one by one:
1. Storage Format: Data File Format and data storage format
2. Sharing pool: resolution process and principle. Sharing is related to Latch, Lock, Pin, Row cache lock, and related wait events. And the Shared Pool memory allocation mechanism.
3. Buffer Cache part: Logical read, physical read process and principle, related Latch, Pin, and related waiting events.
4. Redo: Redo generation process, related Latch, and wait events.
5. Undo: the principle of Undo space usage rules, submission and rollback
6. Principles of backup and recovery mechanisms, learn to use BBED
7. ASM
8. RAC
See DSI. There is also a new Liwes book Oracle Core.

How can I identify oracle 11G training?

First, check whether the organization is on the official WDP authorization page of Oracle. Then, check whether the uniform price of Oracle is higher than the uniform price. If the price is higher than the uniform price, it indicates that there is suspicion of charges; the other is to check whether the course schedule is in one breath. If there is a lecture class or something, it means that it may force you to charge twice later. Then, it is to check the qualifications of equipment and lecturers, in fact, it is also good to judge through the Oracle training audition course. For example, I would like to hear it whenever I have time. Although I have never reported any name, I think it is good. It is also a good choice to visit training institutions on the spot. what others say is false. You need to listen more and then make judgments.