iSelfSchooling.com  Since 1999     References  |  Search more  | Oracle Syntax  | Free Online Oracle Problem Solver

    .Home      .Subscribe     .Login      .Start Learning      .Certification      .Cancel      .Password Reminder      .Password Change     .Sign out

 

. Online Accounting        .Copyright & User Agreement   |
    .Vision      .Biography     .Acknowledgement

.Contact Us      .Comments/Suggestions       .Email2aFriend    |

 

Online Oracle Training for beginners and advanced - The most comprehensive Oracle tutorial

The authors do not guarantee or take any responsibility for the accuracy, or completeness of the information.

DBAs - OEM

 

Lesson 01 | Lesson 02 | Lesson 03 | Lesson 04 | Lesson 05 | Lesson 06 | Lesson 07 | Lesson 08 | Lesson 09 | Lesson 10 | Lesson 11 | Lesson 12 | Lesson 13 | Lesson 14 | Lesson 15 | Lesson 16 |

 

Lesson 13

"Interesting - I use a Mac to help me design the next Cray." - Seymoure Cray (1925-1996)

 

Read first then play the video:

   OEM-VIDEO -Detecting a session lock problem

   

Detecting a session lock problem using OEM

 

Introduction

As a DBA, you are responsible for detecting a session lock problem. The following is a summary of your task:

Covers:

Using the “Lock Monitor” tool

Selecting a target database

Identifying the Lock Session

Obtaining locked users

Obtaining a user’s lock mode

Resolving lock contentions

 

Hands-on
In this exercise you will learn how to identify the session lock problems from the "Lock Monitor" tool using the Oracle Enterprise Management tool (OEM).

Expand the databases.

Select the DBS4RMAN database.

Go to the "Diagnostics Pack" tools and click on the "Lock Monitor" icon.

In the "Lock Manager" window, notice that the "ISELF" user is in the exclusive mode and that it’s holding the SYSTEM user. Although the SYSTEM user requested an exclusive lock, it was not given to it.

Let's go to the ISELF session that was holding the SYSTEM user. Then you commit the transaction.

Go back to the "Lock Manager" window, the lock disappears after the window is refreshed.

Now, the SYSTEM user has an exclusive lock with no holding request
locks. Now, you have a happy customer.