Exception Type Sigbus Object Specific Hardware Error
Contents |
上海Oracle用户组 网站地图 Exadata专题 Maclean写的Oracle入门书 Oracle Latch全解 Oracle SQL性能优化专题 Oracle Database 12c新特性 12c PDB/CDB特性专题 blogs.oracle.com上的镜像 Oracle Feed World 自学Oracle之窗 24*7 Oracle紧急服务 诗檀软件PRM-DUL ora 7445 error 下载PRM Oracle灾难恢复软件 Oracle数据恢复专题 Oracle DUL Data Unloader数据恢复工具 Oracle
Ora-00600 Internal Error Code Solution
DUL LEARN MORE ORA-07445 [SIGBUS] [Object specific hardware error]错误一例 2010/09/09 by ora 00600 internal error code arguments 2141 Maclean Liu 3 Comments 一套Solaris上的9.2.0.7系统,实例意外终止,告警日志中出现以下记录: Thu Sep 2 02:15:41 2010 Errors in file /u01/app/oracle/admin/preg063/bdump/preg063_smon_11391.trc: ORA-07445: exception encountered: core dump
Ora 00600 Internal Error Code Arguments Rwoirw Check Ret Val
[0000000101E05500] [SIGBUS] [Object specific hardware error] [0xFFFFFFFF7CB3BF90] [] [] Thu Sep 2 02:15:48 2010 Errors in file /u01/app/oracle/admin/preg063/bdump/preg063_pmon_11379.trc: ORA-00474: SMON process terminated with error Thu Sep 2 02:15:48 2010 PMON: terminating instance due to error 474 Wed ora 00600 internal error code arguments 4194 Sep 1 15:04:20 2010 Errors in file /u01/app/oracle/admin/preg063/udump/preg063_ora_1772.trc: ORA-07445: exception encountered: core dump [FFFFFFFF7F400980] [SIGBUS] [Object specific hardware error] [0xFFFFFFFF7CA78000] [] [] Wed Sep 1 15:06:24 2010 Errors in file /u01/app/oracle/admin/preg063/udump/preg063_ora_5316.trc: ORA-07445: exception encountered: core dump [0000000101E10F94] [SIGBUS] [Object specific hardware error] [0xFFFFFFFF7C843DC8] [] [] Wed Sep 1 15:06:24 2010 Errors in file /u01/app/oracle/admin/preg063/udump/preg063_ora_5207.trc: ORA-07445: exception encountered: core dump [0000000101E10F94] [SIGBUS] [Object specific hardware error] [0xFFFFFFFF7C887A70] [] [] Wed Sep 1 15:06:24 2010 Errors in file /u01/app/oracle/admin/preg063/udump/preg063_ora_28532.trc: ORA-07445: exception encountered: core dump [0000000101E05500] [SIGBUS] [Object specific hardware error] [0xFFFFFFFF7C9B7FE8] [] [] Wed Sep 1 15:06:31 2010 Errors in file /u01/app/oracle/admin/preg063/udump/preg063_ora_4392.trc: ORA-07445: exception encountered: core dump [0000000100624600] [SIGBUS] [Object specific hardware
November 2003 22:08 Mark Chatwin Messages: 3Registered: November 2003 Junior Member Oracle
Ora-00600 Internal Error Code Arguments Kcratr_nab_less_than_odr
ORA-07445 errors. Hello I am getting lots of 07445
Ora 00600 Internal Error Code Arguments Kdsgrp1
internal errors trying to run certain SQL queries on our Oracle 9i database. ora 600 error oracle 10g I have the .trc files from the server which contains the stack dump of the thread which is crashing. Please can http://www.askmaclean.com/archives/ora-07445-sigbus-object-specific-hardware-error%E9%94%99%E8%AF%AF%E4%B8%80%E4%BE%8B.html you advise me how to resolve this issue. Here is a sample of the trace file. Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [[0x40481760, strcpy()+64]] *** 2003-11-25 09:50:43.023 ksedmp: internal or fatal error ORA-07445: exception encountered: http://www.orafaq.com/forum/t/21313/ core dump [[strcpy()+64]] [[SIGSEGV]] [[Address not mapped to object]] [[0x0]] [[]] [[]] ORA-07445: exception encountered: core dump [[strcpy()+64]] [[SIGSEGV]] [[Address not mapped to object]] [[0x0]] [[]] [[]] ORA-07445: exception encountered: core dump [[evaopn2()+282]] [[SIGSEGV]] [[Address not mapped to object]] [[0x0]] [[]] [[]] Current SQL statement for this session: SELECT SUBSTR(GETTIMING_UNIWOH(TBLWORKORDERS.WO_ID,'U'),1,10) AS UDATE, TBLWORKORDERS.WO_TYPE, TBLWORKORDERTYPES.WO_TYPE_DESC, SUM(TBLINVOICECOSTS.INV_COST) AS COST, SUM(TBLINVOICECOSTS.INV_ADJUSTMENT) AS ADJUSTMENT, SUM(TBLINVOICECOSTS.INV_GST) AS GST, COUNT(TBLWORKORDERS.WO_ID) AS QTY, SUM(TBLINVOICECOSTS.INV_COST+TBLINVOICECOSTS.INV_ADJUSTMENT+TBLINVOICECOSTS.INV_GST) AS NETT FROM (TBLWORKORDERS LEFT JOIN TBLINVOICECOSTS ON TBLWORKORDERS.WO_ID = TBLINVOICECOSTS.WO_ID) LEFT JOIN TBLWORKORDERTYPES ON (TBLWORKORDERS.WO_TYPE = TBLWORKORDERTYPES.WO_TYPE) AND (TBLWORKORDERS.CONTRACT_ID = TBLWORKORDERTYPES.CONTRACT_ID) WHERE (((TBLWORKORDERS.CONTRACT_ID)='ORI001') AND ((TBLWORKORDERS.WO_STATUS)='U') AND (GETTIMING_UNIWOH(TBLWORKORDERS.WO_ID,'U') BETWEEN '01/11/2003 00:00:00' AND '30/11/2003 23:59:59')) GROUP BY SUBSTR(GETTIMING_UNIWOH(TBLWORKORDERS.WO_ID,'U'),1,10), TBLWORKORDERS.WO_TYPE, TBLWORKORDERTYPES.WO_TYPE_DESC ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------
of these signals are indications that your program is seriously broken in some way, and there’s usually no way to continue the computation which encountered the http://www.gnu.org/s/libc/manual/html_node/Program-Error-Signals.html error. Some programs handle program error signals in order to tidy up before terminating; for example, programs that turn off echoing of terminal input should handle program error signals in order to turn echoing back on. The handler should end by specifying the default action for the signal that happened and then reraising it; this will cause the program internal error to terminate with that signal, as if it had not had a handler. (See Termination in Handler.) Termination is the sensible ultimate outcome from a program error in most programs. However, programming systems such as Lisp that can load compiled user programs might need to keep executing even if a user program incurs an error. These programs have handlers which internal error code use longjmp to return control to the command level. The default action for all of these signals is to cause the process to terminate. If you block or ignore these signals or establish handlers for them that return normally, your program will probably break horribly when such signals happen, unless they are generated by raise or kill instead of a real error. When one of these program error signals terminates a process, it also writes a core dump file which records the state of the process at the time of termination. The core dump file is named core and is written in whichever directory is current in the process at the time. (On GNU/Hurd systems, you can specify the file name for core dumps with the environment variable COREFILE.) The purpose of core dump files is so that you can examine them with a debugger to investigate what caused the error. Macro: int SIGFPE The SIGFPE signal reports a fatal arithmetic error. Although the name is derived from “floating-point exception”, this signal actually covers all arithmetic e