Академический Документы
Профессиональный Документы
Культура Документы
Volume 5 Issue 1, November-December 2020 Available Online: www.ijtsrd.com e-ISSN: 2456 – 6470
IO Management in Oracle
Vijay Kumar Tiwari
IT Consultant, HCL America Inc, Texas, United States
How to cite this paper: Vijay Kumar Tiwari "IO Copyright © 2020 by author (s) and
Management in Oracle" Published in International Journal of Trend in Scientific
International Journal of Trend in Scientific Research and Development Journal. This is an
Research and Development (ijtsrd), ISSN: Open Access article
2456-6470, Volume-5 | Issue-1, December distributed under the
2020, pp.1466-1467, URL: terms of the Creative
www.ijtsrd.com/papers/ijtsrd38276.pdf IJTSRD38276 Commons Attribution License (CC BY 4.0)
(http://creativecommons.org/licenses/by/4.0)
@ IJTSRD | Unique Paper ID – IJTSRD38276 | Volume – 5 | Issue – 1 | November-December 2020 Page 1466
International Journal of Trend in Scientific Research and Development (IJTSRD) @ www.ijtsrd.com eISSN: 2456-6470
You would be keen to disable asynchronous I/O when you This is not a very good ASYNCH I/O. Try Synchronous I/O
see high average_wait on event db_file_parallel_wait. Other Note 1: Asynchronous I/O operations are more prone to
reason for turning it off will be synchronous I/O is more block corruptions than synchronous operations so many
reliable. DBAs disable it and follow practice as mentioned in above
paragraph. So if you do not have standby databases and
SQL> select event, average_wait from v$system_event where oracle 11g then which automatically recovers corrupted
event like 'db file parallel write'; block on primary then you would not want asynchronous
I/O
@ IJTSRD | Unique Paper ID – IJTSRD38276 | Volume – 5 | Issue – 1 | November-December 2020 Page 1467