Oracle® Enterprise Manager Framework, Host, and Services Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25162-03 |
|
|
PDF · Mobi · ePub |
The oracle_home metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.
A patch consists of one or more bug fixes. This metric collects all the bugs fixed within that patch applied on the Oracle Home.
Bug number in the patch. There can be multiple bugs fixed in a patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Patch number which contains one or more bug fixes. The patch id may be the same for more that one patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the language of the patch. Generally its "en" (English)
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Unique Patch Identifier. Some patches may have the same patch ID but different patch identifier. This will be used to issue patch advisories.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
A component within an Oracle Home might be dependent on another component. This metric collects the dependency information between the components within an Oracle Home.
This is the internal name of the component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the base version of component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the internal name of the dependent component installed in the same or different Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the base version of the dependent component installed in same or different Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Home globally unique identifier of the Oracle Home where the dependent component is installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Every component installed has its own install type. This information is created by the product installation and collected by this metric.
This is the internal name of the component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the base version of component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is install type Name ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This metric collects the node information on the nodes that participate in the cluster installation.
Each patch affects one or more components and each component is made up of many files. This metric collects information on various files which are affected by the application of this patch to the Oracle Home.
Internal name of the component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Base version of the component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Name of file affected by Patch
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Patch number which contains one or more bug fixes
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Language of patch. Generally its "en" (English).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Unique Patch Identifier. Some patches may have the same patch id but different patch identifier. This will be used to issue patch advisories.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This metric collects all the properties which are later used in cloning and provisioning that Oracle Home.
An Oracle Home installation consists of many components. This metric collects details of all the components installed, including their version and installation date.
Internal name of the component installed in Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the base version of component installed in Oracle Home
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
The current updated version of the component. The version of the component can be updated by "Patchset Updates" or "Patchsets"
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is a brief description of the component.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the external name of the component.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the location where the component is installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the version of the installer used at the time of installation.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the date and time when the installation was done.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Is that a top level component [0/1]. There is at least one top level component in any Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is a list of the languages supported by the component installation.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Earlier versions of OUI (installer) permitted one component within an Oracle Home to be dependent on another component in another Oracle Home. This metric collects that dependency information.
This metric collects all generic properties for that Oracle Home like ARUID, is Oracle Home clonable?, is the Oracle Home readable? OUI_ID for that Oracle Home.
ARU ID of the Oracle Home installation. This is used to determine the platform and version of Operating System while issuing patch advisories from ARU.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the complete path to where Oracle Home is installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the middleware home (in the case of fusion app products) and composite home location (in the case of members of composite homes). A composite home is the location where the core and plug-in Oracle Homes are installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Estimated size of Oracle Home as in inventory measured in kilobytes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Oracle Home type. Its "O" for OUI installed Oracle Homes and "W" for Weblogic homes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Central inventory location where the Oracle Home is registered.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This shows whether this home is clonable or not. Weblogic Homes are always clonable, OUI installed Oracle Homes are clonable if all the components inside that Oracle Home are clonable.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This shows whether this is a CRS installation [0/1].
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the operating system group name of the user who installed the Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the operating system group ID of the user who installed the Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the operating system owner name of the user who installed the Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
All the operating system group names to which the user belongs.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
All the operating system group IDs to which the user belongs.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the operating system owner ID of the user who installed the Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Oracle Base where Oracle Homes are installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the OUI Oracle Home Globally unique identifier. This is unique across all Oracle Product Installations.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the readable name of Oracle Home.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Patform ID of an Oracle Home. This was used in releases 10.1 or earlier. This has been replaced with ARU_ID, still useful for older installations.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This metric collects all the patches which have been applied to the Oracle Home.
This is a description of a Patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the installation time when the patch was installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the OUI installer used for the installation of the patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Is it a Patchset Update? Patchset Updates are just like onoffs, but they can change the minor version of the component
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This show whether the patch can be rolled back [0/1].
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Patch number which contains one or more bug fixes. This ID may be the same for more than one patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Language of patch. Generally its "en" (English)
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Unique Patch Identifier. Some patches may have the same patch ID, but different patch identifiers. This will be used to issue patch advisories.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
The profile name is only used for fusion app patches
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Oracle Patchset consists of many PS_Patches for each component (also called as Versioned Patch). Patchsets are always cumulative; that is all the components within the patchset have the bumped up version number after the application of that patchset. This metric collects that information.
This is a brief description of the Patchset. A patchset contains one of more versioned patches.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the external name of the Patchset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the OUI installer version used for the installation of the patchset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the installation time of the Patchset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the inventory location of the patchset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the minimum OUI installer version to be used for deinstalling the versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
An Oracle Patchset consists of many Versioned Patches corresponding to various components within that Oracle Home. This metric collects information of all the components affected by the patchset and their versions.
This is the base component version, on which the Versioned Patch is applied.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is a brief description of the versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the external name of the versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the path showing where the versioned patch is installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the OUI installer version used at the time of installation.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the time when the versioned patch was installed.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This lists the languages supported by the versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the minimum OUI installer to be used in deinstalling the versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the patchset name which contains this versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the patchset version which contains this versioned patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the versioned patch name (Should be same as the Component Name, on which the Versioned Patch is applied).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
Patch consists of many bug fixes, each of which will have fixes for various components. This metric collects all the information of various components which are fixed by that patch.
This is the internal name of the component which is being patched by the One Off.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the base version of the component which is being patched.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This exists only in Patchset Updates and corresponds to the version of the component being patched.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the patch ID number. The patch ID may be the same for more than one patch.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the patch language. Generally its "en" (English).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This is the Unique Patch Identifier. Some patches may have the same patch ID but different patch identifier. This will be used to issue patch advisories.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.
This exists only in Patchset Updates (PSU) and corresponds to the new version of the component after the PSU has been applied.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The data is picked up from the inventory.
None.