A patch consists of one or more bug fixes. This metric collects all the bugs fixed within that patch applied on the Oracle home directory.
This metric displays the bug number in the patch. There can be multiple bugs fixed in a patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays a brief description of the bug in the patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the patch number which contains one or more bug fixes. The patch id may be the same for more than one patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the language of the patch. Generally it is "en" (English)
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Unique Patch Identifier. Some patches might have the same patch ID but a different patch identifier. This will be used to issue patch advisories.
|
Data Source
The data is picked up from the inventory.
User Action
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 directory.
This is the internal name of the component installed in Oracle home.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the base version of component installed in Oracle home.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the internal name of the dependent component installed in the same or different Oracle home.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the base version of the dependent component installed in same or different Oracle home.
|
Data Source
The data is picked up from the inventory.
User Action
None.
Every installed component 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.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the base version of component installed in Oracle home.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is install type Name ID.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the install type Description ID.
|
Data Source
The data is picked up from the inventory.
User Action
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 about various files which are affected by the application of this patch to the Oracle home directory.
This metric displays the internal name of the component installed in the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the base version of the component installed in the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the name of a file affected by the patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the patch number which contains one or more bug fixes
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the language of the patch. Generally it is "en" (English).
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the Unique Patch Identifier (UPI). Some patches might have the same patch ID but different patch identifiers. This is used to issue patch advisories.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric collects all the properties which are later used in cloning and provisioning that Oracle home directory.
This is the name of the property used for cloning
|
Data Source
The data is picked up from the inventory.
User Action
None.
An Oracle home installation consists of many components. This metric collects details of all the components installed, including their version and installation date.
This metric displays the internal name of the component installed in the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the base version of component installed in the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the current updated version of the component. The version of the component can be updated by "Patchset Updates" or "Patchsets"
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays a brief description of the component.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the external name of the component.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the location where the component is installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the version of the installer used at the time of installation.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the date and time of the installation.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies where it is a top level component [0/1]. There is at least one top level component in any Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays a list of the languages supported by the component installation.
|
Data Source
The data is picked up from the inventory.
User Action
None.
Earlier versions of the Oracle Universal Installer (OUI) permitted one component within an Oracle home directory to be dependent on another component in another Oracle home directory. This metric collects that dependency information.
This metric category collects all generic properties for an Oracle home directory such as the ARU ID, size of the Oracle home directory or the OUI_ID.
This metric displays the Automated Release Update (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.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the complete path to where the Oracle home directory is installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the middleware home directory (in the case of Oracle Fusion Applications products) and the composite home location (in the case of members of composite homes). A composite home directory is the location where the core and plug-in Oracle home directories are installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric displays the estimated size of Oracle home as in inventory measured in kilobytes.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Oracle home type. Its "O" for OUI-installed Oracle home directories and "W" for Oracle WebLogic home directories.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Central inventory location where the Oracle home directory is registered.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This shows whether this Oracle home directory is clonable. Oracle WebLogic home directories are always clonable. OUI-installed Oracle home directories are clonable only if all the components inside that Oracle home directory are clonable.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies whether this is a Cluster Ready Services (CRS) installation [0/1].
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the operating system group name of the user who installed the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the operating system group ID of the user who installed the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the operating system owner name of the user who installed the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
All the operating system group names to which the user belongs.
|
Data Source
The data is picked up from the inventory.
User Action
None.
All the operating system group IDs to which the user belongs.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the operating system owner ID of the user who installed the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Oracle Base where the Oracle home directories are installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the OUI Oracle Home Globally unique identifier. This is unique across all Oracle product installations.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the readable name of the Oracle home directory.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Patform ID of an Oracle home directory. This was used in releases 10.1 or earlier. This has been replaced with ARU_ID, still useful for older installations.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric collects all the patches which have been applied to the Oracle home directory.
This is a description of a patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the installation time when the patch was installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the OUI installer used for the installation of the patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies whether the patch is an online or offline patch. An online patch is a patch that can be applied to live running database instance.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies if this is a patchset update. Patchset updates are like onoffs, but they can change the minor version of the component
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies whether the patch can be rolled back [0/1].
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the patch number which contains one or more bug fixes. This ID might be the same for more than one patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies the language of the patch. Generally, it is "en" (English).
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the Unique Patch Identifier (UPI). Some patches might have the same patch ID, but different patch identifiers. This will be used to issue patch advisories.
|
Data Source
The data is picked up from the inventory.
User Action
None.
The profile name is used for Oracle Fusion Application patches only.
|
Data Source
The data is picked up from the inventory.
User Action
None.
Oracle Patchset consists of many PS_Patches for each component (also known as Versioned Patch). Patchsets are always cumulative; that is, all the components within the patchset have the incremented 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.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the external name of the patchset.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the OUI installer version used for the installation of the patchset.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the installation time of the patchset.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the inventory location of the patchset.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the minimum OUI installer version to be used for removing the versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the internal name of the patchset.
|
Data Source
The data is picked up from the inventory.
User Action
None.
An Oracle patchset consists of many versioned patches corresponding to various components within that Oracle home directory. 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.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is a brief description of the versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the external name of the versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the path showing where the versioned patch is installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the OUI installer version used at the time of installation.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the time when the versioned patch was installed.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric lists the languages supported by the versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the minimum OUI installer to be used when removing the versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the patchset name which contains this versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the patchset version which contains this versioned patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the versioned patch name (should be the same as the Component Name, on which the Versioned Patch is applied).
|
Data Source
The data is picked up from the inventory.
User Action
None.
A 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.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This is the base version of the component which is being patched.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This exists only in Patchset Updates and corresponds to the version of the component being patched.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies the patch ID number. The patch ID might be the same for more than one patch.
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies the patch language. Generally it iss "en" (English).
|
Data Source
The data is picked up from the inventory.
User Action
None.
This metric specifies the Unique Patch Identifier. Some patches might have the same patch ID but a different patch identifier. This will be used to issue patch advisories.
|
Data Source
The data is picked up from the inventory.
User Action
None.