Restricted-Use Licences in Primavera P6: What You Need to Know

What Is a Restricted-Use Licence?

Oracle's licensing model uses "restricted-use licences" to include supporting technology components alongside a primary application product at no additional cost. The concept is straightforward in principle: when you licence Primavera P6 EPPM, you receive the right to use certain Oracle technology stack components — the database, the application server, the reporting tool — but only for the purpose of running Primavera P6. You do not receive a general-purpose licence to those components. You receive a restricted-use licence that is bounded entirely by the P6 application.

This distinction matters because Oracle Database Enterprise Edition, Oracle WebLogic Server, and Oracle BI Publisher are expensive enterprise products in their own right. A full Oracle Database Enterprise Edition licence costs tens of thousands of dollars per processor core. WebLogic Server Standard Edition is similarly priced. Were Oracle to bundle general-purpose licences for these components with every P6 EPPM deployment, it would be giving away hundreds of thousands of dollars of licence value per customer. It does not. The restricted-use licence grants access to these components only within a precisely defined functional boundary, and using them beyond that boundary is a licensing violation that triggers the requirement to purchase full-use licences retroactively.

The formal definition in Oracle's licensing documentation confirms this unambiguously: the included licences are "restricted to use solely with Oracle Primavera P6 EPPM." That phrase — solely with — is the critical qualifier. It excludes any use case that extends beyond the P6 application environment, regardless of how minor or incidental the extension might appear.

The Oracle Database Restricted-Use Boundary

Oracle Primavera P6 EPPM includes a restricted-use licence for Oracle Database. In practice, this means the P6 installation can create and use its own database schemas to store Primavera project management data. The Oracle Database instance provided with P6 is licensed for this purpose — and no other.

The boundary violation that organisations most commonly commit is creating additional schemas or tables on the Primavera database instance for non-P6 applications. This happens through several paths. DBAs who manage the P6 database server sometimes use it for convenience — storing configuration data for related applications, creating reporting schemas that aggregate P6 data with data from other systems, or deploying small internal tools that happen to have database connectivity. Each of these uses constitutes a breach of the restricted-use licence terms.

The financial implication is substantial. If Oracle's LMS (Licence Management Services) team identifies non-P6 data or schemas in the Oracle Database instance bundled with P6, the organisation must purchase full Oracle Database Enterprise Edition licences for all processors on that server retroactively. At tens of thousands of dollars per processor core, a mid-size server with 32 cores generates a licence shortfall measured in the hundreds of thousands of dollars — from what appeared to be a minor operational decision by a DBA managing a database server.

A related risk applies to disaster recovery. If the DR environment for P6 replicates the entire database server rather than just the P6 schemas, any non-P6 data on the primary server is replicated to the DR environment. This creates a double exposure: both the production server and the DR server require full database licences if non-P6 data is present on either.

The WebLogic Server Restricted-Use Boundary

Oracle Primavera P6 EPPM includes a restricted-use licence for Oracle WebLogic Server Standard Edition. This licence covers the deployment of the P6 web application — the Java EE application server environment required to run the P6 web interface. The boundaries of this restricted-use licence are highly specific and documented formally in Oracle's licensing information documents.

WebLogic Standard Edition features are included; WebLogic Enterprise Edition features and WebLogic Suite features are not. The practical implications are significant. The restricted-use WebLogic Server must run in a single-server configuration. Clustering is a WebLogic Enterprise Edition feature. If an organisation clusters its P6 WebLogic environment — a common architecture choice for high availability and load distribution — it has deployed a WebLogic Enterprise Edition feature in a Standard Edition environment, breaching the restricted-use terms.

This specific violation carries known financial consequences. In documented Oracle audit findings, organisations that clustered P6 WebLogic for failover or high availability purposes were required to either purchase full WebLogic Enterprise Edition licences for all processors in the cluster or immediately deactivate clustering. The licensing exposure for a four-processor WebLogic cluster exceeds $200,000 before retroactive support fees are calculated. Infrastructure teams that implement WebLogic clustering as a standard HA architecture pattern without reference to the P6 licensing terms create this exposure routinely and without awareness.

BI Publisher and Other Bundled Components

Oracle BI Publisher is included with P6 EPPM as a reporting engine. Its restricted-use scope is limited to generating reports from Primavera P6 data. BI Publisher is a capable reporting platform that many organisations would use more broadly if the licence permitted — for financial reporting, operational dashboards, or cross-application reporting. The restricted-use licence does not permit this.

Using BI Publisher to generate reports from non-P6 data sources — even if those reports are delivered to P6 users or presented in the context of the P6 application — constitutes a restricted-use boundary breach. The same principle applies to any integration that passes non-P6 data through the BI Publisher instance bundled with P6.

Additional middleware components included with P6 EPPM (such as Oracle Coherence and certain JDK runtime components) carry equivalent restrictions. The general principle is consistent across all bundled components: they may be used solely for P6 EPPM functionality, not for any independent application or data processing purpose.

Indirect Access: A Compound Risk

Restricted-use boundary violations in P6 often compound with indirect access exposure. Oracle's licensing model requires that every user who accesses Oracle database data, directly or through an application integration, be appropriately licensed. With Primavera P6, this creates a specific risk pattern.

Organisations frequently integrate P6 with other enterprise systems — ERP platforms, financial reporting tools, project management dashboards, or executive reporting portals. When these integrations query the P6 database or extract P6 data for consumption by users who are not licensed P6 named users, Oracle's indirect access rules apply. The users accessing P6 data through the integration are accessing Oracle Database data indirectly, and Oracle's audit position is that each such user requires an appropriate database access licence.

Our Primavera P6 licensing guide documents the indirect access risk in detail. The practical consequence is that a P6 deployment serving 50 named users but feeding data to a reporting portal accessed by 300 employees may have named user licence exposure for some or all of those additional 300 users. Oracle's LMS team has raised indirect access claims in P6 environments with increasing regularity as project management data integration has become more common.

Audit Scope Expansion

One of the most important practical risks of restricted-use boundary violations in P6 is that they frequently trigger audit scope expansion. Oracle's LMS team, when conducting a Primavera audit, may begin with a review of P6 named user counts and quickly pivot to a broader Oracle estate review when they identify evidence of non-compliant technology stack usage.

A restricted-use Database violation discovered during a P6 audit provides LMS with grounds to review the full Oracle Database deployment across the organisation. A WebLogic clustering violation opens the door to a review of all WebLogic Server deployments. What began as a Primavera audit can escalate into a comprehensive Oracle technology stack assessment carrying seven-figure exposure. The P6 deployment is the entry point, but the financial consequences extend across the Oracle relationship.

This dynamic makes proactive Oracle compliance assessment more valuable than reactive audit response. An independent review of the P6 deployment against the restricted-use terms — conducted before Oracle initiates contact — allows the organisation to identify and remediate boundary violations on its own terms. Remediation options include architectural changes (separating non-P6 workloads to independent server instances), licensing upgrades for specific components where the usage cannot be separated, or migration to Oracle Cloud or Primavera Cloud where the restricted-use licensing model does not apply in the same way. Booking a consultation with our Oracle advisory team is the first step toward resolving this exposure before it becomes an audit finding.