If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Rather than writing pl/sql, can't you just set up a threshold/notifcation (in grid - I know you use it!!) for when the file system/archive area hits x% full? If you still want to automatically kick the rman job, then set a response action up.
Either that or more space ;-)

Rather than writing pl/sql, can't you just set up a threshold/notifcation (in grid - I know you use it!!) for when the file system/archive area hits x% full? If you still want to automatically kick the rman job, then set a response action up.
Either that or more space ;-)

Bazza

Yea, Great suggestion. I'd love to do this. I'm just not real comfortable with the alerting system 10g OEM. We've been running it side by side with other systems and they have been 100% right on, while OEM has missed some really big problems 50% of the time. That's probably me, but I think it needs help.

I also have the addition of not wanting to fire this when an rman backup (datafile or archivelog) is already running.

There's probably a sql query that could tell me if the db is currently being backed up through rman.

I'm working along the lines of a cron job that counts the rows in v$archived_log where status = 'A' ('D' is deleted), and if rman isn't already running (grep rman or something) and I've got 20 archived logs or so, then kick off the rman process.

My take would be to add more disk space to the archive destination and point your archives to collect in there.

Yea, me too. Unfortunately I'm limited to the disks I have in that ASM diskgroup.

This happens once every 2 weeks. I think we can "swallow the frog" if I can flush logs before it can fill up the space. I'm also thinking about adding online redo logs so we have a little more lead time before the "archivelog dest full" alert is triggered and when the db finally halts transactions.