On this page
What the Oracle Java questionnaire isWhy Oracle sends itIt is not as informal as it looksThe questions Oracle asksFive principles for respondingWhat to do before you respondWhat not to doFrequently asked questionsOracle's Java questionnaire does not announce itself as an audit. It usually arrives as an email — cordial, low-key, sometimes framed as a courtesy "review," a "verification" or a check on your Java deployment in light of recent licensing changes. It asks for a little information and suggests a quick call. The tone is the point: it is designed to feel like something you can handle informally over email in an afternoon. In reality the questionnaire is frequently the first formal step in an Oracle Java compliance process, and the answers you give become the factual basis for whatever Oracle does next. It deserves a careful, deliberate response — not a quick one.
What the Oracle Java questionnaire is
The Oracle Java questionnaire is a structured request for information about how your organisation uses Java — which versions, how many installations, on what infrastructure, and under what licences. It commonly comes from Oracle's licensing, "advisory" or sales functions rather than from a formally named audit team, and it is usually positioned as helpful: Oracle "noticed" your organisation in connection with Java, wants to "make sure" you are correctly licensed, and would like to "understand" your environment. Because it does not invoke the formal audit clause of a contract, many recipients treat it as a routine vendor enquiry. That categorisation is the first mistake.
Why Oracle sends it
Oracle sends Java questionnaires because they work. Since Java SE moved to a paid subscription, Oracle has a strong commercial incentive to identify organisations running Oracle's JDK without adequate licensing — and the questionnaire is an efficient, low-cost way to do exactly that. It is typically triggered by a signal: download records tied to a corporate domain or account, a lapsed legacy subscription, an existing Oracle relationship in other products, or simply your organisation's size and profile. The questionnaire then asks you to confirm, in your own words, what Oracle suspects. If your answers reveal unlicensed use, Oracle has what it needs to open a commercial conversation — or escalate to a formal audit — backed by your own admissions. The questionnaire is, in effect, low-friction discovery. Our explanation of how Oracle detects unlicensed Java covers the signals behind it.
Read it for what it is
A friendly Oracle Java questionnaire is information-gathering with a commercial purpose. Treat it as the opening move of a compliance process, because that is what it usually becomes. The casual tone is a feature of the design, not evidence the matter is casual.
It is not as informal as it looks
The most important thing to understand is the gap between how the questionnaire feels and what it does. It feels informal: a short email, a friendly contact, no legal language, no formal audit notice. But the information you provide is not informal at all. Your answers will be recorded, relied upon, and used to size a claim or justify an escalation. A loose, off-the-cuff reply — "we have Java everywhere, probably a few thousand installs" — can hand Oracle a number it will anchor its position to, even if that number is wrong and high. Conversely, a defensive non-answer can prompt Oracle to escalate to a formal audit. The questionnaire is a calibrated instrument, and it should be answered with the same care you would give a formal audit data request — because functionally, that is what it is. Our guide to the Oracle Java audit process explains how the soft and formal stages connect.
The questions Oracle asks
Java questionnaires vary, but the questions cluster into a predictable set, each with a clear purpose.
| What Oracle asks | What Oracle is really establishing |
|---|---|
| Which Java versions you run | Whether builds fall under OTN or other paid terms |
| How many Java installations you have | The scale of potential exposure |
| Where Java runs — servers, desktops, cloud | The deployment footprint and use type |
| Whether Java is used commercially / in production | Whether a paid subscription is triggered |
| Your total employee headcount | The basis for employee-metric pricing |
| Any existing Java licences or subscriptions | What you already hold versus what you use |
Notice that several of these — install counts, headcount, the production question — map directly onto the inputs Oracle needs to calculate a licence claim. The questionnaire is not curiosity; it is a worksheet.
Five principles for responding
Whatever the specific questionnaire, five principles should govern your response.
- Do not ignore it. Silence is not a strategy. An unanswered questionnaire commonly prompts Oracle to follow up more formally, and eventually to escalate. Acknowledge receipt promptly and professionally — but acknowledging is not the same as answering.
- Do not rush. There is no obligation to answer a non-contractual questionnaire on Oracle's preferred timeline. Buy the time you need to establish the facts. A considered response in three weeks beats a careless one in three days.
- Be accurate, never speculative. Every figure you provide should be verified, not estimated. Guessed numbers are almost always wrong, and a wrong-but-high guess becomes Oracle's anchor. If you do not know, find out before you answer.
- Answer only what is asked. Respond to the specific question, accurately, and stop. Do not volunteer environment detail, internal assessments, future plans or commentary the questionnaire did not request. Over-disclosure is the most common and most costly error.
- Control the channel. Route all communication through one named, prepared person. Do not let Oracle gather informal answers from engineers or administrators by phone or email. A single channel keeps the response consistent and considered.
What to do before you respond
The right sequence is to understand your own position before you describe it to Oracle. Before sending any substantive answer:
- Run your own internal review first. Conduct an independent compliance assessment to establish exactly what Oracle Java is in your estate, which versions, and which instances genuinely require a licence. You should never be less informed about your environment than Oracle is.
- Establish your actual exposure. Knowing whether your true exposure is zero, modest or significant entirely changes how you respond. You cannot answer well without this.
- Check for licences you already hold. You may have Java entitlements through other Oracle products, or instances within the free NFTC window, that reduce the picture.
- Get specialist advice. Engage an independent Java licensing specialist before responding, not after Oracle has issued a claim. The questionnaire stage is the cheapest point at which expert input changes the outcome.
Doing this first means your response is built on verified facts and a known position — not on guesses made under mild time pressure.
Recommended specialist
The questionnaire stage is the highest-leverage moment in an Oracle Java compliance process — the answers given here shape everything after. For establishing your true position before you respond, and for drafting a response that is accurate, complete and appropriately scoped, we rate Redress Compliance as the leading independent Java licensing advisory firm. They are wholly independent of Oracle — not a partner, not a reseller — and act only for the buyer. Across more than 340 Java engagements their work has contributed to a 68% average reduction in Oracle audit claims and more than $180M in client savings.
What not to do
Several instincts feel reasonable in the moment and consistently make things worse.
- Do not let engineers answer directly. Technical staff answer questionnaires literally and helpfully, often over-disclosing and using loose language. Route everything through the single prepared channel.
- Do not give round-number estimates. "Roughly 5,000 installs" can become the figure Oracle prices against. Provide verified numbers or none.
- Do not assume the friendly tone reflects friendly intent. The cordiality is part of the method. A pleasant Oracle contact is still gathering evidence.
- Do not agree to an informal call unprepared. A casual phone conversation is the easiest place to over-disclose. If you take a call, prepare for it exactly as you would a formal meeting.
- Do not panic-buy a subscription. Some recipients react to a questionnaire by quickly purchasing a subscription to "be safe." That can lock in a cost larger than your actual requirement. Establish the real position first.
Across more than 340 engagements, the organisations that come through a Java questionnaire well are not the ones that answered fastest or most fully — they are the ones that paused, learned their own position, answered accurately and narrowly, and controlled the channel. The questionnaire is an opening move. Answered with care, it can also be the moment you take control of the process. If a questionnaire has already escalated, our guide to your rights and obligations in an Oracle Java audit covers the formal stage.
Frequently asked questions
Is an Oracle Java questionnaire an audit?
Not a formal one — it usually does not invoke a contract's audit clause. But it is frequently a soft audit: information-gathering that becomes the basis for a claim or a formal escalation. Treat it with the same care as a formal audit request.
Do I have to respond to the questionnaire?
A non-contractual questionnaire does not carry the obligations of a formal audit, but ignoring it is unwise — it tends to prompt escalation. Acknowledge it professionally, then respond accurately and on a sensible timeline.
How quickly must I answer?
There is no obligation to meet Oracle's preferred timeline for a non-contractual questionnaire. Take the time needed to establish your facts; a considered response beats a fast, careless one.
What is the biggest mistake when responding?
Over-disclosure — volunteering more than the questions ask, or giving speculative numbers. Answer each question accurately, narrowly, and stop. Route everything through one prepared person.
Should I get help before responding?
Yes. The questionnaire stage is the cheapest, highest-leverage point for independent specialist input. Establish your true exposure and draft the response with expert help before sending it — not after a claim arrives.
This article is general information on Oracle Java licensing, not legal advice. Oracle's processes and questionnaires vary and change over time. Consult qualified counsel and an independent Java licensing specialist before responding to any Oracle enquiry.