Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re^2: DBD::Sybase 1.14 for ActiveState Perl 5.16 Windows 32bit and 64bit

by jfroebe (Parson)
on Mar 07, 2013 at 13:09 UTC ( #1022225=note: print w/replies, xml ) Need Help??


in reply to Re: DBD::Sybase 1.14 for ActiveState Perl 5.16 Windows 32bit and 64bit
in thread DBD::Sybase 1.14 for ActiveState Perl 5.16 Windows 32bit and 64bit

thanks! You're absolutely correct.

Sybase Openclient is included in the Sybase Developer's Kit, and ASE PC Client. If you don't have a current subscription from Sybase, you can download the ASE 15.7 Developer Edition for Windows which will include it.

Jason L. Froebe

Blog, Tech Blog

  • Comment on Re^2: DBD::Sybase 1.14 for ActiveState Perl 5.16 Windows 32bit and 64bit

Replies are listed 'Best First'.
Re^3: DBD::Sybase 1.14 for ActiveState Perl 5.16 Windows 32bit and 64bit
by rammoorthi (Novice) on Apr 29, 2013 at 07:11 UTC
    Hi,

    I am getting error after installing dbd::sybase1.14 package.

    The error is

    The application or DLL C:\Perl\site\lib\auto\dbd\sybase\sybase.dll is +not a valid windows image. Please check this against your installatio +n diskette.

    I am using window xp and 32 bit os. active perl version is 5.16. I am trying to connect a sybase database which is remote server actually(sybase is not installed in my machine)

    few info are
    C:\Documents and Settings\Admin>perldoc -l DBD::Sybase C:\Perl\site\lib\DBD\Sybase.pm
    Should i install any other client side s/w or anything. Please help.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1022225]
help
Chatterbox?
[tye]: probably something in the init subsystem that does the mounting that you could disable and reboot.
davido needs to close laptop to board flight home from yapc.
[davido]: I'll look into it in a few hours probably.
[davido]: when i do get to that point I think I'll do it in a vm snapshot just in case. :)
[oiskuu]: tye, you were right: loginuid/sessionid are part of task struct if compiled with AUDITSYSCALL. I have some doubts if you should actually depend on that feature.
[Corion]: oiskuu: Depends on what you want to do with that information
[tye]: I'm not depending on that feature. But I could in this environment. I'm using getlogin(). shrug
[Corion]: For benign logging (which user started this DB instance), it's OK
[tye]: We use auditd for security monitoring. So we can rely on auditing being enabled. I'm not sure who would want to not be able to audit. Maybe some VM inside another system with audit?

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2017-06-23 20:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How many monitors do you use while coding?















    Results (555 votes). Check out past polls.