As the OID administrator you should monitor the provisioning log file from time to time to ensure the growth doesn’t hit 100% of your mount point space allocated. 80% mount point utilization is the standard threshold for any alert notification to be trigger out.

OID LDAP Log Management

You will be surprise to find that the growth of the OID provisioning was faster comparing to Apache log and I would advise you to check the space utilization from time to time. There’s method or way to housekeep the log without shutting down OID and I am going to share it on the next post. Right now I will share on the conservative way to housekeep the log in short time.

Shutdown OID and OC4J instance

$ $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J
$ $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OID

Housekeep OID Provisioning Log

$ cd $ORACLE_HOME/ldap/log
$ tar -cf ./ldap_log_backup.tar *.*
$ gzip ldap_log_backup.tar
 
$ cd $ORACLE_HOME/ldap/odi/log
$ tar -cf ./odi_log_backup.tar *.*
$ gzip odi_log_backup.tar

Startup OID and OC4J instance

$ $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J
$ $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID

HTTP Apache Log Management

Apache log shouldn’t grow much compares to OID log but it was recommended to housekeep from time to time. Follow the script as below to compress all the log files into a single tarball.

Shutdown HTTP instance

$ $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server

Housekeep HTTP Apache Log

$ cd $ORACLE_HOME/Apache/Apache/logs
$ tar -cf ./http_log_backup.tar *.*
$ gzip http_log_backup.tar

Startup HTTP instance

$ $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server