Stale Native Code Files Are Being Cached with File Names Such as: JOXSHM_EXT*, PESHM_EXT*, PESLD* or SHMDJOXSHM_EXT*

(Doc ID 1120143.1)

Last updated on APRIL 23, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
PL/SQL - Version 11.1.0.6 and later
Information in this document applies to any platform.
*** Checked for relevance on 23-Apr-2018 ***

Symptoms

Files with various name formats are being created but not removed which may lead to file storage issues or errors. File name formats are similar to the following:

JOXSHM_EXT_*_sid_name_*
and / or
PESHM_EXT_*_sid_name_*
and / or
PESLD_sid_name_*
and / or
.SHMDJOXSHM_EXT_*_sid_name_*
and / or
.SHMDPESHM_EXT_*_sid_name_*
and / or
.SHMDPESLD_sid_name_*


The location of these files depends on the operating system and how it implements shm_open() there. On platforms such as Linux and Solaris object based shared memory segments are used and the files are found in /dev/shm and /tmp respectively. On AIX, no files are seen at the file system level, however the shared memory segments can be seen using the 'ipcs -ar' command. On other platforms such as HP Itanium, file based shared memory segments are used, with the default location for HP being $ORACLE_HOME/dbs. 

When stale copies of these files are not correctly cleaned up this can impact the server's shared memory and paging space, requiring a server reboot to clear the memory.

Changes

This issue is seen with 11.1 or higher.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms