Perhaps I should clarify. I did take a look through the logs and pointed them to the event viewer items reporting the POST errors and the restart time along with the event ids. (Windows Server 2003) So I didn't mean to imply that I didn't look through the logs at all. Now I'm being asked to diagnose the problem it seems. Chris Taylor Sr. Oracle DBA Ingram Barge Company Nashville, TN 37205 Office: 615-517-3355 Cell: 615-354-4799 Email: chris.taylor@xxxxxxxxxxxxxxx ________________________________ From: Mercadante, Thomas F (LABOR) [mailto:Thomas.Mercadante@xxxxxxxxxxxxxxxxx] Sent: Tuesday, September 30, 2008 8:34 AM To: Taylor, Chris David; ORACLE-L Subject: RE: Server failures Chris, Why would you not want to take a cursory look around? It could be as simple as looking at the alert logs and saying "Oracle did not report any problems" and then kick it up to the SA's. I know I would do it. Tom ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, Chris David Sent: Tuesday, September 30, 2008 9:19 AM To: ORACLE-L Subject: Server failures So how many of you are responsible for examining your database servers for hardware/software faults when it crashes? Not the database, but the actual machine? We recently had a server crash that reported problems when it came back up. It has also saved a dumpfile to be examined and it reported problems during the POST routine. Now I get this email from my DBA manager: (paraphrased) "Chris, John [pc/lan mgr] requested that we try to put our finger on what caused MachineA to failover on Saturday. I looked through the logs extensively today [uh huh] and couldn't find anything - can you look around too and see if you find anything?" -Bob" (Obviously names changed) Maybe I'm just in a bad mood this morning....grrrr Chris Taylor Sr. Oracle DBA Ingram Barge Company Nashville, TN 37205 Office: 615-517-3355 Cell: 615-354-4799 Email: chris.taylor@xxxxxxxxxxxxxxx