License consumption for stand-by Oracle databases
Starting with this release, Oracle inventory has been enhanced to recognize primary/stand-by (also referred to as active/passive) database clusters, improving licensing accuracy and audit readiness. By linking cluster nodes as logical pairs, the system prevents false exceptions and ensures consistent reporting of options and packs across both nodes.
Previously, when reporting on Oracle instances, the primary node correctly showed a running database instance, while the stand-by node detected the database configuration but not a running instance. This resulted in an exception stating that no instance was running at the time of inventory collection.
With this enhancement, IT Asset Management now stores cluster pair information in the database. After reconciliation, the primary node continues to report a running instance, and the stand-by node is no longer flagged as missing a running Oracle instance because it is recognized as part of an primary/stand-by cluster pair.
For licensing purposes, Oracle databases can have one or more standby databases for a running database. If you have a standby database, you must license all Oracle options and packs running on the primary database for the standby database as well. Previously, scans on passive databases did not show all instances, which led to under-calculated consumption.
- If an option is used on the stand-by database but not on the primary database, it is still counted for consumption.
- If an option is used on the primary database but not on the stand-by database, it is counted for consumption.
- If an option is used on both, nothing changes.
- If an option is used on neither, nothing changes.
IT Asset Management (Cloud)
Current