| Database Down [message #207716] |
Wed, 06 December 2006 13:52  |
Alps
Messages: 28
Registered: November 2006
Location: Toronto
|
Junior Member |
|
|
I have two question.
My database was down and I had to reboot it back. what are the few things I need to see first and analyze what went wrong in database so that it became slower and slower. Once database was shut down but still the uptime on unix was showing the same when database was slow. I dont know why the jptime on unix remained the same even after database was shut down.
Thanks
|
|
|
|
|
|
| Re: Database Down [message #209329 is a reply to message #207716] |
Thu, 14 December 2006 05:40  |
kudur_kv
Messages: 75
Registered: February 2005
|
Member |
|
|
Why dont you look at your alert log file. This should give you pretty much the exact reason why your database went down. Or it will give you the name of the trace file in which the errors are recorded.
[Updated on: Thu, 14 December 2006 05:40] Report message to a moderator |
|
|
|
| Re: Database Down [message #209917 is a reply to message #209329] |
Mon, 18 December 2006 08:38 |
Alps
Messages: 28
Registered: November 2006
Location: Toronto
|
Junior Member |
|
|
well there is nothing written in Oracle Trace file nor in Alert.log.
I dont know whats causing such probs.
|
|
|
|
| Re: Database Down [message #211376 is a reply to message #209917] |
Thu, 28 December 2006 04:41 |
kudur_kv
Messages: 75
Registered: February 2005
|
Member |
|
|
The uptime on a unix system shows how much time the system has been up.
The best measure of a DB's health is provided by the alert log files. if you are not able to find any supporting entry in the alert log, then there is only so much you can do to analyze the problems.
If your DB performance is slower, try to take a statspack report and analyze the SGA performance along with some of the wait events.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
