ORA-16198: LGWR received timedout error from KSR
ORA-16198: LGWR received timedout error from KSR
ORA-16198 意味著主庫上的LOG_ARCHIVE_DEST_2的NET_TIMEOUT設定的太小,導致LNS不能在設定的時間內將日誌傳輸到備庫。
解決方法是提高NET_TIMEOUT的值到15-20 秒,
SQL>ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 SERVICE=xyz_STANDBY LGWR SYNC DB_UNIQUE_NAME=xyz_STANDBY NET_TIMEOUT=30 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE);
但是檢視資料庫中的NET_TIMEOUT 值的設定。
09:33:47 ops$admin@rac1>select DEST_NAME,NET_TIMEOUT FROM V$ARCHIVE_DEST;
DEST_NAME NET_TIMEOUT
------------------------- -----------
LOG_ARCHIVE_DEST_1 0
LOG_ARCHIVE_DEST_2 30
LOG_ARCHIVE_DEST_3 30
NET_TIMEOUT 為30 秒。檢視metalink :
Note: If NET_TIMEOUT attribute has already been set to 30, and you still get ORA-16198, that means LNS couldn't finish sending redo block in 30 seconds.
The slowness may caused by:
1. Operating System. Please keep track of OS usage (like iostat).
2. Network. Please keep track network flow (like tcpdump).
不過也有可能是bug
Bug 9259587 Multiple LGWR reconnect attempts in Data Guard MAXIMUM_AVAILABILITY
This note gives a brief overview bug 9259587.
Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 12.1
Versions confirmed as being affected 11.2.0.1 10.2.0.4
Platforms affected Generic (all / most platforms affected)
Fixed:
This issue is fixed in 12.1 (Future Release) 11.2.0.2 (Server Patch Set)
Symptoms:
Related To:
Hang (Process Spins)
Active Dataguard (ADG)
Physical Standby Database / Dataguard
Description
In a Data Guard configuration using LGWR SYNC transport on one or more LOG_ARCHIVE_DEST_n parameters, and using a protection mode of MAXIMUM_AVAILABILITY, then if the primary database becomes disconnected from the standby database, LGWR continues to attempt to reconnect to the standby database. It should instead avoid attempts to reconnect until an ARCH process has re-established communication with the standby database.
Rediscovery Notes:
Alert log contains messages like:
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
Errors in file
/app/oracle/diag/rdbms/ora11g_dga/ora11g/trace/ora11g_lgwr_290838.trc:
ORA-16198: Timeout incurred on internal channel during remote archival
LGWR: Network asynch I/O wait error 16198 log 2 service 'ora11g_DGb'
LGWR: Error 16198 disconnecting from destination LOG_ARCHIVE_DEST_2 standby
host 'ora11g_DGb'
Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
LGWR: Failed to archive log 2 thread 1 sequence 1422 (16198)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22664653/viewspace-704556/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-19511: Error received from media manager layer, error text: ANS0322E (RC-72) no text available fErrorAI
- An error from listenerError
- Slave: received 0 length packet from server, apparent master shutdownServerAPPAST
- linux log中大量 Received SNMP packet(s) from UDPLinuxUDP
- MySQL報錯Slave: received end packet from server, apparent master shutdownMySqlServerAPPAST
- 消除linux log中的大量Received SNMP packet(s) from UDPLinuxUDP
- ORA-24550 Signal Received Error的解決方法Error
- ORA - 12502 TNS:listener received no CONNECT_DATA from clientclient
- tar: Error exit delayed from previous errorsError
- Unknown initial character set index ‘255‘ received from server. Initial client character set can beIndexServerclient
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 3Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 2Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 1Cloud
- Oracle dataguard報錯:Error 1017 received logging on to the standbyOracleError
- LGWR (ospid: 29534): terminating the instance due to error 4021Error
- Linux Log中大量snmpd[10932]: Received SNMP packet(s) from UDP[final]LinuxUDP
- 解決docker: Error response from daemon故障DockerError
- AIX: 'GGS ERROR 190 ... : Received Signal: OMVS Shutdown (33).' [ID 969596.1]AIError
- Got error 28 from storage engine 解決方法GoError
- Oracle LGWR程式Oracle
- MySQL案例09:Last_IO_Error: Got fatal error 1236 from master when reading data from binary logMySqlASTErrorGo
- docker無法拉取(pull)映象Error response from daemonDockerError
- 【Oracle】-【體系結構-LGWR】-LGWR的一些理解Oracle
- Got fatal error 1236 from master when reading data from binary logGoErrorAST
- DBWn,CKPT,LGWR程式
- LGWR,Log Switches, and Checkpoints
- ERROR: Error from ejbc: 檔名、目錄名或卷標語法不正確Error
- rac2節點上配置iscsi 遇到iscsiadm: failing authentication, received incorrect username from targetAI
- Error: cannot fetch last explain plan from PLAN_TABLEErrorASTAI
- 主庫報 Error 12154 received logging on to the standby PING[ARC2]Error
- RAC網路中斷後自動恢復過程日誌ORA-16198: ORA-16198:
- LGWR group commits(原)MIT
- 解決ERROR 1030 (HY000): Got error 168 from storage engine apparmorErrorGoAPP
- PSQLException: ERROR: failed to find conversion function from unknown to charSQLExceptionErrorAIFunction
- Error occurred while downloading files from admin server for deploymentErrorWhileServer
- MySQL主從複製報錯:Got fatal error 1236 from master when reading data fromMySqlGoErrorAST
- LGWR writes redo log (117)
- 解決docker啟動映象報錯:docker: Error response from daemonDockerError