Skip to main content

Oracle

The Oracle licence screen replicates the Database → Oracle inventory, restricted to applications whose database is Oracle (APPS_DBTYPE = 'ORACLE') and enriched with the application name. One line per (Application, Product / Instance).

It is the same data as the database properties page but framed as a licence deliverable: the data set Oracle's LMS auditor will ask for during the annual review.

At a glance​

Nomasx-1 · Licenses · OracleAPPPRODUCTVERSIONHOSTINSTANCECPUACTIVETOTALTECHSIZE GB12Enterprise Edition19.21.0db-prd-jde-01PRDJDE16142218141 24012Diagnostic Pack19.21.0db-prd-jde-01PRDJDE16142218141 24012Advanced Compression19.21.0db-prd-jde-01PRDJDE16142218141 240

Goal of the view​

Same role as Database → Oracle, framed for the licensing review:

  • Per-application slice. The connector only returns rows for applications whose database is Oracle — the licence team rarely needs the others.
  • NUP-ready figures. Active, Total, Technical users — the three counts that drive the named-user plus calculation.
  • Audit pack starting point. Sort by Hostname to discuss server by server with the LMS auditor.

Columns​

ColumnSourceWhat it tells you
Application IDAPPS_ID — application identifier.The connected Oracle-backed application.
ProductORAP_PRODUCT — product / pack name.What is licensed (Enterprise Edition, packs, options).
Full versionORAP_FULL_VERSION — full version string.Patch level.
VersionORAP_VERSION — major version.Oracle major version.
HostnameORAP_HOSTNAME — host.Server.
InstanceORAP_NAME — instance.Oracle instance / SID.
Instances countORAP_COUNT_INST — instance count.RAC distinguisher.
CPUORAP_CPU — CPU core count.Processor-licensing input.
Active usersORAP_ACTIVE_USERS — count.Active named accounts.
Total usersORAP_TOTAL_USERS — count.All named accounts.
Technical usersORAP_TECHNICAL_USERS — count.Accounts tagged technical in Nomasx-1.
PackORAP_PACK — pack code. Hidden.Internal — drives the licence compliance computation.
Size GBORAP_SIZE_GB — total size.Storage footprint.

Tips & best practices​

  • Export the grid as the Oracle LMS data sheet — the columns above match the standard collection form auditors use.
  • Filter on Product containing "Pack" to highlight the heavy packs first. They are the easiest line items to challenge during the audit.
  • The same row is not duplicated by Data Guard standby instances — Nomasx-1 reads them once. If the audit expects to count standbys, build the row count manually.
  • Cross-reference with Subscribed Licenses to know whether a product surfaced here is actually entitled.