Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
oracle_grid_cloud_control_offline_update [2019/12/11 16:21] – created andonovj | oracle_grid_cloud_control_offline_update [2019/12/12 23:36] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 7: | Line 7: | ||
======Offline====== | ======Offline====== | ||
- | During offline update, you have to upload the patch to both: | + | Since oracle goes backwards to common sense. In 12c+ we have to upload the latest catalog (that is latest versions of agents, plugins and so on) to the OMS. |
- | * OMS Host | + | It is important to mention that the catalog doesn' |
- | * Target system | + | |
+ | So let's update the catalog: | ||
+ | |||
+ | =====Catalog Update===== | ||
I spent A LOT OF TIME to find the location to download the files, but in nutshell you have to download the latest update from: | I spent A LOT OF TIME to find the location to download the files, but in nutshell you have to download the latest update from: | ||
https:// | https:// | ||
Line 17: | Line 19: | ||
That link can be found in: | That link can be found in: | ||
+ | |||
https:// | https:// | ||
- | Once upload, we have upload the archive in the OMS as follows: | + | After you upload the file to the OMS Host you can upload it to the OMS itself: |
<sxh bash> | <sxh bash> | ||
Line 62: | Line 64: | ||
</ | </ | ||
- | This update | + | After the catalog has been updated we can download the software itself. In our case, we will manually upload the agent. |
+ | The upload of the agent is used to distribute that agent centrally to other hosts. | ||
+ | |||
+ | In our case we will upload teh SQL Server Agent. | ||
+ | |||
+ | =====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=/ | ||
+ | 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]$ | ||
+ | </ | ||
+ | |||
+ | Since we are doing it, let's do also plugin: | ||
+ | |||
+ | =====Plugin Update===== | ||
+ | Once we update the catalog, navigate to oms: | ||
+ | |||
+ | * Settings -> Extensability -> Self Update | ||
+ | * Self Update -> Plugins -> SQL Server -> Download | ||
+ | |||
+ | Once you press the Download, the OMS will show you the following message: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | After you download the file and upload it on the OMS server, we have to upload it to OMS as instructed: | ||
+ | |||
+ | <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 ~]$ | ||
+ | [oracle@tbp-cx-oms01 OMS_Uploads]$ emcli import_update -omslocal -file=/ | ||
+ | Processing update: Plug-in - Enterprise Manager for Microsoft SQL Server | ||
+ | Successfully uploaded the update to Enterprise Manager. Use the Self Update Console to manage this update. | ||
+ | [oracle@tbp-cx-oms01 OMS_Uploads]$ | ||
+ | </ | ||
+ | |||
+ | ======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 |