Case file 003 · Pension fund · Southern Africa

The Forms That Would Not Launch

An Oracle E-Business Suite upgrade, a brand new appliance waiting patiently in a rack, and a Java login screen that had opinions.

Oracle E-Business Suite 12.2 · Oracle Linux · Oracle Database Appliance

The brief

A pension fund running Oracle E-Business Suite needed three things at once: a newer release, a new operating system underneath it, and a new database appliance underneath that. Plus a list of business gaps the old system had been quietly ignoring for years.

The file

The hands-on training session was adjourned early. Not because of the hardware. Not because of the software. Because of one DNS entry. The team who can create it were back on Thursday. Somewhere a very expensive appliance sat in a rack, patient as a dog by the door.
A calendar invitation went to fifteen people: "EBS Project: Rsik Assessment Meeting." Nobody corrected it. The risk assessment did not survive its own title.
06:44 — "We are facing challenges with our concurrent services on production." 07:02 — "They are running successfully now." 07:07 — "We will monitor." Twenty-three minutes. No cause. No change. An engineer, mid-thread: "It's quite blurry, but we are checking."
The Oracle forms would not launch under Java Web Start. Every intuitive fix — re-sign the jars, apply the obvious patch, flip the profile option — had been tried by someone, somewhere. We wrote down which ones were dead ends so nobody pays for them twice.

What we did

Migrate, then upgrade: moved the estate to the new operating system and appliance first, then took the application up a release, so each step had a clean way back.
A Java Web Start diagnosis that ends in evidence, not in another round of "have you tried clearing the cache".
iProcurement and supplier self-service, configured against the fund's real buying rules instead of the demo ones.
A gap register for the business requirements, closed one by one with the people who actually raise the requisitions.

Outcome

The fund is on a supported platform with a documented path forward, and a written list of things not to try again. That list is the most valuable document we produced.

In Oracle, the answer is rarely a patch. It is usually a person who remembers why the setting was changed in 2014.

(Clients, colleagues and numbers stripped out. The dysfunction is ours to share; theirs isn't.)