Yeah this happens all the time. Architects sell a 'Fusion Middleware' pile of nonsense that will magically solve all problems, and it doesn't work. One notable case is the Cover Oregon website, which literally never worked. Read section C of this for some big laughs:
https://oversight.house.gov/sites/democrats.oversight.house....
deja vu: 20 years ago, I was always hearing people in IT at Stanford bitch about Oracle Financials. They'd been struggling through a 2-year migration to it that was mandated by top management. Some things never change.
While I was an undergrad, Cambridge University hired Oracle to implement a financials system, which was also a fiasco which led to long running internal investigations. https://www.admin.cam.ac.uk/reporter/2001-02/weekly/5861/1.h...
Reminds me, we're currently migrating from Oracle SQL to Postgres because it seems they simply stopped maintenance. They only have official releases for the ROracle package until R 3.6 [0], the latest R version is 4.2. You can still get it to work, but it's getting increasingly harder, and at some point we drew a line (for multiple reasons).
[0] https://www.oracle.com/database/technologies/roracle-downloa...
If you've ever been on the sharp end of Oracle and their incredibly shit web apps that can cost billions of dollars this will be no surprise to you
I don't really know what has happened lately, but 20-25 years ago as a Sun vendor I was involved in or had knowledge of at least 10 large ERP projects, and in all of them SAP won. I don't have the details, but I got the feeling that all those customers discarded Oracle because it barely scored 2 or 3 points in the evaluation matrix. All of those SAP projects were a success. All of them.
You can read the report about the infamous Oracle-produced CAPSA financial system which had terrible problems twenty years ago at the University of Cambridge: https://www.admin.cam.ac.uk/reporter/2001-02/weekly/5861/1.h...
So was it really Oracle's fault or are they the innocents in someone else's incompetent integration plan?
Key factor: The most recent upgrade of this system had taken place in November 2013.
Big ERP project failures always make the news because ERP is so expensive and the victim orgs are often public bodies with no in-house IT expertise, whose procurement process involves senior managers getting hypnotized on a golf course, with no engineers in sight.
The orgs themselves are not always blameless. ERP is expensive because the orgs are complex, and usually don’t understand themselves. The kind of end-to-end processes that ERP implements cross organizational boundaries, which is to say departments that don’t have good communication behaviors between themselves and therefore don’t fully understand why they do things. This is the seed of disaster for any project.
And then Oracle specifically make this difficult situation worse by having supremely opaque product documentation, names, versioning, licensing, and a constellation of internal support teams (which are no different to the client orgs in that they don’t communicate well with each other either).
All these big failures are fundamentally failures to communicate the right information throughout the project. Nobody is willing to do the hard yards of understanding and mapping out end-to-end processes and integration points, and fitting them to technology components. They all think they can shortcut the process by starting with the technology and working backwards from there, because that’s what Oracle sales told them they could do.
I’m not trying to excuse Oracle’s actions here, but ERP failure is normally a two-player game.