If you invoke the WebLogic Smart Update tool using the graphical user interface (GUI) and you encounter the error java.lang.OutOfMemoryError, the Smart Update Tool reports that the specified patch does not exist, as shown below:

To confirm that the patch is valid and that an underlying java.lang.OutOfMemoryError is the problem, add the following options to the command line when you invoke the Smart Update script:

If a java.lang.OutOfMemoryError occurs, the log from the Smart Update tool will contain a stack trace similar to the following:

2010–02–02 13:44:38,346 DEBUG [AWT–EventQueue–0] com.bea.plateng.patch.gui.PatchMediator – java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
	at java.util.concurrent.FutureTask.get(FutureTask.java:83)
	at com.bea.plateng.patch.gui.ProgressDialog.showDialog(ProgressDialog.java:239)
	at com.bea.plateng.patch.gui.ProgressDialog.showProgressDialog(ProgressDialog.java:54)
	at com.bea.plateng.patch.gui.PatchMediator.refreshAll(PatchMediator.java:732)
	...more lines...

To increase the amount of memory that is available to the Smart Update tool, locate the Smart Update script and add the –Xmxheap-size option to the Java command line at the bottom of the script.

In Windows operating environments, the Smart Update script should be in the following location:

For Windows, the Java command should look like this:

In the –Xmxheap-size option, heap-size represents a numeric value that you supply (for example, –Xmx1024M).

In UNIX operating environments, the Smart Update script should be in the following location: