30-Oct-2012PROBLEMPUBLISHED3 |
|
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |
Applies to:
Oracle Server - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]Linux x86
IBM: Linux on System z
Linux x86-64
This issue may be encountered regardless of opatch version being used. An y 11.2 opatch version may report this warning
Symptoms
On 11.2 when applying a PSU, CPU or one-off Patch to either the RDBMS or Grid Infrastructure Homes, the relink phase can generate the following warnings:
ins_srvm.mk:68: warning: overriding commands for target `libsrvm11.so'
ins_srvm.mk:31: warning: ignoring old commands for target `libsrvm11.so'
ins_srvm.mk:71: warning: overriding commands for target `libsrvmocr11.so'
ins_srvm.mk:34: warning: ignoring old commands for target `libsrvmocr11.so'
ins_srvm.mk:74: warning: overriding commands for target `libsrvmhas11.so'
ins_srvm.mk:37: warning: ignoring old commands for target `libsrvmhas11.so'
This will cause Opatch to report:
Opatch succeeded with warnings.
The example above is for a Grid Infrastructure Home and srvm, however warnings against other components may be seen.
The following is an example of a DB Home and precomp:-
ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg'
env_precomp.mk:2115: warning: ignoring old commands for target `pcscfg.cfg'
Changes
Patching which results in relinking taking place i.e.
make -f ins_xxxxx.mk .....
Cause
This warning is independent of the version of opatch used.
Targets are defined more than once within the makefiles and this is just a warning that the second (later) definition is being used:
ins_srvm.mk:71: warning: overriding commands for target `libsrvmocr11.so'
ins_srvm.mk:34: warning: ignoring old commands for target `libsrvmocr11.so'
ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg'
env_precomp.mk:2115: warning: ignoring old commands for target `pcscfg.cfg'
If you check the $OH/install/make.log you will see that these warnings existed before patching i.e. after the original installation. This is not an issue which the patch you are applying has introduced, simply a warning which opatch has correctly captured and is reporting back to the user.
Solution
This is a warning only which opatch is reporting. The Patch has applied successfully and the warning output can be safely ignored.