[Support Tip] opcuiwww aborts on solaris servers running 9.10.210
opcuiwww coredumps (in csm_dbi_jb_msgs_get_escalate function) if OPC_USE_JB_MSGS_GET is set to TRUE and some pattern node, matching existing physical node, exist.
If set to TRUE the OPC_USE_JB_MSGS_GET, loading messages uses SQL to filter messages. In environments with a large volume of history messages, opening the filtered history browser when using the new filtering can take a long time.
Problem is in small stack size (8192) on Solaris platform.
Oracle DB itself requires larger stack size, minimum value should be 32768. This is not mentioned in the Release Note or in Installation Guide.
The stack can be extended by running the following command:
#ulimit -s 32767
The easiest way to do it is to add the command into the /opt/OV/bin/OpC/opcuiwww.sh script, just before the /opt/OV/bin/OpC/opcuiwww call
TSIA Certified Support Professional (Chris Reed)
HP Software values your feedback regarding your overall Support experience. Contact us at email@example.com or my manager directly.