P6 EPPM bundles Oracle Database, WebLogic, and WebCenter under restricted-use grants that live only in the ordering document and are invisible in the software. This guide shows exactly where usage drifts beyond the restriction, what the repricing costs at Enterprise Edition list, and the moves that keep you defensible.
P6 EPPM bundles Oracle Database, WebLogic, and WebCenter under restricted-use grants that live only in the ordering document and are invisible in the software. This guide shows exactly where usage drifts beyond the restriction, what the repricing costs at Enterprise Edition list, and the moves that keep you defensible.
When you buy Primavera P6 EPPM you receive more than the application. Oracle bundles a set of technology components (Oracle Database, WebLogic Server, and WebCenter Content) under what Oracle calls restricted-use or Application Specific Full Use (ASFU) licenses. The defining trait, confirmed across Oracle's own licensing documentation and by multiple licensing advisors, is that the software is technically identical to the full-use product. Full Use and ASFU ship the same binary. The only difference is contractual: Full Use permits any application, ASFU permits one named third-party application only.
That distinction is where the money and the risk both sit. The restriction buys you a substantial discount (ASFU discounts on Oracle Database Enterprise Edition typically run 50 to 80 percent off Full Use list, per Redress Compliance analysis), but it confines the database to running with or through P6 EPPM and nothing else. Nothing in the software enforces this. There is no feature flag, no error message, no license key that trips when you cross the line. The restriction exists only in the ordering document, and usage drifts beyond it silently.
Full Use and ASFU are the same binary. The only thing standing between your discounted grant and a full-price audit finding is contract language nobody in operations can see.
The consequence is blunt. The moment you use that database for anything other than P6 EPPM, you have breached the grant, and Oracle's remedy at audit is a full-use license purchase at standard list price. In our own review work (roughly 30 to 40 Oracle license reviews and audit defenses across 2024 and 2025) restricted-use grants were among the most common silent failure points. Restricted components drifted into standalone use within two to four years of purchase in most estates, and repricing of the drifted components ran three to five times the original restricted-use spend. For a broader map of the stack, see the pillar on Oracle Construction and Engineering licensing across Primavera Unifier, Aconex, and P6 EPPM.
The P6 EPPM Licensing Information Manual (current version 25, published December 12, 2025) is explicit about what ships restricted and where each restriction breaks. There are three components that matter, and each has a documented trigger for full-use exposure.
The WebLogic Server grant included with P6 EPPM is Standard Edition only. Per Oracle's manual, it may run only in a WebLogic Server Standard Edition instance, no other web applications may be deployed in that instance, and it is restricted to Standard Edition features only. Clustering, Coherence, and EJBs are explicitly excluded. Oracle's own worded example: if a customer wishes to cluster their P6 EPPM instance, that triggers a full-use license of WebLogic Server Enterprise Edition (or WebLogic Suite for Oracle Applications). This is the single most common architectural trap, because clustering for high availability is exactly what a mature enterprise deployment tends to add over time.
WebCenter Content is valid only for workspaces or folders built from P6 EPPM and repositories storing P6 EPPM documents. Per the manual, creating any repository, folder, or workspace manually outside of Primavera applications triggers full-use. Oracle's own example is a new departmental workspace or folder. This one drifts through ordinary administrative convenience: a content administrator sets up a folder for a different team, and the restriction is breached without anyone touching the licensing file.
The database is the largest exposure by dollar value and the hardest to police, because a database is a shared resource that other tools naturally want to read from and write to. The grant is dedicated to P6 EPPM. Any other workload, even something as small as an external report or a data export tool, breaches it. Two additional traps sit on top of the base database grant, and both are documented by Oracle itself, which makes them particularly dangerous.
This is the sharpest edge in the entire EPPM stack. When synchronizing P6 EPPM with Oracle Prime Projects, Oracle's own install wizard directs you to select the option labeled "Use Oracle Database Partitioning Option (separately licensed)" to improve synchronization performance. Separately, Oracle publishes a guide titled "Partitioning Oracle Database Tables for P6 EPPM Schema" that walks a DBA through manual table partitioning after the database is set up.
Here is the problem. Partitioning is a separately-licensed Enterprise Edition option. It is not covered by the base P6 EPPM database grant. Oracle documents the step, the install wizard suggests the step, and the guide describes how to perform the step, but nowhere in that flow does the base license actually authorize it. A DBA following Oracle's published instructions in good faith can enable a paid EE option and create direct license exposure. This pattern (Oracle documenting or auto-enabling a paid feature that the base grant does not cover) is not unique to Primavera; we see the same mechanics in the Cloud Management Pack that self-enables inside Enterprise Manager.
Oracle's install wizard tells your DBA to enable Partitioning. Oracle's base license does not permit it. Following the vendor's own instructions can hand the vendor an audit finding.
The buyer move is defensive documentation. Before any DBA touches partitioning, confirm in writing which of your ordering documents (if any) include the Partitioning option as full-use, and if it is not there, treat the wizard prompt as a paid decision that requires a purchase order, not a checkbox. If you have already followed the wizard, this is a remediation item, not a shrug.
The P6 EPPM manual also defines "Access Points" and attaches a licensing obligation to them. Developers or users who are not already licensed for P6 EPPM and who access the application through Access Points must be licensed for the P6 EPPM Web Services program. Access Points explicitly include third-party, Oracle, or custom versions of interfaces, APIs, web services, and database links.
This closes a route many buyers assume is free. The logic runs: if a reporting tool or integration reads P6 data through the database directly rather than through a named user session, that reader still consumes a licensable access path. Combined with the ASFU database restriction, the two rules reinforce each other. A custom report or integration that reads directly from the P6 EPPM database breaches the ASFU grant (non-P6 use of the database) and can also trigger a Web Services program requirement. This is the same counting discipline that applies to human users, covered in our guide to Primavera P6 license compliance and how contractors, read-only reviewers, and API service accounts all count.
The drift triggers are predictable. Across our review work the recurring three are: custom reports built outside the Primavera application that read directly from the database, third-party integration tools writing into the database, and new use cases adopted after the original deployment (another team, another module, another report). None of these look like a licensing event to the people doing them. All of them are.
The cost of breach is not the discounted ASFU rate. It is full Enterprise Edition list plus support plus, frequently, the paid options. The table below sets out the list numbers that define your exposure ceiling. These are Oracle list figures gathered from published pricing sources during 2025 and 2026; your negotiated position may differ, but list is what Oracle quotes first in an audit settlement.
| Item | List price | Basis | Source period |
|---|---|---|---|
| Oracle Database Enterprise Edition | $47,500 | per Processor | Feb 2026 |
| Standard Edition 2 (SE2) | $17,500 | per Processor | Feb 2026 |
| Diagnostics Pack | $7,500 | per Processor | 2026 |
| Tuning Pack | $5,000 | per Processor | 2026 |
| Annual support (any of the above) | 22% of net license | per year, rarely falls | 2025-2026 |
| Partitioning / RAC / Diagnostics | EE-only options | common audit findings | 2025-2026 |
The scale becomes clear on a real server. A 16-core Intel server (0.5 core factor) running Enterprise Edition carries a list license cost of $380,000 plus $83,600 annual support. A two-socket server with 22 cores per socket at 0.5 core factor requires 22 processor licenses, which is $1,045,000 at list, versus SE2 on the same socket-based, two-socket-capped server at just 2 processor licenses, which is $35,000. That gap (roughly $1,010,000 on one server) is the difference between staying inside the restriction and drifting out of it. Where you have control over cores, the ability to cut the licensable count matters enormously; see Oracle-approved hard partitioning and the evidence that holds at audit.
On a 44-core two-socket server the drift from restricted-use to full Enterprise Edition is roughly a million dollars at list. That is the price of one unauthorized report.
Two contractual facts about ASFU deserve attention because they shift risk toward the buyer. First, organizations using Oracle software this way are required to join the Oracle Partner Network and maintain membership for the duration of the ASFU agreement, agreeing to the OPN Master Distribution Agreement and its ASFU Program Distribution addendum. Second, and more importantly, the onus of compliance remains with the end-user, not the ISV. You cannot point at Oracle or a reseller and say the restriction was their responsibility to enforce.
This matters because the restriction is contractually yours to police while being technically invisible. That combination is precisely why audit findings are so expensive here. Oracle audits routinely uncover ASFU misuse, and the standard remedy is a full-price Full Use purchase. For what an examiner actually looks at across the estate, see our guide to what an Oracle audit examines across the Primavera and Unifier estate.
Treat this as a documentation and containment exercise, not a technology project. The steps below are ordered by impact.
The core discipline is simple to state and hard to sustain: the Oracle environment under P6 EPPM must remain dedicated to P6 EPPM. Because the software will never tell you when you cross the line, the control has to be procedural. Put the restricted-use terms in front of your DBAs, integration architects, and content administrators, and make any deviation a purchase decision that goes through licensing review. That single governance step is cheaper than any single audit finding described above.
It includes a restricted-use (ASFU) Oracle Database license, not a free-standing one. The database may only be used with or through P6 EPPM. Any other workload, including an external report or a data export tool, breaches the grant and exposes you to full Enterprise Edition list pricing at audit.
No. Full Use and ASFU ship the identical Oracle binary with identical technical features. The only difference is contractual: ASFU confines the database to one named application. Because nothing in the software enforces this, usage drifts beyond the restriction silently, which is exactly why it is such a common and expensive audit finding.
Not without a separate license. Oracle's Prime sync install wizard prompts you to select the Partitioning option and labels it "separately licensed," and Oracle publishes a guide for partitioning the P6 schema. Partitioning is a paid Enterprise Edition option that the base P6 EPPM grant does not cover. Following the wizard without a full-use Partitioning license creates direct exposure.
The bundled WebLogic grant is Standard Edition only and excludes clustering, Coherence, and EJBs. Per Oracle's own example, clustering your P6 EPPM instance triggers a full-use WebLogic Server Enterprise Edition (or WebLogic Suite) license. Deploying any other web application into that WebLogic instance also breaches the restriction.
The end-user. Under ASFU terms the onus of compliance sits entirely with the customer, not the ISV or reseller. You also typically must join and maintain Oracle Partner Network membership under the ASFU Program Distribution addendum for the life of the agreement.
Repricing runs at full Enterprise Edition list. One EE processor license is $47,500 with 22 percent annual support, before options like Diagnostics ($7,500) and Tuning ($5,000). On a 44-core two-socket server at 0.5 core factor the drift from restricted-use to full EE is roughly $1,045,000 at list versus $35,000 for SE2. In our review work, repricing of drifted components ran three to five times the original restricted-use spend.
Oracle Primavera P6 compliance. Named user counting, EPS access, the contractor trap, and the audit defense framework.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
