Automate OEM partition Maintenance

Question

Hi All,
I was wondering if anyone out there had already automated their routine partition maintenance on the OEM repository and if there was any recommended standard, automated procedure for this from Oracle or the OEM community at large.
I've put something sloppy together that works, but would like to see what you all have out there for UNIX platforms.
Below is what I'm doing currently. I know this is not the best scripting, but I put it together quickly and as of yet have not gotten around to attempting to handle errors or recompile down the entire submit_em_dbms_jobs pkg chain which gets invalidated after the part_maint call.
Let me know if anyone out there knows of a recommended automated procedure for this, or if anyone wants to work on creating a nice one that could be shared as a standard.
Thanks,
Tony
Oracle Cron Entry
# Perform OEM Partition Maintenance, 11PM Fridays
00 23 * * 5 /groups/tapestry/devsupport/se/DBA_Utilities/dba/oem_maint.ksh 2>/dev/null
oem_maint.ksh----------------------------------------------------------------------------------------------------
#!/bin/ksh
# OEM Maintenance - stops OEM, runs partition maint, starts OEM
PATH=.:/usr/sbin:/usr/bin:/sbin
ORA_HOME=/opt/oracle/product/EM102020
export ORA_HOME
export PATH
# OEM Must be stopped to run partition maintenance
$ORA_HOME/oms10g/bin/emctl stop oms
$ORA_HOME/oms10g/bin/emctl stop em
$ORA_HOME/oms10g/opmn/bin/opmnctl stopall
ORAENV_ASK=NO
export ORAENV_ASK
ORACLE_SID=emrep
. oraenv
unset TWO_TASK
/usr/bin/read SYSMANPWD < /homes/oracle/.sysman_pwd
#Connect as sysman and run partition maintenance, then submit jobs
echo "connect sysman/$SYSMANPWD;
spool /tmp/oemmaint.log;
PROMPT Running emd_maintenance.partition_maintenance;
exec emd_maintenance.partition_maintenance;
PROMPT First Run will Fail due to part maint
exec emd_maintenance.submit_em_dbms_jobs;
PROMPT Second Run should succeed
exec emd_maintenance.submit_em_dbms_jobs;
spool off
" | sqlplus -s /nolog
#Email spooled sqlplus session for SAs to check results
cat /tmp/oemmaint.log | mailx -s "OEM Partition Maintenance Results" [email protected]
#Remove the spool file
/usr/bin/rm /tmp/oemmaint.log
#Restart OEM
$ORA_HOME/oms10g/opmn/bin/opmnctl startall
-------------------------------------------------------------------------------------------------------------------------

Answer 1

Thanks for the tips Ugonic,
That's a good point about the log removal, as it overwrites and is very small it's better to just leave the log.
As for the password read from file, it's sloppy but we are a dev shop and have other scripts designed the same way so I'm going to keep the auto-login for now so I can run this via cron in the middle of the night (it takes 30-60 mins to complete). That way we have OEM up when everyone is in the office.
Bazzza -
Our Repository grows like crazy, if I don't run this we get up to 20GB in a matter of months. And the really pathetic part about it is that if I run it too late, everything is loaded at the end of the datafile and I can't shrink it down without playing all sorts of games (like the last time when you all helped me with he sysman schema exp/imp). Really hope this is fixed in the next releases ;)
Thanks for the feedback guys,
Tony