- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
4#
发表于 2014-12-27 19:05:05
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 [GSIGNAL()+53] 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 [gsignal()+53]
Tue Jun 18 18:14:10 2013
Dumping diagnostic data in directory=[cdmp_20130618181410], requested by
(instance=2, osid=38944), summary=[incident=1425941].
Tue Jun 18 18:14:11 2013
Sweep [inc][1425941]: completed
Sweep [inc2][1425941]: completed
Tue Jun 18 18:23:41 2013
Exception [type: SIGSEGV, unknown code] [ADDR:0x7F73C0D42061]
[PC:0x3CD8C7160E, cfree()+30] [flags: 0x0, count: 1]
Exception [type: unknown signal, unknown code] [ADDR:0x3BBF40D3C0]
[PC:0x2D3BAAF, slaac_int()+237] [exception issued by pid: -1086270528, uid:
59] [flags: 0x2, count: 2]
Tue Jun 18 18:23:41 2013
Exception [type: SIGIOT, unknown code] [ADDR:0x51500009822] [PC:0x3CD8C30285,
gsignal()+53] [exception issued by pid: 38946, uid: 1301] [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 [gsignal()+53] [SIGIOT]
[ADDR:0x51500009822] [PC:0x3CD8C30285] [unknown code] []
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 [type: unknown signal, unknown code] [ADDR:0x3BBF40D3C0]
[PC:0x2D3BAAF, slaac_int()+237] [exception issued by pid: -1086270528, uid:
59] [flags: 0x2, count: 3]
Exception [type: unknown signal, unknown code] [ADDR:0x7FFFEDE01DE0]
[PC:0x2D3BAAF, slaac_int()+237] [flags: 0x2, count: 4]
Tue Jun 18 18:23:42 2013
Dumping diagnostic data in directory=[cdmp_20130618182342], requested by
(instance=2, osid=38946), summary=[incident=1425949].
Tue Jun 18 18:23:43 2013
Sweep [inc][1425949]: completed
Sweep [inc2][1425949]: completed
Tue Jun 18 18:33:50 2013
Beginning log switch checkpoint up to RBA [0x49.2.10], 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 [0x49.2.10], 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:
------------ |
|