Tuesday 10 April 2018

Encountered unrecognized patch ID

“Encountered unrecognized patch ID” Failures when trying to apply WLS Patch using bsu Smart Update

Applies to: Oracle Weblogic Server – Version 9.0 to 10.3.6
Information in this document applies to any platform.
Symptoms: When attempting to remove a patch currently  applied or apply a newly downloaded patch using the Smart Update tool in command line, the following error occurs:
Encountered unrecognized patch ID: XYZ  (OR)  Unable to locate the specified product directory [/wlserver_10.3]
Cause: This error may cause due to the wrong version  patch you are trying to apply
Solution:
1.Recheck the patch version of weblogic server you are using.



Choose the right version and unzip the patch recommended while running checkMTpatch.sh. Then unzip the patch in the PATCH_TOP dir.
2.Check the permissions for the patches and move the patches into $FMW_HOME/utils/bsu/cache_dir
After moving the patch we have to smart update the patch by running bsu.
$bsu.sh –install –patch download_dir=$FMW_HOME/utils/bsu/cache_dir  -patchlist=DN1F –prod_dir=$FMW_HOME/wlserver_10.3
If it throws any error like Unable to locate the specified product directory [/wlserver_10.3]
3. Give the full path instead of $FMW_HOME and try again.
Once all are set properly it will check for conflicts …
Checking for conflicts......
Conflict(s) detected - resolve conflict condition and execute patch installation again
Conflict condition details follow:
Patch DN1F is mutually exclusive and cannot coexist with patch(es): CIH8
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
        at java.util.HashMap.inflateTable(HashMap.java:316)
        at java.util.HashMap.put(HashMap.java:488)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.loadPropertyMap(XBeanDataHandler.java:778)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.<init>(XBeanDataHandler.java:99)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.createDataHandler(XBeanDataHandler.java:559)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.getComplexValue(XBeanDataHandler.java:455)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:442)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)
        at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)
        at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)
        at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)
        at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)
        at com.bea.plateng.patch.Patch.main(Patch.java:306)

If any conflicts occurs it recommends to remove the existing patch. In the above case it is suggesting to Remove CIH8 patch. Once we remove the conflict patch, then only it allows us to apply new patch Smart Update.
To remove the conflicted patches run the below command.
$bsu.sh –remove –patchlist=CIH8 –prod_dir=$FMW_HOME/wlserver_10.3
It will take time to remove. Once the conflicted patch is removed we can apply the recommended patch.

Posted by: Anil Bandi
Oracle Apps DBA

No comments:

Post a Comment

Forgot WebLogic Password | Reset WebLogic Password

If you forgot / doesn't aware of Weblogic Console password. Want to Reset it?  1.   Shut down all running services .  Since the Adm...