My Oracle Support Banner

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 JANUARY 29, 2022

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

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

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.