Logs to Check When Db Gets Completely Crashed [message #346547] |
Mon, 08 September 2008 17:23  |
rpp_rp
Messages: 2 Registered: September 2006
|
Junior Member |
|
|
Hi Everybody,
About two weeks back, our production Database was down and it took whole DBA Team around 4 hours to bring it up.
Can anyone suggests which are the logs we need to Check ( I am not pure DBA ..but, rather Mgmt Side and needs to provide the independent third party report on this ) ?
I know that
- Automatic Db Diagnostic Monitor ( ADDM) and STATPACK Report would provide useful info on the current state of the DB
- However, what I need to know is what happened at the time of the Db Breakdown and how we can prevent it further
based on Updates in Standard DB Admin Policies.
Any / ALL Inputs are highly Appreciated.
Thanks,
Regards,
- Ann
|
|
|
|
|
|
Re: Logs to Check When Db Gets Completely Crashed [message #346837 is a reply to message #346548] |
Tue, 09 September 2008 17:46   |
rpp_rp
Messages: 2 Registered: September 2006
|
Junior Member |
|
|
Thanks !
#1 SUN Solaris 4.0 , Oracle 10.2.0.2
#2 Its SAP CRM 4.0 on this Oracle DB
#3 DB was up and running well since 10 months untill this
Crash happened
#4 Ofcourse, DB Team must have some idea at least, what caused
this outage - Based upon the available trace and log files
I need to give independent assessment to Sr Management wit
hout any interaction with DBA Team ..They have already put
their defense at the Sr Management Hearing!!
#5 Well ..what the DBA Team were doing till 3hr 59Min is the
Good Q and that's where again I come in to picture to provide
the analytical report that what took so long to restore it -
Lack of Technical Competency was the Core Factor ( yes, it
is logical to say that such long time to restore the Prod
Db is not acceptable ) or the
Overall Poor DB Admin Policy ( or more precisely - the lack
of such Policy ) was also major contributor to it.
#6 My Task is at the very initial phase and as said I am on IT
Mgmnt Side and that's why I needed some specific trace files
and Log Files before I move to hands on level. Under this
back drop I don't have as of now any trace / log file.
I hope I provided enough details/ background of My Q.
Thanks for your input regarding trace file : The alert_SID.log ..
Any other log file , its' location - is highly appreciated.
Thanks,
- Ann
|
|
|
|
|
Re: Logs to Check When Db Gets Completely Crashed [message #346842 is a reply to message #346547] |
Tue, 09 September 2008 18:31  |
 |
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
Was there are hardware failure?
Was the database restored from backups?
If so, a 4 hour restoration process is not unreasonable; depending upon amount of data & whether tape drives were involved.
Every site should have documented & tested recovery procedures.
Does the type of failure you most recently experienced, correspond to any scenario in YOUR Recovery Procedures?
Each different failure scenario has a different Mean Time To Recover (MTTR).
In some cases MTTR should be measured in minutes.
In other cases MTTR could be measured in days.
More than likely there is more than enough blame to be shared by all involved.
From 1 perspective, you should be glad the database is back online.
Politics will decide whether 4 hours is reasonable or not.
Keep in mind, that nothing is impossible for the person who does NOT have to do it!
[Updated on: Tue, 09 September 2008 20:36] by Moderator Report message to a moderator
|
|
|