问题描述
ORA-1092 : opitsk aborting process
Thu Mar 14 17:45:23 2019
opiodr aborting process unknown ospid (85619) as a result of ORA-1092
Instance terminated by LGWR, pid = 14558
---trace file
Trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_lgwr_14558.trc Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options ORACLE_HOME = /u01/app/oracle/product/db System name: Linux Node name: NEWDB Release: 3.8.13-118.19.4.el6uek.x86_64 Version: #2 SMP Mon Aug 14 14:43:00 PDT 2017 Machine: x86_64 Instance name: db228 Redo thread mounted by this instance: 1 Oracle process number: 23 Unix process pid: 14558, image: oracle@NEWDB (LGWR) *** 2019-03-14 17:45:23.401 *** SESSION ID:(1818.3) 2019-03-14 17:45:23.401 *** CLIENT ID:() 2019-03-14 17:45:23.401 *** SERVICE NAME:(SYS$BACKGROUND) 2019-03-14 17:45:23.401 *** MODULE NAME:() 2019-03-14 17:45:23.401 *** ACTION NAME:() 2019-03-14 17:45:23.401 error 4021 detected in background process ORA-04021: timeout occurred while waiting to lock object kjzduptcctx: Notifying DIAG for crash event ----- Abridged Call Stack Trace ----- ksedsts()+465<-kjzdssdmp()+267<-kjzduptcctx()+232<-kjzdicrshnfy()+63<-ksuitm()+5594<-ksbrdp()+3507<-opirip()+623<-opidrv()+603<-sou2o()+103<-opimai_real()+250<-ssthrdmain()+265<-main()+201<-__libc_start_main()+253 ----- End of Abridged Call Stack Trace ----- *** 2019-03-14 17:45:23.441 LGWR (ospid: 14558): terminating the instance due to error 4021 ksuitm: waiting up to [5] seconds before killing DIAG(14416)
-------------------alert log
RFS[1978]: Selected log 7 for thread 1 sequence 126956 dbid -1829163167 branch 884538467 Thu Mar 14 17:40:37 2019 Media Recovery Waiting for thread 1 sequence 126956 (in transit) Recovery of Online Redo Log: Thread 1 Group 7 Seq 126956 Reading mem 0 Mem# 0: /u02/db/data//sta07.log Thu Mar 14 17:40:38 2019 Archived Log entry 245829 added for thread 1 sequence 126955 ID 0x990ed9e3 dest 1: Thu Mar 14 17:40:42 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms///trace/_ora_84395.trc Thu Mar 14 17:41:41 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms///trace/_ora_84730.trc Thu Mar 14 17:42:04 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84789.trc Thu Mar 14 17:42:14 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84777.trc Thu Mar 14 17:42:26 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84438.trc Thu Mar 14 17:42:40 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84561.trc Thu Mar 14 17:43:05 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84597.trc Thu Mar 14 17:44:53 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84740.trc Thu Mar 14 17:45:09 2019 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_ora_84973.trc Thu Mar 14 17:45:23 2019 Errors in file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_lgwr_14558.trc: ORA-04021: timeout occurred while waiting to lock object LGWR (ospid: 14558): terminating the instance due to error 4021 Thu Mar 14 17:45:23 2019 System state dump requested by (instance=1, osid=14558 (LGWR)), summary=[abnormal instance termination]. Thu Mar 14 17:45:23 2019 opiodr aborting process unknown ospid (48702) as a result of ORA-1092 System State dumped to trace file /u01/app/oracle/product/diag/rdbms/db228/db228/trace/db228_diag_14416_20190314174523.trc Thu Mar 14 17:45:23 2019 ORA-1092 : opitsk aborting process Thu Mar 14 17:45:23 2019 opiodr aborting process unknown ospid (85619) as a result of ORA-1092 Instance terminated by LGWR, pid = 14558 Thu Mar 14 17:54:25 2019 Starting ORACLE instance (normal) ************************ Large Pages Information ******************* Per process system memlock (soft) limit = UNLIMITED Total Shared Global Region in Large Pages = 45 GB (100%) Large Pages used by this instance: 23041 (45 GB) Large Pages unused system wide = 3 (6144 KB) Large Pages configured system wide = 23044 (45 GB) Large Page size = 2048 KB
专家解答
很不幸,遇到了BUG,相关的BUG号是:11712267 和 16717701 。
这个问题在11.2.0.4已经有了解决方案:
如果经常出现,可以设置隐含参数,增加锁超时时间:
alter system set "_adg_parselock_timeout"=500 scope=both sid='*';
最后修改时间:2019-03-20 21:11:40
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。