Re: Shared memory problem on Oracle 7.2.2

jmjm_at_hogpf.ho.att.com (-J.MIKLEWICZ) wrote:
> Just to add my two cents, I recently upgraded from SUN Solaris 2.3,
> Oracle 7.0.15 to Solaris 2.5, Oracle 7.2.3 and the reason I've been
> poking around in this newsgroup is that I have started to get these
> 4031 errors. Other than the upgrade of the op system and the oracle
> code, nothing has been changed :-), by that I mean we haven't made any
> changes to our applications, so it appears that the memory leak still
> exists in 7.2.3, at least on the Solaris platform.

Oracle support indicated to me that the memory leak(s) responsible for the 4031 errors, were caused by several bugs. Some of these were fixed in 7.2.3 and at least one will not be fixed until 7.3. There is probably a patch available to fix this until 7.3 is released on Solaris. A patch on 7.2.3 under HP/UX 10.01, and recompilation of our Pro*C programs, eliminated (or at least delayed??) 4031 errors and serious SMON problems we were experiencing. We have seen no problems for the past week, since installing 7.2.3 with the patch. Symptoms seem to vary somewhat depending on each site's transaction mix. In our case, we saw none of these problems running the same applications and mix under HP/UX 9.05 on a single processor machine. As soon as we moved to a dual processor machine with HP/UX 10.01, we saw sporatic 4031 errors and serious problems with a high active SMON process.

• Andy Zitelli