Zabbix Documentation 4.4

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

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
manual:appendix:install:db_scripts [2019/01/28 15:43]
martins-v more precise wording
manual:appendix:install:db_scripts [2020/03/06 08:05] (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>​
   mysql> create database zabbix character set utf8 collate utf8_bin;   mysql> create database zabbix character set utf8 collate utf8_bin;
-  mysql> grant all privileges on zabbix.* to [email protected]localhost identified by '<​password>​';+  ​mysql> create user '​zabbix'​@'​localhost'​ identified by '<​password>';​ 
 +  ​mysql> grant all privileges on zabbix.* to 'zabbix'@'localhost';
   mysql> quit;   mysql> quit;
  
-If you use Zabbix packages continue with instructions for [[manual:​installation:​install_from_packages:​debian_ubuntu#​importing_data|Debian/​Ubuntu]] or [[manual:​installation:​install_from_packages:​rhel_centos#​importing_data|RHEL/​CentOS]] to import the data into the database.+<note warning>If you are installing from Zabbix packages, stop here and continue with instructions for [[manual:​installation:​install_from_packages:​debian_ubuntu#​importing_data|Debian/​Ubuntu]] or [[manual:​installation:​install_from_packages:​rhel_centos#​importing_data|RHEL/​CentOS]] to import the data into the database.</​note>​ 
 + 
 +If you are installing Zabbix from sources, proceed to import the data into the database:
  
   shell> cd database/​mysql   shell> cd database/​mysql
Line 33: Line 38:
   shell> sudo -u postgres createuser --pwprompt zabbix   shell> sudo -u postgres createuser --pwprompt zabbix
  
-Now we will set up the database ''​zabbix''​ (last parameter) with the previously created user as the owner (''​-O zabbix''​) ​and import initial schema and data (assuming you are in the root directory of Zabbix sources):+Now we will set up the database ''​zabbix''​ (last parameter) with the previously created user as the owner (''​-O zabbix''​).
  
   shell> sudo -u postgres createdb -O zabbix -E Unicode -T template0 zabbix   shell> sudo -u postgres createdb -O zabbix -E Unicode -T template0 zabbix
  
-If you use Zabbix packages continue with instructions for [[manual:​installation:​install_from_packages:​debian_ubuntu#​importing_data|Debian/​Ubuntu]] or [[manual:​installation:​install_from_packages:​rhel_centos#​importing_data|RHEL/​CentOS]] to import the data into the database.+<note warning>If you are installing from Zabbix packages, stop here and continue with instructions for [[manual:​installation:​install_from_packages:​debian_ubuntu#​importing_data|Debian/​Ubuntu]] or [[manual:​installation:​install_from_packages:​rhel_centos#​importing_data|RHEL/​CentOS]] to import the initial schema and data into the database.</​note>​ 
 + 
 +If you are installing Zabbix from sources, proceed to import the initial schema and data (assuming you are in the root directory of Zabbix sources):
  
   shell> cd database/​postgresql   shell> cd database/​postgresql
Line 49: Line 56:
  
 === TimescaleDB === === TimescaleDB ===
- 
-Support of TimescaleDB has been added on **experimental** basis in Zabbix 4.2.0. 
  
 <note warning>​Currently TimescaleDB is not supported by Zabbix proxy.</​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 60: Line 65:
   echo "​CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;"​ | sudo -u postgres psql zabbix   echo "​CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;"​ | sudo -u postgres psql zabbix
  
-Running this command requires database administrator privileges. ​+Running this command requires database administrator privileges. 
 + 
 +<​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): 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):
Line 72: Line 79:
  
 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 101:
   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 ===
  
Line 104: Line 114:
   # stop here if you are creating database for Zabbix proxy   # stop here if you are creating database for Zabbix proxy
   shell> db2batch -d zabbix -f images.sql   shell> db2batch -d zabbix -f images.sql
-  shell> db2batch -d zabbix -f data.sql ​+  shell> db2batch -d zabbix -f data.sql ​-l ';;'​
  
 <​note>​It is important to set UTF-8 locale for Zabbix server, Zabbix proxy and the web server running Zabbix frontend. Otherwise text information from Zabbix will be interpreted by IBM DB2 server as non-UTF-8 and will be additionally converted on the way from Zabbix to the database and back. The database will store corrupted non-ASCII characters.</​note>​ <​note>​It is important to set UTF-8 locale for Zabbix server, Zabbix proxy and the web server running Zabbix frontend. Otherwise text information from Zabbix will be interpreted by IBM DB2 server as non-UTF-8 and will be additionally converted on the way from Zabbix to the database and back. The database will store corrupted non-ASCII characters.</​note>​