ORA-7445 [eoa_process_old_nfs_entry()+57] Reported After Installing New Java Version (Doc ID 2030367.1)

Last updated on JULY 17, 2015

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


Alert log reports error like:

Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x25C0] [PC:0x481AE39, eoa_process_old_nfs_entry()+57] [flags: 0x0, count: 1]
Errors in file /oracle/home/admin/diag/rdbms/r12auto/r12auto/trace/r12auto_ora_9168.trc  (incident=64537):
ORA-07445: exception encountered: core dump [eoa_process_old_nfs_entry()+57] [SIGSEGV] [ADDR:0x25C0] [PC:0x481AE39] [Address not mapped to object] []
Incident details in: /oracle/home/admin/diag/rdbms/r12auto/r12auto/incident/incdir_64537/r12auto_ora_9168_i64537.trc

The trace file shows characteristics like:

*** 2015-01-13 19:47:41.199
*** SESSION ID:(1199.7598) 2015-01-13 19:47:41.199
*** CLIENT ID:() 2015-01-13 19:47:41.199
*** SERVICE NAME:(SYS$USERS) 2015-01-13 19:47:41.199
*** MODULE NAME:(AUTH_LDAP) 2015-01-13 19:47:41.199
*** CLIENT DRIVER:(jdbcthin) 2015-01-13 19:47:41.199
*** ACTION NAME:(ADD SA MEMBER) 2015-01-13 19:47:41.199

----- Current SQL Statement for this session (sql_id=3s2v9u8jj7n91) -----
BEGIN lab_privilege_api.assign_privs(p_logon_id => 'A977T13M1'); END;

----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
0xb826cdb8       177  package body AUTO_1919753948_ODB.AUTH_LDAP
0xb826cdb8       426  package body AUTO_1919753948_ODB.AUTH_LDAP
0xbcbbb318       227  package body AUTO_1919753948_ODB.LAB_PRIVILEGE_API
0xbcbbb318       677  package body AUTO_1919753948_ODB.LAB_PRIVILEGE_API
0xb6ace498         1  anonymous block

----- Call Stack Trace -----

... eoa_process_old_nfs_entry eoa_sst_map eoa_gc_mswmem_with_stack eomsgc_inner_gc seoastk_bottom_in seoastk_bottom_out seoa_note_stack_inside eoa_gc_mswmem eoa_alloc_mswmem_object eoa_new_ool_alloc joezrt_newarray_char sjoezfc_joezrt_newarray_char_punt java_util_Arrays__copyOf java_lang_AbstractS tringBuilder__expandCapacity java_lang_AbstractS tringBuilder__append com_novell_ldap_asnoString com_novell_ldap_asntring com_novell_ldap_Con nection__writeMessage sjoninvk_jit joevm_joe_run_jit_somersault joe_jit_void_trampoline sjoe_jit_void_callback com_novell_ldap_Con nection__writeMessage sjoninvk_jit joevm_joe_run_jit_somersault joe_jit_void_trampoline sjoe_jit_void_callback com_novell_ldap_Message__sendMessage sjoninvk_jit joevm_joe_run_jit_somersault joe_jit_void_trampoline sjoe_jit_void_callback com_novell_ldap_Mes sageAgent__sendMessage sjoninvk_jit joevm_joe_run_jit_somersault ...

Their registry showed no invalid componets and there were no invalid objects.
Also 0 potential problem(s) were found with a Data Dictionary Health Check.


Initially customer confirmed that their JDBC version is Later they identified that the developers implemented Java 7, but did not change the JDBC driver after moving
from Java 6 and still were using ojdbc6.jar (JDBC for Java 6) to connect to Oracle database. Later the scripts have been changed now to use ojdbc7.jar. But again this issue persists
even after setting ojdbc7.jar.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms