- This parameters are available from Oracle 19c (19.1) Database.
- Data Guard maintains internal mechanisms that detect and correct issues with its redo transport and gap resolution processes
- In case of network or disk I/O problems, these mechanisms prevent those processes from hanging and causing unnecessarily long gaps
- Oracle Data Guard has several processes on the Primary and Standby databases that handle redo
transport and archiving which communicate with each other over the network. In certain failure
situations, network hangs, disconnects, and disk I/O issues, these processes can hang potentially
causing delays in redo transport and gap resolution. Data Guard has an internal mechanism to detect
these hung processes and terminate them allowing the normal outage resolution to occur.
The following parameters allow the waits times to be tuned for a specific Data Guard configuration
based on the user network and Disk I/O behavior
SQL> show parameter DATA_GUARD_MAX
NAME TYPE VALUE
———————————— ———– ——————————
data_guard_max_io_time integer 240
data_guard_max_longio_time integer 240
Default: 240
Range of values: 10 to 7200
DATA_GUARD_MAX_IO_TIME
This parameter sets the maximum number of seconds that can elapse before a
process is considered hung while performing a regular I/O operation in an Oracle
Data Guard environment. Regular I/O operations include read, write, and status
operations.
DATA_GUARD_MAX_LONG_IO_TIME
This parameter sets the maximum number of seconds that can elapse before a
process is considered hung while performing a long I/O operation in an Oracle Data
Guard environment. Long I/O operations include open and close operations.
Telegram App: https://t.me/oracledbwr
LinkedIn: https://www.linkedin.com/in/hariprasathdba
LinkedIN Page: https://www.linkedin.com/company/orcldbwr/
Facebook: https://www.facebook.com/HariPrasathdba
FB Group: https://www.facebook.com/groups/oracledbwr/
FB Page : https://www.facebook.com/dbahariprasath/
Twitter : https://twitter.com/hariprasathdba
