Icinga

2.11. Upgrading IDOUtils Database

2.11.1. Upgrading IDOUtils to 1.13

There may be a bug within the database scheme which has been fixed. If you are upgrading from an older IDOUtils version you also need to apply those fixes manually. If you are using rpm/deb packages please read the notes and/or ask the maintainer if he has added those modifications to the install routine.

[Note] Note

Starting with 1.8, you will find newly added config options in version diffed config files in module/idoutils/config/updates e.g. ido2db.cfg_added_1.7_to_1.8.cfg.

[Note] Note

Depending on the changes to be done and the size of your database it may take a while to update your database. Please try to be patient and don't abort the script as it may leave the data being corrupt.

The upgrade files can be found next to the database install files in /path/to/icinga-src/module/idoutils/db/yourrdbm/upgrade/. The syntax is as follows:

<rdbm>-upgrade-<version>.sql

where <rdbm> could be mysql, pgsql or oracle and <version> points to the version you want to upgrade to.

[Note] Note

If you are upgrading from an older version and there are other versions in between be advised that you need to apply those upgrade files with incremental steps!

E.g. you have 1.11.7 installed and want to upgrade to 1.13.0 - you will have to upgrade to 1.12.0 first and then apply the upgrade to 1.13.0.

  1. Backup your current database before upgrading!

  2. Check current IDOUtils version and the target version. Check if there are any version in between and upgrade incremental if necessary.

  3. Apply the upgrade(s) using a rdbm user with appropriate rights. You may use the upgradedb script, but this is not recommended (for MySQL only).

2.11.1. Upgrading IDOUtils to 1.13

Starting with 1.13, the directive broker_module in icinga.cfg is deprecated. Use a module object definition inside module/idoutils.cfg instead.

Please have a look at the section "CHANGES" in the changelog as well.