Summary

The following ERROR is thrown on the database side, Oracle in this case

ORA-29532: Java call terminated by uncaught Java exception: java

2014-09-18 22:01:39.290

Exception in thread "Root Thread" java.lang.OutOfMemoryError

              at com.pega.pegarules.data.internal.clipboard.directstream.InflaterV7.inflateV7(InflaterV7.java)

              at com.pega.pegarules.data.udf.directstreamreader.DirectStreamReaderBase.createDirectStream(DirectStreamReaderBase.java)

              at com.pega.pegarules.data.udf.directstreamreader.DirectStreamReaderBase.get(DirectStreamReaderBase.java)

              at com.pega.pegarules.data.udf.directstreamreader.DirectStreamReader.get(DirectStreamReader.java)

Root Cause

We should be able to resolve this issue by increasing the max heap size for the Oracle JVM. Unfortunately, Pega cannot recommend any DB setting limits as it’s purely environmental depending on the size of the BLOB. Below is an extract of details collected from Oracle documentation which explains the remedy in detail.
 
 
How to see memory allocated to Oracle JVM?
 
select * from v$sgastat where pool = 'java pool';
 
First user need to find out how much heap size they have available right now in total: Take a look at their initialization parameter JAVA_POOL_SIZE. If it is 0, then you are using automatic memory management (10g or 11g) and the heap size is determined by the Oracle server "automatically". Then user can take sga_target (10g) or memory_target (11g) as an upper limit.
 
The maximum heap size per session is limited by the parameter java_max_sessionspace_size (value 0 means default of 4GB).
We might need to increase either the java_pool_size, sga_target/memory_target or java_max_sessionspace_size.
 
 
http://docs.oracle.com/cd/B28359_01/java.111/b31225/chnine.htm#BABHEBIE
 
http://docs.oracle.com/cd/B28359_01/server.111/b28320/initparams099.htm#REFRN10074
 
http://docs.oracle.com/cd/B28359_01/server.111/b28320/initparams100.htm#REFRN10075