How to use OEM to run a script against many targets and send result by emai

Question

Is there a way to use OEM to query the RMAN backup against many targets (databases) and have all the results send to you by a single email?
The script is :
SELECT a.instance_name, b.session_key, b.session_recid, b.session_stamp, b.command_id,
b.status, b.start_time, b.time_taken_display, b.input_type,
b.output_device_type, b.input_bytes_display, b.output_bytes_display,
b.output_bytes_per_sec_display
FROM
v$instance a, V$RMAN_BACKUP_JOB_DETAILS b WHERE ( b.start_time > (SYSDATE - 30) ) order
by b.start_time
Thanks.

Answer 1

Are you using a RMAN catalog? If not, you can used UDM's (this will be messy w/o a RMAN catalog) for what you want to do.
What I started out doing was....
You can create a UDM and push that UDM out to the targets you want. The problem with UDM's, is you can only pull 1 or 2values. I started down this same path and wrote a sql to concatenate the data into one value, such as
SELECT '|'||input_type||'|'||status||'|'||start_time||'|'||end_time||'|'||ROUND(elapsed_seconds,2)||'|'||time_taken_display||'|'
FROM v$rman_backup_job_details
WHERE (INPUT_TYPE, START_TIME)
IN
( SELECT input_type, MAX(START_TIME)
FROM v$rman_backup_job_details
GROUP BY INPUT_TYPE
AND INPUT_TYPE = 'DB FULL';
Do not put any warning/critical thresholds in the UDM and just let OEM Agent gather the data and pull it back into the SYSMAN repository.
You can then look at this view, SYSMAN. MGMT$METRIC_DETAILS to find the correct SQL to pull out the data you need. This view is made up of a 4 way union between 4 sql's. Once you find the SQL you need, then you can pull this information out and into a custom table of your own.
Once you have data into another table, you will then have to extract the concatenated string out, parse it out and report on it. This is where I stopped and said there has to be a better way.
I then thought about it and the RMAN catalog has all this, assuming you are using a RMAN Catalog.
I wrote a piece of dynamic sql to loop through the rman catalog to pull this out into a historical table and store the data. Then I can report on it from there. If you have a RMAN catalog, this works much better.
I also use UDM's to use OEM as a data extract tool to pull the number of archivelogs and bytes my databases create on an hourly basis. I pull 2 values, bytes and # of logs. So this works well with UDM's, don't have to concatenate a bunch of values and then parse it back out again.
I push this UDM to all databases, and have it run hourly. Then daily, I extract this information into a custom table and then use analytic functions to determine how much space is needed on the db servers for archivelogs for a 24 hour time frame. This helps with sizing our log destinations and gives us legitimate reports for Storage teams.
I can also build reports on how many archive logs are generated on a daily, weekly, monthly basis per database. Good for analysis and charge back methods.