For quite some time I could not find the reason behind SQL Developer not opening the java folder. As soon as trying to open it it went crazy. Connections would be reconnected on each mouse click in the tree -> tables, packages, procedures ….
Finally I noticed in alert log an error started popping up. It reads like this:
xxx(3):Exception [type: SIGBUS, Non-existent physical address] [ADDR:0x401FC8000000] [PC:0x10F340C, ksm_mga_heap_alloc_seg()+140] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/xxx1/xxx/trace/xxx_ora_189996.trc (incident=22001) (PDBNAME=xxx):
ORA-07445: exception encountered: core dump [ksm_mga_heap_alloc_seg()+140] [SIGBUS] [ADDR:0x401FC8000000] [PC:0x10F340C] [Non-existent physical address] []
PCHDUAT(3):Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Searching the internet did not reveal much information except something similar. The proposed solution was to increase the /dev/shm space to at lease the size larger than the value of SGA_MAX_SIZE, if set, or should be set to be at least MEMORY_TARGET or MEMORY_MAX_TARGET, whichever is larger.
A simple command for temporary increase provided immediate resolution without even a database bounce.
In my case the memory was set to 11GB so 12GB shm would suffice:
mount -o remount,size=12G /dev/shm
This error was present from version of oracle database 11 onwards and it was still happening on version 19.11.
Related oracle article: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=201141489940754&id=1585946.1&_afrWindowMode=0&_adf.ctrl-state=pvop9ect3_102 (title: ORA-07445: [KCBHFHO()+49] [SIGBUS] [NON-EXISTENT PHYSICAL ADDRESS] (Doc ID 1585946.1))
Leave a Reply