Skip to content

DESCRIPTION.md

Latest commit

 

History

History
27 lines (21 loc) · 1.46 KB

DESCRIPTION.md

File metadata and controls

27 lines (21 loc) · 1.46 KB

Executive Summary

The DBA Feature Usage Statistics report is a critical compliance tool. It queries the internal Oracle usage tracking to see which database features have been used. This is the same data that Oracle LMS (License Management Services) uses during an audit. It helps organizations avoid unexpected bills for expensive options like "Partitioning", "Advanced Compression", or "Diagnostics Pack".

Business Challenge

  • Audit Defense: "Oracle is auditing us. Are we compliant with our contract?"
  • Cost Avoidance: "Did a developer accidentally use the 'Advanced Security' option in the new code?"
  • License Optimization: "We are paying for 'OLAP', but are we actually using it?"

Solution

This report queries DBA_FEATURE_USAGE_STATISTICS.

Key Features:

  • Feature Name: The specific option (e.g., "Automatic Workload Repository").
  • Detected Usages: How many times it was used.
  • Last Usage Date: When it was last triggered.
  • Currently Used: Boolean flag indicating active usage.

Architecture

The report queries DBA_FEATURE_USAGE_STATISTICS.

Key Tables:

  • DBA_FEATURE_USAGE_STATISTICS: The system-maintained usage log.

Impact

  • Financial Risk Reduction: Prevents multi-million dollar non-compliance fines.
  • Governance: Enforces internal policies regarding which features developers are allowed to use.
  • Contract Negotiation: Provides data to negotiate better terms during license renewals.