My Experiences with Databases

Oracle,MySQL,SQL SERVER,Python,Azure,AWS,Oracle Cloud,GCP Etc

  • Enter your email address to follow this blog and receive notifications of new posts by email.

  • Total Views

    • 315,905 hits
  • $riram $anka


    The experiences, Test cases, views, and opinions etc expressed in this website are my own and does not reflect the views or opinions of my employer. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content.Product and company names mentioned in this website may be the trademarks of their respective owners.

Applying WLS patch using BSU -java.lang.OutOfMemoryError: GC overhead limit exceeded

Posted by Sriram Sanka on July 8, 2018


If you are trying to Apply any Big Patch, while Checking for conflicts…., “BSU”  might end-up with Java Heap  Errors.

 

 

To Avoid,  Try to Increase the size in $FMW_Home/utils/bsu . Edit bsu.sh using any editor as below. 

Change the Value MEM_ARGS=”-Xms256m -Xmx512m” to MEM_ARGS=”-Xms1024m -Xmx1024m” or even bigger  and save. 

This will resolve the above issue and re-try applying the patch .

 

For more Details Ref Oracle MOS Doc:  Weblogic 10.3.6 Patching Error Using BSU – “java.lang.OutOfMemoryError: GC overhead limit exceeded” (Doc ID 2007492.1) and 

Enhancement for WLS BSU (Smart Update): Resolves Very Long Time to Apply Patches – Especially When Checking for Patch Conflicts (Doc ID 2271366.1)

 

 

 

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 )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

 
%d bloggers like this: