Skip to main content

Oracle Features

The Features screen catalogs the Oracle features Nomasx-1 monitors via DBA_FEATURE_USAGE_STATISTICS. One line per (Component, Feature). The catalog maps each feature to the licence component its usage would consume — a critical input of the Oracle LMS audit, where unused features may not trigger compliance even if installed.

At a glance​

Nomasx-1 · Settings · Oracle · FeaturesIDCOMPONENTFEATUREDESCRIPTION1Diagnostic PackAWR ReportAutomatic Workload Repository2Tuning PackSQL Tuning AdvisorSQL Tuning Advisor

Goal of the view​

  • Translate Oracle feature labels to the Nomasx-1 component model.
  • Drive the Database → Oracle feature detection. A feature recorded as used in DBA_FEATURE_USAGE_STATISTICS is mapped to its component on the licence reports.

Columns​

ColumnSourceWhat it tells you
IDFEA_ID — internal identifier.Numeric key.
Component IDFEA_CPT_ID — links to Pricing → Components.The component the feature belongs to.
FeatureFEA_FEATURES — Oracle feature name.Label as returned by DBA_FEATURE_USAGE_STATISTICS.
DescriptionFEA_DESCRIPTION — text.Friendly description for non-DBA audiences.

Edit dialog​

Double-click a row to bind a feature to a Nomasx-1 component.

Edit Oracle featureComponentDiagnostic Pack ▾FeatureAWR ReportDescriptionAutomatic Workload Repository
FieldWhat to enter
ComponentDrop-down of Nomasx-1 components. The feature counts against this component.
FeatureFeature name exactly as returned by DBA_FEATURE_USAGE_STATISTICS.
DescriptionPlain-language label for non-DBA readers.

Tips & best practices​

  • Re-import the feature dictionary after every major Oracle release — new features appear with each version.
  • A feature usage detected on a non-subscribed component is the strongest type of audit finding. Aim for zero on production instances.
  • Use the Description field to record what the feature does in plain language — easier to discuss with the business than the raw Oracle name.