alter table graphs_items drop index graphs_items_2; alter table services drop index services_1; Oracle or PostgreSQL 10 drop index dhosts_1; drop index dservices_1; drop index httptest_2; drop index upgrades/dbpatches/1.8/: • MySQL: upgrades/dbpatches/1.8/mysql/patch.sql • Oracle: upgrades/dbpatches/1.8/oracle/patch.sql • PostgreSQL: upgrades/dbpatches/1.8/postgresql/patch.sql Database upgrade of Oracle Previous version of Zabbix had a dependency on a third party library called sqlora8. The library is not actively developed any more. Oracle support is now implemented using native Oracle Call

(default is still all and returns normal load value) vm.memory.size now supports more modes for various platforms. See supported by platform and vm.memory.size parameters pages for more information. validation were improved • Reduced the amount of persistent connections and to Oracle backend and changed to suggested Oracle access functions 10.1.1 New translations • Bulgarian 10.1.2 Completed translations Net-SNMP versions. Since Zabbix 2.0.5 this setting should work in all cases. • Performance for Oracle as the Zabbix backend database was improved by prefetching 2MB of data in SELECT statements. • Zabbix

message has been increased for Oracle database. 5.26 API improvements ** New host prototype API ** A host prototype API has been implemented with the development of VM support for low-level discovery constraints Such indexes were created automatically on MySQL, now they are created also on PostgreSQL, Oracle, DB2 to improve performance of Zabbix server and frontend operations with these databases. Dynamic exceeding the size limit. * Maximum configuration cache size increased to 8GB from 2GB 31 * On Oracle databases variable binding is now used for bulk inserts, resulting in much better performance. 8

more VMware collectors than monitored services in your Zabbix server/proxy configuration. • vmware.vm.perfcounter and vmware.hv.perfcounter items were added to allow custom hypervisor and virtual machine 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 as, for example, in return values Required if MySQL is used as Zabbix backend database. InnoDB engine is required. Oracle 10g or later Required if Oracle is used as Zabbix backend database. PostgreSQL 8.1 or later Required if PostgreSQL

without getting double alerts. vm.memory.size[available] item on AIX now returns the sum of free and cached memory. Before Zabbix 3.0 only the free memory size was returned. vm.memory.size[available] item sysfs, if sysfs access fails then try reading directly from memory. 3.3 Windows monitoring A new vm.vmemory.size key has been added to monitor virtual memory statistics on Windows. 4 Trigger functions French • Japanese • Polish • Portuguese (Brazil) 3 Daemon improvements • Database inserts on Oracle have been reworked to use dynamic binding. This should improve the bulk insert speed, especially

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 as, for example, in return values with Zabbix. Note that MySQL 8.0 is not supported in Zabbix pre-4.0 versions. Oracle 10g or later Required if Oracle is used as Zabbix backend database. PostgreSQL 8.1 or later Required if PostgreSQL Required if Oracle is used as Zabbix backend database. pgsql Required if PostgreSQL is used as Zabbix backend database. Note: Zabbix may work on previous versions of Apache, MySQL, Oracle, and PostgreSQL

problem. Database down message from now on consists of the following content: [MySQL|PostgreSQL|Oracle|IBM DB2] database [on :] is not available: vm.memory.size agent item now supports a slab parameter. • The following agent items now support new Item changes * ''vmware.hv.discovery'' item for VMware hypervisor discovery now returns two [[:manual/vm_monitoring/discovery_fields|additional fields]]: {#PARENT.NAME} and {#PARENT.TYPE}, returning name

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 as, for example, in return values backend database. InnoDB engine is required. MariaDB also works with Zabbix. Oracle 10g or later Required if Oracle is used as Zabbix backend database. PostgreSQL 8.1 or later Required if PostgreSQL Required if Oracle is used as Zabbix backend database. pgsql Required if PostgreSQL is used as Zabbix backend database. Note: Zabbix may work on previous versions of Apache, MySQL, Oracle, and PostgreSQL

If you have troubles setting up the database please consult your Database administrator. Oracle 假设在 Oracle 服务器 host 上存在有权限创建数据库对象的用户（用户名为 zabbix，密码为 password), 并且该用户具有/tmp 目录的写 入权限。Zabbix 数据库需要使用 UTF8 password exists and has permissions to create database objects in ORCL service located on the host Oracle database server with a user shell user having write access to /tmp directory. Zabbix requires a 需要将 Zabbix 数据库安装介质拷贝到 Oracle 服务器上的/tmp/zabbix_images 目录下： If you are creating a database for Zabbix server you need to have images from Zabbix sources on the host where Oracle is running. Copy them