Oracle Error 16063 archiving LNO:n to db

Problem: 客戶19c版本的 alert.log 出現部份的 16063 錯誤訊息

2022-06-03T00:06:09.685391+08:00
Resize operation completed for file# 33, old size 7782400K, new size 7884800K
2022-06-03T00:06:24.219496+08:00
TTO2 (PID:24465): Error 16063 archiving INO:10 to 'dbr'
2022-06-03T00:06:24.629885+08:00
TT05 (PID:112709): SRL selected for T-2.s-104048 for LAD:2
2022-06-03T00:07:40.364133+08:00
Thread 2 advanced to log sequence 104049 (LGWR switch)
Current log# 6
seg# 104049 mem# 0: +DATADG/DB/ONLINELOG/group 6.267.1092587
367
Current l0g# 6 seg# 104049 mem# 1: +FRADG/DB/ONLINELOG/group 6.262.10925873
67
2022-06-03T00:07:41.728337+08:00
TT02 (PID: 24465): SRL selected for T-2.S-104049 for LAD: 4
TT02 (PID:24465) :
SR selected for T-2.5-104049 for LAD:3
2022-06-03T00:07:42.049862+08:00
ARC (PID:24443) : Archived Log entry 892793 added for T-2.5-104048 ID 0x6693c989
TAD:1
2022-06-03T00:07:42.702525+08:00
TTO2 (PID:24465) : SRL selected for T-2.S-104049 for LAD:2
2022-06-03T00:07:43.357092+08:00
TT02 (PID:24465) : Error 16063 archiving NO: 6 to 'dbr'
2022-06-03T00:07:44.411854+08:00

Cause: 對於該錯誤的說法

- Error 16063 is just informative that the destination is detached from the multi-async process and this happens only in environments that have multiple ASYNC destinations
- The detachment happens because one of the destinations is slower than the other destinations. So it can not be collectively served by one process.
- In some situations the switching between single and multi async may be exacerbating the transport lag but the eviction indicates that a network issue is present before switching to a single async process.

Solution:

--Change _REDO_TRANSPORT_ASYNC_MODE
SQL> alter system set "_REDO_TRANSPORT_ASYNC_MODE"=1 scope=spfile sid='*';

--Restart Database
SQL> shutdown immediate;
SQL> startup;

參考來源:

Error 16063 archiving LNO:n to '<db>' (Doc ID 2722180.1)

張貼留言

0 留言