Pre-12+ OCM Collectors to Be Decommissioned Summer of 2015
(Doc ID 1986521.1)
Last updated on OCTOBER 01, 2015
Applies to:Oracle Configuration Manager - Version 10.3.8 to 18.104.22.168.0 [Release 10.3 to 12]
Information in this document applies to any platform.
All Pre-12+ OCM Collectors to Be Decommissioned
Back in November 2014, we upgraded our CCR server to a new generation Exadata Database to support the increasing flows of configuration data coming in from our customers. As part of this configuration change and not to disturb existing customers using older OCM Collectors, we left the door still open albeit knowing that one day this door would need to get closed. That day will be coming sometime in the Summer 2015. This proactive announcement is to allow you to make any nessary changes and/or clear any required security checks you may have in order to install/configure new software.
The existing adapter which allows all pre-12.x Collectors will no longer work. This will impact a small percentage of customers and equates to approximately 4.5% of existing collections today. The Old collector (connected or disconnected) uploads from older collectors will fail after this change.
We do understand that many Oracle Products contain the OCM Collector as part of their Installation media. For those cases, even though the Collector can be a pre-12.x version, it will automatically upgrade itself as part of its normal operation as long as you have auto-update enabled (default behavior).
Here are some OCM common use cases to watch out for:
- If for some Internal business reasons the autoUpdate flag is set as "FALSE", the OCM Client will not upgrade automatically. Therefore, any pre-12.x collector will fail to upload and the following error message will get thrown:
"Mandatory updates available. Please execute emCCR getupdates to download/apply the updates. Collection and upload failed."
So, as the message explains, the OCM Collector can be manually upgraded to the latest release using the "emCCR getupdates" command.
- For those who are not connected to the Internet directly and make use of Disconnected mode uploads (via the ocmconfig.jar file), a 12.x OCM Collector will also have to be used. If not, then a message will be thrown :
“Mandatory packages are available for the source collector"
This is an indication that an ocmconfig.jar file generated from a pre-12.x Collector is being used and getting rejected by our Servers during upload.
Here are some Harvester common use cases to watch out for:
- In the pre-12c of CloudControl , we create the XML files as part of the Harvester job itself while files are uploaded by the OCM collector located under the OMS Oracle_Home location. Therefore, we will see no error with the Harvester job, but will see errors in the OCM collector as already discussed under the OCM common use cases section of this note.
- As of the 12.+ Harvester, we upload the harvested files directly from EM. In this case, the harvester job logs will show failures with harvester upload error represented by a ‘410’ error code. The Oracle Backend CCR Server is responsible for sending this error after determining a pre-12.x collector is being used. This is a standard HTTP error response which means that the resource is no longer available.
Oracle Products which contain OCM
- OCM is shipped with many Oracle products. There may be some products which still contain the older version of OCM. i.e pre 12.x. In these cases where an end user cannot force the auto-update feature to False as we can in an OCM standalone scenario, there will be a workaround implemented where it will send a request to our Content Server checking for any package updates. All this will be transparent to the end-user.
Recommendation is to download and use the latest OCM Collector for your environment. There are 2 ways to get the latest version. Either pull down the Collector via the My Oracle Support -> Collector Tab or, use Patch 5567658 under the My Oracle Support Patches & Updates Tab -> Simple Search
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|All Pre-12+ OCM Collectors to Be Decommissioned|
|Here are some OCM common use cases to watch out for:|
|Here are some Harvester common use cases to watch out for:|
|Oracle Products which contain OCM|