Link
Some time ago I googled great article by Gavin Soorma (
http://gavinsoorma.com/2010/09/purging-trace-and-dump-files-with-11g-adrci). It emphasizes the existence of policies build for information in
diagnostics_dest location.
Example usage
#!/bin/bash
## The script sets trace/diagnostics policies for test environments
SHORT_POLICY="SHORTP_POLICY\=308" #in h (14 days)
LONG_POLICY="LONGP_POLICY\=2400" #in h (100 days)
if [ ! $ORACLE_BASE ]; then
#echo "no ORACLE_BASE defined\n"
#exit
oratab='/etc/oratab'
os=`uname -s`
if [ $os = 'SunOS' ]; then
oratab='/var/opt/oracle/oratab'
fi
## or rather read only interesting lines
readarray -t -u $oratab oratab_entries
for entry in oratab_entries;
do
if [ ${entry:0:1}!='#' ]; then
## set sid
export ORACLE_SID=${entry%%:*}
## get the diag_dest
diag_dest=`sqlplus -S / as sysdba <<-CMD1
set feed off head off
select value from v$parameter where name='diagnostic_dest';
CMD1`
if [ $diag_dest ]; then
break;
fi
fi
done;
else
diag_dest="$ORACLE_BASE/diag"
fi
set -x
echo $diag_dest
cd $diag_dest
for h in `adrci exec="show homes" | grep -v "ADR Homes:"`;
do
adrci exec="set home $h; set control \($SHORT_POLICY,$LONG_POLICY\)"
done;