Hi,

this is not a direct answer to your question, but just a comment based on what you asked for.

You want to migrate an old Perl codebase to the version 5.16 of Perl. That means that you have to test the whole codebase whether it behaves like before. I don't know how you do it. Probably you have good unit tests or you have to do it with integration tests. It seems that all functions of Oraperl begin with 'ora_' so that you can grep all occurences easily. It would be intersting to see if it's not feasible to migrate Oraperl to DBI and DBD::Oracle too.

You have to test all anyways. What do you think?

Regards
McA

Unless you are being ordered to use oraperl with no hope of appeal, use DBI / DBD::Oracle. Oraperl, like sybperl and many other customized perls add a level of complexity to any troubleshooting/debugging efforts.

DBD::Oracle once included a compatibility module named Oraperl that allowed using ancient oraperl scripts with the newer DBI+DBD::Oracle. According to the Changelog, Oraperl was removed from DBD::Oracle with Version 1.51_00 a.k.a. 1.52 in 2012. The good news is that there should be a separate distribution for Oraperl:

RT78987 - removed Oraperl.pm and oraperl.ph; these files will be available in a separate distribution named "Oraperl" (David Perry)

And lo and behold, CPAN knows about a distribution named Oraperl.

So your chances look pretty good to be able to use DBI, DBD::Oracle, and Oraperl to run your old code unmodified except for adding a use Oraperl; line. You just have to install Oraperl as usual (cpan Oraperl on Strawberry, some ppm voodoo on ActivePerl.) Oraperl depends on DBI and DBD::Oracle, so both the cpan tool and ppm should install them automatically (unless they are already installed).

Alexander