Understanding The Oracle Database Target in My Oracle Support and How it Gets there via OCM
(Doc ID 1449145.1)
Last updated on OCTOBER 31, 2019
Oracle Configuration Manager - Version 10.3.6.0.0 and later Information in this document applies to any platform.
This document will explain the logic flow that takes place when a Database target is being collected by the standalone Oracle Configuration Manager(OCM) collector.
Why is this important?
It is important to ensure that collections for Oracle Database targets are discovered and consistently updated in My Oracle Support(MOS) so that users can validate, review, and perform futher proactive actions in MOS. For example, gathering patch advice, creating Service Requests, and any other administrative type functions current available in MOS relating to a Database Target.
As an OCM and MOS user, it is equally important to understand the process of how a Database target gets populated into MOS and in some cases, how to troubleshoot when a Database Target information either goes 'stale' (LAST_COLLECTED column not updated) in MOS or simply no longer appears as a Target altogether.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!