ganesh parab

• Aug 17th, 2005

 

By increasing memory to process simutanous access.

pandish

 Profile Answers by pandish Questions by pandish

• Apr 30th, 2006

 

it may be one of the solution. You gotta check the alert logs & see exactly what it the reason for hanging the database.

Ritesh Singh

• Jul 7th, 2006

 

If the user is complaining the hang problem ..then the experience of a dba reflects the work style that he is going to perform and basically as the rule suggest first try to connect to the database itself and fire some query to check whethere you are allowed to connect or not if you are connected then check for any locked_objects by checking v$locked_object and dba_waiters and dba_blockers.then you have to eliminate the things which are working properly and targetting yourself to the weaker place and then check at os level that which process is consuming the most of the time and then analyze the problem if the problem relates to a single user process then check what that user is doing by checking the sql statement he is firing.than so on

Chiranjeevi Manne

• Mar 30th, 2007

 

1. Check whether the execution plan of various SQL statements have been changed which may happen due to Bulk inserts and updates.
2. Try to gather statistics on regular basis.
3. Check the server side resources using top, vmstat, iostat, sar utilities.
4. Check the storage side
5. Check the network side

singh.neerajin

 Profile Answers by singh.neerajin 

• May 27th, 2008

 

If problem is pertaining to database & a user dont have acess to database level . One can check the process ( taking long time ) through the enterprise manager.

Kunal Mishra

• Oct 10th, 2011

 

First check the Alert log file if any error related to hang issue such. Then I would like to suggest one important step, that is please check archive log destination whether it has enough space, some times when archive log destination got 100% full the database will be hanged and no one can connect to the database apart from dba.

Kunal Mishra

• Oct 10th, 2011

 

Please check archive log destination has enough space, 100% full archivelog destination makes database hanged.

prakash

• Sep 22nd, 2014

 

Check session information and wait events