Any Proactive measures for 10GR2 when upgrading from W2K3 to W2K3 EE

Question

Current environment
SQL> select banner from v$version;
BANNER
Oracle Database 10g Release 10.2.0.2.0 - Production
PL/SQL Release 10.2.0.2.0 - Production
CORE 10.2.0.2.0 Production
TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
NLSRTL Version 10.2.0.2.0 - Production
We are planning an OS upgrade from windows 2003 stand edition to Windows 2003 enterprise edition.
1) From the ORACLE prospective will there be any bottlenecks.
2) Are they any proactive measures i need to take.If so can you provide me link to a doc which might be helpful
Any comments are appreciated.

Answer 1

Both Windows 2003 Standard Edition and Enterprise Edition are certified platforms for Oracle 10g Rel. 2.
I can see you are currently working with patchset 10.2.0.2.0. You didn't mention if you are planning to upgrade to 10.2.0.3.0 but if you are willing to do so, there are several issues reported by the oracle community, I have included verbatim transcripts from the referred sites, just to name a few:
http://www.pythian.com/blogs/356/oracle-10203-patchset-known-issues-and-bugs
Other platforms to watch out with 10.2.0.3 patchset are Windows and Linux 32 bit - Metalink Note 403616.1 “Many Child Cursors create in 10.2.0.3 on Windows and Linux”. This will likely affect applications with heavy usage of bind variables (perhaps, ones with cursor_sharing=force/similar as well) and busy OLTP is a good candidate. See for yourself the note I mentioned above - it describes some symptoms and consequences (latch contention, ORA-4031, ORA-600) pretty well. The good news is that Linux platform has one-off patch available already - patch 5705795.
http://www.pythian.com/blogs/335/oracle-10203-patchset-is-out
Oracle 10.2.0.3 patchset is out
December 5th, 2006 - by Marc Fielding
My colleague Vamsi Chikkam noticed that the Oracle 10.2.0.3 patchset has been released for Linux and Windows 32-bit. The major bugfixes are the same as my original post with a few additions:
* Identical SQL run in different schemas may modify the wrong schema’s tables (bug 5458753)… we have run into this problem at a client site and it’s not pretty. Workarounds include qualifying schema names in SQL and one-off patches for 10.2.0.2. MetaLink note 329673.1 has more details.
* When cursors are being reloaded frequently in the shared pool, PLS-306/ORA-1722/ORA-1858 errors can occur (bug 4752541)
* Under Windows platforms, triggers referencing :NEW/:OLD using NCHAR/NVARCHAR character sets can error out (bug 5388136)
* The same issue as bug 5388136 above also causes compilation errors on 10.2.0.2 databases upgraded from previous releases under Windows(bug 5383828)
http://www.orafaq.com/maillist/oracle-l/2007/03/05/0329.htm
To inform you about important information regarding your software, Oracle is notifying you of an issue discovered in a recent download of a database patch set or bundle. This issue affects the following patch sets and bundles (hereinafter "Patch Set"):
* 10.2.0.3 all ports
* Windows 32 and 64 bit patch bundles: + 9.2.0.7 Bundle 13, 14, 15 + 9.2.0.8 Bundle 2, 3 and 4 + 10.1.0.5 Bundle 9, 10, 11 + 10.2.0.2 Bundle 9, 10, 11, 12, 13 + 10.2.0.3 Bundle 1
Oracle believes that the number of customers with user data that may be affected by this Patch Set is small; however, the information contained in this announcement is intended to help you determine if your data may be affected and what to do if it is. Please read through this message in its entirety to determine if you have the issue and be sure to perform all recommended steps before contacting support. This information should be maintained for your reference as necessary.
Due to 2007 U.S. and Canadian changes to Daylight Saving Time, you may have stored timestamp data in your Oracle database which was not previously within Daylight Saving Time, but is now included (e.g., timestamp data with dates falling between March 11, 2007 and April 1, 2007). Such data must be corrected BEFORE installing a Patch Set into your Oracle Database. The instructions to detect and correct affected data prior to installing Patch Set are documented in MetaLink (for more information, see MetaLink [1]Note ID # 359145.1).
~ Madrid
http://hrivera99.blogspot.com/