Last updated on JULY 05, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms