The required JVM size when cloning the EBS Fusion Middleware products has increased past the default. Unfortunately these errors are sometimes hard to spot in the logs. If adop phase=fs_clone,a, or fail on the apps tier, look in the detailed logs such as those under wlsT2PApply to see if you find errors like initializing the VM, JAVA.LANG.OUTOFMEMORY: JAVA HEAP SPACE, etc.

If you find errors like this, before running running AD utilities, set the environment variable CONFIG_JVM_ARGS,

export CONFIG_JVM_ARGS="-Xmx4096m -Xms1024m -XX:MaxPermSize=1024m -XX:-UseGCOverheadLimit"

I have this explicitly set in my automated cloning scripts as well as in my login profile for when I run the commands directly from the command line.

As you can see from some of the relevant notes on My Oracle Support, in some cases, the commands don’t fail, they just seem to run forever.

Adop Fs_clone Run For Days No Error Just Keep Running (Doc ID 2671167.1)

12.2 EBS adop phase=fs_clone fails during wlsT2PApply on with error “Java Heap Space”/”java.lang.OutOfMemoryError: GC overhead limit exceeded” (Doc ID 2429369.1)

12.2.5: Applications Tier Clone Is Hanging With java.lang.OutOfMemoryError (Doc ID 2244021.1)

Related Posts

Leave a Reply

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