Áú»¢¶Ä²©

This is the documentation page for an unsupported version of Áú»¢¶Ä²©.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

1 Database creation scripts

Overview

A Áú»¢¶Ä²© database must be created during the installation of Áú»¢¶Ä²© server or proxy.

This section provides scripts for creating a Áú»¢¶Ä²© database. A separate schema script is provided for each supported database.

schema.sql, images.sql and data.sql files are located in the database subdirectory of Áú»¢¶Ä²© sources. If Áú»¢¶Ä²© was installed from distribution packages, refer to the distribution documentation.

For a Áú»¢¶Ä²© proxy database, only schema.sql should be imported (no images.sql nor data.sql)

The order of database file import has been changed - images must be imported before data.sql now.

Scripts

MySQL

We assume that a username user with password password exists and has permissions to create database objects.

shell> mysql -u<username> -p<password>
       mysql> create database zabbix character set utf8 collate utf8_bin;
       mysql> quit;
       shell> mysql -u<username> -p<password> zabbix < database/mysql/schema.sql
       # stop here if you are creating database for Áú»¢¶Ä²© proxy
       shell> mysql -u<username> -p<password> zabbix < database/mysql/images.sql
       shell> mysql -u<username> -p<password> zabbix < database/mysql/data.sql

PostgreSQL

We assume that a username user exists and has permissions to create database objects.

shell> psql -U <username>
       psql> create database zabbix; 
       psql> \q 
       shell> cd database/postgresql
       shell> psql -U <username> zabbix < schema.sql
       # stop here if you are creating database for Áú»¢¶Ä²© proxy
       shell> psql -U <username> zabbix < images.sql
       shell> psql -U <username> zabbix < data.sql

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.

If you are creating a database for Áú»¢¶Ä²© server you need to have images somewhere on the Oracle host, for example in the /tmp/zabbix_images folder. Copy all images from misc/images/png_modern to /tmp/zabbix_images directory on the Oracle host:

shell> cd /path/to/zabbix-sources  
       shell> scp -r misc/images/png_modern user@host:/tmp/zabbix_images 

Edit the database/oracle/images.sql file and set images_dir variable to the /tmp/zabbix_images path:

CREATE OR REPLACE DIRECTORY image_dir AS '/tmp/zabbix_images'

Now prepare the database:

shell> sqlplus zabbix/password@host/ORCL
       sqlplus> @database/oracle/schema.sql
       # stop here if you are creating database for Áú»¢¶Ä²© proxy
       sqlplus> @database/oracle/images.sql
       sqlplus> @database/oracle/data.sql

Áú»¢¶Ä²© requires a UTF-8 database character set. If database is not UTF-8, it can be converted by running: ALTER DATABASE NATIONAL CHARACTER SET UTF8;

IBM DB2

shell> db2 "create database zabbix using codeset utf-8 territory us pagesize 32768"
       shell> cd database/ibm_db2
       shell> db2batch -d zabbix -f schema.sql
       # stop here if you are creating database for Áú»¢¶Ä²© proxy
       shell> db2batch -d zabbix -f images.sql
       shell> db2batch -d zabbix -f data.sql 

Áú»¢¶Ä²© 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

shell> cd database/sqlite3
       shell> sqlite3 /var/lib/sqlite/zabbix.db < schema.sql
       # stop here if you are creating database for Áú»¢¶Ä²© proxy
       shell> sqlite3 /var/lib/sqlite/zabbix.db < images.sql
       shell> sqlite3 /var/lib/sqlite/zabbix.db < data.sql

If using SQLite with Áú»¢¶Ä²© proxy, database will be automatically created if it does not exist.

Return to the installation section.