(CR# 436653) If you use a SQL Anywhere ODBC data source on Solaris, an EAServer core dump can occur when the ODBC data source is accessed.
Workaround: Start the database manually, and set the database engine (using the -n option) to the same value as the EngineName property that is defined in $DJC_HOME/intersolv/odbc.ini.
For example, if the ODBC DSN definition in odbc.ini is:
[EAS Demo DB V10u] Driver=/eas60214/ASA100/lib/libdbodbc10_r.so EngineName=easdemo10u Start= UID=dba PWD=sql DatabaseFile=/shared/easdemo10u.db
To start easdemo10u.db, use the -n option to set the value of the database engine to “easdemo10u”:
$ASANY9/bin/dbeng9 -x "tcpip(MyIP=127.0.0.1;Host=localhost;Port=2638;DoBroadcast=no;BroadcastListener=no)" -n easdemo10u /testarea/shared/easdemo10u.db -Z -zs 5M -zn 10 -o ../logs/ds-EASDemo.log
