I received an e-mail from Oracle Global Customer Support regarding the 10.2.0.2 RDBMS server patchset for Sun Sparc Solaris 64-bit. The e-mail said:
Please note that Patch 5117016 is a MANDATORY PATCH required to be installed and run immediately AFTER installation of the 10.2.0.2 Patch Set on Sun Sparc Solaris 64-bit. This patch fixes a known issue in 10.2.0.2 Patch Set on Sun Sparc Solaris where the libserver10.a library is installed incorrectly into $ORACLE_HOME/rdbms/lib instead of into $ORACLE_HOME/lib.
Any patches applied without Patch 5117016 installed must be backed out, Patch 5117016 must be applied and then the patches reinstalled.
Not applying the patch can cause subsequent problems such as:
- Applying patches on top of 10.2.0.2 may have no effect.
- Changing the DBA user or SGA attach address may have no effect
Further details on this issue can be found in ALERT Note 394933.1
Next I went to my Oracle10gR2 installation on my Solaris 9 64-bit server and executed the commands below.
% cd $ORACLE_HOME/rdbms/lib
% ls -l libserver*
-rwxr-xr-x 1 oracle dba 154257164 Feb 24 2006 libserver10.a
% cd $ORACLE_HOME/lib
% ls -l libserver*
-rwxr-xr-x 1 oracle dba 153646336 Oct 20 15:52 libserver10.a
Notice the October 20 date on the $ORACLE_HOME/lib/libserver10.a file. I had version 10.2.0.2 already installed as well as CPUJul2006 (Patch 5225799). On October 20, I applied the patch for Bug 5458753 as described in my blog post “Oracle10g – Bug 5458753”.
It would appear after applying Patch 5458753 on October 20, the libserver10.a library was placed in the correct directory. In addition, according to a development team, the patch corrected the “SQL can execute in wrong Schema” problem.
Perhaps that is why the alert bullet-point is phrased “Applying patches on top of 10.2.0.2 may have no effect.”