The problem we had with the application is that the database wrote to the alert log that a deadlock was detected , but the Oracle transaction was not terminated (essentially the application code is still waiting for the SQL command to complete, thus hanging the entire system). This caused the sysem to hung and had to be restarted .
Ideally speaking the dead lock should abort the session and roll back one of the transactions .
Pls advice as this is a critical one and we r struck with this issue !!!!!!!!!!!!!!!!!
SenExpert
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
usually, a deadlock will not cause the sysem to hung. If your problem is onyl a deadlock, Oracle will detect the deadlock and resolve it. you need to pay more attention on your application if it is designed properly.
you can get information from :
1: database alert log file.
2: when your application is running, you can check:
v$locked_object,v$session,
to help you find out what's happen in your database.
Business Accounts
Answer for Membership
by: adixitPosted on 2004-02-02 at 23:34:14ID: 10259073
There should also be a trace file generated for the session. Have a look there for additional information.
If it happens again you could try killing the session manually using the statement.
ALTER SYSTEM KILL SESSION '<sid>,<serial#>'
Get sid and serial# from v$session.
You may find that Oracle was performing a log of rollback and that is what took the time. You should check the statistics for the session to see if there is any changes. I sometimes get people saying there session has hung, when in reality it is working behind the scenes doing large amounts of rollback and cleaning up etc.