Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Michael Peppler <mpeppler at peppler dot org>
Subject: Re: Change in Sybase Home Directory
Date: Mar 21 2005 8:33PM

On Mon, 2005-03-21 at 21:24, McCarthy, John wrote:
> On our HP unix system, we have a file name " /usr/local/sybase " that
> until recently was "linked" to our Sybase 12.0 directory.  After
> changing the link to point to our Sybase 12.5.3 directory, we get many
> errors from applications using Sybperl, DBlib, and/or CTlib.  Here are
> two examples:
> ----------------------------------------------- Ex. 1
> 				Can't load '/usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/auto/Sybase/DBlib/' for module Sybase::DBlib: No such file or directory at /usr/local/apps/perl5/lib/5.00503/PA-RISC2.0/ line 169.
> 				    at /usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/Sybase/ line 79
> 				    BEGIN failed--compilation aborted at /usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/Sybase/ line 79.
>    BEGIN failed--compilation aborted at /share/test/export/avt10/script/ line 81.
> ----------------------------------------------- Ex. 2
> 	Can't load '/usr/local/apps/perl-5.6.0/lib/site_perl/5.6.0/PA-RISC2.0/auto/Sybase/CTlib/' for module Sybase::CTlib: No such file or
> 	directory at /usr/local/apps/perl-5.6.0/lib/5.6.0/PA-RISC2.0/ line 200.
> 	 at /share/test/import/sgt10/script/ line 373
> Compilation failed in require at /share/test/import/sgt10/script/ line 373.
> -----------------------------------------------
> The "" and files that cannot be loaded do exist with the proper permissions.  Here is " ls -l " for the file:
>   -r-xr-xr-x   1 root       sys         159744 Jun 29  2000 /usr/local/apps/perl-5.6.0/lib/site_perl/5.6.0/PA-RISC2.0/auto/Sybase/CTlib/
> Is this behavior expected when changing the location of the Sybase binaries?
> We were able to solve this problem (for now) by resetting the link back to its prior value.   Is there any other way to resolve this problem?

The best solution would be to rebuild the Sybase::* modules against the
12.5.3 tree - this would be a good idea in any case as the two may not
be binary compatible.

Alternatively you may need to play around with LD_LIBRARY_PATH (or
SHLIB_PATH, or whatever HP-UX uses...) to see if you can get the dynamic
loader to work.

Michael Peppler  -  -
Sybase DBA/Developer
Sybase on Linux FAQ: