I *dont* understand why universities would tolerate this sort of corporate bullying from Oracle, when alternative JVMs and DBMS are *right there*.
I can take a stab at this.
First, it is surprisingly difficult to verifiably eliminate a piece of software from a large environment. We went through this exact exercise a couple years back because we didn't want to pay Oraclegeld. The first 90% is easy. But then you're dealing with Java running on weird devices that are difficult, expensive, or both to replace. And employees who for strange reasons try to keep a copy. And vended applications where swapping the JVM voids your support contract. And all sorts of other weird situations.
And second, these are universities. Schools in general are not exactly famous for having an iron grip on their computing resources. Their IT capabilities in general are different than businesses because their focus is different. And structurally, there are frequently organizational silos and redundant departments with their own budgets for historical reasons, so I imagine even trying to inventory all the computers a school "owns" is can be a challenge in some places. (This is certainly true in the US, I'm guessing English schools are subject to similar pressures.)
So it doesn't surprise me at all if they just couldn't pull it together. Even with centralized administrative control of our machines, it was a multi-month and surprisingly costly effort for us.