This content has been marked as final. Show 6 replies
The issue here is that, before you upgarde your db plugin there are chances that you have applied any patches on your db plugin. In case you have any patches applied on db plugin home explicitely then while doing the plugin upgarde you can run into conflicts so to avoid that you need to apply the MLR patch14546154. In your cases you didnt i guess.. Yes the Readme is old and we have got same feedback just few days back so we are looking into how to get it fixed But the instrucstion in the guide are correct and you need to follow them.
Thank you Akanksha, as always!
I followed the instruction in the README file of the patch 14340329 and applied it successfully to my 126.96.36.199 OMS server, restarted the OMS successfully. However:
1) when I checked the plug-in version on the OMS server (emcli list_plugins_on_server), it shows the Version [revision} for "Oracle Database" is 188.8.131.52.
2) When I checked the plug-in version from the OEM cloud control console (from the plug-in manager page), it also shows the version 184.108.40.206, not 220.127.116.11 [u120804].
Is there any other step I need to take to upgrade the Oracle database plug-ins? Please advise.
Please discard the previous posting. The issue is resolved.
I completed my upgrade to 18.104.22.168 and was able to deploy [u120804) to my OMS.
On the plug-ins page --> Databases --> Oracle Databases I still show the [u120804] next to latest available, latest downloaded, on management server.
I understood that the [u999999] notation means that something needs to be applied, or do I have that wrong?
The column "Management Agent with Plug-in" shows 11, and when I try to deploy to a Management Agent I can't pick any hosts.
So maybe I'm okay, but I'm unclear.
Does anyone have any information on what this should look like?