RE: DBI::PurePerl and DBD::Oracle...

Check.

Correct. The DBI::PurePerl does not include the DBD::Oracle. They do
however work together though, as the tests conducted "after" the make
install worked against my Oracle::XE database.

All the failed test were from the same type of problem. The test could
not load a given DBI and/or DBD::Oracle module in the current @INC.
This kinda hinted to me that it simply couldn't find a needed *.pm file,
which might explain that I haven't set some crucial ${ENV} before
conducting the make test. Given the above @INC issue, I just figured if
I installed the modules, then the @INC issue would disappear...turns out
it worked in my case.

The reason I went with PurePerl is availability of the target machine.
We have little to no control over the Unix/AIX machines we are putting
these modules on. As such, since Perl is already on the machines, the
PurePerl distos involve less red-tape to get them in place. Also,
performance is not a concern, as we are using DBI and DBD mostly for
simple tools and reports running under cron.

Anyway, I'll play around with the install and see if any problems crop
up...


thx,

Adym Lincoln
I/S Corporate - I/S Internal Applications
603-245-3744
Ext : 53744
adym.lincoln@xxxxxxxxxxxxxxxxx

....
Basic Math : Music * Audio = Emotion
Adym Math : Green Day * JBL = Happiness ...
....

-----Original Message-----
From: Jeff Zucker [mailto:jeff@xxxxxxxxxxxxxx]
Sent: Tuesday, August 29, 2006 12:49 PM
To: Lincoln, Adym
Cc: dbi-users@xxxxxxxx
Subject: Re: DBI::PurePerl and DBD::Oracle...

Lincoln, Adym wrote:
Hi all,

Just trying to understand the instructions on both these packages.

The main thing to understand is that DBI::PurePerl is meant to work only

with DBDs that are pure Perl (have no C/XS component) and AFAIK, that
does *not* include DBD::Oracle. You might be able to access Oracle
using DBI::PurePerl via DBD::Proxy, but I doubt it will work directly.

Is there a reason you are trying PurePerl rather than plain DBI?
I guess I'm trying to understand "why" we run the make test prior to
running the make install?

The general idea is that you should only install software that works so
you test first, then if it works, install it. In some cases you can
force an install even if the tests fail but that is opening yourself to
the possibility of failure in production.

In cases such as yours where the tests work better after install, the
chances are that there are some environment variables that are not set
in your test environment so I'd recommend looking at and setting the
environment variables required for DBD::Oracle and then doing the make
test.

--
Jeff
.

Relevant Pages

  • Re: Warp Rogue - SDL help wanted
    ... and the JRE isn't trivialy sized either. ... install those wierd things". ... environment variables, ... GodMode: Boolean = False; ...
    (rec.games.roguelike.development)
  • RE: Environment issues Please help
    ... install an MSI if not installed ... This is becourse the vbscript doen't expands the new installed windows ... It will: 1- wright to registry ... To add and to ACTIVATE new environment variables you need a thirdparty tool ...
    (microsoft.public.scripting.vbscript)
  • RE: Office 2007 Install Error 2203
    ... Sorry for this delayed response due to the weekend. ... It seems that re-set the environment variables fixed this issue. ... guess was that Windows used C:\Temp as a temporary folder used for the ... Since you can install and run Office 2007 Beta without a ...
    (microsoft.public.office.setup)
  • Re: preparing for the next open-source gfortran release
    ... under a new account, you should not get the problem. ... The distribution 4.3.0-20080127 does not have g++. ... This is problem of environment variables. ... install two distributions on Windows. ...
    (comp.lang.fortran)
  • Re: Word 2007 on term session - "Word could not create the work file"
    ... Was the TS in install mode during installation of Office? ... might have to update/add the shadow key in the Terminal Services ... System environment variables: ...
    (microsoft.public.windows.terminal_services)