You basically need to include a large chunk of the $SYBASE directory. You're better off simply making the installation of Sybase (now SAP) Open Client a requirement.

Please note, that while DBD::Sybase is pretty forgiving on the *nixes for binding against different Openclient releases, it is a real bugger in the Windows world. If your environment is Windows, use ODBC.

HOWTO: BUILDING PERL MODULE DBD::SYBASE 1.15 FOR ACTIVESTATE PERL (WINDOWS 32BIT) 5.16.3 USING THE MINGW COMPILER if you need to

Dear Monks, Thanks for your reply, I really don't want to make the Sybase Open Client as a requirement and if possible bundle the required dll/obj files with my appplication. The error which I get when I bundle most of the dll's is The context allocation routine failed when it tried to load localization files!! One or more following problems may caused the failure Your sybase home directory is c:\sql10. Your sybase home directory is c:\sql10. Check the environment variable SYBASE if it is not the one you want! Check the environment variable SYBASE if it is not the one you want! Cannot access file c:\sql10\ini\objectid.dat I have bundled the objectid.dat file also in my application exe, I still get this error as well DBD_alloc method fails. Thanks, Mansi

The official method is to install OpenClient. If you want a self contained binary, you're basically out of luck.

Another option is to use Sybase's JDBC driver (jConnect) with DBD::JDBC. However, using DBD::JDBC will require you to have Java installed somewhere... then it comes down to, if you require Java, why are you using Perl? Catch-22

Jason L. Froebe

Blog, Tech Blog

Just an update, the exact error for alloc method is: DBD::Sybase initialize :cx_ctx_alloc(112) failed at PERL2EXE/STORAGE/Dynaloader.pm line 214.

OK...i guess too: What about your Sybase environment?

IMHO you should have this in your app:

BEGIN {
    $ENV{LANG}=q(C);
    $ENV{SYBASE}=q(/opt/sybase);
}
[download]

And what about the errors you get :-(

Update:

Seems my post is off topic too...

Update2:

Reading my post again the day after i think it wasn't so inferior as suspected.

As jfroebe wrote:

"You basically need to include a large chunk of the $SYBASE directory. You're better off simply making the installation of Sybase (now SAP) Open Client a requirement."

In other words: "What about the Sybase environment?"

BTW, another (old) story about perl2exe by merlyn: perl2exe - no more secrets.

Regards, Karl

It would probably be more helpful to pinpoint the problem you indicate you're having. If you indicated what the "error" you get, actually is. :)

--Chris

Yes. What say about me, is true.

This might be slightly off topic, but, what is the Sybase client licensing model? Does Sybase allow unlimited client software installs, or are they limited? If they are limited then what you are attempting may be in violation of your license.

Sybase licensing is at the server level.

Jason L. Froebe

Blog, Tech Blog

That is sane. Not having sysbase experience, I didn't know if they might be using a dinosaur licensing model.