Re: Upgrade to 10G from 9.2.0.7

  • From: "Arul Ramachandran" <contactarul@xxxxxxxxx>
  • To: gkatteri@xxxxxxxxxxx
  • Date: Tue, 23 Jan 2007 10:09:40 -0800

Hi GovindanK,

Do you know if the 10.2.0.3 re-release is for all platforms? If it is
platform specific, would you know which platforms would need the re-release?

Thanks
Arul

On 1/22/07, GovindanK <gkatteri@xxxxxxxxxxx> wrote:

 The last patch i have mentioned has that. Anyhow, we too are moving to
10.2.0.3; But we have decided to wait for Oracle to Re-Release 10.2.0.3which 
they said (last week) will be available in two weeks. So , we are one
week away from downloading it again. We have temporarily halted our move to
10.2.0.3 for a week.  The reason i am saying this is some db's created in
8i fail during upgrade. Oracle will be providing fix for that when then
Re-Release 10.2.0.3;

HTH

GovindanK

On Mon, 22 Jan 2007 13:30:30 -0500, "Arnold, Sandra" <ArnoldS@xxxxxxxx>
said:

I suggest that you upgrade to 10.2.0.3 because that patchset has the new
Daylight Savings Time changes.  Also, if you upgrade to that version you
will need to the Mandatory Patch 5752399 for 10.2.0.3 on Solaris 64-bt and
Filesystems Managed by Veritas or Solstice Disk Suite software prior to
starting up your database.  I just applied both of the patches to my
Dev/Test server over the weekend.

------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *GovindanK
*Sent:* Monday, January 22, 2007 1:14 PM
*To:* Brandon.Allen@xxxxxxxxxxx; oracledba.williams@xxxxxxxxx;
achoto@xxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
*Subject:* RE: Upgrade to 10G from 9.2.0.7

Here is a summary for 10.2.0.2

5415881 WRONG SORT ORDER RETURNED BY QUERY
4748222 UPDATE COLUMN WITH TDE CAUSES OERI: [ZTSMDWL FAILED] IF THERE IS A
TRIGGER
5117016 LIBSERVER10.A INCORRECTLY LOCATED IN $ORACLE_HOME/RDBMS/LIB/
5380055 ORA-01555 ON ALL INSTANCES AFTER SWITCHOVER AND SWITCHBACK.
5752399 10203 SOLARIS64 IOCTL VERITAS

Some are applicable for 10.1.0.5 and 10.2.0.1; Verify with the "Patch"
page on Metalink.

HTH

GovindanK






--
Arul

Other related posts: