ORA-16198: LGWR received timedout error from KSR

Redo Transport to the standby has stopped after the ORA-16198 error.

ERROR

ORA-16198: LGWR received timedout error from KSR
LGWR: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (16198)
LGWR: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 16198 for archive log file 4 to ‘mwstdbydb’
ORA-16198: LGWR received timedout error from KSR
LGWR: Error 16198 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host ‘hostname’

SOLUTİON

You may encounter this error if a network delay occurs while the Redo Transport mode of the error is SYNC. On top of that, if you set Redo Transport mode as ASYNC, the problem will be solved. Solution steps are below.

Step1:

Check the data is sync by quering the tables that frequently changed on primary and standby.

Step2:

Check if there is a lag on standby?

Step3:

At the end of the researches, it was seen that the problem was a network delay when the Redo Transport mode was SYNC. For this reason, Redo Transport mode was taken to ASYNC.

Set Redo Transport Mode to ASYNC:

On Primary:

After the above procedure, the alert logs in the primary are as follows.

PrimaryInstance1

PrimaryInstance2

StandbyInstance1

StandbyInstance2

Step4:

Check if there is a lag on standby again.

Step5:

Check the data is sync by quering the tables that frequently changed on primary and standby again.

 

Onur ARDAHANLI
Author: Onur ARDAHANLI

Leave a Reply

Your email address will not be published. Required fields are marked *