What is Oracle Data Visualization?

Oracle Data Visualization, usually shortened to DV, is the self service visual analytics capability Oracle built to compete with the modern wave of drag and drop discovery tools. An analyst connects to data, builds projects with charts, narratives, and machine assisted insights, and shares them. As a piece of software it is straightforward. As a licensing object it is one of the more confusing things in the analytics portfolio, because the same DV experience reaches users through at least three distinct vehicles, and the vehicle is what carries the grant.

That is the single idea to hold onto. Data Visualization is not licensed as a product you buy in isolation. It is licensed by whichever delivery vehicle puts it in front of a user, and those vehicles range from a genuinely free desktop client to a metered cloud subscription to a Processor licensed server. Treating DV as one thing with one price is the mistake that produces both overspend and exposure, often in the same estate. The discipline mirrors the documentary approach that runs through all of BI and analytics licensing.

The delivery vehicles and their grants

Three vehicles account for almost every Data Visualization deployment in the field, and each answers the licensing question differently. The first is Data Visualization Desktop, a free standalone client for a single analyst. The second is Oracle Analytics Cloud, where DV is part of a metered subscription. The third is Oracle Analytics Server, the successor to OBIEE, where DV is part of a perpetual Processor or Named User Plus entitlement.

Data Visualization delivery vehicles and how each is licensed
VehicleWho it suitsLicensing basis
DV DesktopOne analyst, local workFree, single user, single machine
Oracle Analytics CloudShared cloud deploymentSubscription, OCPU or named user
Oracle Analytics ServerShared on premise deploymentProcessor or Named User Plus

The practical consequence is that the answer to "how is our Data Visualization licensed" is never a single sentence. It is an inventory: which installs are Desktop, which users reach DV through Oracle Analytics Cloud, and which sit on an Analytics Server entitlement. Until that inventory exists, the position is unknown rather than compliant.

Is Data Visualization Desktop really free?

Yes, and that is precisely where the trouble starts. Data Visualization Desktop is a free client intended for a single analyst working on a single machine with their own data. Oracle does not charge for it, and nothing about installing it creates an entitlement question on its own. The exposure appears when the free client is treated as a licence to do something it never granted.

The Desktop client is free for one analyst on one machine. It is not a free pass to stand up a shared analytics service.

The boundary is sharing. The moment DV content is published to a shared server, scheduled, embedded in another application, or made available to a community of consumers, the deployment has left the free Desktop grant and entered the territory of a licensed vehicle. We routinely find estates where dozens of Desktop installs have quietly become the backbone of departmental reporting, with content passed around and refreshed on shared infrastructure. Each of those patterns needs a server vehicle, and the cumulative gap can be material. The free client is a gift to individual analysts; it is not a route around server licensing.

Which metric applies to server deployments?

Where Data Visualization is delivered through Oracle Analytics Server, it follows the two metrics that govern the rest of the on premise analytics tier: Processor and Named User Plus. Processor counts physical cores multiplied by the Oracle core factor and suits broad deployments where the audience is large or uncountable. Named User Plus counts authorised individuals and is subject to the ten per processor minimum, which makes it suitable for small, defined communities and dangerous for large or growing ones.

The per processor minimum is, as everywhere in the Oracle estate, the variable that produces surprises. A capable Analytics Server hosting DV on substantial hardware can owe far more under Named User Plus minimums than a small user count would suggest, making Processor the cheaper basis despite the modest audience. The arithmetic should be run explicitly against the deployment topology rather than assumed, exactly as set out for the broader tier in the BI Server licensing guide. Where DV connects to an Oracle source, that source database is a separate exposure to be reconciled on its own terms.

Data Visualization inside Oracle Analytics Cloud

In Oracle Analytics Cloud, Data Visualization is not a separate purchase at all; it is part of the OAC subscription, and the licensing questions become consumption questions. OAC is metered, historically by OCPU and increasingly by named user editions, and the cost driver is the size and shape of the service rather than a perpetual entitlement. A buyer moving DV workloads to OAC should understand that the free Desktop grant and the perpetual server grant both fall away and are replaced by a recurring commitment.

The migration question that matters is whether moving DV to Oracle Analytics Cloud resolves an on premise grant uncertainty or merely relocates it onto a meter. Where existing Analytics Server entitlements exist, a buyer should test whether they can be brought to bear under a bring your own licence arrangement rather than paying twice. The economics of that choice deserve a deliberate model, not a default to full subscription pricing.

Data Visualization inside Analytics Server

Oracle Analytics Server is the on premise successor to OBIEE, and for customers who licensed OBIEE Enterprise Edition or BI Foundation Suite, Data Visualization typically arrives as part of that modern entitlement rather than as a new line item. This is good news and a trap at once. It is good news because the capability is already paid for under the existing suite grant. It is a trap because customers frequently assume their legacy OBIEE metrics map cleanly onto the new server, and the mapping is not always one to one.

The disciplined step is to confirm, in the ordering documents, exactly which entitlement covers the Analytics Server install, what metric it carries, and whether the DV capability is genuinely within that grant or requires a supplementary licence. That confirmation is documentary work, and it is the core of any defensible analytics position. Where the answer is unclear, our BI and analytics advisory reconstructs the grant before an auditor does.

The common Data Visualization audit findings

Three findings recur. The first is the Desktop sprawl: a population of free Desktop clients that have collectively become a shared reporting service without any server vehicle behind them. The second is the metric mismatch: a Named User Plus Analytics Server where the per processor minimum, or the actual population reaching DV, exceeds what was purchased. The third is the orphan server: a DV deployment with no traceable grant, stood up during an implementation and never licensed.

All three are documentary and all three are defensible to the degree the buyer has done the inventory in advance. The auditor's leverage comes from being the first to interpret the deployment against the grants; the buyer's defence comes from having interpreted it first, with cleaner data and a tighter reading, which is precisely what audit defence is built to deliver.

Self assessing a Data Visualization estate

A buyer can reach a defensible Data Visualization position by performing, in advance, the same analysis an auditor would. The process classifies every DV touchpoint by vehicle and tests each against the grant that vehicle carries.

Data Visualization self assessment, by deployment
QuestionWhat to confirm
Where is DV reached?Desktop, OAC, or Analytics Server, per user group
Is any Desktop shared?Published or scheduled content needs a server vehicle
Which grant covers the server?Suite entitlement, standalone licence, or none
Does the metric still fit?Compare NUP minimums and population to Processor
What is the gap?Quantify any unlicensed sharing or shortfall

The deployments that fail this test fall into the familiar categories, and each has a remediation: consolidate Desktop sprawl onto a licensed vehicle, realign the server metric to the cheaper basis, or decommission and relicense the orphan deliberately. Choosing the remedy in advance is far cheaper than conceding it under audit, and the self assessment is the routine first step of our analytics advisory.

Oracle Data Visualization licensing: frequently asked questions

Is Oracle Data Visualization Desktop free?

Data Visualization Desktop is a free single user client for individual analysis on one machine. It is not a grant to deploy a shared visual analytics service. The moment content is published to a server or shared with others, a licensed vehicle such as Oracle Analytics Cloud or Analytics Server is required.

How is Data Visualization licensed on a server?

Server deployment is licensed through the vehicle that delivers it. Oracle Analytics Cloud is a subscription priced by OCPU or by named user, while Oracle Analytics Server is licensed by Processor or Named User Plus subject to the ten per processor minimum. See the BI Server licensing guide.

Does Data Visualization need a separate licence from OBIEE?

Where Data Visualization is delivered through Analytics Server, it is part of that entitlement rather than a separate purchase. Where it is reached through Oracle Analytics Cloud, it is part of the OAC subscription. Confusing the legacy OBIEE grant with a modern Analytics Server or OAC entitlement is a frequent source of error.

Can the same Data Visualization client be both free and licensed?

Yes. A Desktop install used purely for one analyst's local work is free, while the same visual capability published through a shared server requires a licensed vehicle. The deployment pattern, not the software, determines the grant.

Related analysis in this cluster: Oracle Analytics Cloud licensing and the BI and analytics pillar.