The line item that kills a database migration is rarely the compute bill. Public bodies trying to move workloads onto European infrastructure keep finding that the licence, not the hardware, decides where the software can economically run [14]. The same arithmetic applies in the private sector: if moving to another cloud means buying new licences, or makes the software you already own prohibitively expensive to run, the vendor shortlist you built was decorative [13].
The procedural stage is more interesting than it sounds. The Commission's line that there is no formal investigation into any company is accurate, and it sits next to a promise to keep monitoring possible anticompetitive practices [3]. Asking third parties for information is a real part of the process without the legal consequences of an opened case, and it is the window in which a company has the most room to resolve concerns before the dispute becomes public and harder to contain [4]. Nothing in an Oracle contract has to change while that window is open [17].
SAP used its window in July, agreeing to make switching away and terminating contracts easier, and avoiding fines that could have reached 10% of global annual revenue [5]. What buyers got there was contract rights; what the EU got was no penalty payment [18]. SAP also bought certainty at the cost of never contesting the underlying concerns [10].
Oracle's position differs in two ways that matter to whoever owns the renewal. Its databases sit under financial systems and government registries that were built around them over decades, which gives licence terms leverage a productivity app never has [7]. And Oracle now sells infrastructure itself, so terms that make running its software elsewhere expensive feed its own cloud business in a way they could not when it mainly sold software [11]. Audit disputes with European customers have run for years and were generally closed with a commercial agreement rather than a regulatory one [8]. The change is that the same clause now reads as a question about competition between cloud providers rather than a bilateral pricing quarrel [12], on a file where the Commission already applies specific rules to cloud services under the Digital Markets Act [16]. Oracle did not comment when Reuters approached it [9].
Two facts about each Oracle workload sort an estate into four boxes: whether you can exit the contract inside the current term without buying anything new, and whether the licence travels to another cloud at the same price. Exit and portability both yes, and regulators are irrelevant to you; you already have the leverage and have not used it. Exit yes, portability no, and your migration case depends on a concession nobody can force yet, so the delay needs a price. Exit no, portability yes, and renewal timing is the only lever you hold. Both no, and you are the case study Brussels is collecting information about [1], which is an argument for keeping the workload still rather than signing a longer term now.
The backdrop is that Oracle is committing enormous sums to AI data centre capacity, which makes an open question about its licensing model awkward to carry [15].
