It's the canonical enterprise vendor on the database side (DB2 has far smaller market share, and SQL Server market play is slightly different), so it's the poster child for anything from no two customers paying the same price for same metrics, to opaqueness and perceived unfairness of the contracts, to seemingly predatory fees, to ambiguous and frequently awful licensing on virtual CPUs, to the various shakedowns and so on.
I'm not saying others in the same market are markedly different; but just like IBM is the HN poster child for a "no longer relevant tech dinosaur", Oracle is the HN poster child for "predatory licensing & fees".
(* Note/disclosure, I have the distinct privilege of being happily employed by one to reasonably happily work on the products of the other :-D )
A quick search of "Oracle" from the homepage search (only in the last year, since your account isn't much older than that), shows most articles are non-technical in nature.
https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=tru...
A case could be made that the database itself is predatory, insofar as Oracle encourages use of non-standard functions that make migration to an alternative very difficult.
10 years ago (at Amazon in fact) was the last time I used Oracle and I've never felt any desire to use it again. I wasted far too much of my working life fixing queries that used the silly outer join operator (+) or debugging proprietary functions that already had a perfectly good ANSI alternative.
In reality, your experience as a dev might not be that bad from within the ecosystem.
But take the hate for what it is: learn portable tooling, be aware of the proprietary bindings, and architect to be more database agnostic.
It may save your job if the budget cuts are between ludicrous oracle licensing and auditing costs, or your salary.