[One Moss per day]-Troubleshooting: High CPU Utilization (164768.1)-System

[One Moss per day]-Troubleshooting: High CPU Utilization (164768.1)-Series 3 these two processes are usually related to IO, but when there is an operating system problem, the two processes may "spin (wait)" until the IO operation is completed. This kind of wait is a kind of CPU operation. The slow or failed asynchronous IO operations can also prove that they are high CPU consumption. If LGWR uses 100% of the CPU resources intermittently, the asynchronous input/output AIO configuration should be re-checked. As a temporary method, you can set the following parameters to prevent LGWR from waiting: _ lgwr_async_io = false. This parameter can disable the asynchronous input and output of LGWR. Note: 813473.1 LGWR Uses Async I/O Inspite Of Setting _ lgwr_async_io = False Note 7385253.8 Bug 7385253-Slow Truncate/DBWR uses high CPU/CKPT blocks on RO enqueue use _ prop = false to disable asynchronous IO it may improve the performance of the database, however, the risk that COMMIT can be lost to ensure data security. According to @ Maclean_liu, a bug (Bug: 8357698) exists between 10.1.0.2 and 11.1.0.6, resulting in overwrite failure after _ lgwr_async_io parameter is set, and is fixed after 11.2, however, the _ lgwr_async_io parameter is also blocked. Whether or not the LGWR enables async io depends entirely on disk_asynch_io and filesystemio_options.