Oracle Versions
The Versions screen catalogs the Oracle database versions Nomasx-1 recognises, paired with the licence component each version falls under. One line per (Component, Version). The catalog is used to classify the rows of the Database → Oracle and Licenses → Oracle screens.
Adding a new version here is the prerequisite to scanning a newly installed Oracle release through Nomasx-1.
At a glance
Goal of the view
- Reference the Oracle versions Nomasx-1 supports and their licence component classification.
- One row per (Component, Version) — a single component can carry multiple versions (Enterprise Edition across 19c and 21c, for example).
Columns
| Column | Source | What it tells you |
|---|---|---|
| ID | VER_ID — internal identifier. | Numeric key. |
| Component ID | VER_CPT_ID — links to Pricing → Components. | The Nomasx-1 component the version maps to. |
| Component | CPT_COMPONENT — denormalised label. | Component name shown to the user. |
| Version | VER_VERSION — Oracle major version. | Version string (19c, 21c, 23c, …). |
Edit dialog
Double-click a row to edit the (Component, Version) pair.
| Field | What to enter |
|---|---|
| Component | Drop-down of the Nomasx-1 components. The version is bound to this component. |
| Version | Oracle major version string as returned by the database dictionary (19c, 21c, 23ai, …). |
Tips & best practices
- Add new versions early. A database upgrade reads a new value from the Oracle dictionary — the scan fails to classify unless the version is declared here.
- Use Oracle's official version label (
19c,21c,23ai) to keep alignment with the price book. - Multiple versions for the same component is normal. Keep them all listed to support mixed estates.