It's all about Weblogic..!!

May 4, 2010

Unrecognized Patch ID Error While Applying Patch Using BSU Tool

Filed under: * Smart Update errors — streethawkz @ 11:02 pm
Symptoms :
Trying to apply the patch using the bsu.sh script on solaris server, it fails with the
following message:
Encountered unrecognized patch ID: EVPG
EVPG is the patch name for example.
Cause:
1. Run the following command in $OCSG_HOME/utils/bsu
./bsu.sh -report -log=test.log -log_priority=trace
2. Check the test.log file, there is following error:
FATAL [Thread-0] com.bea.plateng.patch.PatchSystem – com.bea.plateng.patch.dao.PatchException: java.io.IOException: Permission denied
The cause is due to the installer does not have the permission to the folder where the installation binary file is extracted to.
Solution :
If seeing the Permission denied in the log file for BSU report, then please make sure the installer has the valid permission to the folder where the OCSG installation file is extracted to.

———————————–

OR

ERROR : Encountered unrecognized patch ID: 2LYV

Below are the steps I followed to install the patches.

C:\bea\utils\bsu>bsu.cmd -prod_dir=c:\bea\weblogic92 -patch_download_dir=D:\pat -patchlist=Bug7835091_920mp3 -verbose -install -log=D:\pat\pat.txt -log_priority=trace

Encountered unrecognized patch ID: Bug7835091_920mp3 //ERROR

NOTE:

-I have got an error here because of wrong patch ID that I have specified.

-One thing that is very important is to copy patch-catalog.xml along with the patch jar files to the offline machine. The “Invalid Patch ID” error occurs when Smart Update doesn’t find the patches in patch-catalog.xml.

C:\bea\utils\bsu>bsu.cmd -prod_dir=c:\bea\weblogic92 -patch_download_dir=D:\pat -patchlist=2LYV -verbose -install -log=D:\pat\pat.txt -log_priority=trace

OUTPUT:

Checking for conflicts..

No conflict(s) detected

Starting installation of Patch ID: 2LYV

Installing D:\pat\2LYV.jar

Extracting C:\bea\patch_weblogic923\patch_jars\Bug7835091_920mp3.jar

Updating C:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblog

ic_patch.jar

Old manifest value: Class-Path=

New manifest value: Class-Path=../../../patch_jars/Bug7835091_920mp3.jar

Result: Success

——————–

OR

Encountered unrecognized patch ID: EVPG

This error message can occur when the patch-catalog.xml is out of sync with the

environment in which the patch was downloaded or it might have been corrupted.

Can you take a back up of the patch-catalog.xml file of the node in which the

patch application fails.

Then please try to copy the patch_catalog file from a node where patch

application is successful and place the patch jar file together in the

cache_dir and then run the bsu command.

———————–

OR

Encountered unrecognized patch ID: EVPG

Stack Trace :

at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getInvalidatedPatchMap(PatchCatalogHelper.java:1530)
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:281)
*** Error: BSU utility ended up with an error! ErrorCode=1

Error “Encountered unrecognized patch ID” usually means that patch-catalog.xml
is out of synch with patches in cache_dir folder.

Solution / Workaround :

The reason is old patch.catalog.xml file.


—————–

OR

Encountered unrecognized patch ID: 8IIR

Stack Trace :

Applying patch 8IIR
JVMDUMP006I Processing Dump Event “uncaught”, detail
“java/lang/OutOfMemoryError” – Please Wait.
JVMDUMP007I JVM Requesting Snap Dump using ‘/opt/bea/wls91/utils/bsu/Snap0001.
20090730.154724.667784.trc’
JVMDUMP010I Snap Dump written to /opt/bea/wls91/utils/bsu/Snap0001.20090730.
154724.667784.trc
JVMDUMP007I JVM Requesting Heap Dump using ‘/opt/bea/wls91/utils/bsu/heapdump.
20090730.154724.667784.phd’
JVMDUMP010I Heap Dump written to /opt/bea/wls91/utils/bsu/heapdump.20090730.
154724.667784.phd
JVMDUMP007I JVM Requesting Java Dump using ‘/opt/bea/wls91/utils/bsu/javacore.
20090730.154724.667784.txt’
JVMDUMP012E Error in Java Dump: /opt/bea/wls91/utils/bsu/javacore.20090730.
154724.667784.txt
JVMDUMP013I Processed Dump Event “uncaught”, detail
“java/lang/OutOfMemoryError”.
Exception in thread “main” java.lang.OutOfMemoryError
at java.util.HashMap.addEntry(HashMap.java:798)
at java.util.HashMap.put(HashMap.java:441)
at com.bea.cie.common.dao.xbean.XBeanDataHandler.
loadPropertyMap(XBeanDataHandler.java:749)
at com.bea.cie.common.dao.xbean.XBeanDataHandler.
(XBeanDataHandler.java:97)
at com.bea.cie.common.dao.xbean.XBeanDataHandler.
createDataHandler(XBeanDataHandler.java:530)
at com.bea.cie.common.dao.xbean.XBeanDataHandler.
getComplexValue(XBeanDataHandler.java:426)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getPatchDetails(PatchCatalogHelper.java:623)
at com.bea.plateng.patch.dao.cat.Version.getPatchDetails(Version.java:
41)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getFilteredPatchDetailMap(PatchCatalogHelper.java:1130)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getPatchDetails(PatchCatalogHelper.java:1297)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getEveryPatchDetail(PatchCatalogHelper.java:695)
at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.
getInvalidatedPatchMap(PatchCatalogHelper.java:1530)
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:281)
*** Error: BSU utility ended up with an error! ErrorCode=1
Do you want to restart the last operation? [y=yes|n=no|c=continue without
restarting]

Solution / Workaround :

The error you have got is a java.lang.OutOfMemoryError which means that the Java ran out of heap space during operation.
You may try to increase the heap size fro BSU by setting -Xms128m -Xmx512m in your bsu.sh, where JVM for patch-client.jar is starting.

———–

OR

Encountered unrecognized patch ID: 8IIR

Trying to apply the patch using the bsu.sh script on solaris server, it fails with the
following message:
Encountered unrecognized patch ID: 8IIR

1. Run the following command in $OCSG_HOME/utils/bsu

./bsu.sh -report -log=test.log -log_priority=trace

2. Check the test.log file, there is following error:

FATAL [Thread-0] com.bea.plateng.patch.PatchSystem – com.bea.plateng.patch.dao.PatchException: java.io.IOException: Permission denied

The cause is due to the installer does not have the permission to the folder where the installation binary file is extracted to.

Solution / Workaround :

If seeing the Permission denied in the log file for BSU report, then please make sure the installer has the valid permission to the folder where the OCSG installation file is extracted to.

————-

OR

Many a times when customer copy the patch.jar and patch-catalog.xml file from email/support portal and FTP it to the machine.

They encounter ” Encountered unrecognized patch ID: ” error while running the bsu command.

– Please make sure that the bsu folder has 777 permission ( Not a must )

– When patch-catalog.xml file is copied the file extension is changed to patch-catalog.XML automatically in UNIX environment.

Hence we get the above error..!!

Change the extension to small letters i.e patch-cataog.xml and the command should work fine.. :)

1 Comment »

  1. Hello there! I could have sworn I’ve been to this site before but after reading through some of the post
    I realized it’s new to me. Anyhow, I’m definitely happy
    I found it and I’ll be bookmarking and checking back often!

    Comment by CAT 2014 Results — November 29, 2014 @ 5:25 am


RSS feed for comments on this post. TrackBack URI

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

Blog at WordPress.com.

%d bloggers like this: