Documentation

Sidebar

Zabbix Summit 2022
Register for Zabbix Summit 2022

1 Database creation

Overview

A Zabbix database must be created during the installation of Zabbix server or proxy.

This section provides instructions for creating a Zabbix database. A separate set of instructions is available for each supported database.

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.

If installing from Zabbix Git repository, you need to run:

$ make dbschema

prior to proceeding to the next steps.

MySQL

Character sets utf8 (aka utf8mb3) and utf8mb4 are supported (with utf8_bin and utf8mb4_bin collation respectively) for Zabbix server/proxy to work properly with MySQL database. It is recommended to use utf8mb4 for new installations.

Deterministic triggers need to be created during the import of schema. On MySQL and MariaDB, this requires GLOBAL log_bin_trust_function_creators = 1 to be set if binary logging is enabled and there is no superuser privileges and log_bin_trust_function_creators = 1 is not set in MySQL configuration file.

If you are installing from Zabbix packages, proceed to the instructions for your platform.

If you are installing Zabbix from sources:

  • Create and configure a database and a user.
shell> mysql -uroot -p<password>
       mysql> create database zabbix character set utf8mb4 collate utf8mb4_bin;
       mysql> create user 'zabbix'@'localhost' identified by '<password>';
       mysql> grant all privileges on zabbix.* to 'zabbix'@'localhost';
       mysql> SET GLOBAL log_bin_trust_function_creators = 1;
       mysql> quit;
  • Import the data into the database. For a Zabbix proxy database, only schema.sql should be imported (no images.sql nor data.sql).
shell> cd database/mysql
       shell> mysql -uzabbix -p<password> zabbix < schema.sql
       # stop here if you are creating database for Zabbix proxy
       shell> mysql -uzabbix -p<password> zabbix < images.sql
       shell> mysql -uzabbix -p<password> zabbix < data.sql

log_bin_trust_function_creators can be disabled after the schema has been successfully imported:

shell> mysql -uroot -p<password>
       mysql> SET GLOBAL log_bin_trust_function_creators = 0;
       mysql> quit;

PostgreSQL

You need to have database user with permissions to create database objects.

If you are installing from Zabbix packages, proceed to the instructions for your platform.

If you are installing Zabbix from sources:

  • Create a database user.

The following shell command will create user zabbix. Specify a password when prompted and repeat the password (note, you may first be asked for sudo password):

shell> sudo -u postgres createuser --pwprompt zabbix
  • Create a database.

The following shell command will create 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
  • Import the initial schema and data (assuming you are in the root directory of Zabbix sources).

For a Zabbix proxy database, only schema.sql should be imported (no images.sql nor data.sql).

shell> cd database/postgresql
       shell> cat schema.sql | sudo -u zabbix psql zabbix
       # stop here if you are creating database for Zabbix proxy
       shell> cat images.sql | sudo -u zabbix psql zabbix
       shell> cat data.sql | sudo -u zabbix psql zabbix

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.

TimescaleDB

Instructions for creating and configuring TimescaleDB are provided in a separate section.

Oracle

Instructions for creating and configuring Oracle database are provided in a separate section.

SQLite

Using SQLite is supported for Zabbix proxy only!

The database will be automatically created if it does not exist.

Return to the installation section.