Skip to main content
    ISV Program

    ISV Customer Story · Semiconductor Manufacturer

    Protect Your Customers From Unexpected Oracle Licensing Exposure

    Incorporate independent licensing guidance into your software offering.

    Your customers buy your software to improve their operations. They may also depend on you to understand how its implementation affects their existing technology environment—including licensing requirements they may never think to ask about.

    For applications running on Oracle, a database design or configuration choice can introduce a separately licensed feature. The application may perform exactly as intended while creating a compliance gap for the customer.

    Two incidents at a semiconductor manufacturer demonstrate why licensing guidance deserves a place in the software offering.

    When Factory Software Introduces a Licensing Requirement

    The manufacturer relied on third-party applications to support factory automation and manufacturing operations.

    Incident 1 · Material movement software

    Software connecting production systems with automated transport and storage equipment. LicenseFortress identified nine application tables that appeared to have been created with Oracle Partitioning enabled. The manufacturer did not hold the required Partitioning licenses.

    Incident 2 · Manufacturing operations software

    Unlicensed Partitioning across three database instances in an environment associated with software that organizes production and equipment data to help manufacturers understand factory conditions and improve production flow.

    Each incident would have required the same processor licenses and support

    Taken on its own, either finding would have required the manufacturer to purchase 24 Oracle Partitioning processor licenses. Every processor license also carries support, so both incidents point to one purchase — processor licenses plus support.

    Oracle Partitioning processor licenses · 24 processors × $11,500 each
    $276,000
    Oracle support on those processors · 24 processors × $2,530 each
    $60,720
    Total recorded contractual exposure · processor license + support, both incidents
    $336,720

    A processor license plus support comes to $14,030 per processor. At that rate, the 24 processors needed come to $336,720 — the amount recorded across both incidents, which is why the reports show one figure rather than two.

    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.

    Understand the Dependency Before the Change Reaches Production

    In both incidents, LicenseFortress documented the unlicensed usage, assessed the exposure and identified possible responses:

    Purchasing Partitioning licenses
    Dropping the affected tables
    Implementing an alternative table-and-view approach

    The records do not confirm completed remediation. They demonstrate the importance of identifying the issue so the customer can evaluate its options—and earlier review creates an opportunity to examine those choices before an implementation or upgrade reaches production.

    Before an implementation or upgrade is approved, these questions need answers:

    • Which Oracle features will the application use?
    • Are those features covered by our existing entitlements?
    • Will the implementation or upgrade create new database objects or change feature usage?
    • Are alternative configurations available if a feature requires additional licensing?
    • Who will verify licensing assumptions and review subsequent changes?

    Make Licensing Guidance Part of the Customer Experience

    LicenseFortress’ ISV program gives software providers a way to incorporate independent licensing expertise into their offering. Together, we can define a review that examines:

    Implementations

    How the application will operate within the customer’s Oracle environment and which entitlements it assumes.

    Upgrades

    Whether proposed changes introduce additional database features or licensing requirements.

    Configurations

    Whether application settings and database structures align with the customer’s licensed capabilities.

    Depending on the engagement, that guidance can support implementation planning, customer discussions and decisions about alternative configurations. The objective is to identify licensing dependencies while the vendor and customer still have time to make informed choices.

    Strengthen Your Offering With LicenseFortress

    Your team understands the application. Your customer understands its operational needs. LicenseFortress brings an independent licensing perspective to the decisions connecting the two.

    Incorporating that expertise into your software offering helps customers understand the licensing implications of deployment—and helps your team address those questions before they become unexpected exposure.