HOWEVER, the way they run their business is horrible. Oracle the product was various versions of awesome to just OK. Oracle the business is a modern-day mafioso shakedown.
They bought it, and it was a disaster. Turns out you can't just take a system designed without partitioning in mind and put it on a distributed database. Not that it mattered; the system saw a tiny fraction of its expected usage. The whole game was an absurd amount of money spent on nothing.
To this day I have never used another Oracle product.
[1] I don't think Will Wright was involved in that decision either; I think he was fully checked-out by then and in any case ops wasn't his bailiwick. The conversation just happened to take place in his office.
That never worked right. Amazon got burned trying to use it, Sberbank in Russia went down hard for several days because RAC just crashed, etc.
A) Performance was so terrible by default the DBAs were cops and had given up on real RDBMS performance tools such as indexes and keys (primary and foreign) and instead used a ton of arcane low level file management tools like Oracle was some sort of "build your own DB kit" and the out of the box one was terrible so they needed a bespoke hand built one
B) I was once in a CLI running some sort of very basic Select statement (no joins, because again, no keys; single table; maybe a couple of columns) and watched in horror as an entire Java-based debugger IDE not installed on my extremely locked down work machine launched, spun up, and dived deep, deep into a terrifying stacktrace comprising an awful mix of C++ and Java code. To this day I don't know how or why a Select statement (that worked the second time) crashed so hard into Oracle's own source code. It is possibly related to part A above, but I'm still not sure. I don't know why the debugger symbols much less actual source code from Oracle were even available when it did crash that hard. I did know at the time that actually debugging Oracle's code was very far above my pay grade and in addition to sending the debugger IDE they should have also attached a large check.
I think of that experience often when people tell me that Oracle actually has good tech. If it weren't obvious from how awful their tools are to use as a user (a different previous employer used Oracle's expensive time/attendance/payroll tools and those were the clunkiest, worst web apps to use), that brief, weird horror story of the Select statement in a CMD.EXE window REPL bringing up the wildest stack trace in a debugger that didn't exist on my machine will always leave me feeling doubtful about that.
https://en.m.wikipedia.org/wiki/SQL/PSM
"SQL/PSM is derived, seemingly directly, from Oracle's PL/SQL. Oracle developed PL/SQL and released it in 1991, basing the language on the US Department of Defense's Ada programming language. However, Oracle has maintained a distance from the standard in its documentation. IBM's SQL PL (used in DB2) and Mimer SQL's PSM were the first two products officially implementing SQL/PSM."