Sskgxp_ip: Primary Interface Down In Alert Log
Note:332517.1
[@more@]Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.4.0This problem can occur on any platform.
Symptoms
Message in alert file:
SSKGXP_IP: Primary interface down
operation ioctl
location sskgxphypr3
error Error 0
Cause
The message is trying to indicate that it was unable to send it's inter-instance communication over the private interconnect.The reason this is not necessarily an error, is because in the absence of the availability of the specified interconnect, inter-instance messages will be sent over the public network interface.In the absence of the availability of the specified interconnect, inter- instance messages will be sent over the public network interface.
Solution
1. Check the swap space when these errors happen, try to increase the swap
space.
While making the call to check whether the Primary interface is up or down, we
need to allocate memory via malloc. This will fail if we run out of memory.
Or
2. It was most likely an OS error like having a problem with the hyperfabric interface.
You might also want to contact the OS/cluster vendor and have them check the cluster.
References
Bug 2755777 - Interconnect Failover Using Hmp Takes Long Time來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/85922/viewspace-1002060/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Queries to view Alert Log content And Alert LocationView
- Oracle alert.log:network interface with IP address xxxx no longer operationalOracle
- alert log on Oracle11gOracle
- Oracle11g_alert_logOracle
- alert log檔案的變化
- Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary [ID 789370.1]
- alert檔案中出現:Auto-tuning: Shutting down background process GTXd
- 警告日誌檔案alert_.log
- Alert Dialog "Done"按鈕定義.
- Linux : logrotate: ALERT exited abnormally with [1]LinuxlogrotateORM
- [Shell] monitor oracle alert.log file and sendmailOracleAI
- alert_log設定成external table
- 熟練使用alert.log日誌
- ORA-16191: Primary log shipping client not logged on standbyclient
- Manual Log Switching Causing Cannot Allocate New Log in Alert Log_435887.1
- Alert Log中回收站物件操作告警物件
- 8.Monitor oracle alert.log file and sendmailOracleAI
- PMON failed to acquire latch, see PMON dump in alert logAIUI
- 配置 Oracle 10g RAC primary + RAC logical standbyOracle 10g
- Oracle DG ORA-16191: Primary log shipping client not logged on standbyOracleclient
- Voltage Translation for Analog to Digital Interface ADCGit
- Oracle清理trace、alert、aud、listener.log檔案Oracle
- console.log()和alert()區別
- oracle10g R2 logical standby switchover to primaryOracle
- Alert.log shows No Standby Redo Logfiles Of Size 153600 Blocks AvailableBloCAI
- [Shell] Monitor other host oracle instance alert.log and mailOracleAI
- Oracle 警告日誌 (alert log) 中包含哪些內容 ?Oracle
- put it down?
- 9.Monitor other host oracle instance alert.log and mailOracleAI
- 'PMON failed to acquire latch, see PMON dump' in Alert Log-976714.1AIUI
- Failed to start the Clusterware. Last 20 lines of the alert log follow:AIAST
- Alert.log shows No stdby Redo Logfiles Of Size 153600 Blocks Available-405836.1BloCAI
- [Dataguard]ORA-16191: Primary log shipping client not logged on standby問題解決client
- MongoDB Primary 為何持續出現 oplog 全表掃描?MongoDB
- 【LINUX學習】磁碟分割之建立primary和logical 分割槽Linux
- 一個簡單的自動備份alert log指令碼指令碼
- [20150505]關於alert.log檔案.txt
- interface method 返回 interface 如何實現?