When database monitoring feature encounters ODBC exception it can't handle, then instead of just marking this item as Not supported, the entire zabbix server shuts down. Would be nice, if that error would not have so dramatic consequences and Zabbix server could stay alive after that.
For example:

Handled error
24561:20131023:141301.255 In odbc_DBconnect() db_dsn:'nosuchdb.mydomain.com' user:'myuser'
24561:20131023:141301.256 odbc_Diag(): rc_msg:'SQL_ERROR' rec_nr:1 sql_state:'IM002' native_err_code:0 err_msg:'[unixODBC][Driver Manager]Data source name not found, and no default driver specified'
24561:20131023:141301.256 End of odbc_DBconnect():FAIL
24561:20131023:141301.256 End of get_value_db():NOTSUPPORTED

Un-handled error
20951:20131023:125501.034 In odbc_DBconnect() db_dsn:'myserver.mydomain.com' user:'myuser'
/opt/zabbix/sbin/zabbix_server: poller #1 [got 1 values in 0.077962 sec, getting values]: relocation error: /usr/lib64/libmyodbc5.so: symbol strmov, version libmysqlclient_16 not defined in file libmysqlclient_r.so.16 with link time reference
20945:20131023:125501.044 One child process died (PID:20951,exitcode/signal:127). Exiting ...
20945:20131023:125501.044 zbx_on_exit() called