windows下部署12c oms agent 及清除agent
1. Stop the Agent on the target machine:
cd <AGENT_HOME>/bin
emctl stop agent
2. Login to the Repository Ddatabase (via sqlplus) as user SYSMAN and execute the following command:
For example:
SQL> exec mgmt_admin.cleanup_agent('agentmachine.domain:3872');
3. De-install the Agent on the target machine.
首先在server端安裝元件,需賬號密碼
emcli login -username=sysman -password=123456
在windows端建立目錄,c:\soft和c:\agent
agentDeploy.bat -ignorePrereqs AGENT_BASE_DIR=C:\agent OMS_HOST=172.16.5.233 EM_UPLOAD_PORT=4900 AGENT_REGISTRATION_PASSWORD=Oracle123 ORACLE_HOSTNAME=pzyserver08
安裝後會報錯,切換到bin/emctl下,執行emctl status agent和emctl start agent以及emctl upload
如果遇到
After reinstallation need to add agent and host target and then need to perform sync operation for the upload to be successful.
Perform the following steps to resolve the issue:
1. Start the agent:
<AGENT_INST>/bin/emctl start agent
2. Issue following command to add agent and host targets:
<AGENT_INST>/bin/emctl config agent addinternaltargets
This would list the agent target in Setup > Add Target > Auto Discovery Results > Non-Host Targets.
3. Secure the agent:
<AGENT_INST>/bin/emctl secure agent
This would show the host and agent in pending status under Targets > All targets.
4. Do the following steps to show the status of host and agent as up:
<AGENT_INST>/bin/emctl stop agent
<AGENT_INST>/bin/emctl clearstate agent
<AGENT_INST>/bin/emctl start agent
Once done, the host and agent status would be shown as up.
5. Do a resync of agent as per Note 1376968.1.
Follow these steps to perform agent resynchronization :
6. Verify the agent upload:
<AGENT_INST>/bin/emctl upload
Agent uploads will be successful and remaining targets can be discovered.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/21302630/viewspace-1775226/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Agent Upload to OMS Fails if OMS Locked in Secure,Agent isn't Secured_422922.1AI
- 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
- OCSInventoryNG使用之在windows系統下AGENT的批量部署(二)Windows
- Agent to OMS Communi Fails if Agent is 'Blocked' in 10.2.0.5 Grid Cons_799618.1AIBloC996
- EM 12c推送Agent出錯 - OMS_HOST and EM_UPLOAD_PORT is not availableAI
- Agent to OMS Communi Fails if Agent's REPOSITORY_URL Para has Incorrect_737373.1AI
- windows下安裝配置 Navisphere Host AgentWindows
- 本地部署modelscope-agent
- WIN下安裝agent
- zabbix agent 3.0部署文件 安裝部署
- rpm包 手工安裝OEM 12c agent
- 千問AI agent qwan_agent使用AI
- 【GC】重新配置Agent以應對 OMS伺服器的變化GC伺服器
- windows下安裝Jenkins以及配置分散式agent節點WindowsJenkins分散式
- Oracle 12c OEM Cloud Control AGENT 安裝OracleCloud
- GC 10.2.0.1 OMS和Agent連線失敗後的處理過程GC
- 11g Agent Upload Fails with "OMS version not checked Yet". (Doc ID 1265052.1)AI
- Zabbix Agent-Windows平臺配置指導Windows
- 獲取 Windows Phone 的 User-Agent 字串Windows字串
- DevOps專題|基礎Agent部署系統dev
- Apline部署K3s的Agent
- Java Agent(上)Java
- 智慧體Agent智慧體
- Linux下Apache遮蔽user-agentLinuxApache
- OMS to Agent Comm Fails if IP Address of the Grid Ag Machine is Changed-605009.1AIMac
- sysman.emcp.agent.AgentPlugIn raised by the Agent CA-740628.1PluginAI
- JVMTI Agent 工作原理及核心原始碼分析JVM原始碼
- zabbix安裝agent
- 資料庫agent資料庫
- java agent簡介Java
- Zabbix Agent安裝
- gc/Agent passwd resetGC
- SSH Agent 的作用
- EM Cloud Control 12c OMS 及 OMA 都需要部署Plug-in的原因 - 2Cloud
- EM Cloud Control 12c OMS 及 OMA 都需要部署Plug-in的原因 - 1Cloud
- EM agent無法啟動的原因及分析