Thank you So much. But I see we have both memory_target and
memory_max_target both set as 0,so ideally we should not hit that bug.
DDE: Problem Key 'ORA 4031' was flood controlled (0x2) (incident: 664776)
ORA-04031: unable to allocate bytes of shared memory ("","","","")
OSSIPC:IPCDAT DESTROY QP for qp 0x1987de28 ep 0x1987dc00 drain start time
11715030699
OSSIPC:IPCDAT DESTROY QP for qp 0x1987de28 ep 0x1987dc00 drain complete num
reqs drained 0 drain end time 11715030699 drain time 0 msec time slept 0
OSSIPC:IPCDAT DESTROY QP for qp 0x19860908 ep 0x19860690 drain start time
11715030702
On Wed, Jun 15, 2022 at 2:59 PM Lok P <loknath.73@xxxxxxxxx> wrote:
Have you checked below this seems matching.
ORA-4031 Errors On ASM Instance When Huge Pages Are Enabled On The System
(Doc ID 1625886.1)
On Wed, Jun 15, 2022 at 2:51 PM Pap <oracle.developer35@xxxxxxxxx> wrote:
We are hitting below Ora-4031 in one customer database. Even we have
'free memory' available (~2GB) in shared_pool during the error. And also
the size of the "KKSSP" sub pool and it was showing null value only. Its
version 19.11 database has the below memory setup. We do see the resize
operation in which the shared_pool_size was 12GB and was GROWing and
db_cache was 2GB and was tryin to SHRINK and both errored out.
ORA-04031: unable to allocate 12312 bytes of shared memory ("shared
pool","unknown object","KKSSP^3497","kglseshtTable")
memory_target - 0, memory_max_target - 0,sga_max_size - 35GB,sga_target -
0,shared_pool_size - 8GB,shared_pool_reserved_size -
1.2GB,_shared_pool_reserved_pct - 15,db_cache_size- 20GB
