Part 1: Lessons learned during 11.3.6 sandbox testing
We are now between development and production, So far, no "show stoppers", but a few bumps in the road.
Installing AutoSys agent/app server after EEM and WCC
Because we need to keep 11.3 running during the 11.3.6 upgrade, we have new Windows VMs to install components. One challenge was getting the latest EEM running so we could connect the upgraded instances to that. Currently we only have WCC in EEM, but during the upgrade we are adding AutoSys security. I installed EEM, then WCC, and found AutoSys would not install cleanly. After going through support (21881850) and back issues, we could not progress with the agent install so we configured a "standard" agent. These dependencies are baffling, to say the least.
Miscellany
- Ran out of Oracle processes. Seems like architecting the application servers instead of direct DB processes is still an art.
- WCC 11.3.6 INC2 is mandatory for successful backend communication. Not sure how that got out the door.
- Leftover records in the database. Case opened. 11.3 is the culprit, not the upgrade; greater scrutiny revealed a mess.
- WCC 11.3.6 showing wrong results for failed jobs marked as success. We think the upgrade will "self-heal" this.
- Autorep showing wrong run history. This one should not have gotten out the door either.
- Loss of WCC configuration on AutoSys upgrade. You need to delete an instance and add it back. Save your views, as they could be wiped.