8.0.5 / RedHat 6 / static or dynamically linked binaries

Question

It does appear that you can run Oracle 8.0.5 on RedHat 6, despite
the glibc 2.1 linking problems. Whenever I run an Oracle binary,
I get a core dump. Not good. But when I replace the
dynamically linked binaries with the statically linked ones (by
copying them directly over the old ones in $ORACLE_HOME/bin/ ),
everything seems to work fine.
My question is, what's the downside, if any, of this approach?
I'm concerned mostly with performance, as I'm not just playing
around with this stuff. All our development and test servers are
going to Oracle on Linux. If the old RedHat 5.2 + gclibc 2.0.x
is better, I'd like to know before I implement the RedHat 6 /
8.0.5 solution.
Thanks!
null

Answer 1

Patrick (guest) wrote:
: Alan Mullett (guest) wrote:
: : Checkout http://www.redhat.com/corp/support/errata/rh60-
errata-
: : general.html which says:
: : "Oracle will work on Red Hat Linux 6.0, but you will need to
: use
: : the "compat" packages in order to relink Oracle, if you need
: to
: : do so. You will need to patch the Oracle Makefiles to use
the
: : correct linker from the "compat" packages in order to do
so.
: In
: : order to install Oracle on Red Hat Linux 6.0, you will need
to
: : choose not to create a database at install time; wait until
: : after you have relinked Oracle to create a database."
: : I HAVE NOT TRIED THIS YET BUT WILL LET YOU KNOW HERE (emails
: : will be ignored)
: : Jason Gerry (guest) wrote:
: : : It does appear that you can run Oracle 8.0.5 on RedHat 6,
: : despite
: : : the glibc 2.1 linking problems. Whenever I run an Oracle
: : binary,
: : : I get a core dump. Not good. But when I replace the
: : : dynamically linked binaries with the statically linked
ones
: : (by
: : : copying them directly over the old ones in
: : $ORACLE_HOME/bin/ ),
: : : everything seems to work fine.
: : : My question is, what's the downside, if any, of this
: approach?
: : : I'm concerned mostly with performance, as I'm not just
: playing
: : : around with this stuff. All our development and test
servers
: : are
: : : going to Oracle on Linux. If the old RedHat 5.2 + gclibc
: 2.0.x
: : : is better, I'd like to know before I implement the RedHat
: 6 /
: : : 8.0.5 solution.
: : : Thanks!
: I can't get it to work.
: LINUX memory errors when I try to create database objects and
: start them up.
I am running ORACLE 8.0.5 on Caldera OpenLinux 2.2
successfully -
I can bring up database, shutdown, run sqlplus, etc.
But I AM having problems linking executables with ORACLE
libraries!
I have heard that the problem is with the new compilers
(EGCS instead of GCC). Looks like GNU has given the compiler
stuff to a company called Cygnus.
Personally, I liked the old gcc on 5.2 - lots more stable
and was compiling more of my programs.
FOr e.g.
the new compiler gives error on
#include "stdio.h"
FILE *fp = stderr;
main() {
All compilers including Redhat 5.2, IRIX, AIX, SOLARIS
and even Visual C++ 6.0 compile the above code!
Cygnus claims that this is how it is supposed to work.
Anyway, let's see what happens.
null