Skip to main content

Oracle

The Oracle screen lists the properties of every Oracle database used by a connected application. One line per (Application, Product / Instance). The data is collected by the Nomasx-1 connector through standard V$ views.

It is the inventory required for the Oracle licence audit — and the input for the Licenses → Oracle compliance report.

At a glance​

Nomasx-1 · Database · OracleAPPPRODUCTVERSIONHOSTINSTANCECPUACTIVETOTALTECHDGSIZE GB12Enterprise Edition19.21.0db-prd-jde-01PRDJDE1614221814Y1 24012Diagnostic Pack19.21.0db-prd-jde-01PRDJDE1614221814Y1 24012Advanced Compression19.21.0db-prd-jde-01PRDJDE1614221814Y1 240

Goal of the view​

For each Oracle database backing a connected application:

  • Inventory of installed products. Database edition, packs, options — exactly what an Oracle LMS audit asks for.
  • Sizing data. CPU count + active vs total users + technical users + storage size — the inputs of the Oracle licence calculation, whether NUP (named-user plus) or processor-based.
  • Data Guard footprint. The DG flag tells whether the instance participates in a Data Guard configuration — relevant for failover sizing and licence dual-counting questions.

Columns​

ColumnSourceWhat it tells you
Application IDORAP_APPS_ID — application identifier.The connected application.
ProductORAP_PRODUCT — product / pack / option name.What is installed (Enterprise Edition, Diagnostic Pack, Advanced Compression, …).
Full versionORAP_FULL_VERSION — full version string.Exact installed patch level.
VersionORAP_VERSION — major version.Major version (19c, 21c, …).
HostnameORAP_HOSTNAME — host.Server hosting the instance.
InstanceORAP_NAME — instance name.Oracle SID / DB unique name.
Instances countORAP_COUNT_INST — number of instances.RAC distinguishes from single-instance.
CPUORAP_CPU — CPU core count.Used for processor-based licensing.
Active usersORAP_ACTIVE_USERS — count.Active named accounts on the database.
Total usersORAP_TOTAL_USERS — count.All named accounts on the database.
Technical usersORAP_TECHNICAL_USERS — count derived from USRP_TECHNICAL.Users flagged as technical in Nomasx-1 — excluded from NUP.
PackORAP_PACK — pack code. Hidden.Used by the licence compliance computation.
Data GuardORAP_DG — boolean.Whether the instance is part of a Data Guard configuration.
Size GBORAP_SIZE_GB — total size.Storage footprint.

Tips & best practices​

  • Filter on Product containing "Pack" to extract the management packs in use — the heaviest audit topic.
  • Cross-check Active users against Total users — a large gap means dormant accounts on the database itself, separate from the source-system accounts.
  • The Technical users column lets you compute a "real human" NUP figure when negotiating the renewal.
  • A Data Guard configuration doubles the licence requirement unless the standby is configured as a passive failover — clarify with Oracle.