How Retention Policy works if we set RECOVERY WINDOW for N days

For an example If we are taking L0 backup on Sunday and L1 incremental backup over the week day from Monday to Saturday

If we set RECOVERY WINDOW OF 1 DAYS, it Means RMAN would not consider the incremental level backups which we took on weekdays as obsolete. The previous L0(Sunday) and L1 incremental backups will exist for a week until next L1 backup starts after next Sunday L0. 

The below diagram will explain in More detail

How to Disable Inactivity Log Out in Enterprise Manager Cloud Control 12c

/app/oracle/Middleware/oms/sysman/config

Add the following line after the last line in the above file

oracle.sysman.eml.maxInactiveTime=1440

Restart your OMS using below commands

$OMS_HOME/bin/emctl stop oms

$OMS_HOME/bin/emctl start oms

Registered database with RMAN

[oracle@testserver]$ . oraenv

ORACLE_SID = [+ASM1] ? PTEST

The /u01/app/oracle/product/10.2.0/db_1/bin/orabase binary does not exist

You can set ORACLE_BASE manually if it is required.

[oracle@testserver]$ rman target / catalog rcat@rmaN

Recovery Manager: Release 10.2.0.5.0 - Production on Mon Mar 23 09:08:35 2015

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: PTEST (DBID=1011970264)

recovery catalog database Password:

connected to recovery catalog database

RMAN> register database;

Once it is registered, login to RMAN database and run the below query to check the registered database.

select * from rcat.rc_database;

Shell Script to Purge Audit trail

#!/bin/bash
export ORATAB=/etc/oratab
export PATH=/usr/local/bin:/usr/sbin:$PATH
export SQLDIR=/home/oracle/scripts/Maintanence_script
export DATE=`date +%y%m%d`

ps -ef|grep -v grep|grep pmon|awk '{printf(substr($8,10)"\n")}' | while read DBSID
do
ORACLE_SID=$DBSID
export ORACLE_SID=$DBSID
echo Removing older trace file greater than 15 days ${ORACLE_SID}.....
find /app/oracle/admin/${ORACLE_SID}/adump/*.aud -type f -mtime +15 -exec rm -f {} \;
done
exit;