SYMPTOMS
Oracle service suddenly crashes on Windows Server 2016.
When it crashes, there is no error output in the alert log.
2020-07-07T08:51:58.450055+02:00
Thread 1 cannot allocate new log, sequence 3192
Private strand flush not complete
Current log# 2 seq# 3191 mem# 0: <DIR>\REDO02.LOG
2020-07-07T08:52:01.465742+02:00
Thread 1 advanced to log sequence 3192 (LGWR switch)
Current log# 3 seq# 3192 mem# 0: <DIR>\REDO03.LOG
2020-07-07T08:53:23.326783+02:00
Warning: VKTM detected a forward time drift.
Please see the VKTM trace file for more details:
<DIR>\<ORACLE_SID>_vktm_3176.trc <<<<<<<<<< Oracle service would be crash after this.
2020-07-07T08:54:44.652338+02:00
Starting ORACLE instance (normal) (OS id: 6332)
2020-07-07T08:54:44.652338+02:00
All SGA segments were allocated at startup
CAUSE
This issue was investigated by bug 30777036.
As a result of the investigation, it has been determined that the issue is caused by unpublished bug 29920804.
If this issue occurrs, you will frequently see the following stack in the <sid>core.log.
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
---------------------------------------- ---------------------------------------- ---------------- ---------------- ---------------- ----------------
_alloca_probe()+56 0000000000000000 000000001475f268 0000000000000020 0000000000000000 0000000000000000
kwqbmspqueue()+24 __chkstk() 0000000000000000 0000000000000000 0000000000000000 0000000000000000
kwqbmspmain_switch()+733 kwqbmspqueue() 0000000000000000 0000000000000000 0000000000000000 0000000000000000
kwqbmspmain()+1737 kwqbmspmain_switch() 00000000fe71ba18 0000000000000000 0000000000000000 0000000000000000
kwqmnslv()+1539 kwqbmspmain()+193 0000000000000000 0000000000000000 0000000000000000 0000000000000000
kwsbsmspm()+2137 kwqmnslv()+275 000000002d46c240 0000000000000000 0000000000000080 0000000000000000
kwsbgcbkms()+110 kwsbsmspm()+1710 0000000000000000 0000000000000000 0000000000000000 0000000000000000
ksvrdp_int()+2305 kwsbgcbkms() 0000000000000000 00000000feb3ef50 0000000000000000 0000000000000000
ksvrdp()+18 ksvrdp_int()+2232 0000000000000000 0000000000000000 0000000000000000 0000000000000000
opirip()+669 ksvrdp() 0000000000000000 0000000000000000 0000000000000000 0000000000000000
opidrv()+851 opirip() 0000000000000032 0000000000000004 0000000014e1f690 0000000000000000
sou2o()+110 opidrv()+211 0000000000000000 0000000000000000 0000000000000000 0000000000000000
opimai_real()+283 sou2o() 0000000014e1f6b0 0000000000000032 0000000000000004 0000000014e1f690
opimai()+268 opimai_real() 000000000fe80168 00000000ffffffff 0000000000000000 0000000000000000
BackgroundThreadStart()+580 opimai() 0000000000000003 0000000014e1fc70 00000000a039d905 0000000000000000
00007FFF8E3D84D4 BackgroundThreadStart() 0000000021d1fb90 0000000000000000 0000000000000000 0000000000000000
00007FFF8E52E871 00007FFF8E3D84C0 0000000000000000 0000000000000000 0000000000000000 0000000000000000
The fix is included in Windows Bundle patch 19.7.0.0.0(Patch 30901317) or later.
SOLUTION
Apply Windows Bundle patch 19.7.0.0.0(Patch 30901317) or later.
|