Looking at the SO post you linked to, the bug in question was fixed in 10.2.0.5 (and 10.2.0.4 Patch 2 on Windows). It wouldn't be shocking if the fix was backported to the 9.2.0.8 patchset-- I believe 9.2 was still within the support window when the 10.2.0.4 patchset was released.
Since extended support for Oracle 10.2 ends this month and 9.2 support ended years ago, I'd be curious about why you are testing the application against a 9.2 database today. At this point, if you're going to upgrade, it would seem likely that you'd want to upgrade to something that was still in support. That would mean, realistically, 11.2.