I found that the job history was full in OEM, causing the cpu to start
pegging on our server. I was wondering.. (and I have searched) if anyone
knows of a way to script the clearing of the job history log, or where
that info is even kept.
Once the Job History was cleared in OEM, the jobs started running again.
Previously, the jobs sat in "Starting" mode and just pegged out the cpu on
the server.
Any ideas?
Thanks for your help in advance.

Lisa A. Hale
Oracle/SQL DBA
EIS Database Technology


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________

This electronic message contains information from MeadWestvaco
Corporation or subsidiary companies, which may be confidential,
privileged or otherwise protected from disclosure. The
information is intended to be used solely by the recipient(s)
named. If you are not an intended recipient, be aware that
any review, disclosure, copying, distribution or use of this
transmission or its contents is prohibited. If you have
received this transmission in error, please notify MeadWestvaco
immediately at [Email address protected]
_______________________________________________________________________

Oracle LazyDBA home page