Zabbix Documentation 4.0

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 [2017/09/25 08:51]
dimir [PostgreSQL] add dot
manual:appendix:install:db_scripts [2020/02/20 13:53] (current)
martins-v removing duplicated instructions
Line 1: Line 1:
-==== 1 Database creation ​scripts ​====+==== 1 Database creation ====
  
 === Overview === === Overview ===
Line 5: Line 5:
 A Zabbix database must be created during the installation of Zabbix server or proxy. A Zabbix database must be created during the installation of Zabbix server or proxy.
  
-This section provides ​scripts ​for creating a Zabbix database. A separate ​schema script ​is provided ​for each supported database.+This section provides ​instructions ​for creating a Zabbix database. A separate ​set of instructions ​is available ​for each supported database.
  
 <note tip>''​schema.sql'',​ ''​images.sql''​ and ''​data.sql''​ files are located in the //​database//​ subdirectory of Zabbix sources. If Zabbix was installed from distribution packages, refer to the distribution documentation.</​note>​ <note tip>''​schema.sql'',​ ''​images.sql''​ and ''​data.sql''​ files are located in the //​database//​ subdirectory of Zabbix sources. If Zabbix was installed from distribution packages, refer to the distribution documentation.</​note>​
Line 11: Line 11:
 <note important>​For a Zabbix proxy database, **only** ''​schema.sql''​ should be imported (no images.sql nor data.sql)</​note>​ <note important>​For a Zabbix proxy database, **only** ''​schema.sql''​ should be imported (no images.sql nor data.sql)</​note>​
  
- +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.
-**Scripts**+
  
 === 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;
-  ​# stop here if you are creating database with Zabbix ​packages+ 
 +<note important>​ Zabbix server prior to 4.4 cannot work correctly with newer MariaDB versions out of the box. See [[:​manual/​installation/​known_issues#MariaDB_row_size_error|Known issues]] for required database modifications. </​note>​ 
 + 
 +<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
   shell> mysql -uzabbix -p<​password>​ zabbix < schema.sql   shell> mysql -uzabbix -p<​password>​ zabbix < schema.sql
Line 29: Line 37:
 === PostgreSQL === === PostgreSQL ===
  
-From the command line connect ​to the database ​with a user that has permissions to create objects:+You need to have database user with permissions to create ​database ​objects. The following shell command will create user ''​zabbix''​. Specify password when prompted and repeat password (note, you may first be asked for ''​sudo''​ password):
  
-  shell> sudo -u postgres ​psql+  shell> sudo -u postgres ​createuser --pwprompt zabbix
  
-<note important>​The above command is just an example that will work in default GNU/Linux installations if the user has privileged rights. You can use different command, e. g. "psql -U <​username>"​ depending on how your database ​is configured. We assume that the system administrator knows how to connect to the database properly. +Now we will set up the database ​''​zabbix''​ (last parameter) with the previously created user as the owner (''​-O zabbix''​).
-</​note>​+
  
-Next, run the following commands once you are connected to the database:+  shell> sudo -u postgres createdb -O zabbix -E Unicode -T template0 zabbix
  
-  psqlcreate ​database ​zabbix;  +<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>
-  psql\q +
  
-Stop here if you are using [[manual:​installation:​install_from_packages|Zabbix ​packages]].+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
-  shell> ​psql -U <​username> zabbix ​< schema.sql+  shell> ​cat schema.sql | sudo -u zabbix psql zabbix 
 +  # stop here if you are creating database for Zabbix proxy 
 +  shellcat images.sql | sudo -u zabbix ​psql zabbix 
 +  shell> cat data.sql | sudo -u zabbix psql zabbix
  
-Stop here if you are creating database for Zabbix proxy. +<note important>​The above commands ​are provided as an example that will work in most of GNU/Linux installations. You can use different commands, e. g"psql -U <​username>​" depending on how your system/​database are configured. If you have troubles setting up the database please consult your Database administrator
- +</note>
-  shell> ​psql -U <​username> ​zabbix < images.sql +
-  ​shell>​ psql -U <usernamezabbix < data.sql+
  
 === Oracle === === Oracle ===
 +
 We assume that a //zabbix// database user with //​password//​ 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 Unicode database character set and a ''​UTF8''​ national character set. Check current settings: We assume that a //zabbix// database user with //​password//​ 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 Unicode database character set and a ''​UTF8''​ national character set. Check current settings:
 +
   sqlplus> select parameter,​value from v$nls_parameters where parameter='​NLS_CHARACTERSET'​ or parameter='​NLS_NCHAR_CHARACTERSET';​   sqlplus> select parameter,​value from v$nls_parameters where parameter='​NLS_CHARACTERSET'​ or parameter='​NLS_NCHAR_CHARACTERSET';​
  
-If you are creating a database for Zabbix server you need to have images on a predefined location on Oracle ​host. Copy all images from misc/images/png_modern to /​tmp/​zabbix_images ​directory ​on Oracle host:+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 to a directory ​///​tmp/​zabbix_images// on the Oracle host: 
   shell> cd /​path/​to/​zabbix-sources   shell> cd /​path/​to/​zabbix-sources
-  shell> ssh [email protected]host "mkdir /​tmp/​zabbix_images"​ +  shell> ssh [email protected]oracle_host ​"mkdir /​tmp/​zabbix_images"​ 
-  shell> scp -r misc/​images/​png_modern [email protected]host:/​tmp/​zabbix_images/​+  shell> scp -r misc/​images/​png_modern [email protected]oracle_host:/​tmp/​zabbix_images/​ 
 Now prepare the database: Now prepare the database:
-  ​shell> cd database/​oracle + 
-  shell> sqlplus zabbix/​[email protected]host/ORCL+  ​shell> cd /​path/​to/​zabbix-sources/​database/​oracle 
 +  shell> sqlplus zabbix/​[email protected]oracle_host/ORCL
   sqlplus> @schema.sql   sqlplus> @schema.sql
   # stop here if you are creating database for Zabbix proxy   # stop here if you are creating database for Zabbix proxy
   sqlplus> @images.sql   sqlplus> @images.sql
   sqlplus> @data.sql   sqlplus> @data.sql
-  ​ 
-After executing the images.sql script the /​tmp/​zabbix_images temporary directory can be removed. 
  
 +<note tip>​Please set the initialization parameter CURSOR_SHARING=FORCE for best performance.</​note>​
 +
 +Now the temporary directory can be removed:
 +
 +  shell> ssh [email protected]_host "rm -rf /​tmp/​zabbix_images"​
 === IBM DB2 === === IBM DB2 ===
  
Line 77: Line 92:
   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 ​
 +
 +<​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>​
 +
 +Zabbix frontend uses ''​OFFSET''​ and ''​LIMIT''​ clauses in SQL queries. For this to work, IBM DB2 server must have DB2_COMPATIBILITY_VECTOR variable be set to 3. Run the following command before starting the database server:
 +
 +  shell> db2set DB2_COMPATIBILITY_VECTOR=3
    
 === SQLite === === SQLite ===