Zabbix server does not verify length of column value before insertion. It happens after implementation of bindings for Oracle.

For example:
32209:20140523:164233.253 query [txnlev:1] [insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,message,status,error,esc_step,alerttype) value
s (1,3,135,1,1400852553,1,'[email protected]','PROBLEM: FTP service is down on Zabbix 111 Trigger: FTP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111Tr
igger: FTP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111Trigger: F
TP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111Trigger: FTP service is down on Zabbix 111','Trigger: FTP service is down on Zabbix 111
Trigger status: PROBLEM
Trigger severity: Average
Trigger URL:

Item values:

1. FTP service is running (Zabbix 111:net.tcp.service[ftp]): Down (0)
2. UNKNOWN (UNKNOWN:UNKNOWN): UNKNOWN
3. UNKNOWN (UNKNOWN:UNKNOWN): UNKNOWN

Original event ID: 135',0,'',1,0);
]