1.8.2, 1.8.3 and 1.8.9. 3.5 Known problems Warning: Zabbix frontend in 1.8 does not work with SQLite backend. Please, use one of the other supported databases. 3.5.1 For version 1.8 • PHP mbstring it temporarily became unavailable. With 1.8.2, this is also supported for PostgreSQL, Oracle and SQLite. • Zabbix administrators now can only choose groups they are members of and users of those groups least PostgreSQL 8.3, which introduced much better VACUUM performance. SQLite
php-sqlite3 3.3.5 or later Required if SQLite is used as Zabbix back-end database. Note: Zabbix may work on previous

one running the server. 7 Note: Zabbix web interface must run on the same physical machine if SQLite is used. Proxy Zabbix proxy can collect performance and availability data on behalf of Zabbix server proxy requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations use at least PostgreSQL 8.3, which introduced much better VACUUM performance. SQLite 3.3.5 or later Required if SQLite is used as Zabbix backend database. IBM DB2 9.7 or later Required if IBM DB2 is

one running the server. 6 Note: Zabbix web interface must run on the same physical machine if SQLite is used. Proxy Zabbix proxy can collect performance and availability data on behalf of Zabbix server proxy requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations use at least PostgreSQL 8.3, which introduced much better VACUUM performance. SQLite 3.3.5 or later Required if SQLite is used as Zabbix backend database. IBM DB2 9.7 or later Required if IBM DB2 is

the one running the server. Note: Zabbix web interface must run on the same physical machine if SQLite is used. Proxy Zabbix proxy can collect performance and availability data on behalf of Zabbix server frontend, though - that would still be possible via the link in the lower right corner. 8 5.2.4 SQLite supported by frontend 5.2.5 Improved frontend performance Multiple sections of frontend have their proxy requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations

one running the server. 7 Note: Zabbix web interface must run on the same physical machine if SQLite is used. Proxy Zabbix proxy can collect performance and availability data on behalf of Zabbix server database - manual SQL patch execution is not required anymore. Note: Automatic database upgrade for SQLite is not supported. 5.25.2 Zabbix proxy improvements Zabbix proxies will now be able to work uninterrupted side due to licensing issues. While it was not recommended to use Zabbix server and frontend with SQLite3 database before, this change makes it even less recommended, because simultaneous database access

proxy requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations Required if IBM DB2 is used as Zabbix backend database. SQLite 3.3.5 or later SQLite is only supported with Zabbix proxies. Required if SQLite is used as Zabbix proxy database. Attention: IBM DB2 and To configure the sources for a Zabbix proxy (with SQLite etc.), you may run: ./configure --prefix=/usr --enable-proxy --with-net-snmp --with-sqlite3 --with-ssh2 To configure the sources for a Zabbix

one running the server. 6 Note: Zabbix web interface must run on the same physical machine if SQLite is used. Proxy Zabbix proxy can collect performance and availability data on behalf of Zabbix server side due to licensing issues. While it was not recommended to use Zabbix server and frontend with SQLite3 database before, this change makes it even less recommended, because simultaneous database access access with Zabbix server and frontend may now corrupt the database. Note that using Zabbix proxy with SQLite3 database is still a perfectly valid solution. ** Housekeeper changes ** On zabbix_server and

DB2_COMPATIBILITY_VECTOR=3 SQLite 只有为 Zabbix proxy 创建数据库的时候才能使用 SQLite！ Using SQLite is supported for Zabbix proxy only! Note: 如果使用 SQLite 作为 Zabbix proxy 的数据库，创建时如果数据库不存在，将自动创建。 Note: If using SQLite with Zabbix database will be automatically created if it does not exist. shell> cd database/sqlite3 shell> sqlite3 /var/lib/sqlite/zabbix.db < schema.sql 7 返回安装部分。Return to the installation section. 2 Windows In case of PostgreSQL only empty string results in attempt to use socket. DBName 是 据库名称。 对于 SQLite3 必须提供 数据库文件路径 （Zabbix 的多进程架构 不允许使用内存数据 库，例如 ：memory：， file :: memory：？ cache = shared 或 file：memdb1？

DB2_COMPATIBILITY_VECTOR=3 SQLite 只有为 Zabbix proxy 创建数据库的时候才能使用 SQLite！ Using SQLite is supported for Zabbix proxy only! Note: 如果使用 SQLite 作为 Zabbix proxy 的数据库，创建时如果数据库不存在，将自动创建。 Note: If using SQLite with Zabbix database will be automatically created if it does not exist. shell> cd database/sqlite3 shell> sqlite3 /var/lib/sqlite/zabbix.db < schema.sql 7 返回安装部分。Return to the installation section. 2 Windows In case of PostgreSQL only empty string results in attempt to use socket. DBName 是 据库名称。 对于 SQLite3 必须提供 数据库文件路径 （Zabbix 的多进程架构 不允许使用内存数据 库，例如 ：memory：， file :: memory：？ cache = shared 或 file：memdb1？

DB2_COMPATIBILITY_VECTOR=3 SQLite 只有为 Zabbix proxy 创建数据库的时候才能使用 SQLite！ Using SQLite is supported for Zabbix proxy only! Note: 如果使用 SQLite 作为 Zabbix proxy 的数据库，创建时如果数据库不存在，将自动创建。 Note: If using SQLite with Zabbix database will be automatically created if it does not exist. shell> cd database/sqlite3 shell> sqlite3 /var/lib/sqlite/zabbix.db < schema.sql 7 返回安装部分。Return to the installation section. 2 Windows In case of PostgreSQL only empty string results in attempt to use socket. DBName 是 据库名称。 对于 SQLite3 必须提供 数据库文件路径 （Zabbix 的多进程架构 不允许使用内存数据 库，例如 ：memory：， file :: memory：？ cache = shared 或 file：memdb1？