RE: Upgrade 8.0.5 to 8.1.7.3

[Toepke, Kevin M]

Title: RE: Upgrade 8.0.5 to 8.1.7.3

Matt:

 

I don't have the bug#s. When I opened a TAR on this (now unpublished) the support person called me and told me that I had to downgrade the database to workaround the bug. (All the TAR says is that they called me.) The analyst said that bug is one that is fixed in 9.0.2.

 

In our case, whenever a specific stored procedure was called with a certain range or parameters, Oracle would use all of the available memory on the server -- causing the server to crash.

 

Kevin

-----Original Message-----
From: Adams, Matthew (GEA, MABG, 088130) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 17, 2002 11:58 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Upgrade 8.0.5 to 8.1.7.3

Keven,

  Can you supply bug numbers for these bugs?

Matt

----
Matt Adams - GE Appliances - [EMAIL PROTECTED]
Reason is 6/7ths of treason. - The Xtals

-----Original Message-----
From: Toepke, Kevin M [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 17, 2002 11:19 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Upgrade 8.0.5 to 8.1.7.3

Jack:

First of all, there are some serious problems with 8.1.7.3 that can cause
database crashes and corruption. One bug (may be solaris specific) can crash
the box. I would highly recommend that you "only" upgrade to 8.1.7.2 unless
absolutely necessary. We have downgraded all of our 8.1.7.3 databases to
8.1.7.2 (a *very* painful experience)

That said, I never had trouble upgrading directly to 8.1.7.2 directly from
8.1.5.x or 8.1.6.x. We have done in development, staging and production
without any adverse effects. I don't think I've ever done a 8.0.5 to 8.1.7
directly.

Kevin

-----Original Message-----
Sent: Wednesday, April 17, 2002 10:43 AM
To: Multiple recipients of list ORACLE-L

Hi All,

we are in the process of upgrading to 8.1.7.3 some of our databases (now
8.0.5)
According to the Doc's thsi has to be done in two steps
Upgrade to 8.1.7.0.0 followed by and upgrade to 8.1.7.3.0.

This means that we have to upgrade all our databases in one go, or install
another base 8.1.7 install to do some databases later.

On our test system however we have upgraded directly form 8.0.5 and all
seems to be fine.

Anybody care to comment/share their opinions/experiences

TIA

Jack

===================================================================
De informatie verzonden in dit e-mailbericht is vertrouwelijk en is
uitsluitend bestemd voor de geadresseerde. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan
derden is, behoudens voorafgaande schriftelijke toestemming van Ernst &
Young, niet toegestaan. Ernst & Young staat niet in voor de juiste en
volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch
voor tijdige ontvangst daarvan. Ernst & Young kan niet garanderen dat een
verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten
worden overgebracht zonder inbreuk of tussenkomst van onbevoegde derden.

Indien bovenstaand e-mailbericht niet aan u is gericht, verzoeken wij u
vriendelijk doch dringend het e-mailbericht te retourneren aan de verzender
en het origineel en eventuele kopieën te verwijderen en te vernietigen.

Ernst & Young hanteert bij de uitoefening van haar werkzaamheden algemene
voorwaarden, waarin een beperking van aansprakelijkheid is opgenomen. De
algemene voorwaarden worden u op verzoek kosteloos toegezonden.
=====================================================================
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. You should not copy, disclose or distribute this communication
without the authority of Ernst & Young. Ernst & Young is neither liable for
the proper and complete transmission of the information contained in this
communication nor for any delay in its receipt. Ernst & Young does not
guarantee that the integrity of this communication has been maintained nor
that the communication is free of viruses, interceptions or interference.

If you are not the intended recipient of this communication please return
the communication to the sender and delete and destroy all copies.

In carrying out its engagements, Ernst & Young applies general terms and
conditions, which contain a clause that limits its liability. A copy of
these terms and conditions is available on request free of charge.
===================================================================

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jack van Zanen
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Toepke, Kevin M
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).