Zabbix Documentation 4.2

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:appendix:install:db_scripts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:appendix:install:db_scripts [2019/01/28 13:44]
martins-v on -> enabled
manual:appendix:install:db_scripts [2019/03/01 14:04]
martins-v punctuation fix
Line 13: Line 13:
 UTF-8 is the only encoding supported by Zabbix. It is known to work without any security flaws. Users should be aware that there are known security issues if using some of the other encodings. UTF-8 is the only encoding supported by Zabbix. It is known to work without any security flaws. Users should be aware that there are known security issues if using some of the other encodings.
 === MySQL === === MySQL ===
 +
 +Character set utf8 and utf8_bin collation is required for Zabbix server to work properly with MySQL database.
  
   shell> mysql -uroot -p<​password>​   shell> mysql -uroot -p<​password>​
Line 52: Line 54:
 Support of TimescaleDB has been added on **experimental** basis in Zabbix 4.2.0. Support of TimescaleDB has been added on **experimental** basis in Zabbix 4.2.0.
  
-<note warning>​TimescaleDB is supported ​with Zabbix ​server only.</​note>​+<note warning>Currently ​TimescaleDB is not supported ​by Zabbix ​proxy.</​note>​
  
 We assume that TimescaleDB extension has been already installed in the database (see [[https://​docs.timescale.com/​v1.1/​getting-started/​installation|installation instructions]]). We assume that TimescaleDB extension has been already installed in the database (see [[https://​docs.timescale.com/​v1.1/​getting-started/​installation|installation instructions]]).
Line 72: Line 74:
  
 In order to use partitioned housekeeping for history and trends both these options must be enabled. It's possible to use TimescaleDB partitioning only for trends (by setting //Override item trend period//) or only for history (//Override item history period//). In order to use partitioned housekeeping for history and trends both these options must be enabled. It's possible to use TimescaleDB partitioning only for trends (by setting //Override item trend period//) or only for history (//Override item history period//).
 +
 +<note tip>You may want to run the timescaledb-tune tool provided by TimescaleDB to optimize PostgreSQL configuration parameters in your ''​postgresql.conf''​.</​note>​
 === Oracle === === Oracle ===
  
Line 92: Line 96:
   sqlplus> @images.sql   sqlplus> @images.sql
   sqlplus> @data.sql   sqlplus> @data.sql
-  ​+ 
 +<note tip>​Please set the initialization parameter CURSOR_SHARING=FORCE for best performance.</​note>​ 
 Now the temporary directory can be removed: Now the temporary directory can be removed:
  
   shell> ssh [email protected]_host "rm -rf /​tmp/​zabbix_images"​   shell> ssh [email protected]_host "rm -rf /​tmp/​zabbix_images"​
- 
 === IBM DB2 === === IBM DB2 ===