[Pdns-users] Oracle backend connection string.

[a b]

> I also now made a patch that lets you define the location of oracle libs
> and such, and would be grateful if people could test this patch to see if
> it has some problems.
>
> you can find it from http://wiki.powerdns.com/trac/ticket/726

It might be desirable to change this line,

for p1 in /usr/include/oracle /usr/local/include/oracle

to

for p1 in ${ORACLE_HOME}/include

ORACLE_HOME could be supplied on the command line, or obtained from the environment. I have never seen an installation of an Oracle database in /usr/local, and such installation would violate the Linux Standards Base - Filesystem Hierachy Standard, the AT&T SVR4 filesystem specification, as well as Oracle's own Oracle Flexible Architecture standards.

Also on Solaris, third party and unbundled application packages may not deliver any content in /usr, because Solaris sparse zones have /usr mounted loopback, read only since /usr is vendor's space and therefore off limits.

Ditto for the following line:

for p1 in /usr/lib/oracle /usr/local/lib/oracle

On line 440, LDFLAGS="-L$with_oracle_includes -lnnz11 -locci"

was "$with_oracle_libs", rather than "$with_oracle_includes" meant there? Perhaps like this:

LDFLAGS="-L${with_oracle_libs} -R${with_oracle_libs} -lnnz11 -locci"

These are just recommendations-at-first-glance.

Looking at the work done for pdns-3.1 and Oracle, I found this fragment in the "pdns" module of our build engine:

        #
        # For linking in OCI connectivity / "(g)oracle" backend.
        #
        ORACLE_HOME="/${prefix}/oracle/product/10.2.0/db_2"; export ORACLE_HOME
        LDFLAGS="-L/${prefix}/lib/64 -L${ORACLE_HOME}/lib -R${ORIGIN}:${ORIGIN}/../lib/64:${ORIGIN}/../../lib/64:/${prefix}/lib/64:/usr/sfw/lib/64:${ORACLE_HOME}/lib"

...If you keeps this up, Oracle will become a first class citizen in pdns land (:-)