LGWR Hangs in IO_GETEVENTS when Access to Mirrored REDO Logs is Lost
(Doc ID 850876.1)
Last updated on MARCH 09, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
SUSE \ UnitedLinux x86-64
Symptoms
On SUSE Linux Enterprise Server 10 (x86_64) PATCHLEVEL 1 and a database with mirrored redo logs on two different SAN storage systems with multipathing TURNED ON, LGWR hangs in IO_GETEVENTS system call when access to the mirrored redo log files is lost.
Changes
These database's parameters are set:
filesystemio_options=SETALL
disk_asynch_io=TRUE or filesystemio_options=ASYNCH
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |