Thanks for the question, Antonio.
Asked: July 13, 2025 - 10:59 am UTC
Last updated: August 01, 2025 - 4:00 am UTC
Version: 19.11
Viewed 100+ times
You Asked
I need help with the following problem. I have an Oracle database version 11g GI 19.26 DB 19.11. Stored on ASM disks, I was surprised by an ASM instance deactivation due to a disk monitoring process that shut down the instance. I deactivated the database and rebooted the server. After the server became available again, I verified that the ASM instance was active. I reactivated the database, which did not request recovery. I also opened a support ticket with Oracle. They asked me for a series of trace files along with alert.asm. After analysis, Oracle informed me that the reason for the instance deactivation was a data leak in the /dev/shm filesystem (the server is running Linux 8). The leak is news to me, and to my surprise, Oracle reported that it doesn't know the cause of the leak and doesn't have a monitoring script to evaluate the status of /dev/shm (the available space on the file system is 28GB free and 4GB occupied). Do you have any information about it?
Thank you for your attention.
and Connor said...
I'm a bit lost on "11g GI 19.26 DB 19.11." but anyway...
If you are *truly* using 11g, then check to see if there are files polluting /dev/shm for native compilation (plsql and java). This was a known issue a looonnngg time ago.
But ultimately, if you're leaking into /dev/shm, then its just a matter of time before the database instance is going to have a shared memory problem, so I can understand why an instance would occur to avoid anything worse happening.
I don't have any more information than that.