Oracle 8.0.5, WAS 3.0.2, Redhat 6.1

Question

I recently had Redhat 5.2, Oracle 8.0.5 and WAS 3.0.2 running perfectly. I decided to upgrade the O/S to 6.1. According to Oracle, I have to apply a patch to get the databases to work (Or at least to be certified). I did not apply the patch and
the database seems to be working fine. Does anyone know if I have to apply the patch or recompile the Oracle code?
2nd, I am having problems with WAS 3.0.2 and RH 6.1. I can't seem to start the wrb processes (owsctl start wrb). I am getting a: Error in opening UDP:laptop:2649 message. I think I ran into this before. I don't remember how to fix it. Has anyone else ran into this? Does WAS 3.0.2 work with 6.1 or do I have to go to 4.0.7? Do I need to recompile these executables with the 2.0 libraries like I'm suppose to do with Oracle?
Any help is appreciated.
-Jim Wartnick
null

Answer 1

I would not blame ORACLE - I think the problem is
with the EGCS and the libraries.
I have emails from the linux.devel on these.
For e.g. a simple program such as
#include "stdio.h"
FILE *fp = stderr;
main() {
gives error on Redhat 6.0, Caldera 2.2!
It works on Solaris, IRIX, AIX, Redhat 5.2 and
even with Visual C++ 6!
I have had other programs such as pdksh (ksh) also
dumping on Redhat 6.0 and Caldera 2.2
(even after I compile everything from source!).
I have also had nothing but trouble with other databases
on 6.0. I think new kernels should go through a lot more
testing before being released like this.
I am also debating whether to move back to Redhat 5.2!
Freddy Wissing (guest) wrote:
: Oracle Development Team wrote:
: : Oracle 8.0.5.x is certified on GLIBC 2.1 system and a patch
: : is available for this.
: : The patch available for download contains two files -
: : README including instructions for applying the patch and
: : the patch file glibcpatch.tgz (compressed tar). Follow the
: : instructions provided in the README to apply this patch.
: : This patch is available for both 8.0.5 Standard and
Enterprise
: : Editions of Oracle.
: : Get Technical!
: : http://technet.oracle.com
: I agree with the others. Referring back to an older library
: merely for compatibility's sake is different from forward
: motion. I 've been having nuttin' but trouble with the compat
: stuff, and now my pro-c stuff won't work at all. (separate
post)
: There needs to be REAL glibc-2.1 linking. I hesitate to run
: anything important (no less mission critical) on top of these
: compat packages, and it's truly making me rethink my strategy
of
: using RedHat/Oracle unless I revert back to RedHat 5.2, which I
: liked.
: If you are already publishing a real fix for this, please
: disregard. Otherwise, please do us this favor. There's a
: tremendous RedHat 6.0 population out there.
: Freddy Wissing
null