Oracle 10.2.0.3 patchset is out

By Marc Fielding December 5th, 2006 at 12:00 pm
Posted in Group Blog Posts

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)
These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Google
  • del.icio.us
  • Facebook
  • bodytext
  • Technorati
  • TwitThis
  • Reddit

One Response to “Oracle 10.2.0.3 patchset is out”

  1. Noons Says:

    I’ve seen that 5458753 problem since 9.2.0.6, in Linux!
    Been trying to find any reference on it for ages, thanks for this post.

    Unbelievable that such a BASIC security flaw is in Oracle’s code all the way
    to 10gr2 and NO ONE has fixed it yet except, presumably, in the 2.0.3 patchset!

    About time Oracle started fixing the basics of their flagship product rather than spending their R&D in flights of fancy and “flavour of the day” technologies!

Leave a Reply

Filling out the following captcha not only allows us to cut down on automated blogspam but also helps digitize books. Please feel free to send comments on this approach directly to Paul at vallee@pythian.com.

NOTE: After submitting your comment, verify that it is added to the blog. New comments will be marked as "waiting for moderation" (we only moderate for spam). If the level of spam is as low as we hope, we will bypass this step.