Upgrading From OES1 to OES2

Problem: Sun Java Package replaced by IBM Package - Causes the Sesam-RMI service to fail

Some customers have had their custom installed Sun JVM automatically replaced by the IBM JVM.

Symptoms:

Can't connect with GUI after OES1 to OES2 upgrade

#> . /var/opt/sesam/var/ini/sesam2000.profile ; sm_main status shows all services up except RMI 

Solution:

Install the sun JVM again  and make a symlink to show sesam the location and restart sesam:

Example:

#> ln -s /opt/java/jvm-version/bin/java /opt/sesam/bin/sesam/java ; /etc/init.d/sesam restart

Check:

$> /opt/sesam/bin/sesam/java -version |grep HotSpot;