Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
oracle_grid_cloud_control_offline_update [2019/12/12 10:43] andonovjoracle_grid_cloud_control_offline_update [2019/12/12 23:36] (current) – external edit 127.0.0.1
Line 68: Line 68:
  
 In our case we will upload teh SQL Server Agent. In our case we will upload teh SQL Server Agent.
- 
  
 =====Agent Update===== =====Agent Update=====
 +The agents are usually big files compared to the plugins. For example the windows plugin is ~600 MBs
 +
 +<sxh bash>
 +[oracle@tbp-cx-oms01 ~]$ emcli login -username=sysman
 +Enter password :
 +Login successful
 +[oracle@tbp-cx-oms01 ~]$ emcli sync
 +Synchronized successfully
 +[oracle@tbp-cx-oms01 oradata]$ emcli import_update -omslocal -file=/app/oradata/p28239183_112000_Generic.zip
 +Processing update: Agent Software - Agent Software (13.3.0.0.0) for Microsoft Windows x64 (64-bit)
 +Successfully uploaded the update to Enterprise Manager. Use the Self Update Console to manage this update.
 +[oracle@tbp-cx-oms01 oradata]$
 +</sxh>
 +
 +Since we are doing it, let's do also plugin:
 +
 +=====Plugin Update=====
 Once we update the catalog, navigate to oms: Once we update the catalog, navigate to oms:
  
Line 95: Line 111:
 [oracle@tbp-cx-oms01 OMS_Uploads]$ [oracle@tbp-cx-oms01 OMS_Uploads]$
 </sxh> </sxh>
 +
 +======Deployment======
 +After an agent or plugin has been uploaded, it has to be deployed on the OMS.
 +This is done using the following steps:
 +
 +  * Settings -> Extensability -> Self Update
 +  * Self Update -> Navigate to the Product -> Deploy
  • oracle_grid_cloud_control_offline_update.1576147395.txt.gz
  • Last modified: 2019/12/12 18:43
  • (external edit)