On February 5, 2003 10:29 am, [EMAIL PROTECTED] wrote:
> Hello,
>
> My environment is as follows:
>
> AIX 4.3.3.0 running perl 5.005_03
> Installed DBI 1.32
> Installed DB2 vsn 7.2
>
> I'm requiring install of the DBD::DB2 driver onto a number of AIX RS6000
> machines.  The install originally failed compilation because I hadn't
> installed the DB2 Application Development Client.
>
> I've been told by our DBA that the Application Development Client could be
> installed onto one of our test boxes in order to install DBD::DB2 to that
> box, however it is not allowed on any of the Live boxes.  My question

That's strange.  In version 7, you need the Application Development Client 
installed on your live boxes if you want to compile SQL stored procedures.  
Further, there's no licensing for the App Dev Client, and thus won't cost 
HSBC any more money.

> therefore is would it be feasible to install DBI and DBD::DB2 on one RS6000
> and then copy the compiled code to the 'Live' boxes (all running the same
> version of Perl), without the need to install from scratch?  (and by
> implication, without the need to install then Application Development
> Client on the Live boxes or compile any code on these boxes).

The DBD::DB2 driver should not need the App Dev Client to *run*, only to 
compile.  Thus if your perl is compiled with the same compiler on all AIX 
boxes (which is very likely), and you use the same compiler to compile your 
driver, it should work.

Hint: (not that I've tried this before)  Try compiling it/testing it on one 
box, and then tar up the entire DBD-DB2-0.76 (or whatever version you're 
using) directory after the make/make test/make install is complete.  Take 
that tarball to the next machine, and try make test/make install.  Unless 
others on this list think this is a Bad Idea in general, I'm guessing it 
should work fine.  The advantage is that perl is still doing the installation 
everywhere.

> Any help would be greatly appreciated, otherwise I doubt we will be able to
> use DBI at all and will have to code our own database interface.

Yes, and that would definitely suck.

Reply via email to