/dev/shm Filled Up With Files In Format JOXSHM_EXT_xxx_SID_xxx
(Doc ID 752899.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 14-Jun-2017
/dev/shm is being filled up with files in the format JOXSHM_EXT_???_SID_???? and eventually causing the DB to restart. Oracle is not automatically cleaning those files.
Please note that it is OS specific whether such segments are visible on a filesystem or not, and if so where they get placed. eg: On Solaris shm_open() internally creates a file in /tmp with the prefix .SHMD and less the leading "/" from the shm_open argument whereas on Linux it creates an entry in /dev/shm
Most probably the database has not been closed cleanly. i.e SHUTDOWN IMMEDIATE or SHUTDOWN ABORT is used
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document