manual:appendix:install:db_scripts
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
manual:appendix:install:db_scripts [2019/01/28 10:06] martins-v timescale db: some reordering of info |
manual:appendix:install:db_scripts [2020/03/06 08:07] (current) martins-v fixing link target |
||
|---|---|---|---|
| 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 on the database server (see [[https://docs.timescale.com/latest/getting-started/installation|installation instructions]]). |
| TimescaleDB extension must also be enabled for the specific DB by executing: | TimescaleDB extension must also be enabled for the specific DB by executing: | ||
| Line 62: | Line 64: | ||
| Running this command requires database administrator privileges. | Running this command requires database administrator privileges. | ||
| - | The ''timescaledb.sql'' script is located in database/postgresql (along with schema.sql, images.sql, data.sql). The script must be run after the regular PostgreSQL database has been created with initial schema/data (see section above): | + | <note>If you use a database schema other than 'public' you need to add a SCHEMA clause to the command above. E.g.:\\ ''echo %%"%%CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;%%"%% | sudo -u postgres psql zabbix''</note> |
| + | |||
| + | The ''timescaledb.sql'' script is located in database/postgresql. The script must be run after the regular PostgreSQL database has been created with initial schema/data (see section above): | ||
| cat timescaledb.sql | sudo -u zabbix psql zabbix | cat timescaledb.sql | sudo -u zabbix psql zabbix | ||
| Line 71: | Line 75: | ||
| * Override item trend period | * Override item trend period | ||
| - | In order to use partitioned housekeeping for history and trends both these options must be on. 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 98: | ||
| 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 === | ||