Path: news.easynews.com!easynews!cyclone.swbell.net!cyclone-sf.pbi.net!216.218.192.242!news.he.net!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: bduff@condenast.co.uk (Bruce)
Newsgroups: comp.databases.oracle.server
Subject: statspack auto starting/stopping
Date: 4 Apr 2002 06:45:27 -0800
Organization: http://groups.google.com/
Lines: 13
Message-ID: <2df6b834.0204040645.3109ad95@posting.google.com>
NNTP-Posting-Host: 194.223.244.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1017931527 31477 127.0.0.1 (4 Apr 2002 14:45:27 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 4 Apr 2002 14:45:27 GMT
Xref: easynews comp.databases.oracle.server:142028
X-Received-Date: Thu, 04 Apr 2002 07:43:16 MST (news.easynews.com)

I have configured Statspack on my hp-ux 8.1.7.1.0 Oracle dbase. I'm
manually starting the collector on a daily basis using @spauto.sql.
This is fine to an extent. I now want to start it automatically using
a cron job and say run it between the peak operating hours of 9 and 5.
I should be able to do this.

However, I'm not sure about killing this job each night before the
backup at 9pm. We have a cold backup in place which obviously stops
it. I would ideally like to restart it the next day at 9am using cron.

Has anyone else out there done this? or do you have any other ideas? 

Thanks in advance...