Oracle
The Oracle licence screen lists, for each connected Oracle database, every Oracle licence component checked by the Nomasx-1 collection scripts, together with a green / red indicator telling whether the component is required on the instance — that is, whether the collected usage matches what Oracle considers a licensable feature.
The aim of the page is to identify the licences the database needs, so you can compare them with what is actually subscribed in Subscribed Licenses and close the gap on either side — drop a licence that nothing uses, or purchase a licence that is being used without coverage.
At a glance
Goal of the view
For each Oracle database:
- What needs a licence, what doesn't. Each row is a known Oracle licence component. A green dot in Required means the collection scripts detected usage on the instance — a licence is needed. A red dot means the component is installed but not in use, or not installed at all — no licence to declare.
- Cover the whole catalogue. The list includes the Enterprise Edition, the Database Enterprise Management packs (Diagnostics, Tuning), the Enterprise Edition options (Active Data Guard, Partitioning, Advanced Compression, Database In-Memory, RAC…) and the other Oracle products (Audit Vault, Spatial, …). Nothing is silently dropped.
- One source for the compliance conversation. The same data feeds the renewal discussion with Oracle and the procurement reconciliation — no parallel spreadsheet to maintain.
Columns
| Column | Source | What it tells you |
|---|---|---|
| Category | CPT_CATEGORY — licence family. | The Oracle catalogue family the component belongs to (Database, Enterprise Edition Options, Database Enterprise Management, Other Products…). |
| Component | CPT_COMPONENT — component name. | The licence option itself — Enterprise Edition, Partitioning, Diagnostics Pack, Advanced Security, … |
| Required | ORAL_USED — Y / N. Displayed as a green / red dot. | Green: usage detected, the licence is needed on this database. Red: no usage detected, no licence to declare. |
| App | APPS_NAME — application name. | The application that runs on the database. |
Tips & best practices
- Sort by Required descending to bring all the green-dot lines to the top — the list to subscribe.
- Group by Category in the Group control to read the required components by Oracle catalogue family — the way the Oracle price book is structured.
- Filter on
Componentcontaining "Pack" to focus on the heavy management packs (Diagnostics, Tuning) — the most expensive lines in a typical Oracle bill. - Cross-reference with Subscribed Licenses to check that every green-dot component is covered by an active CSI. A green dot with no subscription is the gap to close.