Increase java heap size of Derby database to resolve the Out of memory errors

Resolving The Problem

You want to enlarge the memory settings when starting up the Derby database.

The Derby database service (derbydb) is controlled by EGO. Use egosh to check its corresponding commands in your system. Then modify the memory settings in the startup script.

For example:

userA@hostA: egosh service view derbydb | grep Command
Command : "${EGO_TOP}\perf\1.2\etc\startNetworkServer.bat" 0.0.0.0 1527
Command : "${EGO_TOP}\perf\1.2\etc\startNetworkServer.bat" 0.0.0.0 1527 ------- this is for Windows
Command : ${EGO_TOP}/perf/1.2/etc/startNetworkServer.sh 0.0.0.0 1527 ------this is for Unix and Linux
userA@hostA: cd $EGO_TOP/perf/1.2/etc
userA@hostA: tail -20 ./startNetworkServer.sh
rm -rf ${PERF_DATADIR}/app/db.lck
fi
if [ -f "${PERF_DATADIR}/app/dbex.lck" ]
then
cp ${PERF_DATADIR}/app/dbex.lck ${PERF_DATADIR}/app/lckfolder/
rm -rf ${PERF_DATADIR}/app/dbex.lck
fi
$JAVA_HOME/bin/java -Xms64M -Xmx512M -cp ${LCP} ------ modify here

Note: Xmx value should not exceed size of memory available on the host.