Home > database >  ORA - 03113: the communication channel of eof and alert the ORA - 07445: in the abnormal errors
ORA - 03113: the communication channel of eof and alert the ORA - 07445: in the abnormal errors

Time:09-23

Development colleague says executive loadjava registered today called the ORA - 03113 error, execute the statement is loadjava - r - f - u schema/password @ IP/service name json - 20180409. The jar, then I open the alert log, when native execution at the same mistake, at the same time in the alert log was a pile of the following error:
Mon Apr 09 16:54:29 2018
Exception [type: SIGSEGV, Address not mapped to the object] [ADDR: 0 by 8] [PC: 0 x10a6bd708, joet_create_root_thread_group () + 136] [flags: 0 x0, count: 1)
Errors in the file/u01/app/oracle/diag/RDBMS/bjsde a4sde2/trace/a4sde2_ora_32061 TRC (incident=1268535) :
ORA - 07445: an exception error: core dump [joet_create_root_thread_group () + 136] [SIGSEGV] [ADDR: 0 by 8] [PC: 0 x10a6bd708] [Address not mapped to the object] []
Incident details: in/u01/app/oracle/diag/RDBMS/bjsde/a4sde2/Incident/incdir_1268535/a4sde2_ora_32061_i1268535 TRC
Use ADRCI or Support the Workbench to package the incident.
See Note 411.1 at My Oracle Support for the error and packaging details.
Mon Apr 09 16:54:33 2018
Dumping the diagnostic data in the directory=[cdmp_20180409165433], requested by (the instance=2, osid=32061), the summary=[incident=1268535].
Mon Apr 09 16:54:33 2018
Exception [type: SIGSEGV, Address not mapped to the object] [ADDR: 0 by 8] [PC: 0 x10a6bd708, joet_create_root_thread_group () + 136] [flags: 0 x0, count: 1)
Errors in the file/u01/app/oracle/diag/RDBMS/bjsde a4sde2/trace/a4sde2_ora_32155 TRC (incident=1268574) :
ORA - 07445: an exception error: core dump [joet_create_root_thread_group () + 136] [SIGSEGV] [ADDR: 0 by 8] [PC: 0 x10a6bd708] [Address not mapped to the object] []
Incident details: in/u01/app/oracle/diag/RDBMS/bjsde/a4sde2/Incident/incdir_1268574/a4sde2_ora_32155_i1268574 TRC
Use ADRCI or Support the Workbench to package the incident.
See Note 411.1 at My Oracle Support for the error and packaging details.
Mon Apr 09 16:54:33 2018
Sweep [inc] [1268574] : completed
Sweep [inc] [1268535] : completed
Sweep/inc2] [1268535] : completed
Mon Apr 09 16:54:39 2018
Exception [type: SIGSEGV, Address not mapped to the object] [ADDR: 0 by 8] [PC: 0 x10a6bd708, joet_create_root_thread_group () + 136] [flags: 0 x0, count: 1)
Errors in the file/u01/app/oracle/diag/RDBMS/bjsde a4sde2/trace/a4sde2_m000_32157 TRC (incident=1268662) :
ORA - 07445: the exception encountered: the core dump [joet_create_root_thread_group () + 136] [SIGSEGV] [ADDR: 0 by 8] [PC: 0 x10a6bd708] [Address not mapped to the object] []
Use ADRCI or Support the Workbench to package the incident.
See Note 411.1 at My Oracle Support for the error and packaging details.
According to alert to TRC files, execute the statement:
* * * 2018-04-09 16:54:33. 700
DbkedDefDump () : Starting a non - incident diagnostic dump (flags=0 x3, level=3, mask=0 x0)
-- -- -- -- -- the Current SQL Statement for this session (sql_id=4 h756dsat9bbr) -- -- -- -- --
The select dbms_java. HandleMd5 ('///'29) from dual
I take out this statement execution alone, really resembles the error described above, what a great god met?
PS: is 11.1 Sparc Solaris operating system, database is 11.2.0.3.0 RAC

CodePudding user response:

Communication channel file at the end, can be in front of the session, to regain the connection is ok

CodePudding user response:

MOS Doc ID 1940340.1
See if this problem,
  • Related