一套Oracle 19c （19.8）RAC dataguard环境，standby 总时自动crash， 报错提示是lms进程异常触发ora-7445 kcbzwb 在cache层的内部错误， 确认为oracle bug, 后期应该比较常见，记录一下。
Dump file /u02/app/oracle/diag/rdbms/stdanbob/anbob1/incident/incdir_280197/anbob1_lms0_119036_119054_i280197.trc Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.8.0.0.0 Build label: RDBMS_19.8.0.0.0DBRU_LINUX.X64_200702 ORACLE_HOME: /u02/app/oracle/product/19.0.0/db_1 System name: Linux Node name: anbob_com1 Release: 3.10.0-957.el7.x86_64 Version: #1 SMP Thu Oct 4 20:48:51 UTC 2018 Machine: x86_64 Instance name: anbob1 Redo thread mounted by this instance: 1 Oracle process number: 24 Unix process pid: 119036, thread id: 119054, image: oracle@anbob_com1 (LMS0) *** 2021-07-05T15:48:46.750428+08:00 *** SESSION ID:(2281.44449) 2021-07-05T15:48:46.750501+08:00 *** CLIENT ID:() 2021-07-05T15:48:46.750525+08:00 *** SERVICE NAME:() 2021-07-05T15:48:46.750544+08:00 *** MODULE NAME:() 2021-07-05T15:48:46.750572+08:00 *** ACTION NAME:() 2021-07-05T15:48:46.750591+08:00 *** CLIENT DRIVER:() 2021-07-05T15:48:46.750609+08:00 *** CONTAINER ID:(4) 2021-07-05T15:48:46.750632+08:00 [TOC00000] Jump to table of contents Dump continued from file: /u02/app/oracle/diag/rdbms/stdanbob/anbob1/trace/anbob1_lms0_119036_119054.trc [TOC00001] ORA-07445: exception encountered: core dump [kcbzwb()+2265] [SIGSEGV] [ADDR:0xCC] [PC:0x1D9E009] [Address not mapped to object] [] ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- ksedst1()+95 call kgdsdst() 7FFFEF55A430 000000003 7FFFEF554760 ? 7FFFEF554878 ? 000000000 000000083 ? ksedst()+58 call ksedst1() 000000001 000000001 7FFFEF554760 ? 7FFFEF554878 ? 000000000 ? 000000083 ? dbkedDefDump()+2344 call ksedst() 000000001 000000001 ? 8 7FFFEF554760 ? 7FFFEF554878 ? 000000000 ? 000000083 ? ksedmp()+577 call dbkedDefDump() 000000003 000000003 7FFFEF554760 ? 7FFFEF554878 ? 000000000 ? 000000083 ? ssexhd()+2859 call ksedmp() 00000044F 000000003 ? 7FFFEF554760 ? 7FFFEF554878 ? 000000000 ? 000000083 ? sslssSynchHdlr()+40 call ssexhd() 00000000B 000000000 1 7FFFEF55BBF0 7FFFEF55BAC0 7FFFEF55BA28 000000083 ? sslsshandler()+94 call sslssSynchHdlr() 000002000 000000000 000000000 7FFFEF55BAC0 ? 7FFFEF55BA28 ? 000000083 ? __sighandler() call sslsshandler() 00000000B 7FFFEF55BBF0 7FFFEF55BAC0 7FFFEF55BAC0 ? 7FFFEF55BA28 ? 000000083 ? kcbzwb()+2265 signal __sighandler() 0000004E3 000000000 001024181 624DD2F1A9FBE77 ? 000000000 ? 000029522 ? kcbgtcr()+68032 call kcbzwb() 424FEA8A0 ? 0000001A1 ? 41AA18970 7FFFF15F97E0 000000001 000000033 ? kclgeneratecr()+785 call kcbgtcr() 7FFFF15F9E90 000000000 5 00000001C 000000000 000000001 ? 000000033 ? kclgeneratecr_pdb() call kclgeneratecr() 400027B69548 7FFFF15FB0A0 +3924 7FFFF15FAE30 060000000 000000000 0000038B4 kclgcr()+334 call kclgeneratecr_pdb() 400027B69548 7FFFF15FB0A0 7FFFF15FAE30 060000000 000000000 0000038B4 kclcrrf()+310 call kclgcr() 400027B69548 7FFFF15FB0A0 7FFFF15FAE30 060000000 0000038B4 000000002 kjblcrcbk()+459 call kclcrrf() 47FBCF340 400027B69548 000000098 060000000 7FFFF15FB0A0 000000000 kjbrscrping()+1695 call kjblcrcbk() 00003F158 0000001A1 FFFFFFFFFFFFFFFF FFFFFFFFE7FA0004 47FBCF340 400027B69548 kjbrcrcvt()+1525 call kjbrscrping() 2F1AEDF48 41FD57948 000000000 47F53D540 000000B6D 000000001 kjbmpocr()+42072 call kjbrcrcvt() 2F1AEDF48 41FD57948 000000000 47F53D540 000000B6D 000000B6D kjmxmpm()+1174 call kjbmpocr() 000000001 41FD57948 ? 000000000 ? 47F53D540 ? 400000B6D 000000B6D ? kjmpmsgi()+708 call kjmxmpm() 400027B694A0 7FFFF16089D0 0681EC1FC 000000001 000000000 000000000 kjmsm()+5040 call kjmpmsgi() 400027B694A0 000000001 000000001 7FFFF16089D0 000000000 000000000 ? ksbdispatch()+365 call kjmsm() 3E3F9F3D0 000000001 ? 000000001 ? 7FFFF16089D0 ? 000000000 ? 000000000 ? opirip()+522 call ksbdispatch() 3E3F9F3D0 ? 000000001 ?
There is a valid scenario where LMS could serve a CR block even when that PDB is marked “closed”. In this case PDB SGA will remain uninitialized and hence wait stats will not be updated.
相关的2个BUG Bug 31796882和Bug 30647133