ORA-07445: exception encountered: core dump [PC:0x90000000D017E10] [SIGSEGV]
这个月给客户做巡检时在alert日志发现这个错误ORA-07445: exception encountered: core dump 请大神帮着分析分析，谢谢！ORA-07445: exception encountered: core dump []
2014/11/18 04:39:20 Incident details in: /u01/oracle/diag/rdbms/momdb/momdb2/incident/incdir_432484/momdb2_ora_16778166_i432484.trc
2014/11/18 04:39:20 Use ADRCI or Support Workbench to package the incident.
2014/11/18 04:39:20 See Note 411.1 at My Oracle Support for error and packaging details.
2014/11/18 04:39:23 Dumping diagnostic data in directory=, requested by (instance=2, osid=16778166), summary=.
2014/11/18 04:39:25 Sweep : completed
2014/11/18 04:39:25 Sweep : completed
数据库版本是11.2.0.3，OS版本是AIX 6.1
*** 2014-11-18 04:39:20.986
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
700001b4ec35250 287 package body SYS.DBMS_BACKUP_RESTORE
ksfq_rls=>skgfrls=>90000000cff2b80 ksfq_rls => ksfq_rls - release the sequential device that was allocated earlier
skgfrls
当rman 在释放channel时可能遇到该问题
ODM Finding:
Hdr: 17240394 11.2.0.3.17 RDBMS 11.2.0.3.17 RMAN PRODID-5 PORTID-226 ORA-7445
Abstract: EXADATA: ORA-7445 RELEASING RMAN CHANNEL
*** 07/30/13 02:32 am ***
PROBLEM:
--------
When performing hot backup of e-Business Suite database on Exadata
the backup completes , but errors out while releasing channel
DIAGNOSTIC ANALYSIS:
--------------------
The RMAN message indicate backup successful but errors while releasing
channel
RMAN-8044: channel dev_0: finished piece 1 at 18-JUN-13
RMAN-8530: piece
handle=ERP_Exadata_Ora_Arch_ERPPROD<ERPPROD_636:818445878:1>.cntl
tag=TAG20130618T180437 comment=API Version 2.0,MMS Version 65.7.0.101
RMAN-8540: channel dev_0: backup set complete, elapsed time: 00:00:07
RMAN-3091: Finished backup at 18-JUN-13
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-12005: error during channel cleanup
WORKAROUND:
-----------
N/A
RELATED BUGS:
-------------
BUG 15953813 --> suspended as no response in the BUG
REPRODUCIBILITY:
----------------
TEST CASE:
----------
STACK TRACE:
------------
skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
<- ssexhd <- sighandler <- gsignal <- abort <- libc_message
<- int_free <- cfree <- safe_free <- Ipc_omnihosts_cache_free <-
IpcExit
<- OB2_Exit <- sbtend <- skgfrls <- ksfq_rls <- ksfqxdes
<- krbdrel <- krbdgdal <- krbpgc <- ksmupg <- ksuxds
<- ksudel <- opidcl <- opidrv <- sou2o <- opimai_real
<- ssthrdmain <- main <- libc_start_main <- start
SUPPORTING INFORMATION:
-----------------------
The database alert log shows ORA-7554
Tue Jun 18 18:14:10 2013
Dumping diagnostic data in directory=, requested by
(instance=2, osid=38944), summary=.
Tue Jun 18 18:14:11 2013
Sweep : completed
Sweep : completed
Tue Jun 18 18:23:41 2013
Exception
Exception
[exception issued by pid: -1086270528, uid:
59]
Tue Jun 18 18:23:41 2013
Exception [PC:0x3CD8C30285,
gsignal()+53] [flags: 0x0, count:
1]
Errors in file
/u01/app/oracle/diag/rdbms/erpprod/ERPPROD2/trace/ERPPROD2_ora_38946.trc
(incident=1425949):
ORA-7445: exception encountered: core dump
[]
Incident details in:
/u01/app/oracle/diag/rdbms/erpprod/ERPPROD2/incident/incdir_1425949/ERPPROD2_o
ra_38946_i1425949.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Exception
[exception issued by pid: -1086270528, uid:
59]
Exception
Tue Jun 18 18:23:42 2013
Dumping diagnostic data in directory=, requested by
(instance=2, osid=38946), summary=.
Tue Jun 18 18:23:43 2013
Sweep : completed
Sweep : completed
Tue Jun 18 18:33:50 2013
Beginning log switch checkpoint up to RBA , SCN: 10293172071514
Thread 2 advanced to log sequence 73 (LGWR switch)
Current log# 7 seq# 73 mem# 0: +DATA/erpprod/onlinelog/group_7.430.818024587
Tue Jun 18 18:33:50 2013
Archived Log entry 97 added for thread 2 sequence 72 ID 0x91fe7e00 dest 1:
Tue Jun 18 18:40:04 2013
Completed checkpoint up to RBA , SCN: 10293172071514
Tue Jun 18 18:46:17 2013
Active Session History (ASH) performed an emergency flush. This may mean that
ASH is undersized. If emergency flushes are a recurring issue, you may
consider increasing ASH size by setting the value of _ASH_SIZE to a
sufficiently large value. Currently, ASH size is 67108864 bytes. Both ASH
size and the total number of emergency flushes since instance startup can be
monitored by running the following query:
select total_size,awr_flush_emergency_count from v$ash_info;
24 HOUR CONTACT INFORMATION FOR P1 BUGS:
----------------------------------------
DIAL-IN INFORMATION:
--------------------
IMPACT DATE:
------------ bug 17240394 最后没有找到cause 和solution ，如果仅仅是release channel时报错 那么一般可以忽略 本帖最后由 parknkjun 于 2014-12-28 00:27 编辑
感谢maclean回复
页:
[1]