Skip to main content

Oracle Export Cleaner (Example Script)

Regular database exports can be monitored and cleaned regularly while keeping desired number of successful exports with this linux script. There are two files, one is config file that containing schema names and corresponding schema export path, the other one  is export cleaner script.

app.config file contents:

export cleaner script:

rm -f /tmp/cleaner.txt

today="$(date +%d%m%Y)"
echo "${today} Oracle Export Cleaner Log\n\n" >> /tmp/cleaner.txt
echo "———-${today} Export Logs———" >> /root/scripts/export_cleaner.log

cat /root/scripts/app.config | while read line

cd ${path}

if [ ! -f "${logname}" ]
echo "$schema $logname does not exists" >> /root/scripts/export_cleaner.log
echo "$schema $logname does not exists\n\n" >> /tmp/cleaner.txt
is_job_completed=$(tail -1 $logname |grep "successfully completed")
if [ "$is_job_completed" == "" ];
echo "$schema $logname unsuccessfull" >> /root/scripts/export_cleaner.log
echo "$schema $logname unsuccessfull\n\n" >> /tmp/cleaner.txt
echo "$schema $logname successfull" >> /root/scripts/export_cleaner.log
echo "$schema $logname successfull\n\n" >> /tmp/cleaner.txt
ls -t ${schema}_expdp*.log | awk 'NR>2' | xargs rm >> /root/scripts/export_cleaner.log
ls -t ${schema}_expdp*.dmp | awk 'NR>2' | xargs rm >> /root/scripts/export_cleaner.log
mailtext=$(cat /tmp/cleaner.txt)
echo -e $mailtext | mail -s "export cleaner"


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) Slave1 Node: (Centos 7.2) Slave2 Node: (Centos 7.2) Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/ Each Node: /etc/