Path: news.easynews.com!easynews!news-out.cwix.com!newsfeed.cwix.com!feed2.news.rcn.net!rcn!feeder.qis.net!sn-xit-02!supernews.com!postnews1.google.com!not-for-mail
From: david.j.jackson@pickledbeans.com (David Jackson)
Newsgroups: comp.databases.oracle.server
Subject: Tier II/III troubleshooting tips?
Date: 2 Feb 2002 09:32:56 -0800
Organization: http://groups.google.com/
Lines: 14
Message-ID: <67b5acd7.0202020932.e64913e@posting.google.com>
NNTP-Posting-Host: 63.165.192.16
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1012671177 3538 127.0.0.1 (2 Feb 2002 17:32:57 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 2 Feb 2002 17:32:57 GMT
Xref: easynews comp.databases.oracle.server:133686
X-Received-Date: Sat, 02 Feb 2002 10:31:45 MST (news.easynews.com)

Good day --
I do a lot 2nd/3rd shift Unix and application support ( I generaly
have root access). It would be helpful to me if I had some trouble
shooting guildlines that could be used before paging YOU at 03:00.

In other words what can I do beyond checking that the "ora" processes
are running? "tnsping" is one that comes to mind also?
How about log files or checking database space problems, oracle backup
(failure/completion), status of oracle jobs?


Thanks for your advice.

David Jackson