Oracle 10.2.0.4 memory corruption

Thanks to a September 23, 2008 Oracle-L post by Jesse Rich, I was notified of a memory corruption problem in 10.2.0.4 Patch 5 and above.

According to Metalink Note 737957.1, the “problem is introduced by the fix of Bug 5386874 in 10.2.0.4, Patch 5.”  Additional information found in the Note:

If the move to Patch 5 or higher has been made and there is no option to revert back to the situation before applying, then the following workaround can be considered:

“event=”10049 trace name context forever, level 2”
# memory protect KGL objs

Do NOT set this event at session level. Only set it in the init.ora / spfile.

It is not possible to get the corrected fix into Patch 9.  The corrected fix is anticipated for Patch 10 but this cannot be guaranteed at the time of writing.

I forgot about this for a couple of months  when I decided to check again.  On November 6, 2008, the same note was updated with:

It is now confirmed that the correct fix is indeed made available into Patch 10.

Upon further investigation, it appears 10.2.0.4 Patch 12 (Patch 7522473) is the most recent patch available for 32-bit Windows.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: