Cleaning up the system – 11i

and R12
P UBLIS HE D ON   June 22, 2009
Here is the small post which describes the potential placed where log files and trace files
are present and can be cleaned up. This is requied when you want to free up space on the
system.

Cleaning up R12 instance:

Following are the locations in applmgr side which you can check and clean up. Be careful
while cleaning up the log files, because some might be needed for analysis or might
contan errors for some reproducible test case. So if you delete some log file which is
needed, you might have to redo that work. Usually its a good idea to leave the logs which
are 1-2 days old and delete the other older logs

Main location for logs and other not useful files on applmgr side:

Forms dump files : $INST_TOP/logs/ora/10.1.2/forms

Reports Cache : $INST_TOP/logs/ora/10.1.2/reports/cache

Apache logs : $INST_TOP/logs/ora/10.1.3/Apache

OPMN Logs : $INST_TOP/logs/ora/10.1.3/opmn

Its advisable not to remove any logs under $INST_TOP/logs/ora/10.1.3/j2ee directory

since these are very important logs and are required frequently for debugging.

Logs for service management : $INST_TOP/logs/appl/admin/log

Concurrent Manager logs : $INST_TOP/logs/appl/conc/log

Concurrent Manager out files : $INST_TOP/logs/appl/conc/out

Other then these directories if you have some patch downloaded at some location, it is
advisable to remove those patches once applied.

Main location for logs and other not useful files on oracle side:
Cleanup background_dump_dest, user_dump_dest and core_dump_dest directories on
database side. These locations usually have huge trace files.

Check the location of ORACLE_HOME using du -sh command. Usually the size of
ORACLE_HOME should be aounr 3-4G. If size of ORACLE_HOME (other then
datafiles) is abnormally large like 7-8G or more then you need to investigate which
directory is consuming more space and accordingly clean up that directory if appropriate.

In some situation if it becomes impossible to clean up the space (because there are no
trace files to cleanup) and you desperately want the space to be available on the file
system, then you can connect to database as sysdba and try to reduce the size of temp
files using “alter database tempfile .. resize” comamnd. This will release some space and
prevent database from crashing in case file system is reaching 100% full.

Again if some patches are downloaded for application, make sure to remove the patches
zip files once they are applied.

Some times we upgrade the database to a major release, like from 9i to 10g or from 10g
to 11g. In that case its advicable to remove the old ORACLE_HOME. This will not only
save space but also will avoid confusion.

Cleaning up 11i instance:

Main location for logs and other not useful files on applmgr side:

Logs for Concurrent manager, forms and

reports: $COMMON_TOP/admin/log/$CONTEXT_NAME

Out files for Concurrent

managers: $COMMON_TOP/admin/out/$CONTEXT_NAME

Apache Log files: $IAS_ORACLE_HOME/Apache/Apache/logs

Jserv Log files: $IAS_ORACLE_HOME/Apache/Jserv/logs

There are some log files in $APPL_TOP/admin/$TWO_TASK/log and $AD_TOP/log,

but its advisable not to delete these logs as they are very important for debugging.

Main location for logs and other not useful files on oracle side:
Cleanup background_dump_dest, user_dump_dest and core_dump_dest directories on
database side. These locations usually have huge trace files.