It's interesting that the third-party consultants hired by the city to implement it aren't named in these articles and "Oracle" is taking the brunt of the blame, much like "Ticketmaster" doesn't care if you don't like them or not, you're going to use them. It's not
just Oracle's fault for a 200m pound invoice, and I agree jumping from SAP to Oracle is probably one reason why the customization costs that much more than going from some smaller accounting system.
You have third-party consultants charging for addressing all the mistakes in the system, present on daily chats and constantly chasing them around for support. Oracle's always upselling you on the parts of the system you haven't implemented yet.
The actual municipal employees are making 75% (my own estimate) of what their industry peers make in salary so they're just trying to do their job as they found it, not attempt to replace the status quo with a "solved, open source, one-size-fits-all solution" like so many here believe various ERP systems are. Everything sounds better on paper.