Oracle Completes Its Acquisition of Sun Microsystems

Oracle publicly announced that it had completed its acquisition of Sun Microsystems on January 27, 2010. The legal merger became effective on January 26: Sun survived as a wholly owned Oracle subsidiary. That one-day distinction aside, the closing transferred control of an unusually broad portfolio, including Java, Solaris, SPARC servers, storage, and MySQL, from a systems and software company to a vendor best known for databases and enterprise applications.

The deal’s history is not a simple tale of Oracle “keeping” or “killing” Sun. Oracle announced a plan and made public product promises; regulators examined a specific competition question; employees, customers, and volunteer communities reacted to the new owner; and product roadmaps then developed at different speeds. Separating those stages avoids attributing every later fork, departure, or release to the closing date alone.

The deal and its regulatory chronology

Oracle and Sun announced their definitive merger agreement on April 20, 2009. Oracle offered $9.50 in cash per Sun share, valuing the transaction at about $7.4 billion, or about $5.6 billion net of Sun’s cash and debt. Oracle’s announcement framed the business logic as an integrated stack, from applications and database to operating system, servers, and storage. It singled out Java and Solaris as strategic software assets and said Oracle intended to continue investing in Java.

The principal public regulatory dispute was about database competition. Sun had completed its acquisition of MySQL in February 2008, before Oracle’s bid; after the proposed merger, MySQL would sit inside a company with a major proprietary database business. U.S. and European authorities reached different initial views. The U.S. Department of Justice said on August 20, 2009 that it had approved the deal. On September 3 the European Commission opened a second-phase investigation. It issued a statement of objections on November 9, saying its concerns about the database market still differed from the U.S. agency’s view.

Date	Milestone	Why it matters
April 20, 2009	Oracle and Sun announced the agreement	Proposed price: $9.50 per share; estimated transaction value: $7.4 billion.
August 20, 2009	U.S. DOJ notified Sun it had approved the transaction	The DOJ said it expected database customers to retain other choices and noted that MySQL’s community could support a derivative.
September 3, 2009	European Commission opened an in-depth investigation	Regulators examined whether ownership of MySQL could lessen competition in relational databases.
November 9, 2009	Commission issued a statement of objections	The U.S. and EU agencies had reached different preliminary assessments.
December 14, 2009	Oracle published ten MySQL pledges	The announcement addressed matters including GPL releases, storage-engine interfaces, and support arrangements.
January 21, 2010	Commission cleared the merger	Its final decision concluded that the deal would not significantly impede effective competition.
January 26–27, 2010	Merger became effective; Oracle announced completion the next day	Sun became an Oracle subsidiary and control formally transferred.

Oracle’s December pledges included continued enhancement and GPL availability of MySQL, maintaining its pluggable storage-engine architecture, and a customer advisory board. The Commission discussed those public statements in its final decision, alongside other evidence: it found that Oracle and MySQL were not close substitutes in every database segment, identified PostgreSQL as a potential competitive constraint, and considered whether forks of MySQL could emerge. The Commission’s decision cleared the concentration under Article 8(1); it was not a general certification of Oracle’s future stewardship or of MySQL’s product health. Nor is it accurate to treat every public pledge as an identical, court-ordered merger condition: the decision distinguished commitments implemented contractually for certain third parties from other unilateral public statements.

This distinction explains why the review matters historically. It brought questions about open-source governance into a high-profile merger proceeding, but the legal test was whether the transaction would substantially harm competition, not whether one owner was philosophically preferable for a project community. The DOJ’s statement itself emphasized that developers and users had expertise to maintain and improve a derivative; the Commission examined that possibility while weighing the market evidence.

Separate projects chose separate paths

The strongest evidence of community response is not a single “exodus” statistic but a series of different governance decisions. Some began before the merger closed, and they should not all be described as reactions to a completed acquisition.

MariaDB began before closing. After Oracle announced its bid, MySQL founder Michael “Monty” Widenius launched MariaDB as a fork in October 2009. The proposed acquisition, not a transfer already completed, was part of the context. The fork let developers and users continue development under a separate project, but it did not instantly replace MySQL or prove that Oracle had abandoned the product.

illumos followed a source-governance break. Garrett D’Amore announced illumos in August 2010 as a project based on OpenSolaris technology, initially with the goal of replacing closed components. Oracle then stopped publishing the full operating-system source in real time during development. The change transformed illumos from a downstream effort into an independent continuation point for much of the open Solaris kernel and userland. The project’s own history and a USENIX talk by DTrace co-creator Bryan Cantrill document this sequence; Oracle continued to develop and release Solaris separately, so “OpenSolaris ended” is more precise than saying Solaris itself ended in 2010.

LibreOffice chose independent governance. In September 2010, long-time OpenOffice.org contributors announced The Document Foundation and LibreOffice as a fork. The stated institutional goal was an open, independent, meritocratic organization. Oracle later donated the OpenOffice.org code to the Apache Software Foundation in June 2011. That produced two distinct successors and governance paths; it did not mean that the original suite vanished immediately or that all contributors moved to one fork.

Hudson’s rename came later. The community around the continuous-integration server Hudson faced a separate dispute over project governance, infrastructure, and Oracle’s trademark applications. On January 11, 2011, its leadership proposed Jenkins as a new name and put the decision to a community vote; the vote was announced as complete on January 29. This was a concrete case where transferring control of a corporate asset also affected a project’s name and independence, but it was not a database-merger remedy.

These examples differ in timing, technical lineage, and cause. MariaDB was already a fork before closing; illumos reacted to the end of OpenSolaris’s public development feed; LibreOffice established an independent foundation; and Hudson/Jenkins resolved a naming and governance dispute. The records do not support the blanket claim that every fork “won,” that each one existed only because of Oracle, or that community activity automatically migrated away from the original project.

Java’s ownership changed; its standards and code did not disappear

Java was one of Oracle’s explicitly named strategic reasons for buying Sun. That did not mean Java originated under Oracle or that Sun had kept the JDK entirely closed: Sun opened the OpenJDK codebase in 2007. Oracle became the owner of that business and a central participant in the platform, while Java specifications continued through the Java Community Process and OpenJDK remained a public development project.

The release chronology also needs care. Java SE 6 was released in December 2006 and Java SE 7 in July 2011, an interval of roughly four and a half years. Oracle’s July 2011 release was important after a long wait, but the calendar does not establish that the acquisition alone caused the delay. After the purchase, Java’s most visible legal conflict was Oracle v. Google: Oracle sued over Android’s use of Java declarations. In April 2021, the U.S. Supreme Court held Google’s particular copying to be fair use. The Court assumed for the sake of its analysis that the material was copyrightable; it did not decide that all APIs are, or are not, copyrightable.

Solaris and SPARC took a different route

Oracle’s 2009 integration pitch placed Solaris and SPARC at the center of a complete hardware-and-software stack. In January 2017, Oracle announced a continuous-delivery model for Solaris 11 instead of a separate Solaris 12 release, while stating that it planned further innovation and support. Oracle released Solaris 11.4 in August 2018 and continued publishing SPARC systems, including the M8 generation. These later facts are a useful corrective to claims that 2017 staffing cuts immediately ended both technologies. They do not, by themselves, prove that Oracle’s long-term investment matched its original merger promises or that the business remained as prominent as Sun’s.

The result was mixed and uneven: Java and Solaris products continued with new ownership; MariaDB, illumos, LibreOffice, and Jenkins built or chose separate paths for distinct reasons; and the regulators’ MySQL review asked a narrower competition question than any of those communities’ governance concerns. Sun ceased to be independent, but neither its software nor its technical communities were transferred as a single, uniform thing.

Related:

Sources:

The deal and its regulatory chronology

Separate projects chose separate paths

Java’s ownership changed; its standards and code did not disappear

Solaris and SPARC took a different route

Comments