When the Oracle Database Listener is started, the system prompts no space left on device.

 

From: http://hi.baidu.com/benmaoer/blog/item/7a5bcbefbf03213aadafd569.html

 

One day, after the machine was restarted due to power failure and insufficient UPS power supply, it was found that the listener could not be started and an error was prompted:

Tnslsnr for Linux: Version 10.2.0.1.0-Production
System parameter file is/home/Oracle/product/10.2.0/db_1/Network/admin/listener. ora
Log messages written to/home/Oracle/product/10.2.0/db_1/Network/log/listener. Log
Error listening on: (address = (Protocol = IPC) (partial = yes) (queuesize = 1 ))
No longer listening on: (description = (address = (Protocol = IPC) (Key = extproc1 )))
TNS-12549: TNS: operating system resource quota exceeded
TNS-12560: TNS: protocol adapter Error
TNS-00519: operating system resource quota exceeded
Linux error: 28: no space left on Device

Check disk space DF-H is still available

Strange, DF-I checked inodes usage at the same time. It was surprised that all inodes in the/var directory were exhausted.

[Oracle @ newadm log] $ DF-I
Filesystem inodes iused ifree iuse % mounted on
/Dev/sda3 131616 22831 108785 18%/
/Dev/sda1 26104 52 26052 1%/boot
/Dev/sda8 3384864 288966 3095898 9%/home
None 258627 1 258626 1%/dev/SHM
/Dev/sda6 131616 29 131587 1%/tmp
/Dev/sda5 393600 64042 329558 17%/usr
/Dev/sda7 131616 131615 1 100%/var

Contact SA to check the cause of inodes depletion in the/var directory, and delete the small files, the listener starts normally.

Later, I checked the eygle article and found that when the listener was started/Var/tmp/. OracleTwo temporary files are generated in the directory. Therefore, when inodes in the/var directory is exhausted, the listener cannot start.