[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tru64-unix-managers
Subject:    SUMMARY: write errors - 5.1A PK5 & Oracle Problems?
From:       Charles Ballowe <hangman () steelballs ! org>
Date:       2003-09-29 19:57:26
[Download RAW message or body]

Huge thanks to Jean-Marc VINCENT of HP for the fix to my problem. His
message and my question are below.

-Charlie

------------------------------
> From jean-marc.vincent@hp.com Sat Sep 27 08:00:26 2003
Subject: RE: update: write errors - 5.1A PK5 & Oracle problems?
Date: Sat, 27 Sep 2003 09:59:56 +0200
From: "Vincent, Jean-marc" <jean-marc.vincent@hp.com>
To: "Charles Ballowe" <hangman@steelballs.org>

Hi Charles,

There is a fix for your current issue and is available as an ERP.

Please take a look at \
http://ftp.support.compaq.com/patches/public/unix/v5.1a/t64kit0019900-v51ab23-e-20030906.README \
to get information how to retrieve it.

Hope this will help you.

Regards,

VINCENT Jean-Marc
Tru64(tm) UNIX Technical Consultant - Tru64(tm) UNIX Ambassador
HP France
33(0)1-6982-5733
jean-marc.vincent@hp.com

 -----Original Message-----
From: 	Charles Ballowe [mailto:hangman@steelballs.org] 
Sent:	Saturday, September 27, 2003 8:26 AM
To:	tru64-unix-managers@ornl.gov
Subject:	update: write errors - 5.1A PK5 & Oracle problems?

The question I asked earlier about the DBAs seeing write errors seems to
be misleading - we've ruled out hardware or OS problems pretty much. It looks
like it might be an incompatibility of some form between 5.1A PK5 (just
applied the patches this weekend) and Oracle 8.1.7.4 but I can't get any
confirmation on that from anybody. Oracle insists it's not their problem,
but nothing I do outside of Oracle can reproduce the problem.

Has anybody else run into this problem before? Any known bugs between 8i and
5.1A PK5? This didn't come up on our test and development systems, but 
the DBAs have managed to get a script from oracle's developers that trigger
it on them. Aparently whatever level of activity on test and dev for the month
that it was on them wasn't enough to expose the problem.

I hope someone has some insight on this and is awake/gets this over the 
weekend.

-Charlie


[prev in list] [next in list] [prev in thread] [next in thread]