Re: DBD-SQLAnywhere-1.16

Richard T Malafa wrote:

Hi Martin,
That is very interesting information. I see all linux but no HPUX or SUN machines in that list. Using HP UX 11i V2 on this test machine.

I didn't have any problems with the environment variables. As a matter of fact I've installed the sqlanywhere version 10. Before you can bring up the server version using "dbsrv10" (don't use dbeng10 - that is for a personal DB and it won't propagate to another machine in your network) You have to install the environment variables by sourcing it either "sa_config.sh" or "sa_config.csh". That will take care of all the environment variables for you.

Then bring up the server with "dbsrv10 -n demo10 /opt/sqlanywhere10/demo.db -ud". The server is brought up for sanity testing..
You can run dblocate to check this.
root@wsmisdb2> dblocate
SQL Anywhere Server Enumeration Utility Version 10.0.1.3419
Server Name Address
----------- -------
demo10 wsmisdb2.cscproj.local:2638 this is the one we just brought up
sqldbserver mars1.cscproj.local:2638 different sql server - not sybase
You then can get through "perl Makefile.PL" and "make". There is a notice about some missing debug code in make but no errors generated.

The show stopper is in "make test". In the "t" subdirectory you have to change every instance at the top of the location of perl if you're not using their location.
That's minor.

The killer is in trying to connect to the database, It just hangs there. You can use the "dbisqlc" command line utility to check that the connect is working and use select statements.

I haven't been able to figure out yet why it hangs at the connect test in "make test" yet.

How did you get that ""Please set the SQLANYxx environment variable (where xx is version number)" and most of the tests
were automated ones." message???? Right after running "make test"??? Did you run "sa_config.sh" or "sa_config.csh" first???

Thanks
Rich

I didn't get "Please set the SQLANYxx environment variable (where xx is version number)" as a message. I just saw that for those people who had reported a test failure to cpan-testers they nearly all got it - see http://www.cpantesters.org/show/DBD-SQLAnywhere.html#DBD-SQLAnywhere-1.16 and click on a few failures. I don't have DBD::SQLAnywhere installed at all - I only thought a) there may be some failures in the test results that you'd find useful and b) you didn't actually tell us what did not work. Beyond, that I do use Adaptive Server Anywhere.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

*Martin Evans <martin.evans@xxxxxxxxxxxx>*

09/23/2008 09:52 AM


To
dbi-users@xxxxxxxx
cc

Subject
Re: DBD-SQLAnywhere-1.16








Richard T Malafa wrote:
> Greeting,
>
> Has anyone been successful installing DBD-SQLAnywhere-1.16 on a HP-UX
> machine???
>
> Thank You
> Rich

According to

http://www.cpantesters.org/show/DBD-SQLAnywhere.html#DBD-SQLAnywhere-1.16

no one has reported a result on HP-UX and in fact all are failures.
However this may just be because it says "Please set the SQLANYxx
environment variable (where xx is version number)" and most of the tests
were automated ones.

Have not tried it myself.

Your posting implies you might be having problems installing - if so
what were they.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

.

Relevant Pages

  • Re: persisten enviroment variables - where and how to set them
    ... variables to the startup script why wasn't it added in the original ... I then realised how would the install know ... >> command and found that the application server was running. ... all its environment variables go with it. ...
    (comp.unix.solaris)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)