'We had to educate Oracle about our contract,' CIO says after Big Red audit

Original Article ↗ Hacker News Discussion ↗

Oracle’s aggressive licensing and audit practices are prompting many organizations to rethink their reliance on its databases, Java, and other products. Commenters describe audits that feel like revenue-maximizing “shakedowns,” deep vendor lock-in via proprietary features, and even a secondary industry of ex-Oracle consultants helping firms navigate compliance. While the core technology is often praised, most argue that legal risk, cost, and inflexibility now outweigh the benefits, leading many to favor PostgreSQL, SQL Server, and other open-source or less litigious alternatives.

Oracle licensing, audits, and compliance ecosystem

  • Many commenters describe Oracle’s default posture as “you’re out of compliance,” with audits used as a revenue tool.
  • Audits are portrayed as aggressive, sometimes triggered by ex‑employees or download telemetry (e.g., Java, VirtualBox).
  • A consulting ecosystem exists around Oracle license compliance, often staffed by ex‑Oracle people, seen by some as a “racket.”
  • Some companies negotiated or even received refunds; others faced six‑figure back bills and, in at least one case, went out of business soon after.

Java and other Oracle products

  • Recent Java SE subscription changes (per-employee licensing) pushed some organizations to migrate off Oracle Java.
  • Consensus: using non‑Oracle JDKs (OpenJDK builds, Corretto, Azul, distro builds) avoids much of the licensing drama, though support and LTS policies vary.
  • Oracle’s policing of VirtualBox Extension Pack licensing alarmed some; others note Docker does similar license enforcement.

Vendor lock‑in and migration difficulty

  • Deep Oracle DB use (proprietary SQL, PL/SQL, stored procedures, triggers, ERP suites like EBS) creates very high switching costs.
  • Multiple stories of multi‑year migrations (including large cloud providers) off Oracle to PostgreSQL, DynamoDB, or other systems.
  • Commenters emphasize that changing DBs involves extensive query and procedure rewrites, schema tweaks, and hidden edge cases (e.g., empty-string semantics).
  • Some argue migration is “not impossible” and share successful moves to MySQL/MariaDB/Postgres; others stress the risk and cost for 30–40‑year‑old, mission‑critical systems.

Technical views of Oracle vs alternatives

  • Technically, Oracle DB is often described as powerful, mature, and strong on transactions, rollbacks, and analytics.
  • Many say PostgreSQL is now “good enough” or preferred for new projects; others mention MS SQL Server, MariaDB, and specialized modern systems for scale or niche use cases.
  • Some note that Oracle’s main problem is not technology but legal and cost risk.

Why organizations still choose Oracle (or SAP, etc.)

  • Enterprise and government buyers value “a vendor to call” and risk transfer more than developer sentiment.
  • Decisions are often made by non‑technical executives or accounting/ERP functions, sometimes influenced by aggressive sales and perks.
  • Several see Oracle and similar vendors as sustained by inertia, entrenched staff skills, and the fear of rewriting huge legacy systems.