Monday, September 9, 2019

/tmp space not recovered after deleting files

My Environment:
DB - 12.1.0.1
APPS - R12.1.3
OS - IBM AIX 6.1

Normally conc.requests will access the temporary folder during concurrent process. If there is no space available (100% filled) in temporary location then all the requests will fail and the issue will be clearly addressed in the log file like no space available in tmp location. Normally it would be /usr/tmp, sometimes /var/tmp



In general deleting the files under temporary location will clear some space, but sometimes it wont happen. Even after you deleted the files, space will not be recovered and it will be still 100% filled. Reason for such situation is that the files are deleted but the process that access that file is still running and hence the space is logically occupied by this process.  Now killing the process is the only safer way and a quick way to fix the issue.

The best way is to use lsof command, get the pid of the process, do a small check and then kill the process using the pid you identified after you decided it is safe to kill. Now the space occupied by that particular process will be released.

Follow the below steps to achieve this.

Install the lsof rpm using the below command

rpm -Uvh <*.rpm>



Once the lsof rpm package is installed, use lsof command to find the details as follows 

/opt/freeware/sbin/lsof | grep /var/tmp 

Output of the above command may show some output like below: 
httpd 30027 oracle 57u REG 104,7 24803361 40 /var/tmp/filemQMbGZ.TMP (deleted) httpd 30033 oracle 75u REG 104,7 773833 44 /var/tmp/file7s8VAe.TMP (deleted) 
And you need to check which process is using the file. 
ps-ef|grep 30027 and than kill them from OS level 


httpd 30962 oracle 71u REG 104,7 72391 88 /var/tmp/filewzh7U1.TMP (deleted) 

kill -9 30027

Once the process is killed at OS level, the space will be freed, as a result conc.req will run normally.



****************************நன்றி****************************





No comments:

Post a Comment

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...