My apologies. I did not mean to imply that OEM 12c is unstable or anything
like that.
However as a paranoid DBA I want to hedge my bets.
Thanks,
Chris
From: Lyall personal [mailto:lyallbarbour@xxxxxxxxxxxxxxx]
Sent: Sunday, April 12, 2015 3:27 PM
To: cgrabowy@xxxxxxxxx; 'Gus Spier'
Cc: 'oracle-l'
Subject: Re: Cron management...
EM 12c Cloud has a great High Availability setup. It doesn't have to be a
single point of failure. We are running our OMS on 2 nodes.
Doesn't really answer your original question. If, as DBAS, you are only using
Cron for DBA stuff, Cloud Control is an option. It does so much ore then Cron,
but if you focus it as a place for your RMAN backups, and monitoring, it's
great.
Sent from my BlackBerry 10 smartphone.
From: Chris Grabowy
Sent: Sunday, April 12, 2015 3:10 PM
To: 'Gus Spier'
Reply To: cgrabowy@xxxxxxxxx <mailto:cgrabowy@xxxxxxxxx>
Cc: 'oracle-l'
Subject: RE: Cron management...
Hey Gus,
I did look at the job scheduling features in OEM 12c. But, IMHO, it does not
compare to Tidal but it is a possibility. You can specify RMAN commands in an
OEM job so that simplifies “backup scripts”, etc.
We have a couple of scripts scheduled in crontab that do the same thing as OEM.
One script will send an email if it can’t connect to the database. Another
script monitors the alert log via ADRCI. If we didn’t have those crontab
scripts then OEM would be a “single point of failure” in our database
monitoring efforts. These scripts come in handy when we do OEM maintenance,
etc. So we really can’t put those monitoring scripts in OEM’s job scheduler.
I hope all is good with you! Are you with the same client?
Thanks,
Chris
From: Gus Spier [mailto:gus.spier@xxxxxxxxx]
Sent: Sunday, April 12, 2015 2:50 PM
To: cgrabowy@xxxxxxxxx <mailto:cgrabowy@xxxxxxxxx>
Cc: oracle-l
Subject: Re: Cron management...
Chris, I haven't looked into it very deeply, but one of the things on my To-Do
list is investigate/implement job scheduling through the OEM/Grid Control.
Would that work in your application?
Regards,
Gus
On Sun, Apr 12, 2015 at 2:47 PM, Chris Grabowy <cgrabowy@xxxxxxxxx
<mailto:cgrabowy@xxxxxxxxx> > wrote:
Howdy.
We currently have about 30 Redhat Linux servers running Oracle 11.2
Recently for a short time the crontab entry for a production backup was
commented out.
Just last week one of the DBAs had "accidently" deleted all the backup scripts.
The scripts directory is NFS mounted so it impacted every server.
The Netbackup folks like to do maintenance during the day. Any Oracle backups
that may have been running abort. These days we get notice from the Netbackup
folks but it's kinda tricky to check 30 servers and determine if anything is
running. Or kick off 30+ archive log backup scripts across all the servers to
clean up the archive log directories before the Netbackup maintenance.
Managing crontabs, jobs and scripts across 30 servers just doesn't seem to be
working.
Our company uses a job scheduling app called Tidal. The manager of that app
demo'd the product to me and it seems like it can address many of our
headaches. In theory a single simple interface to manage all the jobs
scheduled across all the database servers.
However one of the issues identified by the Linux admin is that the Tidal agent
needs root access so he is reluctant to install the Tidal agent anywhere but a
couple of designated Tidal servers.
I am wondering if other sites have stopped using crontab? If so then what did
you replace it with?
Anyway, I am open to any thoughts, suggestions, etc.
Thanks,
Chris Grabowy
--
//www.freelists.org/webpage/oracle-l
