| HIGH no of LOCKS exclusive in tables for UPDATE Statement [message #335136] |
Mon, 21 July 2008 03:23  |
udara
Messages: 9
Registered: July 2008
Location: COLOMBO
|
Junior Member |
|
|
in our production system getting slowness for transation due to exclusive records exist in system. i have kill the process for taking back to normal the system but couldnt recoved.
1. why such exclusive lock hapeen
2. any technique in oracle to avoid such situation
Thanks
|
|
|
|
|
|
| Re: HIGH no of LOCKS exclusive in tables for UPDATE Statement [message #338053 is a reply to message #335143] |
Sat, 02 August 2008 16:12  |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
small explanation...
1. why such exclusive lock hapeen?
To maintain the Data consistency & integrity in database.
2. Any technique in oracle to avoid such situation
If normalization of tables is done properly and code are designed properly we can avoid situation of dead lock. Most locking issues are application specifics. To resolve locking contention, one needs to free the resource by:
1. Asking the HOLDER to commit or rollback,
2. Killing the session which holds the lock,
SQL>ALTER SESSION KILL SESSION sid, serial#;
3. killing the shadow process from o/s.
4. By ROLLBACK FORCE or COMMIT FORCE in distributed transaction.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
