Troubleshooting JSP Compilation Hangs during EBS 12.2 CPU JAN 2026 Patches - AD-TXK Delta 16 Upgrades

Patching Oracle E-Business Suite 12.2 is often a journey full of surprises. Recently, a member of my forum reached out regarding a common but frustrating issue encountered while applying the 2026 CPU  JAN patches and upgrading AD/TXK from Delta 13 to Delta 16.

In this post, I’ll summarize the case and the solution, as it serves as a great reminder of how specific patch dependencies can break an entire upgrade process.

Okay let's start;

The environment was running EBS 12.2.10 with a 19c Database. While applying CPU JAN 2026 patches using adop, the process appeared to hang, or let's say, it slowed to a crawl with a massive failure rate during the JSP compilation phase.

The logs showed the list of jsp translation records as below;

translating jsps...  3% complete: 200/6003 [failed: 200] ETA: 1d0h
  translating jsps...  6% complete: 400/6003 [failed: 400] ETA: 23h17m
  translating jsps...  9% complete: 600/6003 [failed: 600] ETA: 22h24m
  translating jsps... 13% complete: 800/6003 [failed: 800] ETA: 21h34m
  translating jsps... 16% complete: 1000/6003 [failed: 1000] ETA: 20h43m
  translating jsps... 19% complete: 1200/6003 [failed: 1200] ETA: 19h52m
  translating jsps... 23% complete: 1400/6003 [failed: 1400] ETA: 19h1m
  translating jsps... 26% complete: 1600/6003 [failed: 1600] ETA: 18h10m
  translating jsps... 29% complete: 1800/6003 [failed: 1800] ETA: 17h21m
  translating jsps... 33% complete: 2000/6003 [failed: 2000] ETA: 16h29m
  translating jsps... 36% complete: 2200/6003 [failed: 2200] ETA: 15h39m
  translating jsps... 39% complete: 2400/6003 [failed: 2400] ETA: 14h48m
  translating jsps... 43% complete: 2600/6003 [failed: 2600] ETA: 13h58m
  translating jsps... 46% complete: 2800/6003 [failed: 2800] ETA: 13h8m
  translating jsps... 49% complete: 3000/6003 [failed: 3000] ETA: 12h18m
  translating jsps... 53% complete: 3200/6003 [failed: 3200] ETA: 11h29m
  translating jsps... 56% complete: 3400/6003 [failed: 3400] ETA: 10h39m
  translating jsps... 59% complete: 3600/6003 [failed: 3600] ETA: 9h50m
  translating jsps... 63% complete: 3800/6003 [failed: 3800] ETA: 9h0m
  translating jsps... 66% complete: 4000/6003 [failed: 4000] ETA: 8h11m
  translating jsps... 69% complete: 4200/6003 [failed: 4200] ETA: 7h22m

When you see a such big failure rates in the translation phase and an ETA that spans days, you know it's not just a slow server. You understand that something is fundamentally broken in the environment's ability to compile JSPs.

My initial advice in these situations is always to return to the basics: Prerequisites. When adop hangs or JSPs fail to compile  you must verify: OS-level packages and ensure all required libraries for the Oracle stack are present. You must also ensure the software's internal environment is correctly pointing to the right JDK and compiler paths. Patch Prerequisites should also be verified ( AD/TXK upgrade path doesn't have missing dependencies.)

In this case however; the the solution was specific. The Patch:  38502365, - JSP COMPILATION FAILING AFTER APPLYING PATCH 38501349:R12.CAC.C (Patch)....

Once this specific patch was applied, the JSP compilation proceeded as expected, and the upgrade to Delta 16 was successfully completed. That's it.

So let's conclude our article by linking this point as follows;

as we all know; in the world of EBS, one patch fixes what another one breaks is a reality we often live with. This is why tools like the EBS Critical Patch Update Checker are vital, they help us identify what's missing, but even then (as seen in this case) , keeping an eye on the latest patches and support notes is key.

Remember, knowledge is the only treasure that grows when shared. If you encounter similar hangs, don't just wait for the ETA to count down; check your patches and ensure your prerequisites are rock solid.

Stay technical.