A logistics operator's core PowerBuilder application jumped from PB 5.0 all the way to PB 2025 — coordinated with an Oracle 10g to 23ai database upgrade running as one program, not two.
A logistics operator's core operations application had been running on PowerBuilder 5.0 for decades, paired with an Oracle 10g database that had reached the same point of unsupportability. Neither side of the stack could be upgraded in isolation.
PB 5.0 predated nearly every modern language feature, connectivity option, and security standard now required — 15 major releases behind current, with no vendor support and a shrinking pool of engineers who could safely touch it.
Oracle 10g was as unsupportable as the PowerBuilder layer sitting on top of it — upgrading one without the other would have meant validating an old application against a new database driver stack, or vice versa, with no clean fallback.
The application ran core day-to-day operations — there was no maintenance window long enough to take it offline for a rebuild, and no appetite to risk business continuity on a rewrite.
The application and database upgrade paths were planned and executed together from day one, so neither side ever had to run against an incompatible version of the other.
Full codebase scanned to catalogue deprecated syntax, DLL and OLE dependencies, and every point where the application code assumed Oracle 10g-specific behavior.
Oracle DB Ascend mapped the direct 10g → 23ai transformation path, identifying deprecated features, data type changes, and PL/SQL adjustments needed ahead of the application upgrade.
The application moved through validated intermediate PowerBuilder releases on the way to PB 2025, with each stage tested against a parallel, upgraded Oracle environment rather than the legacy 10g instance.
Application and database changes were regression-tested together at every milestone — no PowerBuilder release was signed off against a database version it wouldn't run against in production.
Application and database went live together in one coordinated cutover, followed by 30-day hypercare monitoring across both layers of the stack.
"We weren't just behind on PowerBuilder — we were behind on both ends of the stack at once. Running the two upgrades as one program is what made this achievable without stopping the business." — OptiSol Version Upgrade Lead
Let's Talk
Tell us what you are running today and where you need expert support.
"*" indicates required fields
Global Presence
Five global locations. One connected engineering team.
North America
Chennai · Coimbatore
Client services
Regional operations
Client services
