My Oracle Support Banner

Java.sql.SQLRecoverableException: No More Data To Read From Socket And "ORA-07445: exception encountered: core dump [pevm_SETN()+53] [SIGSEGV]" While Executing Oracle Financial Applications (Doc ID 1464594.1)

Last updated on OCTOBER 17, 2022

Applies to:

JDBC - Version and later
Information in this document applies to any platform.


Oracle Applications using JDBC/thin driver version fails with

java.sql.SQLRecoverableException: No more data to read from socket

while executing a sql statement.

java.sql.SQLRecoverableException: No more data to read from socket
at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(
at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(
at oracle.jdbc.driver.T4CTTIfun.receive(
at oracle.jdbc.driver.T4CTTIfun.doRPC(
at oracle.jdbc.driver.T4C8Oall.doOALL(
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper



and the next information in the alert log:

ORA-07445: exception encountered: core dump [pevm_SETN()+53] [SIGSEGV] [ADDR:0x12] [PC:0x915C27B] [Address not mapped to object] []

========= Dump for incident 116281 (ORA 7445 [pevm_SETN()+53]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x12] [PC:0x915C27B, pevm_SETN()+53] [flags: 0x0, count: 1]
%rax: 0x0000000000000000 %rbx: 0x000000006a43f888 %rcx: 0x0000000000000008
%rdx: 0x0000000000000001 %rdi: 0x00002ba6e70e5810 %rsi: 0x00000000894bcf10
%rsp: 0x00007fff7821eff0 %rbp: 0x00007fff7821f020 %r8: 0x00002ba6e85856c0
%r9: 0x000000006a622048 %r10: 0x000000006a43f888 %r11: 0x00002ba6e85856d8
%r12: 0x00002ba6e70e5810 %r13: 0x00000000894bcf10 %r14: 0x00002ba6e70e5810
%r15: 0x00002ba6e70e5880 %rip: 0x000000000915c27b ïl: 0x0000000000010246
pevm_SETN()+37 (0x915c26b) je 0x915c277
pevm_SETN()+39 (0x915c26d) cmp $3,%rax
pevm_SETN()+43 (0x915c271) jnz 0x915c39a
pevm_SETN()+49 (0x915c277) mov 0x0(%r13),%rcx
> pevm_SETN()+53 (0x915c27b) movzwl 0xa(%rcx),êx
pevm_SETN()+57 (0x915c27f) and $-7,êx
pevm_SETN()+60 (0x915c282) or $2,êx
pevm_SETN()+63 (0x915c285) mov %ax,0xa(%rcx)
pevm_SETN()+67 (0x915c289) cmp $19,íx

*** 2012-05-11 12:33:29.634
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=3fffg3xrbzut4) -----
BEGIN FND_MSG_PUB.initialize ; PO_DOC_NUMBERING_PKG.DEFAULT_DOC_NUMBER_UDA ( p_doc_header_id => :1, p_draft_id => :2, p_template_id => :3, p_context_usage => :4, p_source_org_owned => :5, p_caller => :6, x_doc_number => :7, x_return_status => :8 ); END;





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.