At 3:50 PM -0600 3/24/05, Michael Leo wrote:
>Gang,
>
>I have two Solaris SPARC machines, gilligan and tonga. Gilligan
>is running the 32 bit kernel:
>
> gilligan% isainfo -kv
> 32-bit sparc kernel modules
> gilligan%
>
>while tonga is running the 64-bit kernel:
>
> tonga% isainfo -kv
> 64-bit sparcv9 kernel modules
> tonga%
>
>I installed Ingres Version II 3.0.1 (su9.us5/109) on both
>machines. During the install on gilligan, the system
>indicated that "there is no 64 bit support on this machine,
>installing in 32 bit mode".
>
>When I installed on tonga, there was no such warning.
>
>However, now that they are both installed, I fail to see
>any difference between them....
>
>My question is ... finally ... did I get the 64-bit version installed on
>tonga? And if so, how can I tell?

The solaris build is a hybrid. (At least in r3 it is, not sure about
the earlier releases.) What that means is that you get both 32 and
64 bit versions in one package. The 64-bit executables are in .../lp64
subdirectories. (bin/lp64, lib/lp64, etc.)
You normally run the 32-bit one first. The first thing one of the 32-bit
executables will do is look for the ingres variable
II_LP64_ENABLED
and if it's set (I don't believe the value matters, but I'd have to
look to be sure), the executable immediately exec's off to the lp64
version.

So, look for lp64 subdirectories, and check your ingprenv for
II_LP64_ENABLED.

You'll also have to do the right things with LD_LIBRARY_PATH.
What works best for me is to keep LD_LIBRARY_PATH set for 32-bit,
and define LD_LIBRARY_PATH_64 pointing to the lib/lp64 subdirectory.

I don't know if there is a dbmsinfo() defined to check which server
you're actually running -- that might be a useful thing if it's not
there now.

Karl