Oracle 11g files housekeeping methods

January 3, 2014 by 2 Comments 

Since Oracle Database 11g, all traces, incident dumps and packages, the alert log, Health Monitor reports, core dumps, and more files are stored in the ADR, a file-based Automatic Diagnostic Repository for simplified database diagnostic data management. However housekeeping or purging of those files got not simplified. Unfortunately the new Oracle utility ADRCI can not purge all the files Oracle database generates in ADR. Thus, you should use the other OS tools to accomplish the same. Below I list common Oracle files that must be cleaned periodically with associated housekeeping methods I usually use on Linux servers.

Logs rotation

– Linux log rotate mechanism used
– alert.log, listener.log, backup logs and any other log files affected
– Files are purged and zipped for archiving purpose

Read more about Oracle database housekeeping using Unix logrotate mechanism.

Logs deletion

– Linux crontab utility with shell scripting used
– Oracle SYS Operations Auditing files (*.aud files) affected
– Files are deleted based on number of copies

Read more about housekeeping of Oracle database SYS audit files in adump directory using Unix purge script

ADR purge

– Linux crontab utility with Oracle ADRCI tool used
– ADR related incidents, dumps, reports and traces, xml files (ADRCI can not modify Text-formatted files) affected

In the next posts I’ll show how to accomplish all 3 steps of Oracle database 11g file housekeeping.

Read more about Oracle ADR files purge – automatic with retention policy vs manual with ADRCI and Unix scripting

Enjoyed this article? Please share it with others using the social site of your choice:

Comments

2 Responses to “Oracle 11g files housekeeping methods”
  1. Brett says:

    Quick question concerning using ADR for housekeeping.

    We have numerous database servers where csr is ran under root:

    root 20681 1 1 2016 ? 2-03:50:16 /o/oracle/grid/12.1/bin/crsd.bin

    So, the core dump files under diag/crs are owned by root. It seems the ADR util can’t delete those. Is ADR configured wrong? Is crsd.bin not supposed to be under root ownership, or ????

  2. Kirill Loifman says:

    As far as I know and see currently on 12c GI the trace files owned by root:oinstall. Thus can be managed by ADR tool.

    $ cd /diag/crs//crs/trace
    $ ls -l olsnodes*tr* |wc -l
    -rw-rw—- 1 root oinstall …

Add a Comment

We welcome thoughtful and constructive comments from readers.
If you want your own picture to show with your comment?
Go get a Globally Recognized Avatar!

DBMS Blog Updates : Subscribe RSS RSS: Subscribe to Articles · Subscribe to Comments Subscribe RSS Receive site updates via email