My Oracle Support Banner

High Memory Allocations of type KGNFS in Shared Pool (Doc ID 1309337.1)

Last updated on SEPTEMBER 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
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
Information in this document applies to any platform.


You may see high memory allocations in the shared pool of type
"kgnfs rserver", "kgnfs local" and "kgnfs path".

If these allocations grow large enough they may cause ORA-04031 error.

- ORA-04031: unable to allocate 592 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","kgnfs local")
- ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [4031], [], [], [], [], [], [], [], [], [], []
- ORA-04031: unable to allocate 1456 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","kgnfs rserver")

The incident trace file shows the following failing statement:
----- Current SQL Statement for this session -----
SELECT value FROM v$spparameter WHERE name = 'log_archive_min_succeed_dest'  AND sid='*'

The ORA-4031 trace file shows high values for kgnfs memory allocations:

Memory Utilization of Subpool 1
Allocation Name Size
_________________________ __________
"sql area " 139312592
"kgnfs rserver " 373405552
"kgnfs local " -1945451456 <== (A negative value like this is due to an internal overflow error and indicates value over 2G)


- Direct NFS is enabled.

- For each "kgnfs rserver" entry also entries of type "kgnfs path" and "kgnfs local" are allocated, so these go hand in hand.

- The call stack of the failure show we are opening the spfile:
Call stack:  kghalp <- kgnfsallocmem <- kgnfs_create_rserver_ent <- kgnfsgetmnthdl <- kgodm_getnfscdata <- kgodm_identify <- odm_identify
<- ksfd_odmopn <- ksfdopn<- kspifisp <- ksp_spfile_open<- ksp_spfile_get <- kspspfftcb <- qerfxFetch <- opifch2

- The access of the spfile looks the result of accessing the v$parameter view.

- To monitor the size of sub pools related to kgnfs use the select statements:


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

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