Your Implementation Decisions Affect Your Customer’s Obligations
The licensing consequences of an application can extend beyond the application license itself.
A customer may have licensed Oracle Database without licensing every optional feature an application can use. An implementation, upgrade or configuration change can introduce usage outside those entitlements.
The end customer holds the Oracle agreement and remains responsible for its compliance. An application’s role in introducing the usage does not automatically transfer that responsibility to the application provider, and any rights a customer may have against the provider are a separate contractual question that does not resolve the Oracle compliance issue.
For an ISV, this creates a customer relationship issue as well as a technical consideration. An unexpected licensing requirement can complicate deployment decisions, prompt redesign work and undermine confidence in the overall cost of the solution.